Update: I bounced my Exchange box and my three main DCs (not all at the same 
time) after waiting about 3 hours. Here's what I did notice though.

I got into adsiedit and poked around at the users and noticed that the 
msExchPoliciesIncluded attribute wasn't set. So, once I grabbed the string from 
a different user, I'd hoped that I was out of the woods, but then looked at 
http://support.microsoft.com/kb/328738 and couldn't find the msExchReplicateNow 
attribute. After going through all of the attributes, and seeing that 
msExchPolicyEnabled was empty and was a Boolean value, I threw false into that 
and waited a few minutes and it worked.

Of course, now that I'm writing this to you and testing it again, everything's 
working as normal.

Mucho thanks to everyone -- I need to remember to chill and remember what I 
usually do when something's not working -- reboot the box. Again thanks!

Andrew Greene
Webmaster
City of Anderson
120 E Main St., Anderson, IN 46018
765-648-5947

-----Original Message-----
From: Matteson, John H Jr USA Mr USA 25th SigBN (ITT) [mailto:[EMAIL PROTECTED] 
Sent: Friday, January 11, 2008 12:20 AM
To: MS-Exchange Admin Issues
Subject: RE: Recipient Policies Update Issue

I don't think it's a mandate, it just that by default, that is how often the 
RUS and Information Store sync and stamps the account with an Email address.

As someone else pointed out here, you can bounce the Information Store server 
service and things will move along faster. But then again, do you really want 
to knock everyone off the server just so they can have a new e-mail address? 


John H. Matteson, Jr.
Systems Administrator/ITT Systems
FOB Orgun-E
Afghanistan
DSN - 318 431 8000
VoSIP - (308) 431 - 0000
Iridium - 717.633.3823

"A man who thinks of himself as belonging to a particular national group in 
America has not yet become an American. And the man who goes among you to trade 
upon your nationality is no worthy son to live under the Stars and Stripes."  
Woodrow Wilson


-----Original Message-----
From: Carl Webster [mailto:[EMAIL PROTECTED] 
Sent: Friday, January 11, 2008 12:18 AM
To: MS-Exchange Admin Issues
Subject: Re: Recipient Policies Update Issue



Michael B. Smith mandates that you wait a minimum of 2 hrs before complaining 
about RUS.  I'm sure he has a blog entry about it.
 
http://www.msexchange.org/articles/Troubleshooting-Exchange-Recipient-Update-Service-RUS.html
 
 
Webster


----- Original Message ----
From: Andrew Greene <[EMAIL PROTECTED]>
Subject: Recipient Policies Update Issue





All,

 

I’ve created a couple of new AD and created the mailboxes at the same time. 
I’ve known that it could take just a little bit of time (15 minutes generally 
at the most) for the AD account to replicate to the server that RUS runs 
against, but then the e-mail addresses specified (for me the SMTP, CCMAIL, MS, 
and X400) in the Recipient Policy should generate the e-mail address at that 
time.

 

I created the accounts about an hour and a half ago and the e-mail addresses 
still haven’t populated. I’ve gone into ESM and told the Recipient Policy to 
apply now with no luck, then told RUS to update now, still with no luck, and 
now I’ve told RUS to rebuild, no luck yet, but if I believe the warning message 
it can take several hours. I’ve checked the logs on my Exchange server and 
there are no errors (save a couple of NDRs and a pair of MAPI session issues 
earlier in the day). I’ve also checked the logs on my domain controller that 
RUS runs against and there I don’t see anything in the logs that indicates that 
I should be having this issue.

 

Does anyone have any ideas for next steps on troubleshooting?

 


 



~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~             http://www.sunbeltsoftware.com/Ninja                ~

~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~             http://www.sunbeltsoftware.com/Ninja                ~

Reply via email to