Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.
Solved
AD creates Exchange 2003 Account but not in System Manager
Posted on 2008-10-17
Recently we rebuilt a Windows 2003 Server. Existing user accounts were recreated using the AD New User Wizard. Part of the process involves creating an Exchange 2003 account for each user. Worked fine and all users have working email accounts including two Blackberry Users.
Several weeks later a new user is set up. AD Exchange wizard creates email account. X400 is created and local domain smtp account is created. Had to manually create the default smtp account for the user.
Went into Exchange System Manager to Mailboxes - no user mailbox for the one just created.
Log on to Terminal Server as new user, profile creates successfully. Run Outlook 2003 and use wizard to create local outlook connection to user mailbox on Exchange server. Check name and system returns with "The name could not be resolved. The name could not be matched to a name in the address list."
Have tried Exchange Tasks for user to delete and create Exchange account - no change. Ran diagnostics but can't see anything in Application Events to suggest anything is amiss with RUS.
Any ideas? Have seen similar issues in Knowledge base but they involve replication between multiple servers - this site has one primary server with Exchange installed on the same system as AD. The only other server is the Terminal Server.
Totally baffled!
Several weeks later a new user is set up. AD Exchange wizard creates email account. X400 is created and local domain smtp account is created. Had to manually create the default smtp account for the user.
Went into Exchange System Manager to Mailboxes - no user mailbox for the one just created.
Log on to Terminal Server as new user, profile creates successfully. Run Outlook 2003 and use wizard to create local outlook connection to user mailbox on Exchange server. Check name and system returns with "The name could not be resolved. The name could not be matched to a name in the address list."
Have tried Exchange Tasks for user to delete and create Exchange account - no change. Ran diagnostics but can't see anything in Application Events to suggest anything is amiss with RUS.
Any ideas? Have seen similar issues in Knowledge base but they involve replication between multiple servers - this site has one primary server with Exchange installed on the same system as AD. The only other server is the Terminal Server.
Totally baffled!
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2
2-
2
- +1
7 Comments
try to look at the following thing
in the account proprierties, Exchange advanced, and look if is is enabled the item "Hide from exchange address list"
in the account proprierties, Exchange advanced, and look if is is enabled the item "Hide from exchange address list"
As rakeshmiglani says this is usually caused by the RUS pointing to an old DC - if this is not there or contactable then Exchange will not update / create any users.
Instructions are here:
http://support.microsoft.com/kb/275294
Also a mailbox will not be created on the server until either the user logs on and connects to the mailbox (at which point it will be created) or a mail message is sent to the user.
Instructions are here:
http://support.microsoft.com/kb/275294
Also a mailbox will not be created on the server until either the user logs on and connects to the mailbox (at which point it will be created) or a mail message is sent to the user.
Thanks for the response. How do I check that RUS is pointing to the right DC? The DC name has not been changed and the install of Exchange is completely fresh it has no knowledge of a previous server. Cheers...
Thanks. I looked at the properties for Exchange System Manager - it points to the correct server - nothing looks amiss. So I tried to configure the users Outlook logged in as them and it worked! The account now shows in ESM. Seems to have been an update glitch. Thanks everyone for your help.
It is not an update glitch but depends on your RUS configuration. RUS is configured to query AD for changes and apply them. Depending on where the user was created (which DC) and which server the RUS is configured to use there could be replication latency. Then it depends on how often you have the RUS configured to run / check for changes
Featured Post
If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Compliance and data security require steps be taken to prevent unauthorized users from copying data. Here's one method to prevent data theft via USB drives (and writable optical media).
Microsoft Office 365 is a subscriptions based service which includes services like Exchange Online and Skype for business Online. These services integrate with Microsoft's online version of Active Directory called Azure Active Directory.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller.
Log onto the new domain controller with a user account t…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online.
The email signature template has been downloaded from:
www.mail-signatures…
Suggested Courses
Course of the Month7 days, 1 hour left to enroll
705 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.