Hyper V - Server core-completely stuck without a clue!

[Snookered]

A user told me earlier today that they were unable to use remoteapps to run a program, when attempting they are getting a licence error.

Looking online I think I've found the solution, just delete a "period of grace" registry setting on the effected server and reboot it.

Problem I have is when I try and remote into that VM server I too get the same licence error.

Next problem is where I am stuck, having gone to the physical server and logged on, I see a Server 2012 core command line screen and I can go no further.

How do I get back to either logging on to the correct virtual server or server manager?

I can logon ok to another vm that does have a GUI, can that help me?

 

Many thanks!

[SHimmer45]

if its a reg setting on the core server,

you could start the remoteregistry service and then connect to it and modify the entry using regedit from a pc with a GUI

[Snookered]

if its a reg setting on the core server,

 

Unfortunately it's not on the core server, it's on the normal 2012 virtual server that I can't get remote access to because of the licence issue

[caffrey]

*edit*

 

I think you can just use regedit.exe on core , sorry just read you response

Edited December 3, 2014 by caffrey

[SHimmer45]

ok assuming that the networking is ok on the machine you need to modify you can connect to the registry remotely using regedit assuming the service is started on the remote server.

 

iirc regedit does work on core, but you can make the change on any pc that can connect to the server with the problem. (from your message when you attempt to RDP to the server guest not the hyper-v host it just kicks you out)

Edited December 3, 2014 by SHimmer45

[tmcd35]

If you run Hyper-V Manager on your workstation and connect that to your host server, can you not open a local session to the VM from there? (double click on the VM in Hyper-V Manager)

 

Have you tried RDP'ing to the effected server in console mode? (mstsc /admin)

 

Other than the two licenses for administrating the server through RDP, all other terminal services use, including remote apps, should be licensed appropriately. Surely the solution is to buy the correct licences and not deleting registry keys?

Edited December 3, 2014 by tmcd35

[Snookered]

Other than the two licenses for administrating the server through RDP, all other terminal services use, including remote apps, should be licensed appropriately. Surely the solution is to buy the correct licences and not deleting registry keys?

 

This is a good point, however I'm hoping that when we purchased the licences from a Microsoft verified licence provider the appropriate licences were included in the cost for the year, which still has a number of months to go.

I can't find any detail about this issue on any MS sites, but got the info about deleting the registry setting from this site Server 2012 RDS: No Remote Desktop License Servers Available as well as seeing numerous other references about it including a mention of a KB from Microsoft, but that page would not load for some reason.

[Snookered]

Resolved it by gaining access to Hyper V Manager via one of the other VM Servers and then connecting to the effected server, deleted the registry setting, restarted the server and both I and the other user can reach it okay.

So thanks to everyone for the help.....now to check our licensing is correct.