Zotob.b cleanup
|
Logged in as: Guest
|
|
Users viewing this topic:
none
|
|
Login | |
|
Zotob.b cleanup - 17.Aug.2005 10:02:00 AM
|
|
|
dmckenna
Posts: 1
Joined: 16.Aug.2005
From: Newcastle Upon Tyne
Status: offline
|
I am new to LNSS, just evaluated today and purchased to help with Zotob.b cleanup on 1,400 PCs!
We have got the trial version working, but bearing in mind we've only used the software for 1 day wondered if any vetrans could advise a smoother way to deploy required patches.
We need to deploy the following:
-WIN2K SP4 (installed on about 75% of PC but not all) -MS05-039 PATCH (PC must have SP4 installed first) -zotobfix.exe (Symantec cleanup program).
At present we are running 3 scans/deployments:
1st = detect PCs without SP4 and install. 2nd = detect PCs without MS05-039 and install 3rd = run Zotobfix.exe
We have customised to scan to a minimum and that works quite quickly. We are doing this across small ranges at a time to keep traffic down on WAN and have to repeat 2nd and 3rd scans twice to catch those PCs being upgraded to SP4.
Is there anyway we can speed this up? Eg would it be possible to deploy a custom script to check SP version and install SP4 if needed, then install MS05-039 and run Zotobfix?
I'm not looking for an exact answer, but a pointer in the right direction and advice on which bit of LNSS would do this would be really helpful given our lack of experience of the product and limited time to investigate.
Many thanks.
|
|
|
|
RE: Zotob.b cleanup - 17.Aug.2005 10:35:00 AM
|
|
|
xnih
Posts: 2465
Joined: 30.May2001
From: Idaho
Status: offline
|
you need to do the reboot between SP4 install and the hotfix, granted if you are moving up to SP4 you are going to be missing more than just MS05-039 on those machines.
You can look at doing custom patches and push MS05-039 and the fix in the same time with a call to reboot.exe to end it all off since you'll need to actually do the reboot to get the new .dll's installed by MS05-039 up and functional. So the problem may come up that you run the Zotobfix.exe and it could get reinfected since you won't have done the reboot and got the new .dlls in place.
So if you want to attempt custom patching you can look at some of the articles I did back in 3.x days that still apply: http://myweb.cableone.net/xnih look under Advanced LNSS Options
Though I don't know if that is the best idea, as noted above, but you are welcome to try.
In a nutshell, create a batch file that calls 3 files: 1. MS05-039 2. zotobfix.exe 3. reboot.exe
eric
|
|
|
|
RE: Zotob.b cleanup - 25.Aug.2005 7:32:00 AM
|
|
|
mkogrady
Posts: 6
Joined: 17.Mar.2005
Status: offline
|
Our network folks packaged a hotfix that combined the two patches together so only one reboot was required. Then the stinger tool was run against the machines to make sure it resolved the problem.
|
|
|
|
New Messages |
No New Messages |
Hot Topic w/ New Messages |
Hot Topic w/o New Messages |
Locked w/ New Messages |
Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|