@scottalanmiller said:

So on a user's system when it is failing, what is an nslookup of the A and CNAMEs returning?

What is the preferred syntax to check the A and CNAME with NSLOOKUP? Thanks....

@Hubtech said:

and you've tried ipconfig /release /renew /flushdns /registerdns on these that you were having probs with?

All but RegisterDNS...I will try that. Currently, I have three users I cannot resatore.

And on my new DC/DNS server, this is what it shows under DNS Events:

From Yesterday: SERVERNAME 4015 Error Microsoft-Windows-DNS-Server-Service DNS Server 5/20/2014 7:39:14 AM The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error.

From Today: SERVERNAME 4013 Warning Microsoft-Windows-DNS-Server-Service DNS Server 5/21/2014 6:38:37 AM - The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.

And Again, this is only happening to the DNS (CNAME) of our FILESERVER...all other DNS name resolutions are working fine. I wanted to avoid rebooting the file server but wonder if it could help?

Quick update...seems to be isolated to our file server...it has a physical name and a CNAME and when these certain users have the problems, they can only get to the server by IP Address. Like right now, I can access the file sever by both names. I have a single user (currently) who can only access it by IP address.

I started having weird DNS issues today. Those who have helped me here know that I went through a solo migration recently. Due to my time needed on other projects, I've yet to complete the final steps on our Domain Controller / DNS server migration. But I do plan on accelerating that to later this week or weekend.

Here's what is going on. I get calls this morning about users who could log in, get POP3 email and internet but all of their drive mappings were dead. Several users were able to reconnect after a few reboots.

When I got to the office, I went to someone who was yet reconnected. He was able to go to the IP address of the server but not the DNS name. I went into his network settings and set his preferred DNS server to the new Domain Controller / DNS Server, rebooted and he was fine.

Keep in mind on this next step that we do not currently use DHCP (but plan to.) Some users have static IP's due to some past frequent IP conflicts. And much of those users had this problem today. Their preferred DNS server was the old server. So I changed it to the new server and rebooted. Still no drive connections, so I am guessing replication hadn't taken place? (I assuming they replicate in their current shared state (though the new DC is the primary DC now.) So, on these users and I took them off a static, set the DNS to the new server, rebooted and they were fine.

So, what is going on at the moment? I've never had a DNS issue of this magnitude. I am assuming it is because the old server is still the primary DNS server.

Thanks everyone...

@Dashrender said:

I hate to say it.. but if time is an issue, and there is nothing else on this server (which it sounds like since you can reboot it 20 times a day) why not just build another VM and scrap this one? If you want to save it for later and try to trouble shoot it when you have nothing better to do.. Ok do that.

Whew...would hate to have to do this...it is already sharing duties with the soon to be demoted old domain controller...I can't imagine what would cause this problem since I keep this machine very clean.

@garak0410 said:

@alexntg said:

Try http://social.technet.microsoft.com/Forums/systemcenter/en-US/24ab19c2-84de-4b89-beea-b0e3053c2e61/cannot-install-due-to-pending-reboot-prerequisite-check

Looking at this now...I do have this key and there is a file located at the directory that it lists as PendingFileRename called 9a072afe.BUD...deleting the key and rebooting.

Deleted key...rebooted...retried the feature install...same problem...checked to see if PendingFileRename came back and it didn't.

@alexntg said:

Try http://social.technet.microsoft.com/Forums/systemcenter/en-US/24ab19c2-84de-4b89-beea-b0e3053c2e61/cannot-install-due-to-pending-reboot-prerequisite-check

Looking at this now...I do have this key and there is a file located at the directory that it lists as PendingFileRename called 9a072afe.BUD...deleting the key and rebooting.

@Bill-Kindle said:

@garak0410 said:

Same problem...says the server needs to reboot.

This is very odd since this is a very new VM with nothing really changed on it...

Are you 100% positive you are on the correct VM and not accidentally working on a different VM from this VM's server manager?

Yes sir...I've done this both through remote desktop and on the console for this server on the host...same darn error each time I try to add REMOTE ACCESS role...

Same problem...says the server needs to reboot.

This is very odd since this is a very new VM with nothing really changed on it...

@Bill-Kindle said:

@garak0410 Run that cmdlet only on the VM, not the host machine or you will reboot the entire hyper-visor.

For sure...

@Bill-Kindle said:

@garak0410 said:

@Bill-Kindle said:

How are you restarting the server? That message you are seeing means you have not restarted, or restarted properly. Are you logged into that server that you are working on or are you on another system working with Server Manager?

I've restarted the Server (VM) at the console on the host several times. It keeps coming back with it needs a reboot.

Don't restart that way.

Open up a powershell prompt and type this in:

restart-computer

and press enter.

Trying now...

@Bill-Kindle said:

How are you restarting the server? That message you are seeing means you have not restarted, or restarted properly. Are you logged into that server that you are working on or are you on another system working with Server Manager?

I've restarted the Server (VM) at the console on the host several times. It keeps coming back with it needs a reboot.

I am having a frustrating time adding Remote Access role to my 2012 R2 domain controller (HyperV VM)...

It keeps failing with THE REQUEST TO ADD REMOVE FEATURES FAILED

I've tried repairing my component store with no luck...it keeps telling me the server requires a restart.

Could this have ANYTHING to do with the host machine needing a reboot? That is one thing I've not tired yet.

Let me digress some. I didn't get too far this weekend. For one, it was the first weekend our shop had Friday/Saturday workers all year. So just to be safe, I didn't complete the demotion.

However, I did try adding remote services to the new domain controller and it kept failing, saying it needed to reboot. I would reboot, retry and it still said cannot install until I reboot. Sounds as if the component store is corrupted and will check that out soon.

So currently, my new and old domain controllers are running but here's a problem I am having now.

My VPN users can sign into VPN but can no longer remote desktop. They have all the required permissions but alas, since that aborted install, they cannot remote desktop. If they are a domain admin (me and my manager), it works. Any ideas here? We've used the general Remote Desktop security group in the past and it is no longer working.

Question about moving VPN services...it is as easy as assigning the role (Remote Services) to the server and then point the firewall L2TP and PPTP to the new IP of the server?

@scottalanmiller said:

You can't do an IP alias in DNS because if you think about the mechanics, hitting an IP address means you never talk to DNS. So that wouldn't do anything.

Instead just add the IP address to the NIiC of the new server.

OK...so complete the DC migration, test it, then demote it and then put its old IP in the NIiC on the new one and bam, problem solved?

@scottalanmiller said:

Not sure what you mean.

An "A" record maps a hostname to IP address.

A CNAME is an alias of one hostname to another.

That's is all that either one does. What exactly do you want to have happen?

Sometime back, you suggested a CNAME for the file server to point to the new one. Understand that one...easily done.

In another post here: HERE

I mentioned a VBA project that "hard coded" the IP of the old file server to older jobs and it doesn't change with subsequent openings. Only the NEW jobs have the new server info. Someone mentioned a CNAME but if that is only for a DNS name, I may be screwed. I wouldn't use an A record, would I for this? The file server already has an A record for it's current IP address.

From what I learned in this thread, giving the new file server the same IP as the old one is NOT recommended, right?

And About the CNAME for the old server...basically CNAME it to the new file server, correct? And that application that basically "hard codes' the old server's IP address...can I also CNAME the IP?

@garak0410 said:

Well, I am in a position where I do need the CNAME of the old server in place so we can fix an in house software quirk.

Going back to my check list, this appears to be the next step:

  	§ Transfer FSMO Roles to new Server 2012 R2 Domain Controller
  		□ Transfer all 5 or one at a time and start demoting your old Server 2003 DC's in the next step. But the key to remember is to NOT demote any of the current domain controllers that have any of your FSMO roles on them. Be sure to transfer them off first before proceeding to DC demotion.
  		□ http://blogs.technet.com/b/canitpro/archive/2013/05/27/step-by-step-active-directory-migration-from-windows-server-2003-to-windows-server-2012.aspx

And all of the suggestions lead to that I can do this during business hours....so, taking this step by step. OK to proceed as according to the link above?

I'm doing all remaining steps tonight...before I demote the old one, can it be tested by simply shutting down the old server before I demote, to make sure the new DC is handling it OK?

@Seth-Cooper said:

Yep, keep the device for personal use.

I am curious though, how do you get into a gig to review tech and keep the hardware? Sounds pretty cool, do you work with a site we can read the reviews?

Thanks!

I started writing reviews for a company on a volunteer basis in the late 90's and sometime in the late 2000's, they approached me to be a part of their review and keep program. I never thought my writing skills were all that good but it made an impression them.