G
Guest
We have about 2000+ Windows XP machines deployed on our network using our
VLK. Starting yesterday, we've started to see a few machines after
performing automatic updates come up and say they are not running a legal
version of windows. After digging through some old paperwork, Microsoft
provided us with a new Windows XP VLK key a few years ago and was never
implemented into our XP building process. We use automatic updates back
to Microsoft (no WSUS server here).
How can I easily update the keys on all of machines? Is there a way
Microsoft can validate our old key for just our public IP range? I have the
ability to block Windows Updates on our border router, but that would only be
a temporary solution. The majority of our machines do not use domain logins
(so we can't just use a login script to modify the key).
Any ideas?
--greg
VLK. Starting yesterday, we've started to see a few machines after
performing automatic updates come up and say they are not running a legal
version of windows. After digging through some old paperwork, Microsoft
provided us with a new Windows XP VLK key a few years ago and was never
implemented into our XP building process. We use automatic updates back
to Microsoft (no WSUS server here).
How can I easily update the keys on all of machines? Is there a way
Microsoft can validate our old key for just our public IP range? I have the
ability to block Windows Updates on our border router, but that would only be
a temporary solution. The majority of our machines do not use domain logins
(so we can't just use a login script to modify the key).
Any ideas?
--greg