the server that I had ADNM with msde on it died.
I install ADNM again with msde (new database) on a new server.
Configured most of the settings I could remember, which didn’t take too long.
Ran a discovery task and had all clients go into a group I created under the computer catalog.
The problem is they were discovered yet all show up greyed out with listed for VPS version and Engine version.
My old computer catalog I remember had the check box UNCHECKED for “Try to find an alternative server if unavailable”.
I had it like that because of an issue with another site that is connected via VPN.
Is that setting going to kill me here? Will these clients never find this new server now unless I reinstall them all? That would be really painful.
You don’t have to reinstall the clients - but still, I’m afraid you’ll have to force them use the new server.
The easiest solution would be to have the new server have the same IP address as the old one. In that case, the clients should catch up automatically.
If that cannot be the case, you’ll have to use the aswChAms.exe tool (on each of the clients). It’s used like this
aswChAms.exe name_of_new_AMS
where name_of_new_AMS is either the IP address or the DNS name of the new AMS.
You can have the command run e.g. from the logon script, but note that it must be run under an admin account for it to work properly.
thanks.
Looks like I need that tool but for the life of me I can’t find it.
Doesn’t seem to exist on the ADNM server and I can’t find it on avast.com.
Any pointers?
Also I can leave the login script there for like a week with no ill effects correct? Just to make sure I got everyone as we have people in and out and various times.
wait a minute…
lets say i could get the old server up one more time…
would that solve my problem too? If i could get into the old one, once more, can I tell all the clients who still expect to talk to it to go and talk to the other AMS and push that setting out?
How would I do that if possible?
then I can see if they start showing up on the new AMS?
maybe still do the login script but would that help?
Looks like I need that tool but for the life of me I can't find it.
Doesn't seem to exist on the ADNM server and I can't find it on avast.com.
Any pointers?
LOL, it’s part of the avast netclient/netserver installation.
C:\Program Files\ALWIL Software\Avast4, usually. On the managed clients, of course…
Also I can leave the login script there for like a week with no ill effects correct? Just to make sure I got everyone as we have people in and out and various times.
Absolutely, the program just changes a couple of registry and INI file entries, it’s super-fast and it doesn’t hurt if you run it multiple times.
lets say i could get the old server up one more time...
would that solve my problem too? If i could get into the old one, once more, can I tell all the clients who still expect to talk to it to go and talk to the other AMS and push that setting out?
How would I do that if possible?
Yes, this should also work.
Turn on the old AMS. Then in the Computer Groups’ properties, change the AMS Address field (to point to the new AMS). Then do “Apply on Group” (i.e. force the server to distribute the new settings immediately), wait for a couple of minutes and you should be all set.
ah. my bad. thanks.
so many have moved over now by bringing up the old ams once more. I’ll do the login script to get the rest. One weird thing though I ran the aswchams on a server and it said it was already on the correct AMS (the new one). but in the new ams it is still grey but has a yellow key icon on it.
What is the problem there?
3 of my server are green, 3 have the yellow key on them and 2 are still grey altogether.
My 3rd wave of offense for some machine’s is to run a deployment task on some. Some machines are still gray in the ams and they are sitting on my network powered on. So I ran a deployment task. On some it works on others it doesn’t:
One client gets this:
10/31/07 13:21:40: D800: ReadProgress
10/31/07 13:21:40: D800: Remote setup failed, error 0x2000000A (Error 0x2000000A.)
10/31/07 13:21:40: D800: Finished with error in remote setup
10/31/07 13:21:40: D800: ReadLog
10/31/07 13:21:40: D800: Remote log: C:\Program Files\Alwil Software\Management Tools\DATA\log\D800.log
10/31/07 13:21:40: D800: RemoveProgress
10/31/07 13:21:40: D800: CloseConnection
10/31/07 13:21:40: TerminateAll
10/31/07 13:21:40: rinstInstall end 0
One server gets this:
10/31/07 13:24:13: server: ReadProgress
10/31/07 13:24:13: server: Remote setup failed, error 0x20000016 (Error 0x20000016.)
10/31/07 13:24:13: server: Finished with error in remote setup
10/31/07 13:24:13: server: ReadLog
10/31/07 13:24:13: server: CopyFile \server\C$~AVINSTL\Setup.log C:\Program Files\Alwil Software\Management Tools\DATA\log\server.log error 2 (The system cannot find the file specified)
10/31/07 13:24:13: server: RemoveProgress
10/31/07 13:24:13: server: CloseConnection
10/31/07 13:24:13: TerminateAll
10/31/07 13:24:13: rinstInstall end 0
Error 0x2000000A means that another instance of setup is already running, maybe retrying after a while will help.
Error 0x20000016 means that operating system does not meet minimal requirements. You are probably installing avast! PRO to a server OS which is not possible. Use installation package with avast! Server.
