Solution 1:

I had this problem too. I simply had to re-input the product key, so give this go.

There is further information on how to do this here if you need it.

Solution 2:

Problem is in how Windows handle volume licenses.

You can resolve it from command line with:

slmgr /ipk AAAAA-BBBBB-CCCCC-DDDDD-EEEEE
slmgr /ato 

Detailed description can be found at KB929826

Solution 3:

I solved this problem in a much easier way. Based on some of the comments above, I just connected back to work using my VPN software and everything worked great. If the machine is not connected to the volume license DNS, it will not work.