SOLVED Windows 7 Product Key

  • What is the proper format for entering the windows 7 product key in Fog?
    Caps, dashes, etc?

  • @kman1232 Create a batch file and get it to work like that first. Batch files have a .bat extension, they are considered a windows executable type of file.

    You’d upload the script into a new snapin, then test deploy that on a client and see if it works or not.

  • @Wayne-Workman So if I was going to enter this as a Snap-In would I put this in the “Snapin Run With Argument” or
    “Snapin Arguments” section? I tried copying this script and entering it in the “Snapin Arguments” section and click add, However when I list all snapins it doesn’t appear to be saving. I also checked my server in the /opt/fog/snapins but it also appears to be blank. I am using Fog Version 1.2.0

  • @Wayne-Workman Thanks!

  • Moderator

    I would try to use KMS if you can, if your doing this for OEM it will be a pain…

    You could run the script via batch file, snapins, wpkg, opsi, GPO. It all depends how you are setup and how your environment works.

  • @jcyphert said:

    @VincentJ Sorry if I’m missing something; Where do you put this? Is this something at fog pushes out or log in scripts?

    You would create a batch file with commands in it, and upload it to fog as a snapin.

    This is done through the Snapin Management page. For a simple script, normally you don’t need to worry about the “run with” and “arguments” parts - that’s for other kinds of deployments (mostly MSIs).

    When the snapin has been created in FOG, you would have either a single host or a group execute that snapin by going to tasks -> advanced -> single snapin. There are also other ways to push a snapin.

    Obviously, one of the FOG Clients are required to be installed on hosts for FOG to allow any sort of control post-imaging.

  • @VincentJ Sorry if I’m missing something; Where do you put this? Is this something at fog pushes out or log in scripts?

  • @Leon-Hordyk My script is incredibly similar to @VincentJ 's script, less in fact.

    cscript //B "%windir%\system32\slmgr.vbs" /ato

    My key is already stored in my image, and I just needed the computers to try to activate.

  • @Wayne-Workman
    I just got back from a long weekend, would be interested in the snap-in you are talking about. Currently we have about 200 machines, each with an OEM product key. We have the keys in csv files and for our Lenovo machines run a vbs script manually after fogging (requires admin privileges). Our HP machines won’t accept that script so we ‘cut and paste’ the key manually to register with MS.
    I haven’t any experience with snapins and FOG but have two weeks or so to fiddle before school begins and all of these computers need to be up and ready.

  • Moderator

    This is the process for a KMS Server… so use the part that you need.

    slmgr.vbs -ipk FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4
    slmgr.vbs -skms IPADDRESS:1688
    slmgr.vbs -ato
    slmgr.vbs -dlv > c:\KMS.log

    The key is the public KMS one that you input into clients.

    Mod edited to use code box.

  • I recently used snapins to deploy a Win7 key and activate windows. I’m at home right now but if you’re interested, let me know and I’ll put it here while I’m at work.

  • Senior Developer

    Include dashes. As for caps, that doesn’t matter but I would as windows product keys tend to be all caps.