Question

NTFRS messed up after 'Enable Journal Wrap Automatic Restore' - HELP !

Asked by: Eric_Gennaoui

Greeting dear Experts,

As I logged on our domain controller (server 2003 STD)  this morning, I noticed an NTFRS Journal Wrap Error (13568). After searching here and on MS websites, I followed the solution to add 'Enable Journal Wrap Automatic Restore'  DWORD to the registry, giving it a value of 1 and stop/start the NTFRS service.

Since then, my logs are filled with errors 1054, stating that 'Windows cannot obtain the domain controller name...' and I cant log on any machines using domain credentials. Its been 5 hours now since I tried the first solution but my NTFRS still did not came back. I am using RDP to the server and am afraid of doing a restart since its the only available connection atm and the office are closed for the weekend. I also had couple of errors 1030/1058 regarding GPOs before error 1054 appeared. This D.C is the only one available atm since we recently lost an SBS and I had to seize all FSMO roles to this server (let just say i had better months  :s).

When checking at the Debug Logs of NTFRS, I have errors stating :
WARN - No sysvol outbound connections found for member cn=ntds settings,cn=SERVERNAME,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=DOMAINNAME,dc=local!
<FrsDsGetSysvolInboundCxtions:  6196:  2706: S1: 15:47:38> :DS: WARN - No sysvol inbound connections found for object cn=ntds settings,cn=SERVERNAME,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=DOMAINNAME,dc=local!
<RcsCreateSeedingCxtion:        5368:  7087: S0: 15:47:38> :X: ERROR - no parent computer for DOMAIN SYSTEM VOLUME (SYSVOL SHARE) :  WStatus: ERROR_FILE_NOT_FOUND

Looking at my SYSVOL folder, I have 2 folders inside : one called 'NtFrs_PreExisting___See_EventLog' and 'DO_NOT_REMOVE_NtFrs_PreInstall_Directory', the last one beeing empty.

Anyone would know the best course of action to solve this problem, any input would be greatly appreciated as I'm not sure what to do next. Should I attempt a 'non authoritative FRS restore' or.... help  !

Best Regards,

Eric

This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.

Subscribe now for full access to Experts Exchange and get

Instant Access to this Solution

  • Plus...
  • 30 Day FREE access, no risk, no obligation
  • Collaborate with the world's top tech experts
  • Unlimited access to our exclusive solution database
  • Never be left without tech help again

Subscribe Now

Asked On
2009-09-19 at 13:39:00ID24745924
Tags

NTFRS

,

JOURNAL WRAP ERROR

Topics

Windows 2003 Server

,

Active Directory

,

Disaster Recovery

Participating Experts
2
Points
500
Comments
64

Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.

  • "The time we save is the biggest benefit of Experts Exchange to Warner Bros. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange." Mike Kapnisakis, Warner Bros.
  • "Our team likes having a resource that is more secure than just using Google and most experts using this service really know their stuff. It's nice to look here first versus using Google." Dayna Sellner, Lockheed Martin
  • "Anytime that I've been stumped with a problem, 9 out of 10 times Experts Exchange has either the accepted solution or an open discussion of the potential solution to the problem." Kenny Red, eBay Inc.

See what Experts Exchange can do for you.

Got a question?

We've got the answer.

Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.

Screenshot of Experts Exchange Knowledgebase

Need individual assistance?

Our experts are ready to help.

If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.

Screenshot of Experts Exchange Knowledgebase

Want to learn from the best?

Read articles from industry experts.

Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.

Screenshot of an Article

Working on a long term project?

Store your work and research.

Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.

Screenshot of Experts Exchange Knowledgebase

Access the answers to your technology questions today.

Subscribe Now

30-day free trial. Register in 60 seconds.

What Makes Experts Exchange Unique?

Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Trusted by the world's most respected brands.

image of each brand's logo

Faithfully serving IT professionals since 1996.

Experts Exchange Logo

Try it out and discover for yourself.

Subscribe Now

30-day free trial. Register in 60 seconds.

Related Solutions

  1. Problem with NTFRS - Missing Sysvol and Netlogon on a 2…
    I am having some apparently serious problems with a 2003 SBS server. We have just started the process of putting in a second Domain Controller into this network for a project. I performed the same task in a lab environment before I started on the live environment, and had n...
  2. Journal Wrap Errors on SBS 2003 server
    I have a SBS 2003 server and it is the only domain controller. We have 2 member terminal servers. I was reviewing the log files and found a13568 event id in the file replication service log. The server seems to be running fine and users are able to access shares, run login sc...
  3. Journal Wrap Error SBS + NTFRS Errors on addtional DC -…
    I'm preparing an SBS 2003 environment for migration to SBS 2008. I've got a Journal Wrap condition on the SBS server and journal errors on the member DC. The text indicates I need to do a non-authoritative replication, but I'm concerned as to which server I should do first...
  4. NTFRS ACTIVE DIRECTORY REPLICATION PROBLEM
    REPLICATION FAILED SYSVOL NOT SHARED IN NEWLY ADDED WINDOWS 2003 DOMAIN CONTROLLER NTFRS LOG FROM MY PDC AS BELOW
  5. Server in Journal Wrap
    I have read over many of the answers for Journal Wrap isues and performed the non-authoritative and authoritative reset on my SBS 2003 server and still get the journal wrap error. The C drive was low on disk space for a while, but I moved the Exchange files and have over 6 gb...
  6. NTFRS Journal Wrap Error
    I have 2 domain controllers. I have been getting the following 2 errors when attempting to apply group policy: Event Type: Error Event Source: Userenv Event Category: None Event ID: 1058 Date: Date Time: Time User: User_Name Computer: Computer_Name Description: Windows ...

Free Tech Articles

  1. WARNING: 5 Reasons why you should NEVER fix a computer for free.
    It is in our nature to love the puzzle. We are obsessed. The lot of us. We love puzzles. We love the challenge. We thrive on finding the answer. We hate disarray. It bothers us deep in our soul. W...
  2. SCCM OSD Basic troubleshooting
    SCCM 2007 OSD is a fantastic way to deploy operating systems, however, like most things SCCM issues can sometimes be difficult to resolve due to the sheer volume of logs to sift through and the dispe...
  3. Migrate Small Business Server 2003 to Exchange 2010 and Windows 2008 R2
    This guide is intended to provide step by step instructions on how to migrate from Small Business Server 2003 to Windows 2008 R2 with Exchange 2010. For this migration to work you will need the fo...
  4. Create a Win7 Gadget
    This article shows you how to create a simple "Gadget" -- a sort of mini-application supported by Windows 7 and Vista. Gadgets can be dropped anywhere on the desktop to provide instant information, ...
  5. Outlook continually prompting for username and password
    There have been a lot of questions recently regarding Outlook prompting for a username and password whilst using Exchange 2007. There are a few reasons why this would happen and I will try to cover t...
  6. Backup Exchange 2010 Information Store using Windows Backup
    There seems to be quite a lot of confusion around the ability to backup Exchange 2010 using the built in Windows Backup feature. This stems from the omission of this feature prior to Exchange 2007 s...

Cloud Class Webinars

  1. Avoiding Bugs in Microsoft Access
    Alison Balter takes and in-depth look at avoiding bugs in Access. In this webinar you will learn about using the immediate window to debug your applications, invoking the debugger, using breakpoints to troubleshoot, stepping through code, setting the next statement to execute, ...
  2. Top 10 Best New Features in Visio 2010
    Scott Helmers gives live demonstrations of the top 10 new features in Visio 2010. This webinar will teach you how to create compelling diagrams by adding shapes to the page with a single click, linking the shapes in a diagram to data in Excel (or SQL Server, or SharePoint), ...
  3. IT Consultant Business Secrets Revealed
    Michael Munger, Experts Exchange tech pro and IT consultant, pulls back the curtain on his very successful businesses and answers question on every IT consultant and business owner should know about. He shares secrets on what he did to solve the 5 most common problems in IT, ...
  4. Disaster Recovery and Business Continuity
    Quest CTO, Mike Billon, gives an overview of the steps involved in building a dunamic disaster recovery plan. Through case studies and an examination of software/hardware tooles for monitoring and testing, you'll gain a better understandin of where you are, where you want ...
  5. Organize Your Visio Diagrams with Containers and Lists
    Scott Helmers uses cross functional flowcharts, wireframe diagrams, data graphic legends and seating charts to teach you: how to ustilize all three new structured diagram components in Visio 2010, the best practices for organizeing shapes in previous version of Visio, how to organize ...
  6. How to Us Objects, Properties, Events and Methods in Microsoft Access
    Alison Dalter gives an in-depbth look at objects, properties, events and methods in Microsoft Access. In this webinar you will learn about using the object browser, referring to objects, working with properties and methods, working with object variables, understanding the ...

Join the Community

Give a Little. Get a Lot.

Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.

Join the Community

Answers

 

by: wantabe2Posted on 2009-09-19 at 15:49:39ID: 25375072

1. Stop FRS.
 
2. Start Registry Editor (Regedt32.exe).
 
3. Locate and click the following key in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore/Process at Startup
 
4. On the Edit menu, click Add Value , and then add the following registry value:

Value name: BurFlags
Data type: REG_DWORD
Radix: Hexadecimal
Value data: D2
 
5. Quit Registry Editor.
 
6. Restart FRS.

Use the tool FRSDIAG to verify that all DC's will replicate the SYSVOL contents and created a test file to verify propagation to all DC's. You can also verified the consistency of the SYSVOL contents across all of the DC's using the GPOTOOL resource kit utility.
 

 

by: Eric_GennaouiPosted on 2009-09-19 at 16:57:33ID: 25375340


Thanks for your quick reply Wantabe2

I applied your solution and NTFRS started working again !
However, I now have an error 5706 regarding NETLOGON as the server 'could not create the SCRIPT folder in SYSVOL' (cannot find the file specified)  and still have some 1030/1058 GPO errors as well. After using FRSdiag, all went ok xcept for the NETLOGON.

I went to the C:\WINDOWS\SYSVOL\sysvol\domain'  but there is nothing else than the folder called 'DO_NOT_REMOVE_NTfrs_PREinstall_Directory'.

Should I just restart the server or should I take other actions ?

Many thanks in advance

Eric

 

by: wantabe2Posted on 2009-09-19 at 19:07:38ID: 25375642

Great! Restarting shoudl be fine but please remember anytime you see Journal Wrap Error on a DC usually somethiing really bad has happened...it basically means the DC sees all the changes that needs to take place such as sysvol changes, FRS changes, etc., but it don't know what to do with it. At this point I'd reboot & see what happens after the DCs has sat around long enough to replicate. Keep us updated.

 

by: Eric_GennaouiPosted on 2009-09-19 at 22:37:00ID: 25375994


I was about to restart the server as suggested but another question popped in my mind (damn me!)

Reading article kb290762 about the steps I've taken so far, I fumbled on a note (quoting a part of it) :
"....Any files destined for the replica that exist only in the local Pre-existing folder and did not replicate in after the initial replication may then be copied to the appropriate folder..."

My question is since I don't have that 'Pre-existing directory' anymore, only empty 'Pre-install  directory', should I attempt to restore my System State from backups (either ntbackup or backup exec, I have both) to alternate location and copy back sysvol's folders ? Or does the restart going to take care of all that (that's where I doubt) ?

Thanking you again for your kind patience sir !


 

by: ChiefITPosted on 2009-09-20 at 01:57:41ID: 25376362

You must fix DNS first:

1030 and 1058 are symptoms of a problem. MOST LIKELY DNS.

1054, the inability to contact the domain is also a DNS problem.

DO NOT RUN THE BURFLAG METHOD UNTIL DNS IS FIXED.

On the computer having problems, let's find out why its failing to see the SRV records within DNS.

Go to the command prompt and type. IPconfig /all  Please provide that to us so we can get a feel for the networking involved.

Look in the DNS forward lookup zones for a problem with DNS. Look for greyed out folders and see if the MSDCS file folder exists.

Go to the command prompt and type, DCdiag /fix:DNS

Then, run DCdiag /v to show us the errors in DNS.

Also look in event logs for any DNS errors.

 

by: Eric_GennaouiPosted on 2009-09-20 at 07:53:14ID: 25377425

Hello ChiefIT, thanks for hoping in,

I did not know I had to 'fix DNS' before attempting the BurFlag method. However, my DNS neve gave me a hint of nay problems (in event viewers). BUT....as you mentionned, it looks like I had in fact a greyed out _msdtc folder and inside, was a wrong entry relating to an old DNS we recently lost.

Here is my Ipconfig /all result :

Windows IP Configuration

  Host Name . . . . . . . . . . . . : FS1
  Primary Dns Suffix  . . . . . . . : domainname.local
  Node Type . . . . . . . . . . . . : Unknown
  IP Routing Enabled. . . . . . . . : No
  WINS Proxy Enabled. . . . . . . . : No
  DNS Suffix Search List. . . . . . : domainname.local

Ethernet adapter Local Area Connection 2:

  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : HP NC373i Multifunction Gigabit Server Ad
apter #2
  Physical Address. . . . . . . . . : 00-xx-xx-xx-xx-56
  DHCP Enabled. . . . . . . . . . . : No
  IP Address. . . . . . . . . . . . : 192.168.0.250
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Default Gateway . . . . . . . . . : 192.168.0.1
  DNS Servers . . . . . . . . . . . : 192.168.0.250

Trying dcdiag /fix:dns  always tell me 'Invalid Option'. I then ran dcdiag /v and heres the result (next post):

 

by: Eric_GennaouiPosted on 2009-09-20 at 07:55:24ID: 25377436

Domain Controller Diagnosis

Performing initial setup:
* Verifying that the local machine FS1, is a DC.
* Connecting to directory service on server FS1.
* Collecting site info.
* Identifying all servers.
* Identifying all NC cross-refs.
* Found 1 DC(s). Testing 1 of them.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\FS1
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... FS1 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\FS1
Starting test: Replications
* Replications Check
* Replication Latency Check
DC=ForestDnsZones,DC=domainname,DC=local
Latency information for 1 entries in the vector were ignored.
1 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=domainname,DC=local
Latency information for 1 entries in the vector were ignored.
1 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=domainname,DC=local
Latency information for 1 entries in the vector were ignored.
1 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=domainname,DC=local
Latency information for 1 entries in the vector were ignored.
1 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=domainname,DC=local
Latency information for 1 entries in the vector were ignored.
1 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
......................... FS1 passed test Replications
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Starting test: NCSecDesc
* Security Permissions check for all NC's on DC FS1.
* Security Permissions Check for DC=ForestDnsZones,DC=domainname,DC=local (NDNC,Version 2)
* Security Permissions Check for DC=DomainDnsZones,DC=domainname,DC=local (NDNC,Version 2)
* Security Permissions Check for CN=Schema,CN=Configuration,DC=domainname,DC=local (Schema,Version 2)
* Security Permissions Check for CN=Configuration,DC=domainname,DC=local (Configuration,Version 2)
* Security Permissions Check for DC=domainname,DC=local (Domain,Version 2)
......................... FS1 passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
Unable to connect to the NETLOGON share! (\\FS1\netlogon)
[FS1] An net use or LsaPolicy operation failed with error 1203, No network provider accepted the given network path..
......................... FS1 failed test NetLogons
Starting test: Advertising
The DC FS1 is advertising itself as a DC and having a DS.
The DC FS1 is advertising as an LDAP server
The DC FS1 is advertising as having a writeable directory
The DC FS1 is advertising as a Key Distribution Center
The DC FS1 is advertising as a time server
The DS FS1 is advertising as a GC.
......................... FS1 passed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS Settings,CN=FS1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domainname,DC=local
Role Domain Owner = CN=NTDS Settings,CN=FS1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domainname,DC=local
Role PDC Owner = CN=NTDS Settings,CN=FS1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domainname,DC=local
Role Rid Owner = CN=NTDS Settings,CN=FS1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domainname,DC=local
Role Infrastructure Update Owner = CN=NTDS Settings,CN=FS1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domainname,DC=local
......................... FS1 passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 4107 to 1073741823
* FS1.domainname.local is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 3107 to 3606
* rIDPreviousAllocationPool is 3107 to 3606
* rIDNextRID: 3111
......................... FS1 passed test RidManager
Starting test: MachineAccount
Checking machine account for DC FS1 on DC FS1.
* SPN found :LDAP/FS1.domainname.local/domainname.local
* SPN found :LDAP/FS1.domainname.local
* SPN found :LDAP/FS1
* SPN found :LDAP/FS1.domainname.local/domainname
* SPN found :LDAP/20f9efb7-be68-4e89-a7d1-afbe84945379._msdcs.domainname.local
* SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/20f9efb7-be68-4e89-a7d1-afbe84945379/domainname.local
* SPN found :HOST/FS1.domainname.local/domainname.local
* SPN found :HOST/FS1.domainname.local
* SPN found :HOST/FS1
* SPN found :HOST/FS1.domainname.local/domainname
* SPN found :GC/FS1.domainname.local/domainname.local
......................... FS1 passed test MachineAccount
Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: w32time
* Checking Service: NETLOGON
......................... FS1 passed test Services
Test omitted by user request: OutboundSecureChannels
Starting test: ObjectsReplicated
FS1 is in domain DC=domainname,DC=local
Checking for CN=FS1,OU=Domain Controllers,DC=domainname,DC=local in domain DC=domainname,DC=local on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=FS1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domainname,DC=local in domain CN=Configuration,
DC=domainname,DC=local on 1 servers
Object is up-to-date on all servers.
......................... FS1 passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... FS1 passed test frssysvol
Starting test: frsevent
* The File Replication Service Event log test
......................... FS1 passed test frsevent
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory Service Event log in the last 15 minut
es.
......................... FS1 passed test kccevent
Starting test: systemlog
* The System Event log test
An Error Event occured. EventID: 0xC0000411
Time Generated: 09/20/2009 10:16:24
(Event String could not be retrieved)
An Error Event occured. EventID: 0x0000164A
Time Generated: 09/20/2009 10:31:08
Event String: The Netlogon service could not create server
share
C:\WINDOWS\SYSVOL\sysvol\domainname.local\SCRIPTS.
The following error occurred:
%%2
......................... FS1 failed test systemlog
Test omitted by user request: VerifyReplicas
Starting test: VerifyReferences
The system object reference (serverReference) CN=FS1,OU=Domain Controllers,DC=domainname,DC=local and backlink on CN=FS1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration, DC=domainname,DC=local are correct.
The system object reference (frsComputerReferenceBL) CN=FS1,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=domainname,DC=local and backlink on CN=FS1,OU=Domain Controllers,DC=domainname,DC=local are correct.
The system object reference (serverReferenceBL) CN=FS1,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=domainname,DC=local and backlink on CN=NTDS Settings,CN=FS1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,
CN=Configuration,DC=domainname,DC=local are correct.
......................... FS1 passed test VerifyReferences
Test omitted by user request: VerifyEnterpriseReferences
Test omitted by user request: CheckSecurityError

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation

Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation

Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom

Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom

Running partition tests on : domainname
Starting test: CrossRefValidation
......................... domainname passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... domainname passed test CheckSDRefDom

Running enterprise tests on : domainname.local
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope
provided by the command line arguments provided.
......................... domainname.local passed test Intersite
Starting test: FsmoCheck
GC Name: \\FS1.domainname.local
Locator Flags: 0xe00003fd
PDC Name: \\FS1.domainname.local
Locator Flags: 0xe00003fd
Time Server Name: \\FS1.domainname.local
Locator Flags: 0xe00003fd
Preferred Time Server Name: \\FS1.domainname.local
Locator Flags: 0xe00003fd
KDC Name: \\FS1.domainname.local
Locator Flags: 0xe00003fd
......................... domainname.local passed test FsmoCheck
Test omitted by user request: DNS
Test omitted by user request: DNS


My DNS event viewers still dont show me any errors, even after I corrected the wrong entry in folder _msdcs (sorry for the typo on previous post) and I restarted the DNS service.

 

by: ChiefITPosted on 2009-09-20 at 10:45:17ID: 25378081

This is what I am thinking:

It looks like you may have a bad delegation record in DNS. This happens because Microsoft created a delegation record within your forward lookup zone, then created a separate forward lookup zone for your SRV records.

The design of this was to allow easy replications for a domain/forest combination. When DNS replicates throughout the forest it made it easier for the forest domain to replicate the Forward lookup zone called MSDCS.yourdomain.local.

The problem with this setup is the delegation records don't dynamically updated. So, without that delegation record, your servers can't see the real MSDCS file folder that hold the SRV records.

I believe you may have a flat domain. So, we can delete both the delegation record as well as the SRV records. Then, we can re-register the SRV records to have them put back where they belong. That would be under your forward lookup zone in DNS.

I am going to give  you an example of what I think you are seeing. If this is the case, follow Chris Dent and Dariusq's advice on how to fix this by deleting the two file folders with MSDCS records in them.

You have to do this on all DCs. Then, you can re-register the file folders by going to the command prompt and typing Net Stop Netlogon and Net Start Netlogon.

http://www.experts-exchange.com/Networking/Protocols/DNS/Q_24349599.html

Once done. Go into Active Directory Sites and services and attempt to force replicate. If that doesn't work, then restart the FRS service and again try to force replicate. If that doesn't work, we need to find out what machine is in journal wrap, then use the burflag method to rebuild the sysvol and netlogon shares on that machine only.

 

by: ChiefITPosted on 2009-09-20 at 10:47:32ID: 25378110

One other thing:

I see you only have ONE preferred DNS server:

IP Address. . . . . . . . . . . . : 192.168.0.250
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.1
   DNS Servers . . . . . . . . . . . : 192.168.0.250<<<<<

This is fine if you have a one DC domain with DNS. If you have two DCs, it would be a good idea to add the second as a secondary preferred DNS server on the NIC so they see each other. The DCs use the preferred DNS servers to help them replicate.

 

by: Eric_GennaouiPosted on 2009-09-20 at 11:22:41ID: 25378325


I will try Chris Dent and Dariusq's advices but I unfortunately cant do it until monday or tuesday for some reasons out of my control. Be sure I will get back to you with results.

I'm presently having only one preferred DNS server for the reason with recently lost our main DNS server and this one had to be promoted to primary DNS and I'm in the process of building a new server to be the backup/secondary dns.

Thanks again for all your patience and I will get back to all of you as soon as I can try your advices (Dent's, Dariusq's and ChefIT's)

Regards

 

by: ChiefITPosted on 2009-09-20 at 11:45:32ID: 25378431

I had a feeling you were going to say there was a retired DC in the mix. I wasn't sure if that was a retired DC or simply a DC that's past its tombstone lifetime of 30 days. In your case, Things will be pretty easy if you follow the steps in correct sequence.

We will need to perform metadata cleanup prior to doing anything.

It looks like you have all five FSMO Roles. So, all you have to do is a metadata cleanup. I do see some residue of a retired DC in your DCdiag.

Metadata cleanup will include:


1) DNS metadata
2) AD metadata
3) FRS metadata

(in that order)
The best article to guide you through all three steps is this one:
http://www.petri.co.il/delete_failed_dcs_from_ad.htm

For DNS metadata, follow Chris Dent's and Dariusq's advice of removing the MSDCS file folders and restarting the Netlogon service. Then, remove the old DC's reverse lookup in_address_arpa, and forward lookup zone host records, to be thurough.

For AD metadata, follow the information on Petri's site. I don't expect there to be any AD metadata. But, we need to check.

For FRS metadata, follow the info on Petri's site.

Perform metadata cleanup on this DC, then again run the dcidag to see if there are any more errors. Also see if 1030 and 1058 event errors have stopped and make sure group policies are working on the clients/servers.
_______________________________________________________________________________
I will assist through the implimentation of your new DC. There are a few things you have to be looking out for when promoting and replicating across DCs.

 

by: Eric_GennaouiPosted on 2009-09-20 at 12:13:33ID: 25378537


Yeah it is a D.C (SBS 2003)  we lost because of bad hardware failure  ;(

I already did the Active Directory Meta-Data Cleanup few days ago removing entries of the failed D.C and then manually deleted entries in DNS afterward pointing to it (guess that was ma mistake). I didn't know there was a possibility of doing DNS and FRS metadata cleanup.

It looks like I had left the entry of the failed DNS in the _msdc 'grey folder' but corrected it manually before you posted your last comment (previous), hope this wont mess up the course of action.

Cant wait  to be able to try those solution on monday/tuesday and I greatly appreciate your detailed answers/advices !

 

by: wantabe2Posted on 2009-09-20 at 12:36:12ID: 25378620

Let us know how it rurns out..

 

by: Eric_GennaouiPosted on 2009-09-21 at 21:01:55ID: 25389407


**Updates**

Tuesday is coming and I will finally be on site. A thing or two stills bugs me before I do any cleanup attempts, bear with me pease, I dont have full control over the situation.

I was asked by my authorites if I could create a Virtual Machine and make it as a Secondary D.C / DNS before attempting anything on the actual server (since its our last atm). I told them I would not recommend playing with the A.D/DNS structure while its in this state but im asking the question to make sure there is no possibility.

Also the 'BurFlag method' unfortunately, was attempted when Wantabe2 answered my post (before ChiefIT hoped in), so its been done before the DNS/FRS cleanup.... but its the only reason I think the domain is still up and running, because error 1054 disapeared at that time and users could then log on . Now my only other concern is will it affect my upcoming A.D/DNS/FRS metadata cleanup; and in the meantime, is it safe to reboot the server ?

Warms Regards

 

by: ChiefITPosted on 2009-09-22 at 03:01:11ID: 25391032

Metadata is defined as garbage data from a domain controller that no longer exists.

That data goes through four stages of deletion. (google search, "phantoms tombstones and the active directory infrastructure")

As it stands Metadata cleanup is safe because you are cleaning up the data left over from the improperly deleted server. It is also necessary to clean this data up so your clients are not having problems with a server that doesn't exist. Unless you perform metadata cleanup of the wrong server, you are safe if you follow the steps in the petri article.  

--You have no sites to replicate with. So, since it is trying to replicate you have FRS metadata.

--You also seem to have DNS metadata, because some clients are not seeing the authentication server. DNS rebuilds dynamically. So removing zones or removing the MSDCS records will be a good cleanup process. After you delete the MSDCS file folders in the DNS forward lookup zone, and then restart the netlogon process, your SRV records will be cleaned of the old server. That serves two purposes. It will remove the delegation records, (that DON'T dynamically update in DNS), and clean up DNS SRV records of the old server. So, follow Dariusq and Chris Dent's advice on this cleanup process.  

--I do believe you already removed, the AD metadata. Your server knows of the five FSMO roles and you are not getting a DCgetname error in your DCdiag. But, it doesn't hurt to doublecheck AD for metadata and remove it if necessary.

In this state, another server will not be able to join as an AD server, It will not be able to replicate. Nor will it be able to authenticate with this troubled other server. So, another server will NOT work right, and it will be further detrimental to the state of this domain.

I do understand their concerns. If, you are concerned about these fixes. The best disaster recovery recommendation I can make is to create a True Image Backup of the server. But, I am 100% positive you will not have any problems if you perform metadata cleanup as directed by the Petri article as well as fix DNS as Dariusq and Chris Dent described.  


 

by: Eric_GennaouiPosted on 2009-09-22 at 11:56:54ID: 25396198


**Updates**

2 more hours till I can begin the cleaning process, I just wanted to make sure I understood all the steps :

1. Delete both : ' _msdcs.domain.local' AND  'domain.local'  zones   <---- (Making sure for this one)
2. Recreate 'domain.local' zone from scratch, make sure its A.D integrated
3. Perform A.D Metadata cleanup and then FRS cleanup.
4. Stop and Restart the netlogon service, make sure errors in event viewers disappeared.
5. Reboot

Are these steps correct or did I missed somehting, and should I still need the 'BurFlag Merthod' again after the process?

Regards

 

by: ChiefITPosted on 2009-09-22 at 12:02:30ID: 25396258

1. Delete both : ' _msdcs.domain.local' AND  'domain.local'  zones   <---- (Making sure for this one)
2. Recreate 'domain.local' zone from scratch, make sure its A.D integrated
(To do this, all you have to do is go to the command prompt and type, Net Stop Netlogon and Net Start Netlogon)
3. Perform A.D Metadata cleanup and then FRS cleanup.
(AD may already be clean, Yes you need FRS metadata cleanup.)
4. Stop and Restart the netlogon service, make sure errors in event viewers disappeared.
(Restarting the Netlogon should be for Number 2)
(You might go to the command prompt and also type IPconfig /flushdns to flush the DNS cache of any bad records)
5. Reboot
(Yes, reboot)

(6) Run an DCdiag /v to look at the progress. Clean system logs as you see fit by clearing the events.

 

by: Eric_GennaouiPosted on 2009-09-22 at 12:15:13ID: 25396401


Ok i see....I was confused by whether I should delete the whole 'domain.local' zone or only the *greyed-out   _msdcs folder* IN that zone.

Seeing your post I feel confident to completely remove and delete both zones...though I cant understand how doing a Netlogon stop/restart can 'recreate' my primary forward zone.... But I should have enough advices now to proceed.

Pray for me pretty plz  and God bless you ALL   ;)

 

by: ChiefITPosted on 2009-09-22 at 13:09:52ID: 25397040

There are two MSDCS file folders. One is under your forward lookup zone for the domain. That is the delegation record. That delegates or basically points to the MSDCS.domain.local file folder. Within that folder you will see your SRV records.

You want to delete both MSDCS file folder under Your Domain's Forward lookup zone. Then, delete the MSDCS forward lookup zone. In other words, to be explicit, delete both MSDCS file folders, NOT your domain's forward lookup zone. After doing so, go to the command prompt and type Net stop Netlogon. After doing so, you will see that ONE MSDCS file folder will re-appear. That MSDCS file folder will be located under your forward lookup zone and will have all SRV records in it. What this does is removes the delegation record that doesn't dynamically update and moves your SRV records into your forward lookup zone. It also deletes any SRV records for the old retired DC, that are causing you problems.

DON'T delete your fwd lookup zone, just the MSDCS file folders. One is in your fwd lookup zone, the other is its own fwd lookup zone.

 

by: Eric_GennaouiPosted on 2009-09-22 at 13:37:08ID: 25397322


ooo I think I undertand now (sorry for beeing so slow), so looking at this picture and understanding previous post, I will delete that "greyed-out _msdcs" folder in my "domain.local" ZONE and the "_msdcs.domain.local" ZONE....correct ?

 

by: ChiefITPosted on 2009-09-22 at 14:18:03ID: 25397715

Correct.

Immediately after doing so, go to the command prompt and type:

Ipconfig /flushdns
Net stop netlogon
Net start netlogon
IPconfig /registerdns

That should unhose DNS.

 

by: ChiefITPosted on 2009-09-22 at 14:20:25ID: 25397741

Then, you can go to FRS and AD metadata cleanup as described by the Petri article:

Once again, I don't believe you have AD metadata. I am certain you have FRS metadata.

Once done with FRS and AD metadata, reboot, logon, go to the DNS snap in and make sure you have a single MSDCS file folder under your FWD lookup zone. If so, go to the command prompt and type DCdiag /v, to look at the system's diagnostic utility.

 

by: Eric_GennaouiPosted on 2009-09-22 at 14:42:18ID: 25397905


**Updates**

Ok, I just deleted the _msdcs (greyed-out) under my domain.local zone and deleted the _msdcs.domain.local zone. I flushed DNS and restarted the Netlogon service. But when I am trying to do ipconfig /registerdns, I have an error :
"Registration of DNS records failed: The RPC server is unavailable."

Also when checking at my event viewer, I just got an error 5706 : "The Netlogon service could not create server share C:\WINDOWS\SYSVOL\sysvol\domain.local\SCRIPTS.  The following error occurred:
The system cannot find the file specified."

I hope this is normal....I'll continue with the Metadata Cleanup in the meantime.

Eric

 

by: Eric_GennaouiPosted on 2009-09-22 at 15:52:15ID: 25398347


OK..... I just rebooted...

Now the _msdcs is correctly registered under my zone 'domain.local' (see dns-2.jpeg). This solve the DNS issue. I dont have any Metadata left from the old file server, beeing A.D or FRS, another good thing !

I tried logging on as a user no the domain and the authentication seems ok too, I could browse the network and get on the file server without problem, as well as getting on the internet...we are getting close !

BUT....I still do have some  1030 / 1058 errors; probably because I dont have the folders called 'SCRIPT' and 'POLICIES' in my C:\WINDOWS\SYSVOL\sysvol\domain.local anymore..... (see error 1030/1058 .jpeg)

i ran a DCdiag and heres the result  (Next Post) :

 

by: Eric_GennaouiPosted on 2009-09-22 at 15:56:40ID: 25398387

DCDIAG after :

C:\>dcdiag /v

Domain Controller Diagnosis

Performing initial setup:
   * Verifying that the local machine FS1, is a DC.
   * Connecting to directory service on server FS1.
   * Collecting site info.
   * Identifying all servers.
   * Identifying all NC cross-refs.
   * Found 1 DC(s). Testing 1 of them.
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\FS1
      Starting test: Connectivity
         * Active Directory LDAP Services Check
         * Active Directory RPC Services Check
         ......................... FS1 passed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\FS1
      Starting test: Replications
         * Replications Check
         * Replication Latency Check
            DC=ForestDnsZones,DC=domain,DC=local
               Latency information for 1 entries in the vector were ignored.
                  1 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=domain,DC=local
               Latency information for 1 entries in the vector were ignored.
                  1 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=domain,DC=local
               Latency information for 1 entries in the vector were ignored.
                  1 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=domain,DC=local
               Latency information for 1 entries in the vector were ignored.
                  1 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=domain,DC=local
               Latency information for 1 entries in the vector were ignored.
                  1 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
         ......................... FS1 passed test Replications
      Test omitted by user request: Topology
      Test omitted by user request: CutoffServers
      Starting test: NCSecDesc
         * Security Permissions check for all NC's on DC FS1.
         * Security Permissions Check for
           DC=ForestDnsZones,DC=domain,DC=local
            (NDNC,Version 2)
         * Security Permissions Check for
           DC=DomainDnsZones,DC=domain,DC=local
            (NDNC,Version 2)
         * Security Permissions Check for
           CN=Schema,CN=Configuration,DC=domain,DC=local
            (Schema,Version 2)
         * Security Permissions Check for
           CN=Configuration,DC=domain,DC=local
            (Configuration,Version 2)
         * Security Permissions Check for
           DC=domain,DC=local
            (Domain,Version 2)
         ......................... FS1 passed test NCSecDesc
      Starting test: NetLogons
         * Network Logons Privileges Check
         Unable to connect to the NETLOGON share! (\\FS1\netlogon)
         [FS1] An net use or LsaPolicy operation failed with error 1203, No netw
ork provider accepted the given network path..
         ......................... FS1 failed test NetLogons
      Starting test: Advertising
         The DC FS1 is advertising itself as a DC and having a DS.
         The DC FS1 is advertising as an LDAP server
         The DC FS1 is advertising as having a writeable directory
         The DC FS1 is advertising as a Key Distribution Center
         The DC FS1 is advertising as a time server
         The DS FS1 is advertising as a GC.
         ......................... FS1 passed test Advertising
      Starting test: KnowsOfRoleHolders
         Role Schema Owner = CN=NTDS Settings,CN=FS1,CN=Servers,CN=Default-First
-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=local
         Role Domain Owner = CN=NTDS Settings,CN=FS1,CN=Servers,CN=Default-First
-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=local
         Role PDC Owner = CN=NTDS Settings,CN=FS1,CN=Servers,CN=Default-First-Si
te-Name,CN=Sites,CN=Configuration,DC=domain,DC=local
         Role Rid Owner = CN=NTDS Settings,CN=FS1,CN=Servers,CN=Default-First-Si
te-Name,CN=Sites,CN=Configuration,DC=domain,DC=local
         Role Infrastructure Update Owner = CN=NTDS Settings,CN=FS1,CN=Servers,C
N=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=local
         ......................... FS1 passed test KnowsOfRoleHolders
      Starting test: RidManager
         * Available RID Pool for the Domain is 4107 to 1073741823
         * FS1.domain.local is the RID Master
         * DsBind with RID Master was successful
         * rIDAllocationPool is 3107 to 3606
         * rIDPreviousAllocationPool is 3107 to 3606
         * rIDNextRID: 3111
         ......................... FS1 passed test RidManager
      Starting test: MachineAccount
         Checking machine account for DC FS1 on DC FS1.
         * SPN found :LDAP/FS1.domain.local/domain.local
         * SPN found :LDAP/FS1.domain.local
         * SPN found :LDAP/FS1
         * SPN found :LDAP/FS1.domain.local/domain
         * SPN found :LDAP/20f9efb7-be68-4e89-a7d1-afbe84945379._msdcs.domain
.local
         * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/20f9efb7-be68-4e89-a7
d1-afbe84945379/domain.local
         * SPN found :HOST/FS1.domain.local/domain.local
         * SPN found :HOST/FS1.domain.local
         * SPN found :HOST/FS1
         * SPN found :HOST/FS1.domain.local/domain
         * SPN found :GC/FS1.domain.local/domain.local
         ......................... FS1 passed test MachineAccount
      Starting test: Services
         * Checking Service: Dnscache
         * Checking Service: NtFrs
         * Checking Service: IsmServ
         * Checking Service: kdc
         * Checking Service: SamSs
         * Checking Service: LanmanServer
         * Checking Service: LanmanWorkstation
         * Checking Service: RpcSs
         * Checking Service: w32time
         * Checking Service: NETLOGON
         ......................... FS1 passed test Services
      Test omitted by user request: OutboundSecureChannels
      Starting test: ObjectsReplicated
         FS1 is in domain DC=domain,DC=local
         Checking for CN=FS1,OU=Domain Controllers,DC=domaine,DC=local in dom
ain DC=domain,DC=local on 1 servers
            Object is up-to-date on all servers.
         Checking for CN=NTDS Settings,CN=FS1,CN=Servers,CN=Default-First-Site-N
ame,CN=Sites,CN=Configuration,DC=domain,DC=local in domain CN=Configuration,
DC=domain,DC=local on 1 servers
            Object is up-to-date on all servers.
         ......................... FS1 passed test ObjectsReplicated
      Starting test: frssysvol
         * The File Replication Service SYSVOL ready test
         File Replication Service's SYSVOL is ready
         ......................... FS1 passed test frssysvol
      Starting test: frsevent
         * The File Replication Service Event log test
         ......................... FS1 passed test frsevent
      Starting test: kccevent
         * The KCC Event log test
         Found no KCC errors in Directory Service Event log in the last 15 minut
es.
         ......................... FS1 passed test kccevent
      Starting test: systemlog
         * The System Event log test
         An Error Event occured.  EventID: 0x0000164A
            Time Generated: 09/22/2009   17:35:33
            Event String: The Netlogon service could not create server
share
C:\WINDOWS\SYSVOL\sysvol\domain.local\SCRIPTS.
  The following error occurred:
%%2
         An Error Event occured.  EventID: 0x0000164A
            Time Generated: 09/22/2009   18:22:12
            Event String: The Netlogon service could not create server
share
C:\WINDOWS\SYSVOL\sysvol\domain.local\SCRIPTS.
  The following error occurred:
%%2
         ......................... FS1 failed test systemlog
      Test omitted by user request: VerifyReplicas
      Starting test: VerifyReferences
         The system object reference (serverReference)
         CN=FS1,OU=Domain Controllers,DC=domain,DC=local and backlink on
         CN=FS1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,
DC=domain,DC=local
         are correct.
         The system object reference (frsComputerReferenceBL)
         CN=FS1,CN=Domain System Volume (SYSVOL share),CN=File Replication Servi
ce,CN=System,DC=domain,DC=local
         and backlink on CN=FS1,OU=Domain Controllers,DC=domain,DC=local
         are correct.
         The system object reference (serverReferenceBL)
         CN=FS1,CN=Domain System Volume (SYSVOL share),CN=File Replication Servi
ce,CN=System,DC=domain,DC=local
         and backlink on
         CN=NTDS Settings,CN=FS1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,
CN=Configuration,DC=domain,DC=local
         are correct.
         ......................... FS1 passed test VerifyReferences
      Test omitted by user request: VerifyEnterpriseReferences
      Test omitted by user request: CheckSecurityError

   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom

   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom

   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom

   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom

   Running partition tests on : domain
      Starting test: CrossRefValidation
         ......................... domain passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... domain passed test CheckSDRefDom

   Running enterprise tests on : domain.local
      Starting test: Intersite
         Skipping site Default-First-Site-Name, this site is outside the scope
         provided by the command line arguments provided.
         ......................... domain.local passed test Intersite
      Starting test: FsmoCheck
         GC Name: \\FS1.domain.local
         Locator Flags: 0xe00003fd
         PDC Name: \\FS1.domain.local
         Locator Flags: 0xe00003fd
         Time Server Name: \\FS1.domain.local
         Locator Flags: 0xe00003fd
         Preferred Time Server Name: \\FS1.domain.local
         Locator Flags: 0xe00003fd
         KDC Name: \\FS1.domain.local
         Locator Flags: 0xe00003fd
         ......................... domain.local passed test FsmoCheck
      Test omitted by user request: DNS
      Test omitted by user request: DNS

Now I am wondering if I should create manually those 'SCRIPT' and 'POLICIES' folders or should I try to restore them with a valid backup......must admit I dont have a clue....I did not have any scripts or policies done manually, all were generated by the server I guess...

Eric

 

by: ChiefITPosted on 2009-09-22 at 17:12:18ID: 25398926

Once again restart the netlogon service from the command prompt. Then, run a DCdiag /v. If you still see the netlogon errors, we might have to resort to restoring the Netlogon shares and Sysvol shares using the burflag method.

The file that it's not creating may need to be automatically recreated by using the burflag AUTHORITATIVE method.

The good news is: DNS, FRS and AD are now clean.

You should be able to recreate the Netlogon share using the burflag Authoritative method.

 

by: ChiefITPosted on 2009-09-22 at 17:21:48ID: 25398985

If all else fails, we may have to reset your policies back to the defaults by using GPOfix. That tool resets your default domain policy OR your default Domain Controller policies OR both.

YOU ARE CLOSE TO HAVING A HEALTHY DC. STICK WITH US.

 

by: ChiefITPosted on 2009-09-22 at 17:48:30ID: 25399156

This article says it better than I can, in words: (Here is your fix)
http://www.lanever.com/bbs/archiver/?tid-103.html

""If you restore all of the domain controllers in the domain backup, all the domain controllers enter the seeding state for FRS and try to synchronize with an online replica. This replication does not occur because all of the domain controllers are in the same seeding state. Setting the primary domain controller FSMO role holder to be authoritative forces the domain controller to rebuild its database based on the current contents of the system volume. When that task is completed, the Sysvol and Netlogon shares are shared. All the other domain controllers can then start synchronizing from the online replica.""

 

by: Eric_GennaouiPosted on 2009-09-22 at 18:03:06ID: 25399223


I sooooo appreciate all your detailed comments ChiefIT you can't imagine..!  

I went back home since the network basics were working (DNS, Logon, FRS) and I was asked to let some time pass to ensure this maintenance was successful and to gather informations on next steps.

I was also asked not to try anything remotely but instead, wait to be on site in case of any errors..and I will only be back on site Thursday, tomorrow if I'm lucky.

You can be sure that I will stick with you and read religiously about the 'Authoritative Method' (D4 heh)  and the 'GPOfix tool' in the meantime, to be ready.

Lets hope nothing else fails during that time  ><

Triple Warm Regards !

IM SOO CLOSE, I CAN FEEL IT !!!!!!!!!

 

by: ChiefITPosted on 2009-09-22 at 19:11:29ID: 25399540

I feel we may be closer than you think!!!

I had this same issue one time that I was working with someone on:

All the author did was recreate the file folder that was missing. That was all he did. See if that works for you before you restore using Burflag!

I see no logon errors or DNS errors, so this replica set should rebuild itself upon restarting the netlogon service.

Who knows, it may be fixed by the time you get there tomorrow, or Thursday.
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_23387073.html

In order, recreate the missing folder and see if your group policies recreat themselves. If so, you are golden.

Then, if the Netlogon error in DCdiag goes away, and your 1030/1058 errors don't, that means you don't have all your group policies. and may need to fix them using GPOfix. or delete the active templates and start over. with Group policies.

Last resort: D4 athoritative restore.

 

by: Eric_GennaouiPosted on 2009-09-23 at 17:13:37ID: 25409225


I was playing with this dcgpofix.exe in a Virtual Environnement to familiarize myself with it (before Thursday arrives) and here's the resume :

1. To recreate a similar environment as mine, I deleted manually the entire 'Policies' folder, but could NOT delete the 'Scripts' shared folder in my SYSVOL for some reason (I event tried with 'attrib -s -h'  but that wouldnt do it).

2. When running "dcgpofix.exe /ignoreschema", it recreated the Policies folder and put 2 default policies in it, which is good I think; but when doing "gpupdate /force", it seemed to work for couple of minute but then I ran into another 1030/1058 error, regarding a 'Denied Access' :
 
"Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=testlab,DC=local. The file must be present at the location <\\testlab.local\sysvol\testlab.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (Access is denied. ). Group Policy processing aborted." (I looked with the other policy I had and its the same rights).....Im sure I missed somehting here

So...if I have to use this tool, I am not sure which "switch" should I use in my Production environment, /ignoreschema or /target:domain, /target:DC or both...its a little confusing...

One last thing : "...or delete the active templates and start over. with Group policies." ....Im not sure what you meant by that  :s

Zee rabbit hole iz going deeper...should I take the Blue Pill ?

All Hail ChiefIT !

 

by: ChiefITPosted on 2009-09-23 at 17:40:42ID: 25409374

DCgpofix will only reset the default domain policy or default domain controller policy back to the system's default status. But, I believe it will rebuild the system tree.

When you restored from backup, some of your files ended up missing out of the sysvol and netlogon directory trees.

So, there's a few branches missing out of your tree. (Just Kidding). With those branches missing, you can't support write some leaf objects. (like your scripts), into the scripts folder that doesn't exist.

To get this to act right you may need to recreate the file folders that are missing in syvol and netlogon. Event logs will tell you what those are.

After recreating those, the policies can be written into those respective folders.

Please note: Scripts may need to be recreated in the folders.

So, this may take a little manipulation, but we will get it to work.  

ALSO NOTE: that restarting the FRS service may rebuild the sysvol and netlogon trees. I haven't tried that approach. If in your shoes, I would restart the FRS service, first thing and see what happens.

If that doesn't work, I would manually recreate the missing file folders.

If that doesn't work, I think I would try to rebuild the sysvol and netlogon share with an authoritative restore using the Burflag D4 method.

If that doesn't work, I would try GPOfix.

 

by: ChiefITPosted on 2009-09-23 at 17:46:33ID: 25409411

The syntax of GPOfix is:

Dcgpofix /Target: BOTH   or DC  or DOMAIN

Warning:

***Do not run this unless you need t reset your DC or Default domain policies. ***

 

by: Eric_GennaouiPosted on 2009-09-23 at 18:58:49ID: 25409671


Quoting:
"When you restored from backup, some of your files ended up missing out of the sysvol and netlogon directory trees"

I did not try to restore the system state on that server so far, sorry if I was unclear, I only tried restoring it to "C:\Temp" to check the sysvol folder with the only valid backup I had but it only contained : "DO_NOT_REMOVE_NtFrs_PreInstall_Directory".

Tomorrow I will recheck all the tapes we have dating from couple days before the event (finally got em from the bank) maybe I'll be lucky enough to get the 'intact policies' back by restoring to an alternate location and check the sysvol folders again....If not, I will try all steps mentionned above !

Did a ever say thanks for your patience and dedication ?  

 

by: ChiefITPosted on 2009-09-23 at 21:27:10ID: 25410082

NO problem.

See you tomorrow


 

by: Eric_GennaouiPosted on 2009-09-24 at 06:50:48ID: 25413322


**Updates**

After restoring from an older tape to an alternate location, heres the result (see restore.jpeg); it looks like I have my old 'Domain' policies (see GPOs.jpeg)  in "\SYSVOL\windows\sysvol\domain" folder !

BUT... the "\SYSVOL\windows\sysvol\sysvol\domain.local" folder still contains nothing (see domain-local.jpeg) ....

Should I attempt to copy back the policies in "C:\WINDOWS\SYSVOL\windows\sysvol\domain"  ? (and would I need to restart ntfrs)

And what about those policies that supposed to be in "C:\WINDOWS\SYSVOL\windows\sysvol\sysvol\domain.local"  but are not present in my restore ?? Does copying back the ones above would help for this ones ?

Quadruple Regards

 

by: Eric_GennaouiPosted on 2009-09-24 at 07:10:15ID: 25413512


Heres some screenshots of the actual "C:\WINDOWS\SYSVOL\domain" folder and the "C:\WINDOWS\SYSVOL\sysvol\domain.local" folder on my production server.

 

by: ChiefITPosted on 2009-09-24 at 10:33:31ID: 25415731

When making edits to the Netlogon shares or sysvol shares, your going to want to stop FRS, and restart it upon completion of the edits.

You might try to replace those files and folders "missing" from the backup copy. Remember to stop FRS, before making edits.

 

by: Eric_GennaouiPosted on 2009-09-24 at 11:12:10ID: 25416101


Ok, I will try those steps in order :

1. Stop NTFRS and copy back the folders I have from the backup then restart NTFRS.
It it does not work
2. Stop NTFRS again,  Delete the folders and recreate them manually and restart NTFRS.
It it does not work
3.Stop NTFRS again,  use the 'BurFlag' method with D4 switch and restart NTFRS.   (afraid of using this one :s)
If everything fails
4. Stop NTFRS again, use 'DCGPOfix' and reset my policies using switch 'target:BOTH' I guess, since I missing the file folders in the 2 places.  (even more afraid of using this one ;(  )

Wish me luck and thanks again

Eric

 

by: ChiefITPosted on 2009-09-24 at 13:24:59ID: 25417479

Don't delete anything. Just go in to event logs and look at the file folders missing, (like sripts). Then, recreate that file folder.

 

by: Eric_GennaouiPosted on 2009-09-24 at 17:54:01ID: 25419392


OMGBBQSAUCE !!!!!!!!!!!

Maintenance is DONE and I now have a healthy D.C !!!

Here's the steps I took, for future reference (error '1030'/'1058' - Missing Policies and scripts file folders in SYSVOL) :

1. Restore the System State from a valid backup in an Alternate Location

2. Stop NTFRS.

3. Recreate the folders "Policies" and "scripts"  in "C:\WINDOWS\SYSVOL\windows\sysvol\domain". Doing so automatically recreates them in "C:\WINDOWS\SYSVOL\sysvol\domain.local" (share 'scripts' as NETLOGON in this folder);.

4.  Start NTFRS again and check the Event Viewers for events 1058 telling us which policy the D.C is looking for (note it to be sure) in which location.

5. Stop NTFRS again and copy back the appropriate policy from the restore and start NTFRS again.

6. Wait for other '1058' errors to appear in Event Viewers and repeat step 5 until we have a '1704' event telling us that the 'Security Policy in the Group Policy objects has been applied successfully'.

7. Restart the server and make sure your Event Viewers are cleared of any error (A.D, DNS, FRS etc)

--------------------------------

CHIEFIT MY FRIEND, YOU ARE INDEED GODSENT !!!!!!!
I will never be able to THANK YOU enough for your kind patience, dedication and detailed explanations even if I was sometime slow to understand/had many questions...you are simply amazing and deserve a trillion points !!!

Also thanks to Wantabe2 who enlightened me on BurFlag method !!

'Bless you all  ;)

Eric
P.S: Multiple Solutions from ChiefIT accepted and Awarding all the points to him cuz he da** deserved 'em !!!

 

by: Eric_GennaouiPosted on 2009-09-24 at 18:01:27ID: 31631012

Hope this thread can help other peoples who faces same situation regarding Journal Wrap errors and event ids 1030, 1054, 1058.
ChieftIT was simply amazing in assisting me through all the steps, Merci Mille Fois !!

 

by: ChiefITPosted on 2009-09-24 at 18:19:10ID: 25419474

Excellent Eric!!!

Let me know when you want to bring on your new server.

 

by: Eric_GennaouiPosted on 2009-09-24 at 21:06:07ID: 25419966


That's so kind of you !

As the present problems seems to be solved, I'll keep monitoring everything and if by next Tuesday it remains the same, I should try and promote this new Windows 2008 STD we got (was joined to the domain the day before the Wrap Journal Error occurred).

After running into couple of issues, I was successful in creating a Virtual Testlab involving a Windows server 2008 as 2nd  D.C/DNS in a Windows 2003 forest. I even ran into the same DNS delegation issue you helped me solve (I knew what to do this time ;p) ! I made myself a little tutorial to make sure I dont miss anything (dont know if I could post it somewhere to help others).

I will indeed let you know how it goes since you generously offers it  ;)

Warm Regards

 

by: ChiefITPosted on 2009-09-24 at 23:24:23ID: 25420394

Eric:

When promoting a 2008 DC into a 2003 domain, you will have to run sysprep and domain prep. Also its best to add DNS prior to the promotion process. So, it will add it's DNS records upon coming into the domain.

There are some hidden steps, that Microsoft Fails to tell people.

It is best to have your ducks in an order before promoting things into the domain.

1)I would add the DNS role, make sure that it replicates DNS.

2)Run Domain prep and Sysprep

3) Run DCPromo

4) make it a global catalog server

5) go to the command prompt and type Net stop netlogon and Net start netlogon

6) make sure DNS is AD integrated.

7 Use force replicate using AD sites and services.

8) check for errors using DCdiag as well as Netdiag.

There are steps to prep your domain for a mixed mode domain.

 

by: Eric_GennaouiPosted on 2009-09-25 at 06:58:56ID: 25422999


Good Morning Chief !

There is indeed some steps I omitted prior to promote it in my virtual lab (i.e : install DNS first, stop/start netlogon etc) and I did not do the SySprep, only used the switchs /forestprep, /domainprep and /gpprep. I will restart all over again using your method and let you know how it goes ;)

Here's the steps Ive taken so far :

1.      Make sure your Forest/Domain Functionnal Levels are at Windows Server 2003, if not, raise them using the Active Directory Domain and Trust in Administrative Tools.

2.      Install, configure and fully update the Windows Server 2008 Standard.

3.      Join the Server 2008 to the Domain 2003 in Computer Properties and reboot it.

4.      Prepare the  Windows Server 2003 FOREST Schema by inserting Windows 2008 DVD in the Windows 2003 primary D.C  server and run : D:\SOURCES\ADPREP\ADPREP.EXE /forestprep.

5.      Prepare the  Windows Server 2003 DOMAIN Schema by inserting Windows 2008 DVD in the Windows 2003 primary D.C  server and run : D:\SOURCES\ADPREP\ADPREP.EXE /domainprep /gpprep IN A COMMAND LINE (cmd).

6.      On the server 2008, open Server Manager and click Add Role and click Active Directory Domain Services, click next and let it install.

7.      Once done, in the Run command prompt, type DCPROMO and press enter.

8.      Choose to install Active Directory Services in Advanced Mode, select DNS and Global Catalog as well  and select the appropriates roles and options. ** If you select the option to install DNS server, you might receive a message that indicates that a DNS delegation for the DNS server could not be created and that you should manually create a DNS delegation to the DNS server to ensure reliable name resolution. If you are installing an additional domain controller in either the forest root domain or a tree root domain, you do not have to create the DNS delegation. In this case, click Yes and disregard the message.**

9.      If error 1136/1464 appear, REPLICATE topology in A.D Sites and Services, and apply solution http://support.microsoft.com/?id=932862, then replicate again.

Links :
Installing Additional Domain Controller SOURCE PAGE:
http://technet.microsoft.com/en-us/library/cc733027%28WS.10%29.aspx

Prepare a Windows 2000 or Windows Server 2003 Forest Schema:
http://technet.microsoft.com/en-us/library/cc753437%28WS.10%29.aspx

Prepare a Windows 2000 or Windows Server 2003 Domain Schema:
http://technet.microsoft.com/en-us/library/cc754670%28WS.10%29.aspx

Installing an Additional Domain Controller by Using the Windows Interface:
http://technet.microsoft.com/en-us/library/cc753720%28WS.10%29.aspx
----------------

I'll see if I can merge my infos with yours in a nice and big tutorial ;)

Cheers !

 

by: ChiefITPosted on 2009-09-25 at 09:06:24ID: 25424373

Eric:

Are either of these SBS Operating systems?

 

by: Eric_GennaouiPosted on 2009-09-25 at 09:20:36ID: 25424490


Nope, both machines in the Virtual Testlab are Standard Edition, one is Windows Server 2003 STD 32bit and the other Windows Server 2008 STD x64.

The only SBS we had is the one that failed 2-3 weeks ago in our Production Environment (everything has been seized/transfer to the server we were working on in this thread).

 

by: ChiefITPosted on 2009-09-25 at 09:38:55ID: 25424622

Your plan is a pretty good plan:

Just a few minute details.
_________________________________________________________________

After adding the DNS role:
On the 2008 server. make its ip the primary and the 2003 server the secondary DNS servers on the NIC configuration:
On the 2003 server. Make its IP the primary and the 2008 server the secondary DNS server on the Nic config.

Now, this is one thing they don't tell you:

Once you add the DNS role, and have the nic settings all configured right, then restart the netlogon service to register the SRV records in DNS. That makes a nice replication loop between DCs.

I would make both DCs global catalog.

I have seen too many times when people log promote a DC and don't register the SRV records with DNS. So, they get an SPNEGO errors. Like this:
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_23356031.html
_____________________________________________________________________________

Here's the steps Ive taken so far :

1.      Make sure your Forest/Domain Functionnal Levels are at Windows Server 2003, if not, raise them using the Active Directory Domain and Trust in Administrative Tools.

2.      Install, configure and fully update the Windows Server 2008 Standard.

3.      Join the Server 2008 to the Domain 2003 in Computer Properties and reboot it.

4.      Prepare the  Windows Server 2003 FOREST Schema by inserting Windows 2008 DVD in the Windows 2003 primary D.C  server and run : D:\SOURCES\ADPREP\ADPREP.EXE /forestprep.

5.      Prepare the  Windows Server 2003 DOMAIN Schema by inserting Windows 2008 DVD in the Windows 2003 primary D.C  server and run : D:\SOURCES\ADPREP\ADPREP.EXE /domainprep /gpprep IN A COMMAND LINE (cmd).

6.      On the server 2008, open Server Manager and click Add Role and click Active Directory Domain Services, click next and let it install.

7.      Once done, in the Run command prompt, type DCPROMO and press enter.

8.      Choose to install Active Directory Services in Advanced Mode, select DNS and Global Catalog as well  and select the appropriates roles and options. ** If you select the option to install DNS server, you might receive a message that indicates that a DNS delegation for the DNS server could not be created and that you should manually create a DNS delegation to the DNS server to ensure reliable name resolution. If you are installing an additional domain controller in either the forest root domain or a tree root domain, you do not have to create the DNS delegation. In this case, click Yes and disregard the message.**

9.      If error 1136/1464 appear, REPLICATE topology in A.D Sites and Services, and apply solution http://support.microsoft.com/?id=932862, then replicate again.

 

by: Eric_GennaouiPosted on 2009-09-25 at 10:05:21ID: 25424874


Quoting :
"After adding the DNS role:
On the 2008 server. make its ip the primary and the 2003 server the secondary DNS servers on the NIC configuration:
On the 2003 server. Make its IP the primary and the 2008 server the secondary DNS server on the Nic config. "

Good thing indeed, that's exactly what I'm doing in all my environments when there's more than 1 DNS (in post ID:25377425 on this thread, the secondary DNS was withdrawn from the configuration since we lost it) ;p

Quoting:
"Once you add the DNS role, and have the nic settings all configured right, then restart the netlogon service to register the SRV records in DNS. That makes a nice replication loop between DCs."

That is good to know cuz I must admit I did not find this nice piece of info on MS sites, thanks a bunch !

Both DC's were made Global Catalog as I plan installing Exchange 2007 (in a near future) on this Server 2008 box.

Quoting:
"I have seen too many times when people log promote a DC and don't register the SRV records with DNS. So, they get an SPNEGO errors. Like this:
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_23356031.html "

I did not know about this one either...that is possibly what cause my DNS delegation problem in the first place...just a thought

I am now in the process of updating my virtual machines and am about to start dcpromo on the win2003,  then I'll merge your nice tips with my tutorial and will attempt a 'clean-and-without-errors' dcpromo of the win2008.

Merci Beaucoup pour toutes les informations utiles  :)

I'll let you know how it turns out !

Regards

Eric

 

by: ChiefITPosted on 2009-09-25 at 16:19:07ID: 25428047

I did not know about this one either...that is possibly what cause my DNS delegation problem in the first place...just a thought

No, the delegation records problem was caused by the default way microsoft puts these records in DNS now. Unfortunately the Delegation records don't dynamically update. So, they end up becoming scavaged.

What we did is we removed the Delegation record, so this doesn't happen to you in the future.

Those delegation records are pointers to your domain's SRV records. When having problems with the delegation records, you also have problems with the SRV records in DNS. So, we just removed the problem from occuring.

 

by: Eric_GennaouiPosted on 2009-09-28 at 06:26:17ID: 25439100


'Morning ChiefIT !

Thanks for the clarification about the delegation issue.

I completed my tests over the weekend and everything went fine. I could add the windows 2008 to the 2003 forest withtout issues. The only thing that happened again was the DNS delegation problem, even if I installed the service before promoting the server and I promptly restarted NetLogon, purging the dns cache. I quickly fixed it by deleting the _msdcs folders as usual.

I should attempt everything on the real environment this Tuesday night.

I guess that my next step in a near future would be to make the Win 2008 Primary D.C / DNS. The company is debating whether or not we will try and install an Exchange 2007, since we lost our mail server (when the SBS died, the mails were forwarded to the parent company). Im going to read on both soonly since I never attempted it.

Cheers

 

by: ChiefITPosted on 2009-09-28 at 08:09:29ID: 25439992

There are some real exchange DeVinci's here. Mestha (Simon) is really great.

I suggest you open up a question in Exchange. He will probably pop by. If not there are some other Miestros.

As far a your delegation records. The first DC in the forest will create the delegation record as you saw. So, since this DC is joining as a DC to a domain, you shouldn't have a problem with the delegation records this time.

To rephrase this another way: Microsoft programmed the first DC in the forest to create the delegation and MSDCS file folder separately. They did this so the records could be replicated over to other DCs in the forest. Since you are joining the 2008 server and not creating a new forest, you shouldn't have problems with the delegation records upon promoting the 2008 server.

I think you are going to be fine:

I really recommend an Exchange question for you. You might be able to recover everything with a good exchange question as well as secure your mail server.

I am not as good with Exchange as I wish I was. I use a Linux based mail server called SUN.

 

by: Eric_GennaouiPosted on 2009-09-28 at 12:24:11ID: 25442430


I will for sure open a question(s) as you recommend when the company will decide about the Exchange server. I still have the backups of the mail server (complete ntbackup) along with the .PSTs of all users (on their machines), I should be able to do something with that.

I'll let you know tomorrow how it goes in my prod. environment when I'll join this new Windows 2008 to our network !

Best Regards

Eric

 

by: Eric_GennaouiPosted on 2009-09-29 at 15:00:55ID: 25453843


I just finished installing the DNS and was able to transfer all my 'Forward lookup Zone' to the new server. However, my 'Reverse-Lookup Zone cannot be transfered...I have a message stating that : The server is not authoritative for this zone.."....wonder why since when I lookup at this zone, my primary server is listed as 'Start of Authority'...

Have any clues ?

Regards

 

by: Eric_GennaouiPosted on 2009-09-29 at 15:22:48ID: 25453995


Huhho....... I ran into a problem....when trying to do the 'ADPREP /domainprep /gpprep', I got this error message :

"Adprep was unable to complete because the call back function failed"

After reading 'http://technet.microsoft.com/en-us/library/dd464018%28WS.10%29.aspx' it appears to be an Anti-Virus problems. Microsoft recommend to turn it off and restart the process....but when re-running 'ADPREP /domainprep /gpprep' it still gives me the same error...halp !

 

by: Eric_GennaouiPosted on 2009-09-29 at 15:41:41ID: 25454123

Here is the ADprep LOG :

Adprep created the log file ADPrep.log under C:\WINDOWS\debug\adprep\logs\20090929181036 directory.

Adprep copied file D:\sources\adprep\schema.ini from installation point to local machine under directory C:\WINDOWS.

Adprep copied file D:\sources\adprep\schupgrade.cat from installation point to local machine under directory

C:\WINDOWS\system32.

Adprep copied file D:\sources\adprep\PAS.ldf from installation point to local machine under directory C:\WINDOWS\system32.


Adprep successfully made the LDAP connection to the local Active Directory Domain Controller FS1.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is (null).



LDAP API ldap_search_s() finished, return code is 0x0



Adprep successfully retrieved information from the local Active Directory Domain Services.



Adprep successfully initialized global variables.[Status/Consequence]Adprep is continuing.



Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is

cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_add_s() finished, return code is 0x44



Adprep attempted to create the Active Directory Domain Services object

cn=DomainUpdates,cn=System,DC=domain,DC=local.[Status/Consequence]The object exists so Adprep did not attempt to rerun this

operation but is continuing.



Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is

cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_add_s() finished, return code is 0x44



Adprep attempted to create the Active Directory Domain Services object

cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.[Status/Consequence]The object exists so Adprep did not attempt

to rerun this operation but is continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=ab402345-d3c3-455d-9ff7-40268a1099b6,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=ab402345-d3c3-455d-9ff7-40268a1099b6,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=bab5f54d-06c8-48de-9b87-d78b796564e4,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=bab5f54d-06c8-48de-9b87-d78b796564e4,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=f3dd09dd-25e8-4f9c-85df-12d6d2f2f2f5,cn=Operations,cn=DomainUpdates,cn=System,DC=idomain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=f3dd09dd-25e8-4f9c-85df-12d6d2f2f2f5,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=2416c60a-fe15-4d7a-a61e-dffd5df864d3,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=2416c60a-fe15-4d7a-a61e-dffd5df864d3,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=7868d4c8-ac41-4e05-b401-776280e8e9f1,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=7868d4c8-ac41-4e05-b401-776280e8e9f1,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=860c36ed-5241-4c62-a18b-cf6ff9994173,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=860c36ed-5241-4c62-a18b-cf6ff9994173,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=0e660ea3-8a5e-4495-9ad7-ca1bd4638f9e,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=0e660ea3-8a5e-4495-9ad7-ca1bd4638f9e,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=a86fe12a-0f62-4e2a-b271-d27f601f8182,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=a86fe12a-0f62-4e2a-b271-d27f601f8182,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=d85c0bfd-094f-4cad-a2b5-82ac9268475d,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=d85c0bfd-094f-4cad-a2b5-82ac9268475d,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=6ada9ff7-c9df-45c1-908e-9fef2fab008a,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=6ada9ff7-c9df-45c1-908e-9fef2fab008a,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=10b3ad2a-6883-4fa7-90fc-6377cbdc1b26,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=10b3ad2a-6883-4fa7-90fc-6377cbdc1b26,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=98de1d3e-6611-443b-8b4e-f4337f1ded0b,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=98de1d3e-6611-443b-8b4e-f4337f1ded0b,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=f607fd87-80cf-45e2-890b-6cf97ec0e284,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=f607fd87-80cf-45e2-890b-6cf97ec0e284,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=9cac1f66-2167-47ad-a472-2a13251310e4,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=9cac1f66-2167-47ad-a472-2a13251310e4,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=6ff880d6-11e7-4ed1-a20f-aac45da48650,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=6ff880d6-11e7-4ed1-a20f-aac45da48650,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=293f0798-ea5c-4455-9f5d-45f33a30703b,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=293f0798-ea5c-4455-9f5d-45f33a30703b,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=5c82b233-75fc-41b3-ac71-c69592e6bf15,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=5c82b233-75fc-41b3-ac71-c69592e6bf15,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=4dfbb973-8a62-4310-a90c-776e00f83222,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=4dfbb973-8a62-4310-a90c-776e00f83222,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=8437c3d8-7689-4200-bf38-79e4ac33dfa0,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=8437c3d8-7689-4200-bf38-79e4ac33dfa0,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=7cfb016c-4f87-4406-8166-bd9df943947f,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=7cfb016c-4f87-4406-8166-bd9df943947f,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=f7ed4553-d82b-49ef-a839-2f38a36bb069,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=f7ed4553-d82b-49ef-a839-2f38a36bb069,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=8ca38317-13a4-4bd4-806f-ebed6acb5d0c,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=8ca38317-13a4-4bd4-806f-ebed6acb5d0c,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=3c784009-1f57-4e2a-9b04-6915c9e71961,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=3c784009-1f57-4e2a-9b04-6915c9e71961,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=6bcd5678-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=6bcd5678-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=6bcd5679-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=6bcd5679-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=6bcd567a-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=6bcd567a-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=6bcd567b-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=6bcd567b-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=6bcd567c-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=6bcd567c-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=6bcd567d-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=6bcd567d-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=6bcd567e-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=6bcd567e-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=6bcd567f-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=6bcd567f-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=6bcd5680-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=6bcd5680-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=6bcd5681-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=6bcd5681-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=6bcd5682-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=6bcd5682-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=6bcd5683-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=6bcd5683-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=6bcd5684-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=6bcd5684-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=6bcd5685-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=6bcd5685-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=6bcd5686-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=6bcd5686-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=6bcd5687-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=6bcd5687-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=6bcd5688-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=6bcd5688-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=6bcd5689-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=6bcd5689-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=6bcd568a-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=6bcd568a-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=6bcd568b-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=6bcd568b-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=6bcd568c-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=6bcd568c-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=6bcd568d-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=6bcd568d-8314-11d6-977b-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=3051c66f-b332-4a73-9a20-2d6a7d6e6a1c,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=3051c66f-b332-4a73-9a20-2d6a7d6e6a1c,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=3e4f4182-ac5d-4378-b760-0eab2de593e2,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=3e4f4182-ac5d-4378-b760-0eab2de593e2,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=c4f17608-e611-11d6-9793-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=c4f17608-e611-11d6-9793-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=13d15cf0-e6c8-11d6-9793-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=13d15cf0-e6c8-11d6-9793-00c04f613221,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=dda1d01d-4bd7-4c49-a184-46f9241b560e,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x20



Adprep verified the state of operation

cn=dda1d01d-4bd7-4c49-a184-46f9241b560e,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local. [Status/Consequence]The

operation has not run or is not currently running. It will be run next.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

CN=BuiltIn,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is CN=BuiltIn,DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep successfully modified the security descriptor on object CN=BuiltIn,DC=domain,DC=local.[Status/Consequence]Adprep

merged the existing security descriptor with the new access control entry (ACE).



Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is

cn=dda1d01d-4bd7-4c49-a184-46f9241b560e,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_add_s() finished, return code is 0x0



Adprep successfully created the Active Directory Domain Services object

cn=dda1d01d-4bd7-4c49-a184-46f9241b560e,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=a1789bfb-e0a2-4739-8cc0-e77d892d080a,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x20



Adprep verified the state of operation

cn=a1789bfb-e0a2-4739-8cc0-e77d892d080a,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local. [Status/Consequence]The

operation has not run or is not currently running. It will be run next.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is CN=Domain System

Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is CN=Domain System Volume (SYSVOL

share),CN=File Replication Service,CN=System,DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep successfully modified the security descriptor on object CN=Domain System Volume (SYSVOL share),CN=File Replication

Service,CN=System,DC=domain,DC=local.[Status/Consequence]Adprep merged the existing security descriptor with the new access

control entry (ACE).



Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is

cn=a1789bfb-e0a2-4739-8cc0-e77d892d080a,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_add_s() finished, return code is 0x0



Adprep successfully created the Active Directory Domain Services object

cn=a1789bfb-e0a2-4739-8cc0-e77d892d080a,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=61b34cb0-55ee-4be9-b595-97810b92b017,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x20



Adprep verified the state of operation

cn=61b34cb0-55ee-4be9-b595-97810b92b017,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local. [Status/Consequence]The

operation has not run or is not currently running. It will be run next.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep successfully modified the security descriptor on object DC=domain,DC=local.[Status/Consequence]Adprep merged the

existing security descriptor with the new access control entry (ACE).



Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is

cn=61b34cb0-55ee-4be9-b595-97810b92b017,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_add_s() finished, return code is 0x0



Adprep successfully created the Active Directory Domain Services object

cn=61b34cb0-55ee-4be9-b595-97810b92b017,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=57428d75-bef7-43e1-938b-2e749f5a8d56,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x20



Adprep verified the state of operation

cn=57428d75-bef7-43e1-938b-2e749f5a8d56,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local. [Status/Consequence]The

operation has not run or is not currently running. It will be run next.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

CN=AdminSDHolder,CN=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is

CN=AdminSDHolder,CN=System,DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep successfully modified the security descriptor on object

CN=AdminSDHolder,CN=System,DC=domain,DC=local.[Status/Consequence]Adprep merged the existing security descriptor with the new

access control entry (ACE).



Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is

cn=57428d75-bef7-43e1-938b-2e749f5a8d56,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_add_s() finished, return code is 0x0



Adprep successfully created the Active Directory Domain Services object

cn=57428d75-bef7-43e1-938b-2e749f5a8d56,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=0b7fb422-3609-4587-8c2e-94b10f67d1bf,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x20



Adprep verified the state of operation

cn=0b7fb422-3609-4587-8c2e-94b10f67d1bf,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local. [Status/Consequence]The

operation has not run or is not currently running. It will be run next.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

CN=AdminSDHolder,CN=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is

CN=AdminSDHolder,CN=System,DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep successfully modified the security descriptor on object

CN=AdminSDHolder,CN=System,DC=domain,DC=local.[Status/Consequence]Adprep merged the existing security descriptor with the new

access control entry (ACE).



Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is

cn=0b7fb422-3609-4587-8c2e-94b10f67d1bf,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_add_s() finished, return code is 0x0



Adprep successfully created the Active Directory Domain Services object

cn=0b7fb422-3609-4587-8c2e-94b10f67d1bf,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=71482d49-8870-4cb3-a438-b6fc9ec35d70,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x20



Adprep verified the state of operation

cn=71482d49-8870-4cb3-a438-b6fc9ec35d70,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local. [Status/Consequence]The

operation has not run or is not currently running. It will be run next.



Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is CN=Password Settings Container,

CN=System,DC=domain,DC=local.



LDAP API ldap_add_s() finished, return code is 0x0



Adprep successfully created the Active Directory Domain Services object CN=Password Settings Container,

CN=System,DC=domain,DC=local.



Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is

cn=71482d49-8870-4cb3-a438-b6fc9ec35d70,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_add_s() finished, return code is 0x0



Adprep successfully created the Active Directory Domain Services object

cn=71482d49-8870-4cb3-a438-b6fc9ec35d70,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=aed72870-bf16-4788-8ac7-22299c8207f1,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x20



Adprep verified the state of operation

cn=aed72870-bf16-4788-8ac7-22299c8207f1,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local. [Status/Consequence]The

operation has not run or is not currently running. It will be run next.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep successfully modified the security descriptor on object DC=domain,DC=local.[Status/Consequence]Adprep merged the

existing security descriptor with the new access control entry (ACE).



Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is

cn=aed72870-bf16-4788-8ac7-22299c8207f1,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_add_s() finished, return code is 0x0



Adprep successfully created the Active Directory Domain Services object

cn=aed72870-bf16-4788-8ac7-22299c8207f1,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=f58300d1-b71a-4db6-88a1-a8b9538beaca,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x20



Adprep verified the state of operation

cn=f58300d1-b71a-4db6-88a1-a8b9538beaca,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local. [Status/Consequence]The

operation has not run or is not currently running. It will be run next.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is CN=IP

Security,CN=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is CN=IP

Security,CN=System,DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep successfully modified the security descriptor on object CN=IP

Security,CN=System,DC=domain,DC=local.[Status/Consequence]Adprep merged the existing security descriptor with the new access

control entry (ACE).



Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is

cn=f58300d1-b71a-4db6-88a1-a8b9538beaca,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_add_s() finished, return code is 0x0



Adprep successfully created the Active Directory Domain Services object

cn=f58300d1-b71a-4db6-88a1-a8b9538beaca,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=231fb90b-c92a-40c9-9379-bacfc313a3e3,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x20



Adprep verified the state of operation

cn=231fb90b-c92a-40c9-9379-bacfc313a3e3,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local. [Status/Consequence]The

operation has not run or is not currently running. It will be run next.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep successfully modified the security descriptor on object DC=domain,DC=local.[Status/Consequence]Adprep merged the

existing security descriptor with the new access control entry (ACE).



Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is

cn=231fb90b-c92a-40c9-9379-bacfc313a3e3,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_add_s() finished, return code is 0x0



Adprep successfully created the Active Directory Domain Services object

cn=231fb90b-c92a-40c9-9379-bacfc313a3e3,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=4aaabc3a-c416-4b9c-a6bb-4b453ab1c1f0,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x20



Adprep verified the state of operation

cn=4aaabc3a-c416-4b9c-a6bb-4b453ab1c1f0,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local. [Status/Consequence]The

operation has not run or is not currently running. It will be run next.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep successfully modified the security descriptor on object DC=domain,DC=local.[Status/Consequence]Adprep merged the

existing security descriptor with the new access control entry (ACE).



Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is

cn=4aaabc3a-c416-4b9c-a6bb-4b453ab1c1f0,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_add_s() finished, return code is 0x0



Adprep successfully created the Active Directory Domain Services object

cn=4aaabc3a-c416-4b9c-a6bb-4b453ab1c1f0,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=9738c400-7795-4d6e-b19d-c16cd6486166,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x20



Adprep verified the state of operation

cn=9738c400-7795-4d6e-b19d-c16cd6486166,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local. [Status/Consequence]The

operation has not run or is not currently running. It will be run next.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

CN=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is CN=System,DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep successfully modified the security descriptor on object CN=System,DC=domain,DC=local.[Status/Consequence]Adprep merged

the existing security descriptor with the new access control entry (ACE).



Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is

cn=9738c400-7795-4d6e-b19d-c16cd6486166,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_add_s() finished, return code is 0x0



Adprep successfully created the Active Directory Domain Services object

cn=9738c400-7795-4d6e-b19d-c16cd6486166,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=de10d491-909f-4fb0-9abb-4b7865c0fe80,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x20



Adprep verified the state of operation

cn=de10d491-909f-4fb0-9abb-4b7865c0fe80,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local. [Status/Consequence]The

operation has not run or is not currently running. It will be run next.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

CN=infrastructure,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is

CN=infrastructure,DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep successfully modified the security descriptor on object

CN=infrastructure,DC=domain,DC=local.[Status/Consequence]Adprep merged the existing security descriptor with the new access

control entry (ACE).



Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is

cn=de10d491-909f-4fb0-9abb-4b7865c0fe80,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_add_s() finished, return code is 0x0



Adprep successfully created the Active Directory Domain Services object

cn=de10d491-909f-4fb0-9abb-4b7865c0fe80,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=b96ed344-545a-4172-aa0c-68118202f125,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x20



Adprep verified the state of operation

cn=b96ed344-545a-4172-aa0c-68118202f125,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local. [Status/Consequence]The

operation has not run or is not currently running. It will be run next.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

CN=DomainUpdates,CN=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is

CN=DomainUpdates,CN=System,DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep successfully modified the security descriptor on object

CN=DomainUpdates,CN=System,DC=domain,DC=local.[Status/Consequence]Adprep merged the existing security descriptor with the new

access control entry (ACE).



Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is

cn=b96ed344-545a-4172-aa0c-68118202f125,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_add_s() finished, return code is 0x0



Adprep successfully created the Active Directory Domain Services object

cn=b96ed344-545a-4172-aa0c-68118202f125,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=4c93ad42-178a-4275-8600-16811d28f3aa,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x20



Adprep verified the state of operation

cn=4c93ad42-178a-4275-8600-16811d28f3aa,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local. [Status/Consequence]The

operation has not run or is not currently running. It will be run next.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is OU=Domain

Controllers,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is OU=Domain

Controllers,DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep successfully modified the security descriptor on object OU=Domain

Controllers,DC=domain,DC=local.[Status/Consequence]Adprep merged the existing security descriptor with the new access control

entry (ACE).



Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is

cn=4c93ad42-178a-4275-8600-16811d28f3aa,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_add_s() finished, return code is 0x0



Adprep successfully created the Active Directory Domain Services object

cn=4c93ad42-178a-4275-8600-16811d28f3aa,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=c88227bc-fcca-4b58-8d8a-cd3d64528a02,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x20



Adprep verified the state of operation

cn=c88227bc-fcca-4b58-8d8a-cd3d64528a02,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local. [Status/Consequence]The

operation has not run or is not currently running. It will be run next.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

CN=AdminSDHolder,CN=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is

CN=AdminSDHolder,CN=System,DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep successfully modified the security descriptor on object

CN=AdminSDHolder,CN=System,DC=domain,DC=local.[Status/Consequence]Adprep merged the existing security descriptor with the new

access control entry (ACE).



Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is

cn=c88227bc-fcca-4b58-8d8a-cd3d64528a02,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_add_s() finished, return code is 0x0



Adprep successfully created the Active Directory Domain Services object

cn=c88227bc-fcca-4b58-8d8a-cd3d64528a02,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is

CN=Windows2003Update,CN=DomainUpdates,CN=System,DC=domain,DC=local.



LDAP API ldap_add_s() finished, return code is 0x44



Adprep attempted to create the Active Directory Domain Services object

CN=Windows2003Update,CN=DomainUpdates,CN=System,DC=domain,DC=local.[Status/Consequence]The object exists so Adprep did not

attempt to rerun this operation but is continuing.



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is

CN=Windows2003Update,CN=DomainUpdates,CN=System,DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is

CN=Windows2003Update,CN=DomainUpdates,CN=System,DC=domain,DC=local.



LDAP API ldap_modify_s() finished, return code is 0x0



Adprep successfully set the domain Update revision attribute to 8 on object

CN=Windows2003Update,CN=DomainUpdates,CN=System,DC=domain,DC=local.[Status/Consequence]Adprep updates the domain Update

revision attribute in order to mark the domain as prepared. Adprep is continuing and will now prepare the domain.



Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is

CN=ActiveDirectoryUpdate,CN=DomainUpdates,CN=System,DC=domain,DC=local.



LDAP API ldap_add_s() finished, return code is 0x0



Adprep successfully created the Active Directory Domain Services object

CN=ActiveDirectoryUpdate,CN=DomainUpdates,CN=System,DC=domain,DC=local.



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is

CN=ActiveDirectoryUpdate,CN=DomainUpdates,CN=System,DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is

CN=ActiveDirectoryUpdate,CN=DomainUpdates,CN=System,DC=domain,DC=local.



LDAP API ldap_modify_s() finished, return code is 0x0



Adprep successfully set the domain Update revision attribute to 3 on object

CN=ActiveDirectoryUpdate,CN=DomainUpdates,CN=System,DC=domain,DC=local.[Status/Consequence]Adprep updates the domain Update

revision attribute in order to mark the domain as prepared. Adprep is continuing and will now prepare the domain.



Adprep successfully updated the domain-wide information.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=a3dac986-80e7-4e59-a059-54cb1ab43cb9,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x20



Adprep verified the state of operation

cn=a3dac986-80e7-4e59-a059-54cb1ab43cb9,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local. [Status/Consequence]The

operation has not run or is not currently running. It will be run next.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=446f24ea-cfd5-4c52-8346-96e170bcb912,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation

cn=446f24ea-cfd5-4c52-8346-96e170bcb912,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has

completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is

continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=51cba88b-99cf-4e16-bef2-c427b38d0767,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x20



Adprep verified the state of operation

cn=51cba88b-99cf-4e16-bef2-c427b38d0767,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local. [Status/Consequence]The

operation has not run or is not currently running. It will be run next.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

CN={1FD72DE7-3FE0-4137-B26B-D590B41EF891},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is

CN={1FD72DE7-3FE0-4137-B26B-D590B41EF891},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is

CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

CN={5DE0E412-0247-420F-8BB3-6588B6FC3E05},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is

CN={5DE0E412-0247-420F-8BB3-6588B6FC3E05},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

CN={68A60901-4D20-4970-8067-0E2C761BA13D},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is

CN={68A60901-4D20-4970-8067-0E2C761BA13D},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

CN={6AC1786C-016F-11D2-945F-00C04fB984F9},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is

CN={6AC1786C-016F-11D2-945F-00C04fB984F9},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

CN={7748A4EB-8B97-4A3B-8BD2-E23A2201C9F1},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is

CN={7748A4EB-8B97-4A3B-8BD2-E23A2201C9F1},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

CN={8A567350-A5F2-47F4-8015-2E1BAA6D2550},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is

CN={8A567350-A5F2-47F4-8015-2E1BAA6D2550},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

CN={9D2AAA3D-5564-49E3-8F74-F7583B8184CD},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is

CN={9D2AAA3D-5564-49E3-8F74-F7583B8184CD},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

CN={A5809C0F-FB77-45F5-B82E-E24927B66312},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is

CN={A5809C0F-FB77-45F5-B82E-E24927B66312},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

CN={B56F1EF1-1294-42BE-9C5B-1EED026AE298},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is

CN={B56F1EF1-1294-42BE-9C5B-1EED026AE298},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

CN={C1D2EC89-B532-4343-BA56-12AA84E4E1F3},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is

CN={C1D2EC89-B532-4343-BA56-12AA84E4E1F3},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

CN={D7545779-4981-4EF0-9F63-16CA19DA53B1},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is

CN={D7545779-4981-4EF0-9F63-16CA19DA53B1},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

CN={EF57185A-B526-4C98-AB24-D610F19FA6A8},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is

CN={EF57185A-B526-4C98-AB24-D610F19FA6A8},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

CN={F9FE0C09-D48E-4649-A495-92D6EED3EFC7},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is

CN={F9FE0C09-D48E-4649-A495-92D6EED3EFC7},CN=Policies,CN=System,DC=domain,DC=local.



LDAP API ldap_modify_ext_s() finished, return code is 0x0



Adprep invoked the call back function UpgradeDSGPOs.[Status/Consequence]The call back function finished successfully.



Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is

cn=51cba88b-99cf-4e16-bef2-c427b38d0767,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_add_s() finished, return code is 0x0



Adprep successfully created the Active Directory Domain Services object

cn=51cba88b-99cf-4e16-bef2-c427b38d0767,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is

cn=a3dac986-80e7-4e59-a059-54cb1ab43cb9,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x20



Adprep verified the state of operation

cn=a3dac986-80e7-4e59-a059-54cb1ab43cb9,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local. [Status/Consequence]The

operation has not run or is not currently running. It will be run next.



Adprep was unable to complete because the call back function failed. [Status/Consequence]Error message: (null)[User Action]

Check the log file ADPrep.log, in the C:\WINDOWS\debug\adprep\logs\20090929181036 directory for more information.



Adprep was unable to update domain information. [Status/Consequence]Adprep requires access to existing domain-wide

information from the infrastructure master in order to complete this operation.[User Action] Check the log file, ADPrep.log,

in the C:\WINDOWS\debug\adprep\logs\20090929181036 directory for more information.
------------------------------------------------------


 

by: Eric_GennaouiPosted on 2009-09-29 at 16:03:52ID: 25454237


I disable the Anti-Virus, re-ran adprep /domainprep /gpprep and heres the result  (what bugs me is this statement "Adprep requires access to existing domain-wide information from the infrastructure master in order to complete this operation"):

Adprep created the log file ADPrep.log under C:\WINDOWS\debug\adprep\logs\20090929185942 directory.



Adprep copied file D:\sources\adprep\schema.ini from installation point to local machine under directory C:\WINDOWS.



Adprep copied file D:\sources\adprep\schupgrade.cat from installation point to local machine under directory C:\WINDOWS\system32.



Adprep copied file D:\sources\adprep\PAS.ldf from installation point to local machine under directory C:\WINDOWS\system32.



Adprep successfully made the LDAP connection to the local Active Directory Domain Controller FS1.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is (null).



LDAP API ldap_search_s() finished, return code is 0x0



Adprep successfully retrieved information from the local Active Directory Domain Services.



Adprep successfully initialized global variables.[Status/Consequence]Adprep is continuing.



Domain-wide information has already been updated.[Status/Consequence]Adprep did not attempt to rerun this operation.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is cn=a3dac986-80e7-4e59-a059-54cb1ab43cb9,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x20



Adprep verified the state of operation cn=a3dac986-80e7-4e59-a059-54cb1ab43cb9,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local. [Status/Consequence]The operation has not run or is not currently running. It will be run next.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is cn=446f24ea-cfd5-4c52-8346-96e170bcb912,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation cn=446f24ea-cfd5-4c52-8346-96e170bcb912,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is cn=51cba88b-99cf-4e16-bef2-c427b38d0767,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x0



Adprep checked to verify whether operation cn=51cba88b-99cf-4e16-bef2-c427b38d0767,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local has completed.[Status/Consequence]The operation GUID already exists so Adprep did not attempt to rerun this operation but is continuing.



Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is cn=a3dac986-80e7-4e59-a059-54cb1ab43cb9,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local.



LDAP API ldap_search_s() finished, return code is 0x20



Adprep verified the state of operation cn=a3dac986-80e7-4e59-a059-54cb1ab43cb9,cn=Operations,cn=DomainUpdates,cn=System,DC=domain,DC=local. [Status/Consequence]The operation has not run or is not currently running. It will be run next.



Adprep was unable to complete because the call back function failed. [Status/Consequence]Error message: (null)[User Action] Check the log file ADPrep.log, in the C:\WINDOWS\debug\adprep\logs\20090929185942 directory for more information.



Adprep was unable to update domain information. [Status/Consequence]Adprep requires access to existing domain-wide information from the infrastructure master in order to complete this operation.[User Action] Check the log file, ADPrep.log, in the C:\WINDOWS\debug\adprep\logs\20090929185942 directory for more information.
------------------------------------------------

This log was shorter than the first one, I dont know why though

Hope you can enlighten me !

Thanks in advance



 

by: Eric_GennaouiPosted on 2009-09-29 at 16:18:24ID: 25454332


One last thing... I looked at this post on Expert-Exchange where the admin got whats looks like the same error message than me : "http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/Q_24478699.html?sfQueryTermInfo=1+adprep+domainprep+fail+gpprep"

The solution involved recommended checking the "sysvol\sysvol\policies\{6ac&&&&..} and {31b&&&&&.}". I looked into the sysvol folder and everyhting seems to be OK.

One thing I maybe failed to say was, when I restored all the policies from a backup few days ago, I had few more policies that the server DID NOT ask me for, so I skipped them.....I am now wondering if I would need one of those old policies for this adprep /domainprep /gpprep to work.... my event viewers says nothing about 'missing policies' atm...

wadaya think ?
P.S : Sorry to throw that much infos at you, wanted to make sure I posted everything needed !

 

by: ChiefITPosted on 2009-09-29 at 18:05:30ID: 25454814

Is Windows Firewall disable or configured to run with this domain controller??

 

by: ChiefITPosted on 2009-09-30 at 11:41:35ID: 25461931

Still there Eric??

 

by: Eric_GennaouiPosted on 2009-09-30 at 15:06:40ID: 25464139


Sorry ChiefIT yeah I'm still here ;)

I posted a new topic (http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_24772060.html) about the little issue I had when running the /domainprep /gpprep switches, issue I did not have in my virtual labs. After couple of posts (dariusq kindly popped in as well!), someone told me to safely ignore the error message I had and go on with the dcpromo...which I did and everything is ok now; the windows 2008 is running fine as a backup D.C/DNS.

Cheers

 

by: ChiefITPosted on 2009-09-30 at 16:32:54ID: 25464698

Dariusq is one of my favorites:

SO, ALL IS GOOD!!!

Point me to your Exchange question and I will watch the masters at work with you.

Thanks,

John

 

by: Eric_GennaouiPosted on 2009-09-30 at 20:57:24ID: 25465874


Thanks a bunch for all your support John, I deeply appreciate  ;)

I will indeed post a question in the next few days about Ex 2007, and I'll link it here so you can easily track it  

Warm Regards

20120131-EE-VQP-002

3 Ways to Join

30-Day Free Trial

The Experts

98% positive feedback on 31,087 answers since March 2000. angeliii is a Microsoft Most Valuable Professional for his work with MS SQL Server & Develoment.

He has also proven his knowledge of Visual Basic Programming, PHP Scripting and Oracle Databases.

The Experts

97% positive feedback on 10,752 answers since July 2000. lrmoore has more than 18 years experience in the networking industry.

The six-time Mircosoft MVPs specialties include firewalls, virtual private networking, and network management.

Testimonials

"...and excellent source for support... Kind of like having your very own IT dept." Electriciansnet

Testimonials

"I was apprehensive at signing up at first. However... it has already made my life as an IT administrator much easier." JaCrews

Testimonials

"WOW! You guys have great, active, and knowledgeable people on here." moore50

Business Clients

Business Clients

In the Press

"If you’ve got a question... Experts Exchange can supply an answer.”

In the Press

"...an invaluable aid for both IT professionals and those who require tech support."

In the Press

"where IT professionals provide quick answers on just about any topic"

Business Account Plans

Loading Advertisement...