Step 6: Assess Client Considerations

Article
02/25/2008

Published: November 12, 2007 | Updated: February 25, 2008

Some considerations need to be taken into account when utilizing SoftGrid in production. Although these considerations do not affect the decisions around the infrastructure, they do have an impact on the day-to-day performance and functioning of the environment.

SoftGrid Client Considerations

Ensure that the client cache is large enough to handle the applications being assigned to the user. If the cache is not scaled properly, then the user can experience application failures when disconnected. This occurs because the cache may have flushed the application in preference for another more recently run application. The client cache can be modified through the Desktop Configuration Client, which is installed with the SoftGrid client on the workstation.

SoftGrid Client in Standalone Mode

With the introduction of MSI Utility for SoftGrid 4.2, an additional packaging step has been introduced if running in Standalone Mode. The SoftGrid client has been updated to work with SoftGrid files installed by MSI. It is important to be aware that if a client is operating in a streaming environment that subsequently receives a SoftGrid-enabled application wrapped as an MSI, the client will no longer function within the streaming environment.

Terminal Server Considerations

Windows Server 2003 Terminal Services can be used to take advantage of additional value from SoftGrid virtual applications. Once an application is loaded on a Terminal Server in the SoftGrid cache, any user who has permissions for that application may use it on the Terminal Server. Additionally, SoftGrid can be used as an application coexistence tool. Because each application runs in its own virtual environment, applications that normally could not be installed on the same computer are able to co-exist.

The majority of the sequenced applications will run both on desktops and Terminal Servers without changes. However, testing of the applications should be done to ensure that there are no issues with running the application on Terminal Server.

Terminal Server Standalone Mode

The Terminal Server can run applications packaged with the MSI packaging tool. The SoftGrid client needs to be installed using Terminal Services install mode; however, when the SoftGrid client has been installed, sequenced applications will be loaded into the client cache and will be ready for execution. Apart from not having to install the application in install mode, there is virtually no functional difference for end users accessing the Terminal Server.

Terminal Server with Connected Mode

Terminal Server can also use SoftGrid in Connected Mode. However, because multiple users will be accessing the Terminal Server to access applications installed with SoftGrid, it is recommended to pre-cache the application for performance. Using streaming infrastructure, applications sequenced for desktops can be deployed to a Terminal Server without any modifications.

Streaming Terminal Servers should be located close to the SoftGrid streaming infrastructure. This ensures that applications can be quickly loaded and cached on the Terminal Server. Furthermore, if an application is updated through SoftGrid, the Terminal Server can quickly update its cache. If there is a significant delay in updating an application, all users who use the application in question will experience an outage for the time the application is being loaded. Application updates can only occur after the last user has exited the older version of the application. The update will then take place the next time that the application is launched.

This accelerator is part of a larger series of tools and guidance from Solution Accelerators.

Share via