Results 1 to 4 of 4

Thread: Help Replication problem

  1. #1
    =?Utf-8?B?Tmd1eWVu?= Guest

    Help Replication problem

    I just installed 2 W2k3 servers. They both are DC in cc.com domain.
    mainDC is the fsmo server. then I installed the second server (Email) with
    exchange 2003.
    During the test they ran OK with replication between 2 servers. Later I
    found out they could not replicate any more. I can only remember I promote
    the second server to Global catalog server.
    Now in my Directory service event I have this message
    -----------------------------------------------------------------
    It has been too long since this machine last replicated with the named
    source machine. The time between replications with this source has exceeded
    the tombstone lifetime. Replication has been stopped with this source.
    The reason that replication is not allowed to continue is that the two
    machine's views of deleted objects may now be different. The source machine
    may still have copies of objects that have been deleted (and garbage
    collected) on this machine. If they were allowed to replicate, the source
    machine might return objects which have already been deleted.
    Time of last successful replication:
    2004-11-02 15:53:46
    Invocation ID of source:
    0006f6cc-f6bc-0006-880b-7103f0bd3a03
    Name of source:
    731fdab6-a403-4dfb-b7e9-caea97b57ff3._msdcs.ccorp.com
    Tombstone lifetime (days):
    60

    The replication operation has failed.

    User Action:

    Determine which of the two machines was disconnected from the forest and is
    now out of date. You have three options:

    1. Demote or reinstall the machine(s) that were disconnected.
    2. Use the "repadmin /removelingeringobjects" tool to remove inconsistent
    deleted objects and then resume replication.
    3. Resume replication. Inconsistent deleted objects may be introduced. You
    can continue replication by using the following registry key. Once the
    systems replicate once, it is recommended that you remove the key to
    reinstate the protection.
    Registry Key:
    HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Allow Replication
    With Divergent and Corrupt Partner
    ------------------------------------
    Since it's obviously tell me how to fix it, but I wasn't sure if fix that
    will cause any trouble with the Exchange 2003 server running.
    Should I stop the exchange service, then demote the email server and promote
    it again.
    Do I lose any settings, mailbox that already in place?
    Please help.
    thanks,

  2. #2
    =?Utf-8?B?TnVtcHR5?= Guest

    RE: Help Replication problem

    The Exchange server does not need to be a Domain Controller to function. It
    does however need to be able to talk to a Global Catalog Server. Turn on the
    Global catalog on the Primary Server (Hosts all FSMO roles) and demote the
    exchange server with dcpromo.

    The mailboxes will be linked to the Active Directory users as it writes
    Attributes to the User object. The mailbox will remain active in the Exchange
    Mailbox store.

    If for any reason a mailbox was created and the association with the user
    account has been lost because the change has not replicated, then you will
    have to "Reconnect the mailbox." You can do this by right clicking on the
    mailbox in Exchange System Manager. Go to google and type "Reconnect Exchange
    Mailbox" to find kb articles on how to do this.

    Below I have detailed some steps to diagnose the problems with your Active
    Directory replication. I'd suggest strongly that you do this after business
    hours and plan to work late. It might even pay to have someone else with you
    to bounce ideas off and to doublecheck things.

    To work out why you are having replication issues, prior to promoting the
    Exchange server to a Domain controller again, test all of the following areas
    (in this order) from your FSMO Master Domain Controller:

    - IP Connectivity (can you ping the IP Address, not the server name)
    - Routing (if you run Tracert %ExchangeServerName% what is between the DC
    and the Exchange box, there may be a firewall or dodgy router that needs
    fixing)
    - Network Diagnostics (If you run Netdiag is everything flagging as OK?)
    - Forward Name resolution (Run nslookup
    %exchangeservername%.%domainname%.com and ensure the IP Address is the actual
    IP Address of the exchange server)
    - Reverse Lookup (Run nslookup %ExchangeServerIPAddress% and ensure the IP
    Address resolves back to the exchange server name)
    - Domain Controller DNS Records (Run the DNS/Nslookup tests listed above
    with the domain controllers hostname in its place, the problem may not be the
    DNS entry for your Exchange box, it may be the domain controllers entry)
    - SRV Records (are all of the required DNS SRV records listed in active
    directory, if not, ask why, it may be that the Active Directory records in
    DNS were never created correctly)
    - Domain Controller Diagnostics (Run dcdiag.exe on the Domain Controller,
    there may be some problem with active directory or the Domain Controller may
    have issues)
    - Bring up a completely different machine (MAKE SURE THIS "SERVER" is stable
    and can handle the job for a day or so) as a server and promote it to a DC.
    Ensure everything on this DC is working fine by running DCDIAG and creating a
    user called "TEST123" on the original DC and ensuring that the user is then
    replicated to the temporary Domain Controller
    - If this works OK then transfer all the FSMO roles (one by one) to the
    temporary domain controller (and make it a Global Catalog server), ensure all
    works correctly, demote the original DC, reboot and check it is ok, then run
    DCPROMO again and make it a DC...leave it for a while and make sure it is
    stable then move all the FSMO roles back to it and demote the temporary
    server.
    - If all of the above is successful, then you can start thinking about
    adding the DC role to your Exchange server again.

    Ask yourself if you need two domain controllers, is it to load balance your
    logins or is it for redundancy? If it is redundancy, get a reliable desktop
    and a UPS, put it in another physical part of the building or even a remote
    site if you want to. This wouldn't be a bad idea (even if you do need 2
    domain controllers) simply for very fast recovery in the event of a failure /
    catastrophe. In Active Directory Sites and Services, create a new site and
    assign a different subnet to the site that will be used for redundancy...

    ie. If your Network ID is 192.168.1.0 then you want to set up your "Remote
    Site" as 192.168.100.0 (to allow for growth in your network)

    Add a secondary network card to your FSMO Master Domain Controller and
    assign it an IP Address in the 192.168.100.0 range so it has a foot in both
    camps.

    This will give you a domain controller that will receive all replicated
    items, additions and deletions, but it will not take any logons so the
    machine will just tick over.

    Hope this helps,

    Numpty
    MCP - XP, 2000 Pro, 2000 Server, Active Directory

  3. #3
    =?Utf-8?B?Tmd1eWVu?= Guest

    RE: Help Replication problem

    Thanks Numpty, I just want to double check before I actually demote the Email
    server.
    The communication of the 2 servers seems fine. The Email server running
    slave DNS from the Master domain controller. I will double check with the
    list from your advise.
    I ran the dcdiag also and I post down here for reference. (pretty long)
    -----------------------------------------------------------------------

    Domain Controller Diagnosis

    Performing initial setup:
    Done gathering initial info.

    Doing initial required tests

    Testing server: Default-First-Site-Name\email
    Starting test: Connectivity
    ......................... email passed test Connectivity

    Doing primary tests

    Testing server: Default-First-Site-Name\email
    Starting test: Replications
    [Replications Check,email] A recent replication attempt failed:
    From mainDC to email
    Naming Context: DC=DomainDnsZones,DC=ccorp,DC=com
    The replication generated an error (8614):
    The Active Directory cannot replicate with this server because
    the time since the last replication with this server has exceeded the
    tombstone lifetime.
    The failure occurred at 2005-01-12 13:54:59.
    The last success occurred at 2004-11-02 15:50:02.
    66 failures have occurred since the last success.
    [mainDC] DsBindWithSpnEx() failed with error -2146893022,
    The target principal name is incorrect..
    [Replications Check,email] A recent replication attempt failed:
    From mainDC to email
    Naming Context: DC=ForestDnsZones,DC=ccorp,DC=com
    The replication generated an error (8614):
    The Active Directory cannot replicate with this server because
    the time since the last replication with this server has exceeded the
    tombstone lifetime.
    The failure occurred at 2005-01-12 13:54:59.
    The last success occurred at 2004-11-02 15:50:02.
    66 failures have occurred since the last success.
    [Replications Check,email] A recent replication attempt failed:
    From mainDC to email
    Naming Context: CN=Schema,CN=Configuration,DC=ccorp,DC=com
    The replication generated an error (-2146893022):
    The target principal name is incorrect.
    The failure occurred at 2005-01-16 16:55:06.
    The last success occurred at 2004-11-02 15:50:02.
    1723 failures have occurred since the last success.
    [Replications Check,email] A recent replication attempt failed:
    From mainDC to email
    Naming Context: CN=Configuration,DC=ccorp,DC=com
    The replication generated an error (-2146893022):
    The target principal name is incorrect.
    The failure occurred at 2005-01-16 16:55:06.
    The last success occurred at 2004-11-02 16:14:00.
    2070 failures have occurred since the last success.
    [Replications Check,email] A recent replication attempt failed:
    From mainDC to email
    Naming Context: DC=ccorp,DC=com
    The replication generated an error (-2146893022):
    The target principal name is incorrect.
    The failure occurred at 2005-01-16 16:56:07.
    The last success occurred at 2004-11-02 16:34:05.
    34488 failures have occurred since the last success.
    REPLICATION-RECEIVED LATENCY WARNING
    email: Current time is 2005-01-16 16:56:35.
    DC=DomainDnsZones,DC=ccorp,DC=com
    Last replication recieved from mainDC at 2004-11-02 15:50:02.
    WARNING: This latency is over the Tombstone Lifetime of 60
    days!
    DC=ForestDnsZones,DC=ccorp,DC=com
    Last replication recieved from mainDC at 2004-11-02 15:50:02.
    WARNING: This latency is over the Tombstone Lifetime of 60
    days!
    CN=Schema,CN=Configuration,DC=ccorp,DC=com
    Last replication recieved from mainDC at 2004-11-02 15:50:02.
    WARNING: This latency is over the Tombstone Lifetime of 60
    days!
    CN=Configuration,DC=ccorp,DC=com
    Last replication recieved from mainDC at 2004-11-02 16:14:00.
    WARNING: This latency is over the Tombstone Lifetime of 60
    days!
    DC=ccorp,DC=com
    Last replication recieved from mainDC at 2004-11-02 16:34:05.
    WARNING: This latency is over the Tombstone Lifetime of 60
    days!
    ......................... email passed test Replications
    Starting test: NCSecDesc
    ......................... email passed test NCSecDesc
    Starting test: NetLogons
    ......................... email passed test NetLogons
    Starting test: Advertising
    ......................... email passed test Advertising
    Starting test: KnowsOfRoleHolders
    Warning: mainDC is the Schema Owner, but is not responding to DS
    RPC Bind.
    [mainDC] LDAP bind failed with error 8341,
    A directory service error has occurred..
    Warning: mainDC is the Schema Owner, but is not responding to LDAP
    Bind.
    Warning: mainDC is the Domain Owner, but is not responding to DS
    RPC Bind.
    Warning: mainDC is the Domain Owner, but is not responding to LDAP
    Bind.
    Warning: mainDC is the PDC Owner, but is not responding to DS RPC
    Bind.
    Warning: mainDC is the PDC Owner, but is not responding to LDAP Bind.
    Warning: mainDC is the Rid Owner, but is not responding to DS RPC
    Bind.
    Warning: mainDC is the Rid Owner, but is not responding to LDAP Bind.
    Warning: mainDC is the Infrastructure Update Owner, but is not
    responding to DS RPC Bind.
    Warning: mainDC is the Infrastructure Update Owner, but is not
    responding to LDAP Bind.
    ......................... email failed test KnowsOfRoleHolders
    Starting test: RidManager
    ......................... email failed test RidManager
    Starting test: MachineAccount
    ......................... email passed test MachineAccount
    Starting test: Services
    ......................... email passed test Services
    Starting test: ObjectsReplicated
    ......................... email passed test ObjectsReplicated
    Starting test: frssysvol
    ......................... email passed test frssysvol
    Starting test: frsevent
    There are warning or error events within the last 24 hours after the

    SYSVOL has been shared. Failing SYSVOL replication problems may
    cause

    Group Policy problems.
    ......................... email failed test frsevent
    Starting test: kccevent
    ......................... email passed test kccevent
    Starting test: systemlog
    An Error Event occured. EventID: 0x40000004
    Time Generated: 01/16/2005 16:30:31
    Event String: The kerberos client received a

    An Error Event occured. EventID: 0x40000004
    Time Generated: 01/16/2005 16:36:15
    Event String: The kerberos client received a

    An Error Event occured. EventID: 0x40000004
    Time Generated: 01/16/2005 16:36:49
    Event String: The kerberos client received a

    An Error Event occured. EventID: 0x40000004
    Time Generated: 01/16/2005 16:52:05
    Event String: The kerberos client received a

    An Error Event occured. EventID: 0x40000004
    Time Generated: 01/16/2005 16:54:51
    Event String: The kerberos client received a

    An Error Event occured. EventID: 0x40000004
    Time Generated: 01/16/2005 16:54:54
    Event String: The kerberos client received a

    An Error Event occured. EventID: 0x40000004
    Time Generated: 01/16/2005 16:54:56
    Event String: The kerberos client received a

    ......................... email failed test systemlog
    Starting test: VerifyReferences
    ......................... email passed test VerifyReferences

    Running partition tests on : DomainDnsZones
    Starting test: CrossRefValidation
    ......................... DomainDnsZones passed test
    CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... DomainDnsZones passed test CheckSDRefDom

    Running partition tests on : ForestDnsZones
    Starting test: CrossRefValidation
    ......................... ForestDnsZones passed test
    CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... ForestDnsZones passed test CheckSDRefDom

    Running partition tests on : Schema
    Starting test: CrossRefValidation
    ......................... Schema passed test CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... Schema passed test CheckSDRefDom

    Running partition tests on : Configuration
    Starting test: CrossRefValidation
    ......................... Configuration passed test
    CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... Configuration passed test CheckSDRefDom

    Running partition tests on : ccorp
    Starting test: CrossRefValidation
    ......................... ccorp passed test CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... ccorp passed test CheckSDRefDom

    Running enterprise tests on : ccorp.com
    Starting test: Intersite
    ......................... ccorp.com passed test Intersite
    Starting test: FsmoCheck
    ......................... ccorp.com passed test FsmoCheck
    ------------------------------------------------------------------------------------------------


    "Numpty" wrote:

    > The Exchange server does not need to be a Domain Controller to function. It
    > does however need to be able to talk to a Global Catalog Server. Turn on the
    > Global catalog on the Primary Server (Hosts all FSMO roles) and demote the
    > exchange server with dcpromo.
    >


  4. #4
    =?Utf-8?B?TnVtcHR5?= Guest

    RE: Help Replication problem

    Hey Nguyen,
    It appears from the Dcdiag information you provided that there are problems
    with replication between your domain controllers. I'd suggest moving all the
    FSMO roles to a reliable workstation that is set up as a server (promoted to
    domain controller).

    You particularly want to move the RID Master role, this manages the Domain
    SID that is appended to the user / machine SID to ensure it is unique.

    You should really consider demoting your domain controllers completely after
    all FSMO roles are transferred across (ensure you have full backups first)

    Best of luck :)

    "Nguyen" wrote:

    > Thanks Numpty, I just want to double check before I actually demote the Email
    > server.
    > The communication of the 2 servers seems fine. The Email server running
    > slave DNS from the Master domain controller. I will double check with the
    > list from your advise.
    > I ran the dcdiag also and I post down here for reference. (pretty long)
    > -----------------------------------------------------------------------
    >
    > Domain Controller Diagnosis
    >
    > Performing initial setup:
    > Done gathering initial info.
    >
    > Doing initial required tests
    >
    > Testing server: Default-First-Site-Name\email
    > Starting test: Connectivity
    > ......................... email passed test Connectivity
    >
    > Doing primary tests
    >
    > Testing server: Default-First-Site-Name\email
    > Starting test: Replications
    > [Replications Check,email] A recent replication attempt failed:
    > From mainDC to email
    > Naming Context: DC=DomainDnsZones,DC=ccorp,DC=com
    > The replication generated an error (8614):
    > The Active Directory cannot replicate with this server because
    > the time since the last replication with this server has exceeded the
    > tombstone lifetime.
    > The failure occurred at 2005-01-12 13:54:59.
    > The last success occurred at 2004-11-02 15:50:02.
    > 66 failures have occurred since the last success.
    > [mainDC] DsBindWithSpnEx() failed with error -2146893022,
    > The target principal name is incorrect..
    > [Replications Check,email] A recent replication attempt failed:
    > From mainDC to email
    > Naming Context: DC=ForestDnsZones,DC=ccorp,DC=com
    > The replication generated an error (8614):
    > The Active Directory cannot replicate with this server because
    > the time since the last replication with this server has exceeded the
    > tombstone lifetime.
    > The failure occurred at 2005-01-12 13:54:59.
    > The last success occurred at 2004-11-02 15:50:02.
    > 66 failures have occurred since the last success.
    > [Replications Check,email] A recent replication attempt failed:
    > From mainDC to email
    > Naming Context: CN=Schema,CN=Configuration,DC=ccorp,DC=com
    > The replication generated an error (-2146893022):
    > The target principal name is incorrect.
    > The failure occurred at 2005-01-16 16:55:06.
    > The last success occurred at 2004-11-02 15:50:02.
    > 1723 failures have occurred since the last success.
    > [Replications Check,email] A recent replication attempt failed:
    > From mainDC to email
    > Naming Context: CN=Configuration,DC=ccorp,DC=com
    > The replication generated an error (-2146893022):
    > The target principal name is incorrect.
    > The failure occurred at 2005-01-16 16:55:06.
    > The last success occurred at 2004-11-02 16:14:00.
    > 2070 failures have occurred since the last success.
    > [Replications Check,email] A recent replication attempt failed:
    > From mainDC to email
    > Naming Context: DC=ccorp,DC=com
    > The replication generated an error (-2146893022):
    > The target principal name is incorrect.
    > The failure occurred at 2005-01-16 16:56:07.
    > The last success occurred at 2004-11-02 16:34:05.
    > 34488 failures have occurred since the last success.
    > REPLICATION-RECEIVED LATENCY WARNING
    > email: Current time is 2005-01-16 16:56:35.
    > DC=DomainDnsZones,DC=ccorp,DC=com
    > Last replication recieved from mainDC at 2004-11-02 15:50:02.
    > WARNING: This latency is over the Tombstone Lifetime of 60
    > days!
    > DC=ForestDnsZones,DC=ccorp,DC=com
    > Last replication recieved from mainDC at 2004-11-02 15:50:02.
    > WARNING: This latency is over the Tombstone Lifetime of 60
    > days!
    > CN=Schema,CN=Configuration,DC=ccorp,DC=com
    > Last replication recieved from mainDC at 2004-11-02 15:50:02.
    > WARNING: This latency is over the Tombstone Lifetime of 60
    > days!
    > CN=Configuration,DC=ccorp,DC=com
    > Last replication recieved from mainDC at 2004-11-02 16:14:00.
    > WARNING: This latency is over the Tombstone Lifetime of 60
    > days!
    > DC=ccorp,DC=com
    > Last replication recieved from mainDC at 2004-11-02 16:34:05.
    > WARNING: This latency is over the Tombstone Lifetime of 60
    > days!
    > ......................... email passed test Replications
    > Starting test: NCSecDesc
    > ......................... email passed test NCSecDesc
    > Starting test: NetLogons
    > ......................... email passed test NetLogons
    > Starting test: Advertising
    > ......................... email passed test Advertising
    > Starting test: KnowsOfRoleHolders
    > Warning: mainDC is the Schema Owner, but is not responding to DS
    > RPC Bind.
    > [mainDC] LDAP bind failed with error 8341,
    > A directory service error has occurred..
    > Warning: mainDC is the Schema Owner, but is not responding to LDAP
    > Bind.
    > Warning: mainDC is the Domain Owner, but is not responding to DS
    > RPC Bind.
    > Warning: mainDC is the Domain Owner, but is not responding to LDAP
    > Bind.
    > Warning: mainDC is the PDC Owner, but is not responding to DS RPC
    > Bind.
    > Warning: mainDC is the PDC Owner, but is not responding to LDAP Bind.
    > Warning: mainDC is the Rid Owner, but is not responding to DS RPC
    > Bind.
    > Warning: mainDC is the Rid Owner, but is not responding to LDAP Bind.
    > Warning: mainDC is the Infrastructure Update Owner, but is not
    > responding to DS RPC Bind.
    > Warning: mainDC is the Infrastructure Update Owner, but is not
    > responding to LDAP Bind.
    > ......................... email failed test KnowsOfRoleHolders
    > Starting test: RidManager
    > ......................... email failed test RidManager
    > Starting test: MachineAccount
    > ......................... email passed test MachineAccount
    > Starting test: Services
    > ......................... email passed test Services
    > Starting test: ObjectsReplicated
    > ......................... email passed test ObjectsReplicated
    > Starting test: frssysvol
    > ......................... email passed test frssysvol
    > Starting test: frsevent
    > There are warning or error events within the last 24 hours after the
    >
    > SYSVOL has been shared. Failing SYSVOL replication problems may
    > cause
    >
    > Group Policy problems.
    > ......................... email failed test frsevent
    > Starting test: kccevent
    > ......................... email passed test kccevent
    > Starting test: systemlog
    > An Error Event occured. EventID: 0x40000004
    > Time Generated: 01/16/2005 16:30:31
    > Event String: The kerberos client received a
    >
    > An Error Event occured. EventID: 0x40000004
    > Time Generated: 01/16/2005 16:36:15
    > Event String: The kerberos client received a
    >
    > An Error Event occured. EventID: 0x40000004
    > Time Generated: 01/16/2005 16:36:49
    > Event String: The kerberos client received a
    >
    > An Error Event occured. EventID: 0x40000004
    > Time Generated: 01/16/2005 16:52:05
    > Event String: The kerberos client received a
    >
    > An Error Event occured. EventID: 0x40000004
    > Time Generated: 01/16/2005 16:54:51
    > Event String: The kerberos client received a
    >
    > An Error Event occured. EventID: 0x40000004
    > Time Generated: 01/16/2005 16:54:54
    > Event String: The kerberos client received a
    >
    > An Error Event occured. EventID: 0x40000004
    > Time Generated: 01/16/2005 16:54:56
    > Event String: The kerberos client received a
    >
    > ......................... email failed test systemlog
    > Starting test: VerifyReferences
    > ......................... email passed test VerifyReferences
    >
    > Running partition tests on : DomainDnsZones
    > Starting test: CrossRefValidation
    > ......................... DomainDnsZones passed test
    > CrossRefValidation
    > Starting test: CheckSDRefDom
    > ......................... DomainDnsZones passed test CheckSDRefDom
    >
    > Running partition tests on : ForestDnsZones
    > Starting test: CrossRefValidation
    > ......................... ForestDnsZones passed test
    > CrossRefValidation
    > Starting test: CheckSDRefDom
    > ......................... ForestDnsZones passed test CheckSDRefDom
    >
    > Running partition tests on : Schema
    > Starting test: CrossRefValidation
    > ......................... Schema passed test CrossRefValidation
    > Starting test: CheckSDRefDom
    > ......................... Schema passed test CheckSDRefDom
    >
    > Running partition tests on : Configuration
    > Starting test: CrossRefValidation
    > ......................... Configuration passed test
    > CrossRefValidation
    > Starting test: CheckSDRefDom
    > ......................... Configuration passed test CheckSDRefDom
    >
    > Running partition tests on : ccorp
    > Starting test: CrossRefValidation
    > ......................... ccorp passed test CrossRefValidation
    > Starting test: CheckSDRefDom
    > ......................... ccorp passed test CheckSDRefDom
    >
    > Running enterprise tests on : ccorp.com
    > Starting test: Intersite
    > ......................... ccorp.com passed test Intersite
    > Starting test: FsmoCheck
    > ......................... ccorp.com passed test FsmoCheck
    > ------------------------------------------------------------------------------------------------
    >
    >
    > "Numpty" wrote:
    >
    > > The Exchange server does not need to be a Domain Controller to function. It
    > > does however need to be able to talk to a Global Catalog Server. Turn on the
    > > Global catalog on the Primary Server (Hosts all FSMO roles) and demote the
    > > exchange server with dcpromo.
    > >


Similar Threads

  1. NTDS Replication: How to remove a replication partner?
    By haritable in forum Small Business Server
    Replies: 3
    Last Post: 10-05-2012, 09:50 PM
  2. DCs Replication problem 1311
    By Chrishow in forum Windows Server Help
    Replies: 1
    Last Post: 30-04-2012, 11:36 PM
  3. Domain replication problem
    By irolfi in forum Active Directory
    Replies: 2
    Last Post: 08-12-2011, 03:25 AM
  4. Active Directory Replication Problem
    By joe_ista in forum Operating Systems
    Replies: 1
    Last Post: 10-06-2010, 11:15 AM
  5. SYSVOL Replication Problem
    By hatred in forum Active Directory
    Replies: 5
    Last Post: 19-01-2008, 05:53 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,711,635,141.93868 seconds with 17 queries