Snapin Questions
- 
 @Wayne-Workman This is the script… cscript C:\Windows\System32\slmgr.vbs /skms kms7:1688KMS7 is just a DNS name for the “server”. And no you don’t have to do anything except put in admin credentials to run as admin. 
- 
 If you select a batch script template you will notice you are missing the /cparameter.
- 
 @Joe-Schmitt What does the /c parameter do? 
- 
 
- 
 @Joe-Schmitt Thanks! I’ll check it out. I’m still trying to learn this stuff. 
- 
 It could also be because of the messed up filetype not existing. Cmd is weird sometimes. 
- 
 @Joe-Schmitt Any ideas of what to try? Will powershell handle that any better? 
- 
 I would try the /cas I suggested.
- 
 @Joe-Schmitt No problem. I would add that to the end of the script or just leave it in the parameters within FOG? 
- 
 Use the template feature and select batch script. 
- 
 @Joe-Schmitt Thanks Joe! I’ll give that a go! 
- 
 @Joe-Schmitt Alright, I searched and searched and tried and tried but I cannot for the life of me figure out the how to get a script to run with elevated privileges. The command structure works, it just won’t run unless you are an admin. Any ideas are appreciated. Thanks! Cheers, Joe 
- 
 @Joe-Gill all snapins run as SYSTEM, which has the highest authority over the local system, more than the admin account has. What part of the script needs admin? 
- 
 W10_edu_act.cmd c: cd \windows\system32 c:\windows\system32\cscript.exe //B c:\windows\system32\slmgr.vbs -skms kms7:1688 >> c:\SnapinLogs\W10Activate.log c:\windows\system32\cscript.exe //B c:\windows\system32\slmgr.vbs -ato >> c:\SnapinLogs\W10Activate.log.cmd files are handled by the fog client without any run with parms, and you wont have any local permissions issue. 
  I don’t use a KMS server, so I am unaware of if it would require domain credentials. I would think the machine would have to be domain joined though. I also was under the impression that you can set the KMS details as part of the domain policy. 
- 
 @Wayne-Workman Interesting… It just doesn’t ever seem to run. I can run the script aside from fog using “run as admin” and it does just fine. If I run it without elevated privileges it does not seem to do the command right. 
- 
 @Joe-Gill Have you tried putting in your key for a single host in the Product Key field, and seeing if the fog client will activate windows that way? 
- 
 @Mentaloid I’m very green on a lot of this stuff so bear with me. I would think what you have right there should work just fine. I’ll be working on all of this stuff a little later this week. I’ll give that a try. 
- 
 @Wayne-Workman Not yet. It’s on my list. LOL! 
- 
 @Wayne-Workman I have done this with the MAK key. That works fine. We just wanted to switch over to KMS. Which with our script snap-in it seems to be activating just fine now. I still need to refine it though. I think I’m going to add @Mentaloid’s suggestions to my existing script. I do believe that will finalize automation.  
