Asif Dasl wrote: »
Dynamic Host Configuration Protocol - DNS configuration, WINS, gateway, subnet mask, NTP server usage... just a few that come to mind.
ashokbabusingu wrote: »
DHCP: Dynamic Host Configuration Protocol. DHCP using DORE Process it will assign the IP address Automatically.
Success101 wrote: »
Forgive my ignorance...
A interviewer asked me today: What is DHCP? I told him...it issues IP addresses to clients/workstations/whatever. He said "what else?" Honestly, I don't know.
Clearwaterms wrote: »
When I perform technical interviews, I always present people a problem, and ask them to work through the problem. The goal is that I want to hear what tools they would use to work through a problem.
For example, in the support roles, one of the worst DHCP problems that we used to see was rogue DHCP servers (people bringing in home wifi routers to increase port density) These would start issuing DHCP addresses and if you have a large flat network, it can be a nightmare to track down the device.
During an interview one time, I got a technical question that was phrased like this: "One of the domains in our environment has a AD-DS server that is also a role holder and the role holder has crashed, what would you do to restore the server"
I answered it by saying the most important part is to restore service, so seize the roles in question on a new DC and once the DC is determined down, work through the problem on the server.
I was told that was the wrong answer and that I needed to work through the problem to resolve the server boot issue and users were impacted until we repaired the server.
I told him that was a poor infrastructure design. Safe it to say that 2 days later i received a call that I wasn't an ideal candidate.
Balantine wrote: »
My understanding is that your answer is/was wrong because after seizing FSMO you can't re-add the server: you have to rebuild it. Sometimes this is the way to go, sometimes not. I think the answer the interviewer wanted to hear was something about directory services restore mode or documentation/drivers, offline event logs, crash **** analysis, hardware troubleshooting, backups, etc.
Run dcpromo /forceremoval on Windows Server 2008 DC or re-install it
Do a metadata cleanup: http://technet.microsoft.com/en-us/library/cc736378(v=ws.10).aspx
Promote again the Windows Server 2008 DC and make it a DNS and GC server
Transfer FSMO roles to the Windows Server 2008 DC
Clearwaterms wrote: »
You are correct - except that MS does have a way to do a recovery...After FSMO Seizure is once dead DC off the Domain?