<div>
A domain and a workgroup are 2 different things... if they see the same router then you'll have problems...
</div>


A domain and a workgroup are 2 different things... if they see the same router then you'll have problems...

<div>
Agreed. I suggest you either rename the server (sql01) or build a separate network.
</div>


Agreed. I suggest you either rename the server (sql01) or build a separate network.

<div>
<div class="content wysiwyg-content">
Aloha,<br />
<br />
We have a domain we are trying to abandon because there are several problems with it. We have a server SQL1 in the domain, and we want to get a rebuild of it working in workgroup using the same name. Are we going to have problems with the duplicate names even if they are in different namespaces - for the lack of a better word.<br />
<br />
Mahalo,<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Bill
</div>
</div>


Aloha,

We have a domain we are trying to abandon because there are several problems with it. We have a server SQL1 in the domain, and we want to get a rebuild of it working in workgroup using the same name. Are we going to have problems with the duplicate names even if they are in different namespaces - for the lack of a better word.

Mahalo,
            Bill

Duplicately named servers - one in AD and one in workgroup

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.