Install software using the Symantec Management Platform (SMP) without Software Management Solution
search cancel

Install software using the Symantec Management Platform (SMP) without Software Management Solution

book

Article ID: 181114

calendar_today

Updated On:

Products

IT Management Suite

Issue/Introduction

How to Install software using the Symantec Management Platform (SMP) without Software Management Solution?

Environment

ITMS 8.x

Resolution

Note: This process requires the Symantec Management agent be installed on target computers.

Depending on the size and nature of the install files, it might be necessary to create multiple jobs/tasks.  For the purpose of these instructions, we are assuming this can be done in 1 job that includes 2 tasks.

The following procedure uses Microsoft commands to copy and run needed files without the use of the Software Management agent.  Please see Microsoft for additional information about command lines: 

https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/net-commands-on-operating-systems

  1. Put the desired install files on a share.  IE <serverName>\Share
  2. Ensure there is a folder on the agent to receive the files:  IE C:\Installs
  3. From the console, go to Manage > Jobs and Tasks and navigate to the desired folder for storing the new tasks/job
  4. Create a task to copy the files:
    1. Right click on the folder and go to New > Task
    2. Select the "Run Script" task
    3. Give this task a name.  IE "Copy files"
    4. Leave the default Script type = Command Script and no tokens
    5. Add the line to copy the files from the share to the agent.  The following is an example based on the share named in step 1 and the target in step 2:
      • COPY \\<serverName>\Share\Setup.msi C:\Installs (this copies setup.msi from the share on the server to a pre-existing folder on the root of the client called “Installs”)
    6. If there are multiple files to copy, create a line for each file
  5. Create a task to run the files:
    1. Right click on the folder and go to New > Task
    2. Select the "Run Script" task
    3. Give this task a name.  IE "Run Install"
    4. Leave the default Script type = Command Script and no tokens
    5. Add the command to run the install.  This step requires knowing the available commands for a given install file.  For details on available commands, please contact the vendor of the install files. 
      • MSIExec /I C:\Installs\Setup.msi (this is a fairly common command for a simple install)
    • To test the command, run each line individually on an agent from a Command Window.  If the commands fail, determine the point of failure and edit the command lines as needed.  If both commands run and the product installs  as desired, then create a job to run the complete install. 
  6. Creating a job to run two tasks.  (If there are multiple files to be copied to the target or they are large, it could be better to run each task individually at different times):
    1. Right click on the folder and go to New > Client Job
    2. Give this job a name.  IE "Install Product X"
    3. Click Add Existing
    4. Browse to the copy task (IE ‘Copy files’) and click OK
    5. Click Add Existing
    6. Browse to the run task (IE ‘Run Install’) and click OK
    7. Save Changes
    8. In the “Task Status” window, click Quick Run or New Schedule to select the targets for this job and schedule it.
    • Note: Clicking on Advanced in a task allows changing of permissions to run the scripts in the event of permissions issues.  So that the run doesn’t overlap with the copy, try double clicking on each task and going to Advanced.  Select the ‘Task Options’ tab and ensure ‘Allow other tasks to run...’ is NOT selected.