best luck in the new “settle up”

dont forget to flush DNS before leave :V heheheh

Cheers!

@Sebastian-Roth Hello! Right, I’ll make the push and update booth server and node, let the rep service make a full round and return the logs.

cheers

@Sebastian-Roth said in Replication Issue:

max_per_ip=200

Changes in the conf done, will let the rep job running 2 full rounds and edit this post with the results.

“Seems like the default of 50 is not enough for the amount of images you have” yeah, as I said in the chat, here we use fog A LOT, bout 7 diferent images in frequent use and others 4 used from time to time. F* good tool indeed. hahaha

Edit: Hell yeah! running like a charm! 3 rounds of rep job so far, no mismatch, no max conn reach… beautiful

tks dude! Appreciate ur suport!

tried here, very very curious things happens here, maybe its the point that makes it dont work from win 10 from script.

1-I made the scripts to get the key from FOG
2- to make sure its work I create a txt file with the key and host name in the user desktop after script slmgr -ipk KEY is used
3-the script generate an error “license not valid”
4-rerun the script now with a “echo” of what was executed (maybe key with ‘’-’’ or mispelled characters…); everything fine with the script call, no typos…
4- using the same license tried in the script I go in the GUI of windows and put it to activate… it works “digital license active”

will investigate this further…

ps.: in that regard. my apologies to fog-client… who do the job right way, MS in other hand… messing with us…

good call, I will talk better with the MS people.

Cheers!

Good holidays!

Alright! Got the problem.

Here’s the thing:

when you use an OEM license to install win 10, it will activate as a “digital license” wich means “MS only checks if the original license is a valid one, but activate with the default license for digital installation” (VK7JG-NPHTM-C97JM-9MPGT-3V66T)… I checked that getting the license active after activates using the win7 key…

Well, checking the documentations of MS and talking with some people who works with licensing I get the point that the slmgr script (after win 8.1 at least) wont work with any key whos not a volume one…

possible solutions:

1- using the postinstall scritp, create a desktop file with the win7 OEM key and go pc by pc activating manually;
2- use the default key in the fog server, and the fog client will activate the windows (it was a suggestion from one of the the people who works with licensing)

I asked about the possible “law penalties” of the 2, they say there’s little to none cause there’s one OEM license for each PC imaged, and the activating processes will update the OEM with the default. (they only suggested to keep a good list with all that keys for future use, if necessary).

That’s said, this thread can be closed.

Thanks for the responses

George, good tutorial to use the data from fog, I will use it a little more in others aspects of my environment.

Cheers

tried here, very very curious things happens here, maybe its the point that makes it dont work from win 10 from script.

1-I made the scripts to get the key from FOG
2- to make sure its work I create a txt file with the key and host name in the user desktop after script slmgr -ipk KEY is used
3-the script generate an error “license not valid”
4-rerun the script now with a “echo” of what was executed (maybe key with ‘’-’’ or mispelled characters…); everything fine with the script call, no typos…
4- using the same license tried in the script I go in the GUI of windows and put it to activate… it works “digital license active”

will investigate this further…

ps.: in that regard. my apologies to fog-client… who do the job right way, MS in other hand… messing with us…

@george1421 Hi George, I’ll look into the postinstall script, how it works (how to get data from the fog record, cause I have all keys already inserted into the DB for each host).

Thanks in advance,

Cheers

well… anyway… like in the other post, the guy make some script to activate. I’ll make on that way to (cause I have a bunch of machines, will make a csv with the data em poweshell to parse and activate).

Thanks for the responses.

Cheers

@Sebastian-Roth yeap… and from what Im seeing in the WinActivation.cs you suggested, theres no connection with any database… in the WindowsHostName.cs yes, it gets…

I sugest some improve to log file, if possible put in the “WinActivation Installing Product key” plus first or last digits of the key…

I will continue trouble shooting this…

@Sebastian-Roth if I understand that correctly, this script only try to use some key thats already was on the system (like “modern” BIOS who saves windows keys) right? Theres no use for the “Host Product Key” info in the database, for the client?

@Sebastian-Roth interesting, doubt now: the fog client do this cscript /B /Nologo C:\Windows\System32\slmgr.vbs /ipk V8DTR-W46H2-…-…-… right?

Because its what I will need to do in the powershell, with the key that I saved in the fog server “Host key” input field…

Edit:
My understanding (correct my if I get it wrong) from the process is:

1: fog client checks if the win is activated
2: if not, client goes to database and get the key for that host (here I think happens the error, and dont get the key of DB)
3: client using slmgr.vbs (under the hood) inserts that key
4: restart (and win activate next boot)

@Sebastian-Roth Yes, its possible. It was the recommendation from the MS to place I work to.

Always thought that the “host prod key” was for it =/

well… guess I’ll go for some powershell then…

@Sebastian-Roth yes, activating the win10 pro with the win7 pro license who came with the pc (if I put it manually it works fine, tested in other pc of the same type).

what seems to me by the log is the client is not getting the serial from the database and inserting it in the OS…