"Windows is not Genuine" Help

[useraaron321]

We recently created a new image using WDT and rebuilt all the computers in a local school we look after. Ever since we have done this we have had the message 'Windows is not Genuine' pop up on our screens after every restart. If you input the key manually or if you use VAMT it doesn't seem to matter as when you reboot the machine it just goes back to the same message. We looked into using a KMS server but according to all the other info I have searched through on the web other people experiencing the same issues still get the same message and we dont want to go through all of that just to end up in the same position.

 

It seems like most people seem to have the issue on Windows 7 with SP1. We are using 32bit system.

 

Any help would be great.

 

Thanks

[6Foot2]

We are on Windows 7: SP1: 64 Bit. Our LEA set up our new visualized servers last year. During the deployment they added KMS for us. We have found that it works well.

 

Server O/S: Windows Server 2012.

[tmcd35]

Are you using the Win7 default key, a MAK from the VLSC, or an OEM key? (I assume you're using Win7 Pro).

 

The default built in key is for activation via a KMS server.

If it's a MAK key then have you checked the number of licenses used in VLSC? Could be your out of installs and need to phone MS to raise the limit.

If you're using OEM keys they need to be unique for each machine, so if you've tried using the same key on multiple machine it would explain the message.

 

Hope that helps.

 

FIW, I'm using KMS with Win 7 SP1 and it works fine. Just need to make sure DNS is set up correctly and you have enough clients to pass the activation limit.

[useraaron321]

Hi, Thanks for the reply! Yes is a MAK. We have checked the licences in VLSC and we have plenty left and still the same problem. it even accepts the key while the computer in on but upon restart it drops out again.

[LeMarchand]

winhttp proxy set incorrectly?

[useraaron321]

Good shout but we just checked and that all clear.

[LeMarchand]

Not used MDT, but is it possible the sysprep got messed up so MS think the exact same machine is trying to validate?

[sted]

Not used MDT, but is it possible the sysprep got messed up so MS think the exact same machine is trying to validate?

 

no because you fire out a sysprepped image (it wont let you use a non sysprepped one) and it actually installs it rather than an imaging program like ghost that just dumps a copy of the files to a new hdd so evey install generates a unique sid

[useraaron321]

Ok guys we set up a KMS server and all seems to be working well now with activation so thanks for your help. Don't really understand why we needed to do that as we only have 29 computers on the network and just couldn't understand why it was so difficult.

 

Now however we have a new issue and that is that all the clients still show the black wallpaper with Windows is not genuine in the bottom right. But the machines are all happy that they are genuine. Anyone have any ideas?

[Joanne]

just change the wallpaper back? That's what I've always done

[useraaron321]

Hi Joanne, we have a GPO to change the wallpaper back but it doesn't apply it for some reason.

[Joanne]

I always had to do it manually. I know that at one point I had an issue with black wallpaper (not not genuine though) and I had to push out a reg setting to change it back... was a problem with Windows 7. I'll try and find the tech net article...

 

http://support.microsoft.com/kb/2504610

[useraaron321]

I think your right about the reg setting I think I'll give that a go. Thanks