There is new file server functionality in Windows Server 2012. The file server should be upgraded to Windows Server 2012.
(Specifically look up - ReplicationFrequencyinMinutes)
The Migrate to a physical computer with a different processor version setting ensures that the virtual machine uses only the features of the processor that are available on all versions of a virtualization- capable processor by the same processor manufacturer. It does not provide compatibility between different processor manufacturers.
Note: To enable processor compatibility mode for a virtual machine
* ClickStart, point toAdministrative Tools, and then clickHyper-V Manager.
* Select the server running Hyper-V and the desired virtual machine.
* If the virtual machine is running, you must shut down the virtual machine to change the processor compatibility mode setting.
* In the Action pane, click Settings, and then clickProcessor.
* Expand Processor, and clickCompatibility.
* Click Migrate to a physical computer with a different processor, and then clickOK.
Reference: Processor Compatibility Mode in Hyper-V
Choice 1: Require additional authentication at startup
Choice 2: Choose how BitLocker-protected operating system drives can be recovered
* Choice 1: Require additional authentication at startup
This policy setting is used to control which unlock options are available for operating system drives.
You can set this option to Require startup PIN with TPM
Choice 2: Choose how BitLocker-protected operating system drives can be recovered This policy setting is used to configure recovery methods for operating system drives.
In Save BitLocker recovery information to Active Directory Domain Services, choose which BitLocker recovery information to store in Active Directory Domain Services (AD DS) for operating system drives. If you select Store recovery password and key packages, the BitLocker recovery password and the key package are stored in AD DS. Storing the key package supports recovering data from a drive that is physically corrupted. If you select Store recovery password only, only the recovery password is stored in AD DS.
Reference: BitLocker Group Policy Settings
SO...the first part of this answer is:
1. Create a new site object named Branch2
*When you create the new site Branch2 you will be prompted to associate it with a site link...right now we only have one site link (Main-Branch1). Hit Finish
2. Remove Branch2 site from the Main-Branch1 Site Link
*In order to move a site into a new site link, you must first remove them from their previous site link....In this case Branch2 was put in Main-Branch1 when we create the new site because we didn't have another site link to associate the new site with at the time we created it.
3. Create a new site link object named Main-Branch2
*When you create the site link object you will be asked to place the appropriate sites in this link...choose Main and Branch 2 Because we are using Interstice topology replication, ISTG (similar to KCC with Intrasite) will build a logical transitive connection path between all site links because site link bridge is enabled by default and is a Microsoft best practice to leave this default.
By default a site link has a default cost of 100 so the Main-Branch1 site cost 100. Since we do not have a site link established from Branch2 - Branch1, ISTG will create a logical patch that travels along the Main-Branch2 site link (cost 100) and through Main-Branch1 site link(cost 100) to establish replication connection in the event the least cost path goes down. Since the logical path =200, Branch2 will only replicate with Branch1 if the site link to the Main Site goes down.
To configure the CDP and AIA extensions on CA1
* In Server Manager, click Tools and then click Certification Authority.
* In the Certification Authority console tree, right-click corp-CA1-CA, and then click Properties.
* Click the Extensions tab. Ensure that Select extension is set to CRL Distribution Point (CDP), and in the Specify locations from which users can obtain a certificate revocation list (CRL), do the following:
Reference: Configure the CDP and AIA Extensions on CA1
/ In application policy drop-down list select Certificate Request Agent.
/ The Issuance Requirements Tab
* Application policy. This option specifies the application policy that must be included in the signing certificate used to sign the certificate request. It is enabled when Policy type required in signature is set to either Application policy or Both application and issuance policy.
Reference: Administering Certificate Templates
*Only the TCP Protocol is needed
* Only a Single host is required.
Reference: Create a new Network Load Balancing Port Rule
* NTFS encrypted
Azure Backup supported
* NTFS compressed
Azure Backup supported
* At this time you cannot backup entire Azure Virtual Machines or perform a system state backup of Azure Virtual Machines using Azure Backup.
Note: * NTFS encrypted + NTFS compressed
Azure Backup not supported
Reference: Azure Backup Frequently Asked Questions (FAQ)
* BranchCache is disabled by default on client computers. Take the following steps to enable BranchCache on client computers:
* Turn on BranchCache.
* Enable either Distributed Cache mode or Hosted Cache mode.
* Configure the client firewall to enable BranchCache protocols.
* Distributed Cache mode
If client computers are configured to use Distributed Cache mode, the cached content is distributed among client computers on the branch office network. No infrastructure or services are required in the branch office beyond client computers running Windows 7.
Hosted Cache mode
In hosted cache mode, cached content is maintained on a computer running Windows Server 2008 R2 on the branch office network.
Reference: BranchCache Early Adopter's Guide, Client Configuration
* Filtering Mode: Multiple hosts
The Multiple hosts parameter specifies that multiple hosts in the cluster will handle network traffic for the associated port rule. This filtering mode provides scaled performance and fault tolerance by distributing the network load among multiple hosts. You can specify that the load be equally distributed among the hosts or that each host will handle a specified load weight.
Select Affinity Single or Network to ensure that all network traffic from a particular client is directed to the same host.