Windows 7 Activation Proposal
I’d like to suggest that FOG auto-activate computers after imaging. In my current environment there are many different models each with a unique product key, meaning each computer must be activated manually. This automation would be accomplished with the hostname changer used in the FOG Client. Below is the current code that I have been using.
Note that the wiki’s instructions are not up to date below are the changes, in the format old_command => new_command
You may also have authentication issues if you try and unzip the init.xz file where it resides, if so move it to another folder and move it back when finished)
The key should be base64 encoded. Let me see if it’s being decoded in the GUI
I tried to copy my windows 7 keys from a another db to the new column in the host table.
The result looks like this:
Then i inserted the key directly in the webgui and the key looks like this in phpmyadmin:
It looks like the key will be saved in a crypted way? Is that correct ?
@Tom Elliott, post: 35481, member: 7271 said:
Pretty much, yes.
Ok i will give it a try.
Added the WIn7 Key to the Host details and removed the serial from the client.
Replaced HostnameChange.dll and rebooted client.
After reboot the client was activated again. Perfect !!
Big Thanks to Jbob and Tom.
I hava only one suggestion:
Is it possible to write some informations about the activationprocess to the fog logfile ?
e.g. if the activations fails and why? Or it was succesfull.
Pretty much, yes.
@Tom: so if i’m using fog 1.2 i only need to replace the “HostnameChange.dll” created by Jbob to run the win7 activation during the hostchanger task ?
This is a great feature, thanks jbob!
SVN 2056 should have these code revisions now.
The MOD_HostnameChanger.cs script has been updated as well, but it HAS NOT BEEN COMPILED in fog client.
@Tom Elliott, that is great, it is one less thing I have to implement each time I upgrade!
I hope you don’t mind, but I’m using this code and adding it. I’m going to ask if the user wants to add the product key on registration. The key changer/updater function is now embedded in ipxe, meaning no need for the key.register.php or the fog.key.reg files.
@Ivanov Alexandru I believe it should work with no changes but currently where I work we are still running 1.1.0. My guess is that some of the line numbers may be off. However, if you would like help implementing it into 1.1.2 I would be more than willing to assist you. You can PM me if you wish me to help.
Hello Jbob , if i make these changes to the last %(#555555]Version)[
@axel12: I may not be understanding you, but at the institution I work at we do not have the luxury of volume licensing, each computer has its own unique product key.
@jayphizzle We just upgraded to 1.1 and implemented it, but we were using this modification on 0.32 and 1.0.1. There are additional changes I have implemented. However, I am going to re-code them to be cleaner. Once I do that I’ll post all of my changes.
[B]Edit[/B] All changes I have made for v1.1 are now in the original post in case this feature is not put into FOG but people, like jayphizzle wish to implement it.
@JBob: very nice customization. We have the same activation ‘problem’, but using a autoit script which runs after each deployment.
I would be great if this can be handeld by fog as well.
Which version are you using? Are this the only changes which are needed?
bro, Microsoft has got you covered …
We use VAMT at my school. You can have the choice of using MAK activation (not KMS) if your school does purchase keys in volumes. OR you can activate with no key - which will use the native key already built into the windows box.
Also note this will work for Office too … and work through a proxy as well.
The only requirement is that the windows box MUST be on the domain - so you don’t even need any AD usernames / passwords - since the authentication is done locally from the credentials you are already using.