NTFRS messed up after 'Enable Journal Wrap Automatic Restore' - HELP !
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=
<FrsDsGetSysvolInboundCxti
<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_E
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
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=
<FrsDsGetSysvolInboundCxti
<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_E
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
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
ASKER
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 !
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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):
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):
ASKER
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\FS
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\FS
Starting test: Replications
* Replications Check
* Replication Latency Check
DC=ForestDnsZones,DC=domai
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=domai
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
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
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=domai
* Security Permissions Check for DC=DomainDnsZones,DC=domai
* Security Permissions Check for CN=Schema,CN=Configuration
* Security Permissions Check for CN=Configuration,DC=domain
* 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
Role Domain Owner = CN=NTDS Settings,CN=FS1,CN=Servers
Role PDC Owner = CN=NTDS Settings,CN=FS1,CN=Servers
Role Rid Owner = CN=NTDS Settings,CN=FS1,CN=Servers
Role Infrastructure Update Owner = CN=NTDS Settings,CN=FS1,CN=Servers
......................... 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
* SPN found :LDAP/FS1.domainname.local
* SPN found :LDAP/FS1
* SPN found :LDAP/FS1.domainname.local
* SPN found :LDAP/20f9efb7-be68-4e89-a
* SPN found :E3514235-4B06-11D1-AB04-0
* SPN found :HOST/FS1.domainname.local
* SPN found :HOST/FS1.domainname.local
* SPN found :HOST/FS1
* SPN found :HOST/FS1.domainname.local
* SPN found :GC/FS1.domainname.local/d
......................... 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,
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=FS1,CN=Servers
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\d
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,
The system object reference (frsComputerReferenceBL) CN=FS1,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=domai
The system object reference (serverReferenceBL) CN=FS1,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=domai
CN=Configuration,DC=domain
......................... 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.
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\FS
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\FS
Starting test: Replications
* Replications Check
* Replication Latency Check
DC=ForestDnsZones,DC=domai
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=domai
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
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
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=domai
* Security Permissions Check for DC=DomainDnsZones,DC=domai
* Security Permissions Check for CN=Schema,CN=Configuration
* Security Permissions Check for CN=Configuration,DC=domain
* 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
Role Domain Owner = CN=NTDS Settings,CN=FS1,CN=Servers
Role PDC Owner = CN=NTDS Settings,CN=FS1,CN=Servers
Role Rid Owner = CN=NTDS Settings,CN=FS1,CN=Servers
Role Infrastructure Update Owner = CN=NTDS Settings,CN=FS1,CN=Servers
......................... 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
* SPN found :LDAP/FS1.domainname.local
* SPN found :LDAP/FS1
* SPN found :LDAP/FS1.domainname.local
* SPN found :LDAP/20f9efb7-be68-4e89-a
* SPN found :E3514235-4B06-11D1-AB04-0
* SPN found :HOST/FS1.domainname.local
* SPN found :HOST/FS1.domainname.local
* SPN found :HOST/FS1
* SPN found :HOST/FS1.domainname.local
* SPN found :GC/FS1.domainname.local/d
......................... 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,
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=FS1,CN=Servers
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\d
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,
The system object reference (frsComputerReferenceBL) CN=FS1,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=domai
The system object reference (serverReferenceBL) CN=FS1,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=domai
CN=Configuration,DC=domain
......................... 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.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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 !
Let us know how it rurns out..
ASKER
**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
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
**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
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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 ;)
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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 ?
dns.JPG
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
**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\d
The system cannot find the file specified."
I hope this is normal....I'll continue with the Metadata Cleanup in the meantime.
Eric
ASKER
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\d
i ran a DCdiag and heres the result (Next Post) :
dns-2.JPG
error-1030.JPG
error-1058.JPG
ASKER
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\FS
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\FS
Starting test: Replications
* Replications Check
* Replication Latency Check
DC=ForestDnsZones,DC=domai
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=domai
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
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
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=domai
(NDNC,Version 2)
* Security Permissions Check for
DC=DomainDnsZones,DC=domai
(NDNC,Version 2)
* Security Permissions Check for
CN=Schema,CN=Configuration
(Schema,Version 2)
* Security Permissions Check for
CN=Configuration,DC=domain
(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
-Site-Name,CN=Sites,CN=Con
Role Domain Owner = CN=NTDS Settings,CN=FS1,CN=Servers
-Site-Name,CN=Sites,CN=Con
Role PDC Owner = CN=NTDS Settings,CN=FS1,CN=Servers
te-Name,CN=Sites,CN=Config
Role Rid Owner = CN=NTDS Settings,CN=FS1,CN=Servers
te-Name,CN=Sites,CN=Config
Role Infrastructure Update Owner = CN=NTDS Settings,CN=FS1,CN=Servers
N=Default-First-Site-Name,
......................... 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/dom
* SPN found :LDAP/FS1.domain.local
* SPN found :LDAP/FS1
* SPN found :LDAP/FS1.domain.local/dom
* SPN found :LDAP/20f9efb7-be68-4e89-a
.local
* SPN found :E3514235-4B06-11D1-AB04-0
d1-afbe84945379/domain.loc
* SPN found :HOST/FS1.domain.local/dom
* SPN found :HOST/FS1.domain.local
* SPN found :HOST/FS1
* SPN found :HOST/FS1.domain.local/dom
* SPN found :GC/FS1.domain.local/domai
......................... 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=
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
ame,CN=Sites,CN=Configurat
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\d
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\d
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=l
CN=FS1,CN=Servers,CN=Defau
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=
and backlink on CN=FS1,OU=Domain Controllers,DC=domain,DC=l
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=
and backlink on
CN=NTDS Settings,CN=FS1,CN=Servers
CN=Configuration,DC=domain
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
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\FS
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\FS
Starting test: Replications
* Replications Check
* Replication Latency Check
DC=ForestDnsZones,DC=domai
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=domai
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
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
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=domai
(NDNC,Version 2)
* Security Permissions Check for
DC=DomainDnsZones,DC=domai
(NDNC,Version 2)
* Security Permissions Check for
CN=Schema,CN=Configuration
(Schema,Version 2)
* Security Permissions Check for
CN=Configuration,DC=domain
(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
-Site-Name,CN=Sites,CN=Con
Role Domain Owner = CN=NTDS Settings,CN=FS1,CN=Servers
-Site-Name,CN=Sites,CN=Con
Role PDC Owner = CN=NTDS Settings,CN=FS1,CN=Servers
te-Name,CN=Sites,CN=Config
Role Rid Owner = CN=NTDS Settings,CN=FS1,CN=Servers
te-Name,CN=Sites,CN=Config
Role Infrastructure Update Owner = CN=NTDS Settings,CN=FS1,CN=Servers
N=Default-First-Site-Name,
......................... 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/dom
* SPN found :LDAP/FS1.domain.local
* SPN found :LDAP/FS1
* SPN found :LDAP/FS1.domain.local/dom
* SPN found :LDAP/20f9efb7-be68-4e89-a
.local
* SPN found :E3514235-4B06-11D1-AB04-0
d1-afbe84945379/domain.loc
* SPN found :HOST/FS1.domain.local/dom
* SPN found :HOST/FS1.domain.local
* SPN found :HOST/FS1
* SPN found :HOST/FS1.domain.local/dom
* SPN found :GC/FS1.domain.local/domai
......................... 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=
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
ame,CN=Sites,CN=Configurat
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\d
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\d
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=l
CN=FS1,CN=Servers,CN=Defau
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=
and backlink on CN=FS1,OU=Domain Controllers,DC=domain,DC=l
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=
and backlink on
CN=NTDS Settings,CN=FS1,CN=Servers
CN=Configuration,DC=domain
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
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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 !!!!!!!!!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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-945
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 !
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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_PreIn
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 ?
NO problem.
See you tomorrow
See you tomorrow
ASKER
**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\do
BUT... the "\SYSVOL\windows\sysvol\sy
Should I attempt to copy back the policies in "C:\WINDOWS\SYSVOL\windows
And what about those policies that supposed to be in "C:\WINDOWS\SYSVOL\windows
Quadruple Regards
restore-domain-policies.JPG
domain-GPOs.JPG
domain-local.JPG
ASKER
Heres some screenshots of the actual "C:\WINDOWS\SYSVOL\domain"
prod-sysvol-domain.JPG
prod-sysvol-sysvol-domain.local.jpeg
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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
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 !!!
ASKER
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 !!
ChieftIT was simply amazing in assisting me through all the steps, Merci Mille Fois !!
Excellent Eric!!!
Let me know when you want to bring on your new server.
Let me know when you want to bring on your new server.
ASKER
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
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.
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.
ASKER
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.E
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.E
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 !
Eric:
Are either of these SBS Operating systems?
Are either of these SBS Operating systems?
ASKER
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).
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:
https://www.experts-exchange.com/questions/23356031/There-are-currently-no-logon-servers-available-to-service-the-logon-request.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.E
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.E
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.
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:
https://www.experts-exchange.com/questions/23356031/There-are-currently-no-logon-servers-available-to-service-the-logon-request.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.E
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.E
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.
ASKER
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:
https://www.experts-exchange.com/questions/23356031/There-are-currently-no-logon-servers-available-to-service-the-logon-request.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'
Merci Beaucoup pour toutes les informations utiles :)
I'll let you know how it turns out !
Regards
Eric
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.
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.
ASKER
'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
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.
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.
ASKER
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
ASKER
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
ASKER
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 !
ASKER
Here is the ADprep LOG :
Adprep created the log file ADPrep.log under C:\WINDOWS\debug\adprep\lo
Adprep copied file D:\sources\adprep\schema.i
Adprep copied file D:\sources\adprep\schupgra
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/Conseque
Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is
cn=DomainUpdates,cn=System
LDAP API ldap_add_s() finished, return code is 0x44
Adprep attempted to create the Active Directory Domain Services object
cn=DomainUpdates,cn=System
operation but is continuing.
Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is
cn=Operations,cn=DomainUpd
LDAP API ldap_add_s() finished, return code is 0x44
Adprep attempted to create the Active Directory Domain Services object
cn=Operations,cn=DomainUpd
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=ab402345-d3c3-455d-9ff7
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=bab5f54d-06c8-48de-9b87
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=f3dd09dd-25e8-4f9c-85df
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=2416c60a-fe15-4d7a-a61e
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=7868d4c8-ac41-4e05-b401
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=860c36ed-5241-4c62-a18b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=0e660ea3-8a5e-4495-9ad7
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=a86fe12a-0f62-4e2a-b271
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=d85c0bfd-094f-4cad-a2b5
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6ada9ff7-c9df-45c1-908e
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=10b3ad2a-6883-4fa7-90fc
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=98de1d3e-6611-443b-8b4e
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=f607fd87-80cf-45e2-890b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=9cac1f66-2167-47ad-a472
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6ff880d6-11e7-4ed1-a20f
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=293f0798-ea5c-4455-9f5d
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=5c82b233-75fc-41b3-ac71
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=4dfbb973-8a62-4310-a90c
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=8437c3d8-7689-4200-bf38
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=7cfb016c-4f87-4406-8166
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=f7ed4553-d82b-49ef-a839
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=8ca38317-13a4-4bd4-806f
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=3c784009-1f57-4e2a-9b04
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd5678-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd5679-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd567a-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd567b-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd567c-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd567d-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd567e-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd567f-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd5680-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd5681-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd5682-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd5683-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd5684-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd5685-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd5686-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd5687-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd5688-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd5689-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd568a-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd568b-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd568c-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd568d-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=3051c66f-b332-4a73-9a20
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=3e4f4182-ac5d-4378-b760
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=c4f17608-e611-11d6-9793
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=13d15cf0-e6c8-11d6-9793
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=dda1d01d-4bd7-4c49-a184
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=lo
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=lo
LDAP API ldap_modify_ext_s() finished, return code is 0x0
Adprep successfully modified the security descriptor on object CN=BuiltIn,DC=domain,DC=lo
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
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=dda1d01d-4bd7-4c49-a184
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=a1789bfb-e0a2-4739-8cc0
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=domai
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=domai
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=domai
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
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=a1789bfb-e0a2-4739-8cc0
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=61b34cb0-55ee-4be9-b595
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
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
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=61b34cb0-55ee-4be9-b595
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=57428d75-bef7-43e1-938b
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
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
LDAP API ldap_modify_ext_s() finished, return code is 0x0
Adprep successfully modified the security descriptor on object
CN=AdminSDHolder,CN=System
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
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=57428d75-bef7-43e1-938b
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=0b7fb422-3609-4587-8c2e
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
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
LDAP API ldap_modify_ext_s() finished, return code is 0x0
Adprep successfully modified the security descriptor on object
CN=AdminSDHolder,CN=System
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
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=0b7fb422-3609-4587-8c2e
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=71482d49-8870-4cb3-a438
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=loc
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=loc
Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is
cn=71482d49-8870-4cb3-a438
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=71482d49-8870-4cb3-a438
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=aed72870-bf16-4788-8ac7
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
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
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=aed72870-bf16-4788-8ac7
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=f58300d1-b71a-4db6-88a1
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=doma
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=doma
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=doma
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
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=f58300d1-b71a-4db6-88a1
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=231fb90b-c92a-40c9-9379
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
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
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=231fb90b-c92a-40c9-9379
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=4aaabc3a-c416-4b9c-a6bb
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
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
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=4aaabc3a-c416-4b9c-a6bb
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=9738c400-7795-4d6e-b19d
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=loc
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=loc
LDAP API ldap_modify_ext_s() finished, return code is 0x0
Adprep successfully modified the security descriptor on object CN=System,DC=domain,DC=loc
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
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=9738c400-7795-4d6e-b19d
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=de10d491-909f-4fb0-9abb
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=domai
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=domai
LDAP API ldap_modify_ext_s() finished, return code is 0x0
Adprep successfully modified the security descriptor on object
CN=infrastructure,DC=domai
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
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=de10d491-909f-4fb0-9abb
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=b96ed344-545a-4172-aa0c
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
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
LDAP API ldap_modify_ext_s() finished, return code is 0x0
Adprep successfully modified the security descriptor on object
CN=DomainUpdates,CN=System
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
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=b96ed344-545a-4172-aa0c
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=4c93ad42-178a-4275-8600
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=l
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=l
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=l
entry (ACE).
Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is
cn=4c93ad42-178a-4275-8600
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=4c93ad42-178a-4275-8600
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=c88227bc-fcca-4b58-8d8a
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
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
LDAP API ldap_modify_ext_s() finished, return code is 0x0
Adprep successfully modified the security descriptor on object
CN=AdminSDHolder,CN=System
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
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=c88227bc-fcca-4b58-8d8a
Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is
CN=Windows2003Update,CN=Do
LDAP API ldap_add_s() finished, return code is 0x44
Adprep attempted to create the Active Directory Domain Services object
CN=Windows2003Update,CN=Do
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=Do
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=Do
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=Do
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,C
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
CN=ActiveDirectoryUpdate,C
Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is
CN=ActiveDirectoryUpdate,C
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,C
LDAP API ldap_modify_s() finished, return code is 0x0
Adprep successfully set the domain Update revision attribute to 3 on object
CN=ActiveDirectoryUpdate,C
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=a3dac986-80e7-4e59-a059
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=446f24ea-cfd5-4c52-8346
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=51cba88b-99cf-4e16-bef2
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-B26
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-B26
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-945
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-945
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-8BB
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-8BB
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-806
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-806
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-945
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-945
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-8BD
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-8BD
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-801
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-801
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-8F7
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-8F7
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-B82
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-B82
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-9C5
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-9C5
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-BA5
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-BA5
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-9F6
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-9F6
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-AB2
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-AB2
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-A49
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-A49
LDAP API ldap_modify_ext_s() finished, return code is 0x0
Adprep invoked the call back function UpgradeDSGPOs.[Status/Cons
Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is
cn=51cba88b-99cf-4e16-bef2
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=51cba88b-99cf-4e16-bef2
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=a3dac986-80e7-4e59-a059
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\lo
Adprep was unable to update domain information. [Status/Consequence]Adprep
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\lo
--------------------------
Adprep created the log file ADPrep.log under C:\WINDOWS\debug\adprep\lo
Adprep copied file D:\sources\adprep\schema.i
Adprep copied file D:\sources\adprep\schupgra
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/Conseque
Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is
cn=DomainUpdates,cn=System
LDAP API ldap_add_s() finished, return code is 0x44
Adprep attempted to create the Active Directory Domain Services object
cn=DomainUpdates,cn=System
operation but is continuing.
Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is
cn=Operations,cn=DomainUpd
LDAP API ldap_add_s() finished, return code is 0x44
Adprep attempted to create the Active Directory Domain Services object
cn=Operations,cn=DomainUpd
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=ab402345-d3c3-455d-9ff7
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=bab5f54d-06c8-48de-9b87
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=f3dd09dd-25e8-4f9c-85df
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=2416c60a-fe15-4d7a-a61e
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=7868d4c8-ac41-4e05-b401
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=860c36ed-5241-4c62-a18b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=0e660ea3-8a5e-4495-9ad7
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=a86fe12a-0f62-4e2a-b271
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=d85c0bfd-094f-4cad-a2b5
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6ada9ff7-c9df-45c1-908e
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=10b3ad2a-6883-4fa7-90fc
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=98de1d3e-6611-443b-8b4e
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=f607fd87-80cf-45e2-890b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=9cac1f66-2167-47ad-a472
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6ff880d6-11e7-4ed1-a20f
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=293f0798-ea5c-4455-9f5d
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=5c82b233-75fc-41b3-ac71
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=4dfbb973-8a62-4310-a90c
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=8437c3d8-7689-4200-bf38
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=7cfb016c-4f87-4406-8166
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=f7ed4553-d82b-49ef-a839
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=8ca38317-13a4-4bd4-806f
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=3c784009-1f57-4e2a-9b04
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd5678-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd5679-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd567a-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd567b-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd567c-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd567d-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd567e-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd567f-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd5680-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd5681-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd5682-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd5683-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd5684-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd5685-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd5686-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd5687-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd5688-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd5689-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd568a-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd568b-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd568c-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=6bcd568d-8314-11d6-977b
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=3051c66f-b332-4a73-9a20
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=3e4f4182-ac5d-4378-b760
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=c4f17608-e611-11d6-9793
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=13d15cf0-e6c8-11d6-9793
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=dda1d01d-4bd7-4c49-a184
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=lo
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=lo
LDAP API ldap_modify_ext_s() finished, return code is 0x0
Adprep successfully modified the security descriptor on object CN=BuiltIn,DC=domain,DC=lo
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
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=dda1d01d-4bd7-4c49-a184
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=a1789bfb-e0a2-4739-8cc0
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=domai
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=domai
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=domai
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
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=a1789bfb-e0a2-4739-8cc0
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=61b34cb0-55ee-4be9-b595
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
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
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=61b34cb0-55ee-4be9-b595
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=57428d75-bef7-43e1-938b
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
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
LDAP API ldap_modify_ext_s() finished, return code is 0x0
Adprep successfully modified the security descriptor on object
CN=AdminSDHolder,CN=System
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
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=57428d75-bef7-43e1-938b
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=0b7fb422-3609-4587-8c2e
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
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
LDAP API ldap_modify_ext_s() finished, return code is 0x0
Adprep successfully modified the security descriptor on object
CN=AdminSDHolder,CN=System
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
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=0b7fb422-3609-4587-8c2e
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=71482d49-8870-4cb3-a438
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=loc
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=loc
Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is
cn=71482d49-8870-4cb3-a438
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=71482d49-8870-4cb3-a438
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=aed72870-bf16-4788-8ac7
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
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
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=aed72870-bf16-4788-8ac7
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=f58300d1-b71a-4db6-88a1
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=doma
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=doma
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=doma
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
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=f58300d1-b71a-4db6-88a1
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=231fb90b-c92a-40c9-9379
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
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
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=231fb90b-c92a-40c9-9379
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=4aaabc3a-c416-4b9c-a6bb
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
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
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=4aaabc3a-c416-4b9c-a6bb
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=9738c400-7795-4d6e-b19d
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=loc
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=loc
LDAP API ldap_modify_ext_s() finished, return code is 0x0
Adprep successfully modified the security descriptor on object CN=System,DC=domain,DC=loc
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
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=9738c400-7795-4d6e-b19d
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=de10d491-909f-4fb0-9abb
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=domai
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=domai
LDAP API ldap_modify_ext_s() finished, return code is 0x0
Adprep successfully modified the security descriptor on object
CN=infrastructure,DC=domai
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
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=de10d491-909f-4fb0-9abb
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=b96ed344-545a-4172-aa0c
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
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
LDAP API ldap_modify_ext_s() finished, return code is 0x0
Adprep successfully modified the security descriptor on object
CN=DomainUpdates,CN=System
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
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=b96ed344-545a-4172-aa0c
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=4c93ad42-178a-4275-8600
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=l
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=l
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=l
entry (ACE).
Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is
cn=4c93ad42-178a-4275-8600
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=4c93ad42-178a-4275-8600
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=c88227bc-fcca-4b58-8d8a
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
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
LDAP API ldap_modify_ext_s() finished, return code is 0x0
Adprep successfully modified the security descriptor on object
CN=AdminSDHolder,CN=System
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
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=c88227bc-fcca-4b58-8d8a
Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is
CN=Windows2003Update,CN=Do
LDAP API ldap_add_s() finished, return code is 0x44
Adprep attempted to create the Active Directory Domain Services object
CN=Windows2003Update,CN=Do
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=Do
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=Do
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=Do
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,C
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
CN=ActiveDirectoryUpdate,C
Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is
CN=ActiveDirectoryUpdate,C
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,C
LDAP API ldap_modify_s() finished, return code is 0x0
Adprep successfully set the domain Update revision attribute to 3 on object
CN=ActiveDirectoryUpdate,C
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=a3dac986-80e7-4e59-a059
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation
cn=446f24ea-cfd5-4c52-8346
completed.[Status/Conseque
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=51cba88b-99cf-4e16-bef2
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-B26
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-B26
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-945
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-945
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-8BB
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-8BB
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-806
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-806
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-945
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-945
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-8BD
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-8BD
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-801
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-801
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-8F7
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-8F7
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-B82
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-B82
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-9C5
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-9C5
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-BA5
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-BA5
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-9F6
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-9F6
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-AB2
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-AB2
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-A49
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-A49
LDAP API ldap_modify_ext_s() finished, return code is 0x0
Adprep invoked the call back function UpgradeDSGPOs.[Status/Cons
Adprep was about to call the following LDAP API. ldap_add_s(). The entry to add is
cn=51cba88b-99cf-4e16-bef2
LDAP API ldap_add_s() finished, return code is 0x0
Adprep successfully created the Active Directory Domain Services object
cn=51cba88b-99cf-4e16-bef2
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=a3dac986-80e7-4e59-a059
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\lo
Adprep was unable to update domain information. [Status/Consequence]Adprep
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\lo
--------------------------
ASKER
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\lo
Adprep copied file D:\sources\adprep\schema.i
Adprep copied file D:\sources\adprep\schupgra
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/Conseque
Domain-wide information has already been updated.[Status/Consequenc
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation cn=a3dac986-80e7-4e59-a059
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation cn=446f24ea-cfd5-4c52-8346
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
LDAP API ldap_search_s() finished, return code is 0x0
Adprep checked to verify whether operation cn=51cba88b-99cf-4e16-bef2
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
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation cn=a3dac986-80e7-4e59-a059
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\lo
Adprep was unable to update domain information. [Status/Consequence]Adprep
--------------------------
This log was shorter than the first one, I dont know why though
Hope you can enlighten me !
Thanks in advance
ASKER
One last thing... I looked at this post on Expert-Exchange where the admin got whats looks like the same error message than me : "https://www.experts-exchange.com/questions/24478699/adprep-domainprep-gpprep-fails.html?sfQueryTermInfo=1+adprep+domainprep+fail+gpprep"
The solution involved recommended checking the "sysvol\sysvol\policies\{6
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 !
Is Windows Firewall disable or configured to run with this domain controller??
Still there Eric??
ASKER
Sorry ChiefIT yeah I'm still here ;)
I posted a new topic (https://www.experts-exchange.com/questions/24772060/ADPREP-domainprep-gpprep-FAIL-HELP.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
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
SO, ALL IS GOOD!!!
Point me to your Exchange question and I will watch the masters at work with you.
Thanks,
John
ASKER
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
Hello Fellow Members,
I want to say thanks for the supplied answer to this problem. My customer has a VM of SBS 2003 running for years and a few days ago the system's NTFRS went south. First, tried an auto repair which put the system into a loop where a scan was initiated and would run forever. Using:
HKLM\ SYSTEM\ CurrentControlSet\ Services\ NtFrs\ Parameters\
Backup/Restore\ Process at Startup
BurFlags
You should stop NtFrs, set Burflags to D2 and start NtFrs
Instantly fixed the problem and the customer is back up and running.
Regards,
Grant
I want to say thanks for the supplied answer to this problem. My customer has a VM of SBS 2003 running for years and a few days ago the system's NTFRS went south. First, tried an auto repair which put the system into a loop where a scan was initiated and would run forever. Using:
HKLM\ SYSTEM\ CurrentControlSet\ Services\ NtFrs\ Parameters\
Backup/Restore\ Process at Startup
BurFlags
You should stop NtFrs, set Burflags to D2 and start NtFrs
Instantly fixed the problem and the customer is back up and running.
Regards,
Grant
ASKER
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\d
Should I just restart the server or should I take other actions ?
Many thanks in advance
Eric