Windows 7 OEM & FogClient



  • So I have a question… it has worked in the past with XP however with Win7 it doesn’t.

    We purchase HP machines from our vendor and so each has it’s own Win7 Key. However since it is an HP they have their “special OEM key”. With XP we were able to rip that serial using jellybean or whatever program and then put that key in our sysprep and everything would work as advertised.
    With Win7 however it will not accept that key. I am assuming we may be able to still do it if we started with the installed OS (the one with the bloatware) however when we tried that in the past it adds ~40 minutes to the image upload/download (for some strange reason).
    Anyone know of a work around for this?? I may just be going about this the wrong way.

    Also with Windows 7 and doing snap-ins and printer management on Win7 boxes whenever we push a snap-in or a printer it doesn’t install and instead invokes the “interactive services” screen which then normally comes up with an error etc. It works fine on XP, only does this in Win7. From what I’ve understood this is because of the way User0 is not used anymore in Vista (we have none of those) and Win7 so if the program isn’t updated it will not work properly. It doesn’t always push printers and/or software and now constantly keeps bugging users with the interactive services pop-up and I cannot find a way to get it to stop.
    Anyone have any ideas there?


  • Banned

    This post is deleted!


  • [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.



  • [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.





  • 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.



  • 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.



  • 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.


  • Moderator

    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.



  • [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.

    1. 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.

    2. 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.

    3. 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.

    4. Once all loading is done take a snapshot of the virtual machine.

    5. After snapshot change options on Audit mode box to OOBE and check generalize. Set to Shutdown and click OK.

    6. Set FOG to upload an image from this virtual machine. and turn VM back on and let it upload the image.

    7. 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 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.

    1. 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.

    2. 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.

    3. 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.

    4. Once all loading is done take a snapshot of the virtual machine.

    5. After snapshot change options on Audit mode box to OOBE and check generalize. Set to Shutdown and click OK.

    6. Set FOG to upload an image from this virtual machine. and turn VM back on and let it upload the image.

    7. 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=“noviceuser, post: 9019, member: 868”]So I have a question… it has worked in the past with XP however with Win7 it doesn’t.

    We purchase HP machines from our vendor and so each has it’s own Win7 Key. However since it is an HP they have their “special OEM key”. With XP we were able to rip that serial using jellybean or whatever program and then put that key in our sysprep and everything would work as advertised.
    With Win7 however it will not accept that key. I am assuming we may be able to still do it if we started with the installed OS (the one with the bloatware) however when we tried that in the past it adds ~40 minutes to the image upload/download (for some strange reason).
    Anyone know of a work around for this?? I may just be going about this the wrong way.

    Also with Windows 7 and doing snap-ins and printer management on Win7 boxes whenever we push a snap-in or a printer it doesn’t install and instead invokes the “interactive services” screen which then normally comes up with an error etc. It works fine on XP, only does this in Win7. From what I’ve understood this is because of the way User0 is not used anymore in Vista (we have none of those) and Win7 so if the program isn’t updated it will not work properly. It doesn’t always push printers and/or software and now constantly keeps bugging users with the interactive services pop-up and I cannot find a way to get it to stop.
    Anyone have any ideas there?[/quote]

    I am thinking that you need to talk to your Microsoft people and get a volume key, so that you can use that volume key on your deployments Because with the OEM keys you are going to have that problem.


Log in to reply
 

437
Online

38955
Users

10706
Topics

101580
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.