The server I had the AMS Management Console on is currently being rebuilt\reformatted. Whenever I reinstall the Whole management console + new database on the reformatted server, is there any way to make it recognize\communicate with the clients that were pushed out by the last install? I REALLY don’t want to have to go around and manually uninstall and then reinstall through the “new” console. That would take an excessive amount of time and have to be done after production hours… I am currently evaluating this and up until today really liked it… If I can get this working correctly my company will most likely be purchasing this and ~250 seats for the client coverage… Please tell me there is an easy fix for this… :-[
Well, the clients should begin checking in automatically to the new server, don’t they?
That is, UNLESS there’s another AMS on the network, that would take over them.
Nope, there’s actually none right no AMS server right now, it died…lol So, when I get the operating system reinstalled and avast reinstalled, they should automatically report to the new AMS installation? There’s no configuration changes I need to make?
Exactly.
This is described in detail in the ADNM Administrator’s Guide, sections 9.2 + 9.3
Thanks
Vlk
Another way of ensuring the clients can see the new AMS is to run a script on either logon or manually to call the Avast function which changes the AMS location within the client configuration(AswChAMS). Like so…
C:\Program Files\Alwil Software\Avast4\AswChAMS /YOUR_AMS_NAME_HERE