August 29, 2007
3:33 pm

One of the most common missteps with the SoftGrid client that I have seen over the years is something that is actually merely overlooked. During the installation of the SoftGrid client, the installer program actually asks the user to configure their Desktop Configuration Server. The default behavior of this screen is to be deselected and therefore grayed out. Often, first timers will miss this step and then will not remember or know that they should go into the Client Management Console and add at least one server later.

Later on when they logon to the system, after having Sequenced applications and installed and configured the Server, they expect to see shortcuts for their SoftGrid applications on their desktop. Imagine the disappointment when they see nothing change. The first instinct is to start troubleshooting from the Server Management Console or even dive into the Sequence itself.

How to avoid it: What I recommend people do when they do not see their applications appear at the anticipated shortcut locations is to reduce the areas of concern. What I mean by that is first see from the client whether they can go to “Start -> Run� and then enter the UNC of the SGVAS and successfully connect to the Content share. This tells me if they can even get to the share. If not they need to correct that issue. If this is the problem then begin by investigating IP addresses, names and typos, routing issues and of course DNS entries.

Next, within the Content share, navigate to the .OSD of the SoftGrid Package in question. Double click on that .OSD file. If the application launches by doing this then chances are we have a publishing problem and we would start troubleshooting at the SoftGrid Management Console.

Another popular mistake with these same results is that the .OSD file does not include the client’s operating system in the <OS VALUE> tags. This will prevent it from appearing as a shortcut BUT will still allow it to launch when manually double clicking the OSD file.

Now, another common cause of this issue with the same results actually is found in the SoftGrid Management Console. We will look at that soon.

Full Article

Microsoft, SoftGrid, Virtualization, Virtual Application, Troubleshooting, Knowledgebase, Article

Loading

Contextual Related Posts:

No followup yet

Leave a Response

Comment Preview
« iPhone unlocking video hits WebMicrosoft Office Communications Server 2007 Preview chapters from Resource Kit »
Feed Icon

Subscribe via RSS or email: