Based on recommendations and best practices from Microsoft, and information I found here, I compiled a FSMO placement scenario for 2 domain controllers:
DC1 | DC2 |
PDC Emulator RID Master Infrastructure Master | Schema Master Domain Naming Master Global Catalog |
Also, if your domain is top-level in the AD forest, configure DC1 to sync with external time sources.
To transfer roles, it is recommended to use Powershell's Move-ADDirectoryServerOperationMasterRole.
An excellent TechNet-article explained how rules are evaluated in Windows Firewall, specifically in what order and which rules take precedence over others.
Although unsupported, it is possible to install Microsoft Security Essentials on a Windows Server 2012.
To do this, set the compatibility of the downloaded file to Windows 7, then start that file with the parameter /disableoslimit.
The installation goes without a problem, and as far as I can tell, there are no compatibility issues.
You can download the latest version of iSCSI Initiator for Windows 2000, 2003 and XP. This will upgrade any previously installed version to the latest version:
Sometimes, being an Administrator just isn't enough. In that case, try being the SYSTEM account... You can run processes as the local SYSTEM account quite easily with PsExec (64-bit).
Use it as follows:
psexec -i -s cmd.exe
The command above would run a command prompt as the SYSTEM account. You can replace cmd.exe with something else, although from a command prompt, you can basically run anything else, all as the SYSTEM account.