18 Mar 2008 05:44 PM EDT

posted by Pete Downing

Recently I have been working with the different teams here at Citrix implementing Provisioning Server in XenApp environments.  As we venture into this realm, we are finding remapping of drives is quite common in many 4.x, 3.x and XP implementations.  There are typically two scenarios I hear about:

  • Users are confused when they perform a "Saves As" in an ICA session and they do not see their "C" drive a "C" drive.  Remapping addresses this issue minimizing support calls I image.
  • Customers have spent a sizable amount of money creating application packages to work properly in a remapped environment.  To undo this would be another sizable amount of money so customers are not quick to revert. 

As Provisioning Server was introduced into the picture, people have asked... "What about the remapped drives?" Below is the explanation on how to ensure the remapping is seen when streaming a XenApp (Presentation) Server with Provisioning Server.

Below is the process to make a XenApp (Presentation) Server operable when streamed by a Provisioning Server with remapped drives are part of the baseline.

I will have a follow-on article discussing two partition scenarios coming soon!

As always, I am a huge fan of feedback, so please leave comments.

Summary

When using a Provisioning Server to stream a XenApp (Presentation) Server that has a remapped drive, Provisioning Server does not always boot with the proper drive letter therefore making the streamed target device inoperable. This article will provide the "How To" on creating a vDisk in with the Provisioning Server Image Builder when a XenApp (Presentation) Server is currently remapped.

Requirements

Requirements for completing the task and a specific knowledge and/or hardware and software requirements:

  • Basic knowledge and understanding of Provisioning Server for Datacenters 4.5
  • Advanced knowledge of XenApp (Presentation) Server 4.x
  • Basic knowledge of Active Directory, IIS, Windows System administration and Network Terminology
  • A baseline install of Windows Server 2003 with latest patches and drivers
  • A baseline install of XenApp (Presentation) Server on an existing Master Target Device
  • A vDisk created and ready to image
  • Knowledge of the Citrix Provisioning Server PS Integration Utility: CTX116063 (http://support.citrix.com/article/CTX116063)
  • Assumes default remapping of C: to M:

Background

XenApp (Presentation) Server drive letter remapping is only necessary when users will be accessing and saving data on their local client devices from ICA sessions. For example, when a user uses Microsoft Word on a XenApp (Presentation) Server and perform a 'Save As' they will be asked where to save the document. Without drive mapping, the user can become confused because their local system drive may appear as drive V (as an example). With drive remapping, their system drive will show up a drive letter C.

The advantages of remapping server drive letters are:

  • Users will be able to see their own local disk drives as the correct drive letters.
  • If you need to change the drive letter, the XenApp (Presentation) Server installation program provides an easy way to do this.

The disadvantages of remapping server drive letters are:

  • Any previously installed applications will most likely stop working.
  • Any new installed applications, patches or hotfixes may not properly install.
  • In some situations, unexplainable things happen on the server.

When dealing with a Provisioning Server that is streaming a XenApp (Presentation) Server down to a target device, the drive remapping may not correctly propagate to the vDisk therefore causing the XenApp (Presentation) Server to be inoperable upon boot. Below explain how to configure a XenApp (Presentation) Server that has a remapped drive so that it functions properly when streamed by Provisioning Server.

Procedure

The steps to complete the task:

  1. Boot the master target device and log on to the system as a domain administrator or a domain user.
  2. Install and configure Citrix XenApp (Presentation) Server.  At the end of the installation, you will be prompted to reboot
  3. Reboot the master target device.
  4. When the master target device is successfully restarted, log on to the system as a local or domain administrator, or a domain user (with local install privileges).
  5. Install the Provisioning Server for Datacenters Target Device client software and then shutdown the master target device.
  6. Boot the master target device, enter the BIOS configuration utility and configure the boot order to PXE boot first.  Save configuration settings and continue the boot process. When PXE booting a master target device for the first time, the Provisioning Server Streaming Service will prompt for the following:
    1. Client Name - Give the master target device a meaningful name
    2. Description - Give the master target device a meaningful description
    3. Select vDisk - Select the vDisk that was created and formatted for this installation
    4. Boot From - Select boot from hard drive
  7. When the master target device is successfully restarted, log on to the system as a domain administrator, or a domain user (with local install privileges).
  8. Double click on 'My Computer.'
  9. The drives drive will appear (assuming the defaults) as follows:
    1. System = M:
    2. CD-Rom = N:
    3. vDisk = C: 
  10. Right click on 'My Computer' and click 'Manage.' 
  11. The 'Computer Management' service console will open.
  12. Click on 'Disk Management' to view all disks associated with the Master Target Device.
  13. Right click on the vDisk drive C and click 'Change Drive Letter and Paths.'
  14. The 'Change Drive Letters and Path for C: (vDisks)' dialog box will open.
  15. Click on the 'Change' button.
  16. The 'Change Drive Letters or Path' dialog box will open.
  17. Select a drive letter greater than the remapped system drive.
  18. Click 'OK' to close the 'Change Drive Letter or Path' dialog box and click 'OK' to the 'Confirm' dialog box.
  19. The drive letters should be as follows (assuming system drive letter is M):
    1. System = M:
    2. CD-Rom = N:
    3. vDisk = O:
  20. Install the "PVS PS Integration Utility.msi" on the master target device.
    • As noted this utility does require a logon to invoke the cpsmods.vbs, which performs a series of steps that are critical for the XenApp (Presentation) Server to fully function while being streamed by Provisioning Server.  Several scenarios for completing the logon process are outlined in: CTX116063 (http://support.citrix.com/article/CTX116063)
  21. Click "Next" on the "Welcome" dialog box.
  22. Select the version of XenApp (Presentation) Server currently installed on the master target device and click "Next."
  23. Click "Next" on the "Confirm Installation" dialog box.
  24. Click "Close" on the "Installation Complete" dialog box.
  25. Upon completion of the install, an icon will be created on the desktop of the master target device called either the "CPS 4.5 Integration Tool" or "CPS 4.0 Integration Tool."
  26. Double click on the icon and a dialog box will appear indicating success.
  27. Click "OK" and the "Client Image Builder" will automatically open and proceed to build the image to the vDisk mapped during the PXE boot process.
  28. Build the vDisk pointing the 'Destination Drive' to the proper drive letter (Note: Be sure to 'Optimize' before building the image).
  29. Upon completion of the image build, shut down the master target device.
  30. The vDisk is now ready to stream to multiple Target Devices using Standard Image mode.

More Information

For more information on drive remapping please following these links: http://www.brianmadden.com/content/article/Should-you-remap-drive-letters-when-installing-MetaFrame-Presentation-Server

http://support.citrix.com/article/ctx457309

Note: This procedure will be available with pictures as a TechNote in the Knowledge Center.  I will update with the link once it is posted.

Permalink | Comments (15) |

Comments  (Hide Comments)

Great article Pete.  I look forward to more.  --  Jason E. Smith

Posted by Anonymous at Mar 25, 2008 08:07 | Reply To This

Pete, I am doing a PVS install with PS 4.0 that has remapped drives and multiple partitions. I was thinking for the multiple partitions I would use on vdisk and create two or three partitions on it. Is the procedure you were going to discuss in your next post?

Posted by Anonymous at Apr 02, 2008 08:15 | Reply To This

I am evaluating PVS with remapped drives on multiple partitions now and I am trying to get it to work where it does not feel all "kludgey".  A follow up article on how to do this would be fantastic!  (I could use this like yesterday)

Posted by Anonymous at May 06, 2008 15:55 | Reply To This

Technote can be found here...

http://support.citrix.com/article/CTX116698

Posted by Anonymous at May 06, 2008 16:34 | Reply To This

Thanks!  Unfortunately it does not work...  It will change the vDisk drive letter from P: to M: but subsequent drive letters remain the same.  In the articles case Q: remains Q: versus changing to N: when streamed.

Posted by Anonymous at May 08, 2008 15:17 | Reply To This

When in private image mode you can set it to N while streaming the image.  The limitation is windows, not PVS. 

Posted by Anonymous at May 08, 2008 15:19 | Reply To This

But I don't want it to be in Private Image Mode...  Are you saying this will only work in Private Image mode?  That if I take a master image and try to stream to 50 Terminal Servers with Multiple partitions that I would have to have 50 private images and manually change the drive letter?

Posted by Anonymous at May 08, 2008 23:35 | Reply To This

I should have clarified... once you assign the drive letter in private image mode, then switch back to Standard image mode and it should be set...  Like I said, window tends to get a mind of it's own.

Posted by Anonymous at May 09, 2008 08:49 | Reply To This

Yes, that worked quite nicely.  One more issue I have when taking a master image of a server with remapped drives I didnt have when taking a image of a server without remapped drives...when a server comes up off the standard image I cannot login to the domain.  I get a "...Computer Account cannot be found...".  Is this to be expected as well?

Posted by Anonymous at May 09, 2008 09:36 | Reply To This

Are you a current customer or doing a pilot?  Did you right click on the device in the PVS console and "Add to Domain" and then you need to go to the properties of the vDisk and the last tab (no in front of a console) in the properties box, there is another check box you need to tick.  Once you do those two steps... reboot and you should be set.

Posted by Anonymous at May 09, 2008 09:45 | Reply To This

I am both but my local Citrix contacts have little on no experience on remapped drives and PVS.  Interestingly enough, as I wrote that last message I went and reviewed the domain section in the manual and realized I had left that check box off when I set up my separate vDisk to test this out. I had added it to the domain but just left the password sync check box off.  Thanks for all your help as I think I am now on my way to a successful pilot.

As a side note, you may be wondering why I would need multiple partitions anyway on a vDisk.  The answer to that is that I use a competitor's App Virtualization software package (and have been for 4 years) and have 100's of applications virtualized.  Those applications reference other applications that are installed on that 2nd parition (adobe reader for example).  I am not in a position to "re-virtualize" those applications so being able to get this done was key.  Thanks again!

Posted by Anonymous at May 09, 2008 09:57 | Reply To This

Nice!  This is the scenario we preach about.  I would be very interested to hear about your end result.  Keep me posted...

BTW... this is Pete Downing, PM for PVS.

I am just being lazy and not logging in! 

Posted by Anonymous at May 09, 2008 10:08 | Reply To This

Also, it might be a good idea to modify CTX116698 to correct the following step near the bottom:

"13. Once the vDisk creation is complete and a target device is booted off the newly created vDisk, the two partitions in the vDisk take the place of M: and N: therefore making the XenApp Server operable in a typical scenario."

This gave me the impression that BOTH drives would automatically pick up the M: and N: drive designations with only M: will automatically pick it up and N: will have to be changed in Private mode before streaming in Std Mode. 

Posted by Anonymous at May 09, 2008 10:06 | Reply To This

Good call!  I will make the update.  Thanks for the feedback!  I personally appreciate it!

Pete Downing

Posted by Anonymous at May 09, 2008 10:09 | Reply To This

I figured it was you Pete.  Who else would be monitoring this and responding so quickly?

I thought about somthing else...  How does the PVS integration Utility handle this type of situation where the machine is rebooted in private mode to switch the drive letter?  Should everything be aok there as long as the vbs script runs on startup?

Posted by Anonymous at May 09, 2008 10:56 | Reply To This