Environment
Situation
ERROR: "Could not locate the target container"
The relative path for the Import process is not being read
correctly.
Within a Server Policy Package, under the "Workstation Import Policy" properties, the "Platforms" tab can be selected. Under the specified platform, the administrator has the option to import the workstation into a "User Container". Also, can be used relative path to specify the container where the workstation is going to be imported.
Situation:
O=NTS
OU=RioDeJaneiro
OU=Users
OU=Zenworks
OU=Workstations
OU=Policies
OU=Provo
OU=Users
OU=Zenworks
OU=Workstations
OU=Policies
Suppose you want to use a relative path to specify the container
where the workstation should be imported. For example, you want to
import the workstation objects under the container"Workstations.Zenworks" available under each site. In order to do
it, you need to use relative path in the workstation import policy,
choosing "User Container" and using "dots" in the end of the path
to inform the number of containers above it belongs.
In the DS structure described above, you should use the following
relative path: Workstations.Zenworks.
Explanation: The path is read from the right to the left. The "dot"
at the end specify that the import process should move one
container above the container "Users", this is "RioDeJaneiro". Then, it should
go down to the container "Zenworks", finally go down again
to "Workstations".
When you configure this relative path in a policy running on a
Linux box, it just does not work. Looking in the debug log file
generated by the import process, you will see that the process does
not interpret correctly the "dots" used to separate each
container:
-----------------
Nov 24, 2007 9:17:40 PM User context = Users,RioDeJaneiro,NTS
Nov 24, 2007 9:17:40 PM Login count = 0
Nov 24, 2007 9:17:40 PM ENTER
doContainerSearch -
Workstations.Zenworks,RioDeJaneiro,NTS
Nov 24, 2007 9:17:40 PM Could not
find container workstations.zenworks,riodejaneiro,nts
-----------------
The import process (JAVA) uses ldap searches to locate the
container. The process does not interpret correctly the "dots" used
to separate each container.
Resolution
Workaround:
You can use comma as container's separator:Workstations,Zenworks.
NOTE:it just should be used for import policies running on Linux servers. For Windows/NetWare servers, use "dot" as container's separator.