📎 AI Summary:
The thread discusses a setup issue where a server configured as an imaging server with DHCP isn't issuing IP addresses. The original poster questions whether Windows activation might be blocking DHCP, but subsequent responses clarify that activation doesn't affect DHCP functionality. Experts suggest that the problem may stem from the server's role setup, such as Active Directory or network configuration issues like NIC binding, rather than activation status.
The thread discusses a setup issue where a server configured as an imaging server with DHCP isn't issuing IP addresses. The original poster questions whether Windows activation might be blocking DHCP, but subsequent responses clarify that activation doesn't affect DHCP functionality. Experts suggest that the problem may stem from the server's role setup, such as Active Directory or network configuration issues like NIC binding, rather than activation status.
Solution
the first roll is tip ADDS (Active Directory Domain Services) and from that point on your system becomes a true server as different to a local machine... I would assume you don't have your domain set up or that the other computers don't get seen by the server as being in that domain yet.
