Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

RUS isn't stamping newly created users, not sure what the problem is

Status
Not open for further replies.

texnut

IS-IT--Management
Jan 11, 2007
97
US
Hello all,

We are having an odd problem with what I believe is an issue with the RUS on our Exchange 2k3 server.

A bit of a background: Initially our organization had an Exchange2K and an Exchange2K3 server. I just removed the Exchange2K server from the organization by forcing all the public folders off of it and removing it from the Exchange System Manager.

Now, if we create any new users, the email addresses are not auto-populated (X400 & SMTP).

Any thoughts on how to resolve this? I've gone through the google searches and read several MS articles but none seem to help me resolve this.

Any thoughts?

Thanks, S.
 
Yes, it is currently pointing to the main domain controller but just to test a theory, I created another domain RUS and pointed it to my other domain controller .... and I'm still not seeing any stamps against the users.

I also forced an update and after not seeing any changes forced a rebuild and it still didn't work.

Wierd huh?
 
Hi 58Sniper - I followed and re-followed kb 822931. The only thing I'm guilty of not following is the following:

After fully replicating and moving all Public Folders Exchange2K still wouldn't let me uninstall - I didn't realize that there still was two user (unused) mailboxes that lived on that server even though they didn't show up under mailboxes. Proceeding forward, I forced the removal of the Exchange server via the System Manager, then discovered the two unused mailboxes and removed them outright.

After that, I disjoined the Exchange2K server from the domain and turned it off.

The odd thing is that everything that needed to be rehomed was succesfully rehomed.

Any thoughts?
 
So check this out - I decided to restart the System Attendant (along with that came a restart of the MTA and Info Store).

After the restart, everything updated perfectly.

Just thought I'd share that incase anyone else came across a similar odd situation.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top