Pittsburgh User Group

We have made the move to SVS for MS Office products and a few others. We are using the Task server for our Helpdesk team to deploy and manage the software in real-time after approval.

Our process has been working well and we wanted to share.

The final thing we needed to provide our Helpdesk team was a way to go to the end user's machine and manage SVS layers locally via USB. As stated before, no end user in our environment has the SVS Admin console installed.

Now that we have reviewed using the SVS admin console, let's take a look at managing the layers using cmd line. We felt our helpdesk needed a way to assist users that may have been unreachable via our Task server. Some of this information is already posted but hopefully putting this all together in one place with help others.

As we planned our SVS agent roll-out it became clear to us that no end user should have the SVS admin console on their machine. That being said we need to get our staff familiar with the SVS and the admin console by having them install it on their machine and test. This article covers a basic overview of that process for our Helpdesk team.

To review: Altiris has a top level "reporting" Notification Server (NS) that has Asset and Contract Management Solution installed. It manages assets at this level.

Altiris also has a client facing NS that installs agents, manages machines and forwards inventory to the reporting NS.

To review: Altiris has a top level "reporting" Notification Server (NS) that has Asset and Contract Management Solution installed. It manages assets at this level.

Altiris also has a client facing NS that installs agents, manages machines and forwards inventory to the reporting NS.

Thought we would share our Asset management process with some other users. We have developed documentation that details our Asset Management process for our Helpdesk teams. These processes allow us to keep historical data and perform shell swaps for failing machines.