Windows Server 2000/2003 Thread, AT1.job Scheduled task in Technical; Well it's been months now and we have stopped Conficker from spreading and we even know how to remove it ...
16th October 2009, 09:04 AM #16
Well it's been months now and we have stopped Conficker from spreading and we even know how to remove it by being methodical. Our only problem is now that we are having a problem with some of the machines are not being seen in the WSUS console. This maybe a different problem entirely because we have totally removed Conficker from the affected machines.
We have tried the wuauclt /detecnow and wuauclt /resetauthorization /detectnow commands which have worked for other machines. Any suggestions?
15th February 2010, 01:30 PM #17
- Rep Power
I have exactely the same problem :
At1.job, At2.job,... on many computers of the domain... (I already clean them why removal conficker tool)
And also some computers are not visible in the WSUS !
Have you find a solution ?
16th February 2010, 09:01 AM #18
We did a few things like
Disable Autorun in Group Policy
Disable Scheduled Tasks being created or edited through Group Policy
and a few other little things that i can not remember off the top of my head. but Symantec relaesed a good little guide to stopping conficker.
it makes good reading i would advise you have a look if you havnt already.
Stop Conficker from spreading by using Group Policy | Symantec Connect
16th February 2010, 03:35 PM #19
- Rep Power
Thank you, i will try this..
By FN-GM in forum Scripts
Last Post: 2nd May 2009, 07:17 PM
By adamf in forum Windows
Last Post: 1st December 2008, 11:00 AM
By Stuart_C in forum Windows
Last Post: 25th November 2008, 10:27 AM
By Jobos in forum Windows
Last Post: 30th April 2008, 03:16 PM
By Ste_Harve in forum How do you do....it?
Last Post: 14th September 2007, 02:04 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)