Info about AD Domain Controller to which I'm connected

Hi,
Is there a way to find the AD Domain Controller to which I'm connected ?
Some time I find the info in these file :
/Library/Preferences/OpenDirectory/DynamicData/Active Directory/<MYDOMAIN>.plist
under 'last used server' but this field is not always populated..
Is there any other place where find or some command to use ?? (or even more info about the previous plist file and how is created/populated.. i have several Macsac on same domain but not all computers have the file populated in the same way..)
Any help appreciated
Thanks
m.

Some added toolbar and anti-virus add-ons are known to cause
Firefox issues. '''Disable All of them.'''
Type '''about:preferences#advanced'''<Enter> in the address bar.
Under '''Advanced,''' Select '''Network.'''
Look for '''Configure How Firefox Connects''' and press the '''Settings''' button.
Check the settings.
Some problems occurs when your Internet security program was set
to trust the previous version of Firefox, but no longer recognizes your
updated version as trusted. Now how to fix the problem: To allow
Firefox to connect to the Internet again;
* Make sure your Internet security software is up-to-date (i.e. you are running the latest version).
* Remove Firefox from your program's list of trusted or recognized programs. For detailed instructions, see
'''[https://support.mozilla.org/en-US/kb/configure-firewalls-so-firefox-can-access-internet Configure firewalls so that Firefox can access the Internet.]''' {web link}

Similar Messages

  • When the domain controller locator process happened

    HI Guys
      I read lots of articles about how domain controller located. And so far i thougth i knew most of the process, but still have some question.
    1.when the DC locator happend ,just start during computer boots up ,or started after user press CTRL+ALT+DEL and input username and credential.
    2.Based on following Technet article , step 7, what's the difference between  "If the client has found a DC in the site in which the DC claims the client is located" and "If the returned domain controller is in the cloest site "
    ? And step 8, if the domain that is being quried is same as the domain that the computer joined, was the first domain means the domain the user belongs to ? like xxx\username ?

    Hi Jacky,
    I assume that you are talking about this article:
    Active Directory: Using Catch-All Subnets in Active Directory
    http://technet.microsoft.com/en-us/forefront/2009.06.subnets.aspx
    >when the DC locator happend ,just start during computer boots up ,or started after user press CTRL+ALT+DEL and input username and credential.
    The DC locator initiates after we input domain credentials and press Enter.
    >what's the difference between "If the client has found a DC in the site in which the DC claims the client is located" and "If the returned domain controller is in the closest site "?
    “If the client has found a DC in the site in which the DC claims the client is located” means that the client and a DC are located in the same site. “If the returned domain controller is in the closest site” means that a DC which
    is located in the closest site is found (based on site link cost).
    >if the domain that is being queried is same as the domain that the computer joined, was the first domain means the domain the user belongs to ? like xxx\username ?
    Yes you are right that the first domain means the user account which tries to log on belongs to.
    More information for you:
    Enabling Clients to Locate the Next Closest Domain Controller
    http://technet.microsoft.com/en-us/library/cc733142(v=WS.10).aspx
    I hope this helps.
    Amy

  • When exchange Domain Controller or Global Catalog servers?

    I have a few questions want to get your help.
    1,which situation exchange would contact with the Domain Controller, and which situation  exchange would contact with the Global Catalog servers?what's the difference?
    2,for the mailbox replication service, besides moving the mailbox ,and  DAD relevant operations, which situation mailbox replication service also contact with Dc?
    Please click the Mark as Answer button if a post solves your problem!

    Hi,
    About Question 1:
    For Exchange, GC is mainly for Address Book lookups. Exchange server access to the global catalog for address information.
    About DC, every domain controller contains the following three directory partitions.
    1. Configuration: Contains the Configuration container, which stores configuration objects for the entire forest in cn=configuration,dc= forestRootDomain.
    2. Schema: Contains the Schema container, which stores class and attribute definitions for all existing and possible Active Directory objects in cn=schema,cn=configuration,dc= forestRootDomain.
    3. Domain: Contains a < domain > container, which stores users, computers, groups, and other objects for a specific domain.
    For example, each Exchange Server object has the attribute Boolean messageTrackingEnabled. The Exchange server processes will turn on or off message tracking depending on the value of this attribute in the directory. This is an example of configuration data.
    Configuration data is stored in the Configuration partition of Active Directory, and this partition is replicated to every DC in the Forest. Therefore Exchange can potentially go to any DC to access this information.
    About Question 2:
    The Mailbox Replication Service is responsible for moving mailboxes, importing and exporting .pst files, and restoring disabled and soft-deleted mailboxes. All these options need to contact with DC.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support
    Thank you so much
    Please click the Mark as Answer button if a post solves your problem!

  • Having trouble promoting a server to a Child Domain Controller

    Hello,
    I am having promoting a 2012 server that's already a member of a domain to a child domain controller.  All of the prereq's are met.  When I try to promote it, it shows the steps being processed.  When it begins to replicate the parent domain's
    database, it runs all night and never completes.  Any Idea what's going on?
    Thanks
    John G.
    John Grace

    Hello,
    Just to let you know I can ftp, telnet, and map drives to gptsserver1.gpts.biz from gptsserver2.gpts.biz but can't promote gptsserver2.gpts.biz to a child domain controller.  Any help is appreciated.
    Here is the contents of dcpromo.log from gptsserver2.gpts.biz:
    08/13/2014 21:14:32 [INFO] Promotion request for domain controller of new domain
    08/13/2014 21:14:32 [INFO] DnsDomainName  gpts2.gpts.biz
    08/13/2014 21:14:32 [INFO] FlatDomainName  GPTS2
    08/13/2014 21:14:32 [INFO] SiteName  Default-First-Site-Name
    08/13/2014 21:14:32 [INFO] SystemVolumeRootPath  C:\Windows\SYSVOL
    08/13/2014 21:14:32 [INFO] DsDatabasePath  C:\Windows\NTDS, DsLogPath  C:\Windows\NTDS
    08/13/2014 21:14:32 [INFO] ParentDnsDomainName  gpts.biz
    08/13/2014 21:14:32 [INFO] ParentServer  gptsserver1.gpts.biz
    08/13/2014 21:14:32 [INFO] Account (NULL)
    08/13/2014 21:14:32 [INFO] Options  5243072
    08/13/2014 21:14:32 [INFO] Validate supplied paths
    08/13/2014 21:14:32 [INFO] Validating path C:\Windows\NTDS.
    08/13/2014 21:14:32 [INFO] Path is a directory
    08/13/2014 21:14:32 [INFO] Path is on a fixed disk drive.
    08/13/2014 21:14:32 [INFO] Validating path C:\Windows\NTDS.
    08/13/2014 21:14:32 [INFO] Path is a directory
    08/13/2014 21:14:32 [INFO] Path is on a fixed disk drive.
    08/13/2014 21:14:32 [INFO] Validating path C:\Windows\SYSVOL.
    08/13/2014 21:14:32 [INFO] Path is on a fixed disk drive.
    08/13/2014 21:14:32 [INFO] Path is on an NTFS volume
    08/13/2014 21:14:32 [INFO] Child domain creation -- check the new domain name is child of parent domain name.
    08/13/2014 21:14:32 [INFO] Domain Creation -- check that the flat name is unique.
    08/13/2014 21:14:42 [INFO] Start the worker task
    08/13/2014 21:14:42 [INFO] Request for promotion returning 0
    08/13/2014 21:14:42 [INFO] Using supplied domain controller: gptsserver1.gpts.biz
    08/13/2014 21:14:42 [INFO] Using supplied site: Default-First-Site-Name
    08/13/2014 21:14:42 [INFO] Forcing time sync
    08/13/2014 21:14:42 [INFO] Forcing a time sync with gptsserver1.gpts.biz
    08/13/2014 21:14:42 [INFO] Reading domain policy from the domain controller gptsserver1.gpts.biz
    08/13/2014 21:14:42 [INFO] Stopping service NETLOGON
    08/13/2014 21:14:42 [INFO] Stopping service NETLOGON
    08/13/2014 21:14:42 [INFO] ControlService(STOP) on NETLOGON returned 0(gle=1062)
    08/13/2014 21:14:42 [INFO] Exiting service-stop loop after service NETLOGON entered STOPPED state
    08/13/2014 21:14:42 [INFO] StopService on NETLOGON returned 0
    08/13/2014 21:14:42 [INFO] Configuring service NETLOGON to 1 returned 0
    08/13/2014 21:14:42 [INFO] Stopped NETLOGON
    08/13/2014 21:14:42 [INFO] Creating the System Volume C:\Windows\SYSVOL
    08/13/2014 21:14:42 [INFO] Deleting current sysvol path C:\Windows\SYSVOL 
    08/13/2014 21:14:43 [INFO] Preparing for system volume replication using root C:\Windows\SYSVOL
    08/13/2014 21:14:43 [INFO] Created the system volume
    08/13/2014 21:14:43 [INFO] Copying initial Directory Service database file C:\Windows\system32\ntds.dit to C:\Windows\NTDS\ntds.dit
    08/13/2014 21:14:43 [INFO] Installing the Directory Service
    08/13/2014 21:14:43 [INFO] Calling NtdsInstall for gpts2.gpts.biz
    08/13/2014 21:14:43 [INFO] Starting Active Directory Domain Services installation
    08/13/2014 21:14:43 [INFO] Validating user supplied options
    08/13/2014 21:14:43 [INFO] Determining a site in which to install
    08/13/2014 21:14:43 [INFO] Examining an existing forest...
    08/13/2014 21:14:43 [INFO] Configuring the local computer to host Active Directory Domain Services
    08/13/2014 21:14:44 [INFO] EVENTLOG (Informational): NTDS General / Service Control : 1094
    Software write caching for the following disk drive has been disabled to prevent possible data loss during system failures such as power outages or hardware component failures that can cause a sudden shutdown of the system. The disk drive that stores Active
    Directory Domain Services log files is the only drive affected by this change.
    Disk drive:
    c:
    08/13/2014 21:14:55 [INFO] EVENTLOG (Informational): NTDS General / Internal Configuration : 2120
    This Active Directory Domain Services server does not support the Recycle Bin. Deleted objects may be undeleted, however, when an object is undeleted, some attributes of that object may be lost.  Additionally, attributes of other objects that refer to
    the object being undeleted may also be lost.
    08/13/2014 21:14:56 [INFO] Replicating the schema directory partition
    08/13/2014 21:14:56 [INFO] EVENTLOG (Error): NTDS Replication / DS RPC Client : 1963
    Internal event: The following local directory service received an exception from a remote procedure call (RPC) connection. Extensive RPC information was requested. This is intermediate information and might not contain a possible cause.
    Process ID: 
    488
    Reported error information:
    Error value: 
    Access is denied. (5)
    directory service: 
    gptsserver1.gpts.biz
    Extensive error information:
    Error value: 
    Access is denied. 5
    directory service: 
    gptsserver2
    Additional Data
    Internal ID: 
    5000dfc
    08/13/2014 21:14:56 [INFO] EVENTLOG (Error): NTDS Replication / DS RPC Client : 1961
    Internal event: This log entry is a continuation from the preceding extended error information entry on the following error and directory service.
    Extended information:
    Error value: 
    Access is denied. (5)
    directory service: 
    gptsserver2
    Supplemental information:
    Detection location: 
    1461
    Generating component: 
    RPC Runtime
    Time at directory service: 
    2014-08-14 04:14:56
    Additional Data
    Error value: 
    Access is denied. (5)
    08/13/2014 21:14:56 [INFO] EVENTLOG (Error): NTDS Replication / DS RPC Client : 2839
    Internal event: This log entry is a continuation from the preceding extended error information entry.
    Extended information:
    Extended Error Parameters: 
    0
    Parameter 1: 
    (NULL)
    Parameter 2: 
    (NULL)
    Parameter 3: 
    (NULL)
    Parameter 4: 
    (NULL)
    Parameter 5: 
    (null)
    Parameter 6: 
    (null)
    Parameter 7: 
    (null)
    08/13/2014 21:14:56 [INFO] EVENTLOG (Error): NTDS Replication / DS RPC Client : 1962
    Internal event: The local directory service received an exception from a remote procedure call (RPC) connection. Extended error information is not available.
    directory service: 
    gptsserver1.gpts.biz
    Additional Data
    Error value: 
    Access is denied. (5)
    08/13/2014 21:14:56 [INFO] EVENTLOG (Error): NTDS Replication / Setup : 1125
    The Active Directory Domain Services Installation Wizard (Dcpromo) was unable to establish connection with the following domain controller.
    Domain controller:
    gptsserver1.gpts.biz
    Additional Data
    Error value:
    5 Access is denied.
    08/13/2014 21:15:04 [INFO] EVENTLOG (Error): NTDS Replication / DS RPC Client : 1963
    Internal event: The following local directory service received an exception from a remote procedure call (RPC) connection. Extensive RPC information was requested. This is intermediate information and might not contain a possible cause.
    Process ID: 
    488
    Reported error information:
    Error value: 
    Access is denied. (5)
    directory service: 
    gptsserver1.gpts.biz
    Extensive error information:
    Error value: 
    Access is denied. 5
    directory service: 
    gptsserver2
    Additional Data
    Internal ID: 
    5000dfc
    08/13/2014 21:15:04 [INFO] EVENTLOG (Error): NTDS Replication / DS RPC Client : 1961
    Internal event: This log entry is a continuation from the preceding extended error information entry on the following error and directory service.
    Extended information:
    Error value: 
    Access is denied. (5)
    directory service: 
    gptsserver2
    Supplemental information:
    Detection location: 
    1461
    Generating component: 
    RPC Runtime
    Time at directory service: 
    2014-08-14 04:15:04
    Additional Data
    Error value: 
    Access is denied. (5)
    08/13/2014 21:15:04 [INFO] EVENTLOG (Error): NTDS Replication / DS RPC Client : 2839
    Internal event: This log entry is a continuation from the preceding extended error information entry.
    Extended information:
    Extended Error Parameters: 
    0
    Parameter 1: 
    (NULL)
    Parameter 2: 
    (NULL)
    Parameter 3: 
    (NULL)
    Parameter 4: 
    (NULL)
    Parameter 5: 
    (null)
    Parameter 6: 
    (null)
    Parameter 7: 
    (null)
    08/13/2014 21:15:04 [INFO] EVENTLOG (Error): NTDS Replication / DS RPC Client : 1962
    Internal event: The local directory service received an exception from a remote procedure call (RPC) connection. Extended error information is not available.
    directory service: 
    gptsserver1.gpts.biz
    Additional Data
    Error value: 
    Access is denied. (5)
    08/13/2014 21:15:04 [INFO] EVENTLOG (Error): NTDS Replication / Setup : 1125
    The Active Directory Domain Services Installation Wizard (Dcpromo) was unable to establish connection with the following domain controller.
    Domain controller:
    gptsserver1.gpts.biz
    Additional Data
    Error value:
    5 Access is denied.
    08/13/2014 21:15:20 [INFO] EVENTLOG (Error): NTDS Replication / DS RPC Client : 1963
    Internal event: The following local directory service received an exception from a remote procedure call (RPC) connection. Extensive RPC information was requested. This is intermediate information and might not contain a possible cause.
    Process ID: 
    488
    Reported error information:
    Error value: 
    Access is denied. (5)
    directory service: 
    gptsserver1.gpts.biz
    Extensive error information:
    Error value: 
    Access is denied. 5
    directory service: 
    gptsserver2
    Additional Data
    Internal ID: 
    5000dfc
    08/13/2014 21:15:20 [INFO] EVENTLOG (Error): NTDS Replication / DS RPC Client : 1961
    Internal event: This log entry is a continuation from the preceding extended error information entry on the following error and directory service.
    Extended information:
    Error value: 
    Access is denied. (5)
    directory service: 
    gptsserver2
    Supplemental information:
    Detection location: 
    1461
    Generating component: 
    RPC Runtime
    Time at directory service: 
    2014-08-14 04:15:20
    Additional Data
    Error value: 
    Access is denied. (5)
    08/13/2014 21:15:20 [INFO] EVENTLOG (Error): NTDS Replication / DS RPC Client : 2839
    Internal event: This log entry is a continuation from the preceding extended error information entry.
    Extended information:
    Extended Error Parameters: 
    0
    Parameter 1: 
    (NULL)
    Parameter 2: 
    (NULL)
    Parameter 3: 
    (NULL)
    Parameter 4: 
    (NULL)
    Parameter 5: 
    (null)
    Parameter 6: 
    (null)
    Parameter 7: 
    (null)
    08/13/2014 21:15:20 [INFO] EVENTLOG (Error): NTDS Replication / DS RPC Client : 1962
    Internal event: The local directory service received an exception from a remote procedure call (RPC) connection. Extended error information is not available.
    directory service: 
    gptsserver1.gpts.biz
    Additional Data
    Error value: 
    Access is denied. (5)
    08/13/2014 21:15:20 [INFO] EVENTLOG (Error): NTDS Replication / Setup : 1125
    The Active Directory Domain Services Installation Wizard (Dcpromo) was unable to establish connection with the following domain controller.
    Domain controller:
    gptsserver1.gpts.biz
    Additional Data
    Error value:
    5 Access is denied.
    08/13/2014 21:15:52 [INFO] EVENTLOG (Error): NTDS Replication / DS RPC Client : 1963
    Internal event: The following local directory service received an exception from a remote procedure call (RPC) connection. Extensive RPC information was requested. This is intermediate information and might not contain a possible cause.
    Process ID: 
    488
    Reported error information:
    Error value: 
    Access is denied. (5)
    directory service: 
    gptsserver1.gpts.biz
    Extensive error information:
    Error value: 
    Access is denied. 5
    directory service: 
    gptsserver2
    Additional Data
    Internal ID: 
    5000dfc
    08/13/2014 21:15:52 [INFO] EVENTLOG (Error): NTDS Replication / DS RPC Client : 1961
    Internal event: This log entry is a continuation from the preceding extended error information entry on the following error and directory service.
    Extended information:
    Error value: 
    Access is denied. (5)
    directory service: 
    gptsserver2
    Supplemental information:
    Detection location: 
    1461
    Generating component: 
    RPC Runtime
    Time at directory service: 
    2014-08-14 04:15:52
    Additional Data
    Error value: 
    Access is denied. (5)
    08/13/2014 21:15:52 [INFO] EVENTLOG (Error): NTDS Replication / DS RPC Client : 2839
    Internal event: This log entry is a continuation from the preceding extended error information entry.
    Extended information:
    Extended Error Parameters: 
    0
    Parameter 1: 
    (NULL)
    Parameter 2: 
    (NULL)
    Parameter 3: 
    (NULL)
    Parameter 4: 
    (NULL)
    Parameter 5: 
    (null)
    Parameter 6: 
    (null)
    Parameter 7: 
    (null)
    08/13/2014 21:15:52 [INFO] EVENTLOG (Error): NTDS Replication / DS RPC Client : 1962
    Internal event: The local directory service received an exception from a remote procedure call (RPC) connection. Extended error information is not available.
    directory service: 
    gptsserver1.gpts.biz
    Additional Data
    Error value: 
    Access is denied. (5)
    08/13/2014 21:15:52 [INFO] EVENTLOG (Error): NTDS Replication / Setup : 1125
    The Active Directory Domain Services Installation Wizard (Dcpromo) was unable to establish connection with the following domain controller.
    Domain controller:
    gptsserver1.gpts.biz
    Additional Data
    Error value:
    5 Access is denied.
    08/13/2014 21:16:56 [INFO] EVENTLOG (Error): NTDS Replication / DS RPC Client : 1963
    Internal event: The following local directory service received an exception from a remote procedure call (RPC) connection. Extensive RPC information was requested. This is intermediate information and might not contain a possible cause.
    Process ID: 
    488
    Reported error information:
    Error value: 
    Access is denied. (5)
    directory service: 
    gptsserver1.gpts.biz
    Extensive error information:
    Error value: 
    Access is denied. 5
    directory service: 
    gptsserver2
    Additional Data
    Internal ID: 
    5000dfc
    08/13/2014 21:16:56 [INFO] EVENTLOG (Error): NTDS Replication / DS RPC Client : 1961
    Internal event: This log entry is a continuation from the preceding extended error information entry on the following error and directory service.
    Extended information:
    Error value: 
    Access is denied. (5)
    directory service: 
    gptsserver2
    Supplemental information:
    Detection location: 
    1461
    Generating component: 
    RPC Runtime
    Time at directory service: 
    2014-08-14 04:16:56
    Additional Data
    Error value: 
    Access is denied. (5)
    08/13/2014 21:16:56 [INFO] EVENTLOG (Error): NTDS Replication / DS RPC Client : 2839
    Internal event: This log entry is a continuation from the preceding extended error information entry.
    Extended information:
    Extended Error Parameters: 
    0
    Parameter 1: 
    (NULL)
    Parameter 2: 
    (NULL)
    Parameter 3: 
    (NULL)
    Parameter 4: 
    (NULL)
    Parameter 5: 
    (null)
    Parameter 6: 
    (null)
    Parameter 7: 
    (null)
    08/13/2014 21:16:56 [INFO] EVENTLOG (Error): NTDS Replication / DS RPC Client : 1962
    Internal event: The local directory service received an exception from a remote procedure call (RPC) connection. Extended error information is not available.
    directory service: 
    gptsserver1.gpts.biz
    Additional Data
    Error value: 
    Access is denied. (5)
    08/13/2014 21:16:56 [INFO] EVENTLOG (Error): NTDS Replication / Setup : 1125
    The Active Directory Domain Services Installation Wizard (Dcpromo) was unable to establish connection with the following domain controller.
    Domain controller:
    gptsserver1.gpts.biz
    Additional Data
    Error value:
    5 Access is denied.
    John Grace

  • Exchange server-Removing a Domain Controller from the forest

    Hi Guys,
    I need some help on removing a faulty domain controller from the AD forest. Here is the scenario:
    1. The FSMO roles have been seized to a new domain controller already.
    2. The old one is non-functional and is down for ever.
    I know the steps would be doing a meta-data cleanup And then remove some of the DNS entries related to the old server. But the real issue is:
    > I have Exchange 2013 running in one of the machines configured in the Forest, which was migrated from the old Domain controller. I then set Exchange listening to the new domain controller.
    So, my doubt is, if I delete the old domain controller and do a metadata cleanup, would it have any effect on the exchange server? The Exchange machine acts as an additional domain controller as well. Its a production environment and any
    change that affects Exchange would cause a big loss. Looking forward for your valuable suggestions..
    Regards,
    Nash

    Hi Ed,
    I don't have issues with the AD on the Exchange server. Eventhough it is configured as an AD, Exchange is pointed to the main working domain controller, which is a different machine. I just want to remove the traces of an old domain controller from which
    I transferred the FSMO roles to the new domain controller. The old  domain controller is completely down and hence I can't do a conventional 'dcpromo' on it. So just planning to do a 'metadata clean up' for removing the non-working DC from the forest. 
    So, In essence, I just want to know that, if I do a metadata cleanup, would it affect the Exchange server in any way?
    Regards,
    Nash

  • Domain controller environment do we required CAL's license ?

    Domain controller environment do we required CAL's license?
    Do I need any licensing to connect workstations to a domain?
     Where we have License for the AD Server (2008 /2012 )  and there License of  client os (windows 7/ windows 8 ) still we required the CAL's license DC ?
    I have a server running Windows Server 2012. I want to turn this into a domain controller. In order to connect my workstations to my server

    Hi,
    on this link:
    http://www.microsoft.com/licensing/about-licensing/windowsserver2012-r2.aspx#tab=4 we have the following:
    Client Access Licenses (CALs) are required for each user or device accessed. The Windows Server 2012 related CALs provide entitlement to access and use Windows 2012 R2 functionality.
    on th emultiplexing link:
    http://www.microsoft.com/licensing/about-licensing/briefs/multiplexing.aspx you can download th ePDF data who is mentioned that:
    "Multiplexing does not reduce the number of Microsoft licenses required. Users are required to have the appropriate licenses, regardless of their
    direct or indirect connection to the product. Any user or device that accesses the server, files, or data or content provided by the server that is made available through an automated process requires a CAL."
    thanks
    diramoh

  • ISSUE: "This domain controller must register a DNS SRV resource record, which is required for replication to function correctly"

    so we currently have three domain controllers set up, two of them on 2012r2 and one of them on 2008r2. prior to any of these domain controllers being added to the domain there was only one, running on 2003r2. the 2003r2 server was up and running when the
    first 2012r2 was added and that's when running 'dcdiag /e /c /v' would yield an issue with "_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local" in the DNS portion of the diagnostics, specifically:
    TEST: Records registration (RReg)
    Network Adapter [00000010] Microsoft Hyper-V Network Adapter:
    Error:
    Missing SRV record at DNS server 192.168.22.4:
    _ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
    after adding the second 2012r2 to the domain, this issue is still there... adding the 2008r2 server to the domain and running BPA it gives the following:
    Title:
    This domain controller must register a DNS SRV resource record, which is required for replication to function correctly
    Severity:
    Error
    Date:
    7/3/2014 11:24:48 AM
    Category:
    Configuration
    Issue:
    The "DcByGuid" DNS service (SRV) resource record that advertises this server as an available domain controller in the domain and ensures correct replication is not registered. All domain controllers (but not RODCs) in the domain must register this record.
    Impact:
    Other member computers and domain controllers in the domain or forest will not be able to locate this domain controller. This domain controller will not be able to provide a full suite of services.
    Resolution:
    Ensure that "DcByGuid" is not configured in the "DnsAvoidRegisteredRecords" list, either through Group Policy or through the registry. Restart the Netlogon service. Verify that the DNS service (SRV) resource record "_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local", pointing to the local domain controller "CM-DC4-NY01.cmedia.local", is registered in DNS.
    More information about this best practice and detailed resolution procedures: http://go.microsoft.com/fwlink/?LinkId=126968
    I've tried scanning and then re-scanning every single entry in DNS Manager and do not see any reference to this specific GUID mentioned, nor do I see any other domain controllers referenced that should not be in there. The two 2012r2 and the 2008r2 domain
    controllers are the only ones listed in DNS Manager... the 2003r2 mentioned earlier failed and was removed.

    Just to chime in, I noticed that you said you have one 2008 R2 DC, and two 2012 DCs.
    I also noticed in the ipconfig /all that all DCs are pointint to themselves for DNS. We usually like to see them point to a partner, then itslelf as the second entry, w hether loopback or by its own IP.
    Based on that, what I suggest to level the playing field by choosing the WIndows 2008 R2 DC as the first DNS on all DCs and only administer DNS using that DC. The reason I chose that is because of the least common denominator is what we rather use so we
    don't invoke any new features in the newer 2012 DNS console that 2008 R2 may not understand.  After that's done, on each DC run (and you can use a PowerShell window to run this):
    Rename the system32\config\netlogon.dns and netlogon.dnb files by suffixing ".old" to the file.
    ipconfig /registerdns
    net stop netlogon
    net start netlogon
    Then re-run the dcdiag /e /c /v.
    Post your results, please.
    Ace Fekay
    MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
    This posting is provided AS-IS with no warranties or guarantees and confers no rights.
    I thought the DNS entries were supposed to be the other way around? point to themselves first and a partner as secondary? regardless, as requested, I've changed it to what you've prescribed where they point to the 2008r2 server as the primary with themselves
    as the secondary. I've also followed the steps to what seems like refreshing the DNS? on each of the DCs. Here's the output from dcdiag /e /c /v
    Directory Server Diagnosis
    Performing initial setup:
    Trying to find home server...
    * Verifying that the local machine CM-DC1-NY01, is a Directory Server.
    Home Server = CM-DC1-NY01
    * Connecting to directory service on server CM-DC1-NY01.
    * Identified AD Forest.
    Collecting AD specific global data
    * Collecting site info.
    Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=cmedia,DC=local,LDAP_SCOPE_SUBTREE,(objectCategory
    =ntDSSiteSettings),.......
    The previous call succeeded
    Iterating through the sites
    Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=cmedia
    ,DC=local
    Getting ISTG and options for the site
    * Identifying all servers.
    Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=cmedia,DC=local,LDAP_SCOPE_SUBTREE,(objectClass=nt
    DSDsa),.......
    The previous call succeeded....
    The previous call succeeded
    Iterating through the list of servers
    Getting information for the server CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites
    ,CN=Configuration,DC=cmedia,DC=local
    objectGuid obtained
    InvocationID obtained
    dnsHostname obtained
    site info obtained
    All the info for the server collected
    Getting information for the server CN=NTDS Settings,CN=CM-DC3-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites
    ,CN=Configuration,DC=cmedia,DC=local
    objectGuid obtained
    InvocationID obtained
    dnsHostname obtained
    site info obtained
    All the info for the server collected
    Getting information for the server CN=NTDS Settings,CN=CM-DC4-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites
    ,CN=Configuration,DC=cmedia,DC=local
    objectGuid obtained
    InvocationID obtained
    dnsHostname obtained
    site info obtained
    All the info for the server collected
    * Identifying all NC cross-refs.
    * Found 3 DC(s). Testing 3 of them.
    Done gathering initial info.
    Doing initial required tests
    Testing server: Default-First-Site-Name\CM-DC1-NY01
    Starting test: Connectivity
    * Active Directory LDAP Services Check
    Determining IP4 connectivity
    * Active Directory RPC Services Check
    ......................... CM-DC1-NY01 passed test Connectivity
    Testing server: Default-First-Site-Name\CM-DC3-NY01
    Starting test: Connectivity
    * Active Directory LDAP Services Check
    Determining IP4 connectivity
    * Active Directory RPC Services Check
    ......................... CM-DC3-NY01 passed test Connectivity
    Testing server: Default-First-Site-Name\CM-DC4-NY01
    Starting test: Connectivity
    * Active Directory LDAP Services Check
    Determining IP4 connectivity
    * Active Directory RPC Services Check
    ......................... CM-DC4-NY01 passed test Connectivity
    Doing primary tests
    Testing server: Default-First-Site-Name\CM-DC1-NY01
    Starting test: Advertising
    The DC CM-DC1-NY01 is advertising itself as a DC and having a DS.
    The DC CM-DC1-NY01 is advertising as an LDAP server
    The DC CM-DC1-NY01 is advertising as having a writeable directory
    The DC CM-DC1-NY01 is advertising as a Key Distribution Center
    The DC CM-DC1-NY01 is advertising as a time server
    The DS CM-DC1-NY01 is advertising as a GC.
    ......................... CM-DC1-NY01 passed test Advertising
    Starting test: CheckSecurityError
    * Dr Auth: Beginning security errors check!
    Found KDC CM-DC1-NY01 for domain cmedia.local in site Default-First-Site-Name
    Checking machine account for DC CM-DC1-NY01 on DC CM-DC1-NY01.
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local
    * SPN found :LDAP/CM-DC1-NY01
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local/cmedia
    * SPN found :LDAP/a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/a29d12f1-2869-44bf-8e43-adf7ddf33865/cmedia.local
    * SPN found :HOST/CM-DC1-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC1-NY01.cmedia.local
    * SPN found :HOST/CM-DC1-NY01
    * SPN found :GC/CM-DC1-NY01.cmedia.local/cmedia.local
    [CM-DC1-NY01] No security related replication errors were found on this DC! To target the connection to a
    specific source DC use /ReplSource:<DC>.
    ......................... CM-DC1-NY01 passed test CheckSecurityError
    Starting test: CutoffServers
    * Configuration Topology Aliveness Check
    * Analyzing the alive system replication topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC1-NY01 passed test CutoffServers
    Starting test: FrsEvent
    * The File Replication Service Event log test
    ......................... CM-DC1-NY01 passed test FrsEvent
    Starting test: DFSREvent
    The DFS Replication Event Log.
    Skip the test because the server is running FRS.
    ......................... CM-DC1-NY01 passed test DFSREvent
    Starting test: SysVolCheck
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC1-NY01 passed test SysVolCheck
    Starting test: FrsSysVol
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC1-NY01 passed test FrsSysVol
    Starting test: KccEvent
    * The KCC Event log test
    Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
    ......................... CM-DC1-NY01 passed test KccEvent
    Starting test: KnowsOfRoleHolders
    Role Schema Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role Domain Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role PDC Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Rid Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Infrastructure Update Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN
    =Sites,CN=Configuration,DC=cmedia,DC=local
    ......................... CM-DC1-NY01 passed test KnowsOfRoleHolders
    Starting test: MachineAccount
    Checking machine account for DC CM-DC1-NY01 on DC CM-DC1-NY01.
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local
    * SPN found :LDAP/CM-DC1-NY01
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local/cmedia
    * SPN found :LDAP/a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/a29d12f1-2869-44bf-8e43-adf7ddf33865/cmedia.local
    * SPN found :HOST/CM-DC1-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC1-NY01.cmedia.local
    * SPN found :HOST/CM-DC1-NY01
    * SPN found :HOST/CM-DC1-NY01.cmedia.local/cmedia
    * SPN found :GC/CM-DC1-NY01.cmedia.local/cmedia.local
    ......................... CM-DC1-NY01 passed test MachineAccount
    Starting test: NCSecDesc
    * Security Permissions check for all NC's on DC CM-DC1-NY01.
    The forest is not ready for RODC. Will skip checking ERODC ACEs.
    * Security Permissions Check for
    DC=ForestDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    DC=DomainDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    (Schema,Version 3)
    * Security Permissions Check for
    CN=Configuration,DC=cmedia,DC=local
    (Configuration,Version 3)
    * Security Permissions Check for
    DC=cmedia,DC=local
    (Domain,Version 3)
    ......................... CM-DC1-NY01 passed test NCSecDesc
    Starting test: NetLogons
    * Network Logons Privileges Check
    Verified share \\CM-DC1-NY01\netlogon
    Verified share \\CM-DC1-NY01\sysvol
    ......................... CM-DC1-NY01 passed test NetLogons
    Starting test: ObjectsReplicated
    CM-DC1-NY01 is in domain DC=cmedia,DC=local
    Checking for CN=CM-DC1-NY01,OU=Domain Controllers,DC=cmedia,DC=local in domain DC=cmedia,DC=local o
    n 3 servers
    Object is up-to-date on all servers.
    Checking for CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuratio
    n,DC=cmedia,DC=local in domain CN=Configuration,DC=cmedia,DC=local on 3 servers
    Object is up-to-date on all servers.
    ......................... CM-DC1-NY01 passed test ObjectsReplicated
    Starting test: OutboundSecureChannels
    * The Outbound Secure Channels test
    ** Did not run Outbound Secure Channels test because /testdomain: was not entered
    ......................... CM-DC1-NY01 passed test OutboundSecureChannels
    Starting test: Replications
    * Replications Check
    * Replication Latency Check
    DC=ForestDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    DC=DomainDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    CN=Configuration,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    ......................... CM-DC1-NY01 passed test Replications
    Starting test: RidManager
    * Available RID Pool for the Domain is 16109 to 1073741823
    * CM-DC1-NY01.cmedia.local is the RID Master
    * DsBind with RID Master was successful
    * rIDAllocationPool is 4609 to 5108
    * rIDPreviousAllocationPool is 4609 to 5108
    * rIDNextRID: 4629
    ......................... CM-DC1-NY01 passed test RidManager
    Starting test: Services
    * Checking Service: EventSystem
    * Checking Service: RpcSs
    * Checking Service: NTDS
    * Checking Service: DnsCache
    * Checking Service: NtFrs
    * Checking Service: IsmServ
    * Checking Service: kdc
    * Checking Service: SamSs
    * Checking Service: LanmanServer
    * Checking Service: LanmanWorkstation
    * Checking Service: w32time
    * Checking Service: NETLOGON
    ......................... CM-DC1-NY01 passed test Services
    Starting test: SystemLog
    * The System Event log test
    A warning event occurred. EventID: 0x0000002F
    Time Generated: 07/08/2014 13:19:14
    Event String:
    Time Provider NtpClient: No valid response has been received from manually configured peer 0.ca.pool.ntp.org
    after 8 attempts to contact it. This peer will be discarded as a time source and NtpClient will attempt to discover a n
    ew peer with this DNS name. The error was: The peer is unreachable.
    Found no errors in "System" Event log in the last 60 minutes.
    ......................... CM-DC1-NY01 passed test SystemLog
    Starting test: Topology
    * Configuration Topology Integrity Check
    * Analyzing the connection topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC1-NY01 passed test Topology
    Starting test: VerifyEnterpriseReferences
    ......................... CM-DC1-NY01 passed test VerifyEnterpriseReferences
    Starting test: VerifyReferences
    The system object reference (serverReference) CN=CM-DC1-NY01,OU=Domain Controllers,DC=cmedia,DC=local
    and backlink on
    CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=cmedia,DC=local are
    correct.
    The system object reference (serverReferenceBL)
    CN=CM-DC1-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on
    CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=chiefmed
    ia,DC=local
    are correct.
    The system object reference (frsComputerReferenceBL)
    CN=CM-DC1-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on CN=CM-DC1-NY01,OU=Domain Controllers,DC=cmedia,DC=local are correct.
    ......................... CM-DC1-NY01 passed test VerifyReferences
    Starting test: VerifyReplicas
    ......................... CM-DC1-NY01 passed test VerifyReplicas
    Testing server: Default-First-Site-Name\CM-DC3-NY01
    Starting test: Advertising
    The DC CM-DC3-NY01 is advertising itself as a DC and having a DS.
    The DC CM-DC3-NY01 is advertising as an LDAP server
    The DC CM-DC3-NY01 is advertising as having a writeable directory
    The DC CM-DC3-NY01 is advertising as a Key Distribution Center
    The DC CM-DC3-NY01 is advertising as a time server
    The DS CM-DC3-NY01 is advertising as a GC.
    ......................... CM-DC3-NY01 passed test Advertising
    Starting test: CheckSecurityError
    * Dr Auth: Beginning security errors check!
    Found KDC CM-DC1-NY01 for domain cmedia.local in site Default-First-Site-Name
    Checking machine account for DC CM-DC3-NY01 on DC CM-DC1-NY01.
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local
    * SPN found :LDAP/CM-DC3-NY01
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local/cmedia
    * SPN found :LDAP/5e9d1971-39ca-484c-922d-411c2364c96e._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/5e9d1971-39ca-484c-922d-411c2364c96e/cmedia.local
    * SPN found :HOST/CM-DC3-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC3-NY01.cmedia.local
    * SPN found :HOST/CM-DC3-NY01
    * SPN found :HOST/CM-DC3-NY01.cmedia.local/cmedia
    * SPN found :GC/CM-DC3-NY01.cmedia.local/cmedia.local
    Checking for CN=CM-DC3-NY01,OU=Domain Controllers,DC=cmedia,DC=local in domain DC=cmedia,DC=local o
    n 2 servers
    Object is up-to-date on all servers.
    [CM-DC3-NY01] No security related replication errors were found on this DC! To target the connection to a
    specific source DC use /ReplSource:<DC>.
    ......................... CM-DC3-NY01 passed test CheckSecurityError
    Starting test: CutoffServers
    * Configuration Topology Aliveness Check
    * Analyzing the alive system replication topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC3-NY01 passed test CutoffServers
    Starting test: FrsEvent
    * The File Replication Service Event log test
    ......................... CM-DC3-NY01 passed test FrsEvent
    Starting test: DFSREvent
    The DFS Replication Event Log.
    Skip the test because the server is running FRS.
    ......................... CM-DC3-NY01 passed test DFSREvent
    Starting test: SysVolCheck
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC3-NY01 passed test SysVolCheck
    Starting test: FrsSysVol
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC3-NY01 passed test FrsSysVol
    Starting test: KccEvent
    * The KCC Event log test
    Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
    ......................... CM-DC3-NY01 passed test KccEvent
    Starting test: KnowsOfRoleHolders
    Role Schema Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role Domain Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role PDC Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Rid Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Infrastructure Update Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN
    =Sites,CN=Configuration,DC=cmedia,DC=local
    ......................... CM-DC3-NY01 passed test KnowsOfRoleHolders
    Starting test: MachineAccount
    Checking machine account for DC CM-DC3-NY01 on DC CM-DC3-NY01.
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local
    * SPN found :LDAP/CM-DC3-NY01
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local/cmedia
    * SPN found :LDAP/5e9d1971-39ca-484c-922d-411c2364c96e._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/5e9d1971-39ca-484c-922d-411c2364c96e/cmedia.local
    * SPN found :HOST/CM-DC3-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC3-NY01.cmedia.local
    * SPN found :HOST/CM-DC3-NY01
    * SPN found :HOST/CM-DC3-NY01.cmedia.local/cmedia
    * SPN found :GC/CM-DC3-NY01.cmedia.local/cmedia.local
    ......................... CM-DC3-NY01 passed test MachineAccount
    Starting test: NCSecDesc
    * Security Permissions check for all NC's on DC CM-DC3-NY01.
    The forest is not ready for RODC. Will skip checking ERODC ACEs.
    * Security Permissions Check for
    DC=ForestDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    DC=DomainDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    (Schema,Version 3)
    * Security Permissions Check for
    CN=Configuration,DC=cmedia,DC=local
    (Configuration,Version 3)
    * Security Permissions Check for
    DC=cmedia,DC=local
    (Domain,Version 3)
    ......................... CM-DC3-NY01 passed test NCSecDesc
    Starting test: NetLogons
    * Network Logons Privileges Check
    Verified share \\CM-DC3-NY01\netlogon
    Verified share \\CM-DC3-NY01\sysvol
    ......................... CM-DC3-NY01 passed test NetLogons
    Starting test: ObjectsReplicated
    CM-DC3-NY01 is in domain DC=cmedia,DC=local
    Checking for CN=CM-DC3-NY01,OU=Domain Controllers,DC=cmedia,DC=local in domain DC=cmedia,DC=local o
    n 3 servers
    Object is up-to-date on all servers.
    Checking for CN=NTDS Settings,CN=CM-DC3-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuratio
    n,DC=cmedia,DC=local in domain CN=Configuration,DC=cmedia,DC=local on 3 servers
    Object is up-to-date on all servers.
    ......................... CM-DC3-NY01 passed test ObjectsReplicated
    Starting test: OutboundSecureChannels
    * The Outbound Secure Channels test
    ** Did not run Outbound Secure Channels test because /testdomain: was not entered
    ......................... CM-DC3-NY01 passed test OutboundSecureChannels
    Starting test: Replications
    * Replications Check
    * Replication Latency Check
    DC=ForestDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    DC=DomainDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    CN=Configuration,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    ......................... CM-DC3-NY01 passed test Replications
    Starting test: RidManager
    * Available RID Pool for the Domain is 16109 to 1073741823
    * CM-DC1-NY01.cmedia.local is the RID Master
    * DsBind with RID Master was successful
    * rIDAllocationPool is 15109 to 15608
    * rIDPreviousAllocationPool is 15109 to 15608
    * rIDNextRID: 15110
    ......................... CM-DC3-NY01 passed test RidManager
    Starting test: Services
    * Checking Service: EventSystem
    * Checking Service: RpcSs
    * Checking Service: NTDS
    * Checking Service: DnsCache
    * Checking Service: NtFrs
    * Checking Service: IsmServ
    * Checking Service: kdc
    * Checking Service: SamSs
    * Checking Service: LanmanServer
    * Checking Service: LanmanWorkstation
    * Checking Service: w32time
    * Checking Service: NETLOGON
    ......................... CM-DC3-NY01 passed test Services
    Starting test: SystemLog
    * The System Event log test
    Found no errors in "System" Event log in the last 60 minutes.
    ......................... CM-DC3-NY01 passed test SystemLog
    Starting test: Topology
    * Configuration Topology Integrity Check
    * Analyzing the connection topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC3-NY01 passed test Topology
    Starting test: VerifyEnterpriseReferences
    ......................... CM-DC3-NY01 passed test VerifyEnterpriseReferences
    Starting test: VerifyReferences
    The system object reference (serverReference) CN=CM-DC3-NY01,OU=Domain Controllers,DC=cmedia,DC=local
    and backlink on
    CN=CM-DC3-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=cmedia,DC=local are
    correct.
    The system object reference (serverReferenceBL)
    CN=CM-DC3-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on
    CN=NTDS Settings,CN=CM-DC3-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=chiefmed
    ia,DC=local
    are correct.
    The system object reference (frsComputerReferenceBL)
    CN=CM-DC3-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on CN=CM-DC3-NY01,OU=Domain Controllers,DC=cmedia,DC=local are correct.
    ......................... CM-DC3-NY01 passed test VerifyReferences
    Starting test: VerifyReplicas
    ......................... CM-DC3-NY01 passed test VerifyReplicas
    Testing server: Default-First-Site-Name\CM-DC4-NY01
    Starting test: Advertising
    The DC CM-DC4-NY01 is advertising itself as a DC and having a DS.
    The DC CM-DC4-NY01 is advertising as an LDAP server
    The DC CM-DC4-NY01 is advertising as having a writeable directory
    The DC CM-DC4-NY01 is advertising as a Key Distribution Center
    The DC CM-DC4-NY01 is advertising as a time server
    The DS CM-DC4-NY01 is advertising as a GC.
    ......................... CM-DC4-NY01 passed test Advertising
    Starting test: CheckSecurityError
    * Dr Auth: Beginning security errors check!
    Found KDC CM-DC1-NY01 for domain cmedia.local in site Default-First-Site-Name
    Checking machine account for DC CM-DC4-NY01 on DC CM-DC1-NY01.
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local
    * SPN found :LDAP/CM-DC4-NY01
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local/cmedia
    * SPN found :LDAP/37830012-1f10-43c9-a0ff-2a0e8a912187._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/37830012-1f10-43c9-a0ff-2a0e8a912187/cmedia.local
    * SPN found :HOST/CM-DC4-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC4-NY01.cmedia.local
    * SPN found :HOST/CM-DC4-NY01
    * SPN found :HOST/CM-DC4-NY01.cmedia.local/cmedia
    * SPN found :GC/CM-DC4-NY01.cmedia.local/cmedia.local
    Checking for CN=CM-DC4-NY01,OU=Domain Controllers,DC=cmedia,DC=local in domain DC=cmedia,DC=local o
    n 2 servers
    Object is up-to-date on all servers.
    [CM-DC4-NY01] No security related replication errors were found on this DC! To target the connection to a
    specific source DC use /ReplSource:<DC>.
    ......................... CM-DC4-NY01 passed test CheckSecurityError
    Starting test: CutoffServers
    * Configuration Topology Aliveness Check
    * Analyzing the alive system replication topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC4-NY01 passed test CutoffServers
    Starting test: FrsEvent
    * The File Replication Service Event log test
    ......................... CM-DC4-NY01 passed test FrsEvent
    Starting test: DFSREvent
    The DFS Replication Event Log.
    Skip the test because the server is running FRS.
    ......................... CM-DC4-NY01 passed test DFSREvent
    Starting test: SysVolCheck
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC4-NY01 passed test SysVolCheck
    Starting test: FrsSysVol
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC4-NY01 passed test FrsSysVol
    Starting test: KccEvent
    * The KCC Event log test
    Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
    ......................... CM-DC4-NY01 passed test KccEvent
    Starting test: KnowsOfRoleHolders
    Role Schema Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role Domain Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role PDC Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Rid Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Infrastructure Update Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN
    =Sites,CN=Configuration,DC=cmedia,DC=local
    ......................... CM-DC4-NY01 passed test KnowsOfRoleHolders
    Starting test: MachineAccount
    Checking machine account for DC CM-DC4-NY01 on DC CM-DC4-NY01.
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local
    * SPN found :LDAP/CM-DC4-NY01
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local/cmedia
    * SPN found :LDAP/37830012-1f10-43c9-a0ff-2a0e8a912187._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/37830012-1f10-43c9-a0ff-2a0e8a912187/cmedia.local
    * SPN found :HOST/CM-DC4-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC4-NY01.cmedia.local
    * SPN found :HOST/CM-DC4-NY01
    * SPN found :HOST/CM-DC4-NY01.cmedia.local/cmedia
    * SPN found :GC/CM-DC4-NY01.cmedia.local/cmedia.local
    ......................... CM-DC4-NY01 passed test MachineAccount
    Starting test: NCSecDesc
    * Security Permissions check for all NC's on DC CM-DC4-NY01.
    The forest is not ready for RODC. Will skip checking ERODC ACEs.
    * Security Permissions Check for
    DC=ForestDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    DC=DomainDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    (Schema,Version 3)
    * Security Permissions Check for
    CN=Configuration,DC=cmedia,DC=local
    (Configuration,Version 3)
    * Security Permissions Check for
    DC=cmedia,DC=local
    (Domain,Version 3)
    ......................... CM-DC4-NY01 passed test NCSecDesc
    Starting test: NetLogons
    * Network Logons Privileges Check
    Verified share \\CM-DC4-NY01\netlogon
    Verified share \\CM-DC4-NY01\sysvol
    ......................... CM-DC4-NY01 passed test NetLogons
    Starting test: ObjectsReplicated
    CM-DC4-NY01 is in domain DC=cmedia,DC=local
    Checking for CN=CM-DC4-NY01,OU=Domain Controllers,DC=cmedia,DC=local in domain DC=cmedia,DC=local o
    n 3 servers
    Object is up-to-date on all servers.
    Checking for CN=NTDS Settings,CN=CM-DC4-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuratio
    n,DC=cmedia,DC=local in domain CN=Configuration,DC=cmedia,DC=local on 3 servers
    Object is up-to-date on all servers.
    ......................... CM-DC4-NY01 passed test ObjectsReplicated
    Starting test: OutboundSecureChannels
    * The Outbound Secure Channels test
    ** Did not run Outbound Secure Channels test because /testdomain: was not entered
    ......................... CM-DC4-NY01 passed test OutboundSecureChannels
    Starting test: Replications
    * Replications Check
    * Replication Latency Check
    DC=ForestDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    DC=DomainDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    CN=Configuration,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    ......................... CM-DC4-NY01 passed test Replications
    Starting test: RidManager
    * Available RID Pool for the Domain is 16109 to 1073741823
    * CM-DC1-NY01.cmedia.local is the RID Master
    * DsBind with RID Master was successful
    * rIDAllocationPool is 15609 to 16108
    * rIDPreviousAllocationPool is 15609 to 16108
    * rIDNextRID: 15609
    ......................... CM-DC4-NY01 passed test RidManager
    Starting test: Services
    * Checking Service: EventSystem
    * Checking Service: RpcSs
    * Checking Service: NTDS
    * Checking Service: DnsCache
    * Checking Service: NtFrs
    * Checking Service: IsmServ
    * Checking Service: kdc
    * Checking Service: SamSs
    * Checking Service: LanmanServer
    * Checking Service: LanmanWorkstation
    * Checking Service: w32time
    * Checking Service: NETLOGON
    ......................... CM-DC4-NY01 passed test Services
    Starting test: SystemLog
    * The System Event log test
    Found no errors in "System" Event log in the last 60 minutes.
    ......................... CM-DC4-NY01 passed test SystemLog
    Starting test: Topology
    * Configuration Topology Integrity Check
    * Analyzing the connection topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC4-NY01 passed test Topology
    Starting test: VerifyEnterpriseReferences
    ......................... CM-DC4-NY01 passed test VerifyEnterpriseReferences
    Starting test: VerifyReferences
    The system object reference (serverReference) CN=CM-DC4-NY01,OU=Domain Controllers,DC=cmedia,DC=local
    and backlink on
    CN=CM-DC4-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=cmedia,DC=local are
    correct.
    The system object reference (serverReferenceBL)
    CN=CM-DC4-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on
    CN=NTDS Settings,CN=CM-DC4-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=chiefmed
    ia,DC=local
    are correct.
    The system object reference (frsComputerReferenceBL)
    CN=CM-DC4-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on CN=CM-DC4-NY01,OU=Domain Controllers,DC=cmedia,DC=local are correct.
    ......................... CM-DC4-NY01 passed test VerifyReferences
    Starting test: VerifyReplicas
    ......................... CM-DC4-NY01 passed test VerifyReplicas

  • How to use DNS server for name resolution for items which don't exist in active directory domain controller DNS

    Dear Experts,
    In our office we have a domain controller call it 'Office.com', all computers and corporate servers e.g. exchange, antivirus etc. are member of this 'office.com', it is also having a DNS. All users in office have there preferred DNS set to the corporate
    DNS
    We are working for ministry and offering services to them from our data center so have many servers which are for ministry but they are in our data center. For all these servers we created another DNS server which contains all entries for these servers in
    forward and reverse lookup zones. In this DNS we also created a forward lookup zone for our corporate servers and zone name is 'office.com'
    What we are trying to have is name resolution of all servers which are listed in other DNS build in our office on Win 2008 R2 for ministry servers
    If the user change his preferred DNS to ministry DNS he can resolve the ministry server but then we can not control any thing through group policy since they are using other DNS and not the corporate DNS. 
    How this can be done ? like any group policy applied to corporate domain controller must take effect on users and in addition to this user must also be able to resolve server names in ministry project DNS
    Please assist ASAP.
    regards,

    Hello,
    ok so the GPO setting doesn't apply in any case.
    Clients machines use the first DNS server in the list of configured ones on the NIC. If that one is available search for additional DNS servers will stop.
    What i can not really understand is your description about the second DNS server. This should normally either another DC with AD integrated DNS, so everything is replicatedwithin AD replication or you use a secondary DNS on domain member server that pulls
    the informations from the Master.
    It sounds for me that you have configured a machine with DNS server role and created manually the zone with the same name as the domainand manually create there the required A records?
    Best regards
    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://msmvps.com/blogs/mweber/
    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

  • Login to Domain Controller which is not in network

    Scenario
    I've taken an online clone of one of my Virtual Window 2003 Enterprise Domain Contoller which doesn't hold any roles. Removed the Clone Domain Controller from Network & powered it on.
    Now I want to log into that Domain Controller using my Domain Admin credentials but it's not working.
    Is there a way to log in to that Domain Controller which is taken out of network USING DOMAIN ADMIN ID ?
    I can log in to Restore Mode but that's not what I'm looking for, I need to log in to that DC using my Domain Admin credentials while It's not in network.
    This is for lab purpose.

    Hi Yankee,
    Have you cached credentials on the Domain Controller before you cloned one?
    I just tested that if I cache credentials, users are able to log on when domain controllers are offline.
    If not, you can try to clone another after cached credentials then test again, please note that do not take the cloned DC online, which will lead USN rollback.
    More information for you:
    Cached domain logon information
    http://support.microsoft.com/kb/172931/en-us
    Running Domain Controllers in Hyper-V
    http://technet.microsoft.com/en-us/library/virtual_active_directory_domain_controller_virtualization_hyperv(v=WS.10).aspx
    Best Regards,
    Amy

  • Question about adding Windows 2012 R2 Domain Controller, into a native Windows 2008 R2 single forest domain

    I current have a two server domain, both Windows 2008 R2 and fully updated.   The two servers are on subnet 10.0.1.0 /24
    - Windows 2008 R2 Server A: 10.0.1.1 (DC, GC, FSMO, DNS)
    - Windows 2008 R2 Server B: 10.0.1.2 (DC, GC)
    AD Domain: COMPANY.LOCAL
    I have a second connected subnet, 192.168.1.0 /24) which is routed to the 10.0.1.0/24 subnet and I would like to install a Windows 2012 R2 server onto a server on that subnet and make it a domain controller with AD-Integrated DNS and DHCP for the 192.168.1.0
    /24 subnet.
    - Windows 2012 R2 Server C: 192.168.1.1
    What are the proper progression steps, in order to bring up the Windows 2012 R2 server and then add it to my COMPANY.LOCAL domain and then promote it do a DC/GC/AD-Integrated DNS server?   Are they anything like the following:
    1. Install Windows 2012 R2 server (Server C)
    2. Point Windows 2012 R2 server DNS servers at Server's A and B
    3. Perform AD prep to extend AD schema to support Windows 2012 R2 domain controllers
    4. Promote Windows 2012 R2 server to domain controller (install local DNS service on Server C, during this step)
    * Question:  Will Windows automatically create a DNS zone for the Windows 2012 R2 subnet (192.168.1.0/24) AND also include the DNS zone from the previous Windows 2008 R2 domain (10.0.1.0 /24)?  Or will I need to add the 10.0.1.0 /24 zone to the DNS
    server on Server C, even though the DNS from the Windows 2008 R2 domain is AD integrated?

    Hi,
    Regarding the issue here, please take a look into below articles:
    System Requirements and Installation Information for Windows Server 2012 R2
    http://technet.microsoft.com/en-us/library/dn303418.aspx
    Release Notes: Important Issues in Windows Server 2012 R2
    http://technet.microsoft.com/en-us/library/dn387077.aspx
    Install a Replica Windows Server 2012 Domain Controller in an Existing Domain (Level 200)
    http://technet.microsoft.com/en-us/library/jj574134.aspx
    Here is an example for promoting Windows Server 2012 to a DC, see:
    Step-by-Step Guide for Setting Up A Windows Server 2012 Domain Controller
    http://social.technet.microsoft.com/wiki/contents/articles/12370.step-by-step-guide-for-setting-up-a-windows-server-2012-domain-controller.aspx
    As the server is promoted to a DC, DNS Zones will be replicated and synchronized to it automatically whenever the new one is added to an AD DS domain,  bascially there is no special need to add zones,  for more information, please see:
    Understanding Active Directory Domain Services Integration
    http://technet.microsoft.com/en-us/library/cc726034.aspx
    Hope this may help
    Best regards
    Michael
    If you have any feedback on our support, please click
    here.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • How to find which devices are still using affected domain controller

    Hi Everyone,
    We have a 5 Domain controller's in a Site. And we are going to decommisson one of our affected DC in a site.
    Can you please let me know how to find  the log files to see which devices are still using this domain controller.
    Regards,
    Neel kamal
    Neel kamal

    Neel,
    From strictly an Active Directory perspective, there is nothing special you need to do to decommission a domain controller in a site.  There are many processes that automatically balance out and recreate connections as needed without any user intervention. 
    The DC Locator process will automatically direct clients to active domain controllers, there is nothing you need to do here. 
    What you need to be concerned with are things like the following:
    DNS - Are you running AD integrated DNS and is the DC you are decommissioning hosting that roll - if so, is it the ONLY DC in the
    site that is running DNS?  You'll need at least one in the site.
    DHCP server - Is the DC you are demoting a DHCP server?  You'll need to account for that.
    Global Catalog - Is the DC you are demoting a Global Catalog server?  You'll need at least one in the site.
    File Shares - Is the DC hosting any files shares?  You'll need to move those and make sure you redirect your clients.
    Was this DC a set as a Preferred Bridgehead Server?  You'll need to undo that first.
    Those are the big ones that come to mind.  Decommissioning a DC is easy if you have prepared properly.  The others that have replied have offered some great advice which you should follow.  Do your homework and you should be fine.
    Hope that helps
    Gary
    Gary G. Gray
     MCP, MCTS, MCITP, MCT Alumni
    Please remember to mark the replies as answers if they are helpful.
    This posting is provided AS-IS with no warranties or guarantees and confers no rights.

  • Refreshing the DEV system, which is our domain controller

    Hi,
    We refreshed our DEV system, which is our domain controller. How to get back our STMS configuration in the domain controller ? Can I run se06 in our proudction system to delete the TMS and then running STMS in production to create the TMS. Then approving that in the domain controller. Is there any other way to restore the configuration ?
    Thanks
    Rabi

    You could always specify a backup domain controller before you start.

  • Need to delete Transport system , which is not domain controller

    I need to delete transport system on machine which is not domain controller .
    our domain controller system is not avalible now .
    how can i delete the transport system on my machine as domain controller system is not avaliable .
    Please let me know what can i do ??
    Thanks,
    Asc

    Hi,
    Logon to any system which is in your transport path in client 000. Then in stms, go to Overview ---> Systems. Here you can find all the systems in your transport path. You can also find the domain controller which you have configured as before.
    Now, goto Extras----> Delete TMS Configuration.
    After deleting, logon to system which you want to make as domain controller in client 000. when you execute stms, now it will ask for new stms setup, which you might be aware of.
    If you need more guidance, let me know.
    Thanks,
    Sailesh K

  • Could Apple provide info about IP addresses from which my iPhone was tracked?

    Hello, i've been attacked by two people in the street from the back and my bag with documents and money has been stolen. and now i'm guessing who was it. So i have a question about Find My iPhone app: could Apple provide info about IP addresses from which my iPhone was tracked?

    Welcome to the Apple Community.
    could Apple provide info about IP addresses from which my iPhone was tracked?
    Unfortunately not.

  • Error handling: Customizing error details: Info about the the path to the VI which has thrown the error

    Hi,
    I need a quick advice about how to display in the error cluster the information about the path and VI which has thrown an error.
    When I don't prepare my own error message, and the error is captured automatically, the information about the path, Vi name and calling VIs is presented automatically.
    When I prepare/define my own basic error cluster I have only what I define in the string part of the cluster. 
    How to cause tha apperance the path and VI name in my defined error message?

    MimiKLM wrote:
    You mean this link
    That's helpful too but,  I had read "When I prepare/define my own basic error cluster I have only what I define in the string part of the cluster" as you wanted to use a file to expose those custom error codes and ultimately ship them with your solution dynamically rather than statically
    The error ring will pick up any custom errors you define in the error file(s).  Including formatting!  this then populates the explain errors and error dialogs just like any error definition that ships with any LabVIEW component or toolkit.
    Certainly, an error ring can also STATICALLY define or re-define an error within the application instance the ring is called from.  Those Error Rings are quite flexible!
    Jeff

Maybe you are looking for

  • Display image in html mail

    I was recently sent an email that used an HTML stationery wih several photos embedded in it.  The email opens normally, but all of the images are icons, displaying file name and size.  If I click the icon, the image opens correcly in a separate windo

  • How much RAM can I put in a previous-generation (2008) iMac 2.4CHz

    Hi Guys, Silly question, but can I put more than 4GB of RAM in my 2008 model 2.4GHz iMac? I have upped it to 4GB (2 sticks of 2), but wonder if you can get 4GB sticks for a total of 8GB (2 sticks of 4)? I'm running Logic Pro 8 and with the virtual in

  • Is it possible to make a game for a mobile phone?

    Im a new newbie(means that i completely unaware of J2ME programing) I wonder if it is possible to make a game to my pc for a mobile phone and then send it to the mobile using Irda ..or more generally if a mobile phone uses or supports j2me can i chan

  • Download SAP Netweaver application server ABAP 7.02 SP6 32 Bit trail versio

    Hi All, I am using mac . i have noticed that in SDN we can download SAP Netweaver application server ABAP 7.02 SP6 32 Bit trail version. But all the details specified out there is only for windows os.Do we have options for mac here ?? Thanks, Joe

  • IPhoto won't export cropped iPad and iPhone screen shots

    I started a thread for this thinking it was affecting my whole iPhoto library, when I export a cropped image I get the original. I thought I'd solved it by rebuilding my library, then realized the issue was only manifesting with iPad screen shots. I