shawn1024 Posted April 17, 2007 Posted April 17, 2007 Wondering if anyone else is running into this situation. I created a set of Vista Business images about 30 days ago that are placed on computers we sell. I imaged up one of my computers a couple days ago and noticed that the activation grace period was only showing 2 days left until the OS would need to be activated. It use to show 30 days. We are an OEM, and use the OPK tool set for Vista unattended installs. I imaged up another computer today and pressed Ctrl + Shift + F3 when the first OOBE screen appeared attempting to launch sysprep and reboot back into audit mode so I could attempt to generalize the image. Unfortunatley, the image will not reboot back into audit mode.....and I can not get past the PID entry screen. The activation grace period has apparently expired.Here's the basics on how the images were created:-OS is an unattended network installation.-After install completes I run --> sysprep /generalize /audit /unattend:d:\autounattend.xml /shutdown.-Boot back into audit mode & installl apps, then run --> sysprep /oobe /unattend:d:\oobeunattend.xml /shutdown. -Capture image to network share for deployment on other machines.Questions and/or items I am testing to fix this:-Maybe my last sysprep step should have been --> sysprep /generalize /oobe /unattend:d:\oobeunattend.xml /shutdown ??-Our MS rep suggested using the "Microsoft-Windows-Security-Licensing-SLC | skiprearm=1" setting in my xml files. The only option is to run this tag during the generalize pass. I have not tested this setting out yet and am not that familiar with it to date. This gets us past the running sysprep 3 times rule? or is it the running sysprep /generalized 3 times rule? or is it breaking into a sealed image with the Ctrl + Shift + F3 3 times rule? I am a little confused on this one.Any thoughts, experience or advice on this topic is appreciated. Thanks in advance.Shawn
shawn1024 Posted April 18, 2007 Author Posted April 18, 2007 After some additional testing I have one question answered.1. When I seal the image (run sysprep last time) The correct command should be:--sysprep /generalize /oobe /unattend:d:\oobeunattend.xml /shutdown--save image off to network share for distribution to other machines.My previous images expired because the /generalize command was not used when I sealed my first images.I am still testing "Microsoft-Windows-Security-Licensing-SLC | skiprearm=1" setting. Currently I have this set in my autounattend.xml, but I do not have it set in my oobeunattend.xml file.Shawn
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now