Updates on reboot / shutdown on Windows 2008

Windows 2008 has a very annoying habit of installing updates on a shutdown or reboot. On a server this can be unwanted behavior, and at a minimum it should be configurable. The work around is to go to Start > Run and use "shutdown /r /t 0" instead of the restart option and "shutdown /s /t 0" instead of the shutdown option.

Exchange 2010 public folders not forward emails or tasks

When you've migrated from Exchange 2000 or Exchange 2003 to Exchange 2010 and have decommissioned the older servers, you can run into a situation where your public folders won't accept or forward emails. There are already several posts regarding this on the Internet, but all the ones I've seen were either for email public folders or public folders accepting emails. However, it affects non-email public folders from forwarding emails as well.

The first thing is to see if a public folder will accept an incoming email. If you don't have one set up for it, set up a test folder. Send an email to it and you should an NDR saying:

554 5.2.0 STOREDRV.Deliver.Exception:ObjectNotFoundException; Failed to process message due to a permanent exception with message The Active Directory user wasn't found. ObjectNotFoundException: The Active Directory user wasn't found. ##


This issue is caused because Exchange will look at all Exchange server AD containers, including the empty Exchange 2000/2003 container, for a System Attendant to process the message, and errors out on the empty container. The solution is to delete the empty container using ADSIedit. As always, be very careful using ADSIedit as you can cause a lot of damage. If you see any servers in the container STOP because you're probably looking at the 2010 container. Once it's deleted, give Exchange 2010 some time to see the change and start processing correctly.

Routing Group connectors in Exchange 2003

When you're removing Exchange 2003 servers in an Exchange 2010 organization, one of the steps is removing the routing group connector which connects the 2003 and 2010 administrative groups. When going to the 2003 ESM to do so you'll probably see one or more other connectors there as well. Before removing the last Exchange 2003 server you should remove the other routing group connectors in your 2003 administrative group. If you don't your 2010 transport server will still see the connector but won't see a route to it, and will start logging errors 5015 and 5016 and warning 5006.

Fortuantely, if you've already uninstalled your last 2003 server without removing those connectors and are receiving those warnings and errors, you can simply remove the old connector from the "Send Connectors" tab under the "Hub Transport" organization configuration in 2010 EMC.

WARNING: orphaned scrubbed LV(673) detected

If you run an integrity check on an Exchange 2010 database using Eseutil /G then you might find entries in the output similar to "WARNING: orphaned scrubbed LV(673) detected". It seems these can be generated if the server loses connection to the database without dismounting it first, if the server crashes, or if it's powered off without shutting down. In speaking with Microsoft they said a few of them aren't a danger to the database. However, a lot of them suggests there might be other issue with the database as well, and you should consider moving the mailboxes to a new database and removing the old one.