SOLVED DHCP role not added in AD Domain server, is it any cause for future error?

[Gangaiah Lakkakula]

My AD Domain server, SCCM site server and client systems are in same private network, this private network separated by one router(this router connected to other network). This router assigning IP's perfectly to all AD Domain server, Site SCCM server and clients. Here I changed all clients and SCCM site server to AD Domain server's domain. Here actually i'am not added DHCP role in AD\Domain server, is it\it is any cause for above error? If yes, then which kind of cause would occur.
My router default Ip 192.168.1.1
AD Domain server IP 192.168.1.2
It starting assigning Ip's from 192.168.1.3 dynamically and joined in AD Domain server domain.


Thanks advance.

 

[Prajwal Desai]

If you are not using any DHCP server then the IP's will be provided by router. I see that the new clients are receiving the IP addresses from the same range that the domain controller is in.

 

[Gangaiah Lakkakula]

Thanks @Prajwal Desai , So with this any cause while deploying OS with SCCM site server on clients?

 

[Prajwal Desai]

It shouldn't cause any issues as far as client machines are communicating with DC.

 

[Gangaiah Lakkakula]

Let me know, while we deploying OS on client machines, we need to enable PXE booting. So client's automatically loose there contact with DC, mean while same time OS Package files might not be download properly, then we will get errors, so ultimately OS not deployed properly. So can you tell is it correct analysis, isn't it? And let me know there is any OS deployments methods with static IP arrangement?

 

[raf]

how to configure option 66 67 with no DHCP Server

 

[Prajwal Desai]

Hi, is this issue resolved ?. Please update the thread.