administering hyper-v core (urgent)

[autumn]

g day all

I have an issue with a client I've recently gained. they have a basic server with hyper-v core 2008 and a VM with 2011 SBS. The core is set up connected to the domain which is in the VM. I don't have an local admin account details as the previous techs weren't that forthcoming with information. Now the core has restarted and the VM won't start automatically (has before with shut downs/restarts). On the console I get "server configuration" with 1 to 15 options, now saying this I haven't setup or administered a core server before so not sure if this is normal or not.

I've read the that I need to use MMC for another computer which I can connect to but if I try and do anything I get the error "A security package specific error occurred(1825)". I'm thinking that because the DC isn't running it's not authenticating, with being logged in on the workstation as an administrator on the domain.

What can I do?

so at the moment I have the core running but can't get the SBS running as I can't get MMC to authenticate.

Thanks in advance

Tim

 

[SAG]

This is one of those times where I'd use an offline NT password reset disk and blank the local Administrator account and go from there.
Some people would disagree with me, but it'd kill several birds with one stone and then I could set the local admin to what I wanted it to be.

From there......

 

[cyabro]

So you can log into the hyperv core ok then if you're getting the server config options?
If so you could download the free version of the 5nine hyperv manager and install that on the core. That'll give you basically the same GUI as Microsoft's hyperv manager in windows.

 

[YeOldeStonecat]

This is one of those times where I'd use an offline NT password reset disk and blank the local Administrator account and go from there.
Some people would disagree with me, but it'd kill several birds with one stone and then I could set the local admin to what I wanted it to be.

From there......

That would be my second thing to try. First...I'd call up the prior support people. I know sometimes people feel like "the prior IT guy is the enemy and he won't help me"...but really...I've never had a problem with this, with the people I replace giving me the info I need.

If that guy got run over by a bus, and you can't get the info...then yes...local admin account password reset.

That's the main reason I don't like a local hypervisor host relying on logging into a guest.....because if the guest isn't running...sometimes that local cached credential thing don't always work...and you're stuck like this. Not a good thing when you're troubleshooting a major issue and you can't even get in to manage the local host..not to mention get the guest going.

 

[autumn]

I can get in to the core and get to the command line and powershell in the core but the commands aren't gin=ving me the info either. like get-VM this comes back as basically an unrecognised command.

I am thinking of taking the sbs out of a VM and putting it on the bare metal. but of course I need to get in to the VM first.

 

[Nerm]

I always use the RSAT for situations like this. If you have local login credentials you can manage hyper-v, etc remotely with those tools from a Windows 7 box.

 

[autumn]

OK I've used the 5nine hyperv manager on the workstation to connect to the core machine and it allows me to manage the VM so this is a good start. the bad start is the reason why the VM won't start. it's saying there isn't enough space on the drive to run so looks like a corruption on disk. And no real backup.

 

[krtechsolutions]

Sounds like you not going to have a good night there.

Once you get the server up and running you should remove the Hyper-V from the domain and keep it local only. Also being they have SBS2011 there is no reason to be running core, but each to their own.

 

[autumn]

all up and running again. It was a long day and short night. the drive wasn't corrupt just on of space. threw in another drive and transfer the vm to it and all good.

Yes that's what I'm thinking is to remove the core and run the sbs on the bare metal. will have to convince the owner that will be better. Just a side note/question with sbs on the bare metal what difference in performance would there be? The only other thing with moving it to the bare metal is the licensing won't be legal as they have sbs from the server standard license to run in the VM.

Thanks all

Tim

 

[YeOldeStonecat]

If it's the only guest, there won't be much change in performance.
To boost performance with SBS, assuming they're using Exchange and using data shares heavily and redirected folders, you want SBS to be installed on at least 2x volumes...2x separate volumes. Pagefile on each too. Infostore on the second volume.

See lots of setups with SBS just on a single drive letter....or....it may have 2x drive letters (partitions)...but both partitions are installed on the same RAID volume ...which doesn't gain you performance.

One thing about virtualizing servers....you gain flexibility in moving it across different hardware, and increase your options (and speed) of disaster recovery.

Was snapshots left on..thus consuming space?