[osiris] Re: New config for client not pushing

[scott.brehm at l-3com.com]

Followup.

I finally found the file saved by new-config in it's hosts\xxx\configs
directory. Duh.

I also forgot to add that the event log on the client did show all the
activity about the config being pushed and dropped, etc.

I was finally able to get my client to use the new config by using the
init command on it. Scans are now using the new config file and the
status output confirms the configuration ID is for the expected file.

I'd still like to know what I may have been doing wrong with
push-config. I've been going a bit deeper and by checking the hex
configuration codes from list-configs I can see that the configuration
id shown by the status command has the correct id for the config I just
pushed, but after setting the host, print-config doesn't show the
content of that one unless I include the config name, and edit-config
pulls up the same incorrect config.


- Scott
 

> -----Original Message-----
> From: Brehm, Scott @ ATD 
> Sent: Wednesday, August 29, 2007 10:40 AM
> To: osiris at lists.shmoo.com
> Subject: New config for client not pushing
> 
> I can't get a new configuration pushed to a client. I 
> originally set up my first client with 
> default.windowsserver2003, but I found it pointing to 
> c:\winnt. The client has c:\windows. I was also getting 
> alerts on the Symantec virusdefs folder, so I copied the 
> default config to another file, made my change for c:\windows 
> and added a NoEntry for the virusdefs file. It verified so I 
> set the host to my client and used push-config. The response 
> said it was pushed, but verify-config names the original 
> default config as valid and print-config shows the lines from 
> the default config. A scan shows it still using 
> default.windowsserver2003. 
> 
> I tried to drop-config, which reported success, then 
> push-config, which also reported success, and it's still 
> using the default.
> 
> I tried new-config, got a notepad popup, edited and saved my 
> revised config. The command reported success but I can't find 
> the new config file anywhere and the client is still using 
> the default.
> 
> I created a c:\windows\osiris\configs directory on the 
> client, stuck a copy of config in there and restarted the 
> service. It still used the default.
> 
> I'm out of things to try. I'm running 4.2.3 downloaded from 
> shmoo.com with the management console on Windows 2000 and my 
> test client on Windows 2003.
> 
> Scott Brehm
> 
> IT Manager
> L-3 Communications - Applied Technologies
> 3394 Carmel Mountain Rd, San Diego CA, 92121
> 858-720-4035
> 
>