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

Microsoft SoftGrid consists of several capabilities. The primary capability is application virtualization. Application virtualization can best be described as running an application using a local workstation without installing the application on the client operating system. This means that, instead of loading files into the program files directory and adding entries into the local registry, the application is loaded into a virtual environment on the client. Once the applications are loaded, the client can take advantage of the following key application virtualization features:

• Application settings are not stored on the local computer’s registry. They are maintained in the virtual environment.
• Incompatible application versions can co-exist without any conflicts.
• Applications can be quickly reset to their default deployment state.
• Applications can be removed without leaving any traces on the client computers.

The secondary capability is virtual application management. With SoftGrid 4.2, the primary and secondary technologies can be implemented independently, providing two usage options:

• Standalone Mode. Standalone Mode allows a SoftGrid-enabled application to be delivered to the SoftGrid client using traditional application delivery systems such as Group Policy application installation or System Center Configuration Manager.
• Connected Mode. Connected Mode provides infrastructure to distribute, manage, and report on the usage of SoftGrid-enabled applications. This mode is also known as Classic Mode.

Care should be taken when introducing both modes into a location or where clients are mobile between locations. If a client computer running in Connected Mode receives an application that is distributed via Standalone Mode, the client will cease to run any Connected Mode applications.

Option 1: Standalone Mode

SoftGrid in Standalone Mode consists of just the SoftGrid client and sequencer; no additional SoftGrid server infrastructure is required. Applications are prepared for virtualization in a process called sequencing. Once the application has been sequenced, the MSI Utility for Microsoft Application Virtualization (MSI Utility) is used to create an MSI installer package for the sequenced application.

Note   In SoftGrid 4.2, the MSI Utility will be available as a separate download. This functionality will be incorporated into the Sequencer in version 4.5.

The MSI package allows the sequenced application to be deployed using installation methods already in place. Some common deployment methods are:

• Active Directory publishing through a Group Policy object (GPO).
• Media distribution.
• Run from a file share.
• Software management systems such as Microsoft Systems Management Server (SMS) 2003 or System Center Configuration Manager 2007.

When the application is deployed to a client computer, the application will be fully loaded onto the client computer by the Windows Installer.

If frequent updates to the virtualized application package are required, then be aware that Standalone Mode does not provide a mechanism for delta updates. Delta updating is the process of just sending only the bits that are required to update the application.

If an application is deployed in Standalone Mode and is updated, then the entire application needs to be redeployed to the clients. User preferences for the applications, however, will survive application updates.

When to Use SoftGrid Standalone Mode

Standalone Mode provides a solution for environments where there has already been an investment in a software management system. Additionally, Standalone Mode can allow a small group of users to quickly utilize application virtualization without planning for a complete management infrastructure. Use SoftGrid Standalone Mode:

• Where software management systems, such as SMS 2003 and Microsoft Configuration Manager, are already in place.
• Where resources are limited, such as in small organizations.
• Where network bandwidth limitations prevent electronic software distribution. In this case, virtual application delivery on physical media can be used (for example, CD, DVD, USB Key, and so on).
• Where SoftGrid application virtualization is required in multiple locations and capital and operational costs associated with separate SoftGrid infrastructure are a concern.

Option 2: Connected Mode

SoftGrid in Connected Mode, also known as Classic Mode, uses built-in software distribution and management capabilities. For the purposes of this document, Connected Mode will be the standard term.

Organizations should decide if they want to deploy the SoftGrid Connected Mode infrastructure by considering several additional features (described in the following section) that are exclusively available to this configuration of SoftGrid.

As with Standalone Mode deployments, applications are sequenced using the SoftGrid sequencer. However, instead of being packaged with an MSI file, the SoftGrid-enabled applications are placed on a virtual application server (VAS) that streams applications to client computers.

When to Use SoftGrid Connected Mode

There are several native features that are only available using the full management capabilities of SoftGrid. A complete SoftGrid management environment will be needed if any of the following features are required when planning a SoftGrid installation:

• Application Streaming. This feature allows a SoftGrid application to be incrementally streamed down to a client. Streaming is used both as an application deployment technology and as a management tool. It transports applications to the client machine and permits seamless background application updates. The streaming technology can also reduce the deployment time of an application by separating applications into two feature blocks. Upon the first launch of an application, only Feature Block 1, which is required to start the application, is streamed to the client. As subsequent features are used in the application, SoftGrid streams additional pieces of Feature Block 2 from the SoftGrid servers.
• Group-based Application Publishing. Applications can be associated with security groups in Active Directory. Users will only receive the applications if they are members of the associated groups.
• License Enforcement:
  • Named License. A software package can be associated with a specific user name. Only the user who is named in the policy will be able to launch the application.
  • Concurrent License Restrictions. Software that is licensed for concurrent usage can be metered out based on the number of users currently using an application. If more than the defined number of users attempt to launch the application, the surplus launch attempts will be denied access to the application.
• Built-in SoftGrid Reporting. SoftGrid can provide metering and license tracking. However, there are some scalability issues that are addressed later in this guide.
• SoftGrid Classic Software Usage Reporting Console. SoftGrid provides a console for generating reports.

In order to avoid the risk of poor performance or virtualized application reliability problems within the environment, it is recommended that Connected Mode SoftGrid infrastructure be deployed within a single, well-connected location. In this case, well-connected means 100-megabit or better bandwidth and < 100 ms latency throughout the location.

Evaluating the Characteristics

Technical criteria are not the only factors that should be considered when making an infrastructure design decision. The decision should also be mapped to appropriate operational criteria or characteristics. The following tables compare each option according to the characteristics that are applicable to this decision-making topic.

Validating with the Business

• Does the business have specific requirements for software management? The decision to deploy SoftGrid management infrastructure will have a significant impact on the way applications are handled in the organization. If there is no specific reason for requiring virtual application management, it is more cost effective to deploy SoftGrid using the Standalone Mode.

Decision Summary

Deciding how to deploy SoftGrid applications will come down to deciding if deploying SoftGrid Connected Mode features are required in the organization’s environment.

The reader has a choice at this juncture. If the decision to use Standalone Mode has been made, then proceed to Step 7; otherwise, proceed to Step 2 where the design of SoftGrid in Connected Mode is detailed.