Installing Hyper-V 2008 R2 SP1 on IBM X346 with ADAPTEC SCSI u320 controller

It could be pretty tricky to install Hyper-V 2008 R2 SP1 on IBM x346 with Adaptec controller. If didn’t want to throw away my old server so I decided to install Hyper-V on it to create testing environment.

I do this with colleague of mine, and we faced with problem. Hyper-V wont install on IBM x346. Why? Server asked for driver….

I think that driver is so old that Hyper-V don’t have it in its drivers database, and You can’t install it using ServerGuide CD.

What were we do.

After spending hours trying to install Hyper-V on IBM x346 with Adaptec u320 SCSI controller, finally we have solution.

My colleague Luka Gros spend finds x64 driver for Adaptec SCSI controller. He found it on this link.

After downloading, you must extract this driver and burn it on CD

Steps what we are do after that is:

booting from Hyper-V 2008 R2 SP1 and starting installation

when asked for driver change CD to one with driver and click Browse

find driver on CD and click Next

change CD to installation CD again and finish your installation

Hyper-V is installed and running fine now

Smiješak

P.S.

If You need to manipulate with physical HDD on your Hyper-V, MMC console will return error “RPC server unavailable”.

To avoid this run this command with elevated privileges:

netsh advfirewall firewall set rule group=”Remote Volume Management” new enable=yes

Thanks to Luka Gros

Managed Service Accounts in Active Directory

We all heard that one of many features in Windows server 2008 R2 is Managed Service Account.

Prerequisites for that is domain functionality raised to Windows Server 2008 R2

Most common mistake is that you will create managed service account using Active Directory Users And Computers snap-in. You will not.

Either if you are created account in Managed Service Accounts container it is still user account. To make it work you must give user rights “logon as a service” and “logon as a bat job”.

To create Managed Service Account you must use Power Shell. Creating service accounts is not so complicated. You can create it using simple script

New-ADServiceAccount –name (desired name of account).

Of course before you must “tell” powershell to use Active Directory module. Syntax for this is:

Import-module ActiveDirectory

And before that you must have installed feature:

Active Directory module for Power Shell

image

I’ve described this reversed with reason.

Most common is that you first load module to Power Shell and then start wit Your managed service accounts.

When you are created service account you need to install it on server where You want to use it. Syntax is:

install-ADServiceAccount –identity “(name of service account)”

To install account you must “run as administrator” Power Shell or you will receive error.

image

REMEMBER: You must have ONE managed service account per server. This is the big difference between managed service account and former virtual account.

Now you are ready to use managed service account with specific services

image

image

 

 

For more on this topic you can contact this link