I've probably read through every post in the AppDeploy forums regarding this issue and am still having no luck.

Maybe I am crazy but I am positive that a few months ago I had this working perfectly. While I was on vacation my base image was overwritten and since then we have upgraded our KACE 2100 to the latest version.

I have a basic Wndows 7 image that I push to a new computer. Then the drivers are installed for that model of laptop/desktop and the machine is sysprepped with the following switches... /generalize /oobe /shutdown /unattend:unattend.xml

Image is then captures and post-installation tasks are set.

Prior to April, I was able to deploy an image and not only would the rename PC and join domain script from KACE work but additional post-installation tasks such as SEP and MS Office would install after reboot. Yes, I have read this option is not available without using runonce commands but I can assure you that we had this working just fine.

Currently I am stuck trying to figure out why the rename PC and join domain script is not working as intended after a sysprepped machine is deployed. What is happening is the machine is joining the domain with it's netbios name and kcleanup is not running either. If I run this task manually after the machine has deployed from sysprep the machine joins the domain with it's Dell assett tag as instructed.

It appears something in the sysprep configuration process is preventing the computer from changing it's name and rebooting prior to running the runonce command for the join domain script.

Any ideas?

I've verified the scripts folder does not exist under c:/windows/setup.
0 Comments   [ + ] Show Comments


Please log in to comment

There are no answers at this time
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


Answer this question or Comment on this question for clarity