Category Archives: Howto Tutorials (EN)

Knowledge Network for Tutorials, Howto’s, Workaround, DevOps Code for Professionals.

Windows Server 2012 NTP Configuration

Windows Server NTP Network Time

Correct time synchronization in an AD domain environment is a prerequisite for stable operation. This article describes how NTP (w32tm) is configured on a Windows Server 2012 (FSMO). As a rule, the PDC operations master is the NTP service server in a forest. A PDC emulator in a domain is synchronized with an external time source. In order for a domain controller to be regarded as a reliable time source, this must be specified explicitly.

In order to make the PDC emulator a reliable time source that regularly synchronizes with time servers on the Internet, the following commands from PowerShell are executed as administrator:

net stop w32time
w32tm /config /syncfromflags:manual /manualpeerlist:"0.ch.pool.ntp.org 1.ch.pool.ntp.org"
w32tm /config /reliable:yes
net start w32time

Show which time server is currently in use.

w32tm /query /source

Execute the time synchronization immediately.

w32tm.exe /resync /rediscover /nowait

The clients and servers in domain forest as well as shared storages can now synchronize the time with the PDC emulator.

The firewall permit UDP port 123 inbound, e.g. allow outgoing.

The NTP configuration can also be done via GPO by calling gpmc.msc.

Computerkonfiguration/Administrative Templates/System/Windows-Timeservice/Timeserver
Group Policy Management Console

Following Test Displays a graph of the offset between synchronizing computers.

w32tm /stripchart /computer:pdc.domain.local /samples:1 /dataonly
W32tm stripchart

The configuration can also be checked in the registry.

HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters

Increase Quota on Exchange Server for Outlook Rules

How to increase Quota for Outlook Rules on Exchange Server

Outlook stores rules for Exchange accounts on the server to automatically move forwarders or emails online from the Inbox to folders, even if Outlook is not running. The synchronization of rules also offers the advantage when using your own account on another computer. The rules are then automatically downloaded from the server in Outlook.

If many rules are created, or rules with long names are used, the quota storage on the Exchange Server may no longer be sufficient, the default size is limited to 64 KB.

If you try to enable the rules that are disabled, you receive the following error message:

One or more rules couldn’t be uploaded to Exchange server and have been deactivated. This could be because some of the parameters aren’t supported or there’s insufficient space to store all your rules.

The RulesQuota can be extended with the following cmdlet from the Exchange Management Shell.

Set-Mailbox joe@banana.org -RulesQuota:256kb

Query current RulesQuota with the following cmdlet

Get-Mailbox joe@banana.org | FL displayname, rulesquota
Set-Mailbox -RulesQuota

Note. If rules are created to move to local PST files, advanced options – only on this computer must be enabled. These rules are also uploaded to the server. But they are not run online because PST folders are only present locally on the computer.

Exchange Server Rules Limitation

Microsoft Exchange server, including Office 365 Exchange Online and Outlook.com, as well as on-prem Exchange servers, limit the number of rules a user can have in an Exchange mailbox. The limit is based on total size, not number of rules, so one user might have 20 rules while another has 30.

Exchange 2003 and older limited

Exchange 2003 and older were limited to just 32 KB worth of rules. The limit was increased beginning with Exchange Server 2007, to 64KB by default and configurable up to 256KB. Later versions of Exchange dropped the lower default setting and gave everyone the maximum 256KB. This includes Office 365 Exchange and Outlook.com accounts.