|
|
My company just bought a second server, because our first one is dying. Both
are running Server 2003 Enterprise. I got the new server up and running,
joined it to the domain and made it a domain controller and a global catalog
server. I waited a few hours for all the settings and everything to
propegate over to the new server (we only have 15 users). I then migrated
the Exchange information from 2003 on the old server to 2007 on the new
server and everything seemed to be working just fine.
I went into active directory and used the operations master to transfer RID,
PDC, and Infrastructure to the new server. Everything seemed to work, so
then I transfered all the data and shut down the old server.
However, when I shut down the old server Exchange kept giving me errors
saying it could not find the domain controller. I messed around with it for
a while, but all the computers were giving me errors about being unable to
find the domain.
I powered back the old server and transfered operations manager back to it
and now people are able to log in, but exchange is not functioning on either
server saying it can't find the domain controller. I am out of ideas on what
to troubleshoot and try now. I am just trying to get everything back to an
operational status.
|
|
Hello CPickler,
Is the new server also DNS server?
What about schema master and infrastructure master role, are they also moved?
What DNS server is configured on the new DC and the client machines, changed
to the new DNS?
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
[Quoted Text] > My company just bought a second server, because our first one is
> dying. Both are running Server 2003 Enterprise. I got the new server
> up and running, joined it to the domain and made it a domain
> controller and a global catalog server. I waited a few hours for all
> the settings and everything to propegate over to the new server (we
> only have 15 users). I then migrated the Exchange information from
> 2003 on the old server to 2007 on the new server and everything seemed
> to be working just fine.
>
> I went into active directory and used the operations master to
> transfer RID, PDC, and Infrastructure to the new server. Everything
> seemed to work, so then I transfered all the data and shut down the
> old server.
>
> However, when I shut down the old server Exchange kept giving me
> errors saying it could not find the domain controller. I messed
> around with it for a while, but all the computers were giving me
> errors about being unable to find the domain.
>
> I powered back the old server and transfered operations manager back
> to it and now people are able to log in, but exchange is not
> functioning on either server saying it can't find the domain
> controller. I am out of ideas on what to troubleshoot and try now. I
> am just trying to get everything back to an operational status.
>
|
|
You didn't mention DNS. Did you move DNS to the new server and point your
Exchange and you clients to the new server?
hth
DDS
"CPickler" <CPickler[ at ]discussions.microsoft.com> wrote in message
news:8C998C6C-1AB5-428E-974F-FA4584F98EE4[ at ]microsoft.com...
[Quoted Text] > My company just bought a second server, because our first one is dying.
> Both
> are running Server 2003 Enterprise. I got the new server up and running,
> joined it to the domain and made it a domain controller and a global
> catalog
> server. I waited a few hours for all the settings and everything to
> propegate over to the new server (we only have 15 users). I then migrated
> the Exchange information from 2003 on the old server to 2007 on the new
> server and everything seemed to be working just fine.
>
> I went into active directory and used the operations master to transfer
> RID,
> PDC, and Infrastructure to the new server. Everything seemed to work, so
> then I transfered all the data and shut down the old server.
>
> However, when I shut down the old server Exchange kept giving me errors
> saying it could not find the domain controller. I messed around with it
> for
> a while, but all the computers were giving me errors about being unable to
> find the domain.
>
> I powered back the old server and transfered operations manager back to it
> and now people are able to log in, but exchange is not functioning on
> either
> server saying it can't find the domain controller. I am out of ideas on
> what
> to troubleshoot and try now. I am just trying to get everything back to
> an
> operational status.
|
|
Hello CPickler,
Typo:
What about schema master and domain naming master role, are they also moved?
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
[Quoted Text] > My company just bought a second server, because our first one is
> dying. Both are running Server 2003 Enterprise. I got the new server
> up and running, joined it to the domain and made it a domain
> controller and a global catalog server. I waited a few hours for all
> the settings and everything to propegate over to the new server (we
> only have 15 users). I then migrated the Exchange information from
> 2003 on the old server to 2007 on the new server and everything seemed
> to be working just fine.
>
> I went into active directory and used the operations master to
> transfer RID, PDC, and Infrastructure to the new server. Everything
> seemed to work, so then I transfered all the data and shut down the
> old server.
>
> However, when I shut down the old server Exchange kept giving me
> errors saying it could not find the domain controller. I messed
> around with it for a while, but all the computers were giving me
> errors about being unable to find the domain.
>
> I powered back the old server and transfered operations manager back
> to it and now people are able to log in, but exchange is not
> functioning on either server saying it can't find the domain
> controller. I am out of ideas on what to troubleshoot and try now. I
> am just trying to get everything back to an operational status.
>
|
|
Yes the new server is also a DNS server.
No, I do not think schema master and infrastructure master got moved. The
only infrastructure I moved was in active directory, operations master for
PDC, RIP and the infrastructure in that option. How do I move schema master?
DNS entries on the end computers were still pointing to the old server, but
I was going to change that but when the errors started happening between the
servers, I didn't think that would affect the servers.
|
|
domain naming master role was not moved.
I am trying to make it a one server set-up again, so what all needs to be
migrated to this new server?
|
|
"CPickler" <CPickler[ at ]discussions.microsoft.com> wrote in message
news:8C998C6C-1AB5-428E-974F-FA4584F98EE4[ at ]microsoft.com...
[Quoted Text] > My company just bought a second server, because our first one is dying.
> Both
> are running Server 2003 Enterprise. I got the new server up and running,
> joined it to the domain and made it a domain controller and a global
> catalog
> server. I waited a few hours for all the settings and everything to
> propegate over to the new server (we only have 15 users). I then migrated
> the Exchange information from 2003 on the old server to 2007 on the new
> server and everything seemed to be working just fine.
>
> I went into active directory and used the operations master to transfer
> RID,
> PDC, and Infrastructure to the new server. Everything seemed to work, so
> then I transfered all the data and shut down the old server.
>
> However, when I shut down the old server Exchange kept giving me errors
> saying it could not find the domain controller. I messed around with it
> for
> a while, but all the computers were giving me errors about being unable to
> find the domain.
>
> I powered back the old server and transfered operations manager back to it
> and now people are able to log in, but exchange is not functioning on
> either
> server saying it can't find the domain controller. I am out of ideas on
> what
> to troubleshoot and try now. I am just trying to get everything back to
> an
> operational status.
1. You can't just simply shut down the server. Because:
A. It appears to be a Domain Controller
B. It apears to also be an Exchange Server at the same time.
2. You can remove an old Exchange server from a LAN by just shuting it down.
So I am assuming that the old server is both a DC and an Exchange,...and the
new server is also a DC and an Exchange Server. I am also assuming that DNS
is installed and working correctly on the new Server/DC
....Then...
You have to:
1. Make sure the new server is a properly functioning DC and has a properly
function Exchange Server in the same "Exchange Site" with the previous
Exchange Server.
2. Use the Exchange functionality of "moving" a mail box from one Exchange
to the other untill all mailboxes are moved.
3. While the old Server is still intact and still a DC.follow the process of
removing the "First" Exchange Server from an Exchange Site.
How to remove the first Exchange Server 2003 computer from the
administrative group
http://support.microsoft.com/kb/822931
4. Once all that is completed and verified to be working correctly without
errors,...you can run DCPromo on the old server to demote it to a member
server,..then to a workgroup,...then remove it all together. The FSMO Roles
should transfer *Automatically* during the DCPromo process. The Global
Catalog setting is manual and you will need to do that one yourself.
5. Make sure all Clients now point to the new server for DNS, WINS, etc., or
you can possibly add or change the IP of the server to be what you want.
--
Phillip Windell
www.wandtv.com
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
|
|
"Phillip Windell" <philwindell[ at ]hotmail.com> wrote in message
news:eOGyCHfaJHA.6036[ at ]TK2MSFTNGP05.phx.gbl...
[Quoted Text] > 2. You can remove an old Exchange server from a LAN by just shuting it
> down.
Meant to say "...can NOT remove and old Exchange..."
I hate typos like that,...when they make you say the opposite of what you
meant. :-)
--
Phillip Windell
www.wandtv.com
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
|
|
Hi
-You cannot just shutdown the old server (DC and exchange) an expect that
everything works perfectly... there're other things to do... Like making
sure that you have a GC available, DNS... The exchange also needs some work
and checking before going any further... If you use the normal tools to
remove the exchange and DC the work should be less complicated, if you want
to do it manually then make sure that you know what you're doing before
proceed.
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.
"CPickler" <CPickler[ at ]discussions.microsoft.com> wrote in message
news:8C998C6C-1AB5-428E-974F-FA4584F98EE4[ at ]microsoft.com...
[Quoted Text] > My company just bought a second server, because our first one is dying.
> Both
> are running Server 2003 Enterprise. I got the new server up and running,
> joined it to the domain and made it a domain controller and a global
> catalog
> server. I waited a few hours for all the settings and everything to
> propegate over to the new server (we only have 15 users). I then migrated
> the Exchange information from 2003 on the old server to 2007 on the new
> server and everything seemed to be working just fine.
>
> I went into active directory and used the operations master to transfer
> RID,
> PDC, and Infrastructure to the new server. Everything seemed to work, so
> then I transfered all the data and shut down the old server.
>
> However, when I shut down the old server Exchange kept giving me errors
> saying it could not find the domain controller. I messed around with it
> for
> a while, but all the computers were giving me errors about being unable to
> find the domain.
>
> I powered back the old server and transfered operations manager back to it
> and now people are able to log in, but exchange is not functioning on
> either
> server saying it can't find the domain controller. I am out of ideas on
> what
> to troubleshoot and try now. I am just trying to get everything back to
> an
> operational status.
|
|
|