<div>
The only time I can think of when the workgroup name gets &quot;registered&quot; is when the pc receives a DHCP IP during PXE booting so that it can communicate to the SCCM server. &nbsp;And yes, it happens to be the same IP.<br />
<br />
So now the question is how to track down the culprit and delete the workgroup name from the network?
</div>


The only time I can think of when the workgroup name gets "registered" is when the pc receives a DHCP IP during PXE booting so that it can communicate to the SCCM server.  And yes, it happens to be the same IP.

So now the question is how to track down the culprit and delete the workgroup name from the network?

<div>
<div class="content wysiwyg-content">
Steps that I am experiencing.<br />
<br />
SCCM (System Center Configuration Manager).<br />
<br />
Have a base Windows 7 image with a workgroup name of WIN7BASE. &nbsp;The base image is clean and never been joined to the domain.<br />
<br />
Imaging a new pc via PXE boot with a prompt during the OSD (Operating System Deployment) process for the new computer name.<br />
<br />
Auto joins the domain during the Task Sequence with DHCP.<br />
<br />
All is well at this point. &nbsp;The image is deployed, pc is joined to the domain and is registered in AD and DNS as the new pc name.<br />
<br />
I then discovered in my antivirus management console (Sophos) which routinely scans AD for new pcs that the pc name appears as both the workgroup name and the new pc name.<br />
<br />
I can also ping both names and both return the same IP address.<br />
<br />
The workgroup name does not appear in AD or DNS.<br />
<br />
Any ideas?
</div>
</div>


Steps that I am experiencing.

SCCM (System Center Configuration Manager).

Have a base Windows 7 image with a workgroup name of WIN7BASE.  The base image is clean and never been joined to the domain.

Imaging a new pc via PXE boot with a prompt during the OSD (Operating System Deployment) process for the new computer name.

Auto joins the domain during the Task Sequence with DHCP.

All is well at this point.  The image is deployed, pc is joined to the domain and is registered in AD and DNS as the new pc name.

I then discovered in my antivirus management console (Sophos) which routinely scans AD for new pcs that the pc name appears as both the workgroup name and the new pc name.

I can also ping both names and both return the same IP address.

The workgroup name does not appear in AD or DNS.

Any ideas?

Can ping both netbios and old workgroup name

The Windows operating systems have distinct methodologies for designing and implementing networks, and have specific systems to accomplish various networking processes, such as Exchange for email, Sharepoint for shared files and programs, and IIS for delivery of web pages. Microsoft also produces server technologies for networked database use, security and virtualization.

Windows Networking

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

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.