The Microsoft App-V Team Blog

The official blog for Microsoft Application Virtualization

Wednesdays Tips for New SoftGrid Admins

Wednesdays Tips for New SoftGrid Admins

  • Comments 6
  • Likes

We know there are a lot of you out there who are new to SoftGrid or who will be implementing SoftGrid very soon so we decided to put together a couple tips to help new SoftGrid admins avoid some common pitfalls we tend to see. 

 

During the Virtual Application Server installation, you will be prompted to provide a group for admins and a group for users.  Always use global groups and not local groups.

This can lead to a few different issues but the most common one is that when a local group is used for the SoftGrid admin group, you might get this error when trying to open the SoftGrid server management console:

Unable to log into the SoftGrid System.

The specified user is not authorized to administer this system.

Error code: 0000C803

 

When adding a new user group to the Access Permissions tab of an application, be sure the same group is added to the Group Assignment tab of the Default Provider.

The user group you add during the installation of the server gets automatically added to the Group Assignment tab of the Default Provider, but from that point forward, if you create a new group that you're going to use in managing access to virtualized apps, make sure that same group is defined on the Group Assignment tab of the Default Provider.  This is located under Provider Policies in the server management console.  Failure to do this will possibly cause the following errors:

 

The SoftGrid Client could not launch {application_name} .

Either you are not authorized to use this application or the system could not obtain a license for this application. If the problem persists, please report the following error code to your System Administrator.

Error code: xxxxxx-xxxxxx 07-000DF004

 

or

 

The SoftGrid Client could not launch {application_name} .

You are not authorized to use this application, possibly because there are no more licenses available. Please report the following error code to your System Administrator

Error code: xxxxxx-xxxxxx 07-000DF004

 

On your sequencer machine, be sure to setup a separate drive or partition as the Q drive.

As a best practice, we highly recommend that when you sequence (package) applications you install these applications to the Q: drive.  What gets confusing sometimes is that while the SoftGrid client automatically creates a Q: drive on the fly when it launches a virtualized application, the Sequencer does not.  For whichever computer you're going to use to package your applications, be sure to manually create a partition and assign it the drive letter Q.

 

Hopefully you find these helpful and as always, if you have any topics you'd like to suggest please let me know.

 

- The Microsoft SoftGrid Team

Comments
  • I hope they keep up with this. The tips in this Wednesday's release aren't all that stunning, but they're definitely useful if you aren't used to sequencing applications. This week's tips include details on: - During the Virtual Application Server installation,

  • Though I didn't find this weeks tips to be particularly interesting, they may be news to someone who is new to SoftGrid. Hopefully the team will keep blogging new tips every week (that would be ...

  • Though I didn't find this weeks tips to be particularly interesting, they may be news to someone who is new to SoftGrid. Hopefully the team will keep blogging new tips every week (that would be ...

  • Hoy en cosas interesantes: El video de Bill Gates que aun no habias visto, 25 Videos de SCOM 2007 para

  • More and more attention is being directed to SoftGrid and it is nice to see that there is a TechNet blog

  • Actually you should not use global groups, the correct way is to user local groups and create aggregation universal groups that are members in the local groups and then create global groups that are members of the aggregation groups.  Finally put users to the global security groups.

    At least that is the Microsoft way.

    Using global groups would not be considered best practices

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment