Below is the standard I follow when configuring drives for servers, it helps structure files for future management if needed. The below includes drives for running a SQL Server too.
C – OS and system level files. Only
D – Program files for all apps (including SQL Server)
S – Instance level files/SQL Server system databases and log files typically (except for TempDB) (note.. If I have multiple instances, I won’t make 4 of these.. I’d put all SQL binaries for all instances on S in most situations, with the folders providing the separation)
F – Data files for user databases
L – Log file drive for user databases
T – TempDB
X – Backup drive (though in a lot of cases I elect to stream a backup across to a network drive, not paying for a copy after the backup and I’m immediately backing up to storage someplace else.)
So today I found a nice “feature” of the new
Metro Windows 8 interface. Now that the start button can be exposed by moving your mouse to the bottom left of the screen this does not work well when you have RDP in full screen mode.
I have just connected to Windows Server 2012 using my Windows Surface RT Tablet in full screen and wanted to load up the start menu of the RDP session, moving my mouse to the bottom left corner of the screen will infact bring up the start button on the Windows Surface RT OS and not the RDP session.
A workaround for this is to use the start button on the key board, but the fact remains this adds additional confusion. At least the start buttons are somewhat colour coded to help you distinguish which version they relate to!
If upgrading a domain controller ensure the following commands are run first.