Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Altiris Deployment Solution An Invalid dn syntax has been specified

Created: 11 Sep 2012 | 4 comments

Hi Guys

I always have a problem with the Deployment Solution 6.9 SP5 when i configure some PC over the the Console with right click on Client -> Configure  changing the Computername to something else that the configure Job will end up in an error witj An invalid dn syntax has been specified

I always got this error:

 

why I can`t reconfigure Clients? The permissions for the service user of altiris for Domain Join is correct in the AD and on the client.

Someone can help me?

Regards

Dominik

 

Comments 4 CommentsJump to latest comment

bhawver's picture

Someone else posted something like this in the past...not sure if it applies to you or not:

https://www-secure.symantec.com/connect/forums/invalid-dn-syntax

Also, I would verify that what you are typing is exactly what is in Active Directory.  See my example below:

FQDN.COM DOMAIN

--AD (OU)

---------LOCATION1 (OU)
------------------------Servers (OU)
------------------------Users (OU)
------------------------Global Groups (OU)
------------------------Computers (OU) <----location of object

---------LOCATION2 (OU)
------------------------Computers (OU)

In the above example the domain you would type in would be:  FQDN.COM/AD/LOCATION1/Computers

I want to say, if the computer account already exists in the domain, you may need to just put in "FQDN.COM" (in this example) or it may complain similarly because the object already exists.

Hope this helps.

Brian Hawver
Systems Engineer
Yaskawa America, Inc.

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

bhawver's picture

Also, one thing further on the link I posted above, I've found, especially in Win 7 environments, it is best to separate the name change and domain add into separate tasks.  Both tasks can be part of the same job though.

Brian Hawver
Systems Engineer
Yaskawa America, Inc.

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

wiesel2882's picture

Hi

Thank you for your fast response!

I`ve tried all things that you described. No success.

Regards Dominik

bhawver's picture

Let's try one thing at a time.

Configure the problematic machine and change the computer name, but not add it to the domain.  Put it into  a workgroup named "workgroup".

Once that is successful, we can try adding that same computer into the domain separately.

Brian Hawver
Systems Engineer
Yaskawa America, Inc.

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.