Remote desktop connection to a server takes very long time to connect

The following steps could speed up the RDP connection:
1. Open Network Connections in the configuration panel.
2. Right-click the icon of the network interface which is responsible for the connection to your server and select Properties.
3. In the Networking tab, click on the Configure… button.
4. In the next window, switch to the Advanced tab.
5. Click the Large Send Offload Version 2 (IPv4) and change the value to Disabled.
6. Click Start > click Run > type regedit and then click OK.
7. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
8. In the right pane, make sure that the DisableTaskOffload registry entry exists. If this entry does not exist, add the entry:
DWORD Value: DisableTaskOffload
Value Data: 1
9. Exit Registry Editor.
The following commands need to be entered through the command shell.
Which you can enter by doing: start > run > enter cmd.
netsh interface tcp set global autotuninglevel=disabled
and
netsh interface tcp set global autotuninglevel=highlyrestricted

Warning 25051 - Service Account is not secure in its current configuration

Issue:
When installing the Forefront Identity Manager Synchronization Service or the Forefront Identity Manager Portal you may be presented with a popup Warning 25051 which informs you that the service account is not secure in its current configuration. You are able to continue with the installation if you wish or you could stop the installation and secure the service account being used prior to installation of these features

Cause:
Prior to installing the Forefront Identity Manager Synchronization Service or portal the Service accounts used for each feature are not configured on the server that the feature is to be installed on using the secure method

Resolution:
On the server that host the Forefront Identity Manger Synchronization Service or FIM Service and Portal is installed on.
1.Open up Local Security
2.Expand Local Polices
3.Click on User Rights Assignment
4.Scroll down to locate the following policies
  Deny log on as a batch job
  Deny log on locally
  Deny access to this computer from the network

For each of the above add the service account that is used for the installing feature. For example, on the server that the Synchronization Service is installed on this may be the FIMSync Service account, and on the server that host the FIM portal it may be the FIMService account that is used during the initial configuration. Right Click on the policy you wish to add the service account to and click on properties and then click on Add user or group, Add the correct (User) Service account for the feature being installed to that policy. Repeat steps for each policy.

Enable Proxy Option for Operations Manager Agents?

TO enable the proxy in the GUI go to Administration > Device Management > Agent 
Managed > Right Click the Server you wish to act as a proxy and click Properties > Security Tab > Check Allow this agent to act as a proxy and discover managed objects on other computers

To enable an agent proxy for all agents that are currently disabled the run:

get-SCOMagent | where {$_.ProxyingEnabled -match “False”} | Enable-SCOMAgentProxy

To enable proxy agent for all future agents the run the following in PowerShell ISE:

add-pssnapin “Microsoft.EnterpriseManagement.OperationsManager.Client”;
new-managementGroupConnection -ConnectionString:scomserver.domain.com;
set-location “OperationsManagerMonitoring::”;
Set-DefaultSetting -Name HealthService\ProxyingEnabled -Value True