Re: ConfigDSInteg error
From: Rand Williams [MSFT] (randw_at_online.microsoft.com)
Date: 10/14/04
- Next message: Rand Williams [MSFT]: "Re: Moving Exchange servers"
- Previous message: Rand Williams [MSFT]: "Re: Forestprep"
- In reply to: Manos Anastasiadis: "Re: ConfigDSInteg error"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 14 Oct 2004 17:04:26 -0500
Changing the ADC User Connection Agreement and Public Folder Connection
Agreement to point to the new Exchange 2003 server is so that it will have
an endpoint that goes to the SRS database on the new Exchange 2003 server.
The SRS database is a database on the Exchange 2003 server that emulates an
Exchange 5.5 server directory.
If you do not have other Exchange 5.5 Sites or Admin groups this step is not
necessary. This is too prevent issue such as what you might see in Q291170.
You would not create new connection agreements, but simply change the
Exchange Server you agreements point to. You would also change the port
number from port 389 to port 379, or whatever port you Config_CA agreement
is set to.
When Exchange 2003 is installed into a 5.5 site it detects what port 5.5 is
configured to use for LDAP.
If 5.5 is using the default Port of 389, the SRS will use the default port
of
379.
If 5.5 is configured to use a different port for LDAP, like port 390 for
example, the SRS will
use port 390 as well.
This does not appear to create any issues.
Any ADC connection agreements configured to point to the SRS would need to
use the
SRS port of 390 as well.
NOTE: This means the Config_CA will default to using this port and any ADC
connection agreements that are configured to point to the SRS database, will
need
to be configured to use this port as well.
-- Hope that helps, Rand Williams This posting is provided "AS IS" with no warranties, and confers no rights. Please do not send email to this address, post a reply to this newsgroup. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm "Manos Anastasiadis" <zaffodb@hotmail.com> wrote in message news:O2rYwwHsEHA.392@TK2MSFTNGP14.phx.gbl... > Hi Rand, all, > > Thanks for your rapid answer. > > First of all, the dash only appears on the server name > (ES-0) and not in the organization or site. > > As far as the order of running the tools is concerned, > we simply followed the guidelines of ExDeploy: > First we selected "Deploy the first Exchange 2003 Server" > and then "Coexistence with Exchange 5.5". > We completed Phase 1 & 2 and we're currently in > Phase 3, Step 4. We assigned the "Exchange View Only > Administrator" role to the account under which the ADC > is being run (the same as the original Ex5.5 server's > service account), but we have not yet changed our > "connection agreements to connect to the new server > running Exchange 2003" because I'm not sure > what it actually means. Do we have to change the "Public Folders" > and "Users" CAs created during the ADC configuration > phase and make them connect to the new ES-0 server? > Or should we drop these CAs and create new ones? > Apparently we skipped this part and just tried the validation > tools; during ConfigDSInteg test, we got the error message > I mentioned in my original message. > > However, I am seriously concerned about the process > "path" to be used because, the article > http://support.microsoft.com/default.aspx?kbid=812593 > provides a completely different order of running > the same tools. > > Any comments welcome. > > Manos > > > "Rand Williams [MSFT]" wrote in message ... >> I'm a little confused about the order in which you are running these >> tools >> since integrity check tools prior to installing Exchange 2003 as part of > the >> ExDeploy tools. >> >> The message you are receiving "The object has been identified as a dash >> object." is reported because: >> >> >> We log that fact that the CN has a dash it to bring it to your attention. >> We are >> unable to determine if the dash in the name was intentional or if this >> was > a >> duplicate object created by the ADC, which will append a dash 1 to the >> original >> name. If your Actual Org/Site names contains dashes, no action needs to > be >> taken. >> >> >> -- >> Hope that helps, >> Rand Williams >> >> This posting is provided "AS IS" with no warranties, and confers no > rights. >> Please do not send email to this address, post a reply to this newsgroup. >> >> Use of included script samples are subject to the terms specified at >> http://www.microsoft.com/info/cpyright.htm >> >> >> "Manos Anastasiadis" wrote in message >> > Hi all, >> > >> > We have Exchange 5.5 and are now deploying Exchange 2003. >> > We've used the ExDeploy tool to Exchange 2003 in coexistence >> > with the old 5.5 server. We've completed ForestPrep, DomainPrep, >> > ADC install and setup and finally completed the Exch2003 install. >> > Both ADC and the new Ex2003 run on a WS2003-based >> > server, named "ES-0". SP1 has not been applied yet. >> > We're now running the integrity check tools and we're >> > stuck at the results of the ConfigDSInteg tool. >> > The results of the e2kdsinteg.log file are: >> > >> > --------> Config results from (objectClass=*) ... >> > >> > DN = CN=Config CA_ISC_ES-0,CN=Active Directory Connections,CN=Microsoft >> > Exchange,CN=Services,CN=Configuration,DC=xxx >> > object-class = top$msexchconnectionagreement >> > The object has been identified as a dash object. >> > >> > DN = CN=ES-0,CN=Servers,CN=ISC,CN=Administrative >> > Groups,CN=TUC,CN=Microsoft >> > Exchange,CN=Services,CN=Configuration,DC=xxx >> > object-class = top$server$msexchexchangeserver >> > The object has been identified as a dash object. >> > >> > =================================== >> > >> > Is the name "ES-0" invalid because of the dash? >> > Best Practices Analyzer does not nag about it... >> > Can we ignore this? >> > >> > NOTE: >> > AD is running in 2003-native mode, no WINS server is configured. >> > >> > Thanks in advance >> > >> > Manos >> > >> > >
- Next message: Rand Williams [MSFT]: "Re: Moving Exchange servers"
- Previous message: Rand Williams [MSFT]: "Re: Forestprep"
- In reply to: Manos Anastasiadis: "Re: ConfigDSInteg error"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
