Hi All,
I had a Single domain controller Server 2003
I have already installed 2012 Server on another physical server.
Raised domain functional level to Windows 2003
Promoted 2012 server to Domain controller.
Transferred all fsmo roles to 2012 server and verified too.
Now issue is when I try to edit group policy through 2012 Server I get and error " Failed to open Group Policy Object. You might not have the appropriate rights. " in Details box i got this "The network name cannot be found"
and when in my Group Policy Management when i click on my domain name it shows a pop-up saying "A processing error occurred collecting data using this base domain controller. Please change the base domain controller and try again."
so I right clicked the domain name and click change domain controller and than select my old 2003 domain controller. after doing this every thing started working fine. Means I am able to edit the group policy.
Kindly tell me where did i go wrong while promoting the new 2012 server to Domain controller. even though AD shows my 2012 server is now PDC.
Is there something else which I missed and had to do to completely transfer the Domain controller?
please note I have to turn off the older on after some time so I have to make sure that everything is transferred and the new server can work alone and on its own.
Thanks in Advance
Raja Mansoor
Here are two Warnings which I found in event logs.
1. Event Id 2092 source=ActiveDirectory_DomainService Task category=Replication.
Here is the error
------------------------------------------------
This server is the owner of the following FSMO role, but does not consider it valid. For the partition which contains the FSMO, this server has not replicated successfully with any of its partners since this server has been restarted. Replication errors
are preventing validation of this role.
Operations which require contacting a FSMO operation master will fail until this condition is corrected.
FSMO Role: CN=Schema,CN=Configuration,DC=nmc,DC=net,DC=pk
User Action:
1. Initial synchronization is the first early replications done by a system as it is starting. A failure to initially synchronize may explain why a FSMO role cannot be validated. This process is explained in KB article 305476.
2. This server has one or more replication partners, and replication is failing for all of these partners. Use the command repadmin /showrepl to display the replication errors. Correct the error in question. For example there maybe problems with IP connectivity,
DNS name resolution, or security authentication that are preventing successful replication.
3. In the rare event that all replication partners are expected to be offline (for example, because of maintenance or disaster recovery), you can force the role to be validated. This can be done by using NTDSUTIL.EXE to seize the role to the same server. This
may be done using the steps provided in KB articles 255504 and 324801 on http://support.microsoft.com.
The following operations may be impacted:
Schema: You will no longer be able to modify the schema for this forest.
Domain Naming: You will no longer be able to add or remove domains from this forest.
PDC: You will no longer be able to perform primary domain controller operations, such as Group Policy updates and password resets for non-Active Directory Domain Services accounts.
RID: You will not be able to allocation new security identifiers for new user accounts, computer accounts or security groups.
Infrastructure: Cross-domain name references, such as universal group memberships, will not be updated properly if their target object is moved or renamed.
---------------------
2. Error ID =13508 Source=NtFrs Category=None
Here is the error
------------------------
The File Replication Service is having trouble enabling replication from SERVER to AD-DNS for c:\windows\sysvol\domain using the DNS name server.nmc.net.pk. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name server.nmc.net.pk from this computer.
[2] FRS is not running on server.nmc.net.pk.
[3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
--------------------------------------
Thank you every one for reading such a long post