If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Conficker infection on network - advice wanted on removal/protection
I posted a few weeks ago but have done some further work/consideration
about this issue. I've just taken on a new client whose network has been left in pretty bad shape by their previous IT support provider. They have approximately 11 XP workstations and 1 SBS 2003 DC. To sum up the state they're in: - No server or workstation Windows Updates installed for a very long time (still on XP SP2) - AVG Personal Edition on all workstations, AVG SBS on the server but expired May 2010. - No logon passwords needed/very poor passwords on workstations - Conficker virus infection on all computers. The previous IT firm seemed to give up on the client once they knew they had a Conficker infection. I want to rid them of the Conficker virus first of all. My plan of attack is as follows:- One workstation at a time: 1. Format the workstation. Reinstall Windows. 2. Install all available Windows Updates. 3. Install business class anti-virus software 4. Implement additional protection to prevent reinfection (see below) 5. Ensure complex logon password 6. Join the workstation back into the domain and configure for the user. By doing this I'm hoping to gradually one workstation at a time eradicate the virus from the network and prevent reinfection once the workstation is re-introduced to the network. Additionally doing one at a time to prevent mass downtime. The advice I would appreciate from you guys is: 1. I want to PREVENT re-infection. This is crucial. As well as updates and AV software I plan on doing the following: - Complex local admin password - Block Autorun Is there anything else I can do on the workstation before reintroducing it to the network to PREVENT reinfection? 2. Is this the most effective method of removing the virus from the whole network? Thanks in advance. |
Ads |
#2
|
|||
|
|||
Conficker infection on network - advice wanted on removal/protection
Part of the problem here is that by doing one at a time...when you reintroduce it to the network..it risks reinfection by another workstation
Is the server infected You should go here http://support.microsoft.com/kb/962007 and follow the instructions It may not be required to format each machine unless you think there is more going on. After you've taken all the steps in the KB...run Malwarebytes at Malwarebytes.org and find out whatelse you've got to deal with I'm not a big fan of expecting the virus to be dealt with once it gets into the network...I'd much rather it be dealt with by blocking it from ever getting to the network. A good UTM Firewall will do this...think of it as the Moat around the Castle Then consider ForeFront Client Security on the workstations...can be updated by Windows Update or WSUS -- Cris Hanna [SBS - MVP] (since 1997) Co-Contributor, Windows Small Business Server 2008 Unleashed http://www.amazon.com/Windows-Small-...69967&sr= 8-1 Owner, CPU Services, Belleville, IL A Microsoft Registered Partner ------------------------------------ MVPs do not work for Microsoft Please do not submit questions directly to me. "eggedd2k" wrote in message ... I posted a few weeks ago but have done some further work/consideration about this issue. I've just taken on a new client whose network has been left in pretty bad shape by their previous IT support provider. They have approximately 11 XP workstations and 1 SBS 2003 DC. To sum up the state they're in: - No server or workstation Windows Updates installed for a very long time (still on XP SP2) - AVG Personal Edition on all workstations, AVG SBS on the server but expired May 2010. - No logon passwords needed/very poor passwords on workstations - Conficker virus infection on all computers. The previous IT firm seemed to give up on the client once they knew they had a Conficker infection. I want to rid them of the Conficker virus first of all. My plan of attack is as follows:- One workstation at a time: 1. Format the workstation. Reinstall Windows. 2. Install all available Windows Updates. 3. Install business class anti-virus software 4. Implement additional protection to prevent reinfection (see below) 5. Ensure complex logon password 6. Join the workstation back into the domain and configure for the user. By doing this I'm hoping to gradually one workstation at a time eradicate the virus from the network and prevent reinfection once the workstation is re-introduced to the network. Additionally doing one at a time to prevent mass downtime. The advice I would appreciate from you guys is: 1. I want to PREVENT re-infection. This is crucial. As well as updates and AV software I plan on doing the following: - Complex local admin password - Block Autorun Is there anything else I can do on the workstation before reintroducing it to the network to PREVENT reinfection? 2. Is this the most effective method of removing the virus from the whole network? Thanks in advance. |
#3
|
|||
|
|||
Conficker infection on network - advice wanted on removal/protection
thanks for your response on this.
Yes the server is infected. Having thought this through it's clear that by doing one system at a time there is a risk of reinfection when the cleaned workstation is joined back into the network. The Microsoft link you posted is of great help and this is clearly the path to go down: 1. Stop Conficker from spreading via group policy. 2. Clean each system with AV/Malwarebytes/Malicious Software Removal tool thanks again for your help on this! |
#4
|
|||
|
|||
Conficker infection on network - advice wanted on removal/protection
Especially with the server also infected how will you be sure that all
infections are totally removed without also reformatting the server and reinstalling SBS? "eggedd2k" wrote in message ... thanks for your response on this. Yes the server is infected. Having thought this through it's clear that by doing one system at a time there is a risk of reinfection when the cleaned workstation is joined back into the network. The Microsoft link you posted is of great help and this is clearly the path to go down: 1. Stop Conficker from spreading via group policy. 2. Clean each system with AV/Malwarebytes/Malicious Software Removal tool thanks again for your help on this! |
#5
|
|||
|
|||
Conficker infection on network - advice wanted on removal/protection
I have to agree If server and workstations are infected...I'd flatten everything and start over...or you risk just reinfecting all over again
-- Cris Hanna [SBS - MVP] (since 1997) Co-Contributor, Windows Small Business Server 2008 Unleashed http://www.amazon.com/Windows-Small-...69967&sr= 8-1 Owner, CPU Services, Belleville, IL A Microsoft Registered Partner ------------------------------------ MVPs do not work for Microsoft Please do not submit questions directly to me. "SteveB" wrote in message ... Especially with the server also infected how will you be sure that all infections are totally removed without also reformatting the server and reinstalling SBS? "eggedd2k" wrote in message ... thanks for your response on this. Yes the server is infected. Having thought this through it's clear that by doing one system at a time there is a risk of reinfection when the cleaned workstation is joined back into the network. The Microsoft link you posted is of great help and this is clearly the path to go down: 1. Stop Conficker from spreading via group policy. 2. Clean each system with AV/Malwarebytes/Malicious Software Removal tool thanks again for your help on this! |
#6
|
|||
|
|||
Conficker infection on network - advice wanted on removal/protection
On 9/9/2010 10:10 AM, eggedd2k wrote:
I posted a few weeks ago but have done some further work/consideration about this issue. I've just taken on a new client whose network has been left in pretty bad shape by their previous IT support provider. They have approximately 11 XP workstations and 1 SBS 2003 DC. To sum up the state they're in: - No server or workstation Windows Updates installed for a very long time (still on XP SP2) - AVG Personal Edition on all workstations, AVG SBS on the server but expired May 2010. - No logon passwords needed/very poor passwords on workstations - Conficker virus infection on all computers. The previous IT firm seemed to give up on the client once they knew they had a Conficker infection. I want to rid them of the Conficker virus first of all. My plan of attack is as follows:- One workstation at a time: 1. Format the workstation. Reinstall Windows. 2. Install all available Windows Updates. 3. Install business class anti-virus software 4. Implement additional protection to prevent reinfection (see below) 5. Ensure complex logon password 6. Join the workstation back into the domain and configure for the user. By doing this I'm hoping to gradually one workstation at a time eradicate the virus from the network and prevent reinfection once the workstation is re-introduced to the network. Additionally doing one at a time to prevent mass downtime. The advice I would appreciate from you guys is: 1. I want to PREVENT re-infection. This is crucial. As well as updates and AV software I plan on doing the following: - Complex local admin password - Block Autorun Is there anything else I can do on the workstation before reintroducing it to the network to PREVENT reinfection? 2. Is this the most effective method of removing the virus from the whole network? Thanks in advance. Call Microsoft security at 1-800-Microsoft and ask for their CSS security team for Conficker and they will help you with what to do. Apologies for this... but please repost to www.sbsforum.info this newsgroup is closing tomorrow. |
#7
|
|||
|
|||
Conficker infection on network - advice wanted on removal/protection
On Sat, 11 Sep 2010 18:30:11 -0700, Susan Bradley
wrote: snip Apologies for this... but please repost to www.sbsforum.info this newsgroup is closing tomorrow. While some servers may drop the newsgroup (you didn't identify which of the three you meant), it will have no affect on the other servers that carry it. -- Remove del for email |
#8
|
|||
|
|||
Conficker infection on network - advice wanted on removal/protection
On 9/12/2010 12:06 PM, Barry Schwarz wrote:
On Sat, 11 Sep 2010 18:30:11 -0700, Susan Bradley wrote: snip Apologies for this... but please repost to www.sbsforum.info this newsgroup is closing tomorrow. While some servers may drop the newsgroup (you didn't identify which of the three you meant), it will have no affect on the other servers that carry it. The reality is that many of us will not find another nntp server, so if you want the largest pool of helpers, this is the reality. |
#9
|
|||
|
|||
Conficker infection on network - advice wanted on removal/protection
Susan Bradley wrote:
On 9/12/2010 12:06 PM, Barry Schwarz wrote: On Sat, 11 Sep 2010 18:30:11 -0700, Susan Bradley wrote: snip Apologies for this... but please repost to www.sbsforum.info this newsgroup is closing tomorrow. While some servers may drop the newsgroup (you didn't identify which of the three you meant), it will have no affect on the other servers that carry it. The reality is that many of us will not find another nntp server, so if you want the largest pool of helpers, this is the reality. http://www.aioe.org/ nntp.aioe.org is available, with no registration required. You can start using it immediately. I'm posting from it right now. The reason the owner can afford to do it, is his NNTP server does not support binaries or movie downloads. Paul |
#10
|
|||
|
|||
Conficker infection on network - advice wanted on removal/protection
On Sun, 12 Sep 2010 14:48:46 -0700, Susan Bradley
wrote: On 9/12/2010 12:06 PM, Barry Schwarz wrote: On Sat, 11 Sep 2010 18:30:11 -0700, Susan Bradley wrote: snip Apologies for this... but please repost to www.sbsforum.info this newsgroup is closing tomorrow. While some servers may drop the newsgroup (you didn't identify which of the three you meant), it will have no affect on the other servers that carry it. The reality is that many of us will not find another nntp server, so if you want the largest pool of helpers, this is the reality. If you are using a newsreader (as opposed to a web browser), there are several servers that are either free or have one time fees of less than US $10. -- Remove del for email |
#11
|
|||
|
|||
Conficker infection on network - advice wanted on removal/protection
Sure we could switch to something else but why bother? As Susan points out
you will receive only very limited responses to questions and most of the pool of well qualified respondents such as SBS MVPs and Microsoft personnel will all be using the new forum. That forum is also easily accessed by an NNTP reader using the community bridge. Steve "Barry Schwarz" wrote in message ... On Sun, 12 Sep 2010 14:48:46 -0700, Susan Bradley wrote: On 9/12/2010 12:06 PM, Barry Schwarz wrote: On Sat, 11 Sep 2010 18:30:11 -0700, Susan Bradley wrote: snip Apologies for this... but please repost to www.sbsforum.info this newsgroup is closing tomorrow. While some servers may drop the newsgroup (you didn't identify which of the three you meant), it will have no affect on the other servers that carry it. The reality is that many of us will not find another nntp server, so if you want the largest pool of helpers, this is the reality. If you are using a newsreader (as opposed to a web browser), there are several servers that are either free or have one time fees of less than US $10. -- Remove del for email |
#13
|
|||
|
|||
Conficker infection on network - advice wanted on removal/protection
In article ,
says... On 9/12/2010 12:06 PM, Barry Schwarz wrote: On Sat, 11 Sep 2010 18:30:11 -0700, Susan Bradley wrote: snip Apologies for this... but please repost to www.sbsforum.info this newsgroup is closing tomorrow. While some servers may drop the newsgroup (you didn't identify which of the three you meant), it will have no affect on the other servers that carry it. The reality is that many of us will not find another nntp server, so if you want the largest pool of helpers, this is the reality. I think the reality is that Usenet was around long before MS even learned about email or the Internet and will be around long after it. The forums are a bad way and cumbersome. -- You can't trust your best friends, your five senses, only the little voice inside you that most civilians don't even hear -- Listen to that. Trust yourself. (remove 999 for proper email address) |
#14
|
|||
|
|||
Conficker infection on network - advice wanted on removal/protection
On Sun, 12 Sep 2010 14:48:46 -0700, Susan Bradley
wrote: On 9/12/2010 12:06 PM, Barry Schwarz wrote: On Sat, 11 Sep 2010 18:30:11 -0700, Susan Bradley wrote: snip Apologies for this... but please repost to www.sbsforum.info this newsgroup is closing tomorrow. While some servers may drop the newsgroup (you didn't identify which of the three you meant), it will have no affect on the other servers that carry it. The reality is that many of us will not find another nntp server, so if you want the largest pool of helpers, this is the reality. Not find another nntp....compared to which? I'm guessing you conect to a Microsoft NNTP server, but I bet most don't. I personally do not like the Microsoft forums, I prefer NNTP. Jim |
Thread Tools | |
Display Modes | |
|
|