Left over migration issue??
knucklebuck
on our Windows 2000 domain.
Installed the ADC, moved mailboxes...everything worked out fine,
retired the old server, properly removed from site, etc etc etc.
Anyway, I'm now in the process of migrating services off of my main
domain controller to retire it. I've brought up another DC, transferred
roles to it, started DHCP, got DNS going, pointed Exchange to it.
Everything is going just fine.
However, when I bring up AD Sites & Services, there is an Exchange
folder next to the NTDS settings under my main DC to be retired.
Highlight it on the left and there is nothing on the right hand pane.
If you Right Click and bring up Properties, under the object tab is
this: my.domain.com/Configuration/Sites/Site1/Servers/DC1/Exchange
Settings
DC1 is where ADC was installed...does this folder have anything to do
with it?
Matthew Byrd [MSFT]
That is the remnant of the ADC. Assuming you have flipped over into
Exchange Native mode (or really even as long as you don't have any 5.5
servers any more) then you don't need to worry about this at all. Just go
thru the process of decommissioning the Domain controller liked you plan
there should be no problems due to this object.
Hope this helps,
--
Matthew Byrd
Microsoft PSS
Run Microsoft Exchange Server Best Practices Analyzer Today
http://www.microsoft.com/exchange/downloads/2003/exbpa/default.mspx
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
"knucklebuck" <knuck...@street-troller.com> wrote in message
news:1115603013....@z14g2000cwz.googlegroups.com...
knucklebuck
I demoted my old former PDC and it was still left in AD Sites &
Services, but only with the Exchange folder underneath...no NTDS
settings item. I just deleted the server.
Exchange "seems" to be working fine, but anytime a domain controller
gets rebooted, my Exchange server will log an error saying the former
PDC is not reachable:
Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8260
Date: 5/15/2005
Time: 12:53:28 AM
User: N/A
Computer: Exc-svr
Description:
Could not open LDAP session to directory 'oldpdc.mydomain.com' using
local service credentials. Cannot access Address List configuration
information. Make sure the server 'oldpdc.mydomain.com' is running.
For more information, click
http://www.microsoft.com/contentredirect.asp.
Now, I have another site over a VPN and I manually had to remove a
bunch of DNS entries referring to the old server in order to get my
site links to update themselves to the new PDC. The only thing
referring to the old server is just the computer account in AD...a
member server. This old PDC is completely off-line and Exchange and
clients seem to work fine.
Any idea why Exchange logs this error?
Thanks again!
knucklebuck
following event info:
Event Type: Information
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2081
Date: 5/15/2005
Time: 12:03:50 AM
User: N/A
Computer: Exc-svr
Description:
Process MAD.EXE (PID=1712). DSAccess will use the servers from the
following list:
Domain Controllers:
DC2.mydomain.com
newPDC.mydomain.com
Global Catalogs:
DC2.mydomain.com
newPDC.mydomain.com
The Configuration Domain Controller is set to DC2.mydomain.com.
For more information, click
http://www.microsoft.com/contentredirect.asp.
So the topology was updated, but that error was still logged when
DC2.mydomain.com was just rebooted
Matthew Byrd [MSFT]
You are probably getting this error because your Recipient Update Service is
pointed to the old domain controller. Simply go into the ESM can point the
RUS at a current valid domain controller and this issue should go away.
Hope this Help,
--
Matthew Byrd
Microsoft PSS
Run Microsoft Exchange Server Best Practices Analyzer Today
http://www.microsoft.com/exchange/downloads/2003/exbpa/default.mspx
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
"knucklebuck" <knuck...@street-troller.com> wrote in message
news:1116138559.5...@g44g2000cwa.googlegroups.com...
Matthew Byrd [MSFT]
This is expected. This is the DSAccess process detecting that the old
server doesn't exist and is detecting a new server.
Hope this Help,
--
Matthew Byrd
Microsoft PSS
Run Microsoft Exchange Server Best Practices Analyzer Today
http://www.microsoft.com/exchange/downloads/2003/exbpa/default.mspx
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
"knucklebuck" <knuck...@street-troller.com> wrote in message
news:1116138759.9...@g49g2000cwa.googlegroups.com...
knucklebuck
I do have 2 Recipient Update Services...one called Enterprise
Configuration and the other called the same as my Organization name.
This was a migration from Exchange 5.5
Which one is safe to delete? I've pointed both of them to my new PDC
and they're both set to Always run.
Matthew Byrd [MSFT]
You need both of them they server different purposes. The Enterprise RUS is
responsible for system objects and the domain RUS is responsible for users.
Hope this helps,
--
Matthew Byrd
Microsoft PSS
Run Microsoft Exchange Server Best Practices Analyzer Today
http://www.microsoft.com/exchange/downloads/2003/exbpa/default.mspx
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
"knucklebuck" <knuck...@street-troller.com> wrote in message
news:1116300466.1...@o13g2000cwo.googlegroups.com...