Snapin Questions

[Joe Gill]

@Wayne-Workman No. All I do to run it is select run as administrator and away it goes. Now I did discover that my syntax was bad. Now I’ve got that straightend up.

I saved the file as a cmd file. It does refer to a vbscript program though. Either way Command prompt will run it just fine.

[Wayne Workman]

@Joe-Gill Does it in any way/shape/form access a share?

Can you give us a copy of the script, please remove sensitive keys and such.

[Joe Gill]

@Wayne-Workman This is the script…

cscript C:\Windows\System32\slmgr.vbs /skms kms7:1688

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

[Joe Schmitt]

If you select a batch script template you will notice you are missing the /c parameter.

[Joe Gill]

@Joe-Schmitt What does the /c parameter do?

[Joe Schmitt]

http://ss64.com/nt/cmd.html

[Joe Gill]

@Joe-Schmitt Thanks! I’ll check it out. I’m still trying to learn this stuff.

[Joe Schmitt]

It could also be because of the messed up filetype not existing. Cmd is weird sometimes.

[Joe Gill]

@Joe-Schmitt Any ideas of what to try? Will powershell handle that any better?

[Joe Schmitt]

I would try the /c as I suggested.

[Joe Gill]

@Joe-Schmitt No problem. I would add that to the end of the script or just leave it in the parameters within FOG?

[Joe Schmitt]

Use the template feature and select batch script.

[Joe Gill]

@Joe-Schmitt Thanks Joe! I’ll give that a go!

[Joe Gill]

@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

[Wayne Workman]

@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?

[Mentaloid]

@Joe-Gill

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.

[Joe Gill]

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

[Wayne Workman]

@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?

[Joe Gill]

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

[Joe Gill]

@Wayne-Workman Not yet. It’s on my list. LOL!