Ever since hearing about System Center Mobile Device Manager I've been thinking about the fact we now have two System Center products capable of managing handheld devices, this and ConfigMgr. Why are there two products, how do they compare, and how do I understand which should be used in which scenarios.
Anyway, I found out that Eric Berg has written a good post that helps to understand some of this:
http://blogs.technet.com/systemcenter/archive/2007/11/02/managing-mobile-devices-with-system-center.aspx
Hopefully you'll find that useful as well...
All of my virtual machines now have ConfigMgr installed, but I needed to test something on SMS 2003. I therefore took a copy of one of my machines, uninstalled ConfigMgr and installed SMS 2003. However, whilst the setup was OK the site was not operational. The following error reported in sitecomp.log over and over:
CStatusModule::Initialize(): ERROR: Could not register this process as a source of "SMS Client" events, Win32 LoadLibrary("C:\WINDOWS\system32\smsmsgs\climsgs.dll") returned error 127
It seems that certain dll files are left behind after removing ConfigMgr, and because these are a later version they are not replaced by SMSSetup. You'll find these in:
%windir%\system32\smsmsgs
Stop the sitecomp service, replace the dll files in this folder with the files from the SMS 2003 CD in D:\SMSSETUP\BIN\I386\SYSTEM32\SMSMSGS. Start sitecomp again and you should be good to go. None of this is recommended in production but if you're just playing with test environment then maybe this will help you.