Aaah. I see. What is your site topology like? Do you schedule the DR for
off-hours? If so, you may reduce some of these complaints by restructuring
the DR schedules. For example, if you have a hub-spoke topology you can
schedule the DR so that the hub site requests updates first and after that
the spokes start reading the updates from the hub. That way all updates are
replicated everywhere within a single replication cycle. If it was the
other way around (spokes reading first and then hub reading from the spokes)
the changes from a spoke would take two replication cycles to propagate.
S.
-----Original Message-----
From: John Matteson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 23, 2001 10:50 AM
To: Exchange Discussions
Subject: RE: External verification of Directory Sync.
I would agree that the USN properties would be more appropriate, however,
the programmer has not be able to get to those values via ADSI.
Also, this is a read only type of process. We've had problems in the past,
reported by users, where an account on one side of the organization never
gets updated on the other side of the org, which may be two or three DR hops
away.
John Matteson; Exchange Manager
Geac Corporate Infrastructure Systems and Standards
(404) 239 - 2981
Reduce your stress; Resign as the General Manager of the Universe
-----Original Message-----
From: Soysal, Serdar [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 23, 2001 10:24 AM
To: Exchange Discussions
Subject: RE: External verification of Directory Sync.
It may make more sense to check the USN values for synch verification.
We never tried a project like this but it sounds very very scary to have
someone tinkering with the raw properties of Exchange programmatically.
S.
-----Original Message-----
From: John Matteson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 23, 2001 10:03 AM
To: Exchange Discussions
Subject: External verification of Directory Sync.
Good morning to you all:
I have a person in my group that is trying to program a process that
will run outside of Exchange and access the raw properties of the Exchange
directory to ensure that objects in Site A are in sync with the objects in
Site B.
Current thinking is that he will access the "WHEN CHANGED" property
of each object to ensure that the numbers are the same on each side of the
comparison.
Has anyone ever tried a project like this? Any comments,
suggestions?
John Matteson; Exchange Manager
Geac Corporate Infrastructure Systems and Standards
(404) 239 - 2981
Reduce your stress; Resign as the General Manager of the Universe
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
