000023349 - SecurID- questions about Daylight Savings Time and the RSA appliance

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000023349
Applies ToRSA SecurID Appliance 1.0
RSA SecurID Appliance 2.0
RSA SecurID Appliance 2.0.1
IssueIs the SecurID appliance compatible with the changes in Daylight Savings Time

1. None of the versions of the RSA Appliance, 1.0, 2.0, or 2.0.1, have the appropriate Microsoft fix in the factory configuration. The Microsoft fix was not available until after the appliance was released, and could not be included.

2. A 1.0 or 2.0 RSA Appliance may have been upgraded to 2.0.1 (highly recommended for the best operation). However, if you upgrade a 1.0 or 2.0 appliance to 2.0.1 using the process in the Upgrade Manual, Page 11 says to only install specific "Highly Recommended Operating System fixes" from Microsoft, the exact fixes are listed on P24-27. The Microsoft DST fix was released after the Upgrade Manual was written, and is not included in the list.


The RSA Appliance should be upgraded to the latest version of the Appliance software. During the Microsoft upgrade portion of the Appliance Upgrade process, the latest version of the Microsoft Daylight Savings time fix should be applied to the appliance; as of this writing, it can be found in Microsoft Knowledge Base 931836 .  The Appliance should then be rebooted,as part of the Microsoft upgrade.

Explicit instructions for applying OS patches on the Appliance can be found on our RSA SecurCare OnLine web site:

If it is not possible to install the latest version of the RSA Appliance software at this time, The Microsoft fix above should still be installed on all appliances from the local console using the rsaLocalAdmin account. The appliances will then need to be rebooted (from the Web interface to ensure proper service shutdown, not the local console), and the time settings checked upon restart. 

Legacy Article IDa33547