Beginning in 2007, most of the United States begins Daylight Saving Time at 2:00 a.m. on the second Sunday in March and reverts to standard time on the first Sunday in November. This is a change from previous years, and systems that were set to “automatically adjust” for Daylight Saving Time must be updated in order to accommodate this change that was passed into law in the United States.
As a Scala partner, you should be aware that DST starts on March 11, 2007 this year instead of April 1, and ends on November 4, 2007 instead of October 28. The best way to handle this change is to use Windows Update on all of your systems, or manually install Microsoft’s DST hotfix per the procedures below.
If it is not possible to update your network by March 11, 2007, any scripts that use “!time” to show the time of day on screen or any schedules that rely on the PC’s real-time clock, will be one hour behind between March 11 and April 1.
The following Microsoft Knowledge Base articles cover this topic: http://support.microsoft.com/kb/928388
To obtain the 2007 time zone update for Microsoft Windows operating systems go to: http://support.microsoft.com/kb/914387
How to configure daylight saving time for the United States in 2007 see the following article: http://support.microsoft.com/kb/931836/. February 2007 cumulative time zone update for Microsoft Windows operating systems.
Updating Scala 5 Designer, Content Manager, InfoChannel 3 Designer, and Network Manager using Windows XP
First ‘Download the Update for Windows XP package now’ from http://support.microsoft.com/kb/931836/. This will be the DST fix file called WindowsXP-KB931836-x86-ENU.exe. Execute the fix file. Once completed the system will automatically reboot.
Updating Scala 5 Designer, Content Manager, InfoChannel 3 Designer, and Network Manager using Windows Server 2003
First ‘Download the Update for Windows Server 2003 package now’ from http://support.microsoft.com/kb/931836/. This will be the DST fix file called WindowsServer2003-KB931836-x86-ENU.exe. Execute the fix file. Once completed the system will automatically reboot.
Updating remote Infochannel 5 Players using Windows XP:
The DST fix can be pushed to InfoChannel 5 Players by sending a 3-task maintenance job from Content Manager 5.
First ‘Download the Update for Windows XP package now’ from http://support.microsoft.com/kb/931836/. This will be the DST fix file called WindowsXP-KB931836-x86-ENU.exe.
In Content Manager 5 go to the Network tab, and select Maintenance Jobs. Click on Upload Files to load the fix file WindowsXP-KB931836-x86-ENU.exe. Click on ‘New’ and give the Job a name. Click on Next. Add the following 3 maintenance tasks:
1. Task command: Install File, select the filename ‘WindowsXP-KB931836-x86-ENU.exe’ on the right, Install Path: C:. ADD task.
2. Task command: Run Command, Command Path: C:WindowsXP-KB931836-x86-ENU.exe /quiet /norstart, select Wait for completion:, Seconds to Wait:30, ADD task.
3. Task command: Reboot. ADD task.
Select your players and schedule. Generate the plan.
NOTE: If installing to an EQUUS image the above paths should be F: rather than C:.
Updating remote Infochannel 3 Players using Windows XP:
The DST fix can be pushed to InfoChannel 3 Players by sending a 3-task maintenance job form Network Manager 3.
First ‘Download the Update for Windows XP package now’ from http://support.microsoft.com/kb/931836/ to your Network Manager server. This will be the DST fix file called WindowsXP-KB931836-x86-ENU.exe.
Move the fix file WindowsXP-KB931836-x86-ENU.exe to your Publish Location. Create a New Job selecting the following 3 maintenance tasks:
1. Command: Install File, select your Publish Location, filename ‘WindowsXP-KB931836-x86-ENU.exe’, Full Path to Destination: C:. ADD task.
2. Command: Run Command, Command Line: C:WindowsXP-KB931836-x86-ENU.exe /quiet /norestart. ADD task.
3. Command: Reboot. ADD task.
Select your players and schedule. Run the job.
NOTE: If installing to an EQUUS image the above paths should be F: rather than C:.
Updating NEC/Panasonic Bluefire VC200 & V250 XPE Players:
The appropriate registry key script file needs to be created as per the above Microsoft article # 914387. You can select updates to your time zone only if you wish. Save the file as Tzupdate.reg in NotePad to your Publish Location.
Create a New Job selecting the following 6 maintenance tasks:
1. Command: Run Command, Command Line: EWFMGR C: -commitanddisable, ADD task.
2. Command: Reboot. ADD task.
3. Command: Install File, select your Publish Location, filename TZupdate.reg, Full Path to Destination: E:. ADD task.
4. Command: Run Command, Command Line: REGEDT /S E:Tzupdate.reg. ADD task.
5. Command: Run Command, Command Line: EWFMGR C: -enable, ADD task.
6. Command: Reboot. ADD task.
Select your players and schedule. Run the job.
Updating NEC /Panasonic Bluefire VC300 and VC400 XPE Players:
The DST fix can be pushed to Scala 5 Players by sending two separate maintenances job from Content Manager 5.
First ‘Download the Update for Windows XP package now’ from http://support.microsoft.com/kb/931836/ to your Content Manager Server. This will be the DST fix file called WindowsXP-KB931836-x86-ENU.exe.
In Content Manager 5 go to the Network tab, and select Maintenance Jobs. Click on Upload Files to load the fix file WindowsXP-KB931836-x86-ENU.exe. Click on ‘New’ and give the Job a name. Click on Next. Add the following maintenance tasks:
1. Task command: Run Command, Command Line: EWFMGR C: -commitanddisable, ADD task.
2. Task command: Reboot. ADD task.
Select your players and schedule. Generate the plan.
Create a second Maintenance Job with following tasks:
1. Task command: Install File, select the filename ‘WindowsXP-KB931836-x86-ENU.exe’ on the right, Install Path: F:. ADD task.
2. Task command: Run Command, Command Path: F:WindowsXP-KB931836-x86-ENU.exe /quiet /norestart, select Wait for completion:, Seconds to Wait:30, ADD task.
3. Task command: Run Command, Command Line: EWFMGR C: -enable, ADD task.
4. Task command: Reboot. ADD task.
Select your players and schedule. Generate the plan.
Updating Infochannel 3 & 5 Players using Windows 2000-based Players:
The appropriate registry key script file needs to be created as per the above Microsoft article # 914387. The registry file then needs to be sent to the Player machines via a NM3 ‘Send File’ Job. The registry file can be loaded via the command ‘REGEDT /S regfilename’. The Players must then be rebooted. You can follow the task structure found in the above section for Bluefire VC200 & VC2500 XPE players without using the EWF commands.