DC tryis to replicate with deleted old DC - replmon.jpg (0/1)

A

Alex Litvin

Hello!

I have demoted an old DC server and create a new one
so the network have 2 DCs , replication between them is ok
but they both try to replicate with old deleted DC
see the enclosed picture
ntdsutil and GUI tools did not show me this old server
how to remove these replication link?

thanx
 
A

Alex Litvin

Hello!

I have demoted an old DC server and create a new one
so the network have 2 DCs , replication between them is ok
but they both try to replicate with old deleted DC
see the enclosed picture
ntdsutil and GUI tools did not show me this old server
how to remove these replication link?
something wron with gif attachment - so here is the log

Active Directory Replication Monitor
Printed on 19.08.2004 14:52:41
This report was generated on data from the server: KRAKEN

***************************************************************************
KRAKEN Data
***************************************************************************

This server currently has writable copies of the following directory
partitions:
---------------------------------------------------------------------------
DC=test,DC=domain,DC=com
CN=Configuration,DC=test,DC=domain,DC=com
CN=Schema,CN=Configuration,DC=test,DC=domain,DC=com
DC=DomainDnsZones,DC=test,DC=domain,DC=com
DC=ForestDnsZones,DC=test,DC=domain,DC=com

Because this server is a Global Catalog (GC) server, it also has
copies
of the following directory partitions:
---------------------------------------------------------------------------

Current NTDS Connection Objects
-------------------------------
site1\WEBBI
Connection Name : 84ae9d97-2702-4183-b1b1-c7a200762556
Administrator Generated?: AUTO
Reasons for this connection:
Directory Partition
(CN=Configuration,DC=test,DC=domain,DC=com)
Replicated because the replication partner is a
ring neighbor.

Directory Partition
(CN=Schema,CN=Configuration,DC=test,DC=domain,DC=com)
Replicated because the replication partner is a
ring neighbor.

Directory Partition (DC=test,DC=domain,DC=com)
Replicated because the replication partner is a
ring neighbor.


Current Direct Replication Partner Status
-----------------------------------------

Directory Partition: DC=test,DC=domain,DC=com

Partner Name: **DELETED SERVER #1
Partner GUID: 9C6214B0-289E-4018-986D-2067AAFB1774
Last Attempted Replication: 8/19/2004 2:52:04 PM
(local)
Last Successful Replication: 8/12/2004 6:04:00 PM
(local)
Number of Failures: 166
Failure Reason Error Code: 8524
Failure Description: The DSA operation is unable to
proceed because of a DNS lookup failure.
Synchronization Flags:
DRS_WRIT_REP,DRS_INIT_SYNC,DRS_PER_SYNC
USN of Last Property Updated: 549569
USN of Last Object Updated: 549569
Transport:

Partner Name: site1\WEBBI
Partner GUID: 99C14F97-3477-4C5C-B4A2-C60428B52D2F
Last Attempted Replication: 8/19/2004 2:52:04 PM
(local)
Last Successful Replication: 8/19/2004 2:52:04 PM
(local)
Number of Failures: 0
Failure Reason Error Code: 0
Failure Description: The operation completed
successfully.
Synchronization Flags:
DRS_WRIT_REP,DRS_INIT_SYNC,DRS_PER_SYNC
USN of Last Property Updated: 587837
USN of Last Object Updated: 587837
Transport: Intra-Site RPC

Change Notifications for this Directory Partition
-------------------------------------------------
Server Name: site1\WEBBI
Object GUID: 043E43AA-A3F0-4F8A-807C-AD51654CC503
Time Added: 19.08.2004 14:46:49
Flags: DRS_WRIT_REP
Transport: RPC

Directory Partition: CN=Configuration,DC=test,DC=domain,DC=com

Partner Name: **DELETED SERVER #1
Partner GUID: 9C6214B0-289E-4018-986D-2067AAFB1774
Last Attempted Replication: 8/19/2004 2:52:04 PM
(local)
Last Successful Replication: 8/12/2004 6:06:05 PM
(local)
Number of Failures: 166
Failure Reason Error Code: 8524
Failure Description: The DSA operation is unable to
proceed because of a DNS lookup failure.
Synchronization Flags:
DRS_WRIT_REP,DRS_INIT_SYNC,DRS_PER_SYNC
USN of Last Property Updated: 549605
USN of Last Object Updated: 549605
Transport:

Partner Name: site1\WEBBI
Partner GUID: 99C14F97-3477-4C5C-B4A2-C60428B52D2F
Last Attempted Replication: 8/19/2004 2:52:04 PM
(local)
Last Successful Replication: 8/19/2004 2:52:04 PM
(local)
Number of Failures: 0
Failure Reason Error Code: 0
Failure Description: The operation completed
successfully.
Synchronization Flags:
DRS_WRIT_REP,DRS_INIT_SYNC,DRS_PER_SYNC
USN of Last Property Updated: 587820
USN of Last Object Updated: 587820
Transport: Intra-Site RPC

Change Notifications for this Directory Partition
-------------------------------------------------
Server Name: site1\WEBBI
Object GUID: 043E43AA-A3F0-4F8A-807C-AD51654CC503
Time Added: 19.08.2004 14:12:19
Flags: DRS_WRIT_REP
Transport: RPC

Directory Partition:
CN=Schema,CN=Configuration,DC=test,DC=domain,DC=com

Partner Name: **DELETED SERVER #1
Partner GUID: 9C6214B0-289E-4018-986D-2067AAFB1774
Last Attempted Replication: 8/19/2004 2:52:04 PM
(local)
Last Successful Replication: 8/12/2004 6:04:00 PM
(local)
Number of Failures: 166
Failure Reason Error Code: 8524
Failure Description: The DSA operation is unable to
proceed because of a DNS lookup failure.
Synchronization Flags:
DRS_WRIT_REP,DRS_INIT_SYNC,DRS_PER_SYNC
USN of Last Property Updated: 549562
USN of Last Object Updated: 549562
Transport:

Partner Name: site1\WEBBI
Partner GUID: 99C14F97-3477-4C5C-B4A2-C60428B52D2F
Last Attempted Replication: 8/19/2004 2:52:04 PM
(local)
Last Successful Replication: 8/19/2004 2:52:04 PM
(local)
Number of Failures: 0
Failure Reason Error Code: 0
Failure Description: The operation completed
successfully.
Synchronization Flags:
DRS_WRIT_REP,DRS_INIT_SYNC,DRS_PER_SYNC
USN of Last Property Updated: 587705
USN of Last Object Updated: 587705
Transport: Intra-Site RPC

Change Notifications for this Directory Partition
-------------------------------------------------
Server Name: site1\WEBBI
Object GUID: 043E43AA-A3F0-4F8A-807C-AD51654CC503
Time Added: 13.08.2004 12:23:06
Flags: DRS_WRIT_REP
Transport: RPC

Directory Partition: DC=DomainDnsZones,DC=test,DC=domain,DC=com

Directory Partition: DC=ForestDnsZones,DC=test,DC=domain,DC=com

Current Transitive Replication Partner Status
---------------------------------------------

Directory Partition: DC=test,DC=domain,DC=com

Partner Name: site1\KRAKEN
Partner GUID: 5C548DDB-8E91-47FC-AC71-D80E154FFAF3
USN: 85866

Partner Name: site1\WEBBI
Partner GUID: 99C14F97-3477-4C5C-B4A2-C60428B52D2F
USN: 587837

Partner Name: **DELETED SERVER #1
Partner GUID: 9C6214B0-289E-4018-986D-2067AAFB1774
USN: 549605

Directory Partition: CN=Configuration,DC=test,DC=domain,DC=com

Partner Name: site1\KRAKEN
Partner GUID: 5C548DDB-8E91-47FC-AC71-D80E154FFAF3
USN: 85866

Partner Name: site1\WEBBI
Partner GUID: 99C14F97-3477-4C5C-B4A2-C60428B52D2F
USN: 587837

Partner Name: **DELETED SERVER #1
Partner GUID: 9C6214B0-289E-4018-986D-2067AAFB1774
USN: 549605

Directory Partition:
CN=Schema,CN=Configuration,DC=test,DC=domain,DC=com

Partner Name: site1\KRAKEN
Partner GUID: 5C548DDB-8E91-47FC-AC71-D80E154FFAF3
USN: 85866

Partner Name: site1\WEBBI
Partner GUID: 99C14F97-3477-4C5C-B4A2-C60428B52D2F
USN: 587837

Partner Name: **DELETED SERVER #1
Partner GUID: 9C6214B0-289E-4018-986D-2067AAFB1774
USN: 549605

Directory Partition: DC=DomainDnsZones,DC=test,DC=domain,DC=com

Partner Name: site1\KRAKEN
Partner GUID: 5C548DDB-8E91-47FC-AC71-D80E154FFAF3
USN: 85866

Directory Partition: DC=ForestDnsZones,DC=test,DC=domain,DC=com

Partner Name: site1\KRAKEN
Partner GUID: 5C548DDB-8E91-47FC-AC71-D80E154FFAF3
USN: 85866

Current Group Policy Object Status
----------------------------------
Default Domain Policy
Group Policy Object GUID:
{31B2F340-016D-11D2-945F-00C04FB984F9}
Group Policy Object Version in the DS: 589927
Group Policy Object Version in SYSVOL: 589927

Default Domain Controllers Policy
Group Policy Object GUID:
{6AC1786C-016F-11D2-945F-00C04fB984F9}
Group Policy Object Version in the DS: 45
Group Policy Object Version in SYSVOL: 45

IVC Group Policy
Group Policy Object GUID:
{C5E438C4-4691-46C6-9CC2-4C2EDA725B52}
Group Policy Object Version in the DS: 4784170
Group Policy Object Version in SYSVOL: 4784170

IVC Admins Policy
Group Policy Object GUID:
{D427A4E8-65FA-43E4-A14C-C6EF7663E65F}
Group Policy Object Version in the DS: 1376256
Group Policy Object Version in SYSVOL: 1376256


The server KRAKEN knows about the following FSMO roles:
--------------------------------------------------------------------------
Schema FSMO: site1\KRAKEN
Domain Naming FSMO: site1\KRAKEN
Infrastructure FSMO: site1\KRAKEN
Primary Domain Controller FSMO: site1\KRAKEN
RID Pool FSMO: site1\KRAKEN

Performance Statistics at Time of Report
----------------------------------------

Configuration (Registry)
NOTE: an empty value indicates that Windows 2000 will use the internal
default
NOTE: all empty values may indicate insufficient permission to
retrieve this information from the domain controller
------------------------

DSA
---

Days per Database Phantom Scan:
Initialize MAPI interface:
Enforce LIST_OBJECTS rights:
DSA Heuristics:
Max Threads (ExDS+NSP+DRA):
DSA Database file: C:\WINDOWS\NTDS\ntds.dit
DSA Working Directory: C:\WINDOWS\NTDS
Critical Object Installation:
DS Drive Mappings:
DSA Previous Restore Count:

REPLICATION
-----------

Replicator notify pause after modify (secs):
Replicator notify pause between DSAs (secs):
Replicator intra site packet size (objects):
Replicator intra site packet size (bytes):
Replicator inter site packet size (objects):
Replicator inter site packet size (bytes):
Replicator maximum concurrent read threads:
Replicator operation backlog limit:
Replicator thread op priority threshold:
Replicator intra site RPC handle lifetime (secs):
Replicator inter site RPC handle lifetime (secs):
Replicator RPC handle expiry check interval (secs):

LDAP
----

Max objects in LDAP Search (Admin Limit):
Max concurrent LDAP connections allowed:
Max time allowed for an LDAP Search:
Max concurrent LDAP searches allowed:
Max concurrent threads per LDAP connection allowed:
Minimum idle seconds before potential \ timeout of LDAP
connection (non-authenticated client):
Minimum idle seconds before potential \ timeout of LDAP
connection (authenticated client):

Database
--------

Database backup path: C:\WINDOWS\NTDS\dsadata.bak
Database backup interval (hours):
Database log files path: C:\WINDOWS\NTDS
Database logging/recovery: ON
Hierarchy Table Recalculation interval (minutes): 720
Database restored from backup:
Pending object ownership conversions:
EDB max buffers:
EDB max log buffers:
EDB log buffer flush threshold:
EDB buffer flush start:
EDB buffer flush stop:
EDB max ver pages (increment over the minimum:
Circular Logging:
Server Functionality:
TCP/IP Port:
Restore from disk backup:
Performance Counter Version: 17

KCC
---

Repl topology update delay (secs):
Repl topology update period (secs):
KCC site generator fail-over (minutes):
KCC site generator renewal interval (minutes):
KCC site generator renewal interval (minutes):
CriticalLinkFailuresAllowed:
MaxFailureTimeForCriticalLink (sec):
NonCriticalLinkFailuresAllowed:
MaxFailureTimeForNonCriticalLink (sec):
IntersiteFailuresAllowed:
MaxFailureTimeForIntersiteLink (sec):
KCC connection failures:
IntersiteFailuresAllowed:
IntersiteFailuresAllowed:

***************************************************************************
Enterprise Data
***************************************************************************

Globally Unique Identifiers (GUIDs) for each domain controller in the
enterprise
NOTE: the absence of a GUID means that the server has been demoted.
--------------------------------------------------------------------------------

Site Name: site1
---------------------------------------
Site Options :
Site Topology Generator: CN=NTDS
Settings,CN=KRAKEN,CN=Servers,CN=site1,CN=Sites,CN=Configuration,DC=test,DC=domain,DC=com
Site Topology Renewal :
Site Topology Failover :

KRAKEN
Server GUID (used for DNS)
: 48B95DA6-507E-4F58-97E9-FE131479B344
Replication Database GUID (used to identify partner in
replication): 5C548DDB-8E91-47FC-AC71-D80E154FFAF3
DSA Options : NTDSDSA_OPT_IS_GC
DSA Computer Path : CN=KRAKEN,OU=Domain
Controllers,DC=test,DC=domain,DC=com
DSA Schema Location :
CN=Schema,CN=Configuration,DC=test,DC=domain,DC=com
DSA Mail Address :
DSA DNS Host Name : KRAKEN.test.domain.ru
DSA BridgeHead Transports :

WEBBI
Server GUID (used for DNS)
: 043E43AA-A3F0-4F8A-807C-AD51654CC503
Replication Database GUID (used to identify partner in
replication): 99C14F97-3477-4C5C-B4A2-C60428B52D2F
DSA Options :
DSA Computer Path : CN=WEBBI,OU=Domain
Controllers,DC=test,DC=domain,DC=com
DSA Schema Location :
CN=Schema,CN=Configuration,DC=test,DC=domain,DC=com
DSA Mail Address :
_IsmService@043e43aa-a3f0-4f8a-807c-ad51654cc503._msdcs.test.domain.ru
DSA DNS Host Name : webbi.test.domain.ru
DSA BridgeHead Transports :



Site Links and Site Link Bridges
-----------------------------------------------------

Site Links
----------

DEFAULTIPSITELINK
Link Type: : IP
Distinguished Name :
CN=DEFAULTIPSITELINK,CN=IP,CN=Inter-Site
Transports,CN=Sites,CN=Configuration,DC=test,DC=domain,DC=com
Replication Interval : 180
Cost : 100
Options :
Site List :
site1

Site Link Bridges
------------------

Active Directory Replication Monitor determined that no Site
Link Bridges are present in the Directory.
Inter-Site Transports
---------------------

IP
Options :
DLL Name : ismip.dll
Address Type: dNSHostName

SMTP
Options : NTDSTRANSPORT_OPT_IGNORE_SCHEDULES
DLL Name : ismsmtp.dll
Address Type: mailAddress

Subnets
-------
172.20.11.0/24
Associated Site :
CN=site1,CN=Sites,CN=Configuration,DC=test,DC=domain,DC=com

172.20.12.0/24
Associated Site :
CN=site1,CN=Sites,CN=Configuration,DC=test,DC=domain,DC=com

172.20.21.0/24
Associated Site :
CN=site1,CN=Sites,CN=Configuration,DC=test,DC=domain,DC=com

172.20.22.0/24
Associated Site :
CN=site1,CN=Sites,CN=Configuration,DC=test,DC=domain,DC=com

172.20.31.0/24
Associated Site :
CN=site1,CN=Sites,CN=Configuration,DC=test,DC=domain,DC=com

172.20.32.0/24
Associated Site :
CN=site1,CN=Sites,CN=Configuration,DC=test,DC=domain,DC=com

172.20.41.0/24
Associated Site :
CN=site1,CN=Sites,CN=Configuration,DC=test,DC=domain,DC=com

172.20.42.0/24
Associated Site :
CN=site1,CN=Sites,CN=Configuration,DC=test,DC=domain,DC=com

Active Directory Configuration Data
 
A

Ace Fekay [MVP]

In
Alex Litvin said:
something wron with gif attachment - so here is the log
<snip>

Have you looked at this article to help remove objects?

HOW TO Remove Data in Active Directory After an Unsuccessful Domain
Controller Demotion Q216498:
http://support.microsoft.com/?id=216498

Also, I would look in Sites and Services, ADUC and in ADSI Edit to insure it
doesn't show up there as well.

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
A

Alex Litvin

In
<snip>

Have you looked at this article to help remove objects?

HOW TO Remove Data in Active Directory After an Unsuccessful Domain
Controller Demotion Q216498:
http://support.microsoft.com/?id=216498

Also, I would look in Sites and Services, ADUC and in ADSI Edit to insure it
doesn't show up there as well.

Nowhere ! :(
this object is deleted - i can find it using ldp - it has old name +
DEL - i think this server object is thumbstoned now
but i dont understand how to delete replication tasks which points to
this deleted object
 
A

Ace Fekay [MVP]

In
Alex Litvin said:
Nowhere ! :(
this object is deleted - i can find it using ldp - it has old name +
DEL - i think this server object is thumbstoned now
but i dont understand how to delete replication tasks which points to
this deleted object

Tombstoned means its deleted, but snce it's still showing up as a rep
partner, it still must be somewhere, correct?

Do me a favor and double check in Sites and Services, go under each server's
NTDS Setting and see if there is a connection object to that server in
question from one of the current servers that still remains?



--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
A

Alex Litvin

Tombstoned means its deleted, but snce it's still showing up as a rep
partner, it still must be somewhere, correct?
yes, but i can't find
Do me a favor and double check in Sites and Services, go under each server's
NTDS Setting and see if there is a connection object to that server in
question from one of the current servers that still remains?
no - only auto generated of working servers to each other

here is the repadmin /showreps output (i've inserted '!' to show links
to old server which was deleted, and it's objectguid is in error
messages in windows replication log):

SITE1\DC1
DSA Options : (none)
objectGuid : 043e43aa-a3f0-4f8a-807c-ad51654cc503
invocationID: 99c14f97-3477-4c5c-b4a2-c60428b52d2f

==== INBOUND NEIGHBORS ======================================

CN=Schema,CN=Configuration,DC=test,DC=domain,DC=com
!!!!!!!!!!!!!!!!!!!!!!!!!
SITE1\dc_old
DEL:52ad7299-943f-4dcb-baf0-198aae65c49c (deleted DSA) via RPC
objectGuid: 9c6214b0-289e-4018-986d-2067aafb1774
!!!!!!!!!!!!!!!!!!!!!!!
SITE1\dc2 via RPC
objectGuid: 48b95da6-507e-4f58-97e9-fe131479b344
Last attempt @ 2004-08-19 10:51.32 was successful.

CN=Configuration,DC=test,DC=domain,DC=com
!!!!!!!!!!!!!!!!!!!!!
SITE1\dc_old
DEL:52ad7299-943f-4dcb-baf0-198aae65c49c (deleted DSA) via RPC
objectGuid: 9c6214b0-289e-4018-986d-2067aafb1774
!!!!!!!!!!!!!!!!!!!!
SITE1\dc2 via RPC
objectGuid: 48b95da6-507e-4f58-97e9-fe131479b344
Last attempt @ 2004-08-19 11:27.19 was successful.

DC=test,DC=domain,DC=com
!!!!!!!!!!!!!!
SITE1\dc_old
DEL:52ad7299-943f-4dcb-baf0-198aae65c49c (deleted DSA) via RPC
objectGuid: 9c6214b0-289e-4018-986d-2067aafb1774
!!!!!!!!!!!!!!!!!
SITE1\dc2 via RPC
objectGuid: 48b95da6-507e-4f58-97e9-fe131479b344
Last attempt @ 2004-08-19 11:35.14 was successful.

==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============

CN=Schema,CN=Configuration,DC=test,DC=domain,DC=com
SITE1\dc2 via RPC
objectGuid: 48b95da6-507e-4f58-97e9-fe131479b344

CN=Configuration,DC=test,DC=domain,DC=com
SITE1\dc2 via RPC
objectGuid: 48b95da6-507e-4f58-97e9-fe131479b344

DC=test,DC=domain,DC=com
SITE1\dc2 via RPC
objectGuid: 48b95da6-507e-4f58-97e9-fe131479b344
 
A

Ace Fekay [MVP]

In
Alex Litvin said:
no - only auto generated of working servers to each other

here is the repadmin /showreps output (i've inserted '!' to show links
to old server which was deleted, and it's objectguid is in error
messages in windows replication log):

SITE1\DC1
DSA Options : (none)
objectGuid : 043e43aa-a3f0-4f8a-807c-ad51654cc503
invocationID: 99c14f97-3477-4c5c-b4a2-c60428b52d2f

==== INBOUND NEIGHBORS ======================================

CN=Schema,CN=Configuration,DC=test,DC=domain,DC=com
!!!!!!!!!!!!!!!!!!!!!!!!!
SITE1\dc_old
DEL:52ad7299-943f-4dcb-baf0-198aae65c49c (deleted DSA) via RPC
objectGuid: 9c6214b0-289e-4018-986d-2067aafb1774
!!!!!!!!!!!!!!!!!!!!!!!
SITE1\dc2 via RPC
objectGuid: 48b95da6-507e-4f58-97e9-fe131479b344
Last attempt @ 2004-08-19 10:51.32 was successful.

CN=Configuration,DC=test,DC=domain,DC=com
!!!!!!!!!!!!!!!!!!!!!
SITE1\dc_old
DEL:52ad7299-943f-4dcb-baf0-198aae65c49c (deleted DSA) via RPC
objectGuid: 9c6214b0-289e-4018-986d-2067aafb1774
!!!!!!!!!!!!!!!!!!!!
SITE1\dc2 via RPC
objectGuid: 48b95da6-507e-4f58-97e9-fe131479b344
Last attempt @ 2004-08-19 11:27.19 was successful.

DC=test,DC=domain,DC=com
!!!!!!!!!!!!!!
SITE1\dc_old
DEL:52ad7299-943f-4dcb-baf0-198aae65c49c (deleted DSA) via RPC
objectGuid: 9c6214b0-289e-4018-986d-2067aafb1774
!!!!!!!!!!!!!!!!!
SITE1\dc2 via RPC
objectGuid: 48b95da6-507e-4f58-97e9-fe131479b344
Last attempt @ 2004-08-19 11:35.14 was successful.

==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============

CN=Schema,CN=Configuration,DC=test,DC=domain,DC=com
SITE1\dc2 via RPC
objectGuid: 48b95da6-507e-4f58-97e9-fe131479b344

CN=Configuration,DC=test,DC=domain,DC=com
SITE1\dc2 via RPC
objectGuid: 48b95da6-507e-4f58-97e9-fe131479b344

DC=test,DC=domain,DC=com
SITE1\dc2 via RPC
objectGuid: 48b95da6-507e-4f58-97e9-fe131479b344

Hmm, I'm starting to think looking at this that its really not in the
replication topology and just shows as deleted. If so, it will eventually
disappear after the tombstone if up.

Tell you what, can you run replmon and rt-click on the server name and
choose 'show topology'. Then rt-click on each object and ask to show
intrsite and intersite connections. Please let me know what you find.

Thanks

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top