Each DC has two GUIDs... * the objectGUID identifies the DC itself and is used for replication. That is also the GUID that is registered in _MSDCS. This value can be found in the attribute called "objectGUID" on the NTDS Settings object that is owned by the DC. This GUID is created when promoting the server to a DC and is destroyed when demoting to server. So as long as the DC is a DC this GUID remains * the Invocation ID identifies the database instance on the DC and is used to record originating updates, which means on which database instance was something added ot changed. This value can be found in the attribute called "Invocation ID" on the NTDS Settings object that is owned by the DC. This GUID is created when promoting the server to a DC and is initially the same as the objectGUID. The invocation ID changes as soon as the DC is restored from a backup USING A SUPPORTED AD AWARE BACKUP MECHANISM or when an application partition is instantiated. all service records that registered by the DC are stored in the NETLOGON.DNS file (located in %WINDIR%\System32\Config). That file be used to import data into DNS Cheers, Jorge Met vriendelijke groeten / Kind regards, Ing. Jorge de Almeida Pinto Senior Infrastructure Consultant MVP Windows Server - Directory Services LogicaCMG Nederland B.V. (BU RTINC Eindhoven) ( Tel : +31-(0)40-29.57.777 ( Mobile : +31-(0)6-26.26.62.80 * E-mail : <see sender address>
________________________________ From: [EMAIL PROTECTED] on behalf of [EMAIL PROTECTED] Sent: Wed 2006-09-20 21:19 To: ActiveDir@mail.activedir.org Subject: [ActiveDir] AD and static DNS Does the GUID used for a DC change when the server is brought up through dcpromo, or does it remain the same as the base OS install. That is, can I take the current GUID and use it to prefill my static BIND records, or do I need to do the dcpromo and then create the records? Thanks, Andrew Fidel This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
<<winmail.dat>>
