softricity softgrid platform v4.0 administrator’s...

Softricity® SoftGrid® Platform v4.0Administrator’s Guidev1.0

Notice

General Disclaimer

The contents of this document are subject to change without notice. Therefore, the information presented herein shall not be construed as a commitment or warranty.

Softricity, Inc. shall not be liable for any technical or editorial errors or omissions contained herein or for incidental or consequential damages resulting from the performance, furnishing, reliance on, or use of this material.

Patents Certain software described in this document is protected by issued and pending U.S. and foreign patents.

Softricity, SoftGrid, SystemGuard, Virtual Application Services, Virtual Application Server, Powering Software Services, and the Softricity logo are trademarks or registered trademarks of Softricity, Inc. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation. All other brand and product names are trademarks or registered trademarks of their respective owners.

Copyright This document contains confidential and proprietary information protected by copyright. All rights reserved. Copying or other reproduction of all or parts of this document is prohibited without the permission of Softricity, Inc.

© 2006 by Softricity, Inc.

Contact Information

Softricity, Inc.27 Melcher Street3rd FloorBoston, MA 02210 U.S.A.

Phone: (617) 695-0336

Website: www.softricity.com

www.softricity.com

Contents

Chapter 1Introduction ............................................................................................... 1

Administering the SoftGrid Platform................................................................. 1This guide’s contents ................................................................................ 1

Prerequisites .................................................................................................... 1Platform Concepts............................................................................................ 2

Virtual Environment................................................................................... 2Central Control and Updates .................................................................... 2Delivering applications .............................................................................. 4Installing and configuration ....................................................................... 4

Production environments ................................................................... 5Recurring components....................................................................... 5

Delivery components ................................................................................ 6SoftGrid Sequencer .................................................................................. 7

.sft file ................................................................................................ 7

.osd and .ico files .............................................................................. 7SoftGrid Client........................................................................................... 8

Security and control ........................................................................... 8Virtual runtime environment ............................................................... 8Desktop icon ...................................................................................... 8Desktop configuration ........................................................................ 8SoftGrid Clients in different modes .................................................... 9

SoftGrid Virtual Application Server............................................................ 9Start-up configuration ........................................................................ 9

HTTP Server ............................................................................................. 10.osd, .ico files and desktop configuration........................................... 10

Management Components........................................................................ 11SoftGrid Management Console................................................................. 11

Configuration objects ......................................................................... 12Reporting objects............................................................................... 12MMC snapin....................................................................................... 12

SoftGrid Management Web Service.......................................................... 12Information flow ................................................................................. 13Security .............................................................................................. 13

SoftGrid Data Store................................................................................... 13Configuration records and reports ..................................................... 14

Domain Controller ..................................................................................... 14Beyond this Guide............................................................................................ 15

Other documents ...................................................................................... 15Knowledgebase ........................................................................................ 16Customer Support Center ......................................................................... 16

Chapter 2Configuring Applications ......................................................................... 17

Overview .......................................................................................................... 17 Initial Setup .............................................................................................. 17

Import an Application ....................................................................................... 18Import or Add ............................................................................................ 18

Application User Groups .................................................................................. 19Changing User Groups ............................................................................. 19

Provider Policy Consideration............................................................ 20User Considerations .......................................................................... 20

Application License Groups.............................................................................. 20Change an Application License Group ..................................................... 20

SoftGrid Platform v4.0 1

Platform Administrator’s Guide

Application Shortcuts ....................................................................................... 21Changing Shortcuts .................................................................................. 21

File Type Associations ..................................................................................... 21Changing FTAs ......................................................................................... 21

Application Server Groups ............................................................................... 22Changing Server Groups .......................................................................... 23

Removing Applications..................................................................................... 23User considerations ........................................................................... 23

Delete an Application ................................................................................ 24

Chapter 3Configuring Application Licenses .......................................................... 25

Overview .......................................................................................................... 25License Groups ................................................................................................ 25

Licensing and Reporting ........................................................................... 26Unlimited Licenses ........................................................................................... 27

Create an Unlimited License..................................................................... 27Unlimited Licenses and Suites.................................................................. 28

Adding or Removing a License Group Association ........................... 28License Expiration Warning ...................................................................... 28

Setting License Expiration Warning................................................... 29Named Licenses .............................................................................................. 29

Create a Named License and Group ........................................................ 29Add Named Licenses to a Group.............................................................. 30Change Named Users .............................................................................. 31

Concurrent Licenses ........................................................................................ 32Add a Concurrent License and Group ...................................................... 32Add Concurrent Licenses.......................................................................... 33Change Concurrent Users ........................................................................ 33

Enabling and Disabling Licenses ..................................................................... 34Removing a License......................................................................................... 34Deleting an Application License Group ............................................................ 35

Chapter 4Configuring Virtual Application Servers ................................................ 37

Overview .......................................................................................................... 37Server Groups.................................................................................................. 37

Add a Server Group .................................................................................. 37Add a Server to a Server Group ............................................................... 38Remove a Server Group ........................................................................... 38Remove a Server from a Server Group .................................................... 39

Provider Policies .............................................................................................. 39Change Provider Policy ............................................................................ 39

Log Modules..................................................................................................... 40Change Log Modules................................................................................ 40

Chapter 5Configuring Provider Policies ................................................................. 43

Overview .......................................................................................................... 43Add Provider Policy.......................................................................................... 43

Authentication Options....................................................................... 45

2 SoftGrid Platform v4.0


Apply Provider Policy........................................................................................ 45Change Shortcut Management......................................................................... 46Change User Groups........................................................................................ 47Change Authentication Settings ....................................................................... 47Change Authorization Settings ......................................................................... 48Change Licensing Settings ............................................................................... 49

Chapter 6Managing the SoftGrid Platform.............................................................. 51

Overview........................................................................................................... 51Control of Data Store Growth ........................................................................... 51

Controlling Data Store Growth................................................................... 51Data Store Considerations ........................................................................ 52

SoftGrid Administrator Privileges...................................................................... 52Adding SoftGrid Administrators ................................................................. 53Deleting SoftGrid Administrators ............................................................... 53Resetting SoftGrid Administrators ............................................................. 53

Licenses’ Associated Applications.................................................................... 54Reviewing Associated Applications ........................................................... 54

Reporting .......................................................................................................... 55General Report Procedures....................................................................... 55

Creating Reports ................................................................................ 55Customizing Columns ........................................................................ 56Running Reports ................................................................................ 56Printing or Exporting Reports ............................................................. 56

System Utilization Reports ........................................................................ 56Generate a System Utilization Report ................................................ 57

Software Audit Reports.............................................................................. 57Generate an Audit Report .................................................................. 57

Application Utilization Reports................................................................... 57Generate an Application Utilization Report ........................................ 58

User/Group Activity Reports ...................................................................... 58Generate an Activity Report ............................................................... 58

License Compliance Reports..................................................................... 58Generate a Compliance Report.......................................................... 59

System Error Reports ................................................................................ 59Generate a System Error Report........................................................ 59

User/Group Application Configuration Reports ......................................... 60Generate a User/Group Application Configuration Report ................. 60

Restart a Virtual Application Server.................................................................. 60Change Data Store Access Credentials ........................................................... 61Changing Account Authority Credentials .......................................................... 61

Appendix ATroubleshooting and Messages.............................................................. 63

Knoweldgebase Articles ................................................................................... 63Common Issues................................................................................................ 63

Reclaiming SG Client Cache ..................................................................... 64SG Client Cannot Launch Specified Application e(Error 0A-20000194) ... 64

Application Not Added to Console...................................................... 64.sft File Not in /content Structure ........................................................ 64Specified Provider Policy Does Not Exist ........................................... 65

Application Does Not Complete Launch (Error 04-00000428) .................. 65Application-Specific Errors ................................................................. 65Missing Files....................................................................................... 65Incompatible File Version ................................................................... 65Dr. Watson on Launch Attempt .......................................................... 65User Needs Access to TEMP Directory ............................................. 65



Windows Side-by-Side Assemblies Error .......................................... 66Multiple Instances Fail to Launch ...................................................... 66Launch Requires Administrative Rights............................................. 66User Must Be Assigned to Create global object ................................ 66

Client Cannot Find Package or Files (Error 0A-000800B) ........................ 66Invalid HREF path.............................................................................. 66Invalid Provider Policy ....................................................................... 67Log On Account .sft Permissions....................................................... 67

Invalid WORKINGDIR (Error 2C-8007010B) ............................................ 67Client Cannot Find Server (Error 2A-00002AFC) ..................................... 67Client Cannot Access Application (Error 0A-20000193) ........................... 68

Verifying Access Association............................................................. 68Verifying Provider Policy Association ................................................ 68Verifying ?Customer= Entry............................................................... 68

Conflicting Application Names and Versions (Error 44-00001003)........... 68Invalid Server Port (Error 2A-0000274D).................................................. 69IIS Permissions (Error 0000C824) ............................................................ 69

Local Activation Permissions ............................................................. 69ASP.NET Permissions....................................................................... 70SharePoint Conflicts .......................................................................... 70

Index .......................................................................................................... 71


Chapter 1

Introduction

Administering the SoftGrid PlatformMicrosoft’s SoftGrid Virtual Application Platform enables you to transform your Microsoft Windows and Terminal Server-based applications into centrally managed on-demand services. Your users can initiate these services over a wired or wireless network, across your organization’s LAN or WAN, or across the Internet. Your mobile users can also retain these services in disconnected mode.

This guide’s contents

This Administrator’s Guide presents the key concepts and components of the SoftGrid Platform. It provides information you can use in the planning, configuration, maintenance and management of your application-delivery system.

For related documents that detail installation and provide tutorials, see the online Sequencer, Platform and Client guides.

Note: The SoftGrid Virtual Application Server (VAS) is generally referred to as the Server in this guides.

This chapter describes the separate components and general operation of the SoftGrid system.

• For details and procedures related to administering applications and packages, go to Configuring Applications on page 17.

• For specifics on administering licenses, go to Configuring Application Licenses on page 25.

• For information on VASes and their server groups, go to Configuring Virtual Application Servers on page 37.

• For procedures on creating and managing Provider Policies, go to Configuring Provider Policies on page 43.

• For details on account authorities and credentials, go to Configuring Account Authorities on page 47.

• For management of the data store, user sessions, server logs, and reports, go to Managing the SoftGrid Platform on page 51.

• For troubleshooting and error messages, see Troubleshooting and Messages on page 63.

PrerequisitesTo administer the SoftGrid Platform, it is important that you understand Microsoft network and database technologies, and Softricity-specific technologies. You should:

• Be an experienced network administrator.• Be comfortable working with MSDE or SQL databases.• Have completed current SoftGrid Platform Administration training.


Platform Concepts Administrator’s Guide

Note: If you completed SoftGrid training for an earlier version of the Platform, we strongly recommend that you take the Update training course for SoftGrid v4.0.

Platform ConceptsThe SoftGrid Platform delivers virtualized Windows applications to specified users. This system looks and works the same as traditional per-computer applications as far as users are concerned. To those who configure and administrate SoftGrid, virtualized applications differ greatly from traditional software deployment.

Among the key SoftGrid concepts and components are:

SoftGrid Virtual Application Server (VAS)

Streams your SoftGrid-enabled applications to SoftGrid Clients installed on user’s desktop machines, terminal servers or laptops.

SoftGrid Client The only software required for access to your SoftGrid-enabled applications is the SoftGrid Client. This single application, installed on your users’ computers, enables the streamed applications to launch on the user’s computer in the same manner in which they would launch a locally installed version of the application. This client can be installed on any Windows-desktop or terminal-services machine.

SoftGrid Sequencer The SoftGrid Sequencer is used to convert Windows applications in preparation for streaming from a VAS. You can sequence an application individually or as part of a suite or package of interdependent applications.

SoftGrid Management Web Service

This service facilitates communication between the SoftGrid Management Console and Data Store. It accesses Active Directory or the NT Domain Controller to authorize each SoftGrid user. Upon authorization, it presents the appropriate data to the Console for administration.

SoftGrid Management Console

A snapin to the Microsoft Management Console, this tool is the primary interface by which the SoftGrid administrator adds, configuresing, updates, replaces or removes applications from the SoftGrid Platform. You can also configure user access and application licenses, as well as generate usage reports.

SoftGrid Data Store This houses the SoftGrid environment information, including VAS configuration, streamed application records, and licensing, reporting and server logging data.

Virtual Environment

While your users launch and use their programs as they always have, the applications and their configurations are actually centrally located on a server or group of servers that delivers them on demand. As administrator, you configure applications centrally for all users. You can also designate which users may have access to which applications.

The virtualization of applications shifts your emphasis from the need to visit each individual computer in order to provide your users with the applications that they require to a centralized method of distribution. You will also have the added benefit that with streamed applications running in virtual environments on users’ computers, none of these applications will conflict with any other streamed applications or those which are locally installed.

Thus, your users are able to run multiple versions of a given application. For example, to maintain compatibility with different database files, they may need to open each with a different version of a the same database application. It would be impossible to


Administrator’s Guide Platform Concepts

install more than one version locally, but multiple versions can be streamed, as each has its own virtual environment which will not cause conflicts with other versions.

Central Control and Updates

Unlike traditional per-computer application installation, with the SoftGrid Platform you sequence and configure your applications one time for the Server(s), not individually for each user’s machine. In the same way, you need only patch or provide a version update once, yet it will be distributed to all designated users without the need for individual desktop visits.

The SoftGrid administrator designates which applications are available to users, which users can access each application, and how these shortcuts for these applications appear and work on client desktops and laptops. At any time, the SoftGrid administrator can centrally add, re-configure or remove streamed applications.

If you are enforcing application licensing, this can also be administered centrally. You can monitor your application licensing enforcement through reports which can be generated via the SoftGrid Management Console. You can specifically limit licenses to named users, user groups or set the number of concurrent users.

Figure 1: SoftGrid Platform Components.

The SoftGrid Platform’s purpose is to deliver Windows-compatible applications, singly or in suites, to desktops, laptops or terminal servers in the enterprise and to manage them from a central location.

A number of SoftGrid software components have been designed to work together with Microsoft and third-party software components to achieve this purpose.

This section describes how these software components interact. The following figure highlights the SoftGrid Platform’s application-delivery components.



.Figure 2: The SoftGrid System

Although the SoftGrid Platform is a complex system, you will find it relatively easy to install, configure and manage.

SoftGrid application virtualization significantly differs from traditional deployment. So, it is a good idea to take some time to consider how streamed applications are prepared and delivered. This will enable you to plan your own successful SoftGrid installation.

Delivering applications

The SoftGrid Platform delivers an application to a userwhen:

• The application has been packaged using a SoftGrid Sequencer• The resulting Package has been copied to the content directory of a SoftGrid

VAS• Optionally, the initializing (.osd) and icon (.ico) files associated with the

SoftGrid-ready package file have been copied to an HTTP Server• A reference to the application has been entered into the SoftGrid Data Store

by importing or adding the application package via the SoftGrid Management Console and

• The application’s initializing (.osd) file has been activated at Client computers in order to stream and launch the packaged application

Installing and configuration

Your role as SoftGrid administrator includes configuring the SoftGrid Platform to meet the needs of your organization and its users. You configure the SoftGrid Platform during and after installation of its components.



During installation, you can configure a basic, minimal SoftGrid Platform when you choose Typical in the installation wizard. You might use this for a test environment or a small installation.

The installation wizard will lead you through:

• Assigning an Active Directory or NT4 Domain Controller to authenticate the various account-based transactions that can occur within the SoftGrid Platform

• Choosing or adding a database program whose data store will hold the SoftGrid Platform schema and configurations

• Specifying a Server Group for the default VAS being installed• Designating the content directory, a location on the VAS where SoftGrid-

enabled applications are stored for streamingOnce you have created SoftGrid-enabled applications using the Sequencer, those packages are copied to the content directory of the VAS. Using the SoftGrid Management Console, you publish the sequenced package by importing or adding it, which places the records of this application package in the SoftGrid Data Store. Finally, you install the SoftGrid client on each computer on which your users will be streaming applications.

If you are at the proof-of-concept stage in adopting the SoftGrid Platform, you can install most SoftGrid Platform components on the same computer.

Note: You should not install a SoftGrid Client and Server on the same computer. The SoftGrid Sequencer should be installed on a separate machine as well, ideally on a virtual machine.

Production environments

The SoftGrid Platform Installer also lets you designate which software components of the SoftGrid Platform to install on a given computer. By choosing Custom installation, you create combinations of components appropriate to your production environment.

For example, you can install a SoftGrid Data Store on one computer, a SoftGrid Management Console and the SoftGrid Management Web Service on another and the SoftGridVirtual Application Server on still other machine(s). You can install the SoftGrid VAS on as many computers as demand warrants, as described in the following section.

The SoftGrid Client is the only component of the SoftGrid system which should be installed on your users’ computers. To ensure optimum operation, only one version of the SoftGrid Client should be installed on any user computer. The SoftGrid Sequencer is essential to the Platform, but is an external component. The Sequencer should be installed on a stand-alone machine. For convenience and efficiency, a virtual machine is highly recommended. The resulting SoftGrid-enabled files should be copied to the content directory of to the Server in preparation for application streaming.

The Windows Desktop and Terminal Servers Client, and Sequencer each have their own installers.

Recurring components The number of user sessions which your SoftGrid Platform needs to support at any one time determines how many VASes you should install. As a general rule, a VAS installed on a Microsoft Windows 2003 Server or Advanced Server or XP computer equipped with a single CPU and 512 MB of memory (the recommended minimum) supports 300 simultaneous user sessions. This is the same for both Desktop and Terminal Server Clients.



Each Server Group in the SoftGrid Platform should have at least two Servers. It is strongly recommended that you onfigure these machines for load balancing, for fault tolerance and for aggregation and grooming of application requests.

More than one SoftGrid Management Console can be running in the SoftGrid Platform on any Microsoft Windows 2000/XP/Server 2003 computer. The SoftGrid Management Console can run on the same computer running the SoftGrid Management Web Service, of which the SoftGrid Management Console is a client.

After installation, the SoftGrid Management Console enables you to:

• Specify SoftGrid-enabled applications that will be available to users, as well as how these applications can be accessed from the desktop

• Specify applications subject to licenses and specify the terms of these licenses

• Configure Servers added to a Server Group• Impose policies on particular User Groups that limit access to the SoftGrid

Platform’s applications or cause measurement of their use and• Generate various usage and error reports

The SoftGrid Management Console is your primary interface to the SoftGrid Platform.

Figure 3: SoftGrid and Active Directory or NT Domain Controller Relationships

Delivery components

Playing an essential role in the SoftGrid Platform’s delivery of applications are the following software components (each detailed in the following pages):

SoftGrid Sequencer Packages a Windows-compatible application into a single .sft file and creates all application-specific .osd and .ico files so the application is SoftGrid-enabled, that is, ready for streaming in the SoftGrid Platform.

SoftGrid Client Allows the user to launch any SoftGrid-enabled applications to which that user has access rights. The client also provides the means by which the user may be able to



fully load application(s) into their desktop cache, as well as customize their application shortcuts and File Type Associations. These more advanced features of the client will only be available to users who have been granted the appropriate level of privileges.

SoftGrid Virtual Application Server

Streams a SoftGrid-enabled application’s .sft file to a requesting SoftGrid Client, and provides a source of desktop configuration information based on the settings in the SoftGrid Management Console.

Desktop configuration information

Includes a global listing of SoftGrid-enabled applications, their File Type Associations, and the pathnames of their related .osd and optionally .ico files. A SoftGrid Client configures itself with this information upon successful execution of a desktop configuration (DC) refresh with the VAS.

SoftGrid Sequencer

The SoftGrid Sequencer operates separately from the other components of the SoftGrid Platform. It packages Windows-compatible applications so they can stream from SoftGrid Servers and launch on SoftGrid Client machines.

.

Figure 4: The SoftGrid Sequencer, with Optional HTTP Server

There are four types of files created when an application is sequenced (SoftGrid-enabled) using the SoftGrid Sequencer. Those file types are listed below:

• .sprj File – one per package• .sft File – one per package• .osd Files – one per application in each package• .ico Files – typically one per application in each package

Each of these file types is explained in detail below.

.sprj file Sequencing an application package produces a single .sprj file, regardless of how many applications may be included in the package. This file contains the history of an application package, and is necessary when re-opening a package in the Sequencer for patching or package upgrade. This file can also be used by the SoftGrid Management



Console to import an entire suite of applications at one time, rather than importing them singly using .osd files.

An .sprj file should be kept in the package folder and copied with all other package files to the content directory of the VAS from which it will be streamed.

.sft file Sequencing an application package produces a single .sft file, regardless of how many applications may be included in the package. This file contains not only an application’s component files, but also a record of files, directories, dependencies, initializations and registry settings that the SoftGrid Sequencer builds while monitoring the application’s installer and the launch of any applications in that package.

The .sft file may contain more than one stand-alone application or a suite of applications. These contents are divided into uniformly-sized blocks of unaltered source code and stored in a sequence that is optimized for streaming to a SoftGrid Client.

An .sft file should be kept in the package folder created during sequencing. This entire folder must be moved from the SoftGrid Sequencer to a network share, an FTP Server, or a CD-ROM from which it can be transferred to the Servers to stream this file and its contained applications to SoftGrid Clients. As this .sft file streams to a SoftGrid Client, the Client refers to its contained sequencing record to build the virtual runtime environment the contained application needs to launch and run.

.osd and .ico files Along with an .sft file, the SoftGrid Sequencer creates one or more associated .osd files and .ico files. Typically, each application in a package has its own .osd file and its own .ico file. The .osd files are placed by the Sequencer in the same folder as the .sprj and .sft files. The .ico files are all placed in a subdirectory of that folder by the Sequencer.

The .ico files are used by the SoftGrid Management Console to place an icon on the user’s desktop, Quick Launch bar or Start menu. If an icon is not available for any given application, the SoftGrid Platform will supply a generic icon.

When the user initiates a streaming request by double-clicking an icon or choosing the application from the Start menu, this accesses the XML-formatted .osd file, which contains specific information about the sequenced application and how its packaging has been implemented.

This includes any registry settings and environment variables that augment or otherwise override the virtual runtime environment the .sft file would have the SoftGrid Client create. An .osd file may also include scripts in the file or called by it that augment the .osd file’s actions or even further augment or otherwise override the virtual runtime environment the .sft file would have the SoftGrid Client create.

In practice, it is strongly recommended that the entire package folder be moved from the Sequencer to the content directory of the VAS from which you will stream the application(s). This will not only ensure that the entire package is available in one location for retrieval for subsequent package upgrade, but it will also facilitate the importation of applications via the SoftGrid Management Console. Importation may fail if any .osd or .ico files are missing.

Optionally you may choose to copy a duplicate set of the application’s .osd file and the .ico file to Servers or to a network share, an FTP Server, or a CD-ROM from which they can be transferred to an HTTP Server. You can also send these files to a SoftGrid user as an email attachment.



SoftGrid Client The Client issues a user’s request for a Windows-compatible application to a VAS. Once enough application information streams from the Server, the application runs on the user’s computer.

Figure 5: The SoftGrid Client .

Security and control A Server streams applications to the requesting SoftGrid Client over an RTP (Real Time Protocol) channel. Client and Server communicate over an RTSP (Real Time Streaming Protocol) channel to set up the streaming session and afterward over an RTCP (Real Time Control Protocol) channel. Streaming does not occur until the Client account requesting the application is authenticated and authorized, and before terms of the application’s license, if assigned, are met.

If an application is loaded in cache on the local machine after its initial streaming, the application will load from cache rather than be streamed, but not before the Server performs authentication and authorization and if necessary, a license assignment.

Virtual runtime environment

The Client creates a virtual environment in which to run the application it has requested. To do so, the Client refers to the .sft file’s launch information (cached locally after the first stream) and to the locally-cached .osd file associated with this application to determine what environment this application requires (if the application is part of a suite and other applications in the suite are running, the required environment will already have been created).

Having retrieved an .osd file from an HTTP Server, a network share or as an email attachment, the Client puts this .osd file into cache. The Client automatically updates the version of the .osd file it has in cache with the latest version on the Server. This occurs, for example, after a package has been opened for upgrading in the SoftGrid Sequencer and the new package has been copied to the content directory of the VAS.

Desktop icon The Client also retrieves the application’s .ico file, which it will also cache locally. This icon provides the user with a familiar a way to launch the application, typically through a desktop shortcut. This shortcut is associated with the requested application and the files it can open. Like the .osd file, the .ico file can be stored on and retrieved from an HTTP Server and/or network share. It can also be distributed as an email attachment.

Desktop configuration Opening a file without first launching its application requires an association between this file’s type and the application. You can go to each Client machine and configure it with the necessary File Type Associations. More conveniently, you can provide a standard set of File Type Associations via the desktop configuration settings for each application in the SoftGrid Management Console. Depending on the privileges you allow your users, they may also have the right to create additional File Type Associations for their own machine.



On user login or at a user’s command, the Client should find desktop configuration information on a VAS or an HTTP Server. This process is typically referred to as a desktop configuration (DC) refresh. This refresh sends the Client the desktop configuration which was set up via the SoftGrid Management Console. The DC refresh will return either the VAS version of this desktop configuration information, or that which you have created on your HTTP server. If you use an HTTP server, you create its desktop configuration version by listing applications, associated file types, and .osd/.ico pathnames in an XML-formatted file, then putting this file on your SoftGrid HTTP Server.

SoftGrid Clients in different modes

A computer which has both the SoftGrid for Window Desktops Client installed and the Microsoft RDP Client or the Citrix ICA Client installed can receive SoftGrid-enabled applications both from a VAS and from a SoftGrid for Terminal Servers Client installed on a terminal server. When in this mode, this is a a SoftGrid Dual Mode Client.

The Windows Desktops Client can run SoftGrid-enabled applications even disconnected from the SoftGrid Platform or its local network. In order to effectively use this Disconnected Operation (DO) mode, the user must first be authenticated to use an application by launching it while connected to the Server and have fully loaded it into cache. The user can then run any authenticated, fully loaded applications in this mode for the period that the administrator has configured through the SoftGrid Client snap-in or in the Registry for that client machine.

SoftGrid Virtual Application Server

The Server responds to requests from Clients by executing a DC refresh to provide desktop configuration information or by streaming a requested application’s .sft file.

The Server streams an .sft file over an RTP (Real Time Protocol) channel, all the while controlling this stream over RTCP (Real Time Control Protocol) and RTSP (Real Time Streaming Protocol) channels, and streams the desktop configuration information over the RTSP channel. The Server listens for requests on non-secure port 554 (default) and secure port 332 (default).

Figure 6: The SoftGrid Virtual Application Server.



Start-up configuration Application streaming does not occur until the Server receives its own start-up configuration from the SoftGrid Data Store over an ODBC connection. This configuration defines the Server’s performance characteristics and activities, as determined by settings regarding core processes, memory usage, and log behavior, for example. This configuration also defines the Server’s role in and relationships to the SoftGrid Platform, as determined by assignments pertaining to Server Groups and Provider Policies, for example.

By default, the Server communicates over an ADSI connection with a Domain Controller in its network before commencing an application-streaming session to Clients. This communication authenticates the account initiating this session against the network’s Active Directory or NT4 Domain. The Server also communicates over an ODBC connection with the Data Store. This communication determines whether the account is authorized for this session. It may also determine whether the requested application is subject to a license and if so, what restrictions apply and whether the Clients’ users meet those requirements.

When the desired logging level has been enabled, a Server also sends status and error information to the Data Store regarding use of the Server’s system resources and use of its applications and their licenses.

HTTP Server An HTTP Server can respond to requests from Clients for .osd and .ico files, and for desktop configuration information. This information can include a list of available applications and their locations, shortcuts for these applications and their locations, file types these applications can open, and icons to associate with these file types.

The SoftGrid HTTP server receives requests and transfer files over an HTTP connection and listens for these requests on port 80 (default).

Figure 7: Optional HTTP Server.



.osd, .ico files and desktop configuration

SoftGrid Sequencer-created .osd and .ico files must be transferred to the HTTP Server from a network share, an FTP Server or a CD-ROM. The .sprj and .sft files for any of these applications should be located in the content directory of the VAS.

Desktop configuration information on an HTTP Server must be created by listing applications, associated file types, and .osd/.ico pathnames in an XML-formatted file, which is then transferred to this HTTP Server.

Management Components

After installing and configuring the SoftGrid Platform for first use, you will probably wish to reconfigure the SoftGrid Platform from time to time. These modifications will be necessary to accommodate changes in the SoftGrid Platform’s equipment, available applications, licenses, and Server Group membership. You can also perform periodic maintenance.

Playing essential roles in the SoftGrid Platform’s management are the following software components:


Views, modifies, and creates records for Applications, Application Licenses, Servers, Provider Policies, and Account Authorities. It is in the SoftGrid Management Console that the SoftGrid Platform administrator will create reports of Server messaging and usage.


Validates records for Applications, Application Licenses, Servers, Provider Policies, and Account Authorities created in the SoftGrid Management Console; presents these records to the SoftGrid Data Store for storage and retrieval; and retrieves these records, as well as Server messages and usage information, for presentation to the SoftGrid Management Console for viewing and modification.

SoftGrid Data Store Stores records for Applications, Application Licenses, Servers, Provider Policies, and Account Authorities for retrieval by VASes and by the SoftGrid Management Web Service, and stores VAS messages and usage information for retrieval by the SoftGrid Management Web Service.

Active Directory/NT4 Domain Controller

Authenticates Client users and SoftGrid Platform Administrators as members of particular User Groups that have specific permissions.


The SoftGrid Management Console (highlighted in the following figure) is the primary interface by which you configure the SoftGrid Platform and generate reports about this configuration’s usage.

The SoftGrid Management Console communicates configurations over a .NET Remoting connection to and from the SoftGrid Management Web Service. The Console also obtains usage and error information from the Servers by the same path.



Figure 8: SoftGrid Management Console.

Configuration objects Through the Management Console, you can manage the Data Store’s:

• Records of SoftGrid-enabled applications that are physically available on Servers

• Records of licenses that restrict who can use these applications, and under what conditions

• Records of Servers and their grouping• Records of policies that restrict users’ application usage (through

authentication, authorization, and licensing requirements) or measure application usage (through a metering requirement)

• Records of the SoftGrid Platform’s account authoritiesReporting objects Through the Management Console, you can also create and generate the following

usage and other reports, provided that logging has been directed to the Data Store:

• Software Audit (includes a list of applications used over a selected period; top users; total and average users per application; cumulative minutes per application)

• License Compliance (includes number of application licenses against peak demand)

• Application Utilization (includes concurrent, average and peak sessions over selected period and minutes used for each session)

• Users Activity (includes sessions per application)• System Utilization (includes average number of sessions or users that a

specific Server, a Server Group, or all Servers supported per day, per day of week, and per hour of day; and the number of concurrent sessions or users per day)

• System Error (according to the selected log level, includes transaction messages, fatal error messages, error messages, warning messages, information messages, and all other messages)



• User/Group Application Configuration (Applications, FTAs, and shortcuts assigned to a user or user group)

MMC snapin The SoftGrid Management Console is a snapin to the Microsoft Management Console (MMC). It is part of the Platform installation, if selected in the installation wizard, and appears under Administrative Tools.


The SoftGrid Management Web Service (highlighted in the following figure) handles requests from the SoftGrid Management Console for access to configuration records and usage/error information kept in the SoftGrid Data Store.

The HTTP Server running the SoftGrid Management Web Service transacts these requests over a .NET Remoting connection, and listens for these requests on non-secure port 80 (default) and secure port 443 (default). The SoftGrid Management Web Service relies on a .NET Remoting connection. So, the Microsoft Windows 2000 Server, 2000 Advanced Server, or Server 2003 computer on which the Web Service runs must have the .NET Framework installed. This computer must also have Microsoft IIS (Internet Information Services) installed and enabled.

Figure 9: SoftGrid Management Web Service.

Information flow The SoftGrid Management Web Service presents requested configuration records and requested usage/error information it has retrieved from the Data Store to the Management Console for viewing, editing, or deletion, and for report generation.

It also validates configuration data received from the Management Console to assure the data will conform to the Data Store’s schema. The Web Service then forwards this validated data to the Data Store.

Security Before the SoftGrid Management Console can even commence a configuration or reporting session with the SoftGrid Management Web Service, this Service must communicate over an ADSI connection with a Domain Controller in your network. This communication authenticates the account initiating this configuration session against the network’s Active Directory or NT4 Domain. This Service then communicates with the SoftGrid Data Store to confirm the account is authorized for this configuration session.

SoftGrid Data Store

The SoftGrid Data Store houses the Platform’s configuration records, which are created in the Management Console. It also keeps usage data conveyed to it from Servers as a result of their interaction with Clients. The Data Store resides in an ODBC-compliant database system.



We support and recommend the Microsoft SQL Server. In its absence, we supply MSDE 2000 (Microsoft SQL Server 2000 Desktop Engine) for installation on a Microsoft Windows 2000/XP computer.

The Data Store presents a start-up configuration to a requesting Server. It also confirms that a Client requesting an application from a Server is authorized to make this request. Then, it determines whether the requested application is subject to a license and, if so, what restrictions should apply. It you have configured a logging level, the Data Store can also log a Server’s usage and error information.

The database system housing the Data Store transacts these requests over an ODBC connection and listens for them typically on port 1433 (for Microsoft SQL Server and MSDE).

Figure 10: SoftGrid Data Store.

Configuration records and reports

The Data Store also receives configuration records through the validating SoftGrid Management Web Service from a Management Console and can send these records back to the Management Console at its request. These SoftGrid Platform configuration records can pertain to Applications, Application Licenses, Server Groups, Provider Policies and Account Authorities.

The Data Store can also supply a requesting Management Console (through the SoftGrid Management Web Service) or third-party Report Generator with information showing, for example, how individual Servers, Server Groups, applications and application licenses on the SoftGrid Platform have been used over selectable periods.

The database system housing the Data Store transacts these requests over an OLE DB or ODBC connection and listens for them typically on port 1433 for Microsoft SQL Server and MSDE.

Domain Controller An Active Directory/NT4 Domain Controller responds to a variety of requests from SoftGrid Platform components. You must have already configured the controller to recognize valid user accounts and their group memberships.

The Domain Controller responds to these requests over an ADSI (Active Directory Services Interface) connection and listens for them on port 389 by default.


Beyond this Guide Administrator’s Guide

The Domain Controller acts on requests from Servers to authenticate Client accounts so that these Servers can stream SoftGrid-enabled applications to these Clients. It acts on requests from the SoftGrid Management Web Service to authenticate Management Console accounts so that you can configure the SoftGrid Platform.

Figure 11: The Active Directory/NT4 Domain Controller .

Beyond this GuideIf you have not already installed the SoftGrid Platform, you can find planning and initial configuration instructions in the components’ installation guides.

If your adoption of SoftGrid is still at the proof-of-concept or pilot stage, start with the Quick Start Guide.

Other documents The following online documents support this release:

Softricity SoftGrid Platform v4.0 Quick Start Guide. Leads you through a tutorial on installing the Platform, Client and Sequencer and performing the basic SoftGrid operations in a test environment.

Installing the SoftGrid Sequencer v4.0. Provides hardware, software and network specifications for the SoftGrid Sequencer.

Installing the SoftGrid Components v4.0. Provides hardware, software and network specifications for the SoftGrid Platform. This includes the VAS, Management Web Service, Data Store, and Management Console snapin.

Installing the SoftGrid Client v4.0. Provides hardware and software requirements for both the Universal Desktop and Terminal Server Clients.

SoftGrid Sequencer User’s Guide. Includes descriptions of and instructions for Sequencer operations.

In addition, release notes for the Platform and for the Sequencer include fixed and known issues, as well as other details not available when this guide was last updated.


Administrator’s Guide Beyond this Guide

Knowledgebase The Support section of Softricity’s Web site (www.softricity.com) is home to the Softricity Knowledgebase. Here you can obtain procedures to work around unusual problems and error messages. Here, with the appropriate login credentials, you can also submit product questions and trouble tickets.

Customer Support Center

The Support section of Softricity’s Web site (www.softricity.com) is also home to the Customer Support Center (CSC). Here, with the appropriate login credentials, you can obtain not only SoftGrid software, but also the release notes that supplement this software and associated task-oriented manuals (also sourced here). In the CSC you can access a more technical version of the Softricity Knowledgebase.

If you do not have appropriate login credentials, in most cases, you will have obtained SoftGrid software and associated documentation through a Softricity partner. This partner will also be an important SoftGrid information resource.


http://www.softricity.com

http://www.softricity.com

Beyond this Guide Administrator’s Guide


Admnistrator’s Guide Overview

Chapter 2

Configuring Applications

OverviewAfter you acquire a paqckage with its SoftGrid-enabled applications, you need to move the package files to the appropriate locations on the SoftGrid Virtual Application Servers. Then you can configure and fine-tune each application. This section also describes how you can :

• Import an application to the Servers• Determine which user groups can access a suite• Define an application’s file-type associations (FTAs)• Choose where the application’s shortcuts appear• Disable an application from streaming from the Servers

You can also set and change an application’s license and usage reporting. See Configuring Application Licenses on page 27 for procedures and options.

After the initial setup of your SoftGrid-enabled applications and each time you add an application afterward, you can perform some or all configuration procedures.

Note: Throughout this guide, Server refers to a SoftGrid Virtual Application Server or a SoftGrid HTTP Server. Active Directory refers as well to NT Domain Controller. Also Client and Management Console refer respectively to the SoftGrid Client and SoftGrid Management Console.

Initial Setup As detailed in the SoftGrid installation and Sequencer guides, you should begin using your SoftGrid Platform with SoftGrid-enabled applications.

As administrator, you define who can access the applications. You can change this by reconfiguring the applications through the SoftGrid Server Management Console.

Essential to the permissions and licensing is the SoftGrid Platform interaction with Active Directory or NT Domain Controllers. Your configuration includes choosing user groups for applications and licenses.

Note: Many organizations employ existing User Groups for their SoftGrid implementation.

Your configuration enables Clients on your users’ computers to access SoftGrid-enabled applications from the Servers. You must have properly authorized the access by identifying the User Groups with packages.

The Management Console is the tool for editing a package’s properties. For example, for existing applications, you may want to provide access to a new User Group. You may also decide to control and track licensing for reporting.

Before you start:

1. Copy the sequenced application’s package files into subfolders of the /content folder of each Server. Include its .sprj, .sft, .osd, and .ico files.


Import an Application Administrator’s Guide

2. Know the correct UNC or HTTP paths to the .osd and .ico files of all target Servers.

Import an ApplicationTo make a SoftGrid-enabled application available for streaming from a Server, import it through the Management Console.

Import For each Server you want to make an application available to users:

1. From Administrative Tools, launch the SoftGrid Management Console and connect to the Server.

2. In the left pane, right-click on the Server’s Applications container or on an Applications Group under this container where you want to add applications.

You can choose New Application Group if you want to add one before importing the application.

3. Select Import Applications.

4. Locate the SPRJ file that corresponds to the application you want to import.

5. To import the application with all its related files, in the Open dialog and click Open.

You can enter a Description and choose the Application License Group and Server Group, if you have set up these.

6. Click Next to display the Shortcuts dialog and select where the users’ Clients will publish the application’s shortcuts.

7. Click Next.

8. In the next window, click Add to grant access to a a User Group.

9. In the Add/Edit User Group dialog, select the User Groups whom you want to access this application.

Repeat steps 8 and 9 until you have added all the desired User Groups.

10. Click Next and review the Summary dialog.

11. Click Finish.

Application User GroupsWhen you import an application as described above, you must grant access permission to one or more User Groups for anyone to use it. You can change that access anytime through the SoftGrid Management Console.

You might change User Groups who can access an application when you have:

• Added or deleted groups in Active Directory.• Changed the membership of the User Group you originally granted access to

the application.


Admnistrator’s Guide Application License Groups

• Added or changed which User Groups have licenses to access the application.

• Decided to expand which User Groups can access the application.• Tested the application with one User Group and want to include others.

Changing User Groups

1. From Administrative Tools, launch the SoftGrid Management Console.

2. In the left pane, expand the Applications container and if appropriate its applications group.

3. Right-click the package to change and choose Properties.

4. In the Properties dialog, click the Access Permissions tab.

5. Either click Add or highlight an existing User Group and click Edit.

6. In the Add/Edit User Group dialog, select the User Group.User Considerations If you remove User Groups from access to an application, existing users may lose

access to files they have created with the affected application. You should warn users in those groups before making the changes.

After you remove a User Group, its members lose the shortcuts and any personal settings for the application. This happens the next time they perform a DC Refresh.

Application License GroupsYou can associate a license group with an application or change licenses anytime through the Management Console.

If you decide to enforce licensing for one or more applications:

• Verify that the Provider Policy includes enforcement in its configuration• Configure or create licenses to apply to the applications.

For details on these procedures, see Configuring Application Licenses on page 27.

Important: If the Provider Policy enforces application licensing on a User Group, the application must have an associated Application License Group. If not, the Server does not permit access to the application by members of that group.

Steps overview. Right-click on the application and choose Properties. Add or change licenses from the Application License Group drop-down list.

Change an Application License Group


2. Expand the Applications container in the left pane.

3. In the right pane, right-click on the application to change and choose Properties.

4. In the Properties dialog General tab, click the Application License Group drop-down list and choose the appropriate item.

5. Click Apply.

Your changes take effect when a user next launches this application.


Application Shortcuts Administrator’s Guide

Application ShortcutsWhen sequencing a SoftGrid-enabled application or importing it to a Server, you specify where users see the shortcuts on their computers. You can change this anytime through the Management Console.

These shortcuts appear to users like Windows applications icons and Programs menu items. Selecting or double-clicking them launches the associated SoftGrid-enabled application.

You can choose up to four locations for the Client to publish the shortcut on each computer. Your settings affect all Users with access to this application. Whenever the Client loads on a computer, it publishes to these locations.

Important: For the Clients to publish the shortcuts, the application’s Provider Policy must use the default management setting. To check this, right-click on the Provider Policy and on its General tab, make sure that Manage client desktop using the Management Console is checked.

Changing Shortcuts

Steps overview. Right-click on the application and choose Properties. Add or change shortcuts in the Shortcuts tab.




4. In the Properties dialog Shortcuts tab, click any combination of the four publication options.

• Publish to User’s Desktop displays the shortcut.• Publish to User’s Quick Launch Toolbar.• Publish to User’s Send To Menu adds the shortcut to the Send To menu that

pops up on right-clicking a file that is associated with the application.• Publish to User’s Start Menu inserts the application’s shortcut in the main

Start menu or any submenu you enter or choose below that shortcut choice.5. After you make your choices, click Apply, then OK.

Your changes take effect when the user refreshes the Desktop Configuration.

File Type AssociationsYou can change File Type Associations (FTAs) to ensure that the users’ Clients launch the designated SoftGrid-enabled application when the users double-click files with the identified extension. This procedure discusses actions and considerations needed to change an application’s association with the files it can open.

If users do not have these FTAs, their Clients need to know which application can open a file. In such cases, they can right-click on a file and use the Windows Open with command to select Softricity SoftGrid Client Tray. Alternately, they can launch the application first and then open the file from within it.


Admnistrator’s Guide Application Server Groups

Changing FTAs Steps overview. Right-click on the application and choose Properties. Add or change FTAs on the File Associations tab.




4. In the Properties dialog File Associations tab, you can:

• Click Add to display the New File Type Association dialog. Enter the FTA Extension, without a dot, in the form doc. Either fill in the Create a new file type with this description: box or click the Link this extension with an existing file type: button and choose a file type that already appears in the drop-down list. Click OK to add this FTA to the application.

• Highlight an existing FTA and click Remove to disassociate this application and FTA.When the confirmation dialog appears, click Yes.

• Highlight an existing FTA and click Edit to display the Edit File Type Association dialog. Under its General tab, you can edit the FTA description, choose a different application to open files with that extension, or browse to a different .ico path.On its Advanced tab, you can highlight an existing action and click Edit to modify the action the Client takes when it launches this application. Also, if you know all the related information for an action, you can click New and specify the details. When you finish editing or editing an action, click OK on the Add/Edit Action dialog and then on the Edit File Type Association dialog.

5. After you make all your choices and edits, click OK.

Your changes take effect when the user logs into the Client or refreshes the Desktop Configuration.

Application Server GroupsIt is rare for an administrator to change Server Groups for an application. You might do this if you have created a new Provider Policy to apply licensing or authorization differently from the default Provider Policy. The Provider Policy applies to a Server Group, not to an individual SoftGrid Server. So, associating an application with a new Server Group lets you enforce a different Provider Policy.

Note: We recommend that all Servers in a Server Group have the same .sft files.

Before you change an application’s Server Group:

• You must have created the application record on the Server• You must have created the Server Group

Changing Server Groups

Steps overview. Right-click on the application and choose Properties. Change Server Groups from the drop-down Server Group list at the bottom of the General tab.



Removing Applications Administrator’s Guide



4. In the Properties dialog General tab, click on the drop-down list of the Server Group at the bottom of the dialog, and select the group you want.

5. After you make your selection, click OK.

Your changes take effect immediately. The SoftGrid Platform enforces any Provider Policy differences when the Client launches applications next.

Removing ApplicationsWhen you want to remove an application from streaming from one or more Servers, the procedure is simple. However, doing this affects all users with access to the application.

User considerations Connected users. For users currently logged into your network who are accessing a SoftGrid-enabled application, removing the application from the Server does not immediately disrupt their usage. They continue to use the application and all its features of any application for which they are authenticated and have cached.

When a user exits a SoftGrid-enabled application and you have removed it through the Management Console, the user cannot launch it again. In addition, if Desktop Configuration refreshes when the user logs in again or at a pre-set time, the shortcuts for the deleted application no longer appear.

Remote users. For users who have been authenticated for a SoftGrid-enabled application and then use it on a laptop disconnected from the network, they can continue to launch and use it until they reconnect to the network. When they reconnect, the Server recognizes that the application no longer exists and denies access.

All users. When you remove an application, notify its users first. Users who will lose access to an application through its removal from the SoftGrid Platform need ample notice because they will no longer be able to open the files they created with this application on the Client.

The SoftGrid Platform does not delete orphaned files. These remain where users have saved or moved them.

Depending on the application, when you warn users about an application you will delete, they may have the option from the application of saving their related files in a format that another application can open. Alternately, if they have other applications from a Server or installed locally that are compatible with the application’s file format, they can choose to open those files with them. In such cases, they can associate the file type with the other application. As administrator, you can also associate the FTAs with other compatible applications on the Servers.

Delete an Application

Steps overview. Right-click on the application. Choose Delete. Then confirm by clicking Yes in the warning window.



3. Right-click on the application to remove and choose Delete.


Admnistrator’s Guide Removing Applications

4. In the warning dialog, click Yes to confirm deletion.

Your changes take effect immediately. See the User Considerations above.

After you remove the application from the Management Console, you should manually delete its package, including .sft, .osd, .ico and .sprj files from each of those Servers. You should remove all applications in the package, all records for its versions and the record of the package from the database.

Important:


Removing Applications Administrator’s Guide



Chapter 3

Configuring Application Licenses

OverviewThe SoftGrid Platform gives you control over application licensing. You can configure application licenses:

• To track User Group access for reporting and compliance• To create Unlimited, Concurrent, or Named licenses per application• To use reporting for compliance records or for determining how many of

your users actually access an application, so that you can purchase the proper licensing level

• To enforce licensing per application packageOnce you have created licenses, you can:

• Set or change one’s expiration date• Configure its warning notice timing to users• Assign the license to a different application• Enable or disable a license• Remove a license• Change the number of users for a concurrent license• Change a named license’s users

The licenses you create appear in the SoftGrid Data Store. If you are enforcing licenses, the servers check for an available package license. When a license is available, the application launches. If not, the user receives a Launch failed message, informing them a license is not available.

Enforcing a license of any type also provides additional reporting capabilities. For details, see Reporting on page 57 and more specifically License Compliance Reports on page 60.

License GroupsTo control licenses for SoftGrid-enabled applications, you create one or more Application License Groups. Applications are associated with license groups; each application is assigned to a single license group in the applications Properties dialog. These licenses are not application-specific and you can apply them to multiple applications.

If you need to change the license associated with an application, you can do this through the Management Console. See Change an Application License Group on page 21 for this procedure.


License Groups Administrator’s Guide

Note: You can use Application Licence Groups to enforce licenses by number allowed concurrently or by named users. However, you do not need to do either to monitor license usage and keep compliance records. See the reporting sections of Managing the SoftGrid Platform on page 53 for reporting options and procedures.

Application License Groups appear in the left pane of the Management Console in the Application Licenses container. When you first install and configure a server, this container is empty, meaning there are no Application License Groups yet.

What you want to accomplish with licensing determines which type of license you create for a package. When you have Application License Groups, you associate applications with them through the applications’ Properties dialog.

The license types are:

Unlimited License. Any number of users can simultaneously access the application. This does not require a stored license key in the Application License Group.

Concurrent License. This type enforces licensing by limiting the number of simultaneous users. When all available licenses are in use, the Server denies additional users access until a license is freed by a user exiting all applications in the package. You can configure the number of users and the date the license expires. You can also record a license key for your informational purposes with this type of license.

Named License. This type enforces licensing by limiting licenses to named users on your network. You specify the users who can access the application. You can also record a license key for your informational purposes with this type of license.

You can also create a Named License for all potential users. A License Group has a number of licenses associated with the group. Then within that License Group, create a Concurrent License that limits the number who can access the application to the maximum licenses available. When a user attempts to launch an application, the server retrieves all License Groups associated with any application in the requested package. The server then tries each license until it finds an available license and assigns the license to the user who requested the application.

Note: Named Licenses permit, but do not require, a license key per user. When you add a user or bring up that user’s Properties, you can enter and apply the key. This information is then available in the related license record for that user, but the Server does not use it for authentication or activation.

Licensing and Reporting

Applications that require activation per computer with their registration keys are not suited for SoftGrid enabling. An enterprise or multi-user license is appropriate. You can use SoftGrid license enforcement to limit access or to verify license compliance through SoftGrid reporting.

Instead of license limitations, you can measure usage and conformity to license requirements through SoftGrid’s reporting features. For details and procedures, see Reporting on page 57.

Reporting is a more manual process. However, it lets you develop records as needed to show license compliance.

You can also use reporting to adjust the number of licenses you need. For example, a report on a single application may reveal that fewer of your users than you expect


Admnistrator’s Guide Unlimited Licenses

access the application simultaneously. Depending on the vendor’s license agreement, this may allow you to decrease the number you purchase and maintain.

The following procedures describe the license and license-group types, and how to configure and use them.

Unlimited LicensesYou can create an Unlimited License Group to give any number of users simultaneous access to an application. You may do this when you have an enterprise license and do not need to measure usage for license compliance. It is also useful when you what to measure how many licenses you need to purchase or whether the number of licenses you have is too many or too few.

After you set up an Unlimited License, use SoftGrid Reporting to evaluate usage. For details, see System Error Reports on page 61.

Create an Unlimited License

Steps overview. Right-click on Application Licenses, choose New Unlimited License. and follow the steps in the wizard. Then open the application’s Properties and associate the application with the license.


2. Right-click on the Application Licenses container in the left pane and choose New Named License.

3. In the New Unlimited License Wizard, enter a name for it in the Application License Group Name box.

Optionally, check the Expiration Date box and then click the date arrows to specify the date. When you set the date, this activates the user warning for license expiration.

4. Click Next.

5. In the Named License User window, click Add and select a user to associate with the license in the Add/Edit License User dialog.

Optionally, you can enter a license key for informational purposes.

6. Click Finish.

Important: Even if you have chosen Enabled, the Server does not enforce the licensing until you assign a Provider Policy to it that does so.

To configure a Provider Policy to enforce licensing:

1. In the left pane, select Provider Policies.

2. Right-click on a listed Provider Policy and select Properties. (If you need to create one for this license, follow the procedures in Add Provider Policy on page 45.)

3. On the Properties dialog Provider Pipeline tab, check the Licensing box and from the drop-down list, choose Enforce License Policy.

4. Click Apply,

5. Click OK.


Unlimited Licenses Administrator’s Guide

6. Restart the SoftGrid Virtual APplication Server service on all Servers in the group to begin license enforcement.

Unlimited Licenses and Suites

Some previous versions of the SoftGrid Platform permitted copying and renaming an .sft file to allow multiple versions of an application to reside on one Server. If you want to associate an application with more than one License Group, you should sequence it again and give it a different name from the existing one. Then you can import the application and treat it as different in terms of licensing and user access.

Adding or Removing a License Group

Association

Steps overview. You can add or remove a Applications License Group association from a single application in a suite. Do this through the application’s Properties. On the General tab, select the group or <None>. Click OK and then save the changes.


2. In the left pane, click Applications.

3. In the right pane, click the Application License column heading to sort by license name.

4. For each application associated with the license you want to control, you can remove the association by right-clicking the application and choosing Properties. Then in the Application License Group’s General tab, select <None> Application License Group drop-down list. Apply this setting by clicking OK. This takes effect immediately.

To add an association with a Suite’s application or to change its association, use the same process. Right-click on the association and choose Properties. On the Application General tab, select the group from the Application License Group drop-down menu. Click OK to apply. This takes effect immediately.

License Expiration Warning

If you enforce licenses, you should set the license expiration and may want to record when the current license expires. When a license is set to expire, the Server can notify users before this happens. You can set this warning from 1 to 100 minutes.

When a license expires, the Server does not allow users to access the application. When they try to launch it, they see the same notice as they would if the number of license had reached its maximum.

The Client shuts down an application when the user’s license expires and the user cannot launch it again.

Disconnected users who are authenticated for applications and have cached these on their laptops can continue to use the applications. When they reconnect to the network and attempt to launch the applications, the Server attempts to authenticate them and denies them access to applications whose license have expired.

Setting License Expiration Warning

Steps overview. To set the period for License Expiration Warning, in the application license Properties dialog General tab, set the expiration time. Click Apply and save.


2. In the left pane, expand Application Licenses.

3. In the right pane, right-click the license you want to configure.

4. On the General tab, set the License Expiration Warning time. The range is 1 through 100 minutes.

5. Click Apply.

6. Click OK.


Admnistrator’s Guide Named Licenses

Named LicensesYou can grant access to an application to specific users through a Named License Group. This is useful for license compliance as well as for restricting application access without creating new User Groups in Active Directory.

When you use Named Licenses, only the individual users you add can access the application. The Server denies access to other users who attempt to launch the application.

Either when you create the license or in its Properties anytime, you have the option of entering a license key per user. This is for your records and not necessary for the users to access the application. A concurrent license provides first-come/first-served application access.

Named licenses can be more expensive to use than concurrent ones. If specific users must always have an application available to them, named licenses can ensure that while maintaining license compliance. If it is more important to have a certain number of licenses available at any given time, concurrent licenses are preferable. For details, see Concurrent Licenses on page 33.

Create a Named License and Group

Steps overview. Right-click on Application Licenses, choose New Named License and follow the steps in the wizard that appears.Then open the application’s Properties and associate the application with the license. If necessary, create a custom Provider Policy to enforce this licensing.

Important: You must use a Provider Policy to enforce the license if you want to limit its access to the specified users.


2. Right-click on the Application Licenses container in the left pane and choose New Named License.

3. In the New Named License Wizard, enter a name for the group. Provide a name for the associated license in the next wizard window. Optionally, you can change the warning time for license expiration (up to 100 minutes).

4. Click Next.

5. In the Named License window, enter a descriptive name for the license. If you are ready to provide user access to this application, make sure to check the Enabled box.

Optionally, you can check the Expiration Date box and then click the date arrows to specify the date. Setting the date activates the user warning for license expiration.

6. Click Next.

7. In the Named License User window, click Add and select a user to associate with the license from the Add/Edit License User dialog.

Optionally, enter a license key. Also, you can control per user whether to enable access to the application and when the license expires by toggling the Enabled and Expiration Date boxes.

8. When you have added all named users for this license, click Finish.


Named Licenses Administrator’s Guide

Important: Even though you have chosen Enabled, the Server does not enforce licensing until you assign a Provider Policy that does so.



2. Right click on a listed Provider Policy and select Properties. (If you need to create one for this license, follow the procedures in Add Provider Policy on page 45.)


4. Click Apply,

5. Click OK.

6. Restart the SoftGrid Virtual Application Server service to begin license enforcement.

Add Named Licenses to a Group

Once you create an Application License Group with any type of license, you can add additional Named Licenses as desired.

You might add a separate license for an administrator or user who must have access to an application. In such a case, you might have a set number of licenses available in a Concurrent License. Then, you can create a Named License in the same group specifically for the administrator or user.

Steps overview. Right-click on an Application License Group and choose New Named License. Follow the wizard to enter a description for the license and add users.


2. Expand the Applications Licenses container.

3. Right-click on an Application License Group that is not Unlimited and choose New Named License.

4. In the New Named License Wizard, enter a name for the group. Provide a name for the associated license in the next wizard window. Optionally, change the warning time for license expiration (from 1 through 100 minutes).

5. Click Next.

6. In the Named License User window, click Add and select a user to associate with the license in the Add/Edit License User dialog.

7. Optionally, enter a license key.

8. When you have added all the users, click Finish.

Important: Even if you have chosen Enabled, the SoftGrid Server does not enforce licensing until you assign a Provider Policy that does so.





Admnistrator’s Guide Concurrent Licenses


4. Click Apply,

5. Click OK.


Change Named Users

When the users who need access to an application with named licensing change, you can add or delete them from the license.

This procedure is only for an existing Named License. To create one, see Create a Named License and Group on page 31.

Steps overview. Click an Application License Group that is not Unlimited. Right-click on a Named License in the right pane and choose Properties. On the Users tab, highlight a user and click Edit or Remove. When you finish working, click OK.


2. Expand the Applications Licenses container.

3. In the left pane, expand Application License Group.

4. In the right pane, right-click on a Named License and choose Properties.

5. In the Properties dialog, click the Users tab.

6. In the Users tab, highlight a user and click Remove or Edit. The Remove choice immediately deletes the user from the license. Click Cancel if you do not want this change. The Edit choice brings up the Add/Edit License User dialog for that user. You can change users or enter a user’s license key.

On the same dialog, click Add to include additional named users. On the Add/Edit License User screen, select the user to associate with the license. Optionally, enter a license key.

7. When you finish your changes, click OK.

Concurrent LicensesUse a Concurrent License to limit the maximum number of simultaneous uses of an application. For example, if you have an expensive license for an accounting or drafting program, you can remain in compliance with the terms of the license by enforcing Concurrent Licenses.

These do not ensure an available license to a particular user. If you want to ensure that some users always have access to an application, add them as named users, as described in Create a Named License and Group on page 31.

Add a Concurrent License and Group

Steps overview. Right-click Application Licenses and choose Add New Concurrent License. Follow the wizard to enter a description for the license. In the application’s Properties, select this group in the Application License Group drop-down list. Click OK.



Concurrent Licenses Administrator’s Guide

2. Right-click on the Application Licenses container in the left pane and choose New Concurrent License.

3. In the New Concurrent License Wizard, enter a name for it in the Application License Group Name box.

Optionally, check the Expiration Date box and click the date arrows to specify the date. Setting the date activates the user warning for license expiration.

4. In the Concurrent License window, complete the License Description field with additional information.

Optionally, enter a registration key for informational purposes. You can also check the Expiration Date box and click the date arrows to specify the date. Setting the date activates the user warning for license expiration.

5. Set the Concurrent License Quantity by clicking its arrows.

Optionally, check the Enabled box for license enforcement.

6. Click Finish.






4. Click Apply,

5. Click OK.


Add Concurrent Licenses

This previous procedure created a Concurrent License Group. You can add additional Concurrent Licenses to this group. Adding these increases access to the application. Alternately, you can increase the number of users on the existing license.

If you have more than one license pack with different expiration dates, adding a different Concurrent License for each gives you control and provides accurate expiration notice.

Steps overview. Click Application Licenses and then click Application Licenses. Right-click an Applications Group and choose New Concurrent License. Follow the wizard, including setting the Concurrent License Quantity. .


2. In the left pane, click Application Licenses.

3. In the right pane, right-click on an Applications Group of any type other than Unlimited and choose New Concurrent License.

4. In the New Concurrent License Wizard, enter a name for it in the Application License Group Name box.


Admnistrator’s Guide Concurrent Licenses

Optionally, check the Expiration Date box and click the date arrows to specify the date. Setting this date activates the user warning for license expiration.

5. In the Concurrent License window, complete the License Description field with additional information.

Optionally, enter a registration key for informational purposes. You can also check the Expiration Date box and click the drop-down arrow to specify the date. Setting the date activates the user warning for license expiration.

6. Set the Concurrent License Quantity with the up and down arrows.

Optionally, check the Enabled box for license enforcement.

7. Click Finish.






4. Click Apply,

5. Click OK.


Change Concurrent Users

If your concurrent license terms change or you otherwise want to adjust the number of its users, do so in the license’s Properties. If you have measured usage in SoftGrid reporting and altered the terms of the license upon renewal, you should adjust the number of users.

Steps overview. In the Applications License container, right-click a Concurrent License and choose Properties. Set the license quantity and click OK.


2. In the left pane, expand Application Licenses.

3. In the right pane, right-click on a Concurrent License and choose Properties.

4. In the right pane, right-click on an Applications Group of any type other than Unlimited and choose New Concurrent License.

5. On the Properties dialog General tab, use the arrows for the Concurrent License Quantity to adjust the number of users.

6. Click OK.


Enabling and Disabling Licenses Administrator’s Guide

Enabling and Disabling LicensesSeveral circumstances can require disabling an application’s license. If you need to move a license from one Server to another, you can stop access to the application while you move it. Also, if the license terms change, you can stop access until you meet the new terms.

Note: The license remains available on the Client if the license was acquired before it was disabled.

If you enforce licensing, the Servers do not permit access to applications with disabled licenses.

Note: Before you disable a license, notify the application’s users. They need enough time to complete and save their work.

Steps overview. In the Applications License container, right-click a Concurrent License and choose Properties.Toggle the Enable box and click OK.



3. In the Applications License container, click on an Applications License Group.

4. In the right pane, right-click on a license and choose Properties.

5. On the Properties dialog General tab, clear the Enabled checkbox to disable the license.

To enable the license later, return to the license’s Properties and check the Enabled box.

6. Click OK.

Removing a LicenseIf you decide to stop using an application or to let its license lapse, you can remove it to prevent access. Also, you may remove a license if you find you can decrease the number of users who need access. In this case, you can provide access to a different license and remove the unneeded one.

Note: If users are accessing an application, the SoftGrid Server does not permit removing its license. Notify users and remove the license when no one is accessing the application.

You should notify the application’s users and provide adequate time for them to complete and save their work. If no other local or SoftGrid-enabled application is compatible with these files, they may be orphaned.

Steps overview. Right-click on the license and choose Delete. Confirm in the warning popup.




Admnistrator’s Guide Deleting an Application License

3. In the Applications License container, click on an Applications License Group.

4. In the right pane, right-click on the license to remove and choose Delete.

A warning window advises that deletion also removes usage information from the SoftGrid Data Store. It asks you to confirm deletion.

5. Click Yes. The deletion is immediate.

Note: If this removes all licenses for the application, you can also delete the application’s .sprj, .sft, .osd, and .ico files from the Server.

Deleting an Application License GroupYou can remove an entire Application License Group as well as individual licenses. Do this when you no longer use any of the licenses in the group.

You must remove the group’s licenses as in the above procedure before deleting the group. The Management Console does not permit deletion otherwise.

Also, if any applications are associated with the group, you need to remove the association before you can delete the group. Do this in the application’s Properties by choosing another group or <None> in the Application License Group drop-down list.

Steps overview. Right-click on the Application License Group and choose Delete. Confirm deletion in the warning popup.



3. In the Applications License container, right-click on an Applications License Group and choose Delete.

There is no warning screen. The deletion is immediate. Choose Cancel before saving to keep the group.


Deleting an Application License Group Administrator’s Guide



Chapter 4

Configuring Virtual Application Servers

OverviewOnce you install the SoftGrid Platform, including Virtual Application Servers, you can configure them. This includes:

• Creating Server Groups, each associated with Provider Policies that you can customize for its users.

• Choosing a Provider Policy to deliver, measure and collect data on applications and usage per your specifications.

• Adding or editing logging modules so that each Server Group provides the necessary management and troubleshooting information.

• Reconfiguring or removing Servers and Server Groups as needed.For details on managing and maintaining Servers after configuration, see Managing the SoftGrid Platform on page 53.

Server GroupsIn the Management Console, you create and use Server Groups to control and apply Provider Policy and Logging Properties. Your Server Group configuration applies to all Servers in the group.

The SoftGrid Platform includes Default Server Group in its installation. Unless you add other Server Groups, its Servers belong to this one. Also, they use the default Provider Policy.

You may not need to create additional groups or policies. However, if you have Servers in multiple sites or are delivering applications to disparate User Groups, you may want to apply different policies and logging configurations to various Servers.

Note: Server Group names can be up to 64 character long.

Add a Server Group

To apply different Provider Policies to different groups of users, you can add a new Server Group to facilitate this. For example, if you want one group of users to log into applications, you can enforce this in licensing through a Provider Policy. You can then use a different Server Group with a different Provider Policy for other users.

Steps overview. Right-click on a Server Group and choose New Server Group. Complete the New Server Group Wizard dialog.


Note: If you want to apply a new Provider Policy to this Server Group, set it up before adding the group. For details, see Add Provider Policy on page 45.

2. In the left pane, expand the Server Groups container.


Server Groups Administrator’s Guide

3. Right-click a Server Group and choose New Server Group.

4. In the New Server Group Wizard dialog, enter a meaningful name in the Server Group Name field.

5. Click on the arrow on the drop-down list to choose the group’s Provider Policy.

6. Leave the Enabled checkbox checked.

7. Click Finish.

You can now add one or more Servers to this group, as described below. All Servers in the group use the same Provider Policy.

Note: You must install the SoftGrid Virtual Application Server system on each Server before you can add it to a group. Also, you should create the appropriate Provider Policies before proceeding.

Add a Server to a Server Group

A Server Group requires one or more Servers. All Servers in a group use the same Provider Policy, including settings for which users can access its applications. Consider whether you want to enforce licensing and measure applications usage before you apply a policy to a group.

Steps overview. Right-click on a Server Group and choose New SoftGrid Virtual Application Server. Complete the New Server Wizard dialog.




3. Right-click a Server Group and choose New SoftGrid Virtual Application Server.

4. In the New Server Wizard dialog, enter a meaningful name in the Display Name field.

5. Enter the Server’s name in DNS Host Name field.

6. In the Max Memory Allocation (MB) field, you can accept the default (256MB of RAM) for the Server file cache or change it to up to 80% of the Server’s available RAM, minus approximately 512MB for the operating system.

7. In the Warn Memory Allocation (MB) field, you can accept the default (256MB of RAM) for the Server file low-memory warning trigger or change it to up to 80% of the Max Memory Allocation value in the field above it.

8. Click Finish.

The Server appears in the Server Group immediately. You can add more Servers or associate a Provider Policy with the group now. For details, see Apply Provider Policy on page 47.

Remove a Server Group

If you are taking a Server out of service, are replacing it with another Server or no longer want to apply a specific Provider Policy to that Server and its users, you can remove the Server from its Server Group.

To remove a Server from its group:



Admnistrator’s Guide Provider Policies


3. Click the Server’s group.

4. In the right pane, right-click on the Server and choose Delete.

5. In the warning popup about losing its usage information, click Yes.

The removal from the group is immediate.

Note: Removing the Server does not affect the contents of the Server’s drives, including its SoftGrid applications. However, any historical usage information for reports is no longer available from the SoftGrid Data Store.

Remove a Server from a Server Group

Similarly, if you no longer want to use a Server Group, you can remove it through the Management Console. The Group exists only in the SoftGrid Platform. So removing the group does not affect any of its Servers, other than removing them from the Management Console interface.

To remove a Server Group:



3. Right-click the Server Group you want to remove and choose Delete.

4. In the warning popup, confirm the removal by clicking Yes.

The removal of the group is immediate.

Note: This does not affect the contents of any of the Servers that were in the group. Also, removing the group does not remove the associated Provider Policy.

Provider PoliciesYou control the rules for users who access SoftGrid-enabled applications through Provider Policies. If you do not add and configure a custom policy, the Servers you add use the Default Provider policy. Creating, configuring and associating additional Provider Policies lets you deploy the applications to control licensing, logging, desktop refresh, and authentication per User Group.

For details on creating and configuring Provider Policies, see Configuring Provider Policies on page 45.

Change Provider Policy

If you have more than one Provider Policy, you can change which one applies to a Server Group through the Management Console.

Steps overview. Right-click on a Server Group and choose Properties. Select a Provider Policy on the General tab.



3. Right-click a Server Group and choose Properties.


Log Modules Administrator’s Guide

4. In the Properties dialog General tab, choose a Provider Policy from the drop-down list.

5. Verify that the Enabled checkbox has a check.

6. Click Apply.

7. In the restart pop-up, click OK.

8. On Properties, click OK.

9. Restart the SoftGrid Virtual Application Server service for the changes to take effect. Users already accessing the related applications see any policy changes when they next launch the applications.

Note: You can associate a Provider Policy with a specific application through its .osd file. We recommend making such associations in the OSD Editor in the SoftGrid Sequencer. See the SoftGrid Sequencer User’s Guide for details.

Important: Any changes you make to an .osd file after importing it into the Management Console have no effect. The contents of the .osd file enter into the database only once, upon importation.

Log ModulesYou can add, remove or change the log modules to control where the Server sends its logged messages. In the Provider Pipeline, you can also configure existing log modules.

Change Log Modules

Steps overview. Right-click on a Server Group and choose Properties. On the Properties Logging tab, select a module to remove or edit, or click Add to include a new module.





4. In the Server Group’s Properties dialog, choose the Logging tab.

5. On that tab:

• Click Add to display the Add/Edit Log Module dialog.• Highlight an existing module and click Edit to display the Add/Edit Log

Module dialog with setting for that module.• Highlight an existing module and click Remove to delete the module from

the Server Group’s Provider Pipeline. Removal is immediate. 6. In the Add/Edit Log Module dialog, you can click the Type drop-down list to

choose a module type.

Optionally you can check the Discard message after processing checkbox to activate this choice. Also, you can specify the log file in the Log File Name field.


Admnistrator’s Guide Log Modules

7. In the Event Type drop-down list, for File modules, you can select the logging level. The default is Warnings/Errors, which provides adequate reporting in most cases.

8. When you finish, click OK.

9. On the Properties dialog, click Apply. The changes take effect immediately and affect all Servers in the group.

Important: Increasing the logging level by choosing a higher Event Type can be useful for troubleshooting but can cause the SoftGrid Data Store or other databases where you store the logs to fill up rapidly. The default Warnings/Errors level provides essential reporting. Logging levels Verbose and Info/Warnings/Errors accumulate large amounts of data quickly.


Log Modules Administrator’s Guide



Chapter 5

Configuring Provider Policies

OverviewYou use the SoftGrid Provider Policy to create rules that Servers apply to users of SoftGrid-enabled applications. The Provider is the Server Group of one or more Virtual Application Servers. If you have specified a Provider Policy for that Server Group, its Servers use its rules for access.

Customizing the default policy is optional, as is creating additional policies. If you do not specify one, the Default Provider’s rules apply to connections. In many installations, that is adequate.

If you want to apply different access rules to various users or User Groups, you can create a Provider Policy to control:

• Client log levels sent to the Server log file• Client Desktop management, including FTAs and application shortcuts for

all Clients that access a Server• Desktop Refresh, for when the Client requests a refresh from the Server at

login or preset times• Authentication method for all the Server users• Anonymous User login account information• Usage metering, enabling logging of package and application user sessions

for reporting• Licensing by either auditing or enforcing license policies

The default and any custom Provider Policy you create configure access permissions in a Provider Pipeline. You see these settings in a key dialog in the wizard when you create a policy, as well as afterward in a policy’s Properties.

Add Provider PolicyYou can customize the default policy or add a new one. Multiple policies let you apply different polices to Server Groups for specific sets of users.

Steps overview. Right-click on Provider Policies and choose New Provider Policy. Complete the New Provider Policy Wizard dialogs.


2. In the left pane, right-click on Provider Policies and choose New Provider Policy.

3. In the Provider Policy Properties dialog:

• Enter a meaningful name (up to 64 characters) in the Policy Name box.


Add Provider Policy Administrator’s Guide

• In the SoftGrid Client log messages drop-down list, choose the level of error and informational messages for the Server to record in the SoftGrid Data Store.

• To be able to use the Management Console for applications associated with this policy, leave the check in the Manage client desktop using the Management Console checkbox.

• For automatic SoftGrid refresh on user login, leave the check in the Refresh desktop configuration when a user logs in checkbox.

• Optionally, to set specific times for desktop refresh, check the Refresh configuration every checkbox. Choose the time unit (days, hours, or minutes) from the drop-down list. Then enter a frequency in the range of 30 minutes to 999 days.

Note: You can use both refresh on login and a specific time or either one.

4. When you finish, click Next.

5. In the Add/Edit User Group dialog, navigate to the group and click OK.

6. In the Provider Pipeline dialog:

• Check the Authentication checkbox and use the drop-down list to choose Windows Authentication, Anonymous Authentication, or Basic Authentication. For details on these options, see Authentication Options on page 47.

• If you choose Anonymous Authentication, you can click Browse to navigate to an existing user or leave this box blank. Either way, enter the password twice.

• Check the Enforce Access Permissions Settings checkbox to have the Server authorize users according to the permissions in the applications’ Properties.

• Check the Log Usage Information checkbox to enable that the metering module in the policy’s Provider Pipe. This permits logging of user sessions for reporting on both applications and packages.

• Check the Licensing checkbox to enable the licensing module to grant and track licenses. Then from the drop-down list, choose either Audit License Usage Only to count licenses used but not to prevent access, or Enforce License Policies to permit access only when a valid license is available as well as to record usage.

Note: Enabling licensing for the Provider Pipeline is essential to enforce licensing, even if you have enabled it for the application or package on its Properties.

7. In the Properties dialog General tab of the desired Server Group, choose a Provider Policy from the drop-down list.

8. Verify that the Enabled box has a check.

9. Click Apply.

10. In the restart pop-up, click OK.


12. Restart the SoftGrid Virtual Application Server service for each server in the server group for the changes to take effect. Users already accessing the related applications see any policy changes when they next launch the applications.


Admnistrator’s Guide Apply Provider Policy

Note: You can associate a Provider Policy with a specific application by editing its .osd file. We recommend making such associations in the OSD Editor in the SoftGrid Sequencer. See the SoftGrid Sequencer User’s Guide for details.

Important: For changes to the .osd file to take effect, make them before importing the application package.

Authentication Options For every Server Group you associate with a Provider Policy, the Server enforces one of three type of authentication.

Windows Authentication. This is the default. The users’ login credentials pass to the Server, which permits access to applications if the users have permission.

Basic Authentication. The Server prompts each user for login credentials per application. A drawback is that passwords go over the network in clear text.

Anonymous Authentication. All users have the same listed account and can access every SoftGrid application. We do not recommend this method.

Important: We do not recommend clearing the Authentication checkbox on the Provider Pipeline dialog. Without authentication, the Server cannot enforce licensing, authorize users, deliver shortcuts to users’ desktops, or collect usage data. The only time unauthenticated delivery is appropriate is for applications delivered by Web Server or through an emailed .osd file.

Apply Provider PolicyIf you have more than one Provider Policy, you can change which applies to a Server Group through the Management Console. The policy’s configuration applies to all Servers in the group.

Steps overview. Right-click on a Server Group and choose Properties. Select a Provider Policy on the General tab.




4. In the Properties dialog General tab, choose a Provider Policy from the drop-down list.

5. Verify that the Enabled box has a check.

6. Click Apply.

7. In the restart pop-up window, click OK.


9. Restart the SoftGrid Virtual Application Server service for each server in the server group for the changes to take effect. Users already accessing the related applications see any policy changes when they next launch the applications.


Change Shortcut Management Administrator’s Guide

Note: You can associate a Provider Policy with a specific application through its .osd file. We recommend making such associations in the OSD Editor in the SoftGrid Sequencer. See the SoftGrid Sequencer User’s Guide for details.


Change Shortcut ManagementEach Provider Policy gives you the option of whether to control the placement of application shortcuts to the users’ desktops and menus. If you choose to manage them from the Management Console, when the Desktop Configuration refreshes, your shortcut settings take effect.

If you have more than one Provider Policy, you can change which applies to a Server Group through the Management Console. These settings apply to all Servers in the group.

In most cases, for SoftGrid-enabled applications, you should enable desktop management. However, if you use Microsoft Systems Management Server (SMS) to control applications, you may not want to publish the shortcuts via the Servers.

Steps overview. Right-click on a Provider Policy and choose Properties. Verify or toggle the checkbox for Manage client desktop using the Management Console.


2. In the left pane, expand the Provider Policies container.

3. In the right pane, right-click a policy and choose Properties.

4. On the Properties dialog General tab, verify or toggle the checkbox for Manage client desktop using the Management Console. There:

• Clear the box if you do not want to manage shortcuts through the Management Console.

• Check the box to have the Servers publish the shortcuts. When the box is checked, you can specify when and how often the Servers refresh configuration information.

5. After you make all your changes, click Apply.

6. Click OK.

7. Restart the SoftGrid Virtual Application Server service for the changes to take effect.

Note: If you want to verify or change where the Servers publish shortcuts, see Application Shortcuts on page 22.


Admnistrator’s Guide Change User Groups

Change User GroupsAnytime, you can change which user groups can access a Provider Policy’s associated applications. You might do this when you change a policy or create a new one with rules you want to apply to certain users.

Steps overview. Right-click on a Provider Policy and choose Properties. On the Group Assignment tab, select a group to remove or click Add to include another group. Apply your changes.




4. On the Properties dialog Group Assignment tab, you can:

• Click Add to include a User Group in the policy. Then in the Add/Edit User Group dialog, navigate to the group and click OK.

• Delete a group by highlighting it and clicking Remove. Deletion is immediate, but you can restore the group if you click Cancel before clicking OK.


6. Click OK.

The changes take effect immediately. Users who have launched applications can continue to use them even if their groups are not longer permitted access. However, they will not be able to launch them after they exit.

Change Authentication SettingsIf you decide to change a Server Group’s authentication method, set this in the Provider Policy the group uses. This affects all Servers in the group.

For descriptions of each type, see Authentication Options on page 47.

Steps overview. Right-click on a Provider Policy and choose Properties. On the Provider Pipeline tab, verify or change the Authentication settings at the top. Then apply the changes.




4. On the Properties dialog Provider Pipeline tab, you can:

• Clear the Authentication checkbox to turn off this function on the Server Groups using this policy.

• Enforce authentication and select the type from the drop-down list.


Change Authorization Settings Administrator’s Guide

Important: If you turn off Authentication, all users can access any of the Servers’ applications. If you select Anonymous Authentication all users share the same user name and password. In both configurations, you cannot generate detailed usage or licensing reports.



Note: You can associate a Provider Policy with a specific application by editing its .osd file. We recommend making such associations in the OSD Editor in the SoftGrid Sequencer. See the SoftGrid Sequencer User’s Guide for details.


Change Authorization SettingsYou can set and change the enforcement of access permissions in a Provider Policy. This determines whether Servers associated with this policy verify that a user is authorized to launch the application.

Regardless of the access settings that applications, Servers and Server Groups have, Servers do not enforce access permissions until the Provider Pipeline setting is checked and applied.

Steps overview. Right-click on a Provider Policy and choose Properties. On the Provider Pipeline tab, check or clear the Enforce Access Permission Settings checkbox. Then apply the changes.




4. Check the Enforce Access Permission Settings checkbox to have the Server verify access permission whenever a user tries to launch an application. If you want users to be able to launch regardless of permissions settings, clear the checkbox.

5. Click OK.



Admnistrator’s Guide Change Licensing Settings

Change Licensing SettingsA Provider Pipeline must enforce or audit licensing policies for them to take effect. You specify Application Licenses and associate applications with them. Then you can activate license enforcement in the Provider Policy properties.

If you have not set up the licenses, see Configuring Application Licenses on page 27 for procedures.

Steps overview. Right-click on a Provider Policy and choose Properties. On the Provider Pipeline tab, check or clear the Licensing checkbox. Choose whether to enforce licensing or audit usage only. Then apply the changes.




4. Check the Licensing checkbox to have the Server either enforce licensing or audit license usage. Or if you clear the checkbox, the Server Groups that use this policy will not enforce licensing or save detailed reporting data.

5. If you check the checkbox, select the type of licensing enforcement. Choose:

• Enforce License Policies to have the Servers follow license settings as defined in the license associated with its applications.

• Audit License Usage Only to meter licensing for reporting purposes, but never deny users access to an application even when a license is not available.

6. Click OK.



Change Licensing Settings Administrator’s Guide



Chapter 6

Managing the SoftGrid Platform

Overview After you install and configure your SoftGrid Servers and deliver applications, you can maintain the components and fine-tune their operations. This chapter provides procedures for:

• Control of Data Store Growth on page 53• SoftGrid Administrator Privileges on page 54• Licenses’ Associated Applications on page 56• Reporting on page 57• Restart a Virtual Application Server on page 62• Change Data Store Access Credentials on page 63• Changing Account Authority Credentials on page 63

Control of Data Store GrowthMaintenance of the SoftGrid database is automatic after you configure it. You can reconfigure its size and its, data-retention period anytime.

Also, by monitoring the SQL Server’s message logs, you can see when it becomes large enough to overwrite existing usage data.

The SoftGrid Data Store generates a warning notice to the SQL Server’s message logs when stored data reaches 95% of the maximum size you have set. The Data Store then automatically deletes 10% of the usage data, starting with the oldest records. It does this even if this happens before the Usage History period has past.

This rarely is a problem. The database can grow quickly and exceed your limits when you set logging to its highest levels. Normally, you would do this only for diagnostics, and then reduce the logging level. For details, see Log Modules on page 42.

The default database size is 1024MB (1GB) and default usage-storage period is 6 months. Normally, these settings keep growth well below filling the database.

The database holds usage data, including the launches and shutdowns of SoftGrid-enabled applications. If you have a very large number of users accessing many applications, the database may fill.

Controlling Data Store Growth

Steps overview. Right-click on a Management Web Service and choose System Options. Set the database size and usage retention period.


2. In the left pane, expand SoftGrid Systems, right-click on one of the Management Web Services and choose System Options.


SoftGrid Administrator Privileges Administrator’s Guide

3. On the Database tab, under Database Size:

• You can increase or decrease the Maximum Database Size (MB). The default is 1024. The range is from 1 through 2,147,483,647.

• You can click the No Size Limit button to let the database grow up to the available disk space.

4. On the Database tab, under Usage History:

• You can increase or decrease the retention period in the Keep Usage For (Months). The default is 1. The range is 1 through 120. Of course, the longer the period, the more likely the database will fill.

• You can click Keep All Usage. This prevents deleting stored usage data by time period. The Data Store only deletes data when the hard drive reaches 95% capacity.

5. When you finish your configuration, click Apply and then OK.

The changes take effect immediately.

If you check both No Size Limit and Keep All Usage, the Data Store will not perform any automatic database cleanup. The database would continue to grow.

Data Store Considerations

The SQL Agent must be running to perform database cleanup. You can verify this by looking at it in Administrative Tools>Services>SQLAgent$SOFTGRID (where the last part of the service is the database name). This service should have a Status of Started. Also, in its Properties, its Startup Type must be Automatic.

The Data Store history includes basic information on SoftGrid-enabled applications, such as who launches them, when and long they run in a session. These data form the basis for SoftGrid reports. The data are not large or complex, so that the default of 1024MB should be more than adequate for the six-month retention period. This database grows large only for extreme numbers of applications and sessions.

As with any database, monitor its size, either manually or through your database administration procedures. Likewise, if you have very long usage retention periods, report generation can be slow. You should apply your administration policies to determine whether you want to let the database grow or let the cleanup reduce it when it reaches time or size limits.

If you set the System Options to limit storage by size, it will automatically clean up and erase data. When the database reaches 95% of the limit, the Data Store will delete the oldest 10% of the data without warning. A notice of the action will then appear in the SQL Server message log. If you want to preserve all usage data, you should save the database before it reaches the 95% level.

SoftGrid Administrator PrivilegesYou initially define who has SoftGrid Administrator privileges during Platform installation. Until you change this, only these users can administrate the Servers and other SoftGrid components.

Anytime, you can change members of this group, including adding or deleting members. If you find that you need to expand the number of administrators or replace the ones you chose at installation, you can do that through the Management Console.


Admnistrator’s Guide SoftGrid Administrator Privileges

In addition, if the SoftGrid database become corrupt and you lose access through the Management Console, you can also reset the administrators. This clears all privileges for all SoftGrid Administrators.

Important: If you reset the administrators, everyone loses access to controlling the SoftGrid Platform and Servers through the Management Console. To regain control and assign administrative privileges you must have both administrative access to the database and the SA account login.

Adding SoftGrid Administrators

Steps overview. Right-click on SoftGrid Administrators, choose Add Administrator Group and navigate to the group.


2. In the left pane, right-click on SoftGrid Administrators and choose Add Administrator Group.

3. In the Added SoftGrid Administrators dialog, navigate to the group you want to have privileges.

Note: You can add groups, but not individual users as SoftGrid Administrators.

The addition is immediate. That group can begin administering SoftGrid through the Management Console.

Deleting SoftGrid Administrators

Steps overview. Click on SoftGrid Administrators. In the right pane, right click on a group and choose Delete.


2. In the left pane, click SoftGrid Administrators.

3. In the right pane, right-click on the group to remove and choose Delete.

4. In the confirmation box, click Yes.

Note: You must have at least two SoftGrid Administrator groups to be able to delete one.

The deletion is immediate. That group can no longer administer SoftGrid through the Management Console.

Resetting SoftGrid Administrators

If the SoftGrid Data Store becomes corrupt and causes you to lose administrative access to the SoftGrid Platform through the Management Console, you can reset the administrators. You will be able to add an administrative group during this process.

Important: Before you reset the SoftGrid Administrators, be sure you have the login name and password for the SoftGrid Data Store. This was originally set during installation. You must provide this to add administrators.

Steps overview. Right-click SoftGrid Systems and choose All Tasks>Reset SoftGrid Administrators. Choose the database and log in. Use the Add or Delete buttons to create the administrators’ groups.



Licenses’ Associated Applications Administrator’s Guide

2. In the left pane, right-click SoftGrid Systems and choose All Tasks>Reset SoftGrid Administrators.

Important: The reset wizard connects to the SoftGrid Data Store to reset administrators. It needs the database username and password set at installation to do so.

3. On the Connect to the SoftGrid Management Database dialog, choose the database server from the drop-down list. Enter the user name and password. Also, choose the database from the drop-down list.

4. When you finish, click Next.

5. After the Management Console connects to the database, review the list of SoftGrid Administrator Groups in the next dialog.

6. From the list, you can:

• Highlight a group and click Remove to delete it.• Click Add and navigate to a group in the Add Administrator Group dialog.

Then click OK to add it.7. When you finish adding or deleting groups, click Finish.

The changes are immediate. The members of the SoftGrid Administrators group can control the Platform through the Management Console.

Licenses’ Associated ApplicationsAfter you add and configure your application and licenses, you can verify and review their associations. You may decide to remove a license or change some properties, including application association.

Reviewing Associated Applications

Steps overview. Click on Applications and sort the Application License column in the right pane.


2. In the left pane, click Applications.

3. In the right pane, click the Application License column heading to sort the applications by license names.

4. Examine the applications associated with the license.

Optionally, you can right-click on an application, choose Properties and change its license group, shortcuts, file type associations or access permissions.

Once you review the license’s associated applications, you can see related information and procedures at:

• Application License Groups on page 21• Removing a License on page 36• Enabling and Disabling Licenses on page 36• Deleting an Application License Group on page 37


Admnistrator’s Guide Reporting

ReportingUsing SoftGrid’s built-in reporting, you can generate seven types of reports from the SoftGrid Data Store. In their order in the drop-down lists, they are:

System Utilization. Graph. Average daily and concurrent usage for a Server, Server Group, or all Servers (Enterprise), including usage by day of week and hour of day.

Software Audit. List. Usage for all applications in SoftGrid database. For each, it lists top N users by number of sessions, total and average session duration. It includes total usage for all users.

Application Utilization. Graph with list. Average daily and concurrent sessions for one specified application. It also lists all the application’s users with number of sessions, and total and average session duration. It includes a summary for total usage for all users.

User/Group Activity. Graph. For specified user or user group, total daily and concurrent sessions, including a list of applications by user or group with total and average session duration per application. It also shows total usage for all applications.

License Compliance. List. For licenses in the SoftGrid database, license usage and compliance. For Unlimited licenses, number of distinct users per license. For Concurrent licenses, number allowed against peak concurrent users. For Named licenses, users granted the license and whether they were entitled to use it.

System Error. Graph with list. Number of fatal errors, errors and warnings logged by Server, Server Group, or all Servers (Enterprise). It includes a list of each in ascending order by time.

User/Group Application Configuration. List. Applications, FTAs, and shortcuts assigned to a user or user group.

General Report Procedures

Creating, running, printing and exporting all types of reports are very similar. They involve:

• Creating a new report through a wizard by specifying the defaults.• Running a report to display it on screen, printing it, or exporting it to a PDF

or XLS file.All these actions start in the Management Console.

Creating Reports When you create a report, you set up the related preferences to make running, printing or exporting it more efficient. If you then run a report, you can change those preferences for the current run or accept your defaults.

Right-click on Reports and choose New Report to start. Then name and choose the type of report. For all types except User/Group Application Configuration, you choose a default time period. Some types provide other options, such as users or applications.

Note: You can have multiple versions of the same type of report. For example, you can create Application Utilization reports for more than one application. You might also have a User/Group Activity report for each department by its User Group.


Reporting Administrator’s Guide

The new report then appears in the Reports container in the left pane. You can delete or rename a report. If you want to change its preferences, you can do this by running it and altering them in the run dialogs. The preferences you use become the new defaults for that report.

Customizing Columns You can change the columns that display for a report in the right (Results) pane of the Management Console. To do this:

1. Click Reports in the left pane.

2. Click a report in the right pane.

3. From the upper menu, choose View>Add/Remove Columns.

4. In the Add/Remove Columns wizard, highlight a column in the Displayed columns or Available columns list box and click Add or Remove to move it to another lit box.

To change the order that a column appears in the Results pane, highlight a displayed column and click Move Up or Move Down.

If you want to revert your changes, click Restore Defaults before clicking OK.

5. When you finish, click Ok.

The changes take effect immediately and reflect this report’s display in the Management Console. It does not affect printed or exported reports or other reports.

Running Reports You can run a report at will. Right-click on one and choose Run Report. For all types except User/Group Application Configuration, you see one or more dialogs showing the report preferences. You can confirm these or change them before running the report.

The resulting report appears in the right pane. From there, you can click the print or export icons at the top of the pane to perform those functions.

Printing or Exporting Reports

You do not have to run a report to print or export it. You can right-click on a report and choose either Print Report or Export Report.

Note: For both printing and export, the resulting report uses your preferences. To change any of those settings, run the report first.

When you choose to print a report, you see the Windows print dialog, where you can choose your printer. When you choose to export it, you enter a name for the report, you can navigate to a location for the export, and you choose either Excel (.xls) or Acrobat (.pdf) file format.

System Utilization Reports

Generate a System Utilization report to graphically represent average and concurrent load on a Server, Server Group or Enterprise (all Servers). After you choose the time period, you can select concurrent sessions or users. Both versions also show averages per day of the week and by hour of the day.

The average and concurrent sessions report is a summary of system usage for the chosen Server(s). This can be useful if you are investigating slow applications delivery. You can use it to see if you might need to add a Server or to remove one with a low load.

The users report is similar. It can be useful in measuring license compliance by number of concurrent users.



Generate a System Utilization Report

Steps overview. Right-click on Reports and choose New Report. In the New Report wizard, name the report and choose System Utilization as Report Type. Follow the wizard. Then right-click on the report and run, print or export it.


2. In the left pane, right-click on Reports and choose New Report.

3. Enter a meaningful name for the report.

4. In Report Type drop-down list, choose System Utilization and click Next.

5. In the Report Period dialog, choose how frequently to run the report and click Next.

6. In the Utilization Measurement dialog, choose whether to measure concurrent sessions or users and click Next.

7. In the Server dialog, choose whether to report on one Server, a Server Group or all Servers (Enterprise), and if applicable, choose a Server Group from its drop-down list.

Note: This list is not active for Enterprise-level reports.

8. Click Finish.

Once you add a report, you can run, print or export it. Other than its name, you cannot change its properties. However, you can add reports of this type with different properties. You can also delete it.

Software Audit Reports

Generate a software audit when you want to see the weekly or monthly usage of every SoftGrid-enabled application. This report details users by sessions and total users for every application in the database.

Use this report to see which applications receive the greatest and least use and how many distinct users each has.

Generate an Audit Report

Steps overview. Right-click on Reports and choose New Report. In the New Report wizard, name the report and choose Software Audit as Report Type. Choose a report frequency.




4. In Report Type drop-down list, choose Software Audit and click Next.

5. In the Report Period dialog, choose how frequently to run the report (weekly or monthly) and click Next.

6. Click Finish.

Once you add a report, you can run, print or export it. If you run it, you can change the report period. You can also delete the report.

Application Utilization Reports

You can generate an Application Utilization report for any application in the database. For the day, week or month you specify, it graphs the total daily and concurrent sessions. It lists the number of distinct users and for all uses, shows number of sessions, and total and average session durations.

You can see both how heavy an application’s is used and its most frequent users are.


Reporting Administrator’s Guide

Generate an Application Utilization Report

Steps overview. Right-click on Reports and choose New Report. In the New Report wizard, name the report and choose Application Utilization as Report Type. Choose a report frequency and the application.




4. In Report Type drop-down list, choose Application Utilization and click Next.


6. From the drop-down list, choose the application and click Next.

7. Click Finish.

Once you add a report, you can run, print or export it. If you run it, you can change the report period or pick a different application. You can also delete the report.

Note: If you run reports on one application regularly, you can create and name the report appropriately for it. On the other hand, you can name it more generically and pick the application when you run the report if you want to very which application you choose.

User/Group Activity Reports

Generate a User/Group Activity report to track application sessions for a single user or a user group. For the time period you specify, the report graphs total and concurrent sessions.

The report also shows each application used with sessions, and both total and average session duration.

Generate an Activity Report

Steps overview. Right-click on Reports and choose New Report. In the New Report wizard, name the report and choose User/Group Activity as Report Type. Choose a report frequency. Then select User or User Group and navigate to your choice.




4. In Report Type drop-down list, choose User/Group Activity and click Next.


6. Select either User or User Group and navigate to the one you want.

7. Click Finish.

Once you add a report, you can run, print or export it. If you run it, you can change the report period or pick a different user or user group. You can also delete the report.

License Compliance Reports

You can track license usage with a License Compliance Report. For all applications in the database, it displays the total number of licenses, their types, and number of users per application. The report has separate data for unlimited, concurrent, and named licenses.



Note: License Compliance Reports are only meaningful for concurrent or named licenses and not unlimited ones. License enforcement must be enabled. For procedures on enforcing licensing, see Configuring Application Licenses on page 27.

Generate a Compliance Report

Steps overview. Right-click on Reports and choose New Report. In the New Report wizard, name the report and choose License Compliance as Report Type. Choose a report frequency. Then select User or User Group and navigate to your choice.




4. In Report Type drop-down list, choose License Compliance and click Next.


6. Select either User or User Group and navigate to the one you want.

7. Click Finish.

Once you add a report, you can run, print or export it. If you run it, you can change the report period or pick a different user or user group. You can also delete the report.

System Error Reports

The System Error report is similar to the Windows Event Viewer content. Depending on the message levels you set for SoftGrid components, you see those for the chosen period in the report.

The report displays errors by type, with date and time, message ID, which SoftGrid component and Server generated them, and the message text.

You can peruse this report for maintenance, identifying issues to correct even if users have not reported them. You can also perform troubleshooting and temporarily increase the log levels to capture more error data.

For diagnostic purposes only, you can increase the level of errors sent to the database. However, the two highest levels can fill up the database quickly. So after troubleshooting, you should return this setting to previous levels. For details on setting logging levels, see Log Modules on page 42.

Generate a System Error Report

Steps overview. Right-click on Reports and choose New Report. In the New Report wizard, name the report and choose System Error as Report Type. Choose a report frequency.




4. In Report Type drop-down list, choose, System Error and click Next.


6. Click Finish.



Restart a Virtual Application Server Administrator’s Guide

User/Group Application Configuration Reports

For any user or user group, you can view all accessible applications with their FTAs and published shortcuts. The report displays separate sections for List of Applications, File Associations, and Published Shortcuts.

You can use this report to determine whether the user or group has access to the appropriate applications only and that both the FTAs and shortcuts are correct.

Note: Each of these reports is specific to one user or user group. When you create one, name it meaningfully.

Generate a User/Group Application

Configuration Report

Steps overview. Right-click on Reports and choose New Report. In the New Report wizard, name the report and choose User/Group Application Configuration as Report Type. Choose a report frequency and the application.




4. In Report Type drop-down list, choose User/Group Application Configuration and click Next.


6. From the drop-down list, choose the application and click Next.

7. Click Finish.


Restart a Virtual Application ServerSome Management Console procedures require restarting the Server service for them to take effect. You can restart the SoftGrid Virtual Application Server service without rebooting its computer.

If users have fully cached their SoftGrid-enabled applications, restarting the service should not disrupt any connections. Depending on your change-control procedures, you may notify users or perform the service restart during off-hours.

The Server starts this service automatically by default when its computer boots. The service should continue running. You can check its status under Administrative Tools>Services.

Steps overview. From Windows Administrative Tools, double-click Services. Right-click SoftGrid Virtual Application Server. Then choose Restart.

1. From Administrative Tools, double-click Services.

2. In the Services window, right-click SoftGrid Virtual Application Server.

3. If its Status is Started, choose Restart. If its Status is Stopped, choose Start.

4. When the Status changes to Started, exit Services.


Admnistrator’s Guide Change Data Store Access Credentials

Change Data Store Access CredentialsYour security policy may include periodic password changes. For this or other reason that requires changes to the account that SoftGrid components use to access the SoftGrid Data Sore, you need to update these credentials.

Note: Change credentials at a time that minimizes disruption to users.

Preparation. Before you begin to update the credentials:

• Log into the Management Console computer as a user with SoftGrid Administrator privileges

• Know the logins with local administrator privileges to:– SoftGrid Data Store computer– SoftGrid Management Web Service computer– SoftGrid Virtual Application Servers

Steps overview. For each Server, open its server.conf file in a text editor. Replace the user and password on their lines. Save the file. Restart the Server service.

1. On the SoftGrid Virtual Application Server, locate its configuration file, server.conf. By default it is in \\Program Files\Softricity\SoftGrid Server\conf.

2. Open the file in a text editor, like Notepad.

3. You can change the contents of the credentials lines:

<location>...</location>

<user>...</user>

<password>...</password>

Note: The location entry is the name of the database server.

4. Save the file

5. Record the new credentials and keep in a safe place.

6. Restart the SoftGrid Virtual Application Server service for the changes to take effect.

Changing Account Authority CredentialsWhen your Active Directory server or NT4 Domain Controller has a change of login, you must update the credentials that SoftGrid components use to access it. Access to your account authority affects:

• Whether a Server permits access to applications that require permissions.• Whether you can use the Management Console to add, edit or delete

conurbation records in the SoftGrid data Store.Important: Changing access credentials in the Management Console before

these changes occur in the account authority disables SoftGrid.

Steps overview. Right-click on an Account Authority and choose Properties. Edit the User Name and Password fields. Then apply the changes.


Changing Account Authority Credentials Administrator’s Guide


2. In the left pane, expand the Account Authorities container.

3. In the right pane, right-click an account authority and choose Properties.

4. Enter the correct strings in the User Name and both Password fields.

5. Click Apply.

6. Restart the Server in the group for the changes to take effect.


Admnistrator’s Guide Knoweldgebase Articles

Appendix A

Troubleshooting and Messages

Knoweldgebase ArticlesMany common questions and troubleshooting procedures are in our Softricity Knowledgebase at http://support.softricity.com. There, you can search by keywords or error codes.

Among the most frequently accessed articles are:

Diagnostic Utilities. We recommend two freeware utilities – Filemon and Regmon – to help identify and diagnose symptoms with SoftGrid-enabled applications. Download these utilities from:

http://www.sysinternals.com/

For procedures and tips on using Filemon and Regmon with SoftGrid, see Softricity Knowledgebase Article #500.

Error Code Formats. When searching the Knowledgebase for error codes, be aware that the first 12 digits are unique to version of the client. The ending 10 digits remain constant between all versions.

Typically, when we refer to an error code, we list each of the first 12 digits as an x such as xxxxxx-xxxxxx07-000DF004. Searching for the first 12 digits does not return any results. So, when you search for an error code, enter the last 10 (plus the hyphen), 8 or 4 digits such as 07-000DF004, 000DF004 or F004.

In this appendix, we list errors by those final digits. If you want examples or more information on an error code, check for it in the Knoweldgebase.

In our headings by the following errors, we list them by just the last digits for your quick reference.

Common IssuesThe following diagnostic steps and solutions address typical issues you may encounter with SoftGrid. Where the heading shows an Error number, this is the end

Knowledgebase Topic Article # Sequencing Microsoft Office 2003. 274

Upgrading from SoftGrid 3.2 to 4.0. 663

Whitepaper on streaming protocols used with SoftGrid, load balancers and firewalls.

392

SFTMIME.COM and SFTMIME.EXE command-line options. 266

Commands for publishing SoftGrid-enabled applications in Citrix MetaFrame.

179


http://support.softricity.com

http://support.softricity.com

http://www.sysinternals.com/

Common Issues Administrator’s Guide

of a log message in the SoftGrid Client or Server logs (sftclient.txt or sftserver.txt). These logs may contain additional information useful for troubleshooting.

Reclaiming SG Client Cache

After deleting an application accessible to a SG Client, the local cache size does not reduce. Normally, this does not slow down the user’s computer or cause any memory issues.

However, if you want to clear that cache for future applications, you can change a registry setting to do so. The remaining applications stay available and users can reload them into cache when they them launch the next time.

To reset the SG Client cache:

1. Launch the Registry Editor.

2. Expand HKEY_LOCAL_MACHINE\SOFTWARE\Softricity\SoftGrid Client\CurrentVersion\AppFS.

3. Right-click State and choose Modify.

4. For Value data type 0.

5. Click OK.

6. Exit the Registry Editor.

7. Reboot the Client computer.

SG Client Cannot Launch Specified Application Error 0A-20000194)

If a SoftGrid Client cannot launch a specific application, its log file, sftlog.txt, reports an error in the format: The SoftGrid client could not connect to stream URL '{protocol}://{server_name}:{port}/{path}/{filename}.sft' (FS status: xxxxxx0A-20000194). The client was unable to connect to a SoftGrid server (rc xxxxxx0A-20000194).

This can indicate one of several problems:

1. The application has not been added to the SoftGrid Management Console.

2. The .sft file specified in the related .osd file is not in the Server’s /content directory structure.

3. The Provider Policy specified in the .osd file does not exist.

Note: Find details on this error in Softricity Knowledgebase Article #615.

Application Not Added to Console

If the application does not have a published shortcut, the user can double-click on its .osd file. Also, the user’s desktop may contain a shortcut for an application that no longer exists on the SoftGrid Server or the shortcut may have been copied to an alternate location and the Client cannot find it.

Remove outdated or improperly referenced shortcuts. Then refresh the Desktop Configuration for the Client.

.sft File Not in /contentStructure

If the application file related to an application does not exist in the proper /content directory structure, the Server cannot deliver it. This can happen if the specified relative path name is incorrect in the .osd file.

1. From Administrative Tools, launch SoftGrid Management Console.

2. Expand SoftGrid Systems > {server_name} > Packages > package failing to launch.

3. Double-click the package version.


Admnistrator’s Guide Common Issues

4. Verify that the Softricity File Relative Path only contains the sub-directory of the content directory and the .sft file name.

Specified Provider Policy Does Not Exist

When the Server loads the related .osd file, it uses that file’s specified Provider Policy as referenced in the CODEBASE HREF line following any ?Customer= entry. If the Provider Policy following ?Customer= does not exist, the application will not launch.

Edit the .osd file in the SoftGrid Sequencer OSD Editor to insert the proper Provider Policy.

Application Does Not Complete Launch (Error 04-00000428)

An application can start but not complete a launch and the Client log file, sftlog.txt, reports an error message ending in xxxxxx-xxxxxx04-00000428. This can result from several problems.

Note: Find more details on this error in Softricity Knowledgebase Articles #499 and #500.

Application-Specific Errors

When the log includes this non-specific application error, first check the Windows Event Viewer on the Client desktop. Look for application-specific errors.

These messages may include missing .osd elements of the application. Typically, you can then use the SoftGrid Sequencer OSD Editor to correct the error.

Note: For details on VM Values in the .osd file, see the Guide to Administering the SoftGrid Client for either Windows Desktops or for Terminal Servers. You can download these from Softricity Customer Support or find them in the /Docs subfolders of the installation CD.

Missing Files This error message can result from the application being unable to find a required file. Typically, the file is in the package even thought the executable cannot locate it.

Resolve such problems by editing the .osd file. Add the correct path to the application’s PATH environment variable specified by the VARIABLE attribute of the ENVIRONMENT element.

Incompatible File Version incompatibleIf a file has a version incompatible with the Client computer’s operating system, the launch can fail. Use the Filemon utility to diagnose this.

If the problem is with a system file, you can open the package and remove the suspect file. Then when the Client cannot locate this file, it will attempt to use the local system’s version.

You can also resequence the application, making sure to include the operating system on which it failed.

Dr. Watson on Launch Attempt

If trying to launch an application causes the Client desktop to start Dr. Watson, troubleshoot this with Filemon or Windows Task Manager. After Dr. Watson runs, review the Application Errors.

If you contact Softricity Customer Support, you may be asked to send drwtsn32.log and user.dmp files for diagnosis.

User Needs Access to TEMP Directory

An application launch may fail if it writes to the %TEMP% or %TMP% directory and user does not have access to these locations. You can use Filemon to confirm where has been denied.

A common cause of this is that the TEMP and TMP environment variables specified by the VARIABLE attribute of the ENVIRONMENT element in the .osd file are configured to %SystemRoot%\Temp. Typically, users do not have access to this directory on Windows Terminal Servers.



In the SoftGrid Sequencer OSD Editor, edit the application’s .osd file to change the TEMP and TMP environment variables to %TEMP% and %TMP% or simply remove them from the file. If they do not exist in the .osd file, the application uses the environment variables specified by the local system.

Windows Side-by-Side Assemblies Error

SoftGrid-enabled applications using Windows Side-by-Side Assemblies can stream only to Windows XP and later operating systems. You can determine if Side-by-Side is causing a launch failure by streaming it to Windows 2000 and to XP or 2003. If it only launches on Windows 2000, Side-by-Side is a problem and that application cannot stream to XP or 2003 computers.

Multiple Instances Fail to Launch

An application may not launch a second instance. Some executables check for running processes of the same executable and attempt to attach to these. If that process is in SoftGrid System Guard’s virtual environment, the second launch fails.

This is a known issue.

Launch Requires Administrative Rights

An application may only launch for a user with administrative rights on the Client desktop. This can happen if the user does not have access to local files required by the application or if the system security policy prevents a required action for the launch.

You can diagnose this with Filemon to determine failed actions or denied access. Then you can test the user without local security policies applied.

Afterward, you may need to assign appropriate permissions for the user locally.

User Must Be Assigned to Create global object

Some applications require that the user must be assigned to the Create global object User Rights Assignment on the local computer. This is application specific and not affected by SoftGrid sequencings. It happens most frequently with SoftGrid-enabled applications delivered by Terminal Servers.

To make this assignment:

1. From the Terminal Server, launch the Group Policy Object Editor (gpedit.msc).

2. Expand Local Computer Policy > Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment.

3. Edit the Policy Create global object.

4. Add Authenticated Users.

5. Stream the application.

Client Cannot Find Package or Files (Error 0A-000800B)

An application launch can fail if the Client cannot find the application’s package or one or more of its files. In either case, it reports and error ending in xxxxxx-xxxxxx0A-0000800B.

These can happen when:

• The .osd file contains invalid information in its HREF attribute.• The Provider Policy specified in the .osd file is invalid.• The SoftGrid Virtual Application Server service Log On account does not

have adequate permissions for the .sft files.Note: For examples for the following solutions, see Softricity Knowledgebase

Article #218.

Invalid HREF path If the HREF line in the application’s .osd file contains invalid data, verify its content. In the SoftGrid Sequencer OSD Editor, examine the HREF attribute. Verify the path, server name, port, directories, and .sft file name. Correct any errors.



Invalid Provider Policy If the Provider Policy specified in the application’s .osd no longer exists or is otherwise invalid, verify its existence and name. In the SoftGrid Sequencer OSD Editor, examine the HREF attribute. If the Provider Policy following ?Customer= does not exist or is incorrect, edit this attribute.

Log On Account .sft Permissions

A SoftGrid-enabled application will not load if the Server’s SoftGrid Virtual Application Server service Log On account does not have Read File Permissions to the .sft files.

Normally this is for the SYSTEM account. Verify that it has the proper permissions by right-clicking on the /content folder with the .sft files. Choose Properties. On the Security tab, verify the permissions.

You can verify which account the Server uses by:

1. From Administrative Tools, choose Services.

2. Right-click SoftGrid Virtual Application Server and choose Properties.

3. On the Log On tab, the account appears under Log on as:

Invalid WORKINGDIR (Error 2C-8007010B)

If the application cannot find the WORKINGDIR specified in the related .osd file, it will not launch. The Client log, sftlog.txt, reports an error ending xxxxxx-xxxxxx2C-8007010B.

In the SoftGrid Sequencer OSD Editor, verify the WORKINGDIR element on its own line. That directory must exist on the Client desktop.

Client Cannot Find Server (Error 2A-00002AFC)

If the SoftGrid Client cannot communicate with the Server, applications will not launch. The Client log, sftlog.txt, reports error ending xxxxxx-xxxxxx2A-00002AFC. It also reports No information is logged to sft-server.log for this error code.

Verify the Server’s settings in the application’s .osd file. Then verify communication with the new settings.

To verify Server settings, open the application’s .osd file in the SoftGrid Sequencer OSD Editor. Examine the protocol, server name and port in the HREF line.

• The default protocol is rtsp and the alternate is rtsps.• The default server name is %SFT_SOFTGRIDSERVER%. This environment

variable must be configured on the SoftGrid Clients. Alternately, you can replace this with the Server or load-balancing device’s host name, DNS name, or IP address.

• The default port is 554. Alternate ports include but are not limited to 332 and 443.

When all settings are correct, verify the connections.

1. In Administrative Tools > Services, verify that SoftGrid Virtual Application Server has a Status of Started. If not, right-click the service and choose Start.

2. Next, from the Client desktop, ping the Server by name and port. If the ping is not successful, return to the .osd file and verify the settings.

3. Next, from the Client Desktop, telnet to the Server by name and port. If it cannot open a connection, verify that port traffic between Client and Server is not restricted by a firewall.



Client Cannot Access Application (Error 0A-20000193)

If the SoftGrid Client cannot launch an application and its log, sftlog.txt, reports an error ending xxxxxx-xxxxxx0A-20000193. It also reports that authentication and authorization are denied.

This means that user does not have access to the application. Causes can include:

• The user is not a member of a group with access permissions to the application.

• The user is not a member of a group associated with the Provider Policy.• The .osd file has a misspelling in its ?Customer= section of the HREF line.

Verifying Access Association

If the user is not in a group with access permissions for the application, SoftGrid will not permit the application to launch. To verify permissions:


2. Expand Console Root > SERVER NAME > Applications.

3. Right-click the application and choose Properties.

4. On the Access Permissions tab, verify the user receiving the error code is a member of a group listed and add if necessary.

Verifying Provider Policy Association

If the user is not in a group associated with the Provider Policy for the application, SoftGrid will not permit the application to launch. To verify this association:


2. Expand Console Root > SERVER NAME > Provider Policies.

3. Right-click Default Provider or other policy associated with the application’s Server choose Properties.

4. On the Access Permissions tab, verify the user is a member of a group listed and add if necessary.

Verifying ?Customer=Entry

If the ?Customer= specified in the HREF attribute of the .osd file is misspelled, the Server will not be able to authenticate or authorize access.

For example, if your SoftGrid environment has multiple Provider Policies, the Default Provider and a custom Provider Policy named Anonymous, configure the application’s .osd file. To use the Anonymous Provider Policy, in the Sequencer OSD Editor, edit the HREF line to include the Anonymous user. Such as:

HREF="rtsp://%SFT_SOFTGRIDSERVER%:554/Softricity/sft_ea70.v1.sft?Customer=Anonymous"

Whatever ?Customer name you provide must be accurate.

Conflicting Application Names and Versions (Error 44-00001003)

If the SoftGrid Client cannot load .osd files when it finds identical application Name and VERSION attributes in more than one Suite. Its log, sftlog.txt, reports an error ending xxxxxx-xxxxxx44-00001003.

The SoftGrid prevents adding multiple applications with the same name and version. This mismatch can occur when:

• An application is removed from the SoftGrid Management Console and a new application with the same NAME and VERSION but different SUITE name as the previous application is added.

• An existing application is modified to use a new .osd file that contains the same NAME and VERSION but different SUITE name.



• An .osd file for an existing application is edited to use a different SUITE name.

If you are replacing an application with a new one, remove the old one from the SoftGrid Client cache launching the new application.

If both applications are on the Server, modify one application’s NAME or VERSION.

Invalid Server Port (Error 2A-0000274D)

The SoftGrid Client may fail to refresh a Desktop Configuration Server from SoftGrid Client Management. If the Client log, sftlog.txt, reports and error ending with xxxxxx-xxxxxx2a-0000274D, the Client cannot communication with the Desktop Configuration Server port.

Verify the Server and its port:


2. Click Desktop Configuration Servers.

3. Right-click the Server reporting the error code and choose Properties.

4. Verify the server specified in Host Name:.

5. Verify the port specified in Port:.

When all settings are correct, verify the connections.

1. In Administrative Tools > Services, verify that SoftGrid Virtual Application Server has a Status of Started. If not, right-click the service and choose Start.

2. Next, from the Client desktop, ping the Server by name and port. If the ping is not successful, return to the .osd file and verify the settings.

3. Next, from the Client Desktop, telnet to the Server by name and port. If it cannot open a connection, verify that port traffic between Client and Server is not restricted by a firewall.

IIS Permissions (Error 0000C824)

The SoftGrid Management Console may fail to refresh its connection to the SoftGrid Management Web Service. The Console log file, sftmmc.log, reports an error ending in xxxxxx-xxxxxx0000C824 and a BinaryFormatter Version incompatibility. Also, the Windows Event Viewer log may contain Event IDs 10016, 1009 or 1002.

This can occur when:

• IIS Local Activation permissions do not include NETWORK SERVICE.• The ASP.NET worker process account does not have proper permissions.• Windows SharePoint is installed to the same Website as the SoftGrid

Management Web Service.Note: For details and full procedures to diagnose and remedy this problem,

see Softricity Knowledgebase Article #610.

Local Activation Permissions

Verify that the NETWORK SERVICE account on the Console computer has Local Activation permissions to the IIS Admin Service. Do this by:

1. From Administrative Tools, launch Component Services.

2. Expand Component Services>Computers>My Computer>DCOM Config.

3. Right-click IIS Admin Service and choose Properties.

4. On the Security tab, click Edit for Launch Permissions.

5. Add the NETWORK SERVICE with allow Local Activation permissions.



6. Click OK in each open window in turn.

Note: When a SoftGrid Management Console fails in this way, restart the DefaultAppPool. Do this by launching the IIS Manger from Administrative Tools. Under the Server, right-click on Application Pools>DefaultApPool and choose Start.

ASP.NET Permissions The ASP.NET worker process account needs Full Control permissions to:

• %SystemRoot%\Temp• %SystemRoot%\Microsoft.NET\Framework\VERSION\Temporary ASP.NET

FilesThe SoftGrid installation or upgrade sets these properly. However, if a Server with IIS is promoted to a Domain Controller before the SoftGrid Management Server is installed, the permissions can change.

Note: We do not recommend installing SoftGrid components on a Domain Controller.

You can verify the ASP.NET account from Administrative Tools>ASP.NET State Service properties. Then select each location above and grant this account Full Control.

SharePoint Conflicts The SoftGrid Management Web Service and Windows SharePoint Services 2.0 have a conflict if installed to the same Website. When SharePoint is installed later, it modifies the SoftGridManagement and SoftGridReporting application pool from DefaultAppPool to StsApPool1.

To change the application pool:

1. From Administrative Tools, launch Internet Information Services (IIS) Manager.

2. Expand (Server) >Web Sites>Default Web Site.

3. Right-click SoftGridManagement and choose Properties.

4. On the Virtual Directory tab, for Application pool: choose DefaultAppPool.

5. Click OK.

6. Right-click SoftGridReporting and choose Properties.

7. On the Virtual Directory tab, for Application pool:, choose DefaultAppPool.

8. Click OK.


Index

Symbols.ico file 8

delete 24on HTTP server 11

.osd file 8and HTTP server 9delete 25on HTTP server 11

.sft filedelete 25

.sprj filedelete 24

?Customer=error 70

Aaccess

Account Authority 63limit by Provider Policy 31verify 70

access credentialsData Store 63

Account Authoritychange credentials 63SoftGrid 6

Active Directory 11and Management Web Service 14change credentials 63in SoftGrid 6role 15

activityreports 57

addapplication 20Concurrent License 33, 34Concurrent License group 33Concurrent License users 35license group association 30Provider Policy 45report columns 58Server Group 39Server to Server Group 40SoftGrid administrator 55

administrative rightsrequired for launch 68

administratorsadd 55delete 55prerequisites 1reset 55SoftGrid 54

ADSIand Management Web Service 14authentication 15

Anonymous Authenticationand Provider Policy 47

applicationClient cannot access 70duplicate name and version 70duplicate name and version error 70import 20launch failure 66remove 24user groups 20

application licenseand reporting 28configuration overview 27enable or disable 36remove 36types 28

application license groupchange 21delete 37overview 21

Application Server Groups, see Server GroupsApplication Utilization

report definition 57reports 13

Application Utilization reportgenerate 60overview 59

applicationsby HTTP 11central control 3configuring 19delivery requirements 4license association 56virtualization 2

applyProvider Policy 47

ASP.NETerror 71permissions error 72

auditreports 57

authenticationand Active Directory 15and Provider Policy 47change settings 49options 46, 47

authorizationchange settings 50

BBasic Authentication

and Provider Policy 47

Ccache

reclaim on Client 66central installation

overview 3



changeAccount Authority credentials 63application license group 21authentication settings 49authorization settings 50concurrent users 35Data Store credentials 63File Type Associations 23license settings 51log modules 42named users 33Server Groups 23shortcuts 22, 48user groups 20, 49

change Provider Policy 41Client

description 2functions 9hardware and software 5installation 5virtual environment 9

Client cachereclaim 66

Client cannot access applicationerror 70

Client cannot find fileserror 68

Client installation 5Clients

modes 6columns

reports 58compliance

reports 57components

description 2concepts

SoftGrid Platform 2Concurrent License

add 33, 34change users 35overview 33

concurrent licensedefinition 28

Concurrent License groupadd 33

concurrent userschange 35

configurationinitial 19overview 4reports 57Server start-up 11

configuration objects 13configure

application license 27applications 19license expiration warning 30

contents

this guide 1create

Application Utilization Report 60License Compliance report 61Named License 31report 57Software Audit report 59System Error report 61System Utilization report 59Unlimited License 29User/Group Activity report 60User/Group Application Configuration report 62

Create global objecterror 68

credentialsData Store

change 63custom installation 5Customer=

error 70

DData Store

and log level 43and Management Web Service 14and start-up configuration 15change credentials 63control growthdescription 2ODBC connection 11record storage 15records 13retention period 54size limit 54

database, see Data StoreDefaultAppPool

error 72definitions

SoftGrid components 2delete

.ico file 24

.osd file 25

.sft file 25

.sprj file 24application 24application license group 37concurrent license users 35license 36named users 33package files 25Server Group 40SoftGrid administrator 55

desktop iconssee shortcuts

diagnostics 65disable

license 36disconnected mode

overview 6



domain controllerrole 15

Dr. Watsonon launch 67

duplicateapplication and version 70

Eenable

license 36enforce

Unlimited License 29error

.sft file not in /content 66?Customer= 70administrative rights 68application launch failure 66application not added to Console

applicationnot added to Console 66

application specific 67ASP.NET permissions 72cannot find files 68Client cannot access application 70Client cannot find Server 69Create global object 68DefaultAppPool 72Dr. Watson on launch 67failure to refresh 71IIS permissions 71incomplete launch 67invalid HREF path 68invalid Provider Policy 69invalid Server port 71Local Activation permissions 71missing Provider Policy 67multiple instances 68Read File permissions 69report 57Side-by-Side 68TEMP directory access 67

error codeformats 65

errorsreports 13

expiration settinglicense 30

expiration warninglicense 30

exportreport 58

Ffile permissions

error 69File Type Associations

change 23overview 22requirements 9

Filemondownload 65

filesmissing 67

formatserror code 65reports 58

FTAchange 23overview 22requirements 9

Ggenerate

Application Utilization report 60License Compliance report 61Software Audit report 59System Error report 61System Utilization report 59, 60User/Group Activity report 60User/Group Application Configuration report 62

global objecterror 68

Hhardware

requirements 5history

usagesetting 54

HREF pathinvalid 68

HTTP server.osd files 9application delivery 11

IICO file 8

delete 24ICO file on HTTP server 11ico files

and Client 9icons

see shortcutsimport

application 20installation

Client 5custom 5overview 4

invalid Server port 71invalid WORKINGDIR

error 69

Kkey

license 28Knowledgebase 17

Softricity 65

SoftGrid Platform v4.0


Llaunch

incomplete 67license

activation 28and reporting 28associated applications 56enable or disable 36expiration settings 30expiration warning 30records 13registration key 28remove 36reports 57types 28

License Compliancereport

generate 61overview 60


license groupadd Concurrent 33add Named License 32change 21delete 37overview 21, 27

license group associationadd or remove 30

license keyoverview 28

licensescentral control 3change settings 51

Local Activation permissionserror 71

log levelsand Data Store 43

log moduleschange 42overview 42

loginData Store 63

logscontrol data size

Mmanagement components 12Management Console

and reports 13application not added 66description 2functions 19overview 6

Management Web Serviceand authentication 15data flow 14description 2functions 14

ports 14SharePoint conflict 72

managingshortcuts 48

manualcontents 1

memoryreclaim Client cache 66

missing files 67modes

Clients 6multiple instances

error 68

NNamed License

add to license group 32create 31

named licensedefinition 28overview 31

named userschange 33

NETWORK SERVICEpermissions error 71

OODBC

and Data Store 15ODBC connection

Data Store 11OSD file 8

and HTTP server 9delete 25on HTTP server 11

overviewapplication license groups 21Application Utilization report 59central control 3Concurrent Licenses 33configure license 27configure Provider Policies 45configuring Server 39disconnected mode 6File Type Associations 22installation and configuration 4License Compliance report 60license groups 27license key 28log modules 42Management Console 6named licenses 31Provider Policies 41reporting 57Server Groups 39shortcuts 9, 22SoftGrid 1Software Audit report 59System Error report 61



System Utilization report 58Unlimited Licenses 29user groups 20User/Group activity 60User/Group Application Configuration report 62

Ppackage

delete files 25password

Data Store 63permissions 70

ASP.NET 72error 69IIS 71Local Activation error 71

placePlaceNameCustomer PlaceNameSupport PlaceType-Center 17port

invaliderror 71

portsManagement Web Service 14Server 10

prerequisitesapplication delivery 4SoftGrid administration 1

printreport 58

privilegesadministrative 54

protocolsServer 9, 10

Provider Policiesconfiguration overview 45

Provider Policyadd 45and named licenses 31and Server Groups 23apply 47authentication options 47change 41change authentication settings 49change authorization settings 50change license settings 51change user groups 49error

invalid name 69missing 67overview 41verify association 70

RRead File permissions

error 69records

Server to Data Store 15storage 13

registration key

application 28Regmon

download 65remove

application 24application license group 37concurrent license users 35license 36license association 30named users 33report columns 58Server from Server Group 41Server Group 40SoftGrid administrator 55

remove userdeleted applications 24

reportcolumns 58create 57export formats 58export or print 58multiple versions 57run 58types 13, 57

reportingand licenses 28objects 13overview 57

reportsgeneral procedures 57

requirementsapplication delivery 4SoftGrid administration 1

resetSoftGrid administrator 55

restartServer 62Server service 62

retentiondata 54

rtpServer protocol 9

rtspServer protocol 9

runreport 58

runtime environment 9

SSequencer

description 2Server 11

add to Server Group 40ADSI connection 11configuration 10configuration overview 39description 2functions 10hardware and software 5



ports 10protocols 9, 10remove from Server Group 41restart 62start-up configuration 11

in Data Store 15Server connection 11Server Group

add 39add Server 40and Provider Policy 47change

Provider Policy 41remove 40remove Server 41

Server Groupsand Provider Policy 23changing 23overview 39

Server portinvalid 71

SFT filedelete 25

SharePointconflict 72error 71

shortcutapplication

overview 9shortcuts

changing 22enable desktop management 48managing 48overview 22

Side-by-Sideerror 68

SoftGrid 5Account Authority 6add administrator 55administrator prerequisites 1administrator privileges 54application-delivery diagram 4Client description 2component diagram 3components description 2concepts 2configuring applications 19custom installation 5delete administrator 55initial setup 19management components 12overview 1Sequencer description 2Server description 2

SoftGrid administratorsreset 55

SoftGrid Clientfunctions 9

SoftGrid Data Store

see Data Store 11SoftGrid Management Console

see Management Console 6SoftGrid Management Web Service

see Management Web Service 14SoftGrid Virtual Application Server

see Server 1SoftGrid Virtual Application Server service

restart 62Softricity

Knowledgebase 65Softricity Knowledgebase 17Software Audit

reportoverview 59


Software Audit reportgenerate 59

software requirements 5SPRJ file

delete 24SQL, see Data Storestart-up configuration 11

in Data Store 15support

Knowledgebase 17System Error

reportoverview 61

report definition 57System Error report

generate 61System Utilization

reportoverview 58


System Utilization reportgenerate 59

TTEMP directory

access 67troubleshooting 65

UUnlimited License

create 29overview 29

unlimited licensedefinition 28

updatescentral 3

usagerecords 13

usage historysetting 54

User Activity



reports 13user groups

change 20, 49overview 20

User Rights Assignmenterror 68

User/Group Activityreport

definition 57overview 60

User/Group Activity reportgenerate 60

User/Group Application Configurationreport

overview 62report definition 57

User/Group Application Configuration reportgenerate 62

usersdeleted applications 24

utilizationreports 57

VVAS

see Server 1verify 70

access permissions 70Provider Policy association 70

versionduplication error 70

Virtual Application Serversee Server 1

virtual environment 2Client 9

Wwarning

license expiration 30Website

support 17Windows Authentication

and Provider Policy 47Windows SharePoint

error 71Windows SharePoint conflict 72Windows Side-by-Side error 68WORKINGDIR

error 69


softricity softgrid platform v4.0 administrator’s...

Documents