Updating while NT clients logged out

[talcs]

I have installed EPO on a 2k server and run my updates weekly. When running updates, unless the WinNT clients are logged in, they will not update. This happens only with the NT clients. 2000 and XP work okay. All clients are on the domain. Any ideas?

 

[nmandersloot]

Did you configure your updates via UNC path? In that case validation is necessary and updating may fail if clients are not logged on to the network. You can try updates via FTP

 

[talcs]

The updated dat's are pushed from the server. Therefore no configuration should be necessary as far as I understand. That should only apply if each client does it's own update. Is that correct?

 

[VictorySabre]

DATs aren't pushed out from the server. Usually the clients pull the DATs from the server. If you are using the UNC path and have certain access restrictions on the permissions, you will need to define the account to be used to access that UNC path.

 

[talcs]

I'm sorry, but I was under the impression that the dat's were pushed. Haven't used EPO before, but that just seems silly. You will have to update each PC manually with UNC path and login details (or ftp path) or is there an easier method of defining this. I know ftp is the default, but what if I don't want the clients to go outside the firewall. Will this require manual change. Thanks

 

[mastermind76]

Your clients don't have to leave your LAN. If you are using VS 7.0, you'll have to use AutoUpdate Architect 1.0 in order to have your clients perform a DAT update. If your using earlier versions of VirusScan you could also have on server download the files to a shared folder and configure a task in the epo to have clients download the DAT update from that shared folder. If you have problems accessing the shared folder from NT clients, try creating a null-session-share on the server. After creating a NSS, login information are not needed for NT clients accessing the share. This should solve the problem, but leaves a backdoor open.
Hope it helps.

 

[talcs]

Thanks. Will give it a try

 

[VictorySabre]

In regards to the UNC connection for DAT updates, you can use ePO to configure the AutoUpdates to use the UNC connection and then specify the username, password, and domain that is to be used to connect to the share. You won't need to go to each PC and configure that manually.

Once you enter that information into the AutoUpdate entries in ePO, the clients pull this information during it regular communications interval and sets its tasks up using the configuration you set up.