Hi GuysI understand the Exchange 2003 SP2 holds both a DSAccess cache and that the Information Store also have a cache (e.g. relating to quota limits).Two questions:i) DSAccess Cache: Is the information held in this cache a cached copy of the DC's/GC's that Exchange needs to connect to, or actual AD information on users etc?ii) IS Cache - is this held anywhere that is configurable? For instance, if we change someone's mailbox size limit, we'd like the change to propogate fairly quickly.

i) DSAccess Cache: Is the information held in this cache a cached copy of the DC's/GC's that Exchange needs to connect to, or actual AD information on users etc?Directory Service Access (DSAccess) is an internal component in Exchange 2000 Server and Exchange Server 2003 that controls how all Exchange components access Active Directory directory service. The primary function of DSAccess is to maintain information about various directory-related events and operations. For example, DSAccess discovers the Active Directory topology and detects if domain controllers and global catalog servers are available and responding to queries. In addition, all directory queries made by internal Exchange components such RegardsChinthaka

ii) I'm facing the same problem and few weeks ago I found thishttp://technet.microsoft.com/en-us/library/bb684892.aspxBut, I would like to know if there is an other solution. I'm trying to find a step by step description of a move mailbox in order to find which action perform/forcea cacheupdate.I also read that restart the Exchange System Attendant Service will force DSAccess to query Exchange latest data in AD. I don't know the impact on the Exchange environment if I restart this service. Do all mailboxes will be unavailable during the restart ? ....

When you do Move Mailbox it modifies the AD attribute of Mailbox such as HOMEMDB HOMEMTA etc. so these activties will be taken care by AD replications. it is not best practice to restart SA just to make DSACCESS to query latest exchange data. because SA restarts all exchange services and your database will be dismounted. Understand how DSACCESS works http://www.msexchange.org/tutorials/Closer-Look-Directory-Service-Access-DSAccess-Part1.html Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|

I also read that restart the Exchange System Attendant Service will force DSAccess to query Exchange latest data in AD. I don't know the impact on the Exchange environment if I restart this service. Do all mailboxes will be unavailable during the restart ? .... Yes, all mailboxes will be unavailable during IS service restart. I won't do this and let one user beaffectedfor sometime and if reallyrequiresto access mailbox after mailbox move then change the registry key mentioned in bb684892 article but make sure that it doesn't affect your DC/GC load, also you can ask user to access mailbox through OWA for time being...Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

Thanks guys.Ok, so say I need to change someone's mailbox quota. In our environment, I can do this in two ways:1. Move the mailbox to a Mailbox Store with a higher limit set on the policy2. Change the quota limit directly on the user's mailbox via ADUCSo, from what I understand, #1 will take effect quicker since this information is held in the DSAccess cache (updated every 5 mins), whereas #2 information is held in the IS cache which is updated every 2 hours.Is this correct?

Yes, that's correct. You can change the quota in both way but ultimately it takes up to 2 hrs... Yes, #1 DSAccess Cache basically used for DC/GC user loockup in AD which is 5 mins while #2 mailbox information is 2hrs...Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com