Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Redirecting a Client to a different NS

Created: 28 Nov 2011 | 9 comments
Pravash Sahu's picture
0 0 Votes
Login to vote

Hi friends,

I am using CMS 7.1 SP1, I am trying to redirect the clients to a new NS. I have already  used the AexAgentUtil.exe /server:(New server) from Command prompt at client computers, but this seems to be not working and the client is still connected to the previous NS. I have restarted the services also. any suggestion will be appreciated.

 

Thanks,

 

Pravash

Comments

Dmitri Dragunov's picture
29
Nov
2011
0 Votes 0
Login to vote

Hi Pravash,   Try to ping NS

Hi Pravash,

 

Try to ping NS from Client by FQDN. Client can't redirect on not available NS.

NS should be available from Client by IP and FQDN.

 

Regards,

Dmitri

 

andykn101's picture
29
Nov
2011
0 Votes 0
Login to vote
wmheid@armc.org's picture
29
Nov
2011
0 Votes 0
Login to vote

I just went through this

I just went through this myself. 

From my DS I had to send a job to uninstall the client with the old server settings.  Then I waited a day or two, did an import from my active directory and created a policy to send the client to newly discovered computers with the new settings from my SMP 7.1 Server.

Dmitri Dragunov's picture
29
Nov
2011
0 Votes 0
Login to vote

no need to wait two days :)

Also you may not wait two days, simply add to your DS job the one more step with installation of a new Alitiris Agent from the new NS server using next commandline: "AeXNSC.exe NS:NEW_NS_Name"

Install package can be founded on New NS under "C:\Program Files\Altiris\Notification Server\NSCap\bin\Win32\X86\NS Client Package" directory

 

wmheid@armc.org's picture
29
Nov
2011
0 Votes 0
Login to vote

You are correct about the

You are correct about the wait time.  I was making a number of other changes at the time which is why I waited two days.  Not enough coffee this morning when I type that!

dlopes's picture
29
Nov
2011
0 Votes 0
Login to vote

It´s a bit tricky :)

To get that working you first need to stop the agent with: AexAgentutil.exe /stop then you can use the AexAgentUtil.exe /server:NEWNS.FQDN and the agent will start up with the new NS.

Works all the time for me.

Another way is to change the agent targetted settings and point it to a new NS in the old NS console.

Daniel Lopes de Oliveira
Endpoint Management Architect & Consultant
-----------------------------------------------

MCITP: EA

hamsalad00's picture
29
Nov
2011
1 Vote +1
Login to vote

How I do it

This is the script I use in the DS to flip the NS client to a new NS server:

 

"C:\Program Files\Altiris\Altiris Agent\aexagentutil.exe" /Server:FQDN_of_NS-Server

"C:\Program Files\Altiris\Altiris Agent\aexagentutil.exe" /Restart

 

No need to stop it first. Just need the restart after you send the new info to the client.

AlexTH's picture
30
Nov
2011
2 Votes +2
Login to vote

One more method to change the

One more method to change the NS Server for client:

 

Changing for specific client from NS console.

Independently of that is client currently belong to old or to new NS you can connect to the client from the new NS Server with Real-time management through WMI protocol.

 

  1. Go to Actions -> Remote Management  -> Real-time management.
  2. Specify the IP address or FQDN  and connect to client.
  3. If connection passed correctly (WMI ports and Creds)
  4. In opened tree browse to “Software -> SMA -> Settings.
  5. Use “Change Server”.
Theo Reddy's picture
30
Nov
2011
0 Votes 0
Login to vote

worked for me

Thanks AlexTh,

 

I've had adhoc requirements to change the NS server for agents, and your process above worked for me.

 

Thanks