Hi again guys,
I have just run the get-exchangeserver | fl command and the entries that
Michael mentioned are all null or empty curly brackets, as below:
StaticDomainControllers : {}
StaticGlobalCatalogs : {}
StaticConfigDomainController :
StaticExcludedDomainControllers : {}
CurrentDomainControllers : {}
CurrentGlobalCatalogs : {}
CurrentConfigDomainController :
There is another entry, "OriginatingServer", which has the value of the name
of my old DC.
Is it possible for me to manipulate these values to force Exchange to use my
new DC, do you think? Or again, this is probably asking for trouble later
on..?
Thanks again for everyone's help.
Kind regards,
Andrew
2009/10/13 Andrew Levicki <and...@levicki.me.uk>
> Michael and Rob, thanks for your help. I will have to check tomorrow
> now, as it's late here. I will look into this and if this is not the
> fix, I hope it's OK to bring this subject up again tomorrow. Again,
> all, many thanks.
>
> Andrew.
>
> On 13/10/2009, Michael B. Smith <mich...@owa.smithcons.com> wrote:
> > Seems likely.
> >
> > get-exchangeserver | fl
> >
> > The relevant fields are:
> >
> > StaticDomainControllers : {}
> > StaticGlobalCatalogs : {}
> > StaticConfigDomainController :
> > StaticExcludedDomainControllers : {}
> > CurrentDomainControllers : {}
> > CurrentGlobalCatalogs : {}
> > CurrentConfigDomainController :
> >
> > ________________________________
> > From: Campbell, Rob [rob_campb...@centraltechnology.net]
> > Sent: Tuesday, October 13, 2009 4:24 PM
> > To: MS-Exchange Admin Issues
> > Subject: RE: Exchange 2007 servers listed in System Settings \ Active
> > Directory servers
> >
> > Any chance the DCs were hard coded into the Exchange Server’s registry?
> >
> > From: Andrew Levicki [mailto:and...@levicki.me.uk]
> > Sent: Tuesday, October 13, 2009 2:54 PM
> > To: MS-Exchange Admin Issues
> > Subject: Re: Exchange 2007 servers listed in System Settings \ Active
> > Directory servers
> >
> > Thanks guys, again good questions and info I should have thought to
> provide!
> >
> > DNS on the Exchange server is pointing to the new DC as primary and old
> DC
> > as secondary. And I did try pointing to only the new DC to no avail.
> >
> > And yes, the new server is a GC. As is the old one, but I have also tried
> > making the old DC not a GC.
> >
> > Remembering it is a single domain environment, there is no problem having
> > the Infrastructure Master also being a GC.
> >
> > Thanks for the help guys.
> >
> > Andrew
> > 2009/10/13 Campbell, Rob
> > <rob_campb...@centraltechnology.net<mailto:
> rob_campb...@centraltechnology.net>>
> > And you did make the new DC a GC?
> >
> > From: Andrew Levicki
> > [mailto:and...@levicki.me.uk<mailto:and...@levicki.me.uk>]
> > Sent: Tuesday, October 13, 2009 2:37 PM
> >
> > To: MS-Exchange Admin Issues
> > Subject: Re: Exchange 2007 servers listed in System Settings \ Active
> > Directory servers
> >
> > Ah yes, good question, I tried to put all the info in, but I didn't
> mention
> > sites.
> >
> > It's a single site environment, so yes, old DC, new DC and Exchange
> server
> > are all in the same site.
> >
> > DCs are in the default OU and the Exchange Server is in a "Servers" OU.
> >
> > Thanks Rob :)
> > 2009/10/13 Campbell, Rob
> > <rob_campb...@centraltechnology.net<mailto:
> rob_campb...@centraltechnology.net>>
> > Is the new DC in the same site as your old DC, and the Exchange servers?
> >
> > From: Andrew Levicki
> > [mailto:and...@levicki.me.uk<mailto:and...@levicki.me.uk>]
> > Sent: Tuesday, October 13, 2009 2:31 PM
> > To: MS-Exchange Admin Issues
> > Subject: Re: Exchange 2007 servers listed in System Settings \ Active
> > Directory servers
> >
> > I'm really sorry if that email just went off the sides of your screen. I
> > hope that (a) you
> > know the answer to my question and (b) you will read my message now (damn
> > computers!):
> >
> > Hi all, I wonder if any of you have encountered this problem and can
> advise
> > my best course of action:
> >
> > I have an Exchange 2007 Standard Edition server in a single domain
> > environment, running on Windows Server 2003 R2 x64. There was a Windows
> > Server 2003 domain controller with all the FSMO roles and was a Global
> > Catalog server, which I was hoping to decommission.
> >
> > So I dcpromo'd and transferred the FSMO roles to a new domain controller
> and
> > I am happy that all the replication has occurred and the new DC is fully
> > functional according to all Microsoft's tests.
> > (http://support.microsoft.com/kb/816106)
> >
> > However, on my Exchange server, the old domain controller is still listed
> in
> > the following places:
> > Microsoft Exchange \ Server Configuration \ Server Properties \ "System
> > Settings" tab \ Active Directory servers \ "Domain controller servers
> being
> > used by Exchange" & "Global catalog servers being used by Exchange".
> >
> > So I shut down the old DC and almost immediately Exchange stopped working
> > (mailboxes unavailable, no OWA, no services, nothing). As soon as I
> brought
> > the old DC back up, Exchange worked again.
> >
> > The next step was to shut down the old DC, then restart the Exchange
> > services, but they failed to start. I tried a reboot of the whole server,
> > which then hung on "Applying computer settings". As soon as I brought the
> > old DC back online and then rebooted the Exchange server, everything was
> > fine.
> >
> > As you know, the "Domain controller servers being used by Exchange" &
> > "Global catalog servers being used by Exchange" settings in the above
> > location are not configurable.
> >
> > My question is this: how can I make my Exchange server move on into the
> > brave future with me and the new Domain controller? I really do need to
> > decommission the old one.
> >
> > All help gratefully received.
> >
> > Many thanks and kind regards,
> >
> > Andrew Levicki
> >
> >
> >
> > 2009/10/13 Andrew Levicki
> > <and...@levicki.me.uk<mailto:and...@levicki.me.uk>>
> > Hi all, I wonder if any of you have encountered this problem and can
> advise
> > my best course of action:
> >
> > I have an Exchange 2007 Standard Edition server in a single domain
> > environment, running on Windows Server 2003 R2 x64. There was a Windows
> > Server 2003 domain controller with all the FSMO roles and was a Global
> > Catalog server, which I was hoping to decommission.
> >
> > So I dcpromo'd and transferred the FSMO roles to a new domain controller
> and
> > I am happy that all the replication has occurred and the new DC is fully
> > functional according to all Microsoft's tests.
> > (http://support.microsoft.com/kb/816106)
> >
> > However, on my Exchange server, the old domain controller is still listed
> in
> > the following places:
> > Microsoft Exchange \ Server Configuration \ Server Properties \ "System
> > Settings" tab \ Active Directory servers \ "Domain controller servers
> being
> > used by Exchange" & "Global catalog servers being used by Exchange".
> >
> > So I shut down the old DC and almost immediately Exchange stopped working
> > (mailboxes unavailable, no OWA, no services, nothing). As soon as I
> brought
> > the old DC back up, Exchange worked again.
> >
> > The next step was to shut down the old DC, then restart the Exchange
> > services, but they failed to start. I tried a reboot of the whole server,
> > which then hung on "Applying computer settings". As soon as I brought the
> > old DC back online and then rebooted the Exchange server, everything was
> > fine.
> >
> > As you know, the "Domain controller servers being used by Exchange" &
> > "Global catalog servers being used by Exchange" settings in the above
> > location are not configurable.
> >
> > My question is this: how can I make my Exchange server move on into the
> > brave future with me and the new Domain controller? I really do need to
> > decommission the old one.
> >
> > All help gratefully received.
> >
> > Many thanks and kind regards,
> >
> > Andrew Levicki
> >
> >
> >
> **************************************************************************************************
> >
> > Note:
> >
> > The information contained in this message may be privileged and
> confidential
> > and
> >
> >
> >
> > protected from disclosure. If the reader of this message is not the
> > intended
> >
> > recipient, or an employee or agent responsible for delivering this
> message
> > to
> >
> > the intended recipient, you are hereby notified that any dissemination,
> >
> > distribution or copying of this communication is strictly prohibited. If
> you
> >
> > have received this communication in error, please notify us immediately
> by
> >
> > replying to the message and deleting it from your computer.
> >
> >
> **************************************************************************************************
> >
> >
> >
> **************************************************************************************************
> >
> > Note:
> >
> > The information contained in this message may be privileged and
> confidential
> > and
> >
> > protected from disclosure. If the reader of this message is not the
> > intended
> >
> > recipient, or an employee or agent responsible for delivering this
> message
> > to
> >
> > the intended recipient, you are hereby notified that any dissemination,
> >
> > distribution or copying of this communication is strictly prohibited. If
> you
> >
> > have received this communication in error, please notify us immediately
> by
> >
> > replying to the message and deleting it from your computer.
> >
> >
> **************************************************************************************************
> >
> >
> >
> **************************************************************************************************
> > Note:
> > The information contained in this message may be privileged and
> confidential
> > and
> > protected from disclosure. If the reader of this message is not the
> > intended
> > recipient, or an employee or agent responsible for delivering this
> message
> > to
> > the intended recipient, you are hereby notified that any dissemination,
> > distribution or copying of this communication is strictly prohibited. If
> you
> > have received this communication in error, please notify us immediately
> by
> > replying to the message and deleting it from your computer.
> >
> **************************************************************************************************
> >
> >
>
> --
> Sent from my mobile device
>
>
>
