Activate Windows 7 Pro 64x
-
[quote=“davido38, post: 45085, member: 29185”]I put this in the setupcomplete.cmd
cscript //b c:\windows\system32\slmgr.vbs /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
cscript //b C:\windows\system32\slmgr.vbs -ato[/quote]Hi,
Do you use the same Key for all of your host ? I tell you that because I solve my problem with a KMS server
Regards,
Ch3i. -
Yes it’s the same key. It’s a MAK key.
-
I am BY NO MEANS an expert, but I use the unattend file to activate my windows installs
In the following pass:
[code]<component name=“Microsoft-Windows-Shell-Setup” processorArchitecture=“amd64” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>[/code]I add this, of course replace your key in place of YOUR KEY HERE, besure to include dashes, this causes windows to activate on the first run when the user logs in.
Specifically, I use the administrator account.
[code]
<AutoLogon>
<Enabled>false</Enabled>
<LogonCount>1</LogonCount>
<Username>administrator</Username>
</AutoLogon>
<FirstLogonCommands>
<SynchronousCommand wcm:action=“add”>
<CommandLine>cscript //b c:\windows\system32\slmgr.vbs /ipk YOUR KEY HERE</CommandLine>
<Order>1</Order>
<RequiresUserInput>true</RequiresUserInput>
</SynchronousCommand>
<SynchronousCommand wcm:action=“add”>
<CommandLine>cscript //b c:\windows\system32\slmgr.vbs /ato</CommandLine>
<Order>2</Order>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
</FirstLogonCommands>[/code]You could also use
[code]<component name=“Microsoft-Windows-Shell-Setup” processorArchitecture=“amd64” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<ProductKey>YOUR KEY HERE</ProductKey>
<TimeZone>Eastern Standard Time</TimeZone>
</component>[/code]and instead of passing both activation commands, supply only the cscript //b c:\windows\system32\slmgr.vbs /ato line.
-
[quote=“davido38, post: 45134, member: 29185”]Yes it’s the same key. It’s a MAK key.[/quote]
Ok. Prefer a KMS server to activate all of your Microsoft products (Windows, Office, …), it doesn’t increment your MAK activation.
It’s easy to install it, just a Windows Server.
Using KMS or not, you can use a GPO script to enter/activate your product :
[CODE]slmgr -ipk your-mak-key-here
slmgr -ato[/CODE]
Regards,
Ch3i. -
We have a policy in company that workers who leave have a right to purchase their laptop. Its a procedure. First run killdisk. Then deploy windows and hand it over. Since machines vary im looking for solution where i insert key someplace, deploy windows and hand it over so first boot happens in user hands. I really dont want to sysprep image every time with the right key. Is there a way to insert it into image that sits on fog server? And how? NB! Those PC will not join company domain again.
-
[quote=“Tauno Vürmer, post: 45143, member: 29182”]We have a policy in company that workers who leave have a right to purchase their laptop. Its a procedure. First run killdisk. Then deploy windows and hand it over. Since machines vary im looking for solution where i insert key someplace, deploy windows and hand it over so first boot happens in user hands. I really dont want to sysprep image every time with the right key. Is there a way to insert it into image that sits on fog server? And how? NB! Those PC will not join company domain again.[/quote]
Unfortunately No. You can’t use an Unattend file like that.
You must prepare an unattend file, Issue the sysprep and Generalize command, the process will read your unattend file and will complete it’s process. The machine shuts down, you upload the image to fog and then the machine begins the First installation/OOBE.
By time the image is on the FOG server, or any server, the use of the Unattend file is already surpassed.
The same can be said for WDS or, Acronis, or even Clonezilla. When the sysprep command is issued, it looks for the unattend file in the Panther folder (or the place you specify with the command.) so it’s not a limitation of FOG so to speak, but a limitation of Sysprep. I hope this makes sense.
The only way this would be beneficial to you, would be to upload an image that is still in Audit mode, with the unattend file in place. Then you can pull the image to the machine, make tweaks to the Unattend file and issue sysprep/Generalize command and the process will read your file and set the computer up like new. But then you are manually tweaking each image before you hand it off to the user :(, you can also use the Postdownload scripts to complete this task for you.
The only other option I can think of that would help you, is to edit the NTUSER.DAT file by loading it into Registry editor as a HIVE and edit the Run Once registry key so you could include a self deleting “activation” script with the same commands listed above. This would work weather your image is syspreped or not.
This will force the activation script to run when the ANY user first logs in, and then after running it would remove its self to prevent the user from finding, tampering, or expunging any information from it.
-
Mind you, there is another viable option.
If you have a listing of Keys you would like used, you can use the postdownloadscripts feature of the imaging process to inject the relevant unattend file directly into the system you’re imaging rather than having to sysprep a whole bunch of images.
-
I’m not trying to sound mean or rude, though it can easily be thought as much.
Rather than looking for all the excuses you think are going to make it seem like FOG is failing in some way, maybe make an attempt to understand what can actually be done.
I’m stating this in the sense that you state “I don’t want to have to…” That’s the wrong approach. You’re trying to something to make your life a little easier. Over thinking what actually needs to be done is a common problem we ALL face in the IT world.
I know the postdownloadscripts feature is relatively new and there’s little documentation on it, there is still a couple of threads with pretty decent examples of how to use them. This was brought in in 1.2.0 and is plenty capable.
-
[SIZE=3]Ok Tom, tnx for the hint
am i on the right path? under /images/postdownloadscripts i have the following files:[/SIZE]
[SIZE=3]fog.ad, fog.drivers, fog.postdownload, fog.snapins (rather than having a bulk of code just in fog.postdownload - keeps it nice and seperate) quote from antother thread[/SIZE][SIZE=3]So file fog.postdownload bascially enters all its content via cmd? Basically i should add a command slmgr.vbs -ipk 00000-00000-00000-00000-00000 (replace zeros with real product key) somewhere? Since i cant access my fog server atm i cant see this file either. But is this somewhat correct?[/SIZE]
-
The postdownload scripts could be used to inject an appropriate unattend file. I’m telling you this is most likely your simplest fashion. However, because you want the end user to be able to enter their own hostname/username etc… A similar approach could be used to create a set/series of setupcomplete.cmd that would contain the batch command you’re talking about. The setupcomplete.cmd would be run after all the main stuff is all done.
-
How to get product key from fog server and use in script?
Maybe a script running under Windows 7 x64 something like:
$key=http://x.x.x.x/fog/…?mac=xx:xx:xx:xx:xx:xx
cscript //b c:\windows\system32\slmgr.vbs /ipk $key
cscript //b C:\windows\system32\slmgr.vbs -atoP.S. I have install fog 1.2 on QNAP NAS TS-212 without multicast.
-
@SirAdams said:
How to get product key from fog server and use in script?
Maybe a script running under Windows 7 x64 something like:
$key=http://x.x.x.x/fog/…?mac=xx:xx:xx:xx:xx:xx
cscript //b c:\windows\system32\slmgr.vbs /ipk $key
cscript //b C:\windows\system32\slmgr.vbs -atoP.S. I have install fog 1.2 on QNAP NAS TS-212 without multicast.
I like it.
