Brian S. Tucker

In the beginning, I was unsure of how I would feel about a new application to manage the packaging and deployment of my software to my clients. However, after testing and learning the applicaiton I have come to find that it's not only faster to deploy and update, but easier to manage from a central admin perspective. You know I'm a die hard SMS person by default, but today you get to learn the information you need to setup, configure and deploy sequenced applications in SoftGrid 4.1. The series is short and sweet and broken down into section that just about anyone will understand. Below are the key sections to the series and I hope it helps you either to determine if you will utilize the applicaiton in production, test or simply watch just to know more about this application.

There are some key things to note about SoftGrid that require you to think about the product and server design before you begin.

1. Applications are not registered in Add / Remove Programs. I find this to be a huge issue from someone who wants to inventory my systems and know what's installed.

2. When you "sequence" an application (package), you have to specify a virtual drive letter on the sequencer system. The drive letter on the sequencer system has to be the same with what's configured on the SoftGrid clients. So, before you setup SoftGrid, you need to have internal talks about what drive letter mappings are in use in your organization. If you change your drive letter a few months or years after you setup and sequence in SoftGrid, then you will have to edit all the sequenced applicaitons. Hmmm..... not sure I like that, but it's a fact. All I can suggest is to think about the configuraiton BEFORE you begin.

3. Some applicaitons just can't be sequenced. To understand that statement, I need to explain. First, you can't sequence Internet Explorer. You can't have 2 versions on one system. In order to sequence an application you need one "key" rule to follow as a base for applications that can or cannot be sequenced. For example, JRE or Java Runtime Environment. I know where you might want to sequence this, BUT here is the kicker. For an applicaiton to be sequenced it has to have a shortcut to kick off the sequenced application on the virtual drive. So, if you wanted an Internet applicaiton like JRE (or multiple versions), you would need to have a new shortcut to IE on the desktop or somewhere else to initiate the JRE sequenced application. So, how do you deal with current users who have the default IE icon on the desktop or elsewhere? I'm not sure you can! This is where (if I have explained myself enough) I question what can, can't or should not be sequenced. Once you understand the way applications are sequenced, you can judge for your organization what works best for you. Now, just for argument, you CAN sequence JRE and I have done it, but do you really want the end user to have to open a new IE shortcut just for applications that require JRE? I don't think so.

4. I can confirm that the .adm template I show and explain in Part 2 does not fully work. Some of the GPO settings get applied, but not all. If someone knows of a "fully" working .adm template, plese speak up.

5. As of today, the only way to assign a user to an application is by being a member of an Active Directory or NT 4 domain group. So, if you have 500 applications, plan on 500 AD groups. This makes me think of several issues. Why does Microsoft only have one email system called Exchange? Ok, let's forget about Outlook Express for just a minute and follow what I have to say. Microsoft has Exchange as the only primary email platform. When it comes to application deployments or even security patching we have SMS, AD GPO, BDD, WSUS, Windows Updates, SoftGrid and I'm sure 2 or 3 others. The question I ask is, "why not perfect one"? It seems that each platform is good, very good or out of this world, but why support so many when you can mix all into one and focus on one platform? Maybe a question I have that will never be answered.... Remember that each application requires a group and you will be ok for now.

6. If you have very tight server policies with GPO's, make sure to test the lab settings before you begin a production deployment and document the settings. If you run into problems during the install, make sure to read all the fine print in the KB articles as you may miss a critical step.

Part 1 - Prerequisites and Installation

Part 2 - Client Installation Methods

Part 3 - Deploying Sequenced Applications

Part 4 - Upgrading Sequenced Applications

Part 5 - License Management & Provider Policies

Part 6 - Reporting

Part 7 - Sequencing Applications

Come back in 24 hours (or soon) for the last part of the series... I'm human and it's late!

I have already updated this post. Rather than making a new post for new information on SoftGrid, I will edit this as needed and add videos as asked or have time. Any info on a new version of SoftGrid will be posted to one or more new posts.

Links to SoftGrid help: (updated as I find them)

• SoftGridGuru.com - Forums to ask and find answers to a LOT of issues you may run into.
• Microsoft's Videos - See what the end user sees and an admin overview in 2 videos. Maybe Microsoft should hire me to do all their work? I have hear that before.... lol...
• The SoftGrid Team Blog - A tremendous resource for all info on SoftGrid!
• Zarb & Bennett - Great blog from the UK!

Share this post: