IT Management Suite

Colleagues, I worked out a solution for switching current 7.1 clients on the server 8.0. The idea is to redirect agents from one server to another (including the server site). What steps must be performed after the installation of a new management server?

Symantec Management Agent - Need to point them to new NS(SMP).
https://www.symantec.com/connect/forums/symantec-management-agent-need-point-them-new-nssmp

Hi Alex! Can I just run a remote command line (cmd) using the task execution of the script in the Altiris?

"c:\program files\altiris\altiris agent\aexagentutil.exe /server:new.server.com"

I need to switch a large number of agents (about 500)

Send a task from the old NS with that command.

Hi Alexander.

Yes, you can send a task to run the command to change the NS.

By the way, I'm working at the moment in a project doing exactly that. My task target are all computers that has been resquested a new policy in the last 15 minutes. (except NS - **Don't forget to remove NS from your target). The task works extremelly well, but you have to monitor the migration because some agents you will have to migrate manually.

I'm attaching the script bellow. **Also don't forget to configure the task to run in "Hidden" mode to not show any screen to the user.

@echo off

cd /

cd "%ProgramFiles%\Altiris\Altiris Agent"

AeXAgentUtil.exe /Server:your_new_ns.domain.com

exit

Regards,

Aleksandr, don't forget to

1. Enable "Legacy Agent Communication" settings on 8.0 NS machine (Use a "NSConfigurator.exe" on NS machine in C:\Program Files\Altiris\Notification Server\Bin\Tools\ )

• Because by default this setting is disabled in NS 8.0 and leads to blocking 7.1.x agents for further communication with NS 8.0. All redirected 7.1.x clients to 8.0 NS while "Legacy Agent Communication" is disabled, they will be shown in registration queue in "Legacy Agent Registration Requests" report.
• Once "Legacy Agent Communication" setting will be enabled on NS 8.0, then next policy request from redirected 7.1.x Agent will cause its registration with NS 8.0.

2. Take a few 7.1 client machines for basic verification of their Agent redirection from 7.1.x NS to 8.0 NS, because officialy supported upgrade paths for 8.0 release are from 7.5 SP1 HF7 and 7.6 HF7 to 8.0

3. Pay attention that re-direction of 7.1.x clients to 8.0 NS, using a client task can cause problems with successfull communication between NS 8.0 and redirected 7.1.x clients because of certificates which are used in 8.0 NS. Otherwise make sure that your 7.1.x client computers have appropriate certificates installed in trusted root of NS 8.0 , of course if you are using HTTPs on 8.0 NS machine.

Regards,

IP.