Windows 7 OEM & FogClient
-
I am doing the same thing and here is how I am handling it without issues. (Keep in mind I am still working through HP software issues) Be sure to register the VM in FOG before starting all this.
-
I load Windows 7 in a virtual environment. This can be Virtual Box or others but I personally use VMWare Workstation so I can turn it into a VHD to inject drivers into seemlessly.
-
Once at the Computer naming screen hit CTRL-Shift-F3. This will push you into Audit mode. Don’t change the settings to the Audit mode box as of yet, just close it with the X and start your loading.
-
From there install all updates and software as needed. You can restart as much as needed it will push you back into Audit mode every time. It will continue to pop up the Audit mode box on auto login.
-
Once all loading is done take a snapshot of the virtual machine.
-
After snapshot change options on Audit mode box to OOBE and check generalize. Set to Shutdown and click OK.
-
Set FOG to upload an image from this virtual machine. and turn VM back on and let it upload the image.
-
Push the image back down to the clients as needed.
There are other steps such as driver injection and some of my software must have ID keys reset before botting up the first time, but that happens to some of us.
-
-
[quote=“Psycholiquid71, post: 9179, member: 2717”]I am doing the same thing and here is how I am handling it without issues. (Keep in mind I am still working through HP software issues) Be sure to register the VM in FOG before starting all this.
-
I load Windows 7 in a virtual environment. This can be Virtual Box or others but I personally use VMWare Workstation so I can turn it into a VHD to inject drivers into seemlessly.
-
Once at the Computer naming screen hit CTRL-Shift-F3. This will push you into Audit mode. Don’t change the settings to the Audit mode box as of yet, just close it with the X and start your loading.
-
From there install all updates and software as needed. You can restart as much as needed it will push you back into Audit mode every time. It will continue to pop up the Audit mode box on auto login.
-
Once all loading is done take a snapshot of the virtual machine.
-
After snapshot change options on Audit mode box to OOBE and check generalize. Set to Shutdown and click OK.
-
Set FOG to upload an image from this virtual machine. and turn VM back on and let it upload the image.
-
Push the image back down to the clients as needed.
There are other steps such as driver injection and some of my software must have ID keys reset before botting up the first time, but that happens to some of us.[/quote]
Keep in mind this is a very generalized of explaining it. But it should get you going in the right direction.
-
-
I don’t know of a way to keep the OEM key/activation on a complete reload. You can try removing all the bloatware to get you to a base image, and working from that, or you can scrap the OEM key and use KMS for internal activation management.
I have Fujitsu’s, and thankfully they are minimally bloated. I just had to remove the recovery CD and use GParted to get rid of the recovery partitions, and then I can image keeping the OEM activation key.
-
I just use the OEM DVD that came with my HPs, you can order them also. They are basic Windows 7 64bit DVDs. These have no HP software loaded on them. Im pretty sure if you call them they will send them to you.
For instance my 2760Ps came with 5 discs. Two DVDs were Windows 7 64 and 32 bit, and the others were recovery discs. The Windows discs are just that, Windows. They also have the OEM built in already.
-
Also not to confuse you , when loading in the VM enviro, it will say not activated. This is because the SLIP doesnt match the HP OEM DVD.
But once deployed the machines are auto activated.
-
You can use a normal MS install DVD and use the OEM method of activation, provided the activation is based on the SLP information in the bios. While not complicated, it is a little more work than a post in a forum. Take a look at [url]http://reboot.pro/16578/[/url] for information on how to do this. If you have the original rescue image (DVD or on the hard disk), you can extract the Digital OEM Certificate from the OEM directory (usually in Windows/system32/OEM) of that image.
As another poster points out, this is unlikely to work in a VM due to the bios being part of the activation process. With lots of research, you may be able to work around it.
-
-
[quote=“danuel, post: 9572, member: 628”]You read this?
[url]http://fogproject.org/forum/threads/windows-7-deployment-fog-sad2-driver-tool.380/[/url][/quote]
Just talked to my OEM dealer and found out the following so do this all at your own risk:
I did see one big error in the email below. When it comes to Microsoft Reimagining rights, customers need to do their re-imagining with Microsoft Volume Licensing media and use the Volume Licensing Media key code(s). The client is re-imagining with Windows 7 OEM media. This is not allowed with Microsoft.
Below a link confirming customers cannot re-imaging with OEM media, plus I have included the Microsoft (customer-ready) licensing brief on reimaging.
[url]http://www.microsoft.com/licensing/about-licensing/briefs/reimaging.aspx[/url]If the customer has an EA, they will need to download the media from the VLSC website, and use this Windows 7 volume licensing media for their reimagining needs. This will ensure they stay compliant.
-
[quote=“pt72, post: 9224, member: 2736”]You can use a normal MS install DVD and use the OEM method of activation, provided the activation is based on the SLP information in the bios. While not complicated, it is a little more work than a post in a forum. Take a look at [url]http://reboot.pro/16578/[/url] for information on how to do this. If you have the original rescue image (DVD or on the hard disk), you can extract the Digital OEM Certificate from the OEM directory (usually in Windows/system32/OEM) of that image.
As another poster points out, this is unlikely to work in a VM due to the bios being part of the activation process. With lots of research, you may be able to work around it.[/quote]
The activation works fine when going over to a real machine. Since the rearm is in place inside of the unattend.xml it resets the activation on load and thus letting it look at the BIOS again to let ti auto activate.
-
This post is deleted!