Software Deployment

We've been using Symantec LiveState Delivery (SLD) for approximately a year. We are a medium sized environment with one remote WAN site and we used SLD to migrate the company to Windows XP (from Windows 2000). SLD provides tools to allow a "No Touch" migration. It also allows packaging and deploying of applications.


Pros:

No Touch Migration / Deployment / Imaging
Almost any installation can be packaged and deployed
Package dependencies and exclusions allow for greater control in your environment
Very flexible, if you have the knowledge
Centrally Managed

Cons:

Steep Learning Curve
Advanced documentation lacking, although Tier 2 support is very knowledgeable
Packaged installs are not "enforced", ala GPO
No data migration tools are fully integration, 3rd party tools are needed
Price


Installation and Support:

When SLD is purchased, they recommend a 1 week onsite consultation to get everything installed and running. We decided to try and get it running ourselves. I only recommend doing this if you are HIGHLY technical. For the most part, I was successful. Had more advanced documentation been available, I would've been able to work through some of the issues we encountered. Symantec tech support was very helpful.

The setup process has been significantly improved since the CCM and iCommand versions. There has also been considerable effort by Symantec to make the product more user friendly.

Symantec does update the product on a frequent basis as well. Many of the bugs that I reported were addressed in future patches.

Currently, all support appears to reside within the U.S.

Packaging:

Packaging is great. We came from a GPO only environment, but we now have the freedom to use many other installation types. MSI’s are supported, as well as any other type that can be command line drive. There is also an included utility to script installations by capturing the actual code behind buttons and options used during an install. Think macro recorder, but capturing the actual code instead of mouse positions, etc. You can also have package dependencies and exclusions, which work out great if you are updating apps on a regular basis. Another really cool feature is the ability to use variables, conditions, and user input for packages.
Example: AutoCAD requires a unique serial number. With GPO, you’re stuck with your one install, or you have 10 GPO’s. With SLD, I can add parameters that will prompt the admin for the proper serial when assigning the package to the PC. This will then inject the proper serial number into the MSI and the install will then be unique. If you created a Stand Alone Network install with the AutoCAD deployment tools, you can also make the install Auto Activate.
I can’t get into all the ways this can be used, but I’ve found many uses already. We’ve been able to package over 90% of our apps, a feat that would be nearly impossible using GPO and MSI only installs. I am still working towards our goal of 100%. [8|]

Data Migration:

Symantec ships Client Migration 3.0 with SLD. To be able to use this in a large environment, a SQL server is recommended. Even then, we would get sporadic results. In the end, we decided to user Microsoft’s User State Migration Tool (USMT). This worked out incredibly well, the migrations were predictable and reliable.



In conclusion, I really can’t image life the way it was before SLD. I really enjoy the control, flexibility, standardization, and convenience it brings to the table. I love the fact that I can set a PC on the bench, and within an hour or two have it imaged and all the standard apps installed. All hands off. This applies to 1 or 100 PC’s. My co-worker also agrees that SLD has really enhanced our capabilities and streamlined our processes. He came from a semi-managed environment and can really see the benefits of a well implemented system.