Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

VAM - Virtual Application Manager 1.2

Created: 17 Nov 2010 • Updated: 17 Nov 2010 | 3 comments
TheSmiz's picture
+3 3 Votes
Login to vote

Virtual Application Manager (VAM) - is a utility to help in the management of Virtual Software Packages.  This application can manage layers both on the local workstation and remote computers over the network.  All the normal layer functionality is available and you are required to be an administrator to manage layers.  SVS/SWV must be installed on the workstation you wish to manage.  If you are only intending on managing remote workstations, the local host does not need virtualization installed to do so.

Simply enter the computer name or IP address you would like to connect to, enter your user id an password (either a local admin account on the remote machine or your domain credentials with admin rights to the machine) and click "Query Apps".  For a local computer enter a dot "." for the computer name (using the WMI classes to manage) and no user id or password is required to continue.  (note: if managing your local machine, it will need SVS installed)

You will get a list of virtual applications on that machine.  If there are not any virtual applications installed on the workstation you are querying, a message stating "There are no Virtual Application installed on XXXXX".  If there are virtual applications to manage, clicking on an application in the list will enable/disable the available functions of activate, deactivate, reset, delete and toggle auto activate.

Settings to store User Id and password.  The SvsWmi provider requires a level of impersonation to list and use the activities, so userid and password are required for activities on a remote machine, but not the local workstation.  Open menu--> Settings and you can specify user lever credentials that will be pre-populated whenever you launch the app.  These settings will only be available for the user that sets them.  If another user logs into the machine and launches VAM, they will have a blank set of credentials they would need to populate.

After saving the settings, User Id and Password are pre-populated.

If VAM can't connect to SvsWmi on the remote machine, you will see this message:

Select yes, if you are an admin of the remote machine, and the app will check if SVS 2.x or SWV 6.x is installed and reregister SvsWmi at the correct path when needed.

Requires .NET Framework 3.5 installed on the local (host) computer.
Requires SVS/SWV installed on the computers you wish to manage.

I left the older version, 1.0 available for download as well.

If you have any questions or would like me to post the source or would like the source for you to expand on/play with, please let me know.  If you have any thoughts on features, additions or modifications, please send me a message and I will update as I have time.

Comments 3 CommentsJump to latest comment

Scot Curry's picture

Hi TheSmiz,

We talked about this on my last visit.  This is a great tool, and I know the community would really like this.  I would like to suggest you write a quick article, so more people know about this.

Talk to you soon,

Scot

0
Login to vote
TheSmiz's picture

Man, 3 months and I just saw this post some how.  I will get a little article put together soon and hopefully more people could utilize.

 

Regards,

 

Ryan

0
Login to vote
Megan Guth's picture

This doesn't seem to work with SWV 7.5.541. Are there plans to release an update? This tool is amazing and cuts down on our Support teams' phone time with the customer.

0
Login to vote