Posts made by garak0410

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.

@scottalanmiller said:

The domain name does remain the same. It's the name of the entire domain. There is no other name at any time.

Every machine in a domain whether a node, a DC member or the forest root all share the same name. So the "rename" happens the moment you join the new server to the domain.

And in DNS, the moment you make it a DC it will have an equal share in the DNS round robin name resolution of the domain.

That makes a little more sense...I think.

@scottalanmiller said:

It doesn't. You don't name servers the same thing as old servers.

I hope I didn't confuse everyone again. I understand server name is different but the domain name. I thought I read where it can remain the same

Earlier Question: "If I migrate, the domain remains the same, correct? Dashrender said Yes"

and if so, was wondering at what step does it take over the name of the current domain. Sorry for the confusion...

@scottalanmiller said:

Yeah. If you can do that, it is a better way to go.

OK, so Adprep tonight. Question when looking slightly ahead at my list past ADPREP. If I promote my new DC to a Domain Controller, when does it eventually inherit the name of the soon to be old domain controller? I don't see that option in my list and in this thread even, it is said it can remain the same domain name.

@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'm about to do the next step:

		§ Prepare your Domain for your new Server 2012 R2 Domain Controllers
			□ Run adprep /forstprep from the 2012 DVD on the old server.

Is it safe to run during business hours or should I wait?

OK, so for the file server VM, I am going to create a new VDISK (2 or 2.5 TB most likely) to attach to my file server for the files to copy to. Thanks...

I think it helps to take each thing step by step. I am still aiming for Friday night demotion/promotion.

Question about the virtual file server...it is set up and now I need it to see the D drive from the physical server so it will have its own D drive for the files.. So, when I eventually copy (RoboCopy) the files from the SBS 2003 server to the new file server...where will they be stored? In a VDISK that I attach to the VM or on the Hyper-V host physical drive? Again, sorry for a newbie question but feeling much more confident today.

Good Morning Everyone. Reading the latest updates and slept some of the fear off.

Right now, I've created my two virtual machines and I am downloading updates to them.

VM1: Domain Controller. 2GB of RAM, 1 CPU
VM2: File Server (called services01): 4GB RAM, 2 CPU (this will also host the backup software and antivirus)

When complete, I will let you know. The steps I mentioned several posts ago, I can actually complete up to the demotion and promotion part, correct? Even if the new server will contain the migrated domain name?

@Dashrender said:

You have to set the permission. They don't magically appear. I don't mean to sound curt, I want to make sure we're on the same page. You'll have to set the permissions manually on the sharepoint itself (like your did years ago on the old server) and when using Robocopy supply the correct arguments so that file level permissions are kept during the file copy (I hope you have full access - If you don't I'm not sure how to get around that).

Not curt at all. I'll clarify in the morning...thanks for the help!

@Dashrender said:

@garak0410 said:

I am moving the files AFTER I promote the new one and demote the other one, correct? Or in between the promotion and demotion? (and yes, plan on keeping them on the root of D)

Actually you could move the files anytime after you join the new server to the old Domain. Once that is done, the new server will understand the security principals of the domain and you'd be covered. Now, that being said, I would wait until after you promote the new server to an AD DS server, but you don't have to.

And again, it doesn't matter if I have a separate file server now...same permissions, right? My new login scripts that map the drives will map to the new server...that is if I don't end up with time to do your recommendation of DFS.

@Dashrender said:

@garak0410 said:

• If I migrate, the domain remains the same, correct?

Yes

• If I move the file server to a separate VM, as long as my domain name doesn't change, I should be good, right? That is, permissions to the file server should be OK?

How would you move the file server without moving files? The only thing that makes a file server a file server is the files it servers. The permissions are what you set them to be. Using Robocopy will help in keeping them the same as they were in the old file server. (FYI - MS changed the default permissions on folders I think in Windows 2008 Server - I'd setup the root folder to be the same as the root folder on your old SBS server before you use Robocopy just to make sure don't run into more problems.

Where do you want the pizza delivered?

I am moving the files AFTER I promote the new one and demote the other one, correct? Or in between the promotion and demotion? (and yes, plan on keeping them on the root of D)

It seems like the more questions I ask, the more off course I get. LOL. I thought I "had this" going into my "penciled in" Friday evening migration.

So, in the helpful but still perplexing discussion above, here's what remains and where I want to get back on course...

• If I migrate, the domain remains the same, correct?

• If I move the file server to a separate VM, as long as my domain name doesn't change, I should be good, right? That is, permissions to the file server should be OK?

We have NO Email to migrate (no Exchange) and this isn't counting AV, Files, etc. I just want to get a successful migration in stone, in order first, and then will do the rest of it later...

Thanks as always...wish I could buy everyone in here Pizza!

@scottalanmiller said:

RAID configuration goes before any install.

Right and that is done now. I went with RAID 10 as you suggested! :0

Seems like "nerves" are creeping in again. Heading into this week, I thought this was all I really needed to do as far as the migration goes:

•Order New Server
•Configure
•Install Windows Server 2012 R2
•Download All Updates
•Configure RAID Drives
•Currently Set As:
•Set Roles On Server
•Hypervisor
•Old Server Prep
•Run dcdiag
•Results
•Services
•IsmServ Service is stopped on [PINNSTRDC]
•System Log
•An Error Event occured. EventID: 0x00000457
•8 Of These
•Set Current Domain Functional Level to Windows Server 2003
•Locate your FSMO Roles
•All On Main Server
•Schema Master
•Domain naming master
•Infrastructure Master
•Relative ID (RID) Master
•PDC Emulator
•Prepare your Domain for your new Server 2012 R2 Domain Controllers
•Run adprep /forstprep from the 2012 DVD on the old server.
•Set Up Virtual Machines
•Install Windows Server 2012 R2 and make it a Domain Controller
•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!

Now, got some considerations to make as far as splitting up my DC and file services...

@Dashrender said:

@garak0410 said:

So, if I migrate, my domain name stays the same, correct? Just the server name will change, correct?

Correct. Just the server name changes. But this can and does effect a lot.

For example your file shares. Today they are probably something like \sbsserver\share and after you move to 2012R2 they will change to \2012r2server\share. This means that you have to update all of the connection points that are pointing to the old files shares (normally done through a logon script).

To save yourself this hassle in the future, you can setup DFS now this will change your connection points a little, to something like \domain.name\share\folder The good thing is that in the future when you have to this again, you won't have to change the logon scripts because the \domain.name portion never changes, and you can do all of the changes behind the scenes.

Also don't forget about things like your AV console. If the clients connect to a specifically named server you'll need to change them to point to the new one.

Good idea. In fact, I've done that today. This place is DESKTOP SHORTCUT CRAZY! So I went and made sure all of the shortcuts were to DRIVE LETTERS instead of the servername path. That way, when I roll out new login scripts with the new file server name, the shortcuts will still work.

@Dashrender said:

@garak0410 said:

OK...so when I Robocopy them over, it doesn't matter if domain has changed or if I now have a new file server, as long as it is on the new domain, the permissions (based upon groups and users) should carry over, correct? Again, sorry for my ignorance. I will look at DFS if I have time.

Sorry I didn't realize you were changing domains (why are you doing that?). You'll lose all of the SID associations when you change domains so your permissions won't flow if you are changing domains.

I am migrating from SBS 2003 to Server 2012 R2. Got all the steps from Microsoft. I had originally planned to let my DC do the same as SBS 2003 (file server, DNS, etc. as mentioned above) but now that there are suggestions to split them up, getting a little confused.

So, if I migrate, my domain name stays the same, correct? Just the server name will change, correct?

@Dashrender said:

File permissions have nothing to do with the server they are on, and more to do with the files themselves. Now that being said - the folders that files are in typically push their permissions down to the files.

When you copy your files from the old server to the new one - use something like Robocopy and use the commands that keep the file permissions the same on the copied files.

Also - now is a great time to look at setting up DFS instead of old school UNC shares. This will make life easier for you in 4-7 years when you have to migrate again.

OK...so when I Robocopy them over, it doesn't matter if domain has changed or if I now have a new file server, as long as it is on the new domain, the permissions (based upon groups and users) should carry over, correct? Again, sorry for my ignorance. I will look at DFS if I have time.

You guys are forcing me to think. LOL. I've gotten so spoiled to the one stop shop of Small Business Server. So if I separate them, how does that affect my files and permissions? I know that sounds like a rudimentary question but as Scott said earlier, my nerves are showing and I am perhaps more capable and more knowledgeable than I think I am. If I serve my files on another server, how does that come into play when I do the migration. That is, when promoted, how will my new domain server know to assign permission to the new file server? I know that sounds like a dumb question and it may not be clear, but trying to cross every T and dot every I...

@DenisKelley said:

@garak0410 said:

And these suggestions are even when I allow my DC to be my file server/DNS and also being my anti-virus and backup program host?

DNS is going to be part of the DC anyway. File Server won't be heavily reliant on more RAM or processor cores, but IOPS and Bandwidth, but for a small server, no big deal. The RAM/CPU should be adjusted upwards based on the requirements of the A/V and Backup applications. Why not just leave it a DC and build another VM for the other stuff?

So, say:

VM1: Domain/DNS
VM2: File Server/Web Services/Print Server/Backup Services/Anti-Virus Suite

How much memory for the VM2 would you suggest then for VM2?