Microsoft Project Server, SharePoint, Security and other cool things…

Rolly Perreaux

   LinkedIn - MVP-Press Networking Group   @RollyPerreaux   RSS Feed    

 

How to Install Microsoft Virtual Server 2005 R2 with SP1 on Windows 7 (Graphical Step-by-Step)

Posted on August 10, 2009 by - 5,074 views
facebooktwittergoogle_plusredditpinterestlinkedin

I use Virtual Server a lot in teaching and in my Project Server consulting practice. After upgrading to Windows 7 over the weekend, I come to install Virtual Server 2005 R2 with SP1. It installs with no problem, but when I go to open the Virtual Server Administration Website and I receive the following error:

Error1

 

I then go to check the Services console and sure enough the Virtual Server service is not running:

Error2

 

So I decided to to try starting up the service and it was a No-Go.  smile_sad

Error3

 

Time to do some searching and I found this great post on the Microsoft TechNet Windows 7 forum:
http://social.technet.microsoft.com/Forums/en-US/w7itprovirt/thread/a98e77b7-95d4-444f-8dbc-630c98074436

So not missing another teaching opportunity I decided to take Robip’s post an transpose it into a graphical Step-by-Step procedure. Here it is:

 

Step 1 – Install IIS on Windows 7

1. From the Control Panel, click Programs and Features

Step1

 

2. In the navigation bar, click Turn Windows features on or off.

Step2

 

3. In the Turn Windows features on or off window, select the following settings:

Step3 

 

Step 2 – Disable Program Compatibility Assistant & Application Compatibility Diagnostics (Temporarily)

By default the Program Compatibility Assistant is enabled and always blocks the vssrvc.exe (Virtual Server service) in Virtual Server 2003 R2. In this step we temporarily disable Program Compatibility Assistant & Application Compatibility Diagnostics settings in the Local Group Policy.

1. Click on the Start button and in the Search programs and files box, type Edit Group Policy and press Enter.

Step4

 

2. In the Local Group Policy Editor console, navigate to Computer Configuration –> Administrative Templates –> Windows Components –> Application Compatibility and change the state to Enable for the following highlighted settings:

Step5

 

Settings Information for Application Compatibility Policy:

Application  Telemetry
Mechanism that tracks anonymous usage of specific Windows system components by applications

Application Compatibility Engine
Part of the Loader and looks through a compatibility database every time an application is started on the system. If a match for the application is found, it provides either run-time solutions or compatibility fixes, or displays an Application help message if the application has a know problem.

Program Compatibility Assistant (PCA)
Monitors user initiated programs for known compatibility issues at run time. Whenever a potential issue with an application is detected, the PCA will prompt the user with pointers to recommended solutions.

Program Inventory (PDU)
Inventories programs and files on the system and sends information about these files to Microsoft. This information is used to help associate file to programs and diagnose application compatibility problems.

SwitchBack Compatibility Engine
Mechanism that provides generic compatibility mitigations to older applications by providing older behavior to old applications and new behavior to new applications.

Problem Steps Recorder
Enables capturing the steps taken by the user before encountering a problem.

3. Then navigate to Computer Configuration –> Administrative Templates –> System –> Troubleshooting and Diagnostics –> Application Compatibility Diagnostics and change the state toDisable for the following highlighted settings:

Step6

 

Settings Information for Application Compatibility Diagnostics Policy:

Notify blocked drivers
Determines whether the Program Compatibility Assistant (PCA) will diagnose drivers blocked due to compatibility issues.

Detect application failures caused by deprecated COM objects
Determines whether the Program Compatibility Assistant (PCA) will diagnose DLL load or COM object creation failures in programs.

Detect application failures caused by deprecated Windows DLLs
Determines whether the Program Compatibility Assistant (PCA) will diagnose DLL load failures in programs.

Detect application install failures
Configures the Program Compatibility Assistant (PCA) to diagnose failures with application installations.

Detect application installers that need to be run as administrator
Determines whether the Program Compatibility Assistant (PCA) will diagnose failures with application installers that are not detected to run as administrator.

Detect application unable to launch installers under UAC
Configures the Program Compatibility Assistant (PCA) to diagnose failures with programs under User Account Control (UAC).

4. Close the Local Group Policy Editor console and restart your computer.

Step 3 – Install and Test Microsoft Virtual Server 2005 R2 SP1

1. Download and install the latest version of Microsoft Virtual Server 2005 R2 SP1

http://technet.microsoft.com/en-us/evalcenter/bb738033.aspx

 Step7

 

2. Click on the Start button –> All Programs –> Microsoft Virtual Server and click Virtual Server Administration Website.

3. If you receive a Windows Security popup window, enter your credentials and click OK.
   More information on how to stop this popup later…

4. At this point you should be viewing the Virtual Server Master Status page, similar to the following:

Step8

 

Step 4 – To Stop the Windows Security Popup Window (Optional)

This step assumes that your user account is a member of the Local Administrators group on your computer.

1. At the bottom of Internet Explorer, double click on Internet.

Step12

 

2. In the Internet Security Properties dialog box, click Local Intranet and click Sites.

Step9

 

3. In the Local intranet dialog box, click Advanced.

Step10

 

4. In the Local intranet dialog box, verify your Virtual Server’s URL is listed in the box and click Add and click Close.

Step11

 

5. Click OK twice and close all instances of Internet Explorer.

6. Open the Virtual Server Administration Website again.
    You should not see the Windows Security popup window.

7. Close Internet Explorer.

 

Step 5 – Restoring Program Compatibility Assistant & Application Compatibility Diagnostics Group Policy Settings

In this step you will restore the Group Policy settings that were changed in Step 2.

1. Click on the Start button and in the Search programs and files box, type Edit Group Policy and press Enter.

2. In the Local Group Policy Editor console, navigate to Computer Configuration –> Administrative Templates –> Windows Components –> Application Compatibility and change the state toNot Configured for the following settings:

  • Application  Telemetry
  • Application Compatibility Engine
  • Program Compatibility Assistant (PCA)
  • Program Inventory (PDU)
  • SwitchBack Compatibility Engine
  • Problem Steps Recorder

3. Then navigate to Computer Configuration –> Administrative Templates –> System –> Troubleshooting and Diagnostics –> Application Compatibility Diagnostics and change the state to Not Configured for the following settings:

  • Notify blocked drivers
  • Detect application failures caused by deprecated COM objects
  • Detect application failures caused by deprecated Windows DLLs
  • Detect application install failures
  • Detect application installers that need to be run as administrator
  • Detect application unable to launch installers under UAC

 

Step 6 – Renaming the Virtual Server service (vssrvc.exe) and Modifying the Registry

Now that the PCA is re-enabled, it will unfortunately block the Virtual Server service (vssrvc.exe) from running, so in this step you will rename the vssrvc.exe file and modify all registry settings from the vssrvc.exe file to the newly renamed file.

1. Open Windows Explorer, navigate to C:\Program Files\Microsoft Virtual Server and rename vssrvc.exe to vssrvc_win7.exe.

Step13

 

2. Close Windows Explorer.

3. Click on the Start button and in the Search programs and files box, type REGEDIT and press Enter.

4. In the Registry Editor console, click Edit and click Find.

5. In the Find dialog box, in the Find what box, type vssrvc.exe, select Keys, Values and Data check boxes and click Find Next.

Step14

 

6. At the first entry found, double click the value name and change the Value data to the reflect the new name (vssrvc_win7.exe) and click OK.

Step15

 

7. In the Registry Editor console, press the F3 key to continue the search and repeat task No. 6 until the search is complete.
   (I personally made 6 registry changes, but YMMV)

8. Close the Registry Editor console and restart your computer.

 

Step 7 – Verify the Virtual Server Service

In this step you will verify that the Virtual Server service is running and using the vssrvc_win7.exe file.

1. Click on the Start button and navigate to Control Panel –> Administrative Tools.

2. In the Administrative Tools window, double click Services.

3. In the Services console, double click Virtual Server.

4. In the Virtual Server Properties dialog box, verify the following:

  • The Path to executable should display the path to vssrvc_win7.exe
  • The Service status should display: Started

Step16

 

5. Close the Virtual Server Properties dialog box and the Services console.

6. Click on the Start button –> All Programs –> Microsoft Virtual Server and click Virtual Server Administration Website.

    You should see an entry that the Virtual Server successfully started.

Step17

Good Luck in your future Virtual Server endeavours on Windows 7 !

Comments are closed.




↑ Top