<div>
I guess you are right bit I didnt want to go through all that process.<br />
According to all the articles I read from the microsoft site, a system state backup from the production system could be used to do an authoritative restore on the test domain but I guess in my case the hardware could be the issue.<br />
After several unsuccessfull attempts I took one of my production dc's to the test domain as the only dc. <br />
Run dcpromo on one server as an additional dc. After replication had completed, I removed the production dc from the test domain and seize all FSMO roles to the additional dc. This worked for me but why do we have to go through all that instead of a simple authoritative restore.<br />
Thanks anyway
</div>


I guess you are right bit I didnt want to go through all that process.
According to all the articles I read from the microsoft site, a system state backup from the production system could be used to do an authoritative restore on the test domain but I guess in my case the hardware could be the issue.
After several unsuccessfull attempts I took one of my production dc's to the test domain as the only dc.
Run dcpromo on one server as an additional dc. After replication had completed, I removed the production dc from the test domain and seize all FSMO roles to the additional dc. This worked for me but why do we have to go through all that instead of a simple authoritative restore.
Thanks anyway

<div>
<div class="content wysiwyg-content">
Hi All<br />
I am planning to upgrade to w2k3 but before I do am staging my whole<br />
environment first on an isolated network to see what I will be up to.<br />
I did a system state backup of my production root dc and did an<br />
authoritative restore with that backup on my staging dc. The restore<br />
completes successfully but unable to restart the staging dc after the<br />
restore.<br />
Any ideas<br />

</div>
</div>


Hi All
I am planning to upgrade to w2k3 but before I do am staging my whole
environment first on an isolated network to see what I will be up to.
I did a system state backup of my production root dc and did an
authoritative restore with that backup on my staging dc. The restore
completes successfully but unable to restart the staging dc after the
restore.
Any ideas


Cannot restart dc after authoritative restore

Windows 2000 is an operating system for use on both client and server computers. It is the successor to Windows NT 4.0, and is the last version of Microsoft Windows to display the "Windows NT" designation. Four editions of Windows 2000 were released (Professional, Server, Advanced Server, and Datacenter Server) that shared a core set of features, including many system utilities such as the Microsoft Management Console. All versions of the operating system support NTFS 3.0, Encrypting File System, as well as basic and dynamic disk storage. The Windows 2000 Server family includes support for Active Directory services, Distributed File System and fault-redundant storage volumes.