can anyone help me?
This is relevant to a previous post (also from Frank) regarding the breakage of licences.
It looks like the server id for windows servers is obtained from the SID or something similar, which will be different for a new OS install and prevent a successful putlic of a stored license.dat.
I have a feeling that this issue is unresolvable without changing the way we calculate the server id for windows servers.
Note that there aren't (and won't be) any servers on this site which have simultaneous access to agents and the internet, so autolic is not possible in this case.
Not even a server with access to an HTTP proxy?
A license key is based on two key pieces of information.
One is the number of CPUs in the system which is based
on groups of 4 (i.e. 1 CPU is the same as 2 CPUs but 3 CPUs
to 4 CPUs will cause a new license key to be needed). The
second is what we generaly call the "hostid". There are
various approaches to determining a host's hostid but for
Windows we use the serial number of the System drive.
Assuming that you have not added new CPUs I ask if it is
possible that the serial number of the system drive may
Not even a server with access to an HTTP proxy.
The server was built with PM, backed up, built with PM again and restored.
Apparently the serial number of the system drive can change when it is formatted, which is done as part of the provision.
good stuff. so thats the reason then.
That's the reason, but what's the solution?
Is it possible to format a drive in such a way that the serial number is constant?