By default the standard outlk12.adm templates do not come with a configuration of Outlook Anywhere. You can configure the “Configure Outlook Anywhere user interface options” options to disable or grey out the settings. However, this DOES NOT disable Outlook anywhere, just user interaction with it.

You will need to download a new administrative template that Microsoft released in this hotfix. If you don’t like reading Microsoft’s wonderful support site instructions or Microsoft changes their support site after this blog post, here is the file and instructions paraphrased.

1. Download Add-On Outlook Anywhere Administrative Template here…article-961112 (unzip to reveal article-961112.adm file).
2. In the Group Policy Object Editor add the Article-961112.adm file:
Right-click Administrative Templates and click Add/Remove Templates.
In the Add/Remove Templates dialog box click Add.
In the Policy Templates dialog box locate and select the Article-961112.adm file. Click Open.
Click Close in the Add/Remove Templates dialog box.
3. Under User Configuration in Administrative Templates expand the policy node labeled Article 961112 Policy Settings. (Note: You may see this under Classic Administrative Templates in a sub-menu)
4. Select the Outlook Anywhere (RPC/HTTP) node to list the following policies under the Setting column in the right-pane:

RPC/HTTP Connection Flags -> Set to Enabled -> No Flags
Proxy Server Name -> Do not change
Only Connect if Proxy Server certificate has this principle name -> Do not change
Proxy authentication Setting -> Do not change

5. Double-click each policy to configure the appropriate RPC/HTTP setting for your Outlook clients.

Using Group Policy Objects can be a huge time saver, but if used improperly can be a big headache. Once you’ve messed around with GPO settings enough, you quickly figure out that you need to create new GPOs for specific programs, events, etc… that are not all in one GPO. This gives you a lot more flexibility and makes it very easy to track down troublesome GPO related issues when done properly. Now lets say you create a Power Savings GPO that you want to apply only to computers that meet certain conditions. WMI, Security, and Site Filtering are all too broad for this task, and you want to use Item-Level Targeting. After you create your Group Policy Object you will need to add this setting to the GPO.

In Group Policy Management Settings
-User Configuration -> Preferences -> Control Panel -> Regional Options
-Right-Click and Select New
-Navigate to Common Tab
-Check Item-Level Targeting and Press Targeting…

From here you will be able to select tons of critaria that you want to meet for your GPO. This can be system requirements to install a program, or only select certain Operating Systems. You can also add is not tags that will rule out any computer that meet that criteria. The options are limitless and its very easy to incorporate in your GPO. Personally, I never use the often complicated and time consuming WMI Filters anymore.

Setting up the windows time service can be a bit challenging at times, but I run these steps on my servers and it works every time. (Fixes clocks being off on servers and time discrepancy’s between server and clients)

First, Lets take care of the server setup(Open regedit on time server, Verify registry settings):

1. Change Windows to use the NTP protocol for time synchronization: Key: HKLMSYSTEMCurrentControlSetServicesW32TimeParameters
Value: Type
Data: NTP
————
2. Configure the AnnounceFlags value:
Key: HKLMSYSTEMCurrentControlSetServicesW32TimeConfig
Value: AnnounceFlags
Data: 5
————
3. Enable the NTP server value:
Key: HKLMSYSTEMCurrentControlSetServicesW32TimeTimeProvidersNtpClient
Value: Enabled
Data: 1
————
4. Specify the NTP server to use:
Key: HKLMSYSTEMCurrentControlSetServicesW32TimeParameters
Value: NtpServer
Data: us.pool.ntp.org,0x1
————
5. Select the NTP polling interval:
Key: HKLMSYSTEMCurrentControlSetServicesW32TimeTimeProvidersNtpClient
Value: SpecialPollInterval
Data: 900
————
6. Configure the time correction settings:
Key: HKLMSYSTEMCurrentControlSetServicesW32TimeConfig
Value: MaxPosPhaseCorrection
Radix: Decimal
Data: 3600
————
Key: HKLMSYSTEMCurrentControlSetServicesW32TimeConfig
Value: MaxNegPhaseCorrection
Radix: Decimal
Data: 3600

Once the registry settings have been verified restart w32time service (net stop w32time / net start w32time) followed by running the following command: w32tm /resync

Most people over-think how to correct the time on the workstation setups. Its very simple, do NOT use a GPO! Simply add the following line to your start-up script

• net time \yourtimeserver /set /yes

Have your users logout and back in and they will be synced with the server.