You can quickly update the password in the xml and reimport on your WDS server when you have another bulk deploy operation.ĬMD /c REG.exe add HKLM\System\CurrentControlSet\Control\Network\NewNetworkWindowOff /f If you're security conscious create a wds domain joining account, just for that purpose that controls a specific OUs computer objects (there are guides for this), and just change the password on your domain join service account after a mass deployment. Note that this xml also contains a structure for domain joining in the oobe stage which as worked for me. In short try this command in the oobe stage:Ĭ:\windows\system32\WindowsPowerShell\v1.0\powershell.exe -executionpolicy bypass -noprofile -command "Start-Transcript (Get-WmiObject win32_computersystem).Rename((Get-WmiObject 'win32_bios').im()) Stop-Transcript" It says ~1000, but I've tried with powershell commands that were ~500 chars and they silent fail. I recommend running the pc rename in the oobe stage.Īlso commands to be executed have a max length of ~250 characters total. ProTip (After a deployment go to C:\windows\panther\UnattendGC\setupact.log to review what was processed and when.) So if you have a PC name specified in WDS client naming policy and have the xml configured to rename, then you'll run into that issue. As a note :Synchronous Commands in the Specialize Stage Appear to Run BEFORE other sections in the same stage.
0 kommentar(er)
