We help IT Professionals succeed at work.

Hyper Not Genuine

Hi all,

I really need all of your help for this one. I have Windows Server 2008 R2 Hyper V server with critical virtual machines and this morning out of the blue, the virtual machines won't start.

At first I thought it was due to the wrong time on the server. I changed the time in the bios and restarted. Nothing.

Then I notieced that on the bottom right of the screen after I login it says This copy of Windows in not Genuine. I am assuming this is the reason that I cannot start the virtual machines. I really need some help as my file server with all of our files are on one of the virtual machines.

I did some research, but cannot find anything. I ran notepad and it gave me a licensing page with an option to resolve the licensing issue, I click resolve and I get an error that it cannot access that page.

Please help!
Comment
Watch Question

Svet PaperovIT Manager

Commented:
You should buy a license for this server. Meanwhile, you can run slmgr.vbs –rearm from elevated command prompt to extend the evaluation period of your server.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
Have you Activated this Server?
brwwigginsIT Manager

Commented:
are you sure it's an actual Hyper-V server install and not a Core or other install with the hyper-v role enabled?

The hyper-v server is free and does not need licensing. However if you installed one of the full version products and just enabled the hyper-v role then you'll need a license.

Author

Commented:
Thanks for all of the responses. The server is just the core, which is free and from what I understand, doesn't need to be activated.
VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017
Commented:
if its not this download, youll need a license

http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=3512

Author

Commented:
hanccocka,

How do I know which version is installed?
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
who installed it?

where was it installed from?

Author

Commented:
One of my techs installed it, I am not sure where he got it from. What your saying makes sense since yesterday was 180 days since we installed it. The install date was 7/5/11.

So, I tried the slmgr.vbs, to try and rearm it, but it telling me I need to have elevated privelleges. Any help there?
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
Run As Admin
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
highlight the command prompt and right click Run As Admin

Author

Commented:
I tried running as local and domain admin, still says I need elevated permissions to run the command

Author

Commented:
That is not an option when I right click the command prompt. Remember, this is a core server. How do you highlight the command prompt?
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
Right Click COMMAND Prompt.

or type runas

Author

Commented:
This is what I typed.

runas /user:administrator@corporate.local slmgr.vbs -rearm

I get an error stating that the file doesn't exist. Do I need to do this even though I am logged in as adminstrator or domain administrator?

Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
do you have the file slmgr.vbs?

Author

Commented:
I am assuming so. When I run slmgr.vbs with any of the options, I get an error stating that I need to run the command with elevated privelleges. I cannot figure out to do this in the Hyper Core. I even tried the keyboard combe shift-ctrl-enter. no luck.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
slmgr.vbs –xpr

slmgr.vbs –dli

do the above command work?

Author

Commented:
no, I get the same error message access denied
Svet PaperovIT Manager

Commented:
On server core use cscript C:\windows\system32\slmgr.vbs -rearm to rearm or cscript C:\windows\system32\slmgr.vbs -ato to activate the server
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
try

slmgr.vbs servername administratorname  password -dli

Author

Commented:
ok, same thing. access denied elevated permissions are required

Author

Commented:
ok - I tried running that command and now I get "an error occurred connecting to servername"
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
firewall on? can it resolve servername?

Author

Commented:
i think the firewall is on. Yes, it can resolve. I ping servername and got a response
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
disable firewall.

Author

Commented:
the firewall is disabled and I still get the same error that it cannot connect.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
drop machine name, as it should connect to default machine?

Author

Commented:
no luck. I didn't add a server name and it gave me error invalid set of characters. I used the word default and got the same thing, could not connect, same thing when I use the IP address.

It is driving me crazy!

BTW, I really appreciate your help and I hope you can help me find a solution.
Svet PaperovIT Manager

Commented:
Hi there back,

By default, a command prompt on computers that are running the Server Core installation option of Windows Server 2008 R2 already runs with elevated user rights. You do not have to start the command prompt with elevated user rights in the Server Core environment. from http://technet.microsoft.com/en-us/library/dd379545%28WS.10%29.aspx

Does your user account have local administrative writes?

slmgr.vbs servername administratorname password –xxx command is for remote excedution, so it needs some other services as WinRM to be running and some modifications of the firewall like netsh advfirewall firewall set rule group="Remote Administration" new enable=yes

Here some links that could help with understanding license management on server core

http://technet.microsoft.com/en-us/library/ff793433.aspx

http://technet.microsoft.com/en-us/library/ee441257%28WS.10%29.aspx

What did you get from slmgr.vbs –dlv?
Svet PaperovIT Manager

Commented:
...meant administrative rights not administrative writes... sorry typing mistake
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
@spa... if you check back through he gets access denied with any options
Svet PaperovIT Manager

Commented:
@hanccocka... Yes, I’ve checked them but I didn’t quite understand why he got access denied.
On full Windows server, not a core, you don’t need an elevated command prompt to run slmgr.vbs -dlv. You need, however, an elevated command prompt to run slmgr.vbs -rearm even if you are an administrator.

Also, according to the link above, command prompt on server core already runs with elevated user rights.

So, my guess is that the user account doesn’t have administrative rights.

Sorry, don’t have a lot of experience with server core, just trying to help…

Bty, the fact that the OS already runs for 180-days it means that it has been activated as an evaluation copy. I am not sure that rearm option will work.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
@spaperov:

What is odd is this error

"access denied elevated permissions are required"

I've seen this when you cannot REARM! (because people we doing this alot to rearm Vista and Windows 7 alot!)

Author

Commented:
I appreciate all of the comments. I am not sure what is going on. I am assuming that it needs to be reactivated or rearmed.

I have tried loggin in as local admin as well as domain admin with the same results. We have never rearmed this server, I am only assuming that the OS installed is an evaluation version, but I have not idea. I didn't even know that there was and evaluation verison before my posting today.

I am getting the error on the bottom right that the software is not genuine and getting errors in the event viewer about the windows activation token.

I am also assuming that this is the reason why the virtual machines are not starting.

What else can I do to get this server activated?  if I boot with a Hyper V dvd, is there a repair option?

Author

Commented:
ok,

so I try connectin from another machine to the server core and ran the some option, -sli, svi, ato and now it said it was connected to the server. I click ok, and then I get a permission denied error.

Line: 2007
Char: 5
Error:Permission Denied
Code: 800A0046
Microsoft VBScript Error
kevinhsiehNetwork Engineer

Commented:
Sounds like this might be Windows 2008 Core with the Hyper-V role. What OS is listed for the host in Active Directory Users and Computers? It might be best to export the VMs and reload the host with Hyper-V Server 2008 R2 SP1 with the hotfixes, and them import the VMs back.

Author

Commented:
All,

To resolve this problem and get my file sever back up and running, I had to move the VHD's to an external drive. I built a temporary Hyper V host and created a temporary VM. I then pointed the VM to the VHD on the external HD. At this point, I was up and running.

I had to reload WIndows Server Hyper V using the actual free version and not the evaluation. I am in the process of  copying the VHD back to the main server. I will then create a new VM and point it to the VHD that I copied back.

I will update once it is done copying over to the main server
Svet PaperovIT Manager
Commented:
I hope you will not make the same error again. Please, see the difference
- Windows Server 2008 R2 Core edition (that includes Hyper-V) is not a free one and you can install it as a trial for up to 240-days (initial 10-days + 5x 10-days rearm + 180-days evaluation): http://www.microsoft.com/en-us/server-cloud/windows-server/hyper-v.aspx
- Microsoft Hyper-V Server 2008 R2 is a free product: http://www.microsoft.com/en-us/server-cloud/hyper-v-server/default.aspx 

Author

Commented:
Thank youto both of you for your assistance. I have learned a great lesson from this process.