Skip to main content

CitrixTools Blog

Go Search
Home
Blog
BG
  

CitrixTools Home > CitrixTools Blog
Windows 2008 Hyper-V RC0 on a HP Proliant Server
Microsoft and HP have worked on a fix for those of us that have had issues installing Hyper-V RC0 on a HP Proliant Server that has Proliant Support Pack 8.0 installed... or at least they have found a "work around".
 
 
Basically install the PSP after Hyper-V role and Hyper-V RC0 have been installed.
 
If you are stuck in the Configuring Updates 54% endless loop follow this Microsoft Knowledge Base Article:
to rename the HP Network Configuration Utility cpqteam.dll file.
Setup HP DL360 G5 with Windows 2008 and Hyper-V
This is my check list for getting Windows 2008 with Hyper-V running on a HP DL360 G5 the manual way. I will provide more automated methods at a later data.  I had to install in this order because Hyper-V update was hanging if the PSP (Proliant Support Pack) was installed.

 

Integrate Hardware

Update firmware using latest HP Firmware CD

Change BIOS to enable Processor settings

                Advanced Options

                                Processor Options

                                                Intel ® Virtualization Technology – enabled

                                                No-Execute Memory Protection – enabled

Disable PXE on onboard NIC’s

 

 Install 2008 – boot from DVD, choose Standard

Set Time Zone and Time

Configure Networking  (dhcp can be used temporarily)

Install Hyper-V Role

                Do not select your production NIC, use second NIC for VM's

Download and install Hyper-V Update (KB949219)

http://www.microsoft.com/downloads/details.aspx?FamilyID=DDD94DDA-9D31-4E6D-88A0-1939DE3E9898&displaylang=en

 

Add SNMP to “Roles” / “Features”

Install PSP for x64 Windows 2008

Turn “Off” Firewall (lazy man's way)

Turn “Off” UAC (User Access Control) 

Terminal Server Driver Redirection details
Terminal Server Printer Redirection Wizard Tool

 

The following registry keys must be created on the Terminal Server:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Wds\rdpwd

Name: PrinterMappingINFName
Type: REG_SZ
Data: Name of the .inf file to which you want to redirect lookups.
Example: c:\winnt\inf\ntprintsubs.inf

Name: PrinterMappingINFSection

Type: REG_SZ
Data: Name of the section in the .inf file to which you want to redirect lookups.
Example: Printers

The following is the format of the user defined inf file:

---------------------------------------------------------------------------------------

[Version]
Signature="$CHICAGO$"

[Printers]
"OEM Printer Driver Name" = "Windows 2000 Printer Driver Name"

---------------------------------------------------------------------------------------

Example:

“HP LaserJet 4200 Series” = “HP LaserJet 4 Plus”

PS4.5 Configuring XML to share with IIS
So, you have a Presentation Server 4.0 / 4.5 server running on Windows 2003, the XML port is 80, and you need to also make it a Web Interface server. You need to install IIS, then run aspnet_regiis.exe -i to register the .NET Framework with IIS.
Then follow Citrix Article CTX107683 (http://support.citrix.com/article/CTX107683)
 
 
 
Here is CTX107683:
 

Configuring the XML Service to Share with IIS

Document ID: CTX107683   /   Created On: Sep 26, 2005   /   Updated On: May 1, 2007
Average Rating: 4

Summary

When installing IIS 6.0, the virtual Scripts Folder is not created by default. This document describes how to configure the XML Service to share the port with IIS on Windows 2003.

For other platforms and / or operating systems, refer to CTX104063 – Explaining and Changing the Citrix XML Service Port .

Procedure

1. Unregister the service using the ctxxmlss /u command.

2. Navigate to the \Inetpub folder and create a new folder named Scripts.

3. Open the IIS Manager MMC Snap-in.

4. Right-click Default Web Site and select New > Virtual Directory…

5. Click Next.

6. Under Alias:, type Scripts and click Next.

7. Under Path:, type Drive Letter:\Inetpub\Scripts and click Next.

8. Under Allow the following permissions:, make sure that the following is selected:

    • Read

    • Run Scripts (such as ASP)

    • Execute (such as ISAPI applications or CGI)

9. Click Next and click Finish.

10. Right-click the Scripts virtual directory and go to Properties.

11. Under the Virtual Directory tab, make sure that the Execute Permissions: field is set to Scripts and Executables.

12. Under the Directory Security tab > Authentication and Access Control, click on Edit… and make sure that the Enable anonymous access check box is selected.

13. Copy the following files from the \Program Files\Citrix\System32 folder to the \Inetpub\Scripts folder:

    • ctxxmlss.txt

    • wpnbr.dll

    • ctxconfproxy.dll

    • ctxsta.dll

    • ctxsta.config

14. Locate the ctxadmin.dll file and copy it to a folder called ctxadmin under \Inetpub\Scripts.

15. Create a folder called Resource in \Inetpub\Scripts . Inside this folder create a new folder called en. Locate the ctxstaui.dll file in \Program Files\Citrix\System32\Resource\en and copy it to the folder created above.

16. In IIS Admin right-click Web Service Extensions, select Add a new web service extension. Type the name Citrix XML ISAPI in the Extension name field and click Add. In the Add File popup window, type in or browse to the location of the wpnbr.dll file. Then finish by selecting the Set the extension status to allowed box.

17. In IIS Admin, right-click Web Service Extensions, select Add a new web service extension. Type the name Citrix XML Administration ISAPI in the Extension name field and click Add. In the Add File popup window, type in or browse to the location of the ctxadmin.dll file. Then finish by selecting the Set the extension status to allowed check box.

18. In IIS Admin, right-click Web Service Extensions, select Add a new web service extension. Type the name Citrix ConfProxy ISAPI in the Extension name field and click Add. In the Add File popup window, type in or browse to the location of the ctxconfproxy.dll file. Then finish by selecting the Set the extension status to allowed check box.

19. In IIS Admin, right-click Web Service Extensions, select Add a new web service extension. Type the name Citrix STA ISAPI in the Extension name field and click Add. In the Add File popup window, type in or browse to the location of the ctxsta.dll file. Then finish by selecting the Set the extension status to allowed check box.

20. In IIS Admin, create a new Application Pool called CtxScriptsPool – go to Properties > Identity tab and set this pool to run as the Local System account. Leave the other settings as default. Click Ok.

21. Right-click the Scripts Virtual Directory. On the Virtual Directory tab, set the Application Pool to be the CtxScriptsPool. Apply the Changes.

22. Restart the Independent Management Architecture (IMA) Service.


This document applies to:

  • Presentation Server 4.0 for Microsoft Windows 2003
  • Citrix Presentation Server 4.5 for Windows Server 2003
More Virtualization coming
Getting ready to start building a Microsoft Virtualization Environment that will initially have 7 hosts, this will be using Microsoft's Virtual Server running on Windows 2003 R2 64-bit and be managed with Microsoft Virtual Machine Manager. Yeah, I would rather just start with Windows 2008 but since it was just released this week, we will wait for HyperVisor to be released.
 
Anyway, I hope to learn much during this process and will be posting all that I can in the near future.
 
Stay Tuned!
 
RG
Expanding the System / Boot Partition of a Virtual Server

Assumptions:

You are utilizing Microsoft Virtual Server 2005 SP2

You have a second Virtual Server in which you can mount the .vhd file from the server in question

Scenario:

You have a Windows 2003 server running as a virtual machine, your system / boot partition has reached it’s capacity. You need to expand the system / boot partition.

 

Solution:

Download VHD Resizer from http://vmtoolkit.com/

Shutdown the server in question and your second virtual server

Make a backup of your production .vhd file(s)

Using VHD Resizer add the necessary space to your .vhd

Mount your .vhd into your second Virtual Server so it can see the hard drive

Turn on and login to your second Virtual Server, verify you can see the second disk you mounted, I will assume this is “Disk 1”

 

From a cmd prompt launch diskpart (or from the Run command launch diskpart.exe)

 

***The following are the commands to use with diskpart***

 

List disk

Select disk=1

Detail disk

Select volume=2

Extend

Exit

 

Shutdown you’re second Virtual Server

Unmount the server in question’s .vhd file from your second Virtual Server

 

Ensure your server in question’s .vhd file is correctly mounted to it

Turn on the server in question, you will now have an extended system / boot partition

Active Directory external SNTP settings
Registry key's used on your root domain PDC Emulator to synchronize it's time with an external source, using SNTP servers located in PA and NY.
 
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config]
"AnnounceFlags"=dword:00000005
"MaxNegPhaseCorrection"=dword:00000e10
"MaxPosPhaseCorrection"=dword:00000e10
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters]
"NtpServer"="clock.psu.edu,0x1 timex.cs.columbia.edu,0x1 ntp-1.ece.cmu.edu,0x1 ntp-2.ece.cmu.edu,0x1"
"Type"="NTP"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer]
"Enabled"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient]
"SpecialPollInterval"=dword:00000384
 
 
 
The SNTP Servers I like to use:
University Park, PA: Penn State University
128.118.25.3: clock.psu.edu
Service Area: Internet2, vBNS, CERFnet(AT&T IP Services), PSC/NCNE, and CASC

Pittsburgh, PA: Carnegie Mellon Electrical and Computer Engineering
ntp-1.ece.cmu.edu; ntp-2.ece.cmu.edu
Service Area: PREPNET and PSC region
New York City, NY: Columbia University Computer Science Department
timex.cs.columbia.edu
Service Area: PSINET; NSFNET, and NYSER region
DCPROMO "The wait operation timed out"
When attempting to dcpromo a Windows 2003 domain controller from being a domain controller to a member server you receive the error message "The wait operation timed out".
 
Modify the TCP/IP properties of the server so that it is pointing to another DNS server other than itself, the dcpromo should now finish without error.
1 - 10 Next

 ‭(Hidden)‬ Admin Links