Pierrot

Many thanks!

Thank you @anyweb for the prompt response, much appreciated. Another noob question (merely to confirm), the below is basically the FQDN of the issuing CA server, followed by the common name of the issuing CA server? IssuingCA.windowsnoob.lab.local\windows noob Issuing CA"

Hi @anyweb - Wondering if you could explain this command? Primarily starting from \windows noob issuing CA - Is this the name of the Certification Authority in the certsrv console on the Issuing CA server? And is the windowsnoobissuingca.cer previously configured or is this a new one and can be named whatever we need it to be? Thanks. certutil -config "IssuingCA.windowsnoob.lab.local\windows noob Issuing CA" -ca.cert windowsnoobissuingca.cer

Hi, Here's a dilemma, the DHCP server on 2012 R2 is displaying APIPA 169.254.174.75. It is authorized, and, the static IP or FQDN is also authorized. I can't authorise the 169.254.174.75 from the DHCP server a it gives error "Parameter is incorrect". Using netsh command seem to do the trick, though. What I tried: - Removed DHCP and promote it again, successfully but it still shows 169.x.x.x. - Removed it from Active Directory Site and Services (CN=Configuration). - Tweaked the registry. - Disabled all other unused NICs. - RPC service is running. When I ping the server I get: reply from fe80::e543:83da etc... The funny thing is, that, it is leasing IP addresses. The DHCP server is working (so far) but, not displaying the FQDN. I can also PXE boot from DHCP. Any ideas, tips?