I just verified through ADSI Editor that I am generating OAB Version 1, 2, 3a and 4 ( just set the binary value to 1, it was presently 0, which meant it was only doing 2, 3a and 4)
So I am and have been generating 2, 3a and 4 up until now and I set it to do all of them because it won’t hurt my cause.
I do have autodiscover configured properly though. Everything works perfectly when I pull people out of Cached Mode, but if all of my users did that, it would be a substantial load on my server (roughly 450 users)
2003 is patched current, 99% of my users run off of Terminal Servers and we update them on a weekly basis. But whether the users run on terminal servers or locally on their machine, the result is still the same and the OAB is out of date.
exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Michael B. Smith
What version of server is hosting the OABs?
Are you generating a v3 and a v4 OAB?
Is Office 2003 patched to current?
Michael B. Smith
With me being the only exception, everyone else is unable to see a current version of our global address book.
I made a new forward lookup zone in my DNS settings so that when Exchange searches for Autodiscover.<mydomain> it goes directly back to the mail server and that portion works. But I am still the only user that has an up-to-date GAL (Global Address List) everyone else is months behind. This should have fixed our office 2007 users as they don’t access or *shouldn’t* access the GAL the same as office 2003 users.
What am I missing here and why I am the only one that’s able to see this? Should I start dissecting my permissions?
Any suggestions would be appreciated as this is annoying me and I have people calling me and asking me if they’re getting canned soon because they can’t be seen in the GAL (stupid, I KNOW, but it’s still something I have to deal with)