Tuning Your Windows Server for GroupWise

Wikis > Caledonia Private Wiki > GroupWise Administration > Tuning Your Windows Server for GroupWise

The following information can greatly increase your Windows 2008 R2 server performance when provisioned as a GroupWise server.

Virtual Servers

For Virtual Servers, a few important configuration issues are important:

  • CPU: Allocate at least two vCPU
  • Memory:  Allocate at least 4GB of memory

All Servers

GroupWise is very I/O intensive.  While CPU and Memory are important for GroupWise, a poorly configured and slow disk system is detrimental to GroupWise performance.

  • For best results, the GroupWise data store should be located on its own LUN and Drive letter (i.e. F:\domain, F:\po)
  • Windows indexing should be turned off for the GroupWise data store (for example F:Turn off Indexing on the E: drive
  • Disable Virus Scanning for the GroupWise data store (GroupWise data is encrypted and compressed, and not only causes slow downs, but can generate false positives, endangering the GroupWise data).
  • Registry edits (generally require restarting server)
    • Disable the automatic creation of short file names (8.3) – this will improve performance by avoiding the extra work needed to create the short file names for applications that cannot read long file names.
      • HKLM\SYSTEM\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation = 1
    • Disable the automatic update of date/time stamping (last access update) – this is the equivalent setting to the NoATime that is useful on both NetWare and Linux servers.
      • HKLM\System\CurrentControlSet\Control\FileSystem\NtfsDisableLastAccessUpdate = 1
  • Enable disk defragmentation for the GroupWise data store drive.  If you come from the NetWare (or Linux world – oddly I’ve had a few of those migrations), you are unaccustomed to needing to defrag your disks.  However, Windows can suffer greatly from disk defragmentation.  You should auto schedule a defrag once a week.  
    • Right click on E: drive > Tools tab > [Defragment Now…] > [Configure schedule…]
  • Set Windows Data Execution Prevention (DEP) to “Critical Only”

Here are a few settings that are more for convenience sake.

  • To allow administrators to use ConsoleOne directly on their workstations, rather than accessing the server to do so, define a Windows Share for the GroupWise data store and map a drive from the workstations to the GroupWise domain server.
  • If the Windows Firewall is enabled, add GroupWise Port exceptions to it.  This can include MTP ports, HTTP Monitor ports, SOAP ports, GWDVA ports, and the like.  While I typically do not worry too much about having the local firewall on for Linux servers, and rely on the outward facing firewalls to protect internal servers, with Windows servers it can be prudent to protect them locally, since they are favorites of hackers and malware writers.
  • When setting up GroupWise Agent Startup files, do not use a UNC Path value, but rather reference the GroupWise data store by drive letter.