@scottalanmiller said:
If you have VMware experience, why go through the extra complication of HyperV?
I'm a Microsoft guy at heart...plus no next to nothing about Linux, should I need to troubleshoot ESXi problems.
@scottalanmiller said:
If you have VMware experience, why go through the extra complication of HyperV?
I'm a Microsoft guy at heart...plus no next to nothing about Linux, should I need to troubleshoot ESXi problems.
I do apologize for my ignorance. I just don't think I am ready (at least by tomorrow) to virtualize. Way too many questions remain and are unclear.
@scottalanmiller said:
What do you mean by your "services VM". I'm not sure I understand the reference.
My file server will be called services01.
This is where my "jack of all IT trades and master of nothing" is coming into play, especially in a solo IT shop. I've managed several hundred terabytes SAN's, managed the VMWare ESX VM's, enterprise backup, server support. But I never get the time to dive into the guts of anything, especially with this job, where I am needed for the smallest or biggest IT need.
So, this may help. Here's my remaining to do list before tomorrow night:
Add the AD role.
•http://technet.microsoft.com/en-us/library/hh472162
•After adding the AD DS role and DNS roles to your new Windows 2012 R2 Server simply click the link under Post-deployment configuration from your server manager titled "Promote this server to a Domain Controller"
•Walk through the wizard and add your new domain controller to your existing domain.
•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
•Demote old Server 2003 Domain Controllers
•Run dcpromo and follow steps.
•Remember: Do NOT demote any domain controller that does not have FSMO roles on them.
•http://technet.microsoft.com/en-us/library/cc740017(v=ws.10).aspx
•Raise Domain Functional Level
•Raise the functional level by opening Active Directory Domains and Trusts. Then right click on domain and trusts and select "Raise Forest Functional Level"
•http://technet.microsoft.com/en-us/library/cc730985.aspx
•Migration Complete! grinning
Need to rethink my backup solution and since you are suggesting the free unitrends, I will get that installed on my services VM.
Also remaining post migration:
@scottalanmiller said:
@garak0410 said:
How do I remote into my host if it isn't on my domain?
I'm lost here. How do you access it when it is on the domain? I've never had being on the domain make a difference. You are running into an implied obstacle that I can't visualize.
The Host is currently in WORKGROUP, so I cannot RDP into it. I can only access it physically. Though all I've read over the months, it doesn't get joined to the domain, correct?
@scottalanmiller said:
@garak0410 said:
Side question - Are remote desktop connects to a Hyper-V machine usually sluggish? I RDP into my VM for services and it is just a little sluggish. Want to make sure that doesn't translate into sluggish performance later when I go "live."
No. Should not be sluggish. HyperV performance should be indistinguishable from physical.
Interesting...it just seems like it takes a little longer to RDP into them and screen refreshing seems slower (I.E. opening file explorer seems a TAD choppy.)
@scottalanmiller said:
There should be zero frustrations with the virtual. If you feel there is any frustration, something is wrong. Virtual is pure win. Easier, safer, more reliable.
I've not seen you have any issues with the virtual portions of your project. If you go physical doesn't every concern remain plus you lose your free backup options plus you lose stability and ease of management?
Maybe it is lack of visualizing that has caused nerves again...at least how to backup if I change to Unitrends or Veeam.
Lingering Questions:
How do I remote into my host if it isn't on my domain?
How does the host get backed up? Separate copy of the backup software loaded on it?
Do I need to backup VIDKS or just the content in the VDISK?
Side question - Are remote desktop connects to a Hyper-V machine usually sluggish? I RDP into my VM for services and it is just a little sluggish. Want to make sure that doesn't translate into sluggish performance later when I go "live."
@scottalanmiller said:
Why is Unitrends off of the table? What did I miss?
@scottalanmiller said:
How does being physical fix the backup issue?
Sorry, I may be confused again. If the free version is being phased out or hard to get now, what can I do? What about VEEAM free?
Physical just to not deal with the frustrations with this entire migration and trying to go virtual too. Just one server for all we did (which really isn't much)...
More of a "vent" because other mounting projects and interruptions all day today so far...
@scottalanmiller said:
And some discussion here too: http://social.technet.microsoft.com/Forums/en-US/0eb5670e-1786-4b1c-b970-30fe0f28583e/adding-server-2012-as-dc-to-server-2003-domain-getting-adprep-error?forum=winserver8setup
Excellent video and links. Thanks...
The backup issue is having me lean toward just going physical and not virtualizing. I asked again if we could spare a few thousand on a backup solution and they said not right now. And the Unitrends option looks off the table for now.
I understand the benefits of virtualization but being that I want to get this done this week as my VBA (yuck) projects are piling up, I may just go physical with a one, do it all, beefy server.
@scottalanmiller said:
That article is only for windows 2003 64bit. If you have 32bit then that KB does not apply.
Well, regardless, I am stuck at this point and I'll begin my research there.
@garak0410 said:
@scottalanmiller said:
I would generally wait until after hours but should be pretty safe in most environments. AD is rarely something that an SMB depends on minute to minute.
Tempting to do now...but I can VPN around 5:30 and run it too.
I tried running ADPREP and it didn't work since my current Domain Controller is 32 bit. So if I understand this article correct:
http://support.microsoft.com/kb/2743367
It has to be run remotely? It was kind of vague.
@garak0410 said:
@scottalanmiller said:
Yes. It does file level. I'll let @katieunitrends or @art_of_shred tell you all the technical details.
Great...downloading to my new "services" VM now.
Assuming it gets installed there and not the hypervisor, correct?
@scottalanmiller said:
Yes. It does file level. I'll let @katieunitrends or @art_of_shred tell you all the technical details.
Great...downloading to my new "services" VM now.
@scottalanmiller said:
Unitrends will backup up to 8 VMs for free.
So when we say VM's, is this like images/snapshots or can it also do file level, SQL and SQL transactional logs?
@scottalanmiller said:
It is hard to imagine that you are not in the "free" backup envelope. How many VMs and how many physical hosts total will you have when the migration is all done?
It is Backup Assist. It is basically a glorified NT Backup. It has served us well.
Since I won't be repurposing the old server for a few weeks, once demoted, we will have the following:
New Server (Hypervisor)
VM1: Domain Controller
VM2: Services (File, Print, Web, Anti-Virus) (need file backup here)
SQL Server (Physical) - We just backup SQL with Backup Assist.
Misc - Some of our shop machines have local SQL that we also backup with BackupAssist.
As mentioned, in order to backup AD, BackupAssist has to be ran from the Domain Controller where it also can backup remote files (including the files on VM2)
So, I am open to other free or low cost solutions where I can backup AD, SQL (with options for Transaction Logs), File Server and any other remote PC from a location other than the Domain Controller.
@scottalanmiller said:
@garak0410 said:
@scottalanmiller said:
The domain name will point to all DCs equally.
So at one point of this migration, both servers will be handing the domain, correct?
Yes. Until you decommission the old one they will be an application cluster.
Excellent...sorry, this would be easier if I could TALK rather than type.
My roadblock now is backups since our current solution wants to run on the domain controller to backup AD. I guess it can but I was really moving toward it being the domain controller and nothing else. Everything I look at a glace shows to be $1000 or more per license per server.
@scottalanmiller said:
The domain name will point to all DCs equally.
So at one point of this migration, both servers will be handing the domain, correct?
@scottalanmiller said:
There is some weird terminology there. What is "the AD machine" mean?
(Masking the real names with generic names)
Current Domain Controller
Name: servernamedc
Domain: domainname.local
New Domain Controller (Virtual)
Name: newserver
I think what I am trying to explain and get an answer to...I want the domain domainname.local to remain the same when it migrates to the new domain controller. I do understand that it will be a new server name. Check. But I've been told in this threat and another one, that the domain name can and will remain the same post migration. If that is true so far, I'll follow up with secondary questions.
SO appreciate your patience.
Another curve ball. New backup software wasn't in the budget and the only way our current suite (Backup Assist) backs up AD only if it runs on the Domain Controller. It can backup files remotely but can only backup AD on the AD machine. So, unless I can get another backup solution (doubtful), I'll have to run backups from the Domain Controller and thus, I may need to bump up the memory some.