[Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 329
  • Last Modified:

Exchange 2003, Updating storage limits incredibly slow

We have a 2003 Exchange server in a 2003 AD enviroment with 2 Dc's, when I change a users storage limits on the exchange server it can take nearly 15 minutes for this to take affect, any help appreciated.
0
ronanfitz
Asked:
ronanfitz
  • 3
  • 2
1 Solution
 
jar3817Commented:
I've heard Exchange tends to bind itself to 1 particular global catalog server. If you're making this change on the other domain controller it can take some time for the changes to replicate to the other server. You can force a replication after a change is made from inside the AD Sites and Services app.
0
 
ronanfitzAuthor Commented:
Thanks for that, how do I do that, only a newbie to AD
0
 
jar3817Commented:
Well, pay attention to what server you're making the change on. When you open AD Users and Computers (ADUC) at top of the left tree view you see something like:

Active Directory Users and Computer [some.server.name.yourcorp.com]

That "some.server.name.yourcorp.com" is the server that is being edited. Make a mental note of this. Now open AD Sites and Services (ADSS) and navigate down the tree:

ADSS -> Sites -> Default-First-Site-Name -> Servers -> (your OTHER dc) -> NTDS Settings

on the right you should see something about the other server (some.server.name.yourcorp.com), right click on that and hit "replicate now"
0
 
ronanfitzAuthor Commented:
Jar,

Thanks for that, worked a treaet
0
 
jar3817Commented:
:)
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now