Tag Archives: time

11.6.1, 11.6.1, 11.6.1, 11.6.1, 11.6.1, 11.6.1, 11.6.1, 11.6.1, 11.6.1, 11.6.1, 11.6.1, 11.6.1, 11.6.1, 11.6.1, 11.6.1, 11.6.1, 11.6.1, 11.6.1, 21, 22, 23, 25, 26, 33, 330, 505, 510, 515, 520, 525, 530, 535, 545, 810, 820, 830, System Manager, Watchguard, WSM, XTM

Watchguard XTM 1050, XTM 2050, XTM 2 Series, XTM 3 Series, XTM 5 Series, XTM 8 Series – Fireware XTM OS 11.6.1 – Build # 346666

Leave a comment

Watchguard XTM 1050, XTM 2050, XTM 2 Series, XTM 3 Series, XTM 5 Series, XTM 8 Series – Fireware XTM OS 11.6.1 – Build # 346666

11.6.1 – Build # 346666 Provides some new features and resolves the following issues:

• This release introduces support for the new high-performance XTM 5 Series models 515, 525, 535, and 545

• Provides an update to our localized user interfaces and documentation

• An XTM device configured in bridge mode can now pass VLAN traffic between 802.1Q switches or bridges

• FireCluster support for XTM 25, 26, and 33 wired models

• Several issues have been resolved in this release that caused XTM devices to crash when configured to use Application Control or IPS [66937, 65426, 65636, 67312, 66135, 67159, 67399, 67310]

• An issue was resolved that caused some XTM device processes to crash when running Mu Dynamics default published vulnerability test [66490]

• An issue was resolved that caused a kernel crash and device reboot [67329]

• The XTM 2 Series device can now handle a large file transfer without interface instability [67367]

• A problem that caused incorrect data to display on the XTM 5 Series LCD screen has been resolved [67197]

• Policy Manager now displays the correct VLAN limits for XTM 5 Series models 505, 510, 520, and 530 with a standard Fireware XTM feature key (not Pro) [67780]

• You can now successfully configure and apply Traffic Management actions for XTM 2 and 3 Series devices from the Web UI [67221, 66645]

• Firebox X Edge e-Series devices can now be successfully managed with templates [67658]

• The notification message sent when a local Log or Report database is down now correctly shows the host IP address instead of “???” [41731]

• The Log Server can now handle backup files greater than 2GB in size without generating an error message: “Error (8199), Exception during backup of oldest log data: File is not a zip file” exception” [66811]

• The DHCP lease activity report now works correctly [66062]

• Log Collector now handles XTM device log data that spans multiple SSL/TLS records without crashing [66347]

• A problem has been resolved that caused poor performance on XTM 2 Series models 25 and 26 because of an incorrect memory allocation for security subscription signatures [67240]

• A deny message is now correctly sent to the web browser in most cases when Application Control blocks content in the Web/Web 2.0 category [66201]

• The WebBlocker automatic database update time is no longer off by one hour when daylight savings time is in effect on the host server’s timezone [67551]

• If you use PPPoE or DHCP for an external interface on an XTM device configured to use multi-WAN, the XTM device no longer loses the default routes for external interfaces after the external interface reconnects [67424, 67520]

• A problem has been resolved that caused a static route to fail after an external interface configured to use PPPoE is disconnected, then reconnected [67520]

• Tagged VLAN traffic is now correctly recognized when an XTM device is configured in Bridge mode [64355]

• The CLl command “restore factory default all” now successfully restores a device to its factory default settings [66240]

• An issue has been resolved that caused Policy Manager to incorrectly display an interface IP address as 0.0.0.0/24 when you viewed a FireCluster configuration for a cluster in drop-in mode [63551]

• The Mobile VPN with SSL process no longer crashes during a FireCluster failover [66118]

You can download 11.6.1 – Build # 346666 from the Watchguard website

Microsoft, Office, Outlook 2007, Outlook 2010

Microsoft Outlook 2007 and Microsoft Outlook 2010 do not archive messages as expected based on the received date instead it uses the modified date by default

Microsoft Outlook 2007 and Microsoft Outlook 2010 do not archive messages as expected based on the received date instead it uses the modified date by default

The archiving features with Microsoft Outlook 2007 and Microsoft Outlook 2010 use the last modified date of an item rather than the sent or recieved date to determine if it should be archived.  This can become a real problem if you have recently moved some old messages to a new outlook folder or you have had to export and import messages using a PST file during a Microsoft Exchange Migration or when a user changes desktop computer or laptop.

To work around this issue you need to fully patch Microsoft Office 2007 or Microsoft Office 2010 and then apply the latest hotfixes for Outlook ased upon the service pack level, for example if you have Microsoft Office 2010 Service Pack 1 installed then please check that you apply Outlook 2010 hotfixes desinged for Office 2010 – Service Pack 1.

Once you have patched Outlook 2007 and Outlook 2010 you will have enabled support for the ArchiveIgnoreLastModifiedTime DWORD Registry value, which in turn lets you switch from archive by last modified date to archive by received date.

To enable the switch in behaviour you simply need to add the following registry value dependant upon your version of Microsoft Outlook

Microsoft Outlook 2007

Navigate using regedit.exe to the following location: HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Preferences

Select to create a new DWORD Value and call it ArchiveIgnoreLastModifiedTime

The value data of ArchiveIgnoreLastModifiedTime should be set to 1 (This enables it)

Microsoft Outlook 2010

Navigate using regedit.exe to the following location: HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Preferences

Select to create a new DWORD Value and call it ArchiveIgnoreLastModifiedTime

The value data of ArchiveIgnoreLastModifiedTime should be set to 1 (This enables it)

You have now turned on archiving by received date in Outlook 2007 or 2010 for the user that you are logged in as, please note that you will need to repeat this process whilst logged in as each user that requires archive by received date on this computer.