<div>
It really all depends on what your backing up with BE. &nbsp;If your doing system state as well as all of the folders it should work however you will need to change the computer name just to make sure you dont get a conflict.
</div>


It really all depends on what your backing up with BE.  If your doing system state as well as all of the folders it should work however you will need to change the computer name just to make sure you dont get a conflict.

<div>
JJones312,<br />
<br />
That's what I was thinking as well. &nbsp;Sort of like installing from an image. &nbsp;Do you think I should disjoin and rejoin to the domain so there are no duplicate program IDs (sorry, forget the terminology...)<br />
<br />

</div>


JJones312,

That's what I was thinking as well.  Sort of like installing from an image.  Do you think I should disjoin and rejoin to the domain so there are no duplicate program IDs (sorry, forget the terminology...)



<div>
<div class="content wysiwyg-content">
We have two terminal servers, both running the exact same hardware config and software. &nbsp;One died. &nbsp;Can I backup from the other one and restore it to the one that died once we get the dead server in an operational state??? &nbsp;We use Backup Exec
</div>
</div>


We have two terminal servers, both running the exact same hardware config and software.  One died.  Can I backup from the other one and restore it to the one that died once we get the dead server in an operational state???  We use Backup Exec

restore server

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).