fullpaccopper

VSU uses an application named Altiris. There is an Altiris agent installed on all computers that are on the VSU domain. This agent cannot see your files, but simply reports what type of computer you are using and what software is installed on the computer. How does Altiris know which updates to install on my.

• Altiris Client Management Suite
• Altiris Software Portal

Skip to end of metadataGo to start of metadata

The EMS Desktop Client is used by specific administrators to manage scheduling.

• EMS Desktop Client is only available for Windows users
  • if you use a Mac please follow the directions here.
    
• EMS Desktop can only be used by approved administrators. Reach out to scheduling-services@bethel.edu for access.

The EMS Desktop Client and its prerequisites are installed via the Altiris agent.

Altiris Client Management Suite

Open Altiris Symantec Management Agent

• Right-click on the yellow Symantec icon in the system tray
  
• Select 'Symantec Management Agent'
  

Altiris Software Portal

Start Software Install

• In the newly opened window, select 'EMS' from the list and then click 'EMS' on the left under 'Application Tasks'
  

The installation will start and its progress can be tracked at the bottom of the window above. Nexus 2 guitar expansion free download.

Once complete you can run EMS by clicking on the EMS icon on the desktop.

While logged on to the machine you want to install the agent, locate the installation file. One place to get the file is to drill down into the Symantec Management Platform (SMP) server NSCap share that is created when the server is installed. In the example below, <SMP Server> is the hostname or FQDN of your SMP server.

Copy the file to your machine and then open a command prompt to execute AeXNSC.exe. Run the command prompt as administrator on Windows 2008 and Windows 7. In my example here, I placed it in C:Temp because I will not actually need the file after the installation is done.

Determine where you want the installation path to be. If this is going to be a package server, make sure that the location is somewhere you’ll have plenty of disk space for packages. In my example, I’m using the default. You can substitute anything else you want, like “E:ServerAppsAltiris” or whatever… You’ll also need to inform the installer what the FQDN of the SMP server is. The sytax is like this:

The installer then decompresses to start installing. It went by too fast for me to catch a screenshot of it. It looks very similar to other installers that count to 100. Once the installer finishes running you’ll get a success prompt that will look similar to this one. If you’re maticulous, you can delete AeXNSC.exe that you used to start the installation.

You can monitor the installation by drilling down to the installation path.

Optionally, you can also launch AeXAgentActivate.exe to monitor a little closer.

Click on the settings link to look at the Agent Settings.

You’ll see that the SMP server is shown with what we told it with the /ns switch. Within 15 minutes, it will update with the SMP server, get applicable policies and proceed to be managed. If you’re kind of impatient, you can click the Update button to try and force it to update with the SMP server and keep things moving along. This works kind of like when a pedestrian would press the walk button at an intersection. After the first update, the button is more responsive to policy updates. As new plug-ins are installed, the agent will restart and close these windows. That’s a good sign that things are progressing along as intended.