locked
RUS problem? User created in AD but no Email Address Created RRS feed

  • Question

  • Hi Everyone,

    A little background first... we have a AD structure that had two Exchange servers.  The first was our email server, which was Windows Server 2003 runing Exchange 2003.  The second is our voicemail server, Windows 2003 running Exchange 2003 also.  We have removed the initial mail server (it was in place before the voicemail server) as an Exchange server, by performing a full uninstall of Exchange after migrating all mailboxes (system related), Recipient policies, etc. to the voicemail server.  The uninstall, though complicated, did finish properly with no known problems.

    The voicemail server, when you create a user on it, creates an AD user for that voicemail user, along with an Exchange mailbox to store the messages in.  The voicemail server at this point creates the AD user, but does not properly create the Exchange user email address nor all attributes.  At this point I've gone through RUS troubleshooting and RUS is running, as I can follow the event 8011 and 8012 events through it.  The voice mail server is running and is attempting to build the account, and Exchange replication is attempting to take place (unsure why, it is the only Exchange server) but it never finishes building the account correctly.  I have diagnostic logging turned up but am seeing no errors.

    So, I still have something wrong... anyone have any thoughts as towards where the holdup might be?  I have multiple voice mail users to build, and they are getting a little cranky... voicemail provider says it is an exchange issue and they can't troubleshoot...

     

    Thanks in advance, Ken

    Thursday, January 19, 2012 3:46 PM

All replies

  • Ken,

    This could be a permissions issue where the acccount for the UM server does not have the proper permissions on Exchange to modify attributes for the new mailbox stores.  What UM vendor are you using?  Also, just to check, were Public Folders moved over properly? Everything rehomed onto the new server? 

    For the RUS troubleshooting, have you seen this article?  http://www.msexchange.org/articles/Troubleshooting-Exchange-Recipient-Update-Service-RUS.html


    JAUCG
    Friday, January 20, 2012 3:06 PM
  • Try the below links out and see if it resolve your problem.

    Download exchange best practices analyzer for exchange 2003  and run on server

    http://support.microsoft.com/kb/822794

    http://blogs.technet.com/b/exchange/archive/2004/07/22/191513.aspx

    http://www.ureader.com/msg/11665564.aspx

     

     

    Girishp

     

     

    Friday, January 20, 2012 4:26 PM
  • If this is a third-party product, make sure it's populating the mailNickname attribute of the AD account to which the mailbox is meant to be attached. Given that you have no errors, yet you also have no mailbox, it sounds like Exchange isn't even detecting the account, which in turn may come back to the mailNickname being null.

    This may or may not help in your case, but I've seen this a lot before where a vendor is setting up a mailbox programatically through AD alone.

    Cheers,
    Lain

    Saturday, January 21, 2012 4:45 AM
  • Any updates to this?
    JAUCG
    Saturday, January 21, 2012 7:39 PM
  • Hi
       In fact, I don’t know your problem clearly. 
       Quote: The voicemail server at this point creates the AD user, but does not properly create the Exchange user email address nor all attributes.
       What is the result create user and enable mailbox? Can you see “enable mailbox” page?

    Terence Yu

    TechNet Community Support

    Monday, January 23, 2012 1:32 AM
  • I have continued to work with this.  I apologize that I haven't responded, the Microsoft forums no longer apparently email you when you have a response to your questions.

     

    Anyway, I have rebuilt the recipient policies, reapplied them and now the accounts appear to be being built, but we are still unsuccessful in getting things to populate correctly. 

     

    Let me elaborate... the user account is created in AD, and the user name is populated.  The account is named properly (the number of the voice mailbox), but User Logon Name is blank, the email addresses tab is blank, the simple display name is blank...

     

    So not all attributes are being built still.. very strange.  I have gone through the registry and removed all references to accounts that existed on the other Exchange server, but found no reference to the old one in AD in any way using the techniques in the KB's mentioned above, nor in any account reference...

    I'm at a loss here... and facing a $3000 charge to convert the voice mail to SQL instead of Exchange if I can't get this working... any input is appreciated.

    Wednesday, January 25, 2012 5:26 PM
  • Please see reply above. 
    Wednesday, January 25, 2012 5:26 PM
  • I have continued to work with this.  I apologize that I haven't responded, the Microsoft forums no longer apparently email you when you have a response to your questions.

     

    Anyway, I have rebuilt the recipient policies, reapplied them and now the accounts appear to be being built, but we are still unsuccessful in getting things to populate correctly. 

     

    Let me elaborate... the user account is created in AD, and the user name is populated.  The account is named properly (the number of the voice mailbox), but User Logon Name is blank, the email addresses tab is blank, the simple display name is blank...

     

    So not all attributes are being built still.. very strange.  I have gone through the registry and removed all references to accounts that existed on the other Exchange server, but found no reference to the old one in AD in any way using the techniques in the KB's mentioned above, nor in any account reference...

    I'm at a loss here... and facing a $3000 charge to convert the voice mail to SQL instead of Exchange if I can't get this working... any input is appreciated.

    I believe I found a cure.  Under the Recipient Update Services, there was an Enterprise service but no Domain service.  Upon adding, found that I could now expect an email address to be attached when an account was created.  This repairs the exchange side... Now if the Active Voice works ok, we'll be good.  Thank you all for your help... I believe I'm ok now!
    Wednesday, January 25, 2012 6:50 PM
  • Still think this is a permission issue.  For my customers who use CUCM (Cisco Unity) they have to apply special permissions to each mailbox storage group or mailbox store.  From Cisco:

    http://www.cisco.com/en/US/docs/voice_ip_comm/unity/405/installation/guide/cuevm2knf/IG_019.html#wp1810106

    Which vendor do you have for UM?  Have you contact the vendor of your UM product?


    JAUCG
    Wednesday, January 25, 2012 6:53 PM
  • Any updates?
    JAUCG
    Sunday, January 29, 2012 6:20 PM