I believe in Hyper-V!

SCVMMCategory Archives

The security database on the server does not have a computer account for this workstation trust relationship

Before few days ago I returned snapshot/checkpoint with scvmm and turned on virtual machine, but when I tried to logon with domain user I gave this message, „The security database on the server does not have a computer account for this workstation trust relationship“. I need to mention that snapshot/checkpoint was old only three hours.

image

I logged in with local Administrator account and removed server from the domain and again join to the domain. After restart I logged in with domain account but few services didn’t start. I again restarted server, tried to logon and I gave the same message „The security database on the server does not have a computer account for this workstation trust relationship“.

Solution/Workaround:

You need to do two things.

1. Reapply values in ADSI Edit (adsiedit.msc) or enter new if SPN missing.

    Open adsiedit.msc like on picture below and check settings in servicePrincipalName

image

2. Restart the computer.

3. Login on to your server with local Administrator account.

4. Change domain from FQDN to the short name. In my case ekobit.corp change to ekobit_corp

5. Restart your server and Login as the domain user.

Relax your mind and enjoy Smile.

NOTE: As you might know Winlogon service on Windows 7, Windows Server 2008 and Windows Server 2008 R2 Operating Systems use Kerberos logon. So the Service Principal Names (SPNs) need to be configured properly to support Kerberos Authentication.

Other Reference Articles:

Kerberos Authentication Problems: http://blogs.technet.com/b/askds/archive/2008/05/29/kerberos-authentication-problems-service-principal-name-spn-issues-part-1.aspx

Symptoms when secure channel is broken: http://blogs.technet.com/b/asiasupp/archive/2007/01/18/typical-symptoms-when-secure-channel-is-broken.aspx

Machine Account Password Process: http://blogs.technet.com/b/askds/archive/2009/02/15/test2.aspx

System Center Virtual Machine Manager 2012 RC – Installation

In this post I will explain how to install System Center Virtual Machine Manager 2012 RC from the scratch.

My recommendation; install System Center Virtual Machine Manager on physical server, not on Virtual machine.

First off all you need to create new domain account for SCVMM installation. With that account you need to install all required components for SCVMM, also you need to add that account in Default Domain Policy (GPO) to “Log on as a service” and add to a Local Administrator group in your System Center Virtual Machine Manager server.
Also you need to add your SCVMM server to a Local Administrator Group.

1

1-2

 1-2-3

When you are done with your SCVMM account continue with other requirements. If you use SCVMM server for other VM’s you need to install Hyper-V role.

2

After Hyper-V role is installed continue with SQL Server 2008 R2 installation.

3
4
5

SQL Server 2008 R2 is installed. Now we need to install Web Server (IIS) role.

6
7

8

After Web Server (IIS) role is installed continue with WAIK.

9
10
11
12

OK. We are ready to install our System Center Virtual Machine Manager 2012 RC.

Just follow procedure on pictures below.

13
14
15
16
17
18
19
20
21

If you are going to use Self Service Portal enter adequate parameters.

22

For the Library I’m using storage on same server.

23

At the end we see Installation summary. Check your configuration and click Install.

24
25

Setup completed successfully, but with three warnings.

26

Click Close and don’t open VMM Console, first you need to fix warnings. Logon to SCVMM server like domain admin and open command prompt as administrator. Run command like on picture below.

27-2

If you run command like local VMM admin you will get this error.

27

The second thing you need to do is to enter SCVMM server name in the registry like on picture below.

28

The last but not the least Smile enter this command in cmd.

29

And open you VMM Console.

30

Folks, that’s it.

Hyper-V Server 2008 R2 vs. Hyper-V Role on Windows Server 2008 R2

One of the most common misconceptions in the realm of Microsoft Virtualization products is the difference between the Hyper-V role and Hyper-V Server 2008 R2.
One of the biggest sources of confusion when dealing with Microsoft virtualization technologies is mistaking they Hyper-V role for the same thing as Hyper-V Server 2008 R2.

So what is the difference?
Microsoft Hyper-V Server 2008 R2 is actually a free stripped down version of the Windows Server 2008 operating system designed to be a simplified virtualization solution for consolidating servers, development, and testing environments.

The Hyper-V role is a feature of the Standard, Enterprise and Datacenter edition of Windows Server 2008 R2 that allows for a much more robust virtualization experience. When using the Hyper-V role with Windows Server 2008 R2 Standard, Enterprise, or Datacenter you gain several additional features including a local GUI, high availability (clustering) services, support for large amounts of memory, support for a large amount of processors, and the ability to add additional server roles. Along with this, these versions of Windows Server 2008 R2 include licensing for additional virtual machines which help to decrease cost when deploying new operating systems.