Cannot add new users adding a second Exchange server to the

brad · Joined: 05 Aug 2007 Posts: 20

Hi,
I recently added a new exchange server to the organization and am gradually
moving new users to it. Mail works fine for users on both servers (new and
old) but I just discovered that I cannot add new email accounts. Any new
accounts that are created can log on to the domain but their mailboxes do not
exist. Also, if you look under the account properties, "email addresses"
tab, there are no entries at all.

I check the logs on the DCs and the Exchange server and don't see any sign
of errors.

The new server has been online for a week. Microsoft updates were done last
night. I did'nt have occasion to add new users before the updates so I don't
know if I could have before the updates or not. Can anyone suggest a fix so
that I can add users again?

thanks,
bb
--
bb

Archived from group: microsoft>public>exchange2000>setup>installation

Steven Zhu [MSFT] · Joined: 05 Aug 2007 Posts: 4

Hi,

Thanks for posting here.

From your post, my understanding on this issue is: you cannot see mailbox
after you create user on second Exchange Server. If I am off base, please
feel free to let me know.

First, I would let you know that, actually, an Exchange build-in component,
called Recipient Update Service (RUS), will run periodically by default.
After that, all accounts which match the filter rules configured in
Recipient policies will be stamped on the addresses specified in Recipient
policies. This feature can establish email addresses automatically.
Therefore, if the RUS on your Exchange server runs properly, the email
address will be set within a period of time. I would suggest you go to user
account->Properties->Email Addresses tab to verify if the email address has
been added successfully after some time.

If the addresses are still absent, I would suggest you try the following
troubleshooting steps.

1. After created a new user account with mailbox on your second Exchange
Server, please rebuild both Enterprise and domain RUS within ESM, and then
click Update Now, and then check if the e-mail addresses are stamped
successfully on the new user and test to see if you can send e-mail to the
new mailbox successfully this time.

In Exchange System Manager, go to Recipients -> Recipient Update Services.
Right-click each item in the right pane and select Rebuild. Then, please
right-click each item again to select Update Now.

2. Please check the following configuration.

In Exchange System Manager, go to Recipients -> Recipient Update Services.
Right click on each item in the right pane and click Properties. On the
General tab, please make sure the Exchange server and DC specified are
available. If so, please specify another DC and Exchange server to see if
we can eliminate the problem.

3. Increase diagnostics logging level for MSExchangeAL, MSExchangeDSAccess
and MSExchangeSA to Maximum.

In Exchange System Manager, please right the server, choose properties,
click "Diagnostic Logging" tab, and set all options in MSExchangeAL,
MSExchangeDSAccess and MSExchangeSA to maximum. And create a new user
object, reproduce the issue, and then send me application and system event
logs to my working address at v-stezhu@microsoft.com.

4. Use LDP.exe to dump AD attributes of a good user and a bad user.

Please use the LDP.exe tool to dump the attributes of a problematic and
good user in your AD and also send it to my working address. For more info
about how to use ldp.exe to dump attributes, please refer to the Method 1
in the following Knowledge Base (KB) article:

XADM: Alternative Methods to Obtain a Dump of an Object
http://support.microsoft.com/default.aspx?scid=KB;EN-US;271201

Then, please send me the dumps for further investigation.

Please let me know the results so that I can provide further assistance on
this problem. I am looking forward to your reply.

Have a nice day.

Best Regards,

Steven Zhu
MCSE/MCDBA
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
======================================================
For urgent issues, you may want to contact Microsoft CSS directly.
Please check http://support.microsoft.com for regional support phone
numbers.
Any input or comments in this thread are highly appreciated.
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================

brad · Joined: 05 Aug 2007 Posts: 20

--
bb

"Steven Zhu [MSFT]" wrote:

> Hi,
>
> Thanks for posting here.
>
> From your post, my understanding on this issue is: you cannot see mailbox
> after you create user on second Exchange Server. If I am off base, please
> feel free to let me know.
>
> First, I would let you know that, actually, an Exchange build-in component,
> called Recipient Update Service (RUS), will run periodically by default.
> After that, all accounts which match the filter rules configured in
> Recipient policies will be stamped on the addresses specified in Recipient
> policies. This feature can establish email addresses automatically.
> Therefore, if the RUS on your Exchange server runs properly, the email
> address will be set within a period of time. I would suggest you go to user
> account->Properties->Email Addresses tab to verify if the email address has
> been added successfully after some time.
>
> If the addresses are still absent, I would suggest you try the following
> troubleshooting steps.
>
> 1. After created a new user account with mailbox on your second Exchange
> Server, please rebuild both Enterprise and domain RUS within ESM, and then
> click Update Now, and then check if the e-mail addresses are stamped
> successfully on the new user and test to see if you can send e-mail to the
> new mailbox successfully this time.
>
> In Exchange System Manager, go to Recipients -> Recipient Update Services.
> Right-click each item in the right pane and select Rebuild. Then, please
> right-click each item again to select Update Now.
>
> 2. Please check the following configuration.
>
> In Exchange System Manager, go to Recipients -> Recipient Update Services.
> Right click on each item in the right pane and click Properties. On the
> General tab, please make sure the Exchange server and DC specified are
> available. If so, please specify another DC and Exchange server to see if
> we can eliminate the problem.
>
> 3. Increase diagnostics logging level for MSExchangeAL, MSExchangeDSAccess
> and MSExchangeSA to Maximum.
>
> In Exchange System Manager, please right the server, choose properties,
> click "Diagnostic Logging" tab, and set all options in MSExchangeAL,
> MSExchangeDSAccess and MSExchangeSA to maximum. And create a new user
> object, reproduce the issue, and then send me application and system event
> logs to my working address at v-stezhu@microsoft.com.
>
> 4. Use LDP.exe to dump AD attributes of a good user and a bad user.
>
> Please use the LDP.exe tool to dump the attributes of a problematic and
> good user in your AD and also send it to my working address. For more info
> about how to use ldp.exe to dump attributes, please refer to the Method 1
> in the following Knowledge Base (KB) article:
>
> XADM: Alternative Methods to Obtain a Dump of an Object
> http://support.microsoft.com/default.aspx?scid=KB;EN-US;271201
>
> Then, please send me the dumps for further investigation.
>
> Please let me know the results so that I can provide further assistance on
> this problem. I am looking forward to your reply.
>
> Have a nice day.
>
> Best Regards,
>
> Steven Zhu
> MCSE/MCDBA
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ======================================================
> For urgent issues, you may want to contact Microsoft CSS directly.
> Please check http://support.microsoft.com for regional support phone
> numbers.
> Any input or comments in this thread are highly appreciated.
> ======================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from this issue.
> ======================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================
>
>
> Hi Steven,

It took about 40 hours but the mailbox eventually showed up. Halfway through
the second day of the problem, I was checking the
“account->Properties->Email Addresses” tab to verify if the email address
has been added successfully, as you suggested, and it still was not showing
up, and Outlook could not connect to the account. But the next morning,
about 40 hours after creating the account, I could finally see the mailbox
in ESM, and an address showed up for it under the “account->Properties->Email
Addresses” tab.

Since the mailbox was working, I was content to leave the rest of the issue
until after the weekend.

I returned to the issue this morning. I created two new accounts, one on
the old server and one on the new. I was able to log on with them and connect
to the mailbox with Outlook almost immediately, so it looks as if the problem
is cleared up. However, I still have a couple of questions:

(1) Even though things are working now, would it still be a good idea to run
rebuild & Update on the RUS as part of the porcess of moving to the new
server?

(2) Only the old server is listed under Recipient updates services. I want
to shift all functions to the new server. Would this be a good time to switch
the Exchange server name in RUS properties to the new server? Will users be
impacted when I make the change?

(3)Speaking of moving things to the new server, what about the offline
address list. WHat impact would that have on users? Will it cause any
interruption of service if I move that to the new server as well?

I increased the diagnostic logging levels and am sending the dumps from
LDP.exe for the users, as you suggested. At this point there seems to be no
problems but you may want to look them over to verify that.

Thanks for your help,

bb

Steven Zhu [MSFT] · Joined: 05 Aug 2007 Posts: 4

Hello,

Thanks for your efforts on taking time to let me know that this issue has
been successfully resolved. I am very glad to hear that. Your cooperation
and efforts on this issue are very much appreciated.

From your dump information in email, I believe this issue may caused by
RUS. Actually, the Recipient Update Service is a component in the Exchange
System Attendant service. The Recipient Update Service creates and
maintains Exchange-specific attribute values in Active Directory. If you
create a mailbox for a user, the Recipient Update Service is responsible
for the automatic generation of their Simple Mail Transfer Protocol (SMTP)
address and any other proxy addresses that you have defined for your
recipients. However, in Active Directory Users and Computers, the proxy
addresses are not displayed immediately because of a short latency period
that occurs before the Recipient Update Service produces the new e-mail
addresses, even if the service has been set to run continuously. The
Recipient Update Service updates specific attributes of mail-enabled or
mailbox-enabled Active Directory objects when they are created or modified.

Should you have any other technical questions in the future, please don't
hesitate to let us know by posting in our newsgroups. It's always our
pleasure to be of assistance.

Have a great day.

Best Regards,

Steven Zhu
MCSE/MCDBA
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
======================================================
For urgent issues, you may want to contact Microsoft CSS directly.
Please check http://support.microsoft.com for regional support phone
numbers.
Any input or comments in this thread are highly appreciated.
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================

brad · Joined: 05 Aug 2007 Posts: 20

Hi Steven,

You assisted me with a question on 11/21/06 regarding a problem of not being
able to add new mailboxes to my exchange server. The post was titled “

Cannot add new users adding a second Exchange server to the org. in
exchange2000.setup.installation

The last time this happened, the problem just sort of cleared itself up and
I wasn’t sure what caused it nor why it started working again. But as of
yesterday it is broken again. I am sending the dumps of a good user and a bad
user, as per your previous instructions. Would you mind taking a look at them
and advising me on how to fix this? I urgently need to be able to add new
user mailboxes. Thanks for your help!

5/30/07

--
bb

"Steven Zhu [MSFT]" wrote:

> Hello,
>
> Thanks for your efforts on taking time to let me know that this issue has
> been successfully resolved. I am very glad to hear that. Your cooperation
> and efforts on this issue are very much appreciated.
>
> From your dump information in email, I believe this issue may caused by
> RUS. Actually, the Recipient Update Service is a component in the Exchange
> System Attendant service. The Recipient Update Service creates and
> maintains Exchange-specific attribute values in Active Directory. If you
> create a mailbox for a user, the Recipient Update Service is responsible
> for the automatic generation of their Simple Mail Transfer Protocol (SMTP)
> address and any other proxy addresses that you have defined for your
> recipients. However, in Active Directory Users and Computers, the proxy
> addresses are not displayed immediately because of a short latency period
> that occurs before the Recipient Update Service produces the new e-mail
> addresses, even if the service has been set to run continuously. The
> Recipient Update Service updates specific attributes of mail-enabled or
> mailbox-enabled Active Directory objects when they are created or modified.
>
> Should you have any other technical questions in the future, please don't
> hesitate to let us know by posting in our newsgroups. It's always our
> pleasure to be of assistance.
>
> Have a great day.
>
> Best Regards,
>
> Steven Zhu
> MCSE/MCDBA
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ======================================================
> For urgent issues, you may want to contact Microsoft CSS directly.
> Please check http://support.microsoft.com for regional support phone
> numbers.
> Any input or comments in this thread are highly appreciated.
> ======================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from this issue.
> ======================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================
>
>
>

Sophie Tan [MSFT] · Joined: 28 Sep 2007 Posts: 1

Hello,

Since the post is very aged from last December, I suggst you post the issue
to new post. The Exchange expert should help you as soon as possible.

Thank you for your kind understanding on our newsgroup process.

Regards,

Sophie Tan, MCSE 2000

Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Thread-Topic: Cannot add new users adding a second Exchange server to
the o
| thread-index: AcejCTjNBLthfXyYRY64fmkVRdA8ag==
| X-WBNR-Posting-Host: 207.46.19.168
| From: =?Utf-8?B?YnJhZA==?=
| References:

| Subject: RE: Cannot add new users adding a second Exchange server to the
o
| Date: Wed, 30 May 2007 15:24:00 -0700
| Lines: 69
| Message-ID:
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 8bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
| Newsgroups: microsoft.public.exchange2000.setup.installation
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.exchange2000.setup.installation:140
| NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| X-Tomcat-NG: microsoft.public.exchange2000.setup.installation
|
| Hi Steven,
|
| You assisted me with a question on 11/21/06 regarding a problem of not
being
| able to add new mailboxes to my exchange server. The post was titled “
|
| Cannot add new users adding a second Exchange server to the org. in
| exchange2000.setup.installation
|
| The last time this happened, the problem just sort of cleared itself up
and
| I wasn’t sure what caused it nor why it started working again. But as
of
| yesterday it is broken again. I am sending the dumps of a good user and a
bad
| user, as per your previous instructions. Would you mind taking a look at
them
| and advising me on how to fix this? I urgently need to be able to add new
| user mailboxes. Thanks for your help!
|
| 5/30/07
|
| --
| bb
|
|
| "Steven Zhu [MSFT]" wrote:
|
| > Hello,
| >
| > Thanks for your efforts on taking time to let me know that this issue
has
| > been successfully resolved. I am very glad to hear that. Your
cooperation
| > and efforts on this issue are very much appreciated.
| >
| > From your dump information in email, I believe this issue may caused by
| > RUS. Actually, the Recipient Update Service is a component in the
Exchange
| > System Attendant service. The Recipient Update Service creates and
| > maintains Exchange-specific attribute values in Active Directory. If
you
| > create a mailbox for a user, the Recipient Update Service is
responsible
| > for the automatic generation of their Simple Mail Transfer Protocol
(SMTP)
| > address and any other proxy addresses that you have defined for your
| > recipients. However, in Active Directory Users and Computers, the proxy
| > addresses are not displayed immediately because of a short latency
period
| > that occurs before the Recipient Update Service produces the new e-mail
| > addresses, even if the service has been set to run continuously. The
| > Recipient Update Service updates specific attributes of mail-enabled or
| > mailbox-enabled Active Directory objects when they are created or
modified.
| >
| > Should you have any other technical questions in the future, please
don't
| > hesitate to let us know by posting in our newsgroups. It's always our
| > pleasure to be of assistance.
| >
| > Have a great day.
| >
| > Best Regards,
| >
| > Steven Zhu
| > MCSE/MCDBA
| > Microsoft Online Partner Support
| > Get Secure! - www.microsoft.com/security
| > ======================================================
| > For urgent issues, you may want to contact Microsoft CSS directly.
| > Please check http://support.microsoft.com for regional support phone
| > numbers.
| > Any input or comments in this thread are highly appreciated.
| > ======================================================
| > When responding to posts, please "Reply to Group" via your newsreader
so
| > that others may learn and benefit from this issue.
| > ======================================================
| > This posting is provided "AS IS" with no warranties, and confers no
rights.
| > ======================================================
| >
| >
| >
|

Adding E2K server for new Mailbox Store Hello! i would like to add new e2k server. is there anyone here knows where can i find or maybe use info on how to add another e2k to an existing 2000 domain with e2k installed? thanks!

how do you keep some exchange users on internal mail only? how do you keep some exchange users on internal mail only? We want to allow some of our user to get mail internally and externally (from the internet). Others we only want to allow interal email (nothing from the internet).

Installing new Exchange 2K server to replace old 2K server It is time to replace my old Exchange 2K server. I have another W2K server on my network with Win 2K SP4 and all the currect updates. Both servers are DC's with a single Domain environment. My existing E2K server was installed clean 3 years ago no upgra

Setup a new exchange server. My current exchange 2000 server is running out of disk space and it's also on a old server (PIII). I do have a new server to put exchange on it. how can I move exchange to the new server?

reintsall of exchange server I am planning on doin a complete reformat and reinstall of server 2000 and exchange 2000. Is there a good resource for directions on how ot correctly backup my data and then get the database remounted and running again? Thanks