Managing Active Directory does not always have to be complicated. If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why
Course Of The Month
7 days, 18 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
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
Everything you need to know about backup and disaster recovery with AWS, for FREE!
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
A company’s centralized system that manages user data, security, and distributed resources is often a focus of criminal attention. Active Directory (AD) is no exception. In truth, it’s even more likely to be targeted due to the number of companies …
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
This video shows how to use Hyena, from SystemTools Software, to bulk import 100 user accounts from an external text file. View in 1080p for best video quality.
Suggested Courses
Course of the Month7 days, 18 hours left to enroll
729 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.