Cloning Win7 Embeded / Change "install/WU 'id'"

[GargamelSE]

Hi, a client of mine have prepared a installation of win 7 to be deployed on Siemens PanelPC's that are running a win7 embeded pro system (each their own windows serial).
their SUS server checks the "installation id" to see which updates already applied to this id, however this is a problem, because when we use the clone, they all get the same "id", and the first one that updates, gets all updates, and the installation 2...n gets a reply no updates needed because #1 already got the updates.

How to reset this "id" of some sort for each clones so their local WSUS server see each panel as another individual, even if they are based on the same clone, and near 100% same hardware in each panels?

I had a though we might need to something like this https://support.microsoft.com/en-us/help/971058/how-do-i-reset-windows-update-components

But i am not sure this is enough.

 

[torchwood]

Hi GargamelSE,

Dont get a lot of Business type related questions here,

Anyway i'll throw something in your direction

I was under the impression that "Thin" installs are Volume licenced, your comment

client of mine have prepared a installation of win 7 to be deployed on Siemens PanelPC's that are running a win7 embeded pro system (each their own windows serial).

Not sure if thats the problem as a volume licence key will throw updating to a companies server, WSUS,
Whereas a one off product key will send it to the MS servers

Have a read of this,
http://download.microsoft.com/download/E/F/2/EF2893CF-A973-45F5-8DE0-757EBACC5324/Windows%20Thin%20PC%20Basic%20Deployment%20Guide%20v1%200.pdf


Roy

 

[samuria]

It used to be a problem in the old days and Norton created sidwalker to correct the problem