T
Tim M
I am working on upgrading our domain from 2k to 2003. We have 3 dc's, 2 in
our home site (HomeDC1, HomeDC1) and 1 in another site (SiteDC1). All hold
the GC. We also have 1 Exchange 2000 server in our home site. I am working on
the 2 dc's in our home site. We use AD integrated DNS on all of our dc's and
they are also DHCP servers. Rather than install 2003 as an OS upgrade I
decided to install a 3rd server with 2003 on it (TempDC). I added DNS and
DHCP to this server. I then went though the adprep process. I then ran
dcpromo on the TempDC. Two days later I tranfered the FSMO role from HomeDC1
to HomeDC2. At this point all FSMO roles were on HomeDC2.This was the
Infrastructure master role. I then demoted HomeDC1. I also diabled the dhcp
scope. After demoting this server I rebuilt it with 2003. I then installed
DNS and DHCP and the ran dcpromo on the rebuilt HomeDC1. After 2 days I moved
all FSMO roles from HomeDC2 to HomeDC1 which was now running 2003.
After this change we started having problems with users loging onto a new
desktop and being able to access Outlook 2000. At 1st we thought it had to do
with a new computer and user account. Then we tried the new user account on
an existing computer, then an existing user on a new system and finally an
exiting user on an existing system, all with the same issues. If the user had
never used outlook on a computer they could not establish a connection to the
Exchange server.
Here is the error returned:
"The name could not be resolved.
Network problems are preventing connection to the Microsoft Exchange Server
computer. If this problem presists contact your administrator."
This error lead me to review my DNS and DHCP settings. I was also able to
ping the exchange server and reviewed the ipconfig on the the different
computers. This all checked out fine.
To make things more confusing, I happened to logon to a computer we are
using to test out Office 2003 deployment and the connection to the Exchange
server worked.
At this point I started to review my upgrade steps and found this KB
atrticle http://support.microsoft.com/default.aspx?scid=kb;en-us;314649 I
then follwed the steps to correct the mangled atributes in the schema for
Exchange 2000. Still the proble presists.
I know the easy solution is to deploy Office 2003, but that's not completly
ready and I want to make sure my AD is clean before moving ahead with the
rest of my upgrade.
I have not touched HomeDC2. Should I move the FSMO roles back ti this
server? or to TempDC? Is there another solution? What am I missing?
our home site (HomeDC1, HomeDC1) and 1 in another site (SiteDC1). All hold
the GC. We also have 1 Exchange 2000 server in our home site. I am working on
the 2 dc's in our home site. We use AD integrated DNS on all of our dc's and
they are also DHCP servers. Rather than install 2003 as an OS upgrade I
decided to install a 3rd server with 2003 on it (TempDC). I added DNS and
DHCP to this server. I then went though the adprep process. I then ran
dcpromo on the TempDC. Two days later I tranfered the FSMO role from HomeDC1
to HomeDC2. At this point all FSMO roles were on HomeDC2.This was the
Infrastructure master role. I then demoted HomeDC1. I also diabled the dhcp
scope. After demoting this server I rebuilt it with 2003. I then installed
DNS and DHCP and the ran dcpromo on the rebuilt HomeDC1. After 2 days I moved
all FSMO roles from HomeDC2 to HomeDC1 which was now running 2003.
After this change we started having problems with users loging onto a new
desktop and being able to access Outlook 2000. At 1st we thought it had to do
with a new computer and user account. Then we tried the new user account on
an existing computer, then an existing user on a new system and finally an
exiting user on an existing system, all with the same issues. If the user had
never used outlook on a computer they could not establish a connection to the
Exchange server.
Here is the error returned:
"The name could not be resolved.
Network problems are preventing connection to the Microsoft Exchange Server
computer. If this problem presists contact your administrator."
This error lead me to review my DNS and DHCP settings. I was also able to
ping the exchange server and reviewed the ipconfig on the the different
computers. This all checked out fine.
To make things more confusing, I happened to logon to a computer we are
using to test out Office 2003 deployment and the connection to the Exchange
server worked.
At this point I started to review my upgrade steps and found this KB
atrticle http://support.microsoft.com/default.aspx?scid=kb;en-us;314649 I
then follwed the steps to correct the mangled atributes in the schema for
Exchange 2000. Still the proble presists.
I know the easy solution is to deploy Office 2003, but that's not completly
ready and I want to make sure my AD is clean before moving ahead with the
rest of my upgrade.
I have not touched HomeDC2. Should I move the FSMO roles back ti this
server? or to TempDC? Is there another solution? What am I missing?