Wednesday, October 19, 2011

MAPI32.DLL wrong version or corrupt

One of my clients recieved the error message "MAPI32.DLL wrong version or corrupt" a few months ago, after trying Outlook 2007 and reverting back to Outlook 2003. The fix was simpler than expected...

With Outlook closed, browse on over to C:\Program Files\Common Files\System\MSMAPI\1033 and rename the MSMAPI32.DLL file. Open Outlook again and the MSMAPI32.DLL file will be replaced with the proper version (Office or Outlook install media may be required).

Tuesday, October 18, 2011

User Profile Service service failed

While attempting to log onto an Windows Server 2008 R2 system with Exchange 2010 for the first time, I received the following error: "User Profile Service service failed the logon. User profile cannot be loaded."

After much searching, we found that during a reinstall some bits were left in C:\Users\Default\AppData\Local\Microsoft\Exchange Server

Once the files therein were removed, I was able to login successfully. We surmised that since the files were in the Default profile, something was stopping a new profile from being generated.

Wednesday, September 21, 2011

WMIC to the Rescue

A recent project had me trying to script the retrieval of the Dell Service Tag. Luckily there's WMI Command-line to the rescue.

From a command line or in a script wmic bios get serialnumber will display or grab the Dell Service Tag.

Furthermore, you can use the WMI Command-line to retrieve all kinds of system data and even make configuration changes. Rob van der Woude's great site on scripting has a great primer and examples on using WMIC. TechNet Magazine also has a very useful article on gathering system data using WMIC in your environment.

Finally, checkout the WMI Admin Tools pack. It contains more than I want to type about here, but it gives you the ability to browse the various objects, classes and properties, plus a custom event viewer and much more. Check it out and make your (administrative) life better.

Wednesday, September 14, 2011

List of Exchange Scripts

I started following Pat Richard's blog a few months ago and have since found his scripts to be quite useful. Even if I'm not using them directly, they've been useful as a reference when writing my own.

He recently created a list of scripts available on his site; stop by and take a look.

Tuesday, May 24, 2011

Function Keys at the Command Prompt

This is sort of a noob post, but I'd forgotten about these, even though I use the command prompt almost hourly at work.

With a cmd shell open:

Press     To Get
F1           Last command displayed one letter at a time
F3           Repeat last command
F5           Displays the last commands one-by-one
F7           Displays the command history
F8           Cycles through the last commands, typing a character or two will cause it to match the prefix

There are a couple more, but they don't always respond correctly and IMHO are less useful.

Monday, April 18, 2011

Microsoft Case Studies

Need that extra push to get a budget approved. Perhaps you need ammo to bring into fruition (or shoot down) the latest whim of those in executive row. Microsoft Case Studies may have your answer.

Divided by Industry, Business Need, IT Issue, etc., with searchable fields as expected, there is a good amount of video and downloadable content to help make or break a case.

Wednesday, March 23, 2011

Exchange Keyword Search

So you want to look for a specific word in all the mailboxes on your server without buying a 3rd party application? Try the Exchange Management Shell.

You need three things on your client system before running the command (this is not recommended to be run on the Exchange server itself)

  1. Outlook 2003+

  2. Exchange Management Tools 2007 or 2010

  3. A configured Outlook profile with a folder for the export


get-mailbox –Database "Mailbox name" | Export-Mailbox –SubjectKeywords "Keyword" –TargetMailbox "Your mailbox" –TargetFolder 'Pick one'

The fields that need changing are in red. If you have multiple databases, the command will need to be run multiple times, and of course, the larger the databases, the longer it will take to run.

Good hunting.

Ps. Thanks to SL @ TM for this tip.