Issues deploying clients unattended

Hi

I’m still trialling Enpoint Protection+, which so far is proving OK. However I’m having a seemingly minor issue when doing an unattended deployment. This didn’t happen at first, but for the last couple of deployments has happened each time.

Basically, the deployment starts, the client gets installed on the remote machine which then reboots. After logging in again you get the “Welcome to Avast” message and it is registered in the SOA. So seemingly everything is fine. The problem is the job in the scheduler is stuck at 11% and is not moving to “complete” it in the console. I left it for an hour and nothing changed. Eventually the job status shows as failed although there is a notification in the dashboard which says deployment was successful.

Looking in the install log, it shows copying all the files, shows “ReadProgress” whilst incrementing a percentage, when it gets to 70% it states “Progress not available (64) - may be restarting” (which pretty much ties in with the machine rebooting), it then repeats:

08/27/14 09:27:14:   WST-005: Progress not available (64) - may be restarting
08/27/14 09:27:14:   WST-005: Unknown state
08/27/14 09:27:24:   WST-005: ReadProgress
08/27/14 09:27:24:   WST-005: Progress not available (64) - may be restarting
08/27/14 09:27:24:   WST-005: Unknown state
08/27/14 09:27:34:   WST-005: ReadProgress
08/27/14 09:28:17:   WST-005: Progress not available (64) - may be restarting
08/27/14 09:28:17:   WST-005: Timeout expired
08/27/14 09:28:17:   WST-005: Finished with error in remote setup
08/27/14 09:28:17:   WST-005: ReadProgress
08/27/14 09:28:17:   WST-005: Progress not available (64) - may be restarting
08/27/14 09:28:17:   WST-005: Unknown state
08/27/14 09:28:27:   WST-005: ReadProgress
08/27/14 09:28:27:   WST-005: Progress not available (64) - may be restarting
08/27/14 09:28:27:   WST-005: Unknown state
08/27/14 09:28:37:   WST-005: ReadProgress
08/27/14 09:28:37:   WST-005: Progress not available (64) - may be restarting

until after over an hour:

08/27/14 10:12:26:   WST-005: Progress not available (64) - may be restarting
08/27/14 10:12:26:   WST-005: Unknown state
08/27/14 10:12:36:   WST-005: ReadProgress
08/27/14 10:12:59:   WST-005: Finished OK
08/27/14 10:12:59:   WST-005: RemoveProgress
08/27/14 10:12:59:   WST-005: Folder \\WST-005\C$\~AVINSTL not removed: 145
08/27/14 10:12:59:   WST-005: CloseConnection
08/27/14 10:12:59:   TerminateAll
08/27/14 10:12:59:   rinstInstall end 0

This was after rebooting the client machine again. Is there something which may be blocking the signal for completion? Or is it something on the client not working quite right? The clients were previously using AIS which was uninstalled and before deploying the windows firewall was turned off completely.

Thanks

Did you check if all the needed firewall ports on the client (and server) are open so the communication between both can happen?

Windows firewall was completely disabled before attempting the deployments. The machine with SOA was unchanged from when it previously seemed to work. As it seems to have successfully done the actual installation (seen by the auto-reboot and the fact the client started up) if anything was blocking the signal, it would have been Avast’s firewall - which would be a bit silly of it!

Anyway, the trial is over now and I had a few other issues (which again, may have come from having AIS previously) with connections to IMAP, so I’m going to trial a couple of other systems and see who wins before laying down the company’s limited money .

Hey Daren,

If you have had a previous installation from other Avast products (with or without firewall) or other AV product, did you use the special removal tools from those installations? Avast and the other vendors created special removal tools to completely uninstall the products, this is needed since a regular install never has removed everything and can create this kind of problems…

Can you try deploying with a completely clean installation ? Maybe inside a virtual machine?

I did know about avastclear, but at the time I (possibly incorrectly) presumed as I was “upgrading” there would be no issues, and for the first couple of trial deployments, there wasn’t.

Anyway, as I mentioned, the trial has expired so I’m unsure whether it would allow me to push any more deployments and I have already installed others for now. I may still come back to Avast, but for now it’s on the back-burner.

Thanks for your ideas anyway.