Some applications fail to sequence to specific drive letters

This article has been archived. It is offered "as is" and will no longer be updated.
Some programs that are sequenced by using the Microsoft SoftGrid Sequencer do not sequence to specific drive letters. Both Microsoft programs and third-party programs can be affected by this problem.
This problem may occur because the sequencing process of parsing and replacing specific drive letter information by using the %SFT_MNT% variable in case-sensitive registry keys can cause unexpected behavior.
To work around this problem, use one of the following methods.

Method 1

Configure the application to sequence to a drive letter other then the drive letter that is causing the problem.

Method 2

Configure the application to sequence to the drive letter that is causing this problem. However, move the Package Root Directory one directory level deeper than the current level for the directory.

For example, this problem occurs when the Package Root Directory has the following path on drive O:
Instead, move the Package Root Directory to the following path:
After you move the directory, you would still select "msoffice.v1" as the Package Root Directory.
Note This modification requires that files that use a hard-coded path of O:\SoftGrid\msoffice.v1 are manually modified to use the path of O:\msoffice.v1 before you save the sequence. These files include such extension as .cfg, .config, and .ini.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Article ID: 930995 - Last Review: 01/15/2015 08:37:53 - Revision: 2.0

  • Microsoft SoftGrid for Terminal Services
  • Microsoft SoftGrid for Windows Desktops
  • kbnosurvey kbarchive kbtshoot kbexpertiseinter KB930995