MMC SNAP-IN ERROR

When you install Windows 2003 SP2 or SBS Server R2 you might get errors when you run the Microsoft Management Console. When you open MMC snap-ins, in my case System Manager for Exchange 2003 Server, you will see an error "MMC has detected an error in snap-in. It is recommended you shutdown and restart MMC". According to Microsoft, the source of the problem is that the snap-in is not fully compatible with MMC 3.0, and you most likely have already realized that both Windows 2003 Service Pack 2 and the SBS 2003 R2 Technologies install MMC 3.0. In some of Microsoft's solutions they say you choose the option to ignore and continue running. For POP3 Connector error the hot fix is available through Microsoft updates. Open these URL for instructions; http://support.microsoft.com/default.aspx?scid=kb;EN-US;921096 and http://support.microsoft.com/kb/947532/en-us . Why Microsoft doesn’t get these fixes patched to the software l wonder. We spend a hell lot of time on the Microsoft support website trying to get a solution and it’s so frustrating.

Task Offloading in Windows

Task offloading to Network Interface Card in Windows is whereby the TCP protocol can offload some of the tasks that are being processed by the system processor. In Windows SBS this feature should be disabled. Couple of network configuration errors will arise if its enabled. Microsoft has a special tool called Windows SBS Server 2003 Best Practices Analyzer, which scans the whole system for errors. And if Task Off Loader is not disabled you will see it on critical error reports. A solution to disable it will be provided in the critical error reports. Microsoft will direct you on how to download the hot fix which will disable the feature. The lesson is, if you run the fix it won’t disable it because it’s not in the registry TCPIP entries. So first you have to edit the registry and manually include DisableTaskOffloader entry in the TCPIP- Parameters and set its value to “1”. Follow this registry key: HKey-Local Machine, System, Current Control Set, Services, TCPIP, Parameters . Issues that may arise can be found by following this link http://support.microsoft.com/kb/948496. And also note that Best Analyzer won’t install on SBS 2003 R2 SP1.

Wireless Issues.

So often we overlook at the simplest solutions which actually might turn the wheel. After setting up ADSL Modem using Mac Power Book G4 all was fine till l removed the Ethernet cable. The laptop couldn’t log on to the wireless network which was set on WEP. IMAC on the same network was connecting fine. All the settings seemed fine until l asked Apple Fundi, who suggested l use WPA instead of WEP, and it worked. Question is why would it not work on WEP and yet the Power Book supports it? And word of advise, when installing Windows 2003 SBS please do it on the site. If you do it off site and setup the domain including DNS and AD DC you might have issues when you deploy it at the client site. If you don't wire it to the network (for maybe security reasons), you might broke something trying to find why it doesn't log in. We learn everyday and I now believe in the statement "Knowledge start when you say you don't know."