Small Business Server 2003 to 2012 R2 Migration and Virtualized Domain Controller Questions
-
@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.
-
What error are you getting? Not sure what problem you are running into.
Really this should be its own question as it isn't really a continuation of the original thought and needs discrete troubleshooting. Tacking it on into the stream of this discussion will make it hard to troubleshoot and anyone joining now won't see this question in the middle.
-
-
And I assume that you've been through this: http://technet.microsoft.com/en-us/library/hh472161.aspx#BKMK_NewAdprep
-
-
@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.
-
Why is Unitrends off of the table? What did I miss?
-
How does being physical fix the backup issue?
-
@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...
-
But it IS free. Why turn it down just because the price might go up after you've gotten it for free. It's already yours and free.
And "going away" is a soft term. You are on Spiceworks and if you search the thread about free going away you'll see that for spiceheads it is remaining available for free.
-
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?
-
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."
-
Going virtual isn't related to you moving away from one server. You are combining concepts in your mind. Even if you go with a single server you should still be virtual.
That's what I'm trying to get across. If you perceive any negative to going virtual - that's a red flag. It means that almost certainly you are tying something to virtual that is not a part of it.
-
@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.
-
@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? -
@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.
-
@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.)
-
@garak0410 said:
How does the host get backed up? Separate copy of the backup software loaded on it?
I don't even back up my hosts. They are just containers. Nothing is stored on them.
You can just take an image of the disk if you want.
This is where installing to USB is recommended. Just have a spare USB copy laying around.
-
@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?
-
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! grinningNeed 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:
- Move antivirus over (got a plan from Symantec to make it work, even with server name change)
- RoboCopy files over from old DC to the E drive on services01
- Get login scripts edited to point to services01 for drive mappings.
- Test and verify some workstation logins.
