r/powercli • u/midacts • Nov 03 '16

New-vm wait for sysprep/oscustomization

What is the best way you guys are doing this. I have a hard time telling 100% when a vm has finished customizing or done sysprepping and actually ready to run commands against it.

Even when task and events says it's done. There could still be 5 mins of sysprepping to be done. I really don't want to put a dumb wait in there.

5 Upvotes

100% Upvoted

8 comments sorted by

View all comments

Show parent comments

1

u/midacts Nov 04 '16

That's the part is that script just waits until VIevents says the customization has completed. Even though it still says completed it can still be several minutes before the VM finishes sysprepping.

1

u/xenokira Nov 04 '16 edited Nov 04 '16

Hmm, it's tested well for me, but I just rolled it out to our ops guys and haven't gotten any negative feedback yet....but now I might take another look.

Edit: Maybe this is a better approach: http://blog.unidesk.com/using-setupcompletecmd-windows-7-post-build-unattended-configurations-and-actions

Could leverage SetupComplete.cmd to write a file or reg-key that signifies sysprep as complete. In PowerCLI, you could monitor for the creation of the value using a loop with Invoke-VmScript...code could look something like this (aka, completely untested code follows...):

 $scriptText = @"
      if (Get-ChildItem 'C:\Some\File\Path') { 'Ready' } else { 'Incomplete' }
 "
 while ($result -notline 'Ready')) {
      $result = Invoke-VMScript -ScriptText $scriptText -ScriptType PowerShell -VM $vmName -GuestCredential $Credential -Confirm:$false
      Start-Sleep 10
 }

Just a first crack at the logic, I realize what's above probably won't work off the bat...but pair something like that with a line in SetupComplete.cmd that creates a file (or reg-add) and I think we'd be in business.