This article will be discussing how to use the SVS APIs in .Net C#. It references the FSL2 class I'm writing which can be downloaded here and is meant to show how the API work and what you can do with them. You should also have the latest version of FSLLIB.HLP that's available with the SDK -- for reference -- as I may not cover everything for each method.

Previously, I've covered WMI and SVS with scripting and with .Net C#. This provided the Juice community with a C# class that allowed for easy integration into any .Net application you may want to make.

WMI provides a lot of convenience and relative ease of use, but I know that everyone wants a way to use the actual SVS library for your work. There is an SDK available to download but it's in C++ and doesn't have the best documentation in the world. Over the past few months I've been wrapping various SVS APIs that I've needed into C# and have decided to share that information with the community.

Brian Duckering, AppStream Sr. Director of Products and Alliances, and Scot Curry, Symantec Sr. Systems Engineer presented this lab demonstrates the various rules that can be applied to applications, users and groups in order to simplify and automate application delivery, license management and license optimization. This lab also explores the three different types of application packages that can be streamed and their different behaviors. Exercises include uploading packages, setting rules, and exploration of desired results.

Dale Bethers, Symantec Engineering Manager, and Jeremy Hurren, Symantec Principle Software Engineer, led this lab where participants gained hands-on experience with the basics of creating, delivering and maintaining Altiris Virtual Software Packages (VSPs) using SVS Admin and Altiris Notification Server.

Understanding the rules Windows Installer uses to overwrite files can help minimize the time to troubleshoot installation problems. There are two distinct rules that the Windows Installer service uses when determine if a file should be overwritten: Versioned Files and Non-Versioned files.

Run keys cause programs to automatically run each time that a user logs on. The Windows XP registry includes the following four Run keys: