Just a reminder for myself how to do it really.
I’ll deal with the SYSVOL replication issues first, then move onto the DCOM issues.
They were getting;
I checked the usual, and both DC01 and DC02 could talk ok, so I figured “Let’s just Resync the bugger”.
The above MS KB will tell you in detail, however here is a overlay for replacing DC02 with DC01’s copy (making DC01 Authoritative)
Stop the File Replication Service on both DC01 and DC02
Edit the registry on both;
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
On DC01 I set it to D4 –> AKA Authoritative. On DC02 I set it to D2 –> AKA non-authoritative.
Start the FRS on DC01 and let it clear through the normal event log messages (right up to where it proclaims it is OK to be a DC again! Thank god!), then start up DC02. Monitor, and voila it all synced!
Jobs a goodun’ guvnor 😉
Often I get asked “My New User XXX is not showing in Outlook GAL”.
First of all, let me clarify some things.
In Exchange (2003 and 2007, and no doubt 2000), you have a Global Address List (GAL) and a Offline Address Book (OAB). The GAL is automatically generated more or less on the fly from AD, and contains all your Exchange-enabled users, groups and fish.
OAB is a copy of this that is available for clients (Outlook 200x) to download.
When you have Outlook 200x in Cached mode, you use OAB
When you have Outlook 200x in “Online” mode, you use GAL
When you access OWA, you use GAL
If you have a Mac and use Entourage, you use a combination of LDAP and GAL 😉
So, if your new user has not shown, the first question is “Are you looking @ the GAL or OAB?”
Most the time customers / end users are looking at the OAB, which means that they are probably just waiting for the horrible lag that MS seem to think is acceptable for OAB to re-generate and become available, which is done every night. Tell them to shush for 24hours and check again.
Occasionally you will find that after 24 hours users still cannot see the new additions. This is slightly more interesting, and now we start the fun.
**Fires up his EXCH2k7 VM to demonstrate**
Ok, so your OAB isn’t updating. First of all, force a manual update
Now, watch your App log, you should see around 3 messages stating that the OABGenerator kicked in, and generated your new OAB.
If, however, you get any “issues” (and it will tell you, but inform you to up the logging to see what was wrong), then you need to change your event log level for OABGenerator in Powershell;
“set-eventloglevel “MSExchangeSA\OAL Generator” -Level Medium”
Then re-rebuild your OAB, and re-look at your App log. You will find all your answers there, and can start your googling!
FYI, most common issue is the SMTP address issue. This is where the SMTP field in AD (Email Address in General tab) doesn’t agree with what the default Reply-To address is set in Exchange. Check the two match, make them if they don’t.
And that, my friends, is OAB debugging in Exchange 2007 =D
I seem to have neglected my blogging duties. Not that anyone minds, as no-one reads this, but one day I will require the powers of my blog!
Anyway, Marsedit ran out of its eval license so I am currently using ecto under a trial. Don’t know if I like it as much as Marsedit, so I may go back and buy that but we shall see!
Anyway, I have lots of things to prep for blogging so I shall see you all (or just me) soon!
On a side note, I like Ecto 🙂 A Lot easier for Image uploading 😀