Is this on one or more devices? If on one, did you try to remove that device from AD first?
If on more, check the netsetup.log in windows to see what specific errors are generated (see for example: Using the NETSETUP.log to debug domain join problems in Active Directory )
I have only tried it on the one device at the moment.
I will delete it from AD and try again (I was under the impression that if the device already existed in AD it would take its place)
1 of 1 people found this helpful
It should replace it... But I've seen in numerous cases that what should happen and what does happen are 2 completely different things
Again, check the netsetup.log if you want to be sure what's going wrong.
OK, I think I have made some progress - although it is not exactly "standard".
I checked the ntsetup.log and it showed that the client was trying to connect to the domain with the name of the PC which was used on the original image PC, not the random auto-generated Landesk name.
To get around the problem I inserted an additional 'Join Domain' action a bit further down in my template and that seemed to work!
I know that people say you should Install the LANDESK agent before running the Join Domain action,but if I try to move the original Join domain action below Install LANDESK agent, my template fails.
Can you clarify what you did please? Are you just using exactly same settings as that of the first Join Domain? Also can you share the delete unattend settings please?
Why not just set up your domain join in the unattend.xml?