<div>
If you clone any Windows Workstation or Server, you must use Sysprep.<br />
<br />
However, cloning machines to use in a cluster or network load balance, is probably not a good idea.
</div>


If you clone any Windows Workstation or Server, you must use Sysprep.

However, cloning machines to use in a cluster or network load balance, is probably not a good idea.

<div>
also as this is a clone, and you are using NLB, you will get issues when trying to create the cluster, and converging will not work with &quot;No interfaces are available for installing a new cluster&quot;!<br />
<br />
because it's a clone.
</div>


also as this is a clone, and you are using NLB, you will get issues when trying to create the cluster, and converging will not work with "No interfaces are available for installing a new cluster"!

because it's a clone.

<div>
ah... no wonder when I tried to add the other cloned node I always get the credentials prompt :-|<br />
<br />
so at the moment I'll <br />
1. sysprep it now and then <br />
2. restart <br />
3. exit the domain<br />
4. restart<br />
5. join the domain
</div>


ah... no wonder when I tried to add the other cloned node I always get the credentials prompt :-|

so at the moment I'll
1. sysprep it now and then
2. restart
3. exit the domain
4. restart
5. join the domain

<div>
yes, then you need to follow the Microsoft kb, if you get issues with the Cluster, if you get the error message,
</div>


yes, then you need to follow the Microsoft kb, if you get issues with the Cluster, if you get the error message,

<div>
ok, I'll search around for SPN / SID duplicate script so that i know what to look for here and then do the sysprep on the problem server.
</div>


ok, I'll search around for SPN / SID duplicate script so that i know what to look for here and then do the sysprep on the problem server.

<div>
<div class="content wysiwyg-content">
Hi All,<br />
<br />
I'd like to know what might be the result of making one VM as terminal Server 2003, joined it to the domain and then clone it for secondary node to be added later on to &nbsp;the Terminal Server Load balancing cluster ?<br />
<br />
is this safe to do ? because now I'm having problem with adding one of the node into the NLB Cluster (it always ask for password and keeps rejecting my DOMAIN\ADmin) ?<br />
<br />
Thanks. 
</div>
</div>


Hi All,

I'd like to know what might be the result of making one VM as terminal Server 2003, joined it to the domain and then clone it for secondary node to be added later on to  the Terminal Server Load balancing cluster ?

is this safe to do ? because now I'm having problem with adding one of the node into the NLB Cluster (it always ask for password and keeps rejecting my DOMAIN\ADmin) ?

Thanks. 

Cloning VM to be serving as Windows Terminal Server 2003

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).

Windows Server 2003

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

VMware, a software company founded in 1998,  was one of the first commercially successful companies to offer x86 virtualization. The storage company EMC purchased VMware in 1994. Dell Technologies acquired EMC in 2016. VMware’s parent company is now Dell Technologies.

VMware has many software products that run on desktops, Microsoft Windows, Linux, and macOS, which allows the virtualizing of the x86 architecture.  Its enterprise software hypervisor for servers, VMware vSphere Hypervisor (ESXi), is a bare-metal hypervisor that runs directly on the server hardware and does not require an additional underlying operating system.