Article ID: 938497
Article Last Modified on 12/27/2007
APPLIES TO
- Microsoft SoftGrid Application Virtualization for Terminal Services
- Microsoft SoftGrid Application Virtualization for Windows Desktops
SUMMARY
This article contains general guidelines and release information that will help you upgrade to, or help you perform a clean installation of Microsoft SoftGrid 4.1 SP1. This article lists download locations for the various SoftGrid applications, information about new capabilities, requirements, known issues, and best practices.
INTRODUCTION
This article contains the latest detailed information about Microsoft SoftGrid 4.1 Service Pack 1 (SP1). The article includes new capabilities, general information, and known issues for SoftGrid components. If you have a problem using Microsoft SoftGrid, refer to these release notes first to determine whether this document provides a resolution. If you do not find a resolution, visit the following Microsoft Web site to search for additional resolutions:
MORE INFORMATION
SoftGrid 4.1 SP1 Hotfix Rollup Package 1
This cumulative update for SoftGrid v4.1 SP1 provides the latest updates to SoftGrid v4.1 SP1. In addition to stability improvements, this update contains the following changes:
- Improvements to package upgrade when importing upgraded sequencings into the SoftGrid Server Management Console Snap-in.
- Improvements to package downgrade operation.
- Improvements to nonpaged pool usage when sequencing large applications.
- Improvements to sequencing of applications that use both Microsoft .NET Framework 1.1 and Microsoft .NET Framework 2.0.
- Improvements to command-line parameter handling of virtualized child processes.
New capabilities
SoftGrid 4.1 SP1 Hotfix Rollup Package 1 also provides the following new capabilities:
- Microsoft SoftGrid now provides support for the MSI Utility for Microsoft Application Virtualization.
- Microsoft SoftGrid now supports SoftGrid Server components running under WOW64 on 64-bit Windows.
Download locations
SoftGrid for Windows Desktops (4.1.2.21)
http://download.microsoft.com/download/d/6/d/d6dd54bd-2c9f-41ba-8fd7-4b8b03d5c12f/SoftGrid_wd_setup_4.1.2.21.exe
SoftGrid for Terminal Services (4.1.2.21)
http://download.microsoft.com/download/f/3/d/f3deb4c3-f484-4bf7-ae49-c9f8a010b594/SoftGrid_ts_setup_4.1.2.21.exe
SoftGrid Server (4.1.2.20)
http://download.microsoft.com/download/9/9/4/994b08d3-7f01-4696-994d-a67f2e0bdf33/SoftGrid_server_setup_4.1.2.20.exe
SoftGrid Sequencer (4.1.2.20)
http://download.microsoft.com/download/e/8/0/e80de2bf-bebd-480e-a1ee-f9febb996b8b/SoftGrid_sequencer_setup_4.1.2.20.exe
Previous releases
SoftGrid SoftGrid 4.1 SP1
Download locations
SoftGrid Sequencer (4.1.1.303)
http://download.microsoft.com/download/0/6/c/06cf3aac-347e-4e42-9355-fcfcec3c7f43/SoftGrid_sequencer_setup_4.1.1.303.exe
SoftGrid Server (4.1.1.302)
http://download.microsoft.com/download/a/f/c/afc8cf1f-d271-426e-923a-b04a34674c3c/SoftGrid_server_setup_4.1.1.302.exe
SoftGrid for Terminal Services (4.1.1.310)
http://download.microsoft.com/download/6/3/8/638af9fd-a72c-4125-a5ad-12f94e3eade9/SoftGrid_ts_setup_4.1.1.310.exe
SoftGrid for Windows Desktops (4.1.1.310)
http://download.microsoft.com/download/f/b/6/fb62eeb3-ecd1-4a05-b1b6-ec087cb7ae8c/SoftGrid_wd_setup_4.1.1.310.exe
New capabilities
Microsoft SoftGrid 4.1 SP1 improves support for sequencing SxS applications that have public assemblies, such as the 2007 Microsoft Office release.
General release information
Upgrade or uninstall and reinstall?
You can upgrade a client to SoftGrid 4.1 SP1 from a client version 3.2, version 4.0, or version 4.1. The upgrade process preserves all system configuration settings and user-profile settings. When you upgrade from version 3.2, the client software-application cache is flushed. After the upgrade, you must reload applications.
We recommend that you upgrade clients to the latest version. However, you can also uninstall earlier versions before you install client version 4.x. To uninstall earlier versions, use the Add or Remove Programs utility. When you uninstall, the local SoftGrid settings are removed for the user who performs the uninstall, and the cache is flushed.
If you are using an earlier version of the SoftGrid Sequencer, you cannot upgrade directly to version 4.1 SP1. You must restore the appropriate backup image base operating system on the computer that is running SoftGrid Sequencer before you install version 4.1 SP1. The backup image should contain end-user software that will be on every client computer.
You can upgrade all SoftGrid server components from version 3.1, version 3.2, version 4.0, or version 4.1. Upgrades from earlier releases of the Microsoft SoftGrid components are not supported. If you have older Microsoft SoftGrid components, uninstall them by using the Add or Remove Programs utility before you install version 4.1 SP1 components.
The server upgrade automatically validates existing applications and identifies application configuration problems.
Note Applications that you sequence with the SoftGrid Sequencer version 4.x may not stream correctly to SoftGrid clients that are running version 3.x. You can upgrade target clients to version 4.x or continue to stream version 3.x sequenced applications to the older clients. Testing with client versions 4.x and SoftGrid Sequencer version 4.x is recommended.
Manuals
The following documents support this release:
- SoftGrid Quick Start Guide
- Installing the SoftGrid Sequencer
- Installing the SoftGrid Components
- Installing the SoftGrid Client
- SoftGrid Platform Administrator’s Guide
- SoftGrid Sequencer User’s Guide
Windows Server requirements
The installation requirement for servers is Microsoft Windows Server 2003 SP1, or later versions of Windows Server 2003. This is necessary for the SoftGrid Management Console Snap-in. The SoftGrid Virtual Application Server installs on a computer that is running an earlier version than Windows Server 2003 SP1. However, the SoftGrid Virtual Application Server will not add the console. You can manage this server from a different computer that has the console installed.
Important SoftGrid Server Management Console Snap-in no longer installs or works with Microsoft Windows 2000 Server.
Known issues
| Description | More information |
Active upgrade fails with a combination of 3.x clients and 4.x serversEven after the restart of a domain controller, an active upgrade may fail for 3.x clients and 4.x servers |
Active upgrade works with SoftGrid Sequencer 4.x, 4.x server and 4.x clients. An active upgrade may work in various mixed environments. |
An MSDE upgrade on a SoftGrid version 3.2 server prompts for a restartIf the database is on the same computer as the server, it may prompt for a restart during an MSDE upgrade. If you restart, you must restart the whole upgrade. |
Do not restart. When you are prompted, click Cancel, and then continue with the upgrade. |
Application fails when it starts after you cancel an application importYou receive unexpected error code 00000125 when you try to start an application after you cancel an application import through the SoftGrid Client Management Console Snap-in. |
Unload the application in the SoftGrid Client Management Console Snap-in before you try to restart the application. |
|
If the content directory points to a shared network location that is not available, the uninstall fails with error message 1606. |
If the content directory is a local directory, re-create the directory with the same name before you uninstall. If content is in a shared location, make sure that this location is available to the server before you uninstall. |
Applications that have background processes may prevent the SoftGrid client from uninstalling correctlyA dialog box appears that prompts you to close all the virtual applications before you continue, even though all virtual applications appear to be closed. |
Manually exit from the SoftGrid client notification area before you uninstall the SoftGrid client. |
Client installer does not appear to save new global data folderDuring client installation, the display is not updated when you browse for and select a folder. |
This is a display issue. You can see the change by using either the Back button or the Next button. |
Client UPN logon requires full domain nameFor remote connections, the client logon needs the full UPN name. This includes the suffix. For example, domainuser@company2.int. |
When you log on with a UPN domain user, use the full credentials. |
Conflict about how to import applications used by multiple packagesIn rare cases, when you import an application that is used by more than one package, you may receive error messages and reports that the package GUID is already being used. The Management Console Snap-in may freeze. |
These error messages are a known limitation of this release. However, when you restart the Management Console Snap-in, the package is successfully imported. |
Corrupted VFS files on FAT32 driveOn a computer that is running SoftGrid Sequencer using a FAT32 drive, the VFS files can become corrupted. |
Use only NTFS drives for sequencing. Do not sequence to a FAT32 drive. |
Default application does not appear in a split-server SoftGrid installationIn a SoftGrid installation that uses the Web service and database on one computer and the Virtual Application Server on another, the default application may not appear in the database or on the published shortcut locations. |
This is a known limitation. |
You cannot change the default port during client installThe default port 554 remains after you enter a different port during installation. |
After installation, use the Client Management Console Snap-in to select the SoftGrid server and enter the desired port in the server properties. |
Multi-Stage upgrade failureThe second update on a multi-stage upgrade to Microsoft Office XP can fail on the second consecutive update. |
Install the application to a folder at least two levels under the SoftGrid Sequencer drive root directory. For example, install the application to Q:\MyApp\New instead of Q:\MyApp. |
Sequencer command line: SystemGuard failure messageDuring command line sequencing, you may receive an error message that reports a SystemGuard download failure. The error reports that the installation path parameter is not valid. |
? * s< or >. |
Sequencer may produce extra .osd filesSoftGrid Sequencer version 4.x can generate more .osd files than necessary for an application. |
Before you copy sequenced files to the Virtual Application Server, verify that the .osd files relate to the application. For example, if SoftGrid Sequencer created .osd files for Notepad and Explorer, and you know that these are not part of the application, delete these .osd files before you copy the SoftGrid Sequencer output. |
Server does not start after 3.1 to 4.x server upgradeIf a port number value is in the SQL server DATA_SOURCES table, the SoftGrid server may not start. |
Edit the SQL Server’s DATA_SOURCES table to remove the port number. |
Server Service: Fail on Name ChangeThe SoftGrid Virtual Application Server service does not start when the server name is changed to DNS format. |
Leave the server name in the same format as it is in after installation. |
Server Upgrade Error MessagesIf you modified your SoftGrid server content path during the original install, you may receive two error messages when the upgrade tries to replace DefaultApp.osd. It cannot find that file if it is not in |
Click OK at each error message. This error does not affect the upgrade. You can still locate that file in its previous location. |
Silent upgrade of the server may fail under certain scenariosSilent upgrade of the server may fail when the REINSTALL=ALL and REINSTALLMODE=vomus properties are specified on the misexec command line and you are doing a major upgrade. |
If you run the setup.exe program for the SoftGrid server installer, you will avoid this situation if you determine whether you are doing a major or minor upgrade. Specify the REINSTALL=ALL and REINSTALLMODE=vomus properties on the misexec command line only if you are doing an upgrade from SoftGrid version 4.1. |
SoftGrid client installer does not prevent installation on 64-bit editions of WindowsThe SoftGrid client installer does not detect that it is being run on a 64-bit system and does not provide a dialog to the user that explains that the platform is not supported. |
SoftGrid currently does not support 64-bit editions of Windows. |
SoftGrid Server Management Console Snap-in reports an earlier version after you upgradeAfter you upgrade the SoftGrid Server Management Console Snap-in, the earlier version of SoftGrid Server Management Console Snap-in is displayed in the About SoftGrid Console window. |
The SoftGrid Server Management Console Snap-in was upgraded correctly but the version number is incorrectly cached by MMC 3.0. |
Stand-alone management Web service upgrade failsA SoftGrid management Web service cannot upgrade from version 3.2 to version 4.x. The SoftGrid management Web service cannot locate application packages. |
Upgrade the SoftGrid Virtual Application Server before you try to upgrade a stand-alone Management Web Service. Then, the Management Web Service can find the correct content path for application migration. |
Stopped listener may not recoverUsing the command line to stop the listener when a virtualized application is running can freeze the listener. |
The listener freezes if shutdown by a command line happens when the end-user has virtualized applications that are running. Restart the client computer if this happens. |
Two reports are missing in version 4.1 SP1The license compliance and Use/Group Application Configuration reports do not appear in version 4.1 SP1. |
This is a known limitation. |
Unable to import upgraded sequencings as new applications in the Server Management Console Snap-inIf you try to import a sequencing that has been upgraded through a package upgrade that did not previously exist on the SoftGrid Server Management Console Snap-in, you may receive error code 0000C81E. |
To work around this issue, remove the trailing version number in the .sft file name, for example, rename MyApp_3.sft to MyApp.sft. |
Upgrading SoftGrid server from 3.2.2.8 to 4.x cannot create snap-inIf you try to upgrade the SoftGrid server from 3.2.2.8 to 4.x, it cannot create the SoftGrid Server Management Console Snap-in. |
This issue is resolved if you perform a repair. |
Upgrading SoftGrid server to MMC 3.0 produces error in SoftGrid client Management Console Snap-inIf you have the SoftGrid Client Management Console Snap-in installed on a computer where the SoftGrid Server Management Console Snap-in is also installed and you upgrade to MMC 3.0, when you click any of the nodes under SoftGrid in the SoftGrid Client Management Console Snap-in, you receive an error message. |
If you ignore this error message, the SoftGrid Client Management Console Snap-in works correctly. |
Upgrading the SoftGrid server from version 4.x resets the server log location back to the default locationIf you previously deleted the default log directory and specified a custom log directory, the SoftGrid server does not start with error 41539. |
To resolve this issue, reset the log location manually. |
Usage data lost with server connectionApplication usage information can be discarded when the SoftGrid client reconnects after it loses the connection to the SoftGrid Virtual Application Server. |
This remains a limitation of the client. |
You cannot delete file type associations when you import an .osd fileOn the Import Wizard’s File Associations tab, existing file type associations appear to be deleted correctly. The file type associations may remain in the file type association node of the Management Console Snap-in. |
After you import the file, remove the file type associations through the Management Console Snap-in File Associations node. |
SoftGrid Virtual Application Server, Management Server, and Web Service
General guidelines
- Microsoft Windows NT 4.0 is not supported for SoftGrid components. However, the components continue to function in Windows NT 4.0 domains. See the Quick Start and Installation Guides for more information.
- SQL Server 2005 Express is not supported.
- Installation of Microsoft SoftGrid components requires local administrative credentials on the target server.
- SoftGrid Management Web Service installation requires Microsoft .NET Framework 2.0.
- Do not use the # character in fields of the Microsoft SoftGrid installation wizard. That may cause the installation of the SoftGrid Virtual Application Server to fail.
- Before you install the SoftGrid Virtual Application Server for use with a SQL Server 2005, make sure that the SQL Server configuration has TCP/IP enabled. In the SQL Server Configuration Manager, expand SQL Server 2005 Configuration, and then click Protocols for MSSQLSERVER. Right-click TCP/IP, and then click Enable. Finally, restart the SQL Server. To do this, click SQL Server 2005 Services, right-click SQL Server (MSSQLSERVER), and then click Restart.
- Do not use hyphens (dashes) in an existing SQL database name with a SoftGrid Virtual Application Server. SoftGrid uses SQL functions that do not support database names with hyphens and when hyphens are used, the server installation fails. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
165432 PRB: DBGrid Does Not Insert Record If Field Name Contains Dash
- By default, a Virtual Application Server’s log level is set to Warnings/Errors This includes warnings, errors, fatal errors and transactions. You may have to raise the log level to diagnose problems. Raising the log level results in faster log file growth and takes more disk space. After you raise the log level and diagnose the problem, return the log level to a reduced setting so the sft-server.log file does not grow unnecessarily. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
930843 Log options for SoftGrid Management Console 3.x
- On Windows Server 2003 in a Windows Load Balancing environment, do not set the affinity to None. This can cause a failure of clients that request streamed applications. Instead, set the affinity to Single. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
932018 How SoftGrid Networking works together with Windows Server 2003 Network Load Balancing
- Each Virtual Application Server in a server group should have the same packages of the same versions. If not, SoftGrid clients that are configured to obtain the same application from different servers and clients that fail over from one server to another may experience problems.
- Automated usage cleanup of the SoftGrid data store requires SQLSERVERAGENT to be running on the SoftGrid data store computer.
- You may be unable to log into the SoftGrid Management Console Snap-in through a firewall by using a proxy, unless one of the following conditions is true:
- You authenticate over a Point-to-Point Tunneling Protocol (PPTP) connection.
- You configure authentication for the Default Web Site to include Basic authentication.
The default request time-out for SoftGrid Management Web Service requests is set to 15 minutes (900 seconds). The large default value is required because reports can take a very long time to run. The time-out value can be modified by editing the web.config file and changing the ‘executionTimeout’ attribute of the ‘configuration/system.web/httpRuntime’ element.
<configuration> <system.web> <!-- Time out (in seconds) when servicing request --> <httpRuntime executionTimeout="900" /> </system.web> </configuration>
SoftGrid Server Management Console Snap-in
General guidelines
- To install the SoftGrid Management Console Snap-in, first log on as an administrator on that computer.
- Only users in the Softricity Administrators node can log on to the SoftGrid Management Console Snap-in. You specify these users during installation or you can add them in the SoftGrid Management Console Snap-in.
- It is currently not supported to change the maximum time for licenses.
- The versions of the SoftGrid Management Console Snap-in and SoftGrid Management Web Service must match.
- Use the SoftGrid Sequencer OSD Editor to edit an .osd file and avoid introducing unauthorized XML.
- Avoid making duplicate file type associations that can cause conflicts on the client computers.
SoftGrid Sequencer
Best practices
Before you use the SoftGrid Sequencer, refer to the best practices guidelines for Sequencing. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
932137 Best practices to use for sequencing in Microsoft SoftGrid
Before sequencing an application, search the Microsoft knowledgebase for guidelines on sequencing that help prevent problems sequencing some applications, such as Microsoft Office.
General guidelines
- The Sequencing computer and the SoftGrid clients to which the sequenced application will be streamed must have the same version of the Microsoft Installer. If it is not the same version, the user may see an installer dialog or have trouble running the application.
- If the base operating system on which you are sequencing includes Terminal Services, you must put the operating system into Install mode during the installation phase of sequencing. You can do this through commands. However, to do this through Control Panel, click Add or Remove Programs, and then click Add New Programs. Then, begin your installation phase.
- When you click File, and then click New Package, we recommend that you sequence a new application, and then opt for help. When you have experience sequencing, you can use the individual wizards in the Tools menu.
- If the application crashes during sequencing, re-sequence the application even if it appears to function correctly after the crash.
- By default, all .osd files use the same Virtual Application Server location information and suite name. To modify the location of a single .osd file, use the Sequencer OSD Editor. To change the location or suite name for all .osd files in the package, use the Package Configuration Wizard.
- Use the Sequencer OSD Editor to edit an .osd file and avoid introducing unauthorized XML.
- Keep the .sprj (Project) file together with its other package files. This file contains information that is required for a package upgrade.
- Before you install the SoftGrid Sequencer, verify that the Launch folder windows in a separate process check box is not selected. To do this in Windows Explorer, click Tools, click Folder Options, and then click the View tab. If the Launch folder windows in a separate process check box is selected, click to clear the check box. If you change the value, restart.
- Installation of the SoftGrid Sequencer requires local administrative credentials on the sequencing station.
SoftGrid clients
General guidelines
- Do not install the SoftGrid client on the same computer as a SoftGrid Sequencer.
- The Softricity drive stores application-specific data. Do not store user data on this drive.
- Make sure that users who use roaming profiles only log into one computer at a time. Otherwise, you may experience intermittent problems.
- We recommend that you remove locally installed applications that you plan to stream. Otherwise, users may see a message from the streamed application reporting that says the feature is not available.
- For optimal performance, the client cache must be larger than the size of all streamed applications.
- Load applications in cache that are required for all clients, and make sure that the Disconnected Operation option is enabled. This option lets users start applications when there is a network or SoftGrid Virtual Application Server outage.
- Install SoftGrid client and streamed applications to paths that use 255 characters or less.
- Use a host name instead of an IP address to locate a Desktop Configuration Server if you have not enabled reverse lookup for this address or if this address is dynamic and no longer synchronized to its DNS entry.
- Do not use the Detect and Repair command in a Microsoft Office application’s Help menu. This command can cause an Office error message.
- A client computer that is not part of a domain but that has used a set of credentials to obtain files from a domain’s network share may in some instances use these same credentials when requesting SoftGrid-enabled applications. If these credentials prove invalid, clear them so that you can enter valid ones when you are prompted.
- SoftGrid Administrators can stop the Softricity SoftGrid Client service. Stopping the service ends all client sessions and users may lose data. The best practice is to notify client users to exit all applications and log off from their sessions before you stop this service.
SoftGrid Client for Terminal Servers
General guidelines
- When you use roaming profiles, turn off file caching. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
287566 The Cache Option for Offline Files Must Be Disabled on Roaming User Profile Shares
- If you are using roaming profiles or application-folder redirection, users who roam between SoftGrid client version 3.x and version 4.x may experience problems. In particular, they may encounter shortcuts and file type associations that cannot be accessed and may be unable to view the message history from a SoftGrid client that is running version 3.x. These problems should not result in the loss of user data or application settings. We recommend that you postpone by using central management of desktop configuration until all computers have been upgraded to SoftGrid version 4.x. To reduce potential affects, you should make sure that all SoftGrid clients to which a user can roam are set up to use the same source of desktop configuration information and to update application information upon log on.
Keywords: kbtshoot kbinfo KB938497
