I read from tech. ref. guide that DSAccess component of Exchange is responsible for getting all AD data for Exchange server and wondering how can I force it to update after updates to AD has been made. Which service(s) I need to restart and/or is there another way of doing it thorugh script or registry.
Thanks.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
...it depends. If it is link state information, you have to shut down all systems in the Exchange Org and then boot them up starting with the Routing Group Master, then the bridgehead front-ends, then the OWA front-ends, and then the mailbox servers.
Otherwise, it is generally every 10 hours that the DSAccess process does a full refresh. This is based upon the timeout of the Kerberos ticket (timing is visible if you run the kerbtray resource kit utility).
If I were you I would consider reading KB822931 (http://support.microsoft.
The PSS tool, remonitor, can help to clear up missing entries, but it does not cause a true rebuild of the Link State Table.
.
I thought the same thing, and had even tried that working with Microsoft PSS out of CLT. Even restarting the Routing Engine can not fix stale link state issues. Yes, it can sometimes help if there is an issue. However, in order to fully recreate the Link State Table, all systems in the Org must be shut down. I had an article ready to go, based on this, about 4 months before Bill Boswell published his "LST in Translation" article. Unfortunately I did not get the approval to publish it to my blog. Bill's article was a really good overview of the issue.
http://mcpmag.com/columns/
Out of curiosity, are these messages to servers that are no longer in the environment? Do they still show in ESM or ADSIEdit?
If they don't show in ESM or in ADSIEdit, but show in Winroute (free download) or show in Winroute as missing from Active Directory and still have messages going to them, then you will need to go back to what I noted earlier. You will have to physically shut down all Exchange servers in your environment. The only other option is to run the Remonitor (call to PSS is needed) tool...but that might not fix it.
You *MUST* shut down all of the the Exchange servers and not just the Exchange services.
On Microsoft TechNet the article "Exchange Server Transport and Routing Guide > Part Two > Configuring a Routing Topology > Designating a Routing Group Master" (link: http://www.microsoft.com/t
I wonder how the second part "notifies the routing group master of this change. " works. No restart of any Exchange services on any exchange server in the routing group is required here. I'can update AD through ADSI, like ESM does, but stucked at the notification part. Wonder whether Microsoft publish such information and if so where.
It is not published by Microsoft, that I have seen.
A restart of the System Attendant is a good thing as it causes the Exchange server to re-read the information in the Config container in Active Directory. (As Exchange Admin keyed on).
I spend 46 hours over 2 1/2 days chasing down a link state issue. I spent 2 hours another day when we had a link state issue.
Bob
Business Accounts
Answer for Membership
by: KidegoPosted on 2006-03-15 at 11:41:04ID: 16197784
reboot the System attendant. that will take down the information store and the MTA however, so you may want to notify your users first, or wait until after hours.