25 February 2014

Altiris diagnostic agent tasks

Howto : http://www.symantec.com/docs/HOWTO75097

The attached tasks can update settings on Managed computers and on the SMP server, to collect additional diagnostic information, and to reset the same settings to their default values.
To use these tasks, you need to import the attached file into the Altiris console, possibly  under Jobs and Tasks. To import this XML,

  • Save the attach XML to your local drive
  • Select the folder where you wish the folder and it's contents to be imported,
  • Right-click on the folder and select import
  • Select the the XML on your local drive

20 February 2014

How to remove the Symantec Management Agent (Altiris Agent) manually on the SMP server and assign it to a new drive

Note: Removing the Symantec Management Agent from the SMP itself is not recommended. There are usually some side-effects that may affect functionality on Task Management, DS.


The automatic uninstall process used for the Symantec Management Agent (SMA, formally known as the Altiris Agent) should take care of most of the items that were installed.

Prior to the release of ITMS 7.5, the command "aexagentutil.exe /clean" was not intended to remove SMA anymore. It was left for legacy purposes only. It was recommended to use "AeXNSAgent.exe /uninstall" to uninstall the SMA.

Note: As per ITMS 7.5 release,  for the SMA 7.5 the “/clean” command behaves exactly like "AeXNSAgent /uninstall" command. Actually “AeXAgentUtil.exe /clean” simply launches “aexnsagent.exe /uninstall”.  Using "AeXNSAgent.exe /uninstall" should removes ALL registry, binaries, etc created by agent but leaves behind agent guid (i.e. install on this system uses same guid). Also Log files are not removed as it was decided to let them be for troubleshooting purposes.


On those instances where you need to remove any leftovers or make sure that previous references of the Agent location are removed (in case that you need to install the Agent to a different drive but is not taking the new path), you may want to use the following steps (in most cases using the steps on HOWTO45738 "What is the best way to cleanly uninstall the Symantec Management Agent to leave no remnants (or the bare minimum) behind?" should address most uninstalls):

1.      Uninstall any Altiris Agents found in Add/Remove programs

2.      Find any and all copies of the file AeXAgentUtil.exe and from each location

a.   Run AeXAgentUtil.exe /uninstallagents

          b.      Aexnsagent.exe /uninstall

          (Both executables are located, by default at: C:\Program Files\Altiris\Altiris Agent\)

3. Open Registry find keys where old agent path(s) is found and delete those registry keys

a.       This Includes two entries under the Windows Uninstall registry that could still exist (don’t forget the wow64 hive as well) “Altiris Agents” and “NS Client”.

b.      The Altiris Agent is under the uninstall key and NS Client is under the Altiris\Express key both need to be deleted if not already deleted by the /clean.     

HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\eXpress\NS Client
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\AltirisAgent
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\AltirisAgent

c.       As well you need to clean any references of the Altiris Agent on

HKEY_CLASSES_ROOT\CLSID
HKEY_CLASSES_ROOT\Typelib
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Clsid
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Typelib 

4.      Copy AexNSC.exe from “\\localhost\nscap\bin\win32\x86\NS Client Package” and copy the file to “C:\temp”

5.      In a command prompt (Administrator privileges and make sure the smp.domain.com portion reflects the SMP server) execute the following command line contained within the brackets [] but path should be changed appropriately to the correct location where the NS is installed: [C:\temp\AexNSC.exe -s -a NS="smp.domain.com" PATH="D:\program files\altiris" nsweb="http://smp.domain.com/altiris/" NOSTARTMENU /platform=x64 /s]

6.      Verify that the install correctly installed to path specified

7.      Install Task service agent

a.       Windows Explorer, browse to “D:\Program Files\Altiris\Notification Server\NSCap\bin\Win64\x64\Client Task Management\Server Package”

b.      Double click TaskServerSetup.exe

c.       Change the “Destination Folder” to “D:\Program Files\Altiris\Altiris Agent\Client Task Server\” (or whatever the correct path is), click Next

d.      In the Installation type dialogue window, select “Typical”, continue with the install

e.       Restart the Client Task DataLoader and Object Host Service services


18 February 2014

Installation Failed at step 1 or 2 for ITMS

In the log you light find that the .net AJAX extentions failed to install, then check the following

The Microsoft .NET Framework NGEN v2.0.50727 services are needed by the installer but are disabled by default. They need to be started by .NET installers. To solve this, change the startup type of both services Microsoft .NET Framework NGEN v2.0.50727_X86 and Microsoft .NET Framework NGEN v2.0.50727_X64 to manual and re-install the application, which now runs fine!

Installing on SQL Non Standard Ports

In order for the Notification Server to be able to communicate with a SQL Server using a non-standard port a SQL alias needs to be created. The alias will contain the necessary information about the SQL Server, including servername/instance and port number.

Perform the following steps on your SQL Server:

  1. Click Start > Run and type cliconfg in the run box and click OK.
  2. Click the Alias tab on the SQL Server Client Network Utility screen.
  3. Click the Add button.
  4. In the Server Alias screen enter the name you wish to use to reference your SQL Server.
  5. Click the TCP/IP radio button under Network Libraries.
  6. Enter the SQL Server Name\Instance in the Server Name box.
  7. To specify the specific port, uncheck the Dynamically Determine Port box and input the correct port.
  8. Click the OK button.
  9. On the main SQL Server Client Network Utility Screen click the OK button.
  10. On the SQL Server configuration screen of the Notification Server setup enter the alias name.

Symantec Installation Manager keeps prompting that it needs a reboot...(Workaround)


In some rare occasions the SIM does not start because of Reboot pending....

It looks like the workaround option did its job by now, check the exact steps:

Create the following SIM registry Keys to ignore a pending reboot:
HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\Aim\IgnorPendingReboot

Create a DWord(32) value called “Enable”
Enable = 1 Ignores pending reboot
Enable = 0 Checks for reboot

 

Symantec™ IT Management Suite 7.5 HF4 powered by Altiris™ technology Release Notes

http://www.symantec.com/business/support/index?page=content&id=DOC7126&actp=SUBSCRIPTION