KACE Product Support

It could be uac blocking it try turning uac off. If it a scripted install of windows 7 then UAC can be turned off in the Autounattend File.

Another thought i just had are you running the post install tasks as an administrator?

cserrins, Yes, we are deploying images, not using scripted installs. I do have sysprep integration checked and I am using call commands if trying to run other batch files from a batch file.

So I found some info last night in regards to Windows 7, sysprep, and the Run Once command. I found a post that said that there was an issue with the KBOX2000 not running post install tasks correctly and that you needed to specify "C:\windows\setup\scripts\setupcomplete.cmd" in your answer file. I did this and all post install tasks ran, with the exception of my domain join. I think I have a problem with that script so I am doing some testing this morning along with CordlezToaster's comment to disable the UAC.

As far as CordlezToaster's comment about running the tasks as administrator, how can I specify a user?

So here is my update:

I removed the runonce setting in the answer file and disabled UAC. My post install tasks appear to run without error now, except for the part where I change the machine name. I am currently using the zip file from KACE that uses wsname to change the name, reboots, then joins the domain. The same task works on my XP boxes. For WSNAME, we are using a file that references the mac address of the machine to designate a name.

Also, I have specified driver paths in "offline Servicing", but during setup, it does not install the missing drivers. I can install the drivers by hand with no error. I am copying down the drivers to "C:\drivers\etc..." I am not assigning a user name or password in the answer file on the driver paths because it should not need it since it is looking at the local machine.

Any help with these two areas would be great. Thanks

I might be able to help you with wsname, just some things i though of that got me.

In regards to wsname do you have exclude some mac address in the command line?
My Example:
wsname.exe /RDF:dhcpnames.txt /DFK:$MAC /EXCLUDEADAPTERS[WIRELESS WLAN VMWARE BLUETOOTH PPP IPSEC]

Does the whole thing not work or does it do the rename but not the domain join?
Im not sure how your doing it as i hade to create my own scripts and bats to get the rename and domain join to happen. But i had to make sure it included the entire path in execution and had to have "" marks wrapped around commands with spaces in the name.

Cordlez,

I believe your command line is the same as mine, just a different path to the file. Here is the funny thing, I can run the wsname command line (as long is I remove the domain join) after setup is complete, and it is fine. There is something not happy when I attempt to do the wsname within the kbox2000 post install tasks on Windows 7 only.

Domain join is fine. I had a problem with my script. That is what happens when you are staring at scripts all day. [:D]

If I could also figure out the driver paths as well. I have tried putting them into offline servicing, no go. I have created a run synchronous command for pnputil under the specialize path. Seems like there are a million ways to do it, but no "right way".

Another way of looking at it would to get the autounattend file to join the domain with the wrong computer name then just run wsname to rename in the domain.
So the command would look something like this

wsname /RDF:"F:\DATA\MACAddress to PC Name.txt" /DFK:$MAC /EXCLUDEADAPTERS[WIRELESS WLAN VMWARE BLUETOOTH PPP IPSEC] /rcid /user:mydomain\administrator /pass:secret

Im currently exploring both, but i think this way is a better way of doing it.

When I add the info for joining the domain in the answer file, it does not join the domain, so therefore, I can not rename the computer.

Am I doing something wrong? I am not re-running sysprep everytime I make a change. I am simply replacing the unattend file with a new one. It just seems that no matter what I do, nothing is doing what it is suppose to. Very frustrating.....

Sorry for the long delay, but we got it worked out. Had to contact Kace support and here is what we found out and then did to make it work:

Figured out that the run once command was running immediately after the registry entry was made. Moved the runonce command up one level in the script.

This next one is due to me not knowing Windows 7 sysprep 100%, we needed to replace the unattend.xml in the c:\windows\panther directory because we needed to add another reboot. Did not realize at first that sysprep makes a copy of your unattend.xml and puts it there.

After that, it works like a champ.

Thanks for all your help.

Where are you guys finding the answer file on an image deployment?

"So I found some info last night in regards to Windows 7, sysprep, and the Run Once command. I found a post that said that there was an issue with the KBOX2000 not running post install tasks correctly and that you needed to specify "C:\windows\setup\scripts\setupcomplete.cmd" in your answer file."

Seems like it's not running the setupcomplete.cmd at the end of the image deploymen, since kcleanup is still in C: