Small Business Server 2003 to 2012 R2 Migration and Virtualized Domain Controller Questions
-
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?
-
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?
-
@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?
-
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.
-
@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?
-
@garak0410 said:
@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?
Yup. That should do it.
-
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?
-
Is that the Windows built in VPN service?
-
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.
-
It's been nine months since the last update. Where are things now with this?
-
@scottalanmiller said:
It's been nine months since the last update. Where are things now with this?
We are running quite well, thanks to everyone who helped out. Since The day we went live back in late March, beyond windows updates, I've only had to reboot the host twice due to "slowness" issues...it has been rock solid and totally love it...and thanks @scottalanmiller for encouraging me and talking me into virtualizing...
-
Glad to hear that it is all working well!
