W32.Downadup.B Arghhhhhhhh


It's been 6 years since we were last hit by a major virus, but we have just been hit again (along with a few million others) by W32.Downadup.B

What did it do?: It removed ability of users to log-in to the domain. The following entry appeared in droves on domain controller; "The SAM database was unable to lockout the account of Administrator due to a resource error, such as a hard disk write failure (the specific error code is in the error data) . Accounts are locked after a certain number of bad passwords are provided so please consider resetting the password of the account mentioned above." with an event ID of 12294. At the peak we were probably experiencing around 100 per second.

The end result of the above was that due to the sheer number of requests, active directory was unable to authenticate genuine users....who were getting their account locked instead of getting logged in. Ironically this wasnt the main intension of the virus, just a side effect. In actual fact the virus looks to upload any passwords it finds to a remote server. In order to avoid detection the writers made it upload to a few thousand random domain names to avoid detection by the authorities.

Some more info;
http://www.microsoft.com/security/portal/Entry.aspx?Name=Worm%3aWin32%2fConficker.B

How did we get rid of it?: Firstly we had to disable every single account on the domain with local or domain/enterprise security rights. You can imagine the hassle this is going to cause in terms of service run-as issues. We also had to unplug any administrative workstations from the network and run all fixes direct from the servers.

Micrsoft have provided a tool for prevention, also provided in the form of a windows update (should you happen to do those on a weekly basis);

http://support.microsoft.com/kb/891716

They do however suggest that deployment via Group Policy is not suitable for servers, and kindly provide a handy 36!! step manual process. You can however reduce this to around 5 steps by using Symantec Antivirus, a bit of quick registry editing, and the removal tools.....probably 15 minutes per server. I'd also suggest regular password changing of any admin account you are using, just to ensure that it isnt grabbed and used by an infection.

The only method we have found thus far to remove the threat from an infected PC is to perform a full system scan using Symantec AV. Not great for the users given the load it puts on the workstations, but at least its a fix!

I'm sure this wont be the last such threat, and its been our first since moving to Active Directory.... but I'll be looking into how we can deploy windows updates using SCCM2007 on a regular basis!

Server 2008 Firewall Woes

We have just been working on a niggly problem. We were trying to connect a spare nic in a Server 2008 server to a development network. The development network is currently just a switch with nothing else connected.

As soon as the second nic was plugged in, we lost all connectivity to the server from the main nic, and even lost ability to ping the server.

After a bit of head scratching we realised that although Windows Firewall was turned off, as soon as the second nic was plugged in the Firewall turned itself back on.... thus blocking pings and RDP.

Simple solution was obviously to plug in the connection, and then disable firewall.

VMM2008 SSP - Shared ISOs

We have noticed that when Self Service Portal users are trying to alter the properties of one of their VMs, they have an option to mount an ISO. Down at the bottom of the options is a tick box which says "SHARE" rather than copy.

Normally if you mount an ISO, the ISO file will be copied into a subfolder of the VM before it is mounted. For a 4Gb ISO files (such as SuseLinux) this can take several minutes. So the obvious advantage of using the SHARE option is that it just uses the original ISO rather than creating a copy.

However....there is a catch. The option isnt available if your host if a Hyper-V server. I have logged this with MS via Technet; http://forums.microsoft.com/TechNet/showpost.aspx?postid=4167342&siteid=17

It seems to be a known issue, but as yet they havent given a resolution date.

Dev Con & Dell

We have been having a serious issue with our latest Dell 755s. These PCs come with a built in 4 slot card reader. The A: drive is reserved for a floppy, C: is the local HDD, D: is taken by the DVD drive, leaving E, F, G & H for the card reader. I imagine 90% of network admins have set the users home area to default to H: which obviously causes a major problem when the user tries to log-in to a machine with a card reader. As a short term fix we have used a MS tool called devcon, which can disable devices from the command line. Ill post an update when we find a more long term solution.

VMM2008 Slow Creating VMs


Following on from a previous post on this topic, I have finally (after around 6 weeks of trying) been able to find a resolution to the issue I previous posted about here.

It turns out this this was not actually an issue with VMM being slow installing VM Components. VMM was actually being slow at reading the drives on the host server. thankfully someone from Microsoft jumped onboard (thanks Hector Linares), and was able to confirm that VMM2008 does have this issue if any of the following conditions are met;

VIRTUAL MEDIA: If the host server has any virtual media such as a Dell DRAC or Virtual Floppy.

GPT DISK: If any drives in the host server are using GPT Partition table rather than MBR

UNINITIALIZED DISK: If any of the disks are not initialized.

OTHER MOUNTED VHDs: If a VHD has mounted incorrectly or not dismounted correctly.

In our situation the problem was actually related to GPT. The server has 3 drives, 2 set up as MBR and one set up as GPT. Converting the one GPT disk to MBR instantly fixed the problem, and VMM now creates VMs in under 10 seconds.

As a side note, GPT drives was introduced by MS in Server 2003 SP1, but is really being pushed with server 2008. See this article by MS.

Hopefully MS will have a fix soon, but as of Nov 2008 there is no way of converting an MBR disk to GPT without loosing the data.

Dell's Wonderful Utility Partition

If you have installed and configured a Dell Poweredge Server, you may have noticed a "utility" partition which exists on the system drive....in our our case on the RAID 1 mirror which is our system drive.

For reasons I wont go into, it was suggested that we remove the dell system partition. The Server is a 2008 build, where the partition simply shows up in Storage Management, but you are unable to edit or delete it from there.

Dell's solution was to rebuild the entire server including OS. Great....

I decided there must be a quicker way so had a little expriment with DISKPART. Diskpart is a command line tool which allows you to foricbly remove a partition. As long as you are not trying to force remove a partition within a dynamic disk, this is a fairly straight forward process and is supposed to leave the rest of the drive (or mirror) in tact.

To cut a long store short....dont use DISKPART to force remove a DELL utility partition, it doesnt work, and it will leave you having to rebuild all the data contained on the same drive. Considering the Dell Utility Partition only contains data which is on a normal Dell boot CD, I really cant see the point in it.

DFS Paths For All


We have recently introduced DFS paths onto the network, which offers some significant advantages over standard UNC paths. For those who dont know about DFS;

Click Here

In short.... DFS introduces virtual paths for AD users. Rather than have users going to a path such as "\\ServerName\\volume\file.doc", your users will go to a path such as "\\domain.com\storage\file.doc". The advantage to be gained certainly isnt in path lengths, but in the administration of the paths.

For example, lets say everyones home area points to "\\london\home\userid", and for whatever reason the server "london" is removed from the network. Not only do the files have to be restored to a new location, but everyones paths are going to have to point to the new locations. This includes their home area path, their profile path, and more importantly any links the users has in documents, spreadsheets or databases.

With DFS paths everyones home area can be directed to "\\domain.com\home\userid", and the same with their profile and any Group Policy directed folders. The user is still effecticvely pointing to a serevr, but as this is now being done dynamically if the server goes offline or the data ius migrated, all that needs changing is the DFS pointer. Brilliant.



There are some other advantages such as syncronisation and high-availablity, and I plan to look into these in the near future.

I should also point out another handy tool from Doverstones, which is AD-Find & Replace. This works in the same way as notepad's find & replace for example, but on Active Directory objects. So, if you need to change home area paths for thousands of users, this tool can do it in seconds;

Click Here