| Sys Admin Extraordinaire |

2011-02-12 Initial Post

Windows Server 2003 SP2

Office Communications Server 2007 (non-R2)

If you want to search for OCS users with federation enabled, use the simple LDAP query filter below. It took me some testing to figure out that "TRUE" had to be in all uppercase/all capitals. Other LDAP filters are case insenstitive, but it looks like searching for boolean values, at least in this case, requires upppercase. (more...)

2011-02-14 Updated

2011-02-12 Initial Post

Windows Server 2003 SP2

Exchange Server 2003 SP2

In the IT business, sometimes what seems like a simple question can result in a few hours of work to get a satisfactory answer. The other day I was asked to look at why a query for all ActiveSync enabled users wasn't returning the correct results. The query was using the msExchOmaAdminWirelessEnable attribute. That attribute holds the values for the settings under user properties --> Exchange Features tab --> Mobile Services. (more...)

2011-01-21 Updated

2011-01-15 Initial Post

I know Exchange Server 2003 is old by now, but the client I work for still uses it, so I had set up my own test environment at home. I've worked with Exchange since 5.5, so it's not new to me. I'm also certified on Exchange Server 2007, so I'm up-to-date on the current versions.

I'm posting these screenshots and notes up here for reference. These show some of the AD modifications that are made when Exchange is installed/AD prepared. Exchange Server 2007 and 2010 basically modify AD the same way, so this is good to know. Here's a good article on what ForestPrep and DomainPrep do to AD. Note that in Exchange Server 2007 and 2010, ForesPrep and DomainPrep are no longer used, and PrepareSchema and PrepareAD are used instead. (more...)

2010-10-20 Initial Post

Exchange Server 2003 SP2, Windows Server 2003 SP2 AD

I ran into an issue at work the other day which was new to me and I didn’t really find any good documentation either on the Internet or at work, so I did some testing and wrote up a procedure to get around the issue. The issue has to do with the Associated External Account feature. Basically, that feature is used to grant permission to a mailbox in a cross-forest account/resource forest setup. If both of a user's accounts in the account and resource forest are enabled (not MS recommended), he will not be able to access other users'  Outlook folders or Outlook public folders unless a special procedure is followed.

I'm going to give an account of my testing scenario and will not be going into a lot of background details, so refer to the articles on MSExchange.org and MS TechNet for background info on the Associated External Account feature. The issue can be really confusing, so I don't expect anyone to follow it easily, but if you're reading this, then that means you might have run into the same issue and will understand what I'm describing. (more...)

2010-07-06 Initial Post

Exchange Server 2003 SP2, Windows Server 2003 SP2 AD

These are the AD attribute names for common mailbox size limit settings. You can use these attributes in a script to make changes or view current settings. (more...)