banti

Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • Avatar
    banti
    Member

    Thanks, for the feedback.

    Avatar
    banti
    Member

    Thanks, for your help. I was able to correct the issue by re-naming the DC in AD sites and Services. Once that was completed replication took place and the log in script was working as it planned. Unless, I mistaken I thought one of the benefits of using M/S AD was the fault tolerance. If one site was unavailable you could still replicate to the other sites, by way of manual replication. Am I mistaken?

    Avatar
    banti
    Member

    No to anything in the AD profile. Full AD replication might be causing the issue because we found under AD Sites and Services one of the sites that have a DC the DNS name of the DC is listed properly but the name of the server followed by GUID : CNF:26d18e1e-9069-4b60-bb37-6baf554a8351. I have found that this information is called globally unique identifier (GUID). This might be preventing replication is this true?

Viewing 3 posts - 1 through 3 (of 3 total)

Register for this Petri Webinar!

Software-Defined Unlimited Backup Storage

Tuesday, August 27, 2019 @ 1:00 pm EDT

A Scale-Out Backup storage infrastructure is a must-have technology for your backups. In this webinar, join expert Rick Vanover for a look on what real-world problems are solved by the Scale-Out Backup Repository.

Register Now

Sponsored By