API

The SVS Software Developer Kit is now available in a smaller, simpler format. No dependencies -- just good ol' C code and the necessary documentation! It has also been updated with additional functions added since the original release of SVS 2.1. There's lots of useful new stuff in there, so get it today and start building that next killer app for SVS! As with the previous SVS SDK, it's free!

Our company is moving to Altiris and we had a need to replicate practices with our current management solution in Altiris. The only way to accomplish our end goal was to roll up our sleeves, get comfy with the ASDK, and script our needs out. I ran into many issues getting started with the ASDK and programming to it in Csharp and I didn't find a lot of documentation or examples to help me through it. There are some things out here on Juice, but I'd like to contribute what I came up with to help out other struggling ASDK'ers.

As we near the end of the SDK documentation there are only a few more things to cover. While most of remaining functions fall into a specific category a few don't, so I' ll be spreading those that don't between parts eight and nine (the last article). The main focus for this article is layer rights (or permissions), layer priority and processes (namely ignoring them and running one from an existing layer).

This is part two of a series that teaches you how to create your own SVS Remote tool. (See part one here).

This 40-minute video shows you the code behind the scenes that makes it all work.

You can use the ASDK to programmatically generate incidents but you are limited to using the subject and body fields when creating them. You can then use the ASDK to modify fields one by one, which means if you are changing 5+ fields the workers will have to scroll halfway down the page to view the body of an incident.

This is part one of a two part series that will teach you how to create your own SVS Remote tool. (See part two here.)
This 15-minute video teaches you how to create the user interface using Visual Studio 2005. The next video will show you the code behind the scenes that makes it all work.