Archive for the ‘SCVMM 2012’ Category

SCVMM 2012 error – You cannot access Virtual Machine Manager server localhost. Ensure that your account is a member of a valid user role, and then try the operation again. ID: 1604

April 27, 2012

When opening the SCVMM Console and trying to logon to it, i got the following error:

You cannot access Virtual Machine Manager server localhost.

Ensure that your account is a member of a valid user role, and then try the operation again.

ID: 1604

Weird. Last time i ran it it worked fine.

Into the Eventlogs of the SCVMM server then. There i found this entry:

“Unable to connect to the VMM database because of a general database failure.
Ensure that the SQL Server is running and configured correctly, then try the operation again.”

Event ID 2605, Virtual Machine Manager

So, no connection to the SQL Server that holds the database? Onto the SQL Server then. There, in the Eventlog was this error:

Login failed for user ‘CONTOSO\sa_scvmm’. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <ip-address of scvvm server>]


Hey, that’s weird. After some googling, this error turns up related to UAC (User Account Control) issues on servers.

So i right-clicked the SCVMM Console and ran it with “Run as Administrator”.

And behold, it worked!

Wait, wut? Does that mean i have to start the SCVMM Console as Administrator every time from now on?

So i closed the console, and re-opened it, now without “Run as Administrator”.

Still worked fine. Hmmkay…. Some weird one-time error?


Server App-V 2012 – A First look (really)

April 23, 2012

So, after trying to install the Server App-V sequencing client on Windows Server 2012 Beta (and failing), I switched back to good ol’ Windows Server 2008 R2 SP1 as the testclient.

At least now i’m following the Software Requirements for installing Server App-V

I mounted the DVD/ISO of SCVMM 2012, browsed to the folder SAV\AMD64, and ran SeqSetup.exe, and behold:

And off we go!

Just another EULA to quickly skip through? Well, just note that this product is a part of SCVMM 2012, so no separate licensing for App-V here.


I’m installing this on a clean Windows Server 2008 R2 SP1 VM, and it appears it needs these two Visual C++ packages. Good thing they’re packed into the App-V installer 🙂

And we’re done. Now that was easy. Let’s see what we’ve got now:

The App-V Sequencer  Client installed in Program Files (x86)… hey, didn’t I choose the x64 installer of the client? Oh well…

Another thing, notice the Q:\ drive? If you’re already familiar with the current (client) App-V you’ll not be surprised to see this Q; mapping.

Well actually it’s a redirection to the local C:\ drive, as you can see in this picture:

So, client installed, no reboot asked… let’s start packaging then!

Well, in the next posting that is.




Server App-V 2012 – a (very short) testdrive on Server 2012 Beta.

April 23, 2012

With the System Center 2012 “Cloud-based” approach, focusing on easily deploying multiple VM’s (both Servers and Workstations), a new feature has been added that makes it even easier to get an ApplicationServer quickly up-and-running.
Server Application Virtualization, or Server App-V , or SAV.
The latter not to be confused with Symantec Anti Virus 🙂
So in my testlab based on Server 2012 Beta, Hyper-V, and System Center 2012 SP1 CTP, I was ready to go and build me some packages.
First, we have to install the App-V Sequencing Agent on a clean server, to start packaging.
Of course, I did this on a freshly deployed Windows Server 2012 Beta VM.
Only to get this message:

Okay, I know that the prereqs page states that only Windows Server 2003, 2008, 2008 R2 are supported, but I was hoping that this was outdated, with the CTP of SP1 for SC2012.
So, no dice.
Ah well, lets fire up a good ol’ Server 2008 R2 VM then. :p

What is NOT supported in the SCVMM 2012 SP1 CTP version?

April 16, 2012

After reading this 65-page documentation for the CTP of SP1 for SC2012 i was a little disappointed.

A lot of things are not supported in this release, amongst them:
– installing the VMM Selfservice Portal
Yep. I tried it, but got a LOT of funky errors. Mainly to do with IIS not liking some multiple configuration settings in the web.config.

VMM user roles, anything except the Administrator role is not supported

Perimeter network based hosts. All computers must be in the same AD.

Hmm, but this seemed to work quite well. Just remember that when you install the VMM agent software on the Hyper-V host, you should choose for the SCVMM server to contact the Hyper-V host BY NAME, and not by IP Address. Otherwise you’ll get nasty certificate based errors when you want to connect to a VM on it.

Apparantly the choice for hostname- or ip based connection is written to the Securityfile.txt which is then used to import the host into SCVMM.

When you select IP based, the certificate used to connect to the console of the VM won’t match with the issuer. Bummer. When re-installing the SCVMM agent and choosing the hostname option, all works fine.

– ALL servers, need to run Windows Server 8 Beta.

All? Well, the hyper-v host, the guest VMs, the vmm library server, the vmm management server, even the VMM console must run on it. Only exception is the vmm database server, this can be a 2008 r2 server.  No, Windows 8 Consumer Preview is also not supported.

Well, this makes this CTP really a ” Windows Server 8- only”  release.

To be continued.. 🙂