2008 R2 SP1 Domain Controllers Local Audit Settings

Question for the forum -- On a DC should the Audit settings in Local Security Policy (under administration tools) match the Audit settings that are set in the Default Domain Controller
policy in Active Directory?
My default domain controller policy has a lot of stuff set for auditing -- when I look at the local policy it shows "No Auditing"  -- I can't change it as I would expect
When I run RSOP.MSC I see that the DC is getting its auditing settings from the Default Domain Controller Policy.
When I look at the event log -- I would expect to see more events being logged -- and I don't.  Its logging events in the security log -- but I don't see anything for account management activities where it set to success & failure
in the default domain controller security policy.
Thanks. 

Hi,  
Did you enable Advanced Audit Policy Configuration? If yes,
The audit policy under Computer Configuration\Polices\Windows Settings\Security Settings\Local Policy will not work.
I recommend you to run command
auditpol.exe /get /category:*to
check the audit policy. If account management policy do not applied, we could check if the following file exists:
Windows\SYSVOL\sysvol\domain name\Policies\ {6AC1786C-016F-11D2-945F-00C04fB984F9}\MACHINE\Microsoft\ Microsoft NT\ audit.csv
If yes, we could delete it and then refresh the group policy.
For more detailed information about
Audit Policy, please refer to the following link:
Getting the Effective Audit Policy in Windows 7 and 2008 R2
http://blogs.technet.com/b/askds/archive/2011/03/11/getting-the-effective-audit-policy-in-windows-7-and-2008-r2.aspx
Best Regards,
Erin

Similar Messages

  • Is it possible for Windows 2008R2 Domain Controllers to audit when a programs are installed/uninstalled on clients and send alerts to Admins?

    We have a program called Audit Wizard that we used with Windows 2003 that monitored all clients and alerted my department when a program was installed/uininstalled. since upgrading to windows server 2008R2, the program no longer works correctly.
    So we are wondering if it is possible for Windows 2008R2 Domain Controllers, running at a 2008R2 forest and domain level) to be able to audit when a programs are installed/uninstalled on clients and send alerts to our Admins?
    If so, How?
    Thanks in advance for your help!
    Pete Macias

    Hi Pete,
    >>So we are wondering if it is possible for Windows 2008R2 Domain Controllers, running at a 2008R2 forest and domain level) to be able to audit when a programs are installed/uninstalled on clients and send alerts to our Admins?
    As far as I know, group policy can't help us do this. If you are interested, we can take a look at System Center Operation Manager and ask for suggestions in the following SCOM forum.
    Operations Guide for System Center 2012 - Operations Manager
    https://technet.microsoft.com/en-us/library/hh212887.aspx
    System Center Operation Manager
    https://social.technet.microsoft.com/Forums/systemcenter/en-US/home?category=systemcenteroperationsmanager
    Best regards,
    Frank Shen 
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Windows 2008 (Not R2) Domain controllers Kerberos Errors

    We know the replication of the AD structure is working using repadmin /showREPL *
    Which I ran again this morning and all is fine.
    All 3 Domain Controllers are having Kerberos errors ?
    I tried to reset the Kerberos key but the problem still persists.
    This is exactly what I tried yesterday is there something I'm doing wrong ?
    We have 3 Domain controllers
    ch-dc1-2k8    (PDC)
    ch-dc2-2k8
    na-dc1-2k8
    1) I stopped the Kerberos Key Distribution Center service on all 3 servers and set them to manual
    2) I restarted ch-dc2-2k8 and na-dc1-2k8
    3) Then I did the KLIST PURGEon
    ch-dc2-2k8 and na-dc1-2k8
    4) Then on ch-dc1-2k8 (PDC) I did the
    netdom resetpwd /s:ch-dc1-2k8 /ud:companyname\administrator /pd:*
    5) Set Kerberos Key Distribution Center service to Automatic on ch-dc1-2k8 (PDC)
    6) Restarted ch-dc1-2k8 (PDC)
    7) After it restarted I logged in and let it settle for 5 Minutes
    8) Then I started the kerberos service on ch-dc2-2k8 and na-dc1-2k8
    Am I missing something ?

    Hi,
    I think I have already answer this in separate case you have raised in forum.

  • Server Core 2008 R2 SP1 - AD DS Best Practice Analyzer Scans Don't Produce Any Output

    Hi,
    This is a re-post moving this discussion to the recommended forum "Server Core" from here:
    http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/cc33d429-88e0-4450-a73c-361e395fd217.
    I am having problems producing any output for any AD DS Best Practice Analyzer Scans on a Windows Server Core 2008 R2 SP1 Domain Controller.
    I have imported the "ServerManager" and "BestPractices" PS modules on that Server by running the following commands:
    Import-Module ServerManager
    Import-Module BestPractices
    I've then run
    get-BPAModel, to find out what best practice scan models are availale, this returns the following output:
    Id                                                       
    LastScanTime
    Microsoft/Windows/DirectoryServices     Never
    Microsoft/Windows/DNSServer               Never
    I then run all the BPA scans on that box:
    Get-BPAModel | Invoke-BPAModel
    This returns the following output:
    ModelId                                          
    Success  Detail
    Microsoft/Windows/DirectoryServices True       (InvokeBpaModelOutputDetail)
    Microsoft/Windows/DNSServer          True       (InvokeBpaModelOutputDetail)
    Since the BPA invocation results weren’t displayed automatically, I entered the following command to see them:
    Get-BPAModel | Get-BPAResult | Out-File "D:\Source\BPA.txt"
    This command will create a text file with the scan results but I only see the results of the DNSServer scan, not the DirectoryServices scan.
    I have also tried to view the results in a HTML format by running the following command but still only see the DNSServer scan results:
    Get-BPAModel | Get-BPAResult | ConvertTo-Html | Set-Content d:\Source\BPA.htm
    I have also tried exeucuting the scan ONLY for the "Microsoft/Windows/DirectoryServices" model but can't get any results to be returned.  I have also connected using server manager from a Full install of Server 2008 R2 SP1 but that
    doesn't seem to show any results under the "Best Practices Analyzer" section when the "Active Directory Domain Services" node is selected, all 4 tabs ("Noncompliant", "Excluded", "Compliant" and "All") show zero (0).  However, the summary text above the
    tabs does show when the last scan was performed. which seems to be correct.
    Is there something special that needs to be done to produce the BPA results for the "Microsoft/Windows/DirectoryServices" BPA model on Server Core 2008 R2 SP1?
    BTW: The Forest/Domain is W2K3R2 Native, this is the first W2K8R2 DC in the environment and I have installed .NET 4 framework (Server Core) to support Powershell 3, also installed.
    Thanks, Paul.
    belpad

    Hi Diana,
    OK, pretty sure I've now found the root cause of the issue I've described above.
    I was also looking into Windows Update Agent issues for these W2K8R2 Server Core DC's, where no updates would be applied via WSUS (configured via GPO) and would fail with "FATAL: CBS called Error with 0x8000ffff windows update agent server
    core". 
    Yesterday, I managed to get one of the W2K8R2 Server Core DC's (WSUS updates) working again by removing one of the .NET 4 Framework security updates (KB2600211) which was manually applied when the server was initially setup.  .NET 4 (Server Core Edition
    http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=22833) was installed as a pre-requisitie for Powershell 3.  Once this update was removed, the affected server core DC was restarted and WSUS updates started to get applied.
    So I followed the same procedure on the other server core DC but this did not resolve the WSUS issue this time.  Next, I did further investigation into the Windows Update Agent problem.  This led me to the following article:
    http://blogs.technet.com/b/brad_rutkowski/archive/2008/07/03/windows-update-fails-with-8000ffff-e-unexpected.aspx which described an issue with NTFS permissions being set incorrectly on C: drive, with the "BUILTIN\Users" group completely
    missing on the C: drive.
    I found the affected Server Core DC also had this issue and when the "BUILTIN\Users" was assigned permissions on the C: drive as described above, and the Windows Update Agent re-started, the Server Core DC started to install all required updates
    configured via WSUS.
    Next, I ran the Directory Service BPA, which now produces the desired output either locally or remotely via Server Manager.
    Therefore, I can only assume that the Directory Service BPA also uses "Network Service" much like WUAUSERV (Windows Update Agent), which requires access to the C: drive via the "BUILTIN\Users" assignment.
    So this has subsequently led me to check the C: drive (%systemdrive%) permissions across multiple W2K8R2 machines, all of which showed differing assigned permissions, as follows:
    1. W2K8R2 Server Core DC - With Directory Services BPA and Windows Update Agent Not Working
    C:\>icacls c:\
    c:\ BUILTIN\Administrators:(OI)(CI)(F)
        CREATOR OWNER:(OI)(CI)(IO)(F)
        NT AUTHORITY\INTERACTIVE:(OI)(CI)(RX)
        NT AUTHORITY\SYSTEM:(OI)(CI)(F)
    2. W2K8R2 Server Core DC - With Directory Services BPA and Windows Update Agent Working OK
    C:\>icacls c:\
    c:\ NT AUTHORITY\SYSTEM:(OI)(CI)(F)
        BUILTIN\Administrators:(OI)(CI)(F)
        BUILTIN\Users:(OI)(CI)(RX)
        BUILTIN\Users:(CI)(AD)
        BUILTIN\Users:(CI)(IO)(WD)
        CREATOR OWNER:(OI)(CI)(IO)(F)
    3. W2K8R2 Full DC - With Directory Services BPA and Windows Update Agent Working OK
    C:\>icacls c:
    c: NT SERVICE\TrustedInstaller:(F)
       NT SERVICE\TrustedInstaller:(CI)(IO)(F)
       NT AUTHORITY\SYSTEM:(M)
       NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F)
       BUILTIN\Administrators:(M)
       BUILTIN\Administrators:(OI)(CI)(IO)(F)
       BUILTIN\Users:(RX)
       BUILTIN\Users:(OI)(CI)(IO)(GR,GE)
       CREATOR OWNER:(OI)(CI)(IO)(F)
    4. W2K8R2 Server Core DHCP Server (Migrated from W2K3 with Server Migration Tools) - With DHCP BPA and Windows Update Agent Working OK
    C:\>icacls c:
    c: NT AUTHORITY\SYSTEM:(OI)(CI)(F)
       BUILTIN\Administrators:(OI)(CI)(F)
    5. W2K8R2 Server Core DHCP Server (Migrated from W2K3 with netsh) - With DHCP BPA and Windows Update Agent Working OK
    C:\>icacls c:
    c: NT AUTHORITY\SYSTEM:(OI)(CI)(F)
       BUILTIN\Administrators:(OI)(CI)(F)
       BUILTIN\Users:(OI)(CI)(RX)
       BUILTIN\Users:(CI)(AD)
       BUILTIN\Users:(CI)(IO)(WD)
       CREATOR OWNER:(OI)(CI)(IO)(F)
    None of the above servers have a Group Policy or any in-house scripts defined that configure C: drive permissions.  It seems odd that there should be such a variance in the C: (%systemdrive%) drive permissions across the above servers, with only
    scenarios 2 and 5 above have matching permissions.  I can only imagine that maybe some software or software update might be causing this.
    By reviewing the above output, it seems there is also a difference between the C: drive permissions of W2K8R2 Server Core and W2K8R2 Full.  Not sure if this is by design? 
    Is there any Microsoft Documentation describing what the default %systemdrive% NTFS permissions should be for W2K8R2 Server Core and Full.  Furthermore, do these permissions change when the various infrastructure roles are installed and enabled i.e.
    Domain Controller, DHCP etc.  I ask, since I would like to use the correct set of permissions for %systemroot% in each scenario. Please advise if I should be asking this question in a different forum?
    belpad

  • Migrating Certificate Services to Server 2012 in a 2008 R2 AD Domain

    We have a Windows 2008 R2 SP1 Active Directory domain. Our Enterprise Certificate server is running on Windows 2003 R2. We'd like to introduce a Windows 2012 server into our existing domain and migrate the Certificate Services to that new box. Are there
    any 'gotchas' to implementing Certificate Cervices on a Windows Server 2012 system in a Windows 2008 R2 SP1 domain that we should be concerned with?
    Orange County District Attorney

    Hi,
    You can migrate Certificate Services to another server but server name should be same. Also changing the server name which has CA role installed is not recommended.
    AD CS Migration: Preparing to Migrate
    Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012
    http://technet.microsoft.com/en-us/library/ee126102(v=ws.10).aspx
    Also I would request to post this question in security forum :
    http://social.technet.microsoft.com/Forums/en-US/winserversecurity/threads
    Also you consider, Windows Server 2012 General forum :
    http://social.technet.microsoft.com/Forums/en-US/winserver8gen/thread
    Best regards,
    Abhijit Waikar.
    MCSA | MCSA:Messaging | MCITP:SA | MCC:2012
    Blog: http://abhijitw.wordpress.com
    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees and confers no rights.

  • Domain Controllers that are DNS servers DNS Client settings

    [Copying verbatim from a mail by Joe ]
    So I have been pinged by a few folks recently on configuration of client DNS settings on Domain Controllers that are also functioning as DNS Servers. Lots of debate. I understand there has been long time debate within MSFT as well.
    From http://blogs.technet.com/b/askds/archive/2010/07/17/friday-mail-sack-saturday-edition.aspx there
    is the quote
    "3.When referencing a DNS server on itself, a DNS client should always use a loopback address and not a real IP address."
    From http://www.microsoft.com/en-us/download/confirmation.aspx?id=9166 (Windows
    Server 2008 R2 Core Network Guide)
    "9.        In Preferred DNS server, type the IP address of your DNS server. If you plan to use the local computer as the preferred DNS server, type the IP address of the
    local computer.
    10.       In Alternate DNS Server, type the IP address of your alternate DNS server, if any. If you plan to use the local computer as an alternate DNS server, type the IP address of
    the local computer."
    From http://technet.microsoft.com/en-us/library/dd378900(v=ws.10).aspx (DNS:
    DNS servers on <adapter name> should include their own IP addresses on their interface lists of DNS servers)
    "The inclusion of its own IP address in the list of DNS servers improves performance and increases availability of DNS servers. However, if the DNS server is also a domain controller and it points only to
    itself for name resolution, it can become an island and fail to replicate with other domain controllers. For this reason, use caution when configuring the loopback address on an adapter if the server is also a domain controller. The loopback address should
    be configured only as a secondary or tertiary DNS server on a domain controller...
    Add the loopback IP address to the list of DNS servers on all active interfaces. The loopback IP address should not be the first server in the list."
    ESPECIALLY "For this reason, use caution when configuring the loopback address on an adapter if the server is also a domain controller. The loopback address should be configured only as a secondary or tertiary
    DNS server on a domain controller." and "Add the loopback IP address to the list of DNS servers on all active interfaces. The loopback IP address should not be the first server in the list."
    Why shouldn't loopback not be first, the justification is why you shouldn't only use loopback, not why it shouldn't be first.
    From http://technet.microsoft.com/en-us/library/ff807362(v=ws.10).aspx (DNS:
    DNS servers on <adapter name> should include the loopback address, but not as the first entry)
    "If the loopback IP address is the first entry in the list of DNS servers, Active Directory might be unable to find its replication partners. 
    The inclusion of its own IP address in the list of DNS servers improves performance and increases availability of DNS servers. However, if the DNS server is also a domain controller and it points only to itself,
    or points to itself first for name resolution, this can cause a delay during startup. For this reason, use caution when configuring the loopback address on an adapter if the server is also a domain controller. The loopback address should be configured only
    as a secondary or tertiary DNS server on a domain controller."
    This also seems like justification against only using loopback versus using it first.
    Are there any actual real documented issues for using loopback first and a remote DNS server second and perhaps third? If the local DNS server service isn't working yet (or at all), I would expect the DNS Client process
    to try to connect to it, fail, and then failover to the secondary just like I would expect it to failover if the remote DNS server was secondary and it was unavailable and it failed back to the loopback. Am I making a bad assumption?
    And by documented I don't mean random responses to questions on the internet or other such items. I mean a KB article or technet article or properly researched and tested other web article from a reliable resource.
    thanks, 
    joe

    As I understand it, the scenario whereby a DC could become an 'island' if it points only to itself, or to itself first, was repaired in the Windows Server 2003 product cycle. See
    http://support.microsoft.com/kb/275278 for information about this scenario.
    However, there is still a known problem of slow boot times that can occur. See
    http://support.microsoft.com/kb/2001093 for information about this. The scenario that is discussed assumes there is a power failure and servers shut down due to overheating while on backup power. When
    multiple servers come online simultaneously after power is restored, there can be a significant delay.
    The recommended configuration is one that avoids a single point of failure, but also tries to optimize the speed of resource record registration, so that Active Directory can properly synchronize.
    -Greg

  • Command to set modify Advanced Security Settings (Audit Settings for folders) on windows 2008

    Hello,
    We have requirement to modify  Advanced Security Settings (Audit Settings for folders) on windows 2008. I am looking for a command which does this job.
    I know, using group policies I can do this; in fact I had done this using group policies. However, I need to do this on number of servers which are not in domain. There are around 15 folders on which I need to enable Auditing; manual editing folder advanced
    permissions is a cumbersome job. Hence, I am looking for a command line options.
    I need to know how command can be utilised to enable Audit option on a folder. Please share a command which can do this; once I get the command, I will create a batch file for other necessary folders. (BTW, this is not a scripting question, I just need to
    know the command hence, please do not re-direct me to scripting forum)
    Manually through GUI, I am setting following.. snaps are given below
    Thanks !

    You can try using Auditpol.exe: http://technet.microsoft.com/en-us/library/cc731451%28v=ws.10%29.aspx
    This
    posting is provided "AS IS" with no warranties or guarantees , and confers no rights.   
    Microsoft
    Student Partner 2010 / 2011
    Microsoft
    Certified Professional
    Microsoft
    Certified Systems Administrator: Security
    Microsoft
    Certified Systems Engineer: Security
    Microsoft
    Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft
    Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft
    Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft
    Certified Technology Specialist: Windows 7, Configuring
    Microsoft
    Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer
    Thanks but I guess, auditpol ca be used only to manipulate system audit policies. how do I specify a folder and user in auditpol ? I could not find or understand how folder can be included with auditpol command line options.
    Thanks !

  • Audit/Log GPO changes and Logging of new addition of Domain Controllers in the Event Log

    Hi all, 
    We am trying to log the following items in the event log for Windows 2012. This applies to a domain controller. 
    1) Audit any changes made to the Group Policy
    2) Log the addition of new domain controllers added to the system.
    We need the windows event log to record the above events for security purposes. Can anyone advise if this is doable? If yes what are the steps. 
    Thank you

    Hi,
    >>1) Audit any changes made to the Group Policy
    We can enable audit for directory service object access and configure specific SACL for group policy files to do this.
    Regarding how to step-to-step guide for auditing changes of group policy, the following two blogs can be referred to for more information.
    Monitoring Group Policy Changes with Windows Auditing
    http://blogs.msdn.com/b/ericfitz/archive/2005/08/04/447951.aspx
    Auditing Group Policy changes
    http://blogs.msdn.com/b/canberrapfe/archive/2012/05/02/auditing-group-policy-changes.aspx
    >>2) Log the addition of new domain controllers added to the system.
    Based on my knowledge, when a server is successfully promoted to be domain controller, event ID 29223 will be logged in the System log.
    Regarding this point, the following thread can be referred to for more information.
    Is an Event ID for a completed Domain Controller promotion logged on the PDC?
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/11b18816-7db0-49e2-9a65-3de0e7a9645e/is-an-event-id-for-a-completed-domain-controller-promotion-logged-on-the-pdc?forum=winserverDS
    Best regards,
    Frank Shen

  • Windows 2008 R2 domain controllers with Windows 2003 forest functional level Supported after Windows 2003 support ends in July 2015

    Hi
    Anyone knows whether Windows 2008 R2 domain controllers with Windows 2003 forest functional level will still be Supported after Windows 2003 support ends in July 2015 ?
    Thanks

    When Windows Server 2003 support ends, you should not have a Windows Server 2003 Domain Controller running if you would like to be supported by Microsoft. This means that there will be no reason to have a DFL or FFL that is lower than Windows Server 2008.
    So, if you are keeping Windows Server 2003 FFL to keep DCs running Windows Server 2003 then this is not supported.
    This posting is provided AS IS with no warranties or guarantees , and confers no rights.
    Ahmed MALEK
    My Website Link
    My Linkedin Profile
    My MVP Profile

  • Create a child or subdomain in a field or domain in Windows Server 2008 R2 SP1 using Powershell

    I am trying to create a child or subdomain in a field or domain in Windows Server 2008 R2 SP1 using Powershell.
    ps>powershell.exe -noprofile -command "&{ start-process powershell -ArgumentList '-noprofile -file C:\Users\Administrator\Documents\Powershell\psfile.ps1' -verb RunAs}"
    psfile.ps1
    ([WMIClass]"\\sandpit\root\MicrosoftDNS:MicrosoftDNS_Zone").CreateZone("subdomain.domain.com", 0, $False)

    This is a duplicate of a duplicate of a duplicate.
    I think this is the current:
    http://social.technet.microsoft.com/Forums/scriptcenter/en-US/734be028-438d-433c-b3f7-676c0490b61d/create-a-child-or-subdomain-in-a-field-or-domain-in-windows-server-2008-r2-sp1-using-powershell?forum=winserverpowershell
    Don't retire TechNet! -
    (Don't give up yet - 12,830+ strong and growing)

  • Compatibility Exchange Server 2003 SP2 and Domain controllers Windows Server 2008 R2

    Hi all, I have this scenario:
    - Two Domain Controllers Windows Server 2003 R2 SP2
    - Two mail servers Exchange Server 2003 with the following version:
      6.5 (Build 7638.2 Service Pack 2)
    I want to upgrade my domain controllers to Windows Server 2008 R2.
    My question is whether exchange Server 2003 6.5 (Build 7638.2 Service Pack 2) is supported with Domain Controllers Windows Server 2008 R2.
    Can you tell me some official Microsoft website where this reflected?
    regards
    Microsoft Certified IT Professional Server Administrator

    Exchange Server 2003 SP2 supports DCs running Windows Server 2008 R2. These DCs should be RWDCs and not RODCs:
    Exchange 2003 SP2 will now be supported against writeable Windows Server 2008 R2 Active Directory Servers.  Additionally, with the General Availability of Exchange Server 2010, and those looking to standardize on Windows
    Server 2008 R2 we have enhanced the supportability of forest and domain functional levels up to Windows Server 2008 R2.  This change is effective immediately on Exchange 2003 SP2.
    Reference: http://blogs.technet.com/b/exchange/archive/2009/11/30/3408893.aspx
    This posting is provided AS IS with no warranties or guarantees , and confers no rights.
    Ahmed MALEK
    My Website Link
    My Linkedin Profile
    My MVP Profile

  • Prepare 2003 Forest/Domain for 2008 R2 or 2012 Domain Controllers

    Hi,
    I would be grateful if you could help me with this:
    We have a single Forest/Single Domain structure which is managed by 4 Windows Server 2003 Std Edition. We are now trying to add a Server 2008 R2 as a domain controller. I have followed lots of articles on MS and other website with regards to preparing the
    Forest and domain before promoting the new server and here is what I got so far:
    Schema master - Windows 2003 SE
    FFL/DFL both set to 2003
    Run Adprep32.exe (found it on 2008 R2 disc) /forestprep and the outcome was:
    lDAPDisplayName "uidNumber" defined for object "CN=VintelauidNumber,CN=Schema,CN=Configuration,DC=Domain,DC=co,DC=uk" conflicts with the schema extensions needed for Windows Server 2008 R2.
    [Status/Consequence]
    Adprep will not extend your existing schema.
    [User Action]
    Contact the vendor of the application that extended the schema with the lDAPDisplayName value uidNumber and resolve this inconsistency.  Then run adprep again.
    ==============================================================================
    OID "1.3.6.1.1.1.1.0" defined for object CN=Vintela-uidNumber,CN=Schema,CN=Configuration,DC=Domain,DC=co,DC=uk conflicts with the schema extensions needed for Windows Server 2008 R2.
    [Status/Consequence]
    Adprep will not extend your existing schema.
    [User Action]
    Contact the vendor of the application that extended the schema with the OID value "1.3.6.1.1.1.1.0" and resolve this inconsistency.  Then run adprep again.
    ==============================================================================
    lDAPDisplayName "gidNumber" defined for object "CN=Vintela-gidNumber,CN=Schema,CN=Configuration,DC=Domain,DC=co,DC=uk" conflicts with the schema extensions needed for Windows Server 2008 R2.
    [Status/Consequence]
    Adprep will not extend your existing schema.
    [User Action]
    Contact the vendor of the application that extended the schema with the lDAPDisplayName value gidNumber and resolve this inconsistency.  Then run adprep again.
    ==============================================================================
    OID "1.3.6.1.1.1.1.1" defined for object CN=Vintela-gidNumber,CN=Schema,CN=Configuration,DC=Domain,DC=co,DC=uk conflicts with the schema extensions needed for Windows Server 2008 R2.
    [Status/Consequence]
    Adprep will not extend your existing schema.
    [User Action]
    Contact the vendor of the application that extended the schema with the OID value "1.3.6.1.1.1.1.1" and resolve this inconsistency.  Then run adprep again.
    ==============================================================================
    lDAPDisplayName "gecos" defined for object "CN=Vintela-gecos,CN=Schema,CN=Configuration,DC=Domain,DC=co,DC=uk" conflicts with the schema extensions needed for Windows Server 2008 R2.
    [Status/Consequence]
    Adprep will not extend your existing schema.
    [User Action]
    Contact the vendor of the application that extended the schema with the lDAPDisplayName value gecos and resolve this inconsistency.  Then run adprep again.
    ==============================================================================
    OID "1.3.6.1.1.1.1.2" defined for object CN=Vintela-gecos,CN=Schema,CN=Configuration,DC=Domain,DC=co,DC=uk conflicts with the schema extensions needed for Windows Server 2008 R2.
    [Status/Consequence]
    Adprep will not extend your existing schema.
    [User Action]
    Contact the vendor of the application that extended the schema with the OID value "1.3.6.1.1.1.1.2" and resolve this inconsistency.  Then run adprep again.
    ==============================================================================
    lDAPDisplayName "unixHomeDirectory" defined for object "CN=Vintela-homeDirectory,CN=Schema,CN=Configuration,DC=Domain,DC=co,DC=uk" conflicts with the schema extensions needed for Windows Server 2008 R2.
    [Status/Consequence]
    Adprep will not extend your existing schema.
    [User Action]
    Contact the vendor of the application that extended the schema with the lDAPDisplayName value unixHomeDirectory and resolve this inconsistency.  Then run adprep again.
    ==============================================================================
    OID "1.3.6.1.1.1.1.3" defined for object CN=Vintela-homeDirectory,CN=Schema,CN=Configuration,DC=Domain,DC=co,DC=uk conflicts with the schema extensions needed for Windows Server 2008 R2.
    [Status/Consequence]
    Adprep will not extend your existing schema.
    [User Action]
    Contact the vendor of the application that extended the schema with the OID value "1.3.6.1.1.1.1.3" and resolve this inconsistency.  Then run adprep again.
    ==============================================================================
    lDAPDisplayName "loginShell" defined for object "CN=VintelaloginShell,CN=Schema,CN=Configuration,DC=Domain,DC=co,DC=uk" conflicts with the schema extensions needed for Windows Server 2008 R2.
    [Status/Consequence]
    Adprep will not extend your existing schema.
    [User Action]
    Contact the vendor of the application that extended the schema with the lDAPDisplayName value loginShell and resolve this inconsistency.  Then run adprep again.
    ==============================================================================
    OID "1.3.6.1.1.1.1.4" defined for object CN=Vintela-loginShell,CN=Schema,CN=Configuration,DC=Domain,DC=co,DC=uk conflicts with the schema extensions needed for Windows Server 2008 R2.
    [Status/Consequence]
    Adprep will not extend your existing schema.
    [User Action]
    Contact the vendor of the application that extended the schema with the OID value "1.3.6.1.1.1.1.4" and resolve this inconsistency.  Then run adprep again.
    On the Schema master, run AD Schema, MMC and deactivated the object for Vintela. run the adprep32 /forestprep again and still the same result.
    Would you please advise what else can/must be done? anyone knows anything on Vintela (Quest VAS) and how to get rid of it?
    thanks for your help in advance.

    Hi,
    Thanks for your post.
    In this case, the most cause may be the OIDS are in conflict with the 2008 /forestprep. Could you please let me know if the forest functional level is 2003? If not, please raise it to 2003.
    For the information about how to raise functional level, please refer to the articles as below:
    What Are Active Directory Functional Levels?
    http://technet.microsoft.com/en-us/library/cc787290(WS.10).aspx
    Raise the Domain Functional Level
    http://technet.microsoft.com/en-us/library/cc753104.aspx
    Raise the Forest Functional Level
    http://technet.microsoft.com/en-us/library/cc730985.aspx
    What is the Impact of Upgrading the Domain or Forest Functional Level?
    http://blogs.technet.com/b/askds/archive/2011/06/14/what-is-the-impact-of-upgrading-the-domain-or-forest-functional-level.aspx
    Besides, for the best practice, we can back up all domain controllers’ system state for the unexpected issues. Here is one article related to backup Active Directory.
    Backing up Active Directory
    http://technet.microsoft.com/en-us/library/cc961924.aspx
    I hope this information is helpful for you. If there is anything that requires further clarification, please don’t hesitate to let me know.
    Best regards,
    Ann
    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.

  • Running Best Practice Analyzer on remote 2008 R2 domain controllers

    Hello Powershell World,
    I'll start out by first mentioning that I am a powershell rookie so I gladly welcome any input to help me improve or work more efficiently.  Anyway, I recently used powershell to run the best practice analyzer for DNS on all of our domain controllers.
     The way I went about was pretty tedious and inefficient but still got the job done through a series of one-liners and exported the report to a UNC path as follows:
    Enable-PSremoting -Force (I logged into all of the domain controllers individually and ran this before running the one-liners below from my workstation)
    New-PSSession -Name <Session Name> -ComputerName <Hostname>
    Enter-PSSession -Name <Session Name>
    Import-Module bestpractices
    Invoke-BPAModel Microsoft/Windows/DNSServer
    Get-BPAResult Microsoft/Windows/DNSServer | Select ModelId,Severity,Category,Title,Problem,Impact,Resolution,Compliance,Help | Sort Category | Export-CSV \\server\share\BPA_DNS_SERVERNAME.csv
    I'm looking to do this again but for the Directory Services best practice analyzer without having to individually enable remoting on the domain controllers and also provide a lsit of servers for the script to run against. 
    Thanks in advance for all your help!

    What do you mean by "without having to individually enable remoting "?
    You cannot remote without enabling remoting.  You only need to enable remoting once.  It is a configuraiton change.  If you have done it once you do not need to do it again.
    Here is how to runfrom a list of DCs.
    $sb={
    Import-Module bestpractices
    Invoke-BPAModel Microsoft/Windows/DNSServer
    Get-BPAResult Microsoft/Windows/DNSServer |
    Select ModelId,Severity,Category,Title,Problem,Impact,Resolution,Compliance,Help |
    Sort Category |
    Export-CSV "\\server\share\BPA_DNS_$env:COMPUTERNAME.csv"
    Invoke-BPAModel Microsoft/Windows/DirectoryServices
    # etc...
    ForEach($dc in $listofDCs){
    Invoke-Command -ScriptBlock $sb -Computer $dc
    ¯\_(ツ)_/¯

  • Reboot domain controller changes audit policy on Default Domain Controller Policy

    This has been happening for a long time no matter whether my DCs were running Windows Server 2003 or, as they are now, are running Windows Server 2012 R2. It happens on DCs in one particular site, but the policy change it causes is domain-wide.
    I have 2 DCs at that site, every time one of them is rebooted, the following policy is turned off, from Success and Failure to No auditing:
    Default Domain Controllers Policy - Computer Configuration - Policies - Windows Settings - Security Settings - Local Policies/Audit Policy.
    I have monitoring application relying on this policy being turned on, and if it's off, it's being reported. The monitoring application knows the change, but it doesn't know how the change was made.
    All my DCs are running Windows Server 2012 R2, DFL 2008 R2.
    Thanks and regards.

    Hi,
    >>I have 2 DCs at that site, every time one of them is rebooted, the following policy is turned off, from Success and Failure to No auditing:
    Did we try to run command gpresult/h report.html with admin privileges to collect group policy result report to check how the policy setting was  applied after rebooting?  Besides, we can also try to run command
    auditpol /get / category:* from an elevated command prompt to check what audit settings are applied.
    Best regards,
    Frank Shen
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Group Policy processing failure on 2008 when MIX Domain 2003 with DC 2008

    Dear I try to add additional Windows 2008 Domain to My Domain controller 2003  and I ma Receiving Group policy error in DC 2008  With Event ID 1055
    The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
    a) Name Resolution failure on the current domain controller. 
    b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Microsoft-Windows-GroupPolicy" Guid="{AEA1B4FA-97D1-45F2-A64C-4D69FFFD92C9}" /> 
      <EventID>1055</EventID> 
      <Version>0</Version> 
      <Level>2</Level> 
      <Task>0</Task> 
      <Opcode>1</Opcode> 
      <Keywords>0x8000000000000000</Keywords> 
      <TimeCreated SystemTime="2014-03-06T14:36:44.411955300Z" /> 
      <EventRecordID>3859</EventRecordID> 
      <Correlation ActivityID="{28DAD258-26D0-4C1E-A4B7-F37DEE04C8F1}" /> 
      <Execution ProcessID="952" ThreadID="3276" /> 
      <Channel>System</Channel> 
      <Computer>PRIMARYDC.Qtit.com</Computer> 
      <Security UserID="S-1-5-18" /> 
      </System>
    - <EventData>
      <Data Name="SupportInfo1">1</Data> 
      <Data Name="SupportInfo2">1632</Data> 
      <Data Name="ProcessingMode">0</Data> 
      <Data Name="ProcessingTimeInMilliseconds">1578</Data> 
      <Data Name="ErrorCode">5</Data> 
      <Data Name="ErrorDescription">Access is denied.</Data> 
      </EventData>
      </Event>
    I install See KB939820 for a hotfix applicable to Microsoft DC 2003 regrading to he KRBTGT account 
    Refer Url : http://support.microsoft.com/kb/939820 
    I run dcdiag /v on  and repadmin /showrepl at DC 2008
    the dcdiag /v result
    Directory Server Diagnosis
    Performing initial setup:
       Trying to find home server...
       * Verifying that the local machine PRIMARYDC, is a Directory Server. 
       Home Server = PRIMARYDC
       * Connecting to directory service on server PRIMARYDC.
       * Identified AD Forest. 
       Collecting AD specific global data 
       * Collecting site info.
       Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=Qtit,DC=com,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=Qtit,DC=com
       Getting ISTG and options for the site
       * Identifying all servers.
       Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=Qtit,DC=com,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
       The previous call succeeded....
       The previous call succeeded
       Iterating through the list of servers 
       Getting information for the server CN=NTDS Settings,CN=SECONDAD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com 
       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=PRIMARYDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com 
       objectGuid obtained
       InvocationID obtained
       dnsHostname obtained
       site info obtained
       All the info for the server collected
       * Identifying all NC cross-refs.
       * Found 2 DC(s). Testing 1 of them.
       Done gathering initial info.
    Doing initial required tests
       Testing server: Default-First-Site-Name\PRIMARYDC
          Starting test: Connectivity
             * Active Directory LDAP Services Check
             Determining IP4 connectivity 
             * Active Directory RPC Services Check
             ......................... PRIMARYDC passed test Connectivity
    Doing primary tests
       Testing server: Default-First-Site-Name\PRIMARYDC
          Starting test: Advertising
             The DC PRIMARYDC is advertising itself as a DC and having a DS.
             The DC PRIMARYDC is advertising as an LDAP server
             The DC PRIMARYDC is advertising as having a writeable directory
             The DC PRIMARYDC is advertising as a Key Distribution Center
             The DC PRIMARYDC is advertising as a time server
             The DS PRIMARYDC is advertising as a GC.
             ......................... PRIMARYDC passed test Advertising
          Test omitted by user request: CheckSecurityError
          Test omitted by user request: CutoffServers
          Starting test: FrsEvent
             * The File Replication Service Event log test 
             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. 
             A warning event occurred.  EventID: 0x800034C8
                Time Generated: 03/06/2014   10:18:56
                Event String:
                The File Replication Service has detected an enabled disk write cache on the drive containing the directory c:\windows\ntfrs\jet on the computer PRIMARYDC. The File Replication Service might not recover when power to
    the drive is interrupted and critical updates are lost.
             A warning event occurred.  EventID: 0x800034C8
                Time Generated: 03/06/2014   10:53:21
                Event String:
                The File Replication Service has detected an enabled disk write cache on the drive containing the directory c:\windows\ntfrs\jet on the computer PRIMARYDC. The File Replication Service might not recover when power to
    the drive is interrupted and critical updates are lost.
             ......................... PRIMARYDC passed test FrsEvent
          Starting test: DFSREvent
             The DFS Replication Event Log. 
             Skip the test because the server is running FRS.
             ......................... PRIMARYDC passed test DFSREvent
          Starting test: SysVolCheck
             * The File Replication Service SYSVOL ready test 
             File Replication Service's SYSVOL is ready 
             ......................... PRIMARYDC passed test SysVolCheck
          Starting test: KccEvent
             * The KCC Event log test
             Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
             ......................... PRIMARYDC passed test KccEvent
          Starting test: KnowsOfRoleHolders
             Role Schema Owner = CN=NTDS Settings,CN=SECONDAD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             Role Domain Owner = CN=NTDS Settings,CN=SECONDAD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             Role PDC Owner = CN=NTDS Settings,CN=SECONDAD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             Role Rid Owner = CN=NTDS Settings,CN=SECONDAD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             Role Infrastructure Update Owner = CN=NTDS Settings,CN=SECONDAD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             ......................... PRIMARYDC passed test KnowsOfRoleHolders
          Starting test: MachineAccount
             Checking machine account for DC PRIMARYDC on DC PRIMARYDC.
             * SPN found :LDAP/PRIMARYDC.Qtit.com/Qtit.com
             * SPN found :LDAP/PRIMARYDC.Qtit.com
             * SPN found :LDAP/PRIMARYDC
             * SPN found :LDAP/PRIMARYDC.Qtit.com/QTIT
             * SPN found :LDAP/e3d8c76c-1b59-4de6-9f7f-c438df9a2863._msdcs.Qtit.com
             * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/e3d8c76c-1b59-4de6-9f7f-c438df9a2863/Qtit.com
             * SPN found :HOST/PRIMARYDC.Qtit.com/Qtit.com
             * SPN found :HOST/PRIMARYDC.Qtit.com
             * SPN found :HOST/PRIMARYDC
             * SPN found :HOST/PRIMARYDC.Qtit.com/QTIT
             * SPN found :GC/PRIMARYDC.Qtit.com/Qtit.com
             ......................... PRIMARYDC passed test MachineAccount
          Starting test: NCSecDesc
             * Security Permissions check for all NC's on DC PRIMARYDC.
             The forest is not ready for RODC. Will skip checking ERODC ACEs.
             * Security Permissions Check for
               DC=ForestDnsZones,DC=Qtit,DC=com
                (NDNC,Version 3)
             Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have 
                Replicating Directory Changes In Filtered Set
             access rights for the naming context:
             DC=ForestDnsZones,DC=Qtit,DC=com
             * Security Permissions Check for
               DC=DomainDnsZones,DC=Qtit,DC=com
                (NDNC,Version 3)
             Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have 
                Replicating Directory Changes In Filtered Set
             access rights for the naming context:
             DC=DomainDnsZones,DC=Qtit,DC=com
             * Security Permissions Check for
               CN=Schema,CN=Configuration,DC=Qtit,DC=com
                (Schema,Version 3)
             * Security Permissions Check for
               CN=Configuration,DC=Qtit,DC=com
                (Configuration,Version 3)
             * Security Permissions Check for
               DC=Qtit,DC=com
                (Domain,Version 3)
             ......................... PRIMARYDC failed test NCSecDesc
          Starting test: NetLogons
             * Network Logons Privileges Check
             Verified share \\PRIMARYDC\netlogon
             Verified share \\PRIMARYDC\sysvol
             ......................... PRIMARYDC passed test NetLogons
          Starting test: ObjectsReplicated
             PRIMARYDC is in domain DC=Qtit,DC=com
             Checking for CN=PRIMARYDC,OU=Domain Controllers,DC=Qtit,DC=com in domain DC=Qtit,DC=com on 1 servers
                Object is up-to-date on all servers.
             Checking for CN=NTDS Settings,CN=PRIMARYDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com in domain CN=Configuration,DC=Qtit,DC=com on 1 servers
                Object is up-to-date on all servers.
             ......................... PRIMARYDC passed test ObjectsReplicated
          Test omitted by user request: OutboundSecureChannels
          Starting test: Replications
             * Replications Check
             * Replication Latency Check
                DC=ForestDnsZones,DC=Qtit,DC=com
                   Latency information for 18 entries in the vector were ignored.
                      18 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=Qtit,DC=com
                   Latency information for 18 entries in the vector were ignored.
                      18 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=Qtit,DC=com
                   Latency information for 20 entries in the vector were ignored.
                      20 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=Qtit,DC=com
                   Latency information for 20 entries in the vector were ignored.
                      20 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=Qtit,DC=com
                   Latency information for 20 entries in the vector were ignored.
                      20 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).  
             * Replication Site Latency Check 
             ......................... PRIMARYDC passed test Replications
          Starting test: RidManager
             * Available RID Pool for the Domain is 14607 to 1073741823
             * SecondAD.Qtit.com is the RID Master
             * DsBind with RID Master was successful
             * rIDAllocationPool is 14107 to 14606
             * rIDPreviousAllocationPool is 14107 to 14606
             * rIDNextRID: 14124
             ......................... PRIMARYDC 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
             ......................... PRIMARYDC passed test Services
          Starting test: SystemLog
             * The System Event log test
             A warning event occurred.  EventID: 0x0000A001
                Time Generated: 03/06/2014   16:04:05
                Event String:
                The Security System could not establish a secured connection with the server ldap/PRIMARYDC.Qtit.com/[email protected]. No authentication protocol was available.
             An error event occurred.  EventID: 0x0000041F
                Time Generated: 03/06/2014   16:06:35
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
                a) Name Resolution failure on the current domain controller. 
                b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
             An error event occurred.  EventID: 0x0000041F
                Time Generated: 03/06/2014   16:11:36
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
                a) Name Resolution failure on the current domain controller. 
                b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
             An error event occurred.  EventID: 0x0000041F
                Time Generated: 03/06/2014   16:16:38
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
                a) Name Resolution failure on the current domain controller. 
                b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
             An error event occurred.  EventID: 0x0000041F
                Time Generated: 03/06/2014   16:21:39
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
                a) Name Resolution failure on the current domain controller. 
                b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
             An error event occurred.  EventID: 0x0000041F
                Time Generated: 03/06/2014   16:26:41
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
                a) Name Resolution failure on the current domain controller. 
                b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
             An error event occurred.  EventID: 0x00000457
                Time Generated: 03/06/2014   16:30:46
                Event String:
                Driver TOSHIBA e-STUDIO16/20/25 PCL 6 required for printer TOSHIBA e-STUDIO16/20/25 PCL 6 is unknown. Contact the administrator to install the driver before you log in again.
             An error event occurred.  EventID: 0x00000457
                Time Generated: 03/06/2014   16:30:48
                Event String:
                Driver Microsoft XPS Document Writer v4 required for printer Microsoft XPS Document Writer is unknown. Contact the administrator to install the driver before you log in again.
             An error event occurred.  EventID: 0x00000457
                Time Generated: 03/06/2014   16:30:49
                Event String:
                Driver Send to Microsoft OneNote 15 Driver required for printer Send To OneNote 2013 is unknown. Contact the administrator to install the driver before you log in again.
             An error event occurred.  EventID: 0x00000457
                Time Generated: 03/06/2014   16:31:14
                Event String:
                Driver Send to Microsoft OneNote 15 Driver required for printer Send To OneNote 2013 is unknown. Contact the administrator to install the driver before you log in again.
             An error event occurred.  EventID: 0x00000457
                Time Generated: 03/06/2014   16:31:16
                Event String:
                Driver Microsoft XPS Document Writer v4 required for printer Microsoft XPS Document Writer is unknown. Contact the administrator to install the driver before you log in again.
             An error event occurred.  EventID: 0x00000457
                Time Generated: 03/06/2014   16:31:16
                Event String:
                Driver WebEx Document Loader required for printer WebEx Document Loader is unknown. Contact the administrator to install the driver before you log in again.
             An error event occurred.  EventID: 0x0000041F
                Time Generated: 03/06/2014   16:31:42
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
                a) Name Resolution failure on the current domain controller. 
                b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
             ......................... PRIMARYDC failed test SystemLog
          Test omitted by user request: Topology
          Test omitted by user request: VerifyEnterpriseReferences
          Starting test: VerifyReferences
             The system object reference (serverReference)
             CN=PRIMARYDC,OU=Domain Controllers,DC=Qtit,DC=com and backlink on
             CN=PRIMARYDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             are correct. 
             The system object reference (serverReferenceBL)
             CN=PRIMARYDC,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=Qtit,DC=com
             and backlink on
             CN=NTDS Settings,CN=PRIMARYDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             are correct. 
             The system object reference (frsComputerReferenceBL)
             CN=PRIMARYDC,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=Qtit,DC=com
             and backlink on CN=PRIMARYDC,OU=Domain Controllers,DC=Qtit,DC=com are
             correct. 
             ......................... PRIMARYDC passed test VerifyReferences
          Test omitted by user request: VerifyReplicas
          Test omitted by user request: DNS
          Test omitted by user request: DNS
       Running partition tests on : ForestDnsZones
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test
             CrossRefValidation
       Running partition tests on : DomainDnsZones
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test
             CrossRefValidation
       Running partition tests on : Schema
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
       Running partition tests on : Configuration
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
       Running partition tests on : Qtit
          Starting test: CheckSDRefDom
             ......................... Qtit passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Qtit passed test CrossRefValidation
       Running enterprise tests on : Qtit.com
          Test omitted by user request: DNS
          Test omitted by user request: DNS
          Starting test: LocatorCheck
             GC Name: \\PRIMARYDC.Qtit.com
             Locator Flags: 0xe00031fc
             PDC Name: \\SecondAD.Qtit.com
             Locator Flags: 0xe00001bd
             Time Server Name: \\PRIMARYDC.Qtit.com
             Locator Flags: 0xe00031fc
             Preferred Time Server Name: \\PRIMARYDC.Qtit.com
             Locator Flags: 0xe00031fc
             KDC Name: \\PRIMARYDC.Qtit.com
             Locator Flags: 0xe00031fc
             ......................... Qtit.com passed test LocatorCheck
          Starting test: Intersite
             Skipping site Default-First-Site-Name, this site is outside the scope
             provided by the command line arguments provided. 
             ......................... Qtit.com passed test Intersite
    repadmin /showrepl Result
    ******************************8
    ==== INBOUND NEIGHBORS ===================================
    DC=Qtit,DC=com
        Default-First-Site-Name\SECONDAD via RPC
            DSA object GUID: c5ef6e17-77f0-43f6-8d39-5497c563f
            Last attempt @ 2014-03-06 16:41:04 was successful.
    CN=Configuration,DC=Qtit,DC=com
        Default-First-Site-Name\SECONDAD via RPC
            DSA object GUID: c5ef6e17-77f0-43f6-8d39-5497c563f
            Last attempt @ 2014-03-06 16:41:39 was successful.
    CN=Schema,CN=Configuration,DC=Qtit,DC=com
        Default-First-Site-Name\SECONDAD via RPC
            DSA object GUID: c5ef6e17-77f0-43f6-8d39-5497c563f
            Last attempt @ 2014-03-06 15:53:01 was successful.
    DC=DomainDnsZones,DC=Qtit,DC=com
        Default-First-Site-Name\SECONDAD via RPC
            DSA object GUID: c5ef6e17-77f0-43f6-8d39-5497c563f
            Last attempt @ 2014-03-06 16:27:31 was successful.
    DC=ForestDnsZones,DC=Qtit,DC=com
        Default-First-Site-Name\SECONDAD via RPC
            DSA object GUID: c5ef6e17-77f0-43f6-8d39-5497c563f
            Last attempt @ 2014-03-06 15:53:01 was successful.
    I try to down the DC 2003 and access \\Qtit.com it success open the syslog on DC 2008
    Any help or advice 

    Hi,
    Were there other error codes logged in Event Viewer?
    Regarding Event ID 1055, the following article can be referred to for troubleshooting.
    Event ID 1055 — Group Policy Preprocessing (Security)
    http://technet.microsoft.com/en-us/library/cc727272(v=ws.10).aspx
    Based on the report you posted, this issue may be related to FRS replication service. As a result, we can use ntfrsutl tool to check whether the replication service is healthy.
    Regarding this point, the following articles can be referred to for more information.
    Troubleshooting File Replication Service
    http://technet.microsoft.com/en-us/library/bb727056.aspx
    Ntfrsutl
    http://technet.microsoft.com/en-us/library/hh875636.aspx
    In addition, we can also try doing a non-authoritative Sysvol restore on Windows Server 2008 DC to see whether the issue persists.
    Using the BurFlags registry key to reinitialize File Replication Service replica sets
    http://support.microsoft.com/kb/290762/en-us
    Hope it helps.
    Best regards,
    Frank Shen

Maybe you are looking for