Tech Support > Operating Systems > Windows 2003 > adprep /domainprep
adprep /domainprep
Posted by Toni Uranjek on March 1st, 2004


Hi!

I'm are trying to upgrade our domain from Windows 2000 to Windows 2003. We
have single domain forest, with two domain controllers (no Exchange, domain
is in Windows 2000 Native mode), first is holding all fsmo rolles. I ran
"adprep /forestprep" on schema master without any problem. Changes were
sucessfully replicated and then I tried to run "adprep /domainprep" on
infrastructure master. I've ended up with this error in adprep.log

---------
Adprep was about to call the following LDAP API. ldap_search_s(). The base
entry to start the search is
cn=446f24ea-cfd5-4c52-8346-96e170bcb912,cn=Operations,cn=DomainUpdates,cn=Sy
stem,DC=domain,DC=local.

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

Adprep verified the state of operation
cn=446f24ea-cfd5-4c52-8346-96e170bcb912,cn=Operations,cn=DomainUpdates,cn=Sy
stem,DC=domain,DC=local.

[Status/Consequence]
The operation has not run or is not currently running. It will be run next.

Adprep was unable to complete because the call back function (null) failed.

[Status/Consequence]
Error message: Windows cannot determine the local sysvol location. Upgrade
of Domain Group Policy Objects failed. (The system cannot find the file
specified. )
---------

Specified object does not exist in
domain.local\System\DomainUpdates\Operations. I found no errors with dcdiag
or nediag. Everything works fine.

I'm looking for an explanation of error "Windows cannot determine the local
sysvol location. Upgrade of Domain Group Policy Objects failed. (The system
cannot find the file specified. )" or for any information on how to continue
with domain upgrade.

TIA

Toni Uranjek


Posted by David Everett [MSFT] on March 5th, 2004


Hello Toni,

From the error it appears adprep /domainprep is not able to locate Sysvol on
the Infrastructure Master.

1. Verify Netlogon Service is started on the DC
2. Verify Sysvol is shared out on this server by typing "Net Share" at the
command line.
3. Verify the Sysvol REG_SZ value is present under
HKLM\System\CurrentControlSet\Services\Netlogon\Pa rameters and that the path
to the Shared sysvol folder is correct. If this value is missing Add the
REG_SZ value called Sysvol and enter the correct path, then stop and restart
the Net Logon service. The default location is C:\winnt\sysvol\sysvol but
yours may be at a different location.

--
David Everett
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
"Manfred" <simonet@cdiglobal.com> wrote in message
news:174401c384cf$cca46b50$a301280a@phx.gbl...

"Toni Uranjek" <toni.uranjek@email.si> wrote in message
news:eulhYQ8$DHA.2212@TK2MSFTNGP10.phx.gbl...



Similar Posts