I want to use the utilities to deploy the clients to many PCs.
How do I begin.?

After installing the SyAM Software Management Utilities you should share the flder that the utiliites are in, by default c:\syam\utilities. Now put the client executable (unzipped) into this folder.

Open the SyAM Utilities via start->programs->syam->utilities->syam utilities. When the window opens you can scan a your network range or domain on the system discovery tab.

Once you have selected the systems you wish to install, click the add to install list button and add them to the list.

Select the SyAM Installation Settings tab and enter the network path to the share folder and select the system client software to install.

Select Agent with local Interface or Agent only, computer type, language,etc.

Select the Authentication tab and enter the Administrative login information for the systems. Click all three checkboxes.

Select the Installation tab verify the systems in the list and click the install button.

I want to use the utilities to schedule shutdowns to many PCs.
How do I begin.?

Open the SyAM Utilities via start->programs->syam->utilities->syam utilities. When the window opens you can scan a your network range or domain on the system discovery tab.

Once you have selected the systems you wish to install, click the add to install list button and add them to the list.

Select the Power Management tab and verify the systems in the list. Click on the shutdown for the particular days and times, then click the Send Power Scheduler Settings

This will issue the setting to all of the systems in the list and the result will be shown in the Power Management History window.

I am getting errors when I try to install the client software on a remote system, what should I be looking for?

First, check to see if the windows firewall is turned on at either system.

Second, check to see that you can connect to the remote system using \\systemname\c$. Verify that you can connect to the remote system. From the remote system verify that you can connect to the share drive on the system running the SyAM Management Utilities.

Third, A common administrative user and password. All systems must have a commom username and password. you must be logged in and using that username and password when you invoke the utility. This allows you to connect to the remote system and and also back to the share drive where the software client executable is.

Fourth, Verify that the path you are using to the software executable is to the share drive and not to the local driver c:

Deploying MSI packages

Store the msi and associated files in a sub folder off of the apps folder In our example we have stored the files for the Adobe Reader 8.11 in a sub folder called amf

Next copy the depsvc.exe from the apps folder to the new sub folder amf, this SyAM file is required by the Management Utility.

Now create a batch file that will define what runs on the remote system.

First running the command for msi execution, the path the network shared folder where the msi files are and then any additional silent installation parameters

Here is the batch file created to install Adobe Reader 8.11 MSI package

BATCH File called adbmsitest.bat cd \windows\system32 msiexec.exe /i \\192.168.200.13\c$\syam\utilities\apps\amf\acroread.msi /qn exit

Now within the Third Party Installation tab instead of choosing the specific executable file we chose the batch file to execute on the remote system. The batch file runs the msi executable and defined parameters from the network share to perform the installation silently without user interaction.

**Please Note – you do not enter any custom parameters for the batch file chosen as they are contained within the actual batch file. If you MSI installation forces a reboot we recommend you check off the Do Not Check for Process Completion (For BIOS Updates), this will stop the utility from trying to check the system as it will be rebooting and would report that the installation had failed.

From the Installation tab select the List you wish to deploy the MSI package to from the drop down menu. This will show the systems within the list you have chosen. When ready, click on the Install third Party Tab.

Once it has completed it will be shown below in the Installation history. If for any reason it was unsuccessful in deploying the MSI package it will provide a reason why it failed, please review the reason for failure and make the necessary correction and try again.
As the system being updated is managed it will report the Asset change to the System Area Manager event log.