Windows 7 Thread, win 7 sysprep in Technical; ive just altered my normal x64 win 7 sysprep file to try and get it to autojoin a domain but ...
1st July 2010, 09:32 AM #1
win 7 sysprep
ive just altered my normal x64 win 7 sysprep file to try and get it to autojoin a domain but ask for computer name does the following look right (as atm short of sysprepping my home pc/laptop (and i dont have a domain here anyway) does this look right to anyone?
GMT Standard Time
ou=staff domained laptops win7x64,dc=domain,dc=local
1st July 2010, 10:04 AM #2
You can't ask for a computer name *and* join the domain with the supplied sysprep. You either need to prestage the name or use something like mysysprep2 or script the join in a late stage.
With the supplied tools, the join will happen BEFORE the computer name is changed. When this is changed in the oobe pass, then the machine account trust from the domain gets broken.
Microsoft know, they don't care.
1st July 2010, 12:35 PM #3
- Rep Power
You can actually have it prompt you for a computer name, and then in the oobe System phase run a powershell command to have it join to the domain, all it will ask you is for a valid PW. This is how we are currently setting up our Win7 PC's.
C:\windows\system32\windowspowershell\v1.0\powershell.exe -command "Add-Computer -domainname xxxx -cred xxxx\administrator"
1st July 2010, 12:39 PM #4
thanks both its not essential it joins the domain but would be nice although sometimes with win7 ive found if i fore the image out from wds (using my old sysprep file basically the same without the domain bits) it will autoname them username1 and domain it without being asked if only it was consistent lol
1st July 2010, 12:48 PM #5
with WDS, you can set it so that unknown computers must be approved by an administrator
this generates a Request ID, adds the PC to the Pending Devices container in WDS.. right click the ID and give it the appropriate name, this then creates the AD comptuer account and auto-names the PC during imaging.
right click servername.domain.local then choose properties then set the PXE Response Tab as shown...
It only does this the once..
The ONLY caveat I have found is that if you delete a WDS-Staged Computer account, you need to wait 30 days before you can WDS it again, this is something to do with the WDS ID Database not syncing with AD...
1st July 2010, 01:10 PM #6
We had a similar issue and found that by using the following command it will clear things out and WDS will then give the machine an IP address and allow you to continue again.
The ONLY caveat I have found is that if you delete a WDS
-Staged Computer account, you need to wait 30 days before you can WDS
WDSUTIL /Delete-AutoAddDevices /DeviceType:ApprovedDevices
1st July 2010, 01:12 PM #7
Doesn't that delete all devices and force them to receive new request IDs ?
1st July 2010, 01:26 PM #8
Quite probably, we were looking to continually rebuild a test machine and this was the only way we found to make it work.
We are still in the learning stage though so any advice will be greatfully recieved, especially if we are committing a huge no no in using that command.
By Chuckster in forum Windows Server 2008 R2
Last Post: 18th February 2010, 04:47 PM
By Chuckster in forum Windows
Last Post: 29th October 2009, 12:05 PM
By Ste_Harve in forum Windows
Last Post: 31st July 2008, 02:51 PM
By tosca925 in forum Windows
Last Post: 7th April 2006, 01:53 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)