Re: [ActiveDir] Exchange 5.5 Upgrade Problems

[Al Mulnick]

Which directory answers though?  They don't both answer on both ports do they? 
On 4/19/06, Dan DeStefano <[EMAIL PROTECTED]> wrote:



I can connect and bind successfully to the ex5.5 machine from the new ws2k3 machine using the domain admin account and the service account and via both ports: 389 and 38900.

 




From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] 
On Behalf Of Al MulnickSent: Wednesday, April 19, 2006 2:47 PM
To: ActiveDir@mail.activedir.org

Subject: Re: [ActiveDir] Exchange 5.5 Upgrade Problems 


 

I missed the part about the ADC then.  :)

 

Try the event log - what do you see at startup of the machine? If you connect to tcp 389 of that machine, what answers? (try LDP and just connect - you should see what you're looking for there.)  Until you can connect to the Exchange directory via LDAP, you're not going anywhere. Basically, be sure to check that the LDAP component is operational and work from there. 


 

Al 

On 4/19/06, Dan DeStefano <
[EMAIL PROTECTED]> wrote: 


The ADC is set to use port 38900 and the LDAP protocol at the Ex5.5 site level is set to use 38900, but at the server level it is set to use 389 (when I change this, mail stops flowing). Regardless, when I try connecting in ADC tools to the 
Ex5.5 box it fails on either port.
 
I am trying to build a new Ex2k3 server in the domain, but it will not join the organization because the ADC tools have not bee run, or at least that is the error message I am getting. 

 
 
Dan
 




From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] 
On Behalf Of Ion GottSent: Wednesday, April 19, 2006 10:25 AMTo: 
ActiveDir@mail.activedir.org; ActiveDir@mail.activedir.org

Subject: RE: [ActiveDir] Exchange 5.5 Upgrade Problems
 


The Exchange 5.5 directory should be listening on another port since it is running on a DC that is already listening on 389 for AD LDAP operations. 



 

If possible it would probably be a lot safer and easier to build a new Exchange 2003 server and just migrate to the new machine...if possible. 


 





Ion 

 

 
 

 



From:
 [EMAIL PROTECTED] on behalf of Dan DeStefano
Sent: Tue 4/18/2006 6:50 PM

To: 
ActiveDir@mail.activedir.orgSubject: RE: [ActiveDir] Exchange 5.5 Upgrade Problems


We are planning a complete domain migration and restructuring, but that takes a while and the client has not signed off yet, but they want ex2k3 features quickly. So we determined the fastest way to implement ex2k3 would be to do an in-place upgrade of their server. 

 




From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] 
On Behalf Of Brian DesmondSent: Tuesday, April 18, 2006 9:38 PMTo: 
ActiveDir@mail.activedir.orgSubject: RE: [ActiveDir] Exchange 5.5 Upgrade Problems
 
Why are you doing this interim upgrade when your end goal is a 2k3 native environment? 

 

Thanks,
 Brian Desmond

[EMAIL PROTECTED]
 
c - 312.731.3132
 
 




From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] 
On Behalf Of Dan DeStefanoSent: Tuesday, April 18, 2006 9:05 PMTo: 
ActiveDir@mail.activedir.orgSubject: RE: [ActiveDir] Exchange 5.5 Upgrade Problems
 
Yes, I can connect to the dc/ex5.5 box from the new ex2k3 member server using ldp on both ports 389 and 38900. I can also bind using the enterprise/domain admin account and the ex service account. 

 
I am not trying to do a direct upgrade from 5.5 to 2k3, rather I am trying to do an interim upgrade to ex2k, then upgrade from ex2k to ex2k3. I am receiving the database inconsistent errors when trying to do the ex2k upgrade. 

 
Note: I am not sure if it matters, but in ex5.5 administrator, the ldap protocol for the site is set to 38900, but for the server it is set to 389. I tried changing it in the server to 38900, but that stopped mail from flowing. 

 
 
Dan
 




From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] 
On Behalf Of Brian DesmondSent: Tuesday, April 18, 2006 8:39 PMTo: 
ActiveDir@mail.activedir.orgSubject: RE: [ActiveDir] Exchange 5.5 Upgrade Problems
 
Could be all sorts of things here, but lets start simple. Can you do an ldap bind to the exchange box on port 38900 using the ldp tool (or similar) from the support tools? 

 
You can't do an inplace upgrade from 5.5 to 2003 which is what it sounds like you're doing when you get the consistency error. 

 
 
 

Thanks,
 Brian Desmond

[EMAIL PROTECTED]
 
c - 312.731.3132
 
 




From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] 
On Behalf Of Dan DeStefanoSent: Tuesday, April 18, 2006 8:10 PMTo: 
ActiveDir@mail.activedir.orgSubject: [ActiveDir] Exchange 5.5 Upgrade Problems
 
I have taken over administration of a w2k AD domain running Exchange 5.5. This domain was a mess and it took a lot of doing just to resolve all the errors in the event logs, but now they are just about all resolved and the DC/Ex5.5 server passes all netdiag/dcdiag tests. 

 
My current project is to upgrade the Ex5.5 server (which is also the domain's only DC) to Ex2k3, but I am running into problems. I have 

RE: [ActiveDir] Exchange 5.5 Upgrade Problems

[Dan DeStefano]

I can connect and bind successfully to the
ex5.5 machine from the new ws2k3 machine using the domain admin account and the
service account and via both ports: 389 and 38900.

 









From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Al Mulnick
Sent: Wednesday, April 19, 2006
2:47 PM
To: ActiveDir@mail.activedir.org
Subject: Re: [ActiveDir] Exchange
5.5 Upgrade Problems



 



I missed the part about the ADC then.  :)





 





Try the event log - what do you see at startup of the machine? If you
connect to tcp 389 of that machine, what answers? (try LDP and just connect -
you should see what you're looking for there.)  Until you can connect to
the Exchange directory via LDAP, you're not going anywhere. Basically, be sure
to check that the LDAP component is operational and work from there. 





 





Al

 





On 4/19/06, Dan
DeStefano <[EMAIL PROTECTED]>
wrote: 





The ADC is set to use port 38900 and the LDAP protocol at the
Ex5.5 site level is set to use 38900, but at the server level it is set to use
389 (when I change this, mail stops flowing). Regardless, when I try connecting
in ADC tools to the Ex5.5 box it fails on either port.

 

I am trying to build a new Ex2k3 server in the domain, but it
will not join the organization because the ADC tools have not bee run, or at
least that is the error message I am getting. 

 

 

Dan

 









From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
On Behalf Of Ion Gott
Sent: Wednesday, April 19, 2006
10:25 AM
To: ActiveDir@mail.activedir.org;
ActiveDir@mail.activedir.org






Subject: RE:
[ActiveDir] Exchange 5.5 Upgrade Problems



 





The Exchange 5.5 directory should be listening
on another port since it is running on a DC that is already listening on 389
for AD LDAP operations. 









 





If
possible it would probably be a lot safer and easier to build a new Exchange
2003 server and just migrate to the new machine...if possible. 





 















Ion 





 





 














 







From: [EMAIL PROTECTED]
on behalf of Dan DeStefano
Sent: Tue 4/18/2006 6:50 PM






To: ActiveDir@mail.activedir.org
Subject: RE:
[ActiveDir] Exchange 5.5 Upgrade Problems









We are planning a complete domain migration and restructuring,
but that takes a while and the client has not signed off yet, but they want
ex2k3 features quickly. So we determined the fastest way to implement ex2k3
would be to do an in-place upgrade of their server. 

 









From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
On Behalf Of Brian Desmond
Sent: Tuesday, April 18, 2006 9:38
PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Exchange
5.5 Upgrade Problems



 

Why are you doing this interim upgrade when
your end goal is a 2k3 native environment? 

 



Thanks, 
Brian
Desmond

[EMAIL PROTECTED]

 

c -
312.731.3132

 

 











From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
On Behalf Of Dan DeStefano
Sent: Tuesday, April 18, 2006 9:05
PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Exchange
5.5 Upgrade Problems



 

Yes, I can connect to the dc/ex5.5 box from the new ex2k3
member server using ldp on both ports 389 and 38900. I can also bind using the
enterprise/domain admin account and the ex service account. 

 

I am not trying to do a direct upgrade from 5.5 to 2k3, rather
I am trying to do an interim upgrade to ex2k, then upgrade from ex2k to ex2k3.
I am receiving the database inconsistent errors when trying to do the ex2k
upgrade. 

 

Note: I am not sure if it matters, but in ex5.5
administrator, the ldap protocol for the site is set to 38900, but for the
server it is set to 389. I tried changing it in the server to 38900, but that
stopped mail from flowing. 

 

 

Dan

 









From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
On Behalf Of Brian Desmond
Sent: Tuesday, April 18, 2006 8:39
PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Exchange
5.5 Upgrade Problems



 

Could be all sorts of things here, but lets
start simple. Can you do an ldap bind to the exchange box on port 38900 using
the ldp tool (or similar) from the support tools? 

 

You can't do an inplace upgrade from 5.5 to
2003 which is what it sounds like you're doing when you get the consistency
error. 

 

 

 



Thanks, 
Brian
Desmond

[EMAIL PROTECTED]

 

c -
312.731.3132

 

 











From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
On Behalf Of Dan DeStefano
Sent: Tuesday, April 18, 2006 8:10
PM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] Exchange 5.5
Upgrade Problems



 

I
have taken over administration of a w2k AD domain running Exchange 5.5. This
domain was a mess and it took a lot of doing just to resolve all the errors in
the event logs, but now they are just about all resolved and the DC/Ex5.5
server passes all netdiag/dcdiag tests. 

 

My
current project is to upgrade the Ex5.5 server (which is also the domain's only
DC) to Ex2k3, but I a

Re: [ActiveDir] Exchange 5.5 Upgrade Problems

[Al Mulnick]

I missed the part about the ADC then.  :)
 
Try the event log - what do you see at startup of the machine? If you connect to tcp 389 of that machine, what answers? (try LDP and just connect - you should see what you're looking for there.)  Until you can connect to the Exchange directory via LDAP, you're not going anywhere. Basically, be sure to check that the LDAP component is operational and work from there. 

 
Al 
On 4/19/06, Dan DeStefano <[EMAIL PROTECTED]> wrote:



The ADC is set to use port 38900 and the LDAP protocol at the Ex5.5 site level is set to use 38900, but at the server level it is set to use 389 (when I change this, mail stops flowing). Regardless, when I try connecting in ADC tools to the 
Ex5.5 box it fails on either port.
 
I am trying to build a new Ex2k3 server in the domain, but it will not join the organization because the ADC tools have not bee run, or at least that is the error message I am getting.

 
 
Dan
 




From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] 
On Behalf Of Ion GottSent: Wednesday, April 19, 2006 10:25 AMTo: 
ActiveDir@mail.activedir.org; ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Exchange 5.5 Upgrade Problems


 



The Exchange 5.5 directory should be listening on another port since it is running on a DC that is already listening on 389 for AD LDAP operations.




 

If possible it would probably be a lot safer and easier to build a new Exchange 2003 server and just migrate to the new machine...if possible.


 






Ion 


 

 


 



From:
 [EMAIL PROTECTED] on behalf of Dan DeStefano
Sent: Tue 4/18/2006 6:50 PM
To: 
ActiveDir@mail.activedir.orgSubject: RE: [ActiveDir] Exchange 5.5 Upgrade Problems




We are planning a complete domain migration and restructuring, but that takes a while and the client has not signed off yet, but they want ex2k3 features quickly. So we determined the fastest way to implement ex2k3 would be to do an in-place upgrade of their server.

 




From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] 
On Behalf Of Brian DesmondSent: Tuesday, April 18, 2006 9:38 PMTo: 
ActiveDir@mail.activedir.orgSubject: RE: [ActiveDir] Exchange 5.5 Upgrade Problems
 
Why are you doing this interim upgrade when your end goal is a 2k3 native environment? 

 

Thanks,
Brian Desmond

[EMAIL PROTECTED]
 
c - 312.731.3132
 
 




From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] 
On Behalf Of Dan DeStefanoSent: Tuesday, April 18, 2006 9:05 PMTo: 
ActiveDir@mail.activedir.orgSubject: RE: [ActiveDir] Exchange 5.5 Upgrade Problems
 
Yes, I can connect to the dc/ex5.5 box from the new ex2k3 member server using ldp on both ports 389 and 38900. I can also bind using the enterprise/domain admin account and the ex service account.

 
I am not trying to do a direct upgrade from 5.5 to 2k3, rather I am trying to do an interim upgrade to ex2k, then upgrade from ex2k to ex2k3. I am receiving the database inconsistent errors when trying to do the ex2k upgrade.

 
Note: I am not sure if it matters, but in ex5.5 administrator, the ldap protocol for the site is set to 38900, but for the server it is set to 389. I tried changing it in the server to 38900, but that stopped mail from flowing.

 
 
Dan
 




From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] 
On Behalf Of Brian DesmondSent: Tuesday, April 18, 2006 8:39 PMTo: 
ActiveDir@mail.activedir.orgSubject: RE: [ActiveDir] Exchange 5.5 Upgrade Problems
 
Could be all sorts of things here, but lets start simple. Can you do an ldap bind to the exchange box on port 38900 using the ldp tool (or similar) from the support tools?

 
You can't do an inplace upgrade from 5.5 to 2003 which is what it sounds like you're doing when you get the consistency error.

 
 
 

Thanks,
Brian Desmond

[EMAIL PROTECTED]
 
c - 312.731.3132
 
 




From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] 
On Behalf Of Dan DeStefanoSent: Tuesday, April 18, 2006 8:10 PMTo: 
ActiveDir@mail.activedir.orgSubject: [ActiveDir] Exchange 5.5 Upgrade Problems
 
I have taken over administration of a w2k AD domain running Exchange 5.5. This domain was a mess and it took a lot of doing just to resolve all the errors in the event logs, but now they are just about all resolved and the DC/Ex5.5 server passes all netdiag/dcdiag tests.

 
My current project is to upgrade the Ex5.5 server (which is also the domain's only DC) to Ex2k3, but I am running into problems. I have successfully run Forestprep and Domainprep. However, when I attempt to run the installation, I receive the error "Exchange… cannot be assigned the task "upgrade" because… the directory database is in an inconsistent state… the private and or public stores are in an inconsistent state". However, when using Eseutil to check database consistency of all 3 databases, it reports that they are consistent. Even so, I tried using Eseutil to: repair all 3 DBs and perform soft recovery on all 3 DBs, but nothing worked. I then ran ever

RE: [ActiveDir] Exchange 5.5 Upgrade Problems

[Dan DeStefano]

I am not trying to upgrade from Ex5.5 to
Ex2k3, but rather from Ex5.5 to Ex2k, then, from Ex2k to Ex2k3.

 









From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Al Mulnick
Sent: Wednesday, April 19, 2006
10:45 AM
To: ActiveDir@mail.activedir.org
Subject: Re: [ActiveDir] Exchange
5.5 Upgrade Problems



 



In place of Exchange 5.5 to Exchange 2003? Check the readme, release
notes and migration path scenarios again.  Last I checked, that was
not a supported upgrade path (2000 to 2003 is supported although not always
preferred).  





 





 





 





Al

 





On 4/18/06, Dan
DeStefano <[EMAIL PROTECTED]>
wrote: 





We are planning a complete domain migration and
restructuring, but that takes a while and the client has not signed off yet,
but they want ex2k3 features quickly. So we determined the fastest way to
implement ex2k3 would be to do an in-place upgrade of their server. 

 









From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
On Behalf Of Brian Desmond
Sent: Tuesday, April 18, 2006 9:38
PM






To: ActiveDir@mail.activedir.org
Subject: RE:
[ActiveDir] Exchange 5.5 Upgrade Problems







 

Why are you doing this interim upgrade when
your end goal is a 2k3 native environment? 

 



Thanks, 
Brian
Desmond

[EMAIL PROTECTED]

 

c -
312.731.3132

 

 











From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
On Behalf Of Dan DeStefano
Sent: Tuesday, April 18, 2006 9:05
PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Exchange
5.5 Upgrade Problems



 

Yes, I can connect to the dc/ex5.5 box from the new ex2k3
member server using ldp on both ports 389 and 38900. I can also bind using the
enterprise/domain admin account and the ex service account. 

 

I am not trying to do a direct upgrade from 5.5 to 2k3,
rather I am trying to do an interim upgrade to ex2k, then upgrade from ex2k to
ex2k3. I am receiving the database inconsistent errors when trying to do the
ex2k upgrade. 

 

Note: I am not sure if it matters, but in ex5.5
administrator, the ldap protocol for the site is set to 38900, but for the
server it is set to 389. I tried changing it in the server to 38900, but that
stopped mail from flowing. 

 

 

Dan

 









From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
On Behalf Of Brian Desmond
Sent: Tuesday, April 18, 2006 8:39
PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Exchange
5.5 Upgrade Problems



 

Could be all sorts of things here, but lets
start simple. Can you do an ldap bind to the exchange box on port 38900 using
the ldp tool (or similar) from the support tools? 

 

You can't do an inplace upgrade from 5.5 to
2003 which is what it sounds like you're doing when you get the consistency
error. 

 

 

 



Thanks, 
Brian
Desmond

[EMAIL PROTECTED]

 

c -
312.731.3132

 

 











From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
On Behalf Of Dan DeStefano
Sent: Tuesday, April 18, 2006 8:10
PM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] Exchange 5.5
Upgrade Problems



 

I
have taken over administration of a w2k AD domain running Exchange 5.5. This
domain was a mess and it took a lot of doing just to resolve all the errors in
the event logs, but now they are just about all resolved and the DC/Ex5.5
server passes all netdiag/dcdiag tests. 

 

My
current project is to upgrade the Ex5.5 server (which is also the domain's only
DC) to Ex2k3, but I am running into problems. I have successfully run
Forestprep and Domainprep. However, when I attempt to run the installation, I
receive the error "Exchange… cannot be assigned the task
"upgrade" because… the directory database is in an inconsistent
state… the private and or public stores are in an inconsistent state".
However, when using Eseutil to check database consistency of all 3 databases,
it reports that they are consistent. Even so, I tried using Eseutil to: repair
all 3 DBs and perform soft recovery on all 3 DBs, but nothing worked. I then
ran every test/repair using isinteg, all of which completed successfully and
only some of which reported errors. However, nothing has worked and I am still
getting the same errors when trying to upgrade. I also upgraded the ADC to the
Ex2k SP3 version, which had no effect. 

 

Now
my plan is to install a new WS2k3/Ex2k3 server into the Ex5.5 organization,
move all mailboxes to it, then decommission the old Ex5.5 box. While waiting
for my maintenance window to upgrade the current ADC to the 2k3 version, I
installed EX2k3 ADC on the new mail server (which is not a DC). Now, when I try
to run the "Data collection" step in ADC tools on the new ws2k3 box,
I receive the error "Server :389 is not an Exchange 5.5
server or an SRS service". I realized that since it was installed on a DC
that the LDAP port in ADC was changed to 38900, so I changed it in ADC tools.
However, I am now receiving the error "Could not connect to server
:38900 with LDAP error

RE: [ActiveDir] Exchange 5.5 Upgrade Problems

[Dan DeStefano]

The ADC is set to use port 38900 and the
LDAP protocol at the Ex5.5 site level is set to use 38900, but at the server
level it is set to use 389 (when I change this, mail stops flowing). Regardless,
when I try connecting in ADC tools to the Ex5.5 box it fails on either port.

 

I am trying to build a new Ex2k3 server in
the domain, but it will not join the organization because the ADC tools have
not bee run, or at least that is the error message I am getting.

 

 

Dan

 









From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ion Gott
Sent: Wednesday, April 19, 2006
10:25 AM
To: ActiveDir@mail.activedir.org;
ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Exchange
5.5 Upgrade Problems



 





The Exchange 5.5 directory should be
listening on another port since it is running on a DC that is already listening
on 389 for AD LDAP operations.





 





If possible it would probably be a lot safer and easier to
build a new Exchange 2003 server and just migrate to the new machine...if
possible.





 

















Ion 





 





 













 







From:
[EMAIL PROTECTED] on behalf of Dan DeStefano
Sent: Tue 4/18/2006 6:50 PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Exchange
5.5 Upgrade Problems





We are planning a complete domain
migration and restructuring, but that takes a while and the client has not
signed off yet, but they want ex2k3 features quickly. So we determined the
fastest way to implement ex2k3 would be to do an in-place upgrade of their
server.

 









From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Desmond
Sent: Tuesday, April 18, 2006 9:38
PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Exchange
5.5 Upgrade Problems



 

Why are you doing
this interim upgrade when your end goal is a 2k3 native environment? 

 



Thanks,
Brian
Desmond

[EMAIL PROTECTED]

 

c -
312.731.3132

 

 











From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan DeStefano
Sent: Tuesday, April 18, 2006 9:05
PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Exchange
5.5 Upgrade Problems



 

Yes, I can connect to the dc/ex5.5 box
from the new ex2k3 member server using ldp on both ports 389 and 38900. I can
also bind using the enterprise/domain admin account and the ex service account.

 

I am not trying to do a direct upgrade
from 5.5 to 2k3, rather I am trying to do an interim upgrade to ex2k, then
upgrade from ex2k to ex2k3. I am receiving the database inconsistent errors
when trying to do the ex2k upgrade.

 

Note: I am not sure if it matters, but in
ex5.5 administrator, the ldap protocol for the site is set to 38900, but for
the server it is set to 389. I tried changing it in the server to 38900, but
that stopped mail from flowing.

 

 

Dan

 









From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Desmond
Sent: Tuesday, April 18, 2006 8:39
PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Exchange
5.5 Upgrade Problems



 

Could be all sorts
of things here, but lets start simple. Can you do an ldap bind to the exchange
box on port 38900 using the ldp tool (or similar) from the support tools?

 

You can’t do
an inplace upgrade from 5.5 to 2003 which is what it sounds like you’re
doing when you get the consistency error.

 

 

 



Thanks,
Brian
Desmond

[EMAIL PROTECTED]

 

c -
312.731.3132

 

 











From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan DeStefano
Sent: Tuesday, April 18, 2006 8:10
PM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] Exchange 5.5
Upgrade Problems



 

I have taken over administration of a w2k AD domain running
Exchange 5.5. This domain was a mess and it took a lot of doing just to resolve
all the errors in the event logs, but now they are just about all resolved and
the DC/Ex5.5 server passes all netdiag/dcdiag tests.

 

My current project is to upgrade the Ex5.5 server (which is
also the domain’s only DC) to Ex2k3, but I am running into problems. I
have successfully run Forestprep and Domainprep. However, when I attempt to run
the installation, I receive the error “Exchange… cannot be assigned
the task “upgrade” because… the directory database is in an
inconsistent state… the private and or public stores are in an
inconsistent state”. However, when using Eseutil to check database
consistency of all 3 databases, it reports that they are consistent. Even so, I
tried using Eseutil to: repair all 3 DBs and perform soft recovery on all 3
DBs, but nothing worked. I then ran every test/repair using isinteg, all of
which completed successfully and only some of which reported errors. However,
nothing has worked and I am still getting the same errors when trying to
upgrade. I also upgraded the ADC to the Ex2k SP3 version, which had no effect.

 

Now my plan is to install a new WS2k3/Ex2k3 server into the
Ex5.5 organization, move all mailboxes to it, then decommission the old Ex5.5
box. While

Re: [ActiveDir] Exchange 5.5 Upgrade Problems

[Al Mulnick]

In place of Exchange 5.5 to Exchange 2003? Check the readme, release notes and migration path scenarios again.  Last I checked, that was not a supported upgrade path (2000 to 2003 is supported although not always preferred). 

 
 
 
Al 
On 4/18/06, Dan DeStefano <[EMAIL PROTECTED]> wrote:



We are planning a complete domain migration and restructuring, but that takes a while and the client has not signed off yet, but they want ex2k3 features quickly. So we determined the fastest way to implement ex2k3 would be to do an in-place upgrade of their server.

 




From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] 
On Behalf Of Brian DesmondSent: Tuesday, April 18, 2006 9:38 PM
To: 
ActiveDir@mail.activedir.orgSubject: RE: [ActiveDir] Exchange 5.5 Upgrade Problems



 
Why are you doing this interim upgrade when your end goal is a 2k3 native environment? 

 

Thanks,
Brian Desmond

[EMAIL PROTECTED]
 
c - 312.731.3132
 
 




From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] 
On Behalf Of Dan DeStefanoSent: Tuesday, April 18, 2006 9:05 PMTo: 
ActiveDir@mail.activedir.orgSubject: RE: [ActiveDir] Exchange 5.5 Upgrade Problems
 
Yes, I can connect to the dc/ex5.5 box from the new ex2k3 member server using ldp on both ports 389 and 38900. I can also bind using the enterprise/domain admin account and the ex service account.

 
I am not trying to do a direct upgrade from 5.5 to 2k3, rather I am trying to do an interim upgrade to ex2k, then upgrade from ex2k to ex2k3. I am receiving the database inconsistent errors when trying to do the ex2k upgrade.

 
Note: I am not sure if it matters, but in ex5.5 administrator, the ldap protocol for the site is set to 38900, but for the server it is set to 389. I tried changing it in the server to 38900, but that stopped mail from flowing.

 
 
Dan
 




From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] 
On Behalf Of Brian DesmondSent: Tuesday, April 18, 2006 8:39 PMTo: 
ActiveDir@mail.activedir.orgSubject: RE: [ActiveDir] Exchange 5.5 Upgrade Problems
 
Could be all sorts of things here, but lets start simple. Can you do an ldap bind to the exchange box on port 38900 using the ldp tool (or similar) from the support tools?

 
You can't do an inplace upgrade from 5.5 to 2003 which is what it sounds like you're doing when you get the consistency error.

 
 
 

Thanks,
Brian Desmond

[EMAIL PROTECTED]
 
c - 312.731.3132
 
 




From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] 
On Behalf Of Dan DeStefanoSent: Tuesday, April 18, 2006 8:10 PMTo: 
ActiveDir@mail.activedir.orgSubject: [ActiveDir] Exchange 5.5 Upgrade Problems
 
I have taken over administration of a w2k AD domain running Exchange 5.5. This domain was a mess and it took a lot of doing just to resolve all the errors in the event logs, but now they are just about all resolved and the DC/Ex5.5 server passes all netdiag/dcdiag tests.

 
My current project is to upgrade the Ex5.5 server (which is also the domain's only DC) to Ex2k3, but I am running into problems. I have successfully run Forestprep and Domainprep. However, when I attempt to run the installation, I receive the error "Exchange… cannot be assigned the task "upgrade" because… the directory database is in an inconsistent state… the private and or public stores are in an inconsistent state". However, when using Eseutil to check database consistency of all 3 databases, it reports that they are consistent. Even so, I tried using Eseutil to: repair all 3 DBs and perform soft recovery on all 3 DBs, but nothing worked. I then ran every test/repair using isinteg, all of which completed successfully and only some of which reported errors. However, nothing has worked and I am still getting the same errors when trying to upgrade. I also upgraded the ADC to the Ex2k SP3 version, which had no effect.

 
Now my plan is to install a new WS2k3/Ex2k3 server into the Ex5.5 organization, move all mailboxes to it, then decommission the old Ex5.5 box. While waiting for my maintenance window to upgrade the current ADC to the 2k3 version, I installed EX2k3 ADC on the new mail server (which is not a DC). Now, when I try to run the "Data collection" step in ADC tools on the new ws2k3 box, I receive the error "Server :389 is not an Exchange 
5.5 server or an SRS service". I realized that since it was installed on a DC that the LDAP port in ADC was changed to 38900, so I changed it in ADC tools. However, I am now receiving the error "Could not connect to server :38900 with LDAP error 6.  Check server name, port number and account permissions". I am logged on with the Enterprise/Domain Administrator account and the ADC service is set to use the same service account as the ADC on the 
Ex5.5 server.
 
If you need any more info please let me know.
Any help that anyone can provide will be greatly appreciated.
 
 
Dan DeStefano
Info-lution Corporation
www.info-lution.com

MCSE - 2073750
 
If you have received thi

RE: [ActiveDir] Exchange 5.5 Upgrade Problems

[Ion Gott]

The Exchange 5.5 directory 
should be listening on another port since it is running on a DC that is already 
listening on 389 for AD LDAP operations.
 
If possible it would probably be a lot 
safer and easier to build a new Exchange 2003 server and just migrate to the new 
machine...if possible.
 




Ion 

 
 


From: [EMAIL PROTECTED] on 
behalf of Dan DeStefanoSent: Tue 4/18/2006 6:50 PMTo: 
ActiveDir@mail.activedir.orgSubject: RE: [ActiveDir] Exchange 5.5 
Upgrade Problems


We are planning a 
complete domain migration and restructuring, but that takes a while and the 
client has not signed off yet, but they want ex2k3 features quickly. So we 
determined the fastest way to implement ex2k3 would be to do an in-place upgrade 
of their server.
 




From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
On Behalf Of Brian 
DesmondSent: Tuesday, April 
18, 2006 9:38 PMTo: 
ActiveDir@mail.activedir.orgSubject: RE: [ActiveDir] Exchange 5.5 
Upgrade Problems
 
Why are you doing 
this interim upgrade when your end goal is a 2k3 native environment? 

 

Thanks,Brian 
Desmond
[EMAIL PROTECTED]
 
c - 
312.731.3132
 
 




From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
On Behalf Of Dan 
DeStefanoSent: Tuesday, April 
18, 2006 9:05 PMTo: 
ActiveDir@mail.activedir.orgSubject: RE: [ActiveDir] Exchange 5.5 
Upgrade Problems
 
Yes, I can connect to 
the dc/ex5.5 box from the new ex2k3 member server using ldp on both ports 389 
and 38900. I can also bind using the enterprise/domain admin account and the ex 
service account.
 
I am not trying to do a 
direct upgrade from 5.5 to 2k3, rather I am trying to do an interim upgrade to 
ex2k, then upgrade from ex2k to ex2k3. I am receiving the database inconsistent 
errors when trying to do the ex2k upgrade.
 
Note: I am not sure if 
it matters, but in ex5.5 administrator, the ldap protocol for the site is set to 
38900, but for the server it is set to 389. I tried changing it in the server to 
38900, but that stopped mail from flowing.
 
 
Dan
 




From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
On Behalf Of Brian 
DesmondSent: Tuesday, April 
18, 2006 8:39 PMTo: 
ActiveDir@mail.activedir.orgSubject: RE: [ActiveDir] Exchange 5.5 
Upgrade Problems
 
Could be all sorts 
of things here, but lets start simple. Can you do an ldap bind to the exchange 
box on port 38900 using the ldp tool (or similar) from the support 
tools?
 
You can’t do an 
inplace upgrade from 5.5 to 2003 which is what it sounds like you’re doing when 
you get the consistency error.
 
 
 

Thanks,Brian 
Desmond
[EMAIL PROTECTED]
 
c - 
312.731.3132
 
 




From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
On Behalf Of Dan 
DeStefanoSent: Tuesday, April 
18, 2006 8:10 PMTo: 
ActiveDir@mail.activedir.orgSubject: [ActiveDir] Exchange 5.5 Upgrade 
Problems
 
I have taken over administration of 
a w2k AD domain running Exchange 5.5. This domain was a mess and it took a lot 
of doing just to resolve all the errors in the event logs, but now they are just 
about all resolved and the DC/Ex5.5 server passes all netdiag/dcdiag 
tests.
 
My current project is to upgrade the 
Ex5.5 server (which is also the domain’s only DC) to Ex2k3, but I am running 
into problems. I have successfully run Forestprep and Domainprep. However, when 
I attempt to run the installation, I receive the error “Exchange… cannot be 
assigned the task “upgrade” because… the directory database is in an 
inconsistent state… the private and or public stores are in an inconsistent 
state”. However, when using Eseutil to check database consistency of all 3 
databases, it reports that they are consistent. Even so, I tried using Eseutil 
to: repair all 3 DBs and perform soft recovery on all 3 DBs, but nothing worked. 
I then ran every test/repair using isinteg, all of which completed successfully 
and only some of which reported errors. However, nothing has worked and I am 
still getting the same errors when trying to upgrade. I also upgraded the ADC to 
the Ex2k SP3 version, which had no effect.
 
Now my plan is to install a new 
WS2k3/Ex2k3 server into the Ex5.5 organization, move all mailboxes to it, then 
decommission the old Ex5.5 box. While waiting for my maintenance window to 
upgrade the current ADC to the 2k3 version, I installed EX2k3 ADC on the new 
mail server (which is not a DC). Now, when I try to run the “Data collection” 
step in ADC tools on the new ws2k3 box, I receive the error “Server 
:389 is not an Exchange 5.5 server or an SRS service”. I 
realized that since it was installed on a DC that the LDAP port in ADC was 
changed to 38900, so I changed it in ADC tools. However, I am now receiving the 
error “Could not connect to server :38900 with LDAP error 
6.  Check server name, port number and account permissions”. I am logged on 
with the Enterprise/Domain Administrator account and the ADC service is set to 
use the same service account as the ADC on the Ex5.5 server.
 
If you need any more info please let 
me know.
Any

RE: [ActiveDir] Exchange 5.5 Upgrade Problems

[Dan DeStefano]

We are planning a complete domain
migration and restructuring, but that takes a while and the client has not
signed off yet, but they want ex2k3 features quickly. So we determined the
fastest way to implement ex2k3 would be to do an in-place upgrade of their
server.

 









From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Desmond
Sent: Tuesday, April 18, 2006 9:38
PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Exchange
5.5 Upgrade Problems



 

Why are you doing
this interim upgrade when your end goal is a 2k3 native environment? 

 



Thanks,
Brian
Desmond

[EMAIL PROTECTED]

 

c -
312.731.3132

 

 











From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Dan DeStefano
Sent: Tuesday, April 18, 2006 9:05
PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Exchange
5.5 Upgrade Problems



 

Yes, I can connect to the dc/ex5.5 box
from the new ex2k3 member server using ldp on both ports 389 and 38900. I can
also bind using the enterprise/domain admin account and the ex service account.

 

I am not trying to do a direct upgrade
from 5.5 to 2k3, rather I am trying to do an interim upgrade to ex2k, then
upgrade from ex2k to ex2k3. I am receiving the database inconsistent errors
when trying to do the ex2k upgrade.

 

Note: I am not sure if it matters, but in
ex5.5 administrator, the ldap protocol for the site is set to 38900, but for
the server it is set to 389. I tried changing it in the server to 38900, but
that stopped mail from flowing.

 

 

Dan

 









From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Desmond
Sent: Tuesday, April 18, 2006 8:39
PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Exchange
5.5 Upgrade Problems



 

Could be all sorts
of things here, but lets start simple. Can you do an ldap bind to the exchange
box on port 38900 using the ldp tool (or similar) from the support tools?

 

You can’t do
an inplace upgrade from 5.5 to 2003 which is what it sounds like you’re
doing when you get the consistency error.

 

 

 



Thanks,
Brian
Desmond

[EMAIL PROTECTED]

 

c -
312.731.3132

 

 











From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan DeStefano
Sent: Tuesday, April 18, 2006 8:10
PM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] Exchange 5.5
Upgrade Problems



 

I have taken over administration of a w2k AD domain running
Exchange 5.5. This domain was a mess and it took a lot of doing just to resolve
all the errors in the event logs, but now they are just about all resolved and
the DC/Ex5.5 server passes all netdiag/dcdiag tests.

 

My current project is to upgrade the Ex5.5 server (which is
also the domain’s only DC) to Ex2k3, but I am running into problems. I
have successfully run Forestprep and Domainprep. However, when I attempt to run
the installation, I receive the error “Exchange… cannot be assigned
the task “upgrade” because… the directory database is in an
inconsistent state… the private and or public stores are in an
inconsistent state”. However, when using Eseutil to check database
consistency of all 3 databases, it reports that they are consistent. Even so, I
tried using Eseutil to: repair all 3 DBs and perform soft recovery on all 3
DBs, but nothing worked. I then ran every test/repair using isinteg, all of
which completed successfully and only some of which reported errors. However,
nothing has worked and I am still getting the same errors when trying to
upgrade. I also upgraded the ADC to the Ex2k SP3 version, which had no effect.

 

Now my plan is to install a new WS2k3/Ex2k3 server into the
Ex5.5 organization, move all mailboxes to it, then decommission the old Ex5.5
box. While waiting for my maintenance window to upgrade the current ADC to the
2k3 version, I installed EX2k3 ADC on the new mail server (which is not a DC).
Now, when I try to run the “Data collection” step in ADC tools on
the new ws2k3 box, I receive the error “Server :389 is
not an Exchange 5.5 server or an SRS service”. I realized that since it
was installed on a DC that the LDAP port in ADC was changed to 38900, so I
changed it in ADC tools. However, I am now receiving the error “Could not
connect to server :38900 with LDAP error 6.  Check server
name, port number and account permissions”. I am logged on with the
Enterprise/Domain Administrator account and the ADC service is set to use the
same service account as the ADC on the Ex5.5 server.

 

If you need any more info please let me know.

Any help that anyone can provide will be greatly
appreciated.

 

 

Dan DeStefano

Info-lution Corporation

www.info-lution.com

MCSE - 2073750

 

If you have received this message in error
please notify the sender, disregard any content  and remove it from your
possession.

If you have received this message in error
please notify the sender, disregard any content  and remove it from your
possession.





If you have received this message in error please notify the

RE: [ActiveDir] Exchange 5.5 Upgrade Problems

[Brian Desmond]

Why are you doing this interim upgrade when your end goal is a
2k3 native environment? 

 



Thanks,
Brian Desmond

[EMAIL PROTECTED]

 

c - 312.731.3132

 

 











From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dan DeStefano
Sent: Tuesday, April 18, 2006 9:05 PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Exchange 5.5 Upgrade Problems



 

Yes,
I can connect to the dc/ex5.5 box from the new ex2k3 member server using ldp on
both ports 389 and 38900. I can also bind using the enterprise/domain admin
account and the ex service account.

 

I
am not trying to do a direct upgrade from 5.5 to 2k3, rather I am trying to do
an interim upgrade to ex2k, then upgrade from ex2k to ex2k3. I am receiving the
database inconsistent errors when trying to do the ex2k upgrade.

 

Note:
I am not sure if it matters, but in ex5.5 administrator, the ldap protocol for
the site is set to 38900, but for the server it is set to 389. I tried changing
it in the server to 38900, but that stopped mail from flowing.

 

 

Dan

 









From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian Desmond
Sent: Tuesday, April 18, 2006 8:39 PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Exchange 5.5 Upgrade Problems



 

Could be all sorts of things here, but lets start simple. Can
you do an ldap bind to the exchange box on port 38900 using the ldp tool (or
similar) from the support tools?

 

You can’t do an inplace upgrade from 5.5 to 2003 which is
what it sounds like you’re doing when you get the consistency error.

 

 

 



Thanks,
Brian Desmond

[EMAIL PROTECTED]

 

c - 312.731.3132

 

 











From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dan DeStefano
Sent: Tuesday, April 18, 2006 8:10 PM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] Exchange 5.5 Upgrade Problems



 

I have
taken over administration of a w2k AD domain running Exchange 5.5. This domain
was a mess and it took a lot of doing just to resolve all the errors in the
event logs, but now they are just about all resolved and the DC/Ex5.5 server
passes all netdiag/dcdiag tests.

 

My current
project is to upgrade the Ex5.5 server (which is also the domain’s only
DC) to Ex2k3, but I am running into problems. I have successfully run
Forestprep and Domainprep. However, when I attempt to run the installation, I
receive the error “Exchange… cannot be assigned the task
“upgrade” because… the directory database is in an
inconsistent state… the private and or public stores are in an
inconsistent state”. However, when using Eseutil to check database
consistency of all 3 databases, it reports that they are consistent. Even so, I
tried using Eseutil to: repair all 3 DBs and perform soft recovery on all 3
DBs, but nothing worked. I then ran every test/repair using isinteg, all of
which completed successfully and only some of which reported errors. However,
nothing has worked and I am still getting the same errors when trying to
upgrade. I also upgraded the ADC to the Ex2k SP3 version, which had no effect.

 

Now my plan
is to install a new WS2k3/Ex2k3 server into the Ex5.5 organization, move all
mailboxes to it, then decommission the old Ex5.5 box. While waiting for my
maintenance window to upgrade the current ADC to the 2k3 version, I installed
EX2k3 ADC on the new mail server (which is not a DC). Now, when I try to run
the “Data collection” step in ADC tools on the new ws2k3 box, I
receive the error “Server :389 is not an Exchange 5.5
server or an SRS service”. I realized that since it was installed on a DC
that the LDAP port in ADC was changed to 38900, so I changed it in ADC tools.
However, I am now receiving the error “Could not connect to server
:38900 with LDAP error 6.  Check server name, port number
and account permissions”. I am logged on with the Enterprise/Domain
Administrator account and the ADC service is set to use the same service
account as the ADC on the Ex5.5 server.

 

If you need
any more info please let me know.

Any help
that anyone can provide will be greatly appreciated.

 

 

Dan DeStefano

Info-lution
Corporation

www.info-lution.com

MCSE
- 2073750

 

If you have
received this message in error please notify the sender, disregard any content
 and remove it from your possession.

If you have
received this message in error please notify the sender, disregard any content
 and remove it from your possession.

RE: [ActiveDir] Exchange 5.5 Upgrade Problems

[Dan DeStefano]

Yes, I can connect to the dc/ex5.5 box
from the new ex2k3 member server using ldp on both ports 389 and 38900. I can
also bind using the enterprise/domain admin account and the ex service account.

 

I am not trying to do a direct upgrade
from 5.5 to 2k3, rather I am trying to do an interim upgrade to ex2k, then
upgrade from ex2k to ex2k3. I am receiving the database inconsistent errors
when trying to do the ex2k upgrade.

 

Note: I am not sure if it matters, but in
ex5.5 administrator, the ldap protocol for the site is set to 38900, but for
the server it is set to 389. I tried changing it in the server to 38900, but
that stopped mail from flowing.

 

 

Dan

 









From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Desmond
Sent: Tuesday, April 18, 2006 8:39
PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Exchange
5.5 Upgrade Problems



 

Could be all sorts
of things here, but lets start simple. Can you do an ldap bind to the exchange
box on port 38900 using the ldp tool (or similar) from the support tools?

 

You can’t do
an inplace upgrade from 5.5 to 2003 which is what it sounds like you’re
doing when you get the consistency error.

 

 

 



Thanks,
Brian
Desmond

[EMAIL PROTECTED]

 

c -
312.731.3132

 

 











From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan DeStefano
Sent: Tuesday, April 18, 2006 8:10
PM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] Exchange 5.5
Upgrade Problems



 

I have taken over administration of a w2k AD domain running
Exchange 5.5. This domain was a mess and it took a lot of doing just to resolve
all the errors in the event logs, but now they are just about all resolved and
the DC/Ex5.5 server passes all netdiag/dcdiag tests.

 

My current project is to upgrade the Ex5.5 server (which is
also the domain’s only DC) to Ex2k3, but I am running into problems. I
have successfully run Forestprep and Domainprep. However, when I attempt to run
the installation, I receive the error “Exchange… cannot be assigned
the task “upgrade” because… the directory database is in an
inconsistent state… the private and or public stores are in an
inconsistent state”. However, when using Eseutil to check database
consistency of all 3 databases, it reports that they are consistent. Even so, I
tried using Eseutil to: repair all 3 DBs and perform soft recovery on all 3
DBs, but nothing worked. I then ran every test/repair using isinteg, all of
which completed successfully and only some of which reported errors. However,
nothing has worked and I am still getting the same errors when trying to
upgrade. I also upgraded the ADC to the Ex2k SP3 version, which had no effect.

 

Now my plan is to install a new WS2k3/Ex2k3 server into the
Ex5.5 organization, move all mailboxes to it, then decommission the old Ex5.5
box. While waiting for my maintenance window to upgrade the current ADC to the
2k3 version, I installed EX2k3 ADC on the new mail server (which is not a DC).
Now, when I try to run the “Data collection” step in ADC tools on
the new ws2k3 box, I receive the error “Server :389 is
not an Exchange 5.5 server or an SRS service”. I realized that since it
was installed on a DC that the LDAP port in ADC was changed to 38900, so I
changed it in ADC tools. However, I am now receiving the error “Could not
connect to server :38900 with LDAP error 6.  Check server
name, port number and account permissions”. I am logged on with the
Enterprise/Domain Administrator account and the ADC service is set to use the
same service account as the ADC on the Ex5.5 server.

 

If you need any more info please let me know.

Any help that anyone can provide will be greatly
appreciated.

 

 

Dan DeStefano

Info-lution Corporation

www.info-lution.com

MCSE - 2073750

 

If you have received this message in error
please notify the sender, disregard any content  and remove it from your
possession.





If you have received this message in error please notify the sender, disregard any content  and remove it from your possession.

RE: [ActiveDir] Exchange 5.5 Upgrade Problems

[Brian Desmond]

Could be all sorts of things here, but lets start simple. Can
you do an ldap bind to the exchange box on port 38900 using the ldp tool (or similar)
from the support tools?

 

You can’t do an inplace upgrade from 5.5 to 2003 which is
what it sounds like you’re doing when you get the consistency error.

 

 

 



Thanks,
Brian Desmond

[EMAIL PROTECTED]

 

c - 312.731.3132

 

 











From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dan DeStefano
Sent: Tuesday, April 18, 2006 8:10 PM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] Exchange 5.5 Upgrade Problems



 

I have
taken over administration of a w2k AD domain running Exchange 5.5. This domain
was a mess and it took a lot of doing just to resolve all the errors in the
event logs, but now they are just about all resolved and the DC/Ex5.5 server
passes all netdiag/dcdiag tests.

 

My current
project is to upgrade the Ex5.5 server (which is also the domain’s only
DC) to Ex2k3, but I am running into problems. I have successfully run
Forestprep and Domainprep. However, when I attempt to run the installation, I
receive the error “Exchange… cannot be assigned the task
“upgrade” because… the directory database is in an
inconsistent state… the private and or public stores are in an
inconsistent state”. However, when using Eseutil to check database
consistency of all 3 databases, it reports that they are consistent. Even so, I
tried using Eseutil to: repair all 3 DBs and perform soft recovery on all 3
DBs, but nothing worked. I then ran every test/repair using isinteg, all of
which completed successfully and only some of which reported errors. However,
nothing has worked and I am still getting the same errors when trying to
upgrade. I also upgraded the ADC to the Ex2k SP3 version, which had no effect.

 

Now my plan
is to install a new WS2k3/Ex2k3 server into the Ex5.5 organization, move all
mailboxes to it, then decommission the old Ex5.5 box. While waiting for my
maintenance window to upgrade the current ADC to the 2k3 version, I installed
EX2k3 ADC on the new mail server (which is not a DC). Now, when I try to run
the “Data collection” step in ADC tools on the new ws2k3 box, I
receive the error “Server :389 is not an Exchange 5.5
server or an SRS service”. I realized that since it was installed on a DC
that the LDAP port in ADC was changed to 38900, so I changed it in ADC tools.
However, I am now receiving the error “Could not connect to server
:38900 with LDAP error 6.  Check server name, port number
and account permissions”. I am logged on with the Enterprise/Domain
Administrator account and the ADC service is set to use the same service
account as the ADC on the Ex5.5 server.

 

If you need
any more info please let me know.

Any help
that anyone can provide will be greatly appreciated.

 

 

Dan DeStefano

Info-lution
Corporation

www.info-lution.com

MCSE
- 2073750

 

If you have
received this message in error please notify the sender, disregard any content
 and remove it from your possession.

RE: [ActiveDir] Exchange 5.5

[Philadelphia, Lynden - Revios Toronto]

Title: Message








Do you have a white paper on the procedure?

 



 

Lynden 











From: Adams, Kenneth W
(Ken) [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 17, 2005
4:10 PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Exchange
5.5



 



IIRC, IF the folders have been replicated
to another Exchange 5.5 server, you can specify the home server on that other
server.  I had that happen to me years ago, so I'm not positive about the
procedure.



Ken
Adams 

-Original Message-
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Philadelphia, Lynden - Revios Toronto
Sent: Thursday, February 17, 2005
4:02 PM
To: 'ActiveDir@mail.activedir.org'
Subject: [ActiveDir] Exchange 5.5

Has anyone come across an article on how to take
control of public folders if the home server is gone? 

 


 
  This message is intended for the use of the individual or entity to which it is addressedand may contain information that is privileged, confidential and exempt from disclosureunder applicable law.  If the reader of this message in not the intended recipient or theemployer or agent responsible for delivering the message to the recipient, you arehereby notified that dissemination, distribution or copying of this communication isstrictly prohibited.  If you have received this communication in error, please notify usimmediately by email or telephone, and delete this message and all of its attachments.
 


 







This message is intended for the use of the individual or entity to which it is addressed
and may contain information that is privileged, confidential and exempt from disclosure
under applicable law.  If the reader of this message in not the intended recipient or the
employer or agent responsible for delivering the message to the recipient, you are
hereby notified that dissemination, distribution or copying of this communication is
strictly prohibited.  If you have received this communication in error, please notify us
immediately by email or telephone, and delete this message and all of its attachments.

RE: [ActiveDir] Exchange 5.5

[Adams, Kenneth W \(Ken\)]

Title: Message



IIRC, 
IF the folders have been replicated to another Exchange 5.5 server, you can 
specify the home server on that other server.  I had that happen to me 
years ago, so I'm not positive about the procedure.
Ken Adams 

-Original Message-From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
On Behalf Of Philadelphia, Lynden - Revios TorontoSent: 
Thursday, February 17, 2005 4:02 PMTo: 
'ActiveDir@mail.activedir.org'Subject: [ActiveDir] Exchange 
5.5

Has anyone come across an article on how to take control 
of public folders if the home server is gone? 
 

  
  
This message is intended for the use of the individual or entity to which it is addressed
and may contain information that is privileged, confidential and exempt from disclosure
under applicable law.  If the reader of this message in not the intended recipient or the
employer or agent responsible for delivering the message to the recipient, you are
hereby notified that dissemination, distribution or copying of this communication is
strictly prohibited.  If you have received this communication in error, please notify us
immediately by email or telephone, and delete this message and all of its attachments.

RE: [ActiveDir] exchange 5.5, active directory and ADC

[Roger Seielstad]

Yes. Its pretty flexible for that
 
-- 
Roger D. Seielstad - 
MTS MCSE MS-MVP Sr. Systems Administrator Inovis Inc. 
 

  
  
  From: Chaudhary, Amit 
  [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 01, 2004 
  2:21 AMTo: [EMAIL PROTECTED]Subject: RE: 
  [ActiveDir] exchange 5.5, active directory and ADC
  
  
  Nick
   
  Cheers, can you 
  configure ADC to create any accounts it needs to in a separate container in 
  the AD?
   
  
  
  
  
  From: 
  [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
  On Behalf Of Nicolas 
  BlankSent: 01 June 2004 
  10:04To: 
  [EMAIL PROTECTED]Subject: RE: [ActiveDir] exchange 5.5, 
  active directory and ADC
   
  Amit,
  Depending on how the 
  accounts were created, it is possible to use the ADC to match accounts already 
  existing in AD. If no match is found for a 5.5 mailbox, a duplicate account 
  will be created in AD.  The default matching rule will match the 5.5 
  associated-NT-Account field to the AD account’s sid or sidHistory attribute. 
   You may extend the matching rules in the ADC so that you can match RDN 
  to CN or a mail alias to samaccountname ifyou have a match between those. I 
  strongly suggest you read the article below: 
   
  Understanding and 
  Deploying Exchange 2000 Active Directory 
Connector
  http://www.microsoft.com/downloads/details.aspx?FamilyID=c763b584-c511-4687-b27f-a13a8f82d4c8&displaylang=en
   
  If you configure your 
  ADC incorrectly, you may only have duplicate accounts, but at worst case you 
  might lose mail.
   
   
  -Original 
  Message-From: 
  [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
  On Behalf Of Chaudhary, 
  AmitSent: 01 June 2004 10:13 
  AMTo: 
  [EMAIL PROTECTED]Subject: [ActiveDir] exchange 5.5, active 
  directory and ADC
   
  Hi
   
  This maybe a bit of 
  topic but I was hoping to get some advice from the 
  list.
   
  I have a Windows 2000 
  active directory environment, one of my Windows 2000 servers is running 
  exchange 5.5 (not a DC). We have been considering moving to exchange 2003, the 
  migration method was to join exchange 2003 to the existing site, move the 
  mailboxes and then bring down the old server. The problem is that I have come 
  across the Active Directory Connector and I wanted to get some more 
  information on this, as I have been told it has not been installed on my site. 
  I.e. the 5.5 directory is not updating the active directory and vice 
  versa.
   
  If we were to install 
  the Active Directory Connector, would exchange create new accounts in my AD 
  for all the mailboxes I have in my mail system, or will it see that active 
  directory accounts are already created? The AD accounts are created as 
  firstname lastname, but the 
  display names for our email accounts are lastname, firstname. What will be the 
  overall affect on my AD of installing this connector and enabling 
  bi-directional communication?
   
  Regards
   
  Amit

RE: [ActiveDir] exchange 5.5, active directory and ADC

[Roger Seielstad]

It goes through a whole matching process - in a nutshell, 
it will match the accounts based on the Primary Windows NT account attribute in 
the Exchange DS. There's a whole lot of documentation on the ADC on 
Microsoft.com/exchange
 
 
-- 
Roger D. Seielstad - 
MTS MCSE MS-MVP Sr. Systems Administrator Inovis Inc. 
 

  
  
  From: Chaudhary, Amit 
  [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 01, 2004 
  1:13 AMTo: [EMAIL PROTECTED]Subject: 
  [ActiveDir] exchange 5.5, active directory and ADC
  
  
  Hi
   
  This maybe a bit of topic but I 
  was hoping to get some advice from the list.
   
  I have a Windows 2000 active 
  directory environment, one of my Windows 2000 servers is running exchange 5.5 
  (not a DC). We have been considering moving to exchange 2003, the migration 
  method was to join exchange 2003 to the existing site, move the mailboxes and 
  then bring down the old server. The problem is that I have come across the 
  Active Directory Connector and I wanted to get some more information on this, 
  as I have been told it has not been installed on my site. I.e. the 5.5 
  directory is not updating the active directory and vice 
  versa.
   
  If we were to install the Active 
  Directory Connector, would exchange create new accounts in my AD for all the 
  mailboxes I have in my mail system, or will it see that active directory 
  accounts are already created? The AD accounts are created as firstname lastname, but the display 
  names for our email accounts are lastname, 
  firstname. What will be the overall affect on my AD of installing 
  this connector and enabling bi-directional 
  communication?
   
  Regards
   
  Amit

RE: [ActiveDir] exchange 5.5, active directory and ADC

[Ayers, Diane]

I'll second Nick's comment to test 
your implementation in a lab setup first before doing it live.  There are 
some subtle (and not so subtle) things that you can do to hose your production 
setup.  The first lab run we did hosed our lab but we learned.  That's 
what labs are for
 
Diane


From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of Nicolas 
BlankSent: Tuesday, June 01, 2004 3:11 AMTo: 
[EMAIL PROTECTED]Subject: RE: [ActiveDir] exchange 5.5, 
active directory and ADC


Correct, suggest since 
you haven’t worked with the ADC before that you lab/vmware this at least once, 
and document your process before trying this in production. This way you’ll have 
something to work with without being tempted to tick any options you haven’t 
seen work in the lab before.
 
-Original 
Message-From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
On Behalf Of Chaudhary, 
AmitSent: 01 June 2004 11:49 
AMTo: 
[EMAIL PROTECTED]Subject: RE: [ActiveDir] exchange 5.5, 
active directory and ADC
 
Sorry 

 
But 
want to make sure I’m understanding you here. You suggesting set schedule to 
never, until the ADC is inplace and working ok? Then moving it to a schedule? We 
don’t plan to completely shut down the old exchange server for a few weeks at 
least.
 
Anything else I 
should be aware off adding the ADC in terms of this migration to Exchange 
2003
 




From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
On Behalf Of Nicolas 
BlankSent: 01 June 2004 
10:39To: 
[EMAIL PROTECTED]Subject: RE: [ActiveDir] exchange 5.5, 
active directory and ADC
 
Yip, the 
AD container/OU is selectable whilst creating the recipient agreement 
connection. Suggest the first thing you configure is setting your schedule to 
“NEVER”, and finish your other bits and pieces.
 
-Original 
Message-From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
On Behalf Of Chaudhary, 
AmitSent: 01 June 2004 11:21 
AMTo: 
[EMAIL PROTECTED]Subject: RE: [ActiveDir] exchange 5.5, 
active directory and ADC
 
Nick
 
Cheers, 
can you configure ADC to create any accounts it needs to in a separate container 
in the AD?
 





From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
On Behalf Of Nicolas 
BlankSent: 01 June 2004 
10:04To: 
[EMAIL PROTECTED]Subject: RE: [ActiveDir] exchange 5.5, 
active directory and ADC
 
Amit,
Depending 
on how the accounts were created, it is possible to use the ADC to match 
accounts already existing in AD. If no match is found for a 5.5 mailbox, a 
duplicate account will be created in AD.  The default matching rule will 
match the 5.5 associated-NT-Account field to the AD account’s sid or sidHistory 
attribute.  You may extend the matching rules in the ADC so that you can 
match RDN to CN or a mail alias to samaccountname ifyou have a match between 
those. I strongly suggest you read the article below: 
 
Understanding and 
Deploying Exchange 2000 Active Directory Connector
http://www.microsoft.com/downloads/details.aspx?FamilyID=c763b584-c511-4687-b27f-a13a8f82d4c8&displaylang=en
 
If you 
configure your ADC incorrectly, you may only have duplicate accounts, but at 
worst case you might lose mail.
 
 
-Original 
Message-From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
On Behalf Of Chaudhary, 
AmitSent: 01 June 2004 10:13 
AMTo: 
[EMAIL PROTECTED]Subject: [ActiveDir] exchange 5.5, active 
directory and ADC
 
Hi
 
This maybe a bit of topic 
but I was hoping to get some advice from the list.
 
I have a Windows 2000 
active directory environment, one of my Windows 2000 servers is running exchange 
5.5 (not a DC). We have been considering moving to exchange 2003, the migration 
method was to join exchange 2003 to the existing site, move the mailboxes and 
then bring down the old server. The problem is that I have come across the 
Active Directory Connector and I wanted to get some more information on this, as 
I have been told it has not been installed on my site. I.e. the 5.5 
directory is not updating the active directory and vice versa.
 
If we were to install the 
Active Directory Connector, would exchange create new accounts in my AD for all 
the mailboxes I have in my mail system, or will it see that active directory 
accounts are already created? The AD accounts are created as firstname lastname, but the display names 
for our email accounts are lastname, 
firstname. What will be the overall affect on my AD of installing 
this connector and enabling bi-directional communication?
 
Regards
 
Amit

RE: [ActiveDir] exchange 5.5, active directory and ADC

[Chaudhary, Amit]

Cheers for all the
info

 









From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Coleman, Hunter
Sent: 01 June 2004 15:30
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] exchange
5.5, active directory and ADC



 

This is a fat document that is great for
getting up to speed on the ADC:

http://www.microsoft.com/technet/prodtechnol/exchange/2000/library/udadc.mspx

 

It talks about Exchange 2000, but all of
the concepts and a lot of the specifics will carry over to Exch 2003

 

Hunter

 







From: Chaudhary, Amit [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 01, 2004 3:49
AM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] exchange
5.5, active directory and ADC

Sorry 

 

But want to make sure
I’m understanding you here. You suggesting set schedule to never, until
the ADC is inplace and working ok? Then moving it to a schedule? We don’t
plan to completely shut down the old exchange server for a few weeks at least.

 

Anything else I should
be aware off adding the ADC in terms of this migration to Exchange 2003

 









From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nicolas Blank
Sent: 01 June 2004 10:39
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] exchange
5.5, active directory and ADC



 

Yip, the AD container/OU is selectable
whilst creating the recipient agreement connection. Suggest the first thing you
configure is setting your schedule to “NEVER”, and finish your
other bits and pieces.

 

-Original Message-
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chaudhary,
 Amit
Sent: 01 June 2004 11:21 AM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] exchange
5.5, active directory and ADC

 

Nick

 

Cheers,
can you configure ADC to create any accounts it needs to in a separate
container in the AD?

 













From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nicolas Blank
Sent: 01 June 2004 10:04
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] exchange
5.5, active directory and ADC



 

Amit,

Depending
on how the accounts were created, it is possible to use the ADC to match
accounts already existing in AD. If no match is found for a 5.5 mailbox, a
duplicate account will be created in AD.  The default matching rule will
match the 5.5 associated-NT-Account field to the AD account’s sid or
sidHistory attribute.  You may extend the matching rules in the ADC so
that you can match RDN to CN or a mail alias to samaccountname ifyou have a
match between those. I strongly suggest you read the article below: 

 

Understanding
and Deploying Exchange 2000 Active Directory Connector

http://www.microsoft.com/downloads/details.aspx?FamilyID=c763b584-c511-4687-b27f-a13a8f82d4c8&displaylang=en

 

If you
configure your ADC incorrectly, you may only have duplicate accounts, but at
worst case you might lose mail.

 

 

-Original Message-
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chaudhary,
 Amit
Sent: 01 June 2004 10:13 AM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] exchange 5.5,
active directory and ADC

 

Hi

 

This maybe a bit of topic
but I was hoping to get some advice from the list.

 

I have a Windows 2000
active directory environment, one of my Windows 2000 servers is running
exchange 5.5 (not a DC). We have been considering moving to exchange 2003, the
migration method was to join exchange 2003 to the existing site, move the
mailboxes and then bring down the old server. The problem is that I have come
across the Active Directory Connector and I wanted to get some more information
on this, as I have been told it has not been installed on my site. I.e.
the 5.5 directory is not updating the active directory and vice versa.

 

If we were to install the
Active Directory Connector, would exchange create new accounts in my AD for all
the mailboxes I have in my mail system, or will it see that active directory
accounts are already created? The AD accounts are created as firstname lastname, but the display names
for our email accounts are lastname,
firstname. What will be the overall affect on my AD of installing
this connector and enabling bi-directional communication?

 

Regards

 

Amit

RE: [ActiveDir] exchange 5.5, active directory and ADC

[Coleman, Hunter]

This is a fat document that is great for getting up to 
speed on the ADC:
http://www.microsoft.com/technet/prodtechnol/exchange/2000/library/udadc.mspx
 
It talks about Exchange 2000, but all of the concepts and a 
lot of the specifics will carry over to Exch 2003
 
Hunter


From: Chaudhary, Amit 
[mailto:[EMAIL PROTECTED] Sent: Tuesday, June 01, 2004 3:49 
AMTo: [EMAIL PROTECTED]Subject: RE: [ActiveDir] 
exchange 5.5, active directory and ADC


Sorry 

 
But want to make 
sure I’m understanding you here. You suggesting set schedule to never, until the 
ADC is inplace and working ok? Then moving it to a schedule? We don’t plan to 
completely shut down the old exchange server for a few weeks at 
least.
 
Anything else I 
should be aware off adding the ADC in terms of this migration to Exchange 
2003
 




From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
On Behalf Of Nicolas 
BlankSent: 01 June 2004 
10:39To: 
[EMAIL PROTECTED]Subject: RE: [ActiveDir] exchange 5.5, 
active directory and ADC
 
Yip, the AD 
container/OU is selectable whilst creating the recipient agreement connection. 
Suggest the first thing you configure is setting your schedule to “NEVER”, and 
finish your other bits and pieces.
 
-Original 
Message-From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
On Behalf Of Chaudhary, 
AmitSent: 01 June 2004 11:21 
AMTo: 
[EMAIL PROTECTED]Subject: RE: [ActiveDir] exchange 5.5, 
active directory and ADC
 
Nick
 
Cheers, 
can you configure ADC to create any accounts it needs to in a separate container 
in the AD?
 





From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
On Behalf Of Nicolas 
BlankSent: 01 June 2004 
10:04To: 
[EMAIL PROTECTED]Subject: RE: [ActiveDir] exchange 5.5, 
active directory and ADC
 
Amit,
Depending 
on how the accounts were created, it is possible to use the ADC to match 
accounts already existing in AD. If no match is found for a 5.5 mailbox, a 
duplicate account will be created in AD.  The default matching rule will 
match the 5.5 associated-NT-Account field to the AD account’s sid or sidHistory 
attribute.  You may extend the matching rules in the ADC so that you can 
match RDN to CN or a mail alias to samaccountname ifyou have a match between 
those. I strongly suggest you read the article below: 

 
Understanding and 
Deploying Exchange 2000 Active Directory Connector
http://www.microsoft.com/downloads/details.aspx?FamilyID=c763b584-c511-4687-b27f-a13a8f82d4c8&displaylang=en
 
If you 
configure your ADC incorrectly, you may only have duplicate accounts, but at 
worst case you might lose mail.
 
 
-Original 
Message-From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
On Behalf Of Chaudhary, 
AmitSent: 01 June 2004 10:13 
AMTo: 
[EMAIL PROTECTED]Subject: [ActiveDir] exchange 5.5, active 
directory and ADC
 
Hi
 
This maybe a bit of topic 
but I was hoping to get some advice from the list.
 
I have a Windows 2000 
active directory environment, one of my Windows 2000 servers is running exchange 
5.5 (not a DC). We have been considering moving to exchange 2003, the migration 
method was to join exchange 2003 to the existing site, move the mailboxes and 
then bring down the old server. The problem is that I have come across the 
Active Directory Connector and I wanted to get some more information on this, as 
I have been told it has not been installed on my site. I.e. the 5.5 
directory is not updating the active directory and vice 
versa.
 
If we were to install the 
Active Directory Connector, would exchange create new accounts in my AD for all 
the mailboxes I have in my mail system, or will it see that active directory 
accounts are already created? The AD accounts are created as firstname lastname, but the display names 
for our email accounts are lastname, 
firstname. What will be the overall affect on my AD of installing 
this connector and enabling bi-directional 
communication?
 
Regards
 
Amit

RE: [ActiveDir] exchange 5.5, active directory and ADC

[Nicolas Blank]

Correct, suggest since you haven’t
worked with the ADC before that you lab/vmware this at least once, and document
your process before trying this in production. This way you’ll have
something to work with without being tempted to tick any options you haven’t
seen work in the lab before.

 

-Original Message-
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chaudhary, Amit
Sent: 01 June 2004 11:49 AM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] exchange
5.5, active directory and ADC

 

Sorry


 

But
want to make sure I’m understanding you here. You suggesting set schedule
to never, until the ADC is inplace and working ok? Then moving it to a
schedule? We don’t plan to completely shut down the old exchange server
for a few weeks at least.

 

Anything
else I should be aware off adding the ADC in terms of this migration to
Exchange 2003

 









From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nicolas Blank
Sent: 01 June 2004 10:39
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] exchange
5.5, active directory and ADC



 

Yip, the
AD container/OU is selectable whilst creating the recipient agreement
connection. Suggest the first thing you configure is setting your schedule to
“NEVER”, and finish your other bits and pieces.

 

-Original Message-
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chaudhary, Amit
Sent: 01 June 2004 11:21 AM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] exchange
5.5, active directory and ADC

 

Nick

 

Cheers,
can you configure ADC to create any accounts it needs to in a separate
container in the AD?

 













From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nicolas Blank
Sent: 01 June 2004 10:04
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] exchange
5.5, active directory and ADC



 

Amit,

Depending
on how the accounts were created, it is possible to use the ADC to match
accounts already existing in AD. If no match is found for a 5.5 mailbox, a
duplicate account will be created in AD.  The default matching rule will
match the 5.5 associated-NT-Account field to the AD account’s sid or
sidHistory attribute.  You may extend the matching rules in the ADC so
that you can match RDN to CN or a mail alias to samaccountname ifyou have a
match between those. I strongly suggest you read the article below: 

 

Understanding
and Deploying Exchange 2000 Active Directory Connector

http://www.microsoft.com/downloads/details.aspx?FamilyID=c763b584-c511-4687-b27f-a13a8f82d4c8&displaylang=en

 

If you
configure your ADC incorrectly, you may only have duplicate accounts, but at
worst case you might lose mail.

 

 

-Original Message-
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chaudhary, Amit
Sent: 01 June 2004 10:13 AM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] exchange 5.5,
active directory and ADC

 

Hi

 

This maybe a bit of topic
but I was hoping to get some advice from the list.

 

I have a Windows 2000
active directory environment, one of my Windows 2000 servers is running
exchange 5.5 (not a DC). We have been considering moving to exchange 2003, the
migration method was to join exchange 2003 to the existing site, move the
mailboxes and then bring down the old server. The problem is that I have come
across the Active Directory Connector and I wanted to get some more information
on this, as I have been told it has not been installed on my site. I.e.
the 5.5 directory is not updating the active directory and vice versa.

 

If we were to install the
Active Directory Connector, would exchange create new accounts in my AD for all
the mailboxes I have in my mail system, or will it see that active directory
accounts are already created? The AD accounts are created as firstname lastname, but the display names
for our email accounts are lastname,
firstname. What will be the overall affect on my AD of installing
this connector and enabling bi-directional communication?

 

Regards

 

Amit

RE: [ActiveDir] exchange 5.5, active directory and ADC

[Chaudhary, Amit]

Sorry 

 

But want to make sure I’m
understanding you here. You suggesting set schedule to never, until the ADC is
inplace and working ok? Then moving it to a schedule? We don’t plan to
completely shut down the old exchange server for a few weeks at least.

 

Anything else I should
be aware off adding the ADC in terms of this migration to Exchange 2003

 









From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nicolas Blank
Sent: 01 June 2004 10:39
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] exchange
5.5, active directory and ADC



 

Yip, the AD container/OU is selectable
whilst creating the recipient agreement connection. Suggest the first thing you
configure is setting your schedule to “NEVER”, and finish your
other bits and pieces.

 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Chaudhary, Amit
Sent: 01 June 2004 11:21 AM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] exchange
5.5, active directory and ADC

 

Nick

 

Cheers,
can you configure ADC to create any accounts it needs to in a separate
container in the AD?

 













From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nicolas Blank
Sent: 01 June 2004 10:04
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] exchange
5.5, active directory and ADC



 

Amit,

Depending
on how the accounts were created, it is possible to use the ADC to match
accounts already existing in AD. If no match is found for a 5.5 mailbox, a
duplicate account will be created in AD.  The default matching rule will
match the 5.5 associated-NT-Account field to the AD account’s sid or
sidHistory attribute.  You may extend the matching rules in the ADC so
that you can match RDN to CN or a mail alias to samaccountname ifyou have a
match between those. I strongly suggest you read the article below: 

 

Understanding
and Deploying Exchange 2000 Active Directory Connector

http://www.microsoft.com/downloads/details.aspx?FamilyID=c763b584-c511-4687-b27f-a13a8f82d4c8&displaylang=en

 

If you
configure your ADC incorrectly, you may only have duplicate accounts, but at
worst case you might lose mail.

 

 

-Original Message-
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chaudhary, Amit
Sent: 01 June 2004 10:13 AM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] exchange 5.5,
active directory and ADC

 

Hi

 

This maybe a bit of topic
but I was hoping to get some advice from the list.

 

I have a Windows 2000
active directory environment, one of my Windows 2000 servers is running
exchange 5.5 (not a DC). We have been considering moving to exchange 2003, the
migration method was to join exchange 2003 to the existing site, move the
mailboxes and then bring down the old server. The problem is that I have come
across the Active Directory Connector and I wanted to get some more information
on this, as I have been told it has not been installed on my site. I.e.
the 5.5 directory is not updating the active directory and vice versa.

 

If we were to install the
Active Directory Connector, would exchange create new accounts in my AD for all
the mailboxes I have in my mail system, or will it see that active directory
accounts are already created? The AD accounts are created as firstname lastname, but the display names
for our email accounts are lastname,
firstname. What will be the overall affect on my AD of installing
this connector and enabling bi-directional communication?

 

Regards

 

Amit

RE: [ActiveDir] exchange 5.5, active directory and ADC

[Nicolas Blank]

Yip, the AD container/OU is selectable
whilst creating the recipient agreement connection. Suggest the first thing you
configure is setting your schedule to “NEVER”, and finish your
other bits and pieces.

 

-Original Message-
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chaudhary, Amit
Sent: 01 June 2004 11:21 AM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] exchange
5.5, active directory and ADC

 

Nick

 

Cheers,
can you configure ADC to create any accounts it needs to in a separate
container in the AD?

 









From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nicolas Blank
Sent: 01 June 2004 10:04
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] exchange
5.5, active directory and ADC



 

Amit,

Depending
on how the accounts were created, it is possible to use the ADC to match
accounts already existing in AD. If no match is found for a 5.5 mailbox, a
duplicate account will be created in AD.  The default matching rule will
match the 5.5 associated-NT-Account field to the AD account’s sid or
sidHistory attribute.  You may extend the matching rules in the ADC so
that you can match RDN to CN or a mail alias to samaccountname ifyou have a
match between those. I strongly suggest you read the article below: 

 

Understanding
and Deploying Exchange 2000 Active Directory Connector

http://www.microsoft.com/downloads/details.aspx?FamilyID=c763b584-c511-4687-b27f-a13a8f82d4c8&displaylang=en

 

If you
configure your ADC incorrectly, you may only have duplicate accounts, but at
worst case you might lose mail.

 

 

-Original Message-
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chaudhary, Amit
Sent: 01 June 2004 10:13 AM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] exchange 5.5,
active directory and ADC

 

Hi

 

This maybe a bit of topic
but I was hoping to get some advice from the list.

 

I have a Windows 2000
active directory environment, one of my Windows 2000 servers is running
exchange 5.5 (not a DC). We have been considering moving to exchange 2003, the
migration method was to join exchange 2003 to the existing site, move the
mailboxes and then bring down the old server. The problem is that I have come
across the Active Directory Connector and I wanted to get some more information
on this, as I have been told it has not been installed on my site. I.e.
the 5.5 directory is not updating the active directory and vice versa.

 

If we were to install the
Active Directory Connector, would exchange create new accounts in my AD for all
the mailboxes I have in my mail system, or will it see that active directory
accounts are already created? The AD accounts are created as firstname lastname, but the display names
for our email accounts are lastname,
firstname. What will be the overall affect on my AD of installing
this connector and enabling bi-directional communication?

 

Regards

 

Amit

RE: [ActiveDir] exchange 5.5, active directory and ADC

[Chaudhary, Amit]

Nick

 

Cheers, can you
configure ADC to create any accounts it needs to in a separate container in the
AD?

 









From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nicolas Blank
Sent: 01 June 2004 10:04
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] exchange
5.5, active directory and ADC



 

Amit,

Depending on how the accounts were
created, it is possible to use the ADC to match accounts already existing in
AD. If no match is found for a 5.5 mailbox, a duplicate account will be created
in AD.  The default matching rule will match the 5.5 associated-NT-Account
field to the AD account’s sid or sidHistory attribute.  You may
extend the matching rules in the ADC so that you can match RDN to CN or a mail
alias to samaccountname ifyou have a match between those. I strongly suggest
you read the article below: 

 

Understanding and Deploying Exchange 2000
Active Directory Connector

http://www.microsoft.com/downloads/details.aspx?FamilyID=c763b584-c511-4687-b27f-a13a8f82d4c8&displaylang=en

 

If you configure your ADC incorrectly, you
may only have duplicate accounts, but at worst case you might lose mail.

 

 

-Original Message-
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chaudhary, Amit
Sent: 01 June 2004 10:13 AM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] exchange 5.5,
active directory and ADC

 

Hi

 

This maybe a bit of topic
but I was hoping to get some advice from the list.

 

I have a Windows 2000
active directory environment, one of my Windows 2000 servers is running
exchange 5.5 (not a DC). We have been considering moving to exchange 2003, the
migration method was to join exchange 2003 to the existing site, move the
mailboxes and then bring down the old server. The problem is that I have come
across the Active Directory Connector and I wanted to get some more information
on this, as I have been told it has not been installed on my site. I.e.
the 5.5 directory is not updating the active directory and vice versa.

 

If we were to install the
Active Directory Connector, would exchange create new accounts in my AD for all
the mailboxes I have in my mail system, or will it see that active directory
accounts are already created? The AD accounts are created as firstname lastname, but the display names
for our email accounts are lastname,
firstname. What will be the overall affect on my AD of installing
this connector and enabling bi-directional communication?

 

Regards

 

Amit

RE: [ActiveDir] exchange 5.5, active directory and ADC

[Nicolas Blank]

Amit,

Depending on how the accounts were
created, it is possible to use the ADC to match accounts already existing in
AD. If no match is found for a 5.5 mailbox, a duplicate account will be created
in AD.  The default matching rule will match the 5.5 associated-NT-Account
field to the AD account’s sid or sidHistory attribute.  You may
extend the matching rules in the ADC so that you can match RDN to CN or a mail
alias to samaccountname ifyou have a match between those. I strongly suggest
you read the article below: 

 

Understanding and Deploying Exchange 2000
Active Directory Connector

http://www.microsoft.com/downloads/details.aspx?FamilyID=c763b584-c511-4687-b27f-a13a8f82d4c8&displaylang=en

 

If you configure your ADC incorrectly, you
may only have duplicate accounts, but at worst case you might lose mail.

 

 

-Original Message-
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chaudhary, Amit
Sent: 01 June 2004 10:13 AM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] exchange 5.5,
active directory and ADC

 

Hi

 

This maybe a bit of topic
but I was hoping to get some advice from the list.

 

I have a Windows 2000
active directory environment, one of my Windows 2000 servers is running
exchange 5.5 (not a DC). We have been considering moving to exchange 2003, the
migration method was to join exchange 2003 to the existing site, move the
mailboxes and then bring down the old server. The problem is that I have come
across the Active Directory Connector and I wanted to get some more information
on this, as I have been told it has not been installed on my site. I.e.
the 5.5 directory is not updating the active directory and vice versa.

 

If we were to install the
Active Directory Connector, would exchange create new accounts in my AD for all
the mailboxes I have in my mail system, or will it see that active directory
accounts are already created? The AD accounts are created as firstname lastname, but the display names
for our email accounts are lastname,
firstname. What will be the overall affect on my AD of installing
this connector and enabling bi-directional communication?

 

Regards

 

Amit

RE: [ActiveDir] Exchange 5.5 and active directory connector errors

[Salandra, Justin A.]

Have you
setup all your connection agreements correctly to replicate two way from exchange
5.5 to AD?

Have you
setup a Public Folder Connection Agreement?

 

-Original
Message-
From: Rick Reynolds
[mailto:[EMAIL PROTECTED]
Sent: Thursday, June 05, 2003 2:06
PM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] Exchange 5.5
and active directory connector errors

 

While
trying to install Exchange 2000 where the active directory is installed. 

I keep
getting the following error. 

 

Setup
has detected that the Exchange 5.5 site your server belongs to has not
replicated to the Active Directory yet. You can either wait for replication to
complete and try the upgrade again or upgrade a server from a site that has
already been replicated to the AD.

 

I have
tried all that I can find on the microsoft knowledge base, and am trying here
before I spend the money to call Microsoft. 

 

RE: [ActiveDir] Exchange 5.5 and active directory connector errors

[Garello, Kenneth]

That message comes up if the install
account does not have the proper privileges.

 

I used the exchange 5.5 service account which
is a domain administrator to install.

 

Ken

 

-Original Message-
From: Salandra, Justin A.
[mailto:[EMAIL PROTECTED] 
Sent: Thursday, June 05, 2003 2:15
PM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Exchange
5.5 and active directory connector error s

 

Have you setup all your connection agreements correctly to replicate
two way from exchange 5.5 to AD?

Have you setup a Public Folder Connection Agreement?

 

-Original
Message-
From: Rick Reynolds
[mailto:[EMAIL PROTECTED]
Sent: Thursday, June 05, 2003 2:06
PM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] Exchange 5.5
and active directory connector errors

 

While
trying to install Exchange 2000 where the active directory is installed. 

I keep
getting the following error. 

 

Setup
has detected that the Exchange 5.5 site your server belongs to has not
replicated to the Active Directory yet. You can either wait for replication to
complete and try the upgrade again or upgrade a server from a site that has
already been replicated to the AD.

 

I have
tried all that I can find on the microsoft knowledge base, and am trying here
before I spend the money to call Microsoft. 

 

RE: [ActiveDir] Exchange 5.5 and AD

[gasseru]

I had the same problem in our enviroment.
The following workaround should prevent you from the automatcally back changes after 
you haver corrected the problem manually.
In the AD under the Exchange Advanced Tab go to the Mailbox Rights from the User and 
remove the User "self" instead join the Useraccount with "Full Mailbox access" to the 
mailbox rights.
After this change it should be stable.


Urs



-Original Message-
From: Salandra, Justin A. [mailto:[EMAIL PROTECTED]] 
Sent: Dienstag, 26. November 2002 16:03
To: ActiveDir (E-mail)
Subject: [ActiveDir] Exchange 5.5 and AD
Importance: High


Guys and Girls,

I hope you can help me on this

Microsoft had me update the ADC.EXE from the E2K SP3 CD to avoid my users
mailboxes that were created by the ADC.EXE from losing the mailbox owner
right every few days making me have to go and recheck the box.  Now all
users that are created by the ADC from the E2K SP3 CD are losing the mailbox
owner right and their role is being changed to Custom in the Exchange Admin
program and they are getting a access denied error, and after I change the
permissions in the exchange admin program, a few days later it changes back.
The CA is a two way CA and these users were created while it was a two way
CA.  All those created prior to this version of the ADC are still good.  The
version of the ADC that I have running is 6.0.6249.0 which is a higher
version then what the fix calls for.  If any of you are having this problem
and have found a way to fix it, please let me know.

Thanks 


Justin A. Salandra, MCSE
Senior Network Engineer
Catholic Healthcare System
914.681.8117 office
646.483.3325 cell
[EMAIL PROTECTED]  

List info   : http://www.activedir.org/mail_list.htm
List FAQ: http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/

List info   : http://www.activedir.org/mail_list.htm
List FAQ: http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/

RE: [ActiveDir] Exchange 5.5 upgrade to 2000

[Hutchins, Mike]

I need such a beast Please send forth the knowledge.. :-)

-Original Message-
From: Ken Cornetet [mailto:[EMAIL PROTECTED]] 
Sent: Monday, October 07, 2002 8:58 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Exchange 5.5 upgrade to 2000


Not just public folders! If you use distribution lists to assign
security to
*any* Exchange resource (calendars, inbox, etc.), it will not work in
mixed mode AD.

The good news is that (as Clyde suggests) you can use another AD domain
to host the USGs.

The bad news is that since global catalogs have read-only copies[1] of
groups from other domains, your users can no longer maintain DL
membership from Outlook.

Since this is exactly what we are doing, I had to develop a web based
app[2] to allow users to maintain DLs after they are migrated to E2K
mailboxes. Microsoft also has a freebie DL maintenance tool called
AutoDL (or some
such...) that has quite a bit of capabilities.

[1] Not quite 100% true, but close enough for this discussion. [2]
Written in Perl - I'd be happy to share with anyone who needs such a
beast.

-Original Message-
From: Burns, Clyde [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 07, 2002 8:03 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Exchange 5.5 upgrade to 2000


Jennifer, another thing to think about migrating from Exchange 5.5 to
Exchange 2000. One of the caviats that you are going to run into is
distribution lists in your Windows 2000 mixed mode domain (or lack of).
The ADC creates Universal Security groups in windows 2000 from
distributions lists in Exchange 5.5. These type of groups arent
available in w2k mixed-mode. Which can cause havok on public folders IF
you use distribution lists to give/restrict access to public folders.

<http://support.microsoft.com/default.aspx?scid=kb;en-us;Q316886&sd=tech
> is a good jumping off point to read about this. In your case of not
being able to go native in w2k you may have to setup a temporary native
mode child domain for your distribution lists to live in.

Clyde Burns

-Original Message-
From: Craig Cerino [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 04, 2002 2:19 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Exchange 5.5 upgrade to 2000


Jennifer - you can do what you need right now.

When one of our satellite offices was still in mixed mode they were
running Exchange 5.0 on and NT4.0 box. This box was also a BDC (formerly
the PDC until AD servers were introduced.

I recommend you upgrade your 5.5 box to SP6 (if it's not already there.)
Set up an ADC between the Exchange 5.5 box and one of your AD DC's and
allow replication to begin.

Then when you are ready --- install a separate (preferably new/clean
box) Win 2K Exch 2K server into that exchange site (remembering to run
setup with the /ForestPrep and DomainPrep switches separately) - migrate
your mailboxes over to the 2K box decommission the 5.5 box  and
switch to Exchange Native Mode (which is different than Win2K [AD]
NATIVE MODE).

Then when you are sure you have no remaining NT 4.0 domain controllers
--- switch to Windows 2000 Native Mode.


Craig  



Craig P. Cerino
MCSE, MCP+I
Systems Administrator
TIE SOLUTIONS, Inc
[EMAIL PROTECTED]
www.tiesolutions.com
 


-Original Message-
From: Jennifer Fountain [mailto:[EMAIL PROTECTED]] 
Sent: Friday, October 04, 2002 2:07 PM
To: '[EMAIL PROTECTED]'
Subject: [ActiveDir] Exchange 5.5 upgrade to 2000

We are currently in mixed mode and cannot switch to native.  We
currently
have e5.5 and plan to upgrade to e2k next month.   (since we aren't in
native, we can't do a migrations using the adc - right?) can i setup my
new exchange server (offline) with w2k and e5.5 and then upgrade to 2000
then take down the production 5.5 and put the new 2k box into
production? any gotchas? can i do this? thanks!!



--
Thank you
Jenn Fountain
215.712.5156

List info   : http://www.activedir.org/mail_list.htm
List FAQ: http://www.activedir.org/list_faq.htm
List archive:
http://www.mail-archive.com/activedir%40mail.activedir.org/
List info   : http://www.activedir.org/mail_list.htm
List FAQ: http://www.activedir.org/list_faq.htm
List archive:
http://www.mail-archive.com/activedir%40mail.activedir.org/
List info   : http://www.activedir.org/mail_list.htm
List FAQ: http://www.activedir.org/list_faq.htm
List archive:
http://www.mail-archive.com/activedir%40mail.activedir.org/
List info   : http://www.activedir.org/mail_list.htm
List FAQ: http://www.activedir.org/list_faq.htm
List archive:
http://www.mail-archive.com/activedir%40mail.activedir.org/
List info   : http://www.activedir.org/mail_list.htm
List FAQ: http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/

RE: [ActiveDir] Exchange 5.5 upgrade to 2000

[Burns, Clyde]

While on the topic of distributions lists from 5.5 to 2000, there is one
other support related issue that IMO is worth mentioning. Assigning "Manage"
permissions to Universal Security groups aka distribution lists. In exchange
5.5 theres a nice clean GUI to give a user the ability to add/remove names
from a distribution list. In Exchange 2000 the "Managed by" tab on a group
is "informational only" according to
<http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q281489&;> You cant
use it to give a user manage permissions to the group. You have to give the
user some pretty specific advanced permissions to allow them to manage a
group. 

I will admit though that being able to give a user/group permission to
change the membership of another group without 3rd party software is a
pretty nice thing.

Clyde Burns


-Original Message-
From: Ken Cornetet [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 07, 2002 10:58 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Exchange 5.5 upgrade to 2000


Not just public folders! If you use distribution lists to assign security to
*any* Exchange resource (calendars, inbox, etc.), it will not work in mixed
mode AD.

The good news is that (as Clyde suggests) you can use another AD domain to
host the USGs.

The bad news is that since global catalogs have read-only copies[1] of
groups from other domains, your users can no longer maintain DL membership
from Outlook.

Since this is exactly what we are doing, I had to develop a web based app[2]
to allow users to maintain DLs after they are migrated to E2K mailboxes.
Microsoft also has a freebie DL maintenance tool called AutoDL (or some
such...) that has quite a bit of capabilities.

[1] Not quite 100% true, but close enough for this discussion.
[2] Written in Perl - I'd be happy to share with anyone who needs such a
beast.

-Original Message-
From: Burns, Clyde [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 07, 2002 8:03 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Exchange 5.5 upgrade to 2000


Jennifer, another thing to think about migrating from Exchange 5.5 to
Exchange 2000. One of the caviats that you are going to run into is
distribution lists in your Windows 2000 mixed mode domain (or lack of). The
ADC creates Universal Security groups in windows 2000 from distributions
lists in Exchange 5.5. These type of groups arent available in w2k
mixed-mode. Which can cause havok on public folders IF you use distribution
lists to give/restrict access to public folders.

<http://support.microsoft.com/default.aspx?scid=kb;en-us;Q316886&sd=tech> is
a good jumping off point to read about this. In your case of not being able
to go native in w2k you may have to setup a temporary native mode child
domain for your distribution lists to live in.

Clyde Burns

-Original Message-
From: Craig Cerino [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 04, 2002 2:19 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Exchange 5.5 upgrade to 2000


Jennifer - you can do what you need right now.

When one of our satellite offices was still in mixed mode they were
running Exchange 5.0 on and NT4.0 box. This box was also a BDC (formerly
the PDC until AD servers were introduced.

I recommend you upgrade your 5.5 box to SP6 (if it's not already there.)
Set up an ADC between the Exchange 5.5 box and one of your AD DC's and
allow replication to begin.

Then when you are ready --- install a separate (preferably new/clean
box) Win 2K Exch 2K server into that exchange site (remembering to run
setup with the /ForestPrep and DomainPrep switches separately) - migrate
your mailboxes over to the 2K box decommission the 5.5 box  and
switch to Exchange Native Mode (which is different than Win2K [AD]
NATIVE MODE).

Then when you are sure you have no remaining NT 4.0 domain controllers
--- switch to Windows 2000 Native Mode.


Craig  



Craig P. Cerino
MCSE, MCP+I
Systems Administrator
TIE SOLUTIONS, Inc
[EMAIL PROTECTED]
www.tiesolutions.com
 


-Original Message-
From: Jennifer Fountain [mailto:[EMAIL PROTECTED]] 
Sent: Friday, October 04, 2002 2:07 PM
To: '[EMAIL PROTECTED]'
Subject: [ActiveDir] Exchange 5.5 upgrade to 2000

We are currently in mixed mode and cannot switch to native.  We
currently
have e5.5 and plan to upgrade to e2k next month.   (since we aren't in
native, we can't do a migrations using the adc - right?) can i setup my
new
exchange server (offline) with w2k and e5.5 and then upgrade to 2000
then
take down the production 5.5 and put the new 2k box into production?
any gotchas? can i do this? thanks!!



--
Thank you
Jenn Fountain
215.712.5156

List info   : http://www.activedir.org/mail_list.htm
List FAQ: http://www.activedir.org/list_faq.htm
List archive:
http://www.mail-archive.com/activedir%40mail.activedir.org/
List info   : http://www.acti

RE: [ActiveDir] Exchange 5.5 upgrade to 2000

[Craig Cerino]

Clyde --- that is a GREAT point - we ran into that with one of our
public folders when the small domain I spoke of was migrated -  took me
a while to figure out what the heck was wrong.

It's always the little things.

-Original Message-
From: Burns, Clyde [mailto:[EMAIL PROTECTED]] 
Sent: Monday, October 07, 2002 9:03 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Exchange 5.5 upgrade to 2000

Jennifer, another thing to think about migrating from Exchange 5.5 to
Exchange 2000. One of the caviats that you are going to run into is
distribution lists in your Windows 2000 mixed mode domain (or lack of).
The
ADC creates Universal Security groups in windows 2000 from distributions
lists in Exchange 5.5. These type of groups arent available in w2k
mixed-mode. Which can cause havok on public folders IF you use
distribution
lists to give/restrict access to public folders.

<http://support.microsoft.com/default.aspx?scid=kb;en-us;Q316886&sd=tech
> is
a good jumping off point to read about this. In your case of not being
able
to go native in w2k you may have to setup a temporary native mode child
domain for your distribution lists to live in.

Clyde Burns

-Original Message-
From: Craig Cerino [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 04, 2002 2:19 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Exchange 5.5 upgrade to 2000


Jennifer - you can do what you need right now.

When one of our satellite offices was still in mixed mode they were
running Exchange 5.0 on and NT4.0 box. This box was also a BDC (formerly
the PDC until AD servers were introduced.

I recommend you upgrade your 5.5 box to SP6 (if it's not already there.)
Set up an ADC between the Exchange 5.5 box and one of your AD DC's and
allow replication to begin.

Then when you are ready --- install a separate (preferably new/clean
box) Win 2K Exch 2K server into that exchange site (remembering to run
setup with the /ForestPrep and DomainPrep switches separately) - migrate
your mailboxes over to the 2K box decommission the 5.5 box  and
switch to Exchange Native Mode (which is different than Win2K [AD]
NATIVE MODE).

Then when you are sure you have no remaining NT 4.0 domain controllers
--- switch to Windows 2000 Native Mode.


Craig  



Craig P. Cerino
MCSE, MCP+I
Systems Administrator
TIE SOLUTIONS, Inc
[EMAIL PROTECTED]
www.tiesolutions.com
 


-Original Message-
From: Jennifer Fountain [mailto:[EMAIL PROTECTED]] 
Sent: Friday, October 04, 2002 2:07 PM
To: '[EMAIL PROTECTED]'
Subject: [ActiveDir] Exchange 5.5 upgrade to 2000

We are currently in mixed mode and cannot switch to native.  We
currently
have e5.5 and plan to upgrade to e2k next month.   (since we aren't in
native, we can't do a migrations using the adc - right?) can i setup my
new
exchange server (offline) with w2k and e5.5 and then upgrade to 2000
then
take down the production 5.5 and put the new 2k box into production?
any gotchas? can i do this? thanks!!



--
Thank you
Jenn Fountain
215.712.5156

List info   : http://www.activedir.org/mail_list.htm
List FAQ: http://www.activedir.org/list_faq.htm
List archive:
http://www.mail-archive.com/activedir%40mail.activedir.org/
List info   : http://www.activedir.org/mail_list.htm
List FAQ: http://www.activedir.org/list_faq.htm
List archive:
http://www.mail-archive.com/activedir%40mail.activedir.org/
List info   : http://www.activedir.org/mail_list.htm
List FAQ: http://www.activedir.org/list_faq.htm
List archive:
http://www.mail-archive.com/activedir%40mail.activedir.org/
List info   : http://www.activedir.org/mail_list.htm
List FAQ: http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/

RE: [ActiveDir] Exchange 5.5 upgrade to 2000

[MHR(Michael Ross)]

Title: RE: [ActiveDir] Exchange 5.5 upgrade to 2000






Anyone have the link to the "Six Steps" document? I lost my link.


-Original Message-
From: Burns, Clyde [mailto:[EMAIL PROTECTED]] 
Sent: Monday, October 07, 2002 8:03 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Exchange 5.5 upgrade to 2000



Jennifer, another thing to think about migrating from Exchange 5.5 to Exchange 2000. One of the caviats that you are going to run into is distribution lists in your Windows 2000 mixed mode domain (or lack of). The ADC creates Universal Security groups in windows 2000 from distributions lists in Exchange 5.5. These type of groups arent available in w2k mixed-mode. Which can cause havok on public folders IF you use distribution lists to give/restrict access to public folders.

<http://support.microsoft.com/default.aspx?scid=kb;en-us;Q316886&sd=tech> is a good jumping off point to read about this. In your case of not being able to go native in w2k you may have to setup a temporary native mode child domain for your distribution lists to live in.

Clyde Burns


-Original Message-
From: Craig Cerino [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 04, 2002 2:19 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Exchange 5.5 upgrade to 2000



Jennifer - you can do what you need right now.


When one of our satellite offices was still in mixed mode they were running Exchange 5.0 on and NT4.0 box. This box was also a BDC (formerly the PDC until AD servers were introduced.

I recommend you upgrade your 5.5 box to SP6 (if it's not already there.) Set up an ADC between the Exchange 5.5 box and one of your AD DC's and allow replication to begin.

Then when you are ready --- install a separate (preferably new/clean
box) Win 2K Exch 2K server into that exchange site (remembering to run setup with the /ForestPrep and DomainPrep switches separately) - migrate your mailboxes over to the 2K box decommission the 5.5 box  and switch to Exchange Native Mode (which is different than Win2K [AD] NATIVE MODE).

Then when you are sure you have no remaining NT 4.0 domain controllers
--- switch to Windows 2000 Native Mode.



Craig  




Craig P. Cerino
MCSE, MCP+I
Systems Administrator
TIE SOLUTIONS, Inc
[EMAIL PROTECTED]
www.tiesolutions.com
 



-Original Message-
From: Jennifer Fountain [mailto:[EMAIL PROTECTED]] 
Sent: Friday, October 04, 2002 2:07 PM
To: '[EMAIL PROTECTED]'
Subject: [ActiveDir] Exchange 5.5 upgrade to 2000


We are currently in mixed mode and cannot switch to native.  We currently
have e5.5 and plan to upgrade to e2k next month.   (since we aren't in
native, we can't do a migrations using the adc - right?) can i setup my new exchange server (offline) with w2k and e5.5 and then upgrade to 2000 then take down the production 5.5 and put the new 2k box into production? any gotchas? can i do this? thanks!!



--
Thank you
Jenn Fountain
215.712.5156


List info   : http://www.activedir.org/mail_list.htm
List FAQ    : http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
List info   : http://www.activedir.org/mail_list.htm
List FAQ    : http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
List info   : http://www.activedir.org/mail_list.htm
List FAQ    : http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/

RE: [ActiveDir] Exchange 5.5 upgrade to 2000

[Burns, Clyde]

Jennifer, another thing to think about migrating from Exchange 5.5 to
Exchange 2000. One of the caviats that you are going to run into is
distribution lists in your Windows 2000 mixed mode domain (or lack of). The
ADC creates Universal Security groups in windows 2000 from distributions
lists in Exchange 5.5. These type of groups arent available in w2k
mixed-mode. Which can cause havok on public folders IF you use distribution
lists to give/restrict access to public folders.

<http://support.microsoft.com/default.aspx?scid=kb;en-us;Q316886&sd=tech> is
a good jumping off point to read about this. In your case of not being able
to go native in w2k you may have to setup a temporary native mode child
domain for your distribution lists to live in.

Clyde Burns

-Original Message-
From: Craig Cerino [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 04, 2002 2:19 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Exchange 5.5 upgrade to 2000


Jennifer - you can do what you need right now.

When one of our satellite offices was still in mixed mode they were
running Exchange 5.0 on and NT4.0 box. This box was also a BDC (formerly
the PDC until AD servers were introduced.

I recommend you upgrade your 5.5 box to SP6 (if it's not already there.)
Set up an ADC between the Exchange 5.5 box and one of your AD DC's and
allow replication to begin.

Then when you are ready --- install a separate (preferably new/clean
box) Win 2K Exch 2K server into that exchange site (remembering to run
setup with the /ForestPrep and DomainPrep switches separately) - migrate
your mailboxes over to the 2K box decommission the 5.5 box  and
switch to Exchange Native Mode (which is different than Win2K [AD]
NATIVE MODE).

Then when you are sure you have no remaining NT 4.0 domain controllers
--- switch to Windows 2000 Native Mode.


Craig  



Craig P. Cerino
MCSE, MCP+I
Systems Administrator
TIE SOLUTIONS, Inc
[EMAIL PROTECTED]
www.tiesolutions.com
 


-Original Message-
From: Jennifer Fountain [mailto:[EMAIL PROTECTED]] 
Sent: Friday, October 04, 2002 2:07 PM
To: '[EMAIL PROTECTED]'
Subject: [ActiveDir] Exchange 5.5 upgrade to 2000

We are currently in mixed mode and cannot switch to native.  We
currently
have e5.5 and plan to upgrade to e2k next month.   (since we aren't in
native, we can't do a migrations using the adc - right?) can i setup my
new
exchange server (offline) with w2k and e5.5 and then upgrade to 2000
then
take down the production 5.5 and put the new 2k box into production?
any gotchas? can i do this? thanks!!



--
Thank you
Jenn Fountain
215.712.5156

List info   : http://www.activedir.org/mail_list.htm
List FAQ: http://www.activedir.org/list_faq.htm
List archive:
http://www.mail-archive.com/activedir%40mail.activedir.org/
List info   : http://www.activedir.org/mail_list.htm
List FAQ: http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
List info   : http://www.activedir.org/mail_list.htm
List FAQ: http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/

RE: [ActiveDir] Exchange 5.5 upgrade to 2000

[Salandra, Justin A.]

How do you configure two domains and parent and a child to replicate and
create mailboxes for user accounts in both domains to a 5.5 server in the
parent domain

 -Original Message-
From:   Dave Kinnamon [mailto:[EMAIL PROTECTED]] 
Sent:   Friday, October 04, 2002 2:31 PM
To: '[EMAIL PROTECTED]'
Subject:    RE: [ActiveDir] Exchange 5.5 upgrade to 2000

Exactly, but also ...

Before you setup the ADC(remember to install this from the E2K CD), run the
NTDSNoMAtch utility on your Exch5.5 box.  This utility identifies multiple
NT accounts that have the same mailbox associated with them.  In W2K/E2K,
mailboxes can only have one user/account associated with them.

Once you have you list of problem mailboxes, manally make whatever changes
you want.  Run NTDSNoMAtch until no problems are found.  Now you're ready
for the ADC install.


Dave K.





-Original Message-
From: Jennifer Fountain [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 04, 2002 1:07 PM
To: '[EMAIL PROTECTED]'
Subject: [ActiveDir] Exchange 5.5 upgrade to 2000


We are currently in mixed mode and cannot switch to native.  We currently
have e5.5 and plan to upgrade to e2k next month.   (since we aren't in
native, we can't do a migrations using the adc - right?) can i setup my new
exchange server (offline) with w2k and e5.5 and then upgrade to 2000 then
take down the production 5.5 and put the new 2k box into production?
any gotchas? can i do this? thanks!!



--
Thank you
Jenn Fountain
215.712.5156

List info   : http://www.activedir.org/mail_list.htm
List FAQ: http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
List info   : http://www.activedir.org/mail_list.htm
List FAQ: http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
List info   : http://www.activedir.org/mail_list.htm
List FAQ: http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/

RE: [ActiveDir] Exchange 5.5 upgrade to 2000

[Dave Kinnamon]

Exactly, but also ...

Before you setup the ADC(remember to install this from the E2K CD), run the
NTDSNoMAtch utility on your Exch5.5 box.  This utility identifies multiple
NT accounts that have the same mailbox associated with them.  In W2K/E2K,
mailboxes can only have one user/account associated with them.

Once you have you list of problem mailboxes, manally make whatever changes
you want.  Run NTDSNoMAtch until no problems are found.  Now you're ready
for the ADC install.


Dave K.





-Original Message-
From: Jennifer Fountain [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 04, 2002 1:07 PM
To: '[EMAIL PROTECTED]'
Subject: [ActiveDir] Exchange 5.5 upgrade to 2000


We are currently in mixed mode and cannot switch to native.  We currently
have e5.5 and plan to upgrade to e2k next month.   (since we aren't in
native, we can't do a migrations using the adc - right?) can i setup my new
exchange server (offline) with w2k and e5.5 and then upgrade to 2000 then
take down the production 5.5 and put the new 2k box into production?
any gotchas? can i do this? thanks!!



--
Thank you
Jenn Fountain
215.712.5156

List info   : http://www.activedir.org/mail_list.htm
List FAQ: http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
List info   : http://www.activedir.org/mail_list.htm
List FAQ: http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/

RE: [ActiveDir] Exchange 5.5 upgrade to 2000

[Craig Cerino]

Jennifer - you can do what you need right now.

When one of our satellite offices was still in mixed mode they were
running Exchange 5.0 on and NT4.0 box. This box was also a BDC (formerly
the PDC until AD servers were introduced.

I recommend you upgrade your 5.5 box to SP6 (if it's not already there.)
Set up an ADC between the Exchange 5.5 box and one of your AD DC's and
allow replication to begin.

Then when you are ready --- install a separate (preferably new/clean
box) Win 2K Exch 2K server into that exchange site (remembering to run
setup with the /ForestPrep and DomainPrep switches separately) - migrate
your mailboxes over to the 2K box decommission the 5.5 box  and
switch to Exchange Native Mode (which is different than Win2K [AD]
NATIVE MODE).

Then when you are sure you have no remaining NT 4.0 domain controllers
--- switch to Windows 2000 Native Mode.


Craig  



Craig P. Cerino
MCSE, MCP+I
Systems Administrator
TIE SOLUTIONS, Inc
[EMAIL PROTECTED]
www.tiesolutions.com
 


-Original Message-
From: Jennifer Fountain [mailto:[EMAIL PROTECTED]] 
Sent: Friday, October 04, 2002 2:07 PM
To: '[EMAIL PROTECTED]'
Subject: [ActiveDir] Exchange 5.5 upgrade to 2000

We are currently in mixed mode and cannot switch to native.  We
currently
have e5.5 and plan to upgrade to e2k next month.   (since we aren't in
native, we can't do a migrations using the adc - right?) can i setup my
new
exchange server (offline) with w2k and e5.5 and then upgrade to 2000
then
take down the production 5.5 and put the new 2k box into production?
any gotchas? can i do this? thanks!!



--
Thank you
Jenn Fountain
215.712.5156

List info   : http://www.activedir.org/mail_list.htm
List FAQ: http://www.activedir.org/list_faq.htm
List archive:
http://www.mail-archive.com/activedir%40mail.activedir.org/
List info   : http://www.activedir.org/mail_list.htm
List FAQ: http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/