The State Duma of Russia adopted in July a bill to return to winter time, as well as to establish a new system of time zones. As a result, on October 26, 2014, in most regions of Russia, the time will be set back an hour again, and 11 time zones will appear in the country instead of the 9 currently existing, and their borders will change.
Some general information
With the adoption of the Federal Law of the Russian Federation No. No. 248-FZ “On Amendments to the Federal Law “On the Calculation of Time” on the territory of the Russian Federation on October 26, 2014, the clock is changed and the corresponding time zones and time values are established. As a result, most regions of Russia will go back 1 hour, while 3 new time zones will be created and 2 current time zones will be merged into one new one. The configuration of time zones will change - a number of regions will move to neighboring or new zones. The transition to summer and winter time will not be carried out throughout the year.On September 23, 2014, Microsoft released a cumulative update (kb2998527) for Windows operating systems to reflect current changes in timekeeping and made it available for download on the Microsoft Download Center (https://support2.microsoft.com/kb/2998527 /) and Windows Update (https://catalog.update.microsoft.com). This update contains the latest changes adopted in Russia. In addition, a new time zone for the Republic of Belarus will be created in Windows operating systems.
The change in time calculation will take place on October 26, 2014 at 2:00 local time. In this regard, in Windows operating systems, these changes will be displayed at the time of the change in the clock count following 1h:59m:59s.
what will happen on October 26, 2014 at 2:00 local time
Time zones in Russia will change and quite significantly. Picture from Lenta.ruAs a result, the next cheerful life awaits us, viz.
Changes to existing time zones
after you install update KB29985527 on your operating systems, the following will change in the existing time zones registered in the systems| |
|
New display name |
|
Current display name |
| 1 |
Russia Time Zone 1 |
(UTC+02:00) Kaliningrad (RTZ 1) |
Kaliningrad Standard Time |
(UTC+03:00) Kaliningrad, Minsk |
| 2 |
Russia Time Zone 2 |
(UTC+03:00) Moscow, St. Petersburg, Volgograd (RTZ 2) |
Russian Standard Time |
(UTC+04:00) Moscow, St. Petersburg, Volgograd |
| 3 |
Russia Time Zone 4 |
(UTC+05:00) Ekaterinburg (RTZ 4) |
Ekaterinburg Standard Time |
(UTC+06:00) Ekaterinburg |
| 4 |
Russia Time Zone 5 |
(UTC+06:00) Novosibirsk (RTZ 5) |
North Central Asia Standard Time |
(UTC+07:00) Novosibirsk |
| 5 |
Russia Time Zone 6 |
(UTC+07:00) Krasnoyarsk (RTZ 6) |
North Asia Standard Time |
(UTC+08:00) Krasnoyarsk |
| 6 |
Russia Time Zone 7 |
(UTC+08:00) Irkutsk (RTZ 7) |
North Asia East Standard Time |
(UTC+09:00) Irkutsk |
| 7 |
Russia Time Zone 8 |
(UTC+09:00) Yakutsk (RTZ 8) |
Yakutsk Standard Time |
(UTC+10:00) Yakutsk |
On October 26, 2014 at 2:00 am local time, the clocks of user PCs located in these time zones will be automatically adjusted to winter time. But there were exceptions. Exceptions are:
- in the Republic of Udmurtia and the Samara region, you should manually switch to the “Russian Time Zone 3” time zone instead of the automatically set RTZ 2 (Russian Time Zone 2) time zone;
- in the Kemerovo region, you should manually switch to the time zone “Russian Time Zone 6” instead of the automatically set time zone RTZ 5 (Russian Time Zone 5);
- in the Trans-Baikal Territory, you should manually switch to the “Russian Time Zone 7” time zone instead of the automatically set time zone RTZ 8 (Russian Time Zone 8).
New time zones
| |
New time zone name |
New display name |
Current time zone name |
Current display name |
| 1 |
Russia Time Zone 3 |
(UTC+04:00) Izhevsk, Samara (RTZ 3) |
Is absent |
Is absent |
| 2 |
Russia Time Zone 10 |
(UTC+11:00) Chokurdakh (RTZ 10) |
Is absent |
Is absent |
| 3 |
Russia Time Zone 11 |
(UTC+12:00) Anadyr, Petropavlovsk-Kamchatsky (RTZ 11) |
Is absent |
Is absent |
User computers located in these time zones must be manually set to the appropriate time zone. Otherwise, from October 26, 2014, from 2 am local time, the display of time on these computers will be incorrect.
Consolidation of time zones
| |
New time zone name |
New display name |
Current time zone name |
Current display name |
| 1 |
Russia Time Zone 9 |
(UTC+10:00) Vladivostok, Magadan (RTZ 9) |
Vladivostok Standard Time |
(UTC+11:00) Vladivostok |
| Magadan Standard Time |
(UTC+12:00) Magadan |
For computers set to the “Vladivostok Standard Time” time zone, the time zone will change automatically. For computers set to the “Magadan Standard Time” time zone, only the time will be adjusted. Computers in this time zone must be manually switched to the new time zone "Russia Time Zone 9" as the main time zone after October 26, 2014.
Exceptions for computers set to “Magadan Standard Time” are:
- in the Magadan region, you should manually switch to the time zone “Russian Time Zone 8”;
- in the Chukotka Autonomous Okrug (Chukotka) and Kamchatsky Krai (Kamchatka), you must manually switch to the “Russia Time Zone 11” time zone.
Expected Issues
Well, without this:- no official updates will be released for Windows XP to correct the time display (except for the Embedded edition);
- Windows Server 2003 and Windows XP Embedded operating systems will not be automatically reconfigured to new time zones after installing update KB2998527 (even if they are automatically configured for other operating systems);
- Microsoft Outlook email clients up to version 2007 inclusive (versions of Microsoft Outlook 2010 and later do not experience such a problem) after the time change at 2:00 am on October 26, 2014, will incorrectly display calendar tasks created earlier than this date (the time in them will shift one hour back ) scheduled for a date later than 2:00 am on October 26, 2014.
- ADD nasty MC released a crooked patch for Windows XP Embedded and Server 2003. Fixes are expected in December 2014. Or just after October 26, uncheck the box "Automatically switch to daylight saving time and back"
We start updating
Microsoft Windows XP Professional Update
For XP, we have two upgrade options:- turn XP into Embedded;
- make changes to the registry directly.
The transformation begins:
- run the registry editor on the target machine and navigate to the path HKEY_LOCAL_MACHINE\SYSTEM\WPA\;
- select the WPA partition with the right mouse click and select the context menu item Create - Partition;
- create a section named PosReady;
- inside the PosReady section, create a DWORD value named Installed and give it a value of 1.
After installation is complete, you must manually change the time zone. For Moscow time, you will have to change +04:00 Abu Dhabi to +03:00 RTZ 2. Don't forget to check that the box "Automatically switch to daylight saving time and back" is checked. Otherwise, the time translation will be incorrect. Therefore, if your OS is older than 2011 and this box is unchecked, it will not return after installing the fix. Why MS did this I don't understand.
After you install the hotfix from Embedded, you can remove the new values in the WPA registry key. You can remove them before reboot. After the reboot, the OS will not delete them. Unfortunately, I cannot say what this registry branch and / or the installation of a patch for Embedded can also affect.
Making changes to the registry directly
The second option for changing time zones on Windows XP can be directly editing the registry. It is convenient when you have a bunch of XP in, for example, a domain that needs to be updated. Then you create .reg files and distribute them through group policy. To do this, you need to build a reference XP (for example, on a virtual machine), turn it into Embedded using the above method, install the kb2998527 fix, set the correct current time zone and unload two registry branches:
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones - time zone database
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation - current timezone
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones] - removes the time zone database
[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation] - removes the value of the current time zone
As a result, we will have four files for distribution: 1.reg, 2.reg, 3.reg and 4.reg. In this order, they will need to be applied. By the way, in this way we get two bonuses:
- no need to fill your head with the "automatic daylight saving time" checkbox - it will be set automatically
- calendars won't work in Outlook (more on that below)
ADD all parameters from files 1.reg, 2.reg, 3.reg and 4.reg can be placed in one .reg file. So it will be more convenient.
Distribution via GPO
Because in the 2003-XP environment, the established group policy preferences are quite rare, we will make fixes in the registry with a simple script. To do this, let's create a file with the .cmd extension with the following content:
@echo off
IF EXIST c:\windows\ok.file (exit) ELSE (regedit /s \\contoso.internal\SYSVOL\contoso.internal\scripts\1.reg & regedit /s \\contoso.internal\SYSVOL\contoso.internal \scripts\2.reg & regedit /s \\contoso.internal\SYSVOL\contoso.internal\scripts\3.reg & regedit /s \\contoso.internal\SYSVOL\contoso.internal\scripts\4.reg & echo .2>c:\windows\ok.file & tzchange.exe /c “Russian Standard Time”)
The script does the following: check if the ok.file file exists in the Windows folder, and if so, exits. The script has already been run. If the file does not exist, then the values from the .reg files are applied in the specified sequence. Don't forget that the .reg files must be available on a network path. After application, the ok.file file is created in the Windows directory and the current time zone is assigned, because after changing the registry, this will not happen automatically. You can also just reboot the PC instead of the tzchange command (or give the shutdown -r command). As anyone likes.
It remains to make a group policy. We go to the group policy editor. Expand Computer Configuration - Windows Settings - Scripts. In the left part of the policy editing window, double-click the Startup item. In the window for editing the properties of the Startup item, click the Add button and add the .cmd file created earlier to the network path. Click OK twice and close the Group Policy Editor window. Apply the created policy to the organizational unit containing the accounts of the target PCs. After the target PCs restart, the policy will be applied.
Microsoft Windows 2003 Server Update
Update kb2998527 has been released for Microsoft Windows 2003. Therefore, the main problem is to translate the time zone where necessary. It is clear that this can be done manually. As well as deleting registry values and adding the necessary ones (for example, in the same way as for XP). To do this, on a reference machine with the update installed and the correct time zone, unload the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation registry branch and save it under the name 2.reg. Then create a 1.reg file with the following content[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation].
Apply the above method through group policy to Windows 2003 servers in the specified sequence. First file 1, then 2. And then the choice is either the command to change the current time zone or just reboot.
Update tasks in Outlook 2000-2007 calendar
And the last problem in the context of outdated Microsoft systems that I had to face when testing the switch to winter time is that in tasks that were created before the switch to winter time on dates later than October 26, the time “went” an hour ago. In other words, what was scheduled for 9am became scheduled for 8am after installing hotfix kb2998527 on dates later than October 26th. What is wrong. By the way, when testing on XP, where changes to the registry were applied directly (without “turning” the OS into Embedded), the calendars did not “go”. Where the update was put, everything is as it should - they left.Microsoft has a utility for this. There are actually two, one running on the client, the other running directly on the Exchange server. But since what is running on the Exchange server can break it (and MS hints at it) it's safer to run around the machines, if anything, than to conjure over the restoration of the database. Therefore, I will only consider a utility that runs on the client side. Also, I will not consider updating calendars in office mailboxes and public folders. All this is discussed in the MS article (it will be below) and the relation to the essence of this post is somewhat indirect.
Calendars "go" on almost all operating systems after changing the time zone with the version of Outlook from 2000 to 2007. Why practically, because it's worth checking. Maybe you are lucky and the tasks will remain in place. For example, in my experiments, the calendars in Outlook 2007 remained correct in Windows 7. But the official position of the MS is that these versions of Outlook will "go". The versions of Outlook 2010 and 2013 do not require actions. Everything is always fine there.
So, in order to fix the work of "traveled" tasks in calendars, we need to go to the site http://support2.microsoft.com/kb/930879/en and download either the 32-bit or 64-bit version of the Time Zone Data Update Tool package .There are no problems with this. The problem is in mass deployment and in mass execution. Officially, the MC literally says the following “install and run”. Which is not always convenient. Therefore, I faced the task of transferring all this to group policies.
As a result, it turned out that the tool for fixing calendars - OutlookTimeZoneMove.exe - is nothing more than an archive that can be opened with the same WinRAR. Which is what was done. TZMove.msi has been extracted from OutlookTimeZoneMove.exe. Unfortunately, the x64 and x86 versions are named the same, so don't forget to rename TZMove.msi to TZMove_32.msi and TZMove_64.msi, respectively.
After that, these files must be placed on a network share that is accessible to domain users for reading and a group policy must be created for distribution. You will have to create two group policies and configure them to run on the OS with its bit depth (for example, through WMI filters), but these settings are beyond the scope of this article.
After creating a group policy, open it for editing. Expand User Configuration - Software Settings. Click on the item Software installation, select the context menu item New - Package and add the TZMove.msi file to the network path. Press OK. In the right part of the policy editing window, double-click the created package and enter its properties. Go to the Deployment tab and set the distribution type switch to Assignrd and to the switch on the Install this application at logon item. 
Click OK to close the Group Policy Editor window. Apply the created policy to the organizational unit that contains the target user accounts. After the PC restarts and the target user logs in, the Outlook Calendar Adjustment Tool will be deployed to the target PC for the target user.
And we only have to launch this tool, because it is quite difficult to force the user to do it himself. The complexity, at first glance, lies in the fact that the fix tool is installed in three paths to the executable file:
- For 32x OS - “%PROGRAMFILES%\Microsoft Office\Office12\Office Outlook Time Zone Data Update Tool\tzmove.exe”
- For 64x OS - “%PROGRAMFILES(x86)%\Microsoft Office\Office12\Office Outlook Time Zone Data Update Tool\tzmove.exe”
- For Outlook 2010 64x - “%PROGRAMFILES%\Microsoft Office\Office14\Time Zone Data Update Tool for Microsoft Outlook\tzmove.exe”
@echo off
IF EXIST "%userprofile%\ok1.file" (exit) ELSE ("%PROGRAMFILES%\Microsoft Office\Office12\Office Outlook Time Zone Data Update Tool\tzmove.exe" /quiet & “%PROGRAMFILES(x86)%\Microsoft Office\Office12\Office Outlook Time Zone Data Update Tool\tzmove.exe” /quiet & “%PROGRAMFILES%\Microsoft Office\Office14\Time Zone Data Update Tool for Microsoft Outlook\tzmove.exe” /quiet echo. 2>"% userprofile%\ok1.file")
The script will check if there is an ok1.file file in the user's profile folder and if it is, the script exits (it was already running). If the file does not exist, then the script tries to execute in "quiet" mode the tool for adjusting tasks in the user's calendar in all three possible ways. One will work. Not the Jedi way, but quickly implemented. Then it creates ok1.file and exits.
After creating a group policy, open it for editing. Expand User Configuration - Windows Settings - Scripts. In the left part of the policy editing window, double-click on the Logon item. In the window for editing the properties of the Logon item, click the Add button and add the previously created .cmd file to the network path.
Click OK twice and close the Group Policy Editor window. Apply the created policy to the organizational unit that contains the target user accounts.
After the target PC is restarted, the target user's logon PC will silently (require no user interaction) adjust the tasks in the Outlook calendar.
That's all I wanted to tell. I hope this helps those who are facing a similar problem. I will be glad to answer questions and comments.
Bonus for those who read to the end:
if you don't know if the checkbox was checked or unchecked on 2003 and XP OS where the fix will be installed, just delete one registry value by distributing a .reg file with the following content:
“DisableAutoDaylightTimeSet”=-
Tags: Add tags
- This is a near-Earth object with a diameter of about 30 meters. It was discovered on August 29, 2006, when it was at a distance of 4.5 million km. from our planet. Scientists observed the celestial body for 10 days, after which the asteroid ceased to be visible in telescopes.Based on such a short observation period, it is impossible to accurately determine the distance at which the asteroid 2006 QV89 will approach the Earth on 09/09/2019, since the asteroid has not been observed since then (since 2006). Moreover, according to various estimates, the object may approach our planet not at all on the 9th, but on a different date in September 2019.
As for whether 2006 QV89 will hit Earth on September 9, 2019 or not - the chance of a collision is extremely low.
Thus, the Sentry System (developed by the JPL Center for NEO Studies) shows that the probability of a body colliding with the Earth is 1:9100 (those. about one ten thousandth of a percent).
The European Space Agency (ESA) estimates the chance of an asteroid orbit crossing our planet as 1 to 7300 (0,00014 % ). The ESA ranked 2006 QV89 as the 4th celestial body of potential danger to Earth. According to the agency, the exact time of the "flight" of the body on September 9, 2019 is 10:03 Moscow time.
In both Orthodoxy and Catholicism, Easter always falls on a Sunday.
Easter 2020 is preceded by Great Lent, which begins 48 days before the Bright Holiday. And after 50 days celebrate the Trinity.
Popular pre-Christian customs that have survived to this day include dyeing eggs, making Easter cakes and curd cakes.
Easter treats are consecrated in the church on Saturday, on the eve of Easter 2020, or after the service on the very day of the Feast.
To greet each other on Easter should be the words "Christ is Risen", and to answer - "Truly Risen."
For the Russian team, this will be the fourth game in this qualifying tournament. Recall that in the previous three meetings, Russia “at the start” lost to Belgium with a score of 1:3, and then won two dry victories - over Kazakhstan (4:0) and over San Marino (9:0). The last victory was the largest ever for the existence of the Russian national football team.
As for the upcoming meeting, according to the bookmakers, the Russian team is the favorite in it. The Cypriots are objectively weaker than the Russians, and nothing good can be expected from the upcoming match for the islanders. However, we must take into account that the teams have never met before, and therefore we can expect unpleasant surprises.
The Russia-Cyprus meeting will take place on June 11, 2019 In Nizhniy Novgorod at the stadium of the same name built for the 2018 FIFA World Cup. Start of the match - 21:45 Moscow time.
Where and what time do the national teams of Russia and Cyprus play:
* Location of the match - Russia, Nizhny Novgorod.
* Game start time - 21:45 Moscow time.
On the night of October 25-26, 2014, Russia will switch to winter time. Last time.
Clock change in October 2014 will be the last
vid_roll_width="300px" vid_roll_height="150px">On the night of October 25-26, Russia switches to winter time. At 2 a.m. Moscow time from Saturday to Sunday, the clock hands will be moved back one hour in most regions of the country, TASS reports.
The decree on the transition to winter time was signed on July 22 this year by Russian President Vladimir Putin. Since 2011, the country has lived according to the so-called summer time, which intcbatch ahead of astronomical by two hours. Tonight will be the last seasonal switchover: in accordance with the presidential decree, there will be no more transitions from summer to winter time and vice versa in the country.
After the translation of the hour hands, Moscow time will differ from Coordinated Universal Time (UTC) not by +4, but by +3 hours.
Daylight savings time 2014: where will it take place
In connection with the transition to winter time in Russia, the number of time zones will change. Now there will be 11 instead of 9.
Residents of five regions will not change their clocks: in the Samara and Kemerovo regions, Udmurtia, Kamchatka and Chukotka, the time will remain the same. In time, the Kemerovo region will join its neighbors: the Krasnoyarsk Territory, Khakassia and Tyva, the difference with Moscow will not be 3 hours, as Kemerovo residents are used to, but 4.
But the population of the Trans-Baikal Territory and the Magadan Region needs to move the arrows back 2 hours.
The new subjects of the Russian Federation - the Republic of Crimea and Sevastopol - will live according to Moscow time.
The 2014 clock change was rated positively by the Ministry of Health and football fans
The Ministry of Health of Russia positively assessed the translation of the hands an hour ago. This process should be taken for granted, Alexander Chuchalin, the ministry's chief physician, told Interfax.
According to the expert, proper rest and good sleep will help Russian citizens to survive the transition to winter time without any problems.
With a two-three-hour difference in summer time, doctors even diagnosed a new disease - "desynchronosis", a mismatch of biorhythms. The risk group includes people who, on duty, have to get up early. Having stepped over from "eternal summer" to "eternal winter", the whole big country will begin to wake up at dawn.
Will football fans also benefit from approaching Grivinch? now the Champions League matches will be broadcast earlier, which means that hundreds of thousands of fans will finally get enough sleep.
Recall that the transition to winter and summer time was canceled in the summer of 2011 at the initiative of President Dmitry Medvedev. Then this measure was supported by 73 percent of Russians. Now in Russia there is a constant summer time, ahead of astronomical time by two hours, but the opinion of citizens has changed - at the end of 2013, only 32 percent of Russians supported the abolition of the switchover.
October 26, 2014 at 2 o'clock in the morning it is necessary to turn the clock hands 1 hour back. That is, the transfer of clocks to winter time in 2014 will occur on the last Sunday of October.
At this moment, according to the previously adopted Federal Law of the Russian Federation of July 21, 2014 N 248-FZ, “Moscow time” will be established, which will correspond to UTC (SU) +3 hours. Until October 26, 2014, Moscow time corresponds to UTC (SU) + 4 hours.
According to the law, there will be 11 time zones on the territory of the Russian Federation, the boundaries of which will be formed taking into account the boundaries of the subjects of the federation. After October 26, 2014, there will be no more daylight saving time switches.
Why you need to switch to winter time
The official and most common explanation for the need to switch switches is as follows: "Switching the switches allows you to reduce energy loads and improve the environmental situation, ensures the stable operation of the country's unified energy system, the consistency of transport flows and communications, and the organization of television and radio broadcasting."
The average person usually wakes up around 7 am and goes to bed at 11 pm local time. If you completely abandon the transfer to winter and summer time, but for half a year it will get up much later than dawn. Moving the clock forward in the spring and back in the fall makes you get up during daylight hours and spend less electricity on lighting.
During the periods of transition to winter time and back, scientists even revealed a new disease, which they called desynchronosis (disturbance of normal life), provoking depression, hypertensive crises, and heart attacks.
According to some researchers, saving energy hardly justifies the deterioration in well-being, performance and health - categories that can also be represented by economic calculations.
The change of clocks in autumn to winter time, and in spring to summer time, exists in more than 100 countries of the world. In astrology, when calculating horoscopes, it is necessary to take into account the date of adoption of standard time in a particular region of the planet, be aware of changes in the boundaries of time zones that occur periodically, and also take into account the transition to winter time and vice versa.
However, problems after the transition to winter time occur not only among astrologers, but also among most people. Children, the elderly and sick people feel a particular inconvenience when translating the arrows. It can take a month or more for some people to get used to it. How can we help our body cope with this stress and re-adjust the internal biological clock?
The main signs of a malfunction of our biological clock are reduced performance, fatigue, irritability and depressed mood. In order to set yourself up for positive and reduce body stress to a minimum, you need to listen to calm melodic music in the first week after the transition to winter time, walk in the fresh air, enjoy the beauty and colors of autumn. The support of your loved ones and loved ones is very important.
Astrology in the period of adaptation to the new time advises to do without annoying red tones in clothes and accessories, silver-blue and bluish-green shades, complemented by translucent scarves and knitted lace shawls, mother-of-pearl jewelry or pearl beads, will be much more appropriate. Blue denim pants and jackets are perfect for this occasion.
True, the main question still remains: is it permissible for a person to play with time? The big question is whether we have the right to transfer to the day what belongs to the night, and vice versa? After all, as the wise men of antiquity stated, after a while God manifests in our lives.
When God wants to give people additional time at their prayers, He Himself stops the luminaries in their movement across the firmament and extends the day for several hours: “... the sun stood in the sky and did not rush to the west for almost a whole day,” says one of the books. bible
The State Duma of Russia adopted in July a bill to return to winter time, as well as to establish a new system of time zones. As a result, on October 26, 2014, in most regions of Russia, the time will be set back an hour again, and 11 time zones will appear in the country instead of the 9 currently existing, and their borders will change.
Some general information
With the adoption of the Federal Law of the Russian Federation No. No. 248-FZ “On Amendments to the Federal Law “On the Calculation of Time” on the territory of the Russian Federation on October 26, 2014, the clock is changed and the corresponding time zones and time values are established. As a result, most regions of Russia will go back 1 hour, while 3 new time zones will be created and 2 current time zones will be merged into one new one. The configuration of time zones will change - a number of regions will move to neighboring or new zones. The transition to summer and winter time will not be carried out throughout the year.On September 23, 2014, Microsoft released a cumulative update (kb2998527) for Windows operating systems to reflect current changes in timekeeping and made it available for download on the Microsoft Download Center (https://support2.microsoft.com/kb/2998527 /) and Windows Update (https://catalog.update.microsoft.com). This update contains the latest changes adopted in Russia. In addition, a new time zone for the Republic of Belarus will be created in Windows operating systems.
The change in time calculation will take place on October 26, 2014 at 2:00 local time. In this regard, in Windows operating systems, these changes will be displayed at the time of the change in the clock count following 1h:59m:59s.
what will happen on October 26, 2014 at 2:00 local time
Time zones in Russia will change and quite significantly. Picture from Lenta.ruAs a result, the next cheerful life awaits us, viz.
Changes to existing time zones
after you install update KB29985527 on your operating systems, the following will change in the existing time zones registered in the systems| |
|
New display name |
|
Current display name |
| 1 |
Russia Time Zone 1 |
(UTC+02:00) Kaliningrad (RTZ 1) |
Kaliningrad Standard Time |
(UTC+03:00) Kaliningrad, Minsk |
| 2 |
Russia Time Zone 2 |
(UTC+03:00) Moscow, St. Petersburg, Volgograd (RTZ 2) |
Russian Standard Time |
(UTC+04:00) Moscow, St. Petersburg, Volgograd |
| 3 |
Russia Time Zone 4 |
(UTC+05:00) Ekaterinburg (RTZ 4) |
Ekaterinburg Standard Time |
(UTC+06:00) Ekaterinburg |
| 4 |
Russia Time Zone 5 |
(UTC+06:00) Novosibirsk (RTZ 5) |
North Central Asia Standard Time |
(UTC+07:00) Novosibirsk |
| 5 |
Russia Time Zone 6 |
(UTC+07:00) Krasnoyarsk (RTZ 6) |
North Asia Standard Time |
(UTC+08:00) Krasnoyarsk |
| 6 |
Russia Time Zone 7 |
(UTC+08:00) Irkutsk (RTZ 7) |
North Asia East Standard Time |
(UTC+09:00) Irkutsk |
| 7 |
Russia Time Zone 8 |
(UTC+09:00) Yakutsk (RTZ 8) |
Yakutsk Standard Time |
(UTC+10:00) Yakutsk |
On October 26, 2014 at 2:00 am local time, the clocks of user PCs located in these time zones will be automatically adjusted to winter time. But there were exceptions. Exceptions are:
- in the Republic of Udmurtia and the Samara region, you should manually switch to the “Russian Time Zone 3” time zone instead of the automatically set RTZ 2 (Russian Time Zone 2) time zone;
- in the Kemerovo region, you should manually switch to the time zone “Russian Time Zone 6” instead of the automatically set time zone RTZ 5 (Russian Time Zone 5);
- in the Trans-Baikal Territory, you should manually switch to the “Russian Time Zone 7” time zone instead of the automatically set time zone RTZ 8 (Russian Time Zone 8).
New time zones
| |
New time zone name |
New display name |
Current time zone name |
Current display name |
| 1 |
Russia Time Zone 3 |
(UTC+04:00) Izhevsk, Samara (RTZ 3) |
Is absent |
Is absent |
| 2 |
Russia Time Zone 10 |
(UTC+11:00) Chokurdakh (RTZ 10) |
Is absent |
Is absent |
| 3 |
Russia Time Zone 11 |
(UTC+12:00) Anadyr, Petropavlovsk-Kamchatsky (RTZ 11) |
Is absent |
Is absent |
User computers located in these time zones must be manually set to the appropriate time zone. Otherwise, from October 26, 2014, from 2 am local time, the display of time on these computers will be incorrect.
Consolidation of time zones
| |
New time zone name |
New display name |
Current time zone name |
Current display name |
| 1 |
Russia Time Zone 9 |
(UTC+10:00) Vladivostok, Magadan (RTZ 9) |
Vladivostok Standard Time |
(UTC+11:00) Vladivostok |
| Magadan Standard Time |
(UTC+12:00) Magadan |
For computers set to the “Vladivostok Standard Time” time zone, the time zone will change automatically. For computers set to the “Magadan Standard Time” time zone, only the time will be adjusted. Computers in this time zone must be manually switched to the new time zone "Russia Time Zone 9" as the main time zone after October 26, 2014.
Exceptions for computers set to “Magadan Standard Time” are:
- in the Magadan region, you should manually switch to the time zone “Russian Time Zone 8”;
- in the Chukotka Autonomous Okrug (Chukotka) and Kamchatsky Krai (Kamchatka), you must manually switch to the “Russia Time Zone 11” time zone.
Expected Issues
Well, without this:- no official updates will be released for Windows XP to correct the time display (except for the Embedded edition);
- Windows Server 2003 and Windows XP Embedded operating systems will not be automatically reconfigured to new time zones after installing update KB2998527 (even if they are automatically configured for other operating systems);
- Microsoft Outlook email clients up to version 2007 inclusive (versions of Microsoft Outlook 2010 and later do not experience such a problem) after the time change at 2:00 am on October 26, 2014, will incorrectly display calendar tasks created earlier than this date (the time in them will shift one hour back ) scheduled for a date later than 2:00 am on October 26, 2014.
- ADD nasty MC released a crooked patch for Windows XP Embedded and Server 2003. Fixes are expected in December 2014. Or just after October 26, uncheck the box "Automatically switch to daylight saving time and back"
We start updating
Microsoft Windows XP Professional Update
For XP, we have two upgrade options:- turn XP into Embedded;
- make changes to the registry directly.
The transformation begins:
- run the registry editor on the target machine and navigate to the path HKEY_LOCAL_MACHINE\SYSTEM\WPA\;
- select the WPA partition with the right mouse click and select the context menu item Create - Partition;
- create a section named PosReady;
- inside the PosReady section, create a DWORD value named Installed and give it a value of 1.
After installation is complete, you must manually change the time zone. For Moscow time, you will have to change +04:00 Abu Dhabi to +03:00 RTZ 2. Don't forget to check that the box "Automatically switch to daylight saving time and back" is checked. Otherwise, the time translation will be incorrect. Therefore, if your OS is older than 2011 and this box is unchecked, it will not return after installing the fix. Why MS did this I don't understand.
After you install the hotfix from Embedded, you can remove the new values in the WPA registry key. You can remove them before reboot. After the reboot, the OS will not delete them. Unfortunately, I cannot say what this registry branch and / or the installation of a patch for Embedded can also affect.
Making changes to the registry directly
The second option for changing time zones on Windows XP can be directly editing the registry. It is convenient when you have a bunch of XP in, for example, a domain that needs to be updated. Then you create .reg files and distribute them through group policy. To do this, you need to build a reference XP (for example, on a virtual machine), turn it into Embedded using the above method, install the kb2998527 fix, set the correct current time zone and unload two registry branches:
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones - time zone database
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation - current timezone
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones] - removes the time zone database
[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation] - removes the value of the current time zone
As a result, we will have four files for distribution: 1.reg, 2.reg, 3.reg and 4.reg. In this order, they will need to be applied. By the way, in this way we get two bonuses:
- no need to fill your head with the "automatic daylight saving time" checkbox - it will be set automatically
- calendars won't work in Outlook (more on that below)
ADD all parameters from files 1.reg, 2.reg, 3.reg and 4.reg can be placed in one .reg file. So it will be more convenient.
Distribution via GPO
Because in the 2003-XP environment, the established group policy preferences are quite rare, we will make fixes in the registry with a simple script. To do this, let's create a file with the .cmd extension with the following content:
@echo off
IF EXIST c:\windows\ok.file (exit) ELSE (regedit /s \\contoso.internal\SYSVOL\contoso.internal\scripts\1.reg & regedit /s \\contoso.internal\SYSVOL\contoso.internal \scripts\2.reg & regedit /s \\contoso.internal\SYSVOL\contoso.internal\scripts\3.reg & regedit /s \\contoso.internal\SYSVOL\contoso.internal\scripts\4.reg & echo .2>c:\windows\ok.file & tzchange.exe /c “Russian Standard Time”)
The script does the following: check if the ok.file file exists in the Windows folder, and if so, exits. The script has already been run. If the file does not exist, then the values from the .reg files are applied in the specified sequence. Don't forget that the .reg files must be available on a network path. After application, the ok.file file is created in the Windows directory and the current time zone is assigned, because after changing the registry, this will not happen automatically. You can also just reboot the PC instead of the tzchange command (or give the shutdown -r command). As anyone likes.
It remains to make a group policy. We go to the group policy editor. Expand Computer Configuration - Windows Settings - Scripts. In the left part of the policy editing window, double-click the Startup item. In the window for editing the properties of the Startup item, click the Add button and add the .cmd file created earlier to the network path. Click OK twice and close the Group Policy Editor window. Apply the created policy to the organizational unit containing the accounts of the target PCs. After the target PCs restart, the policy will be applied.
Microsoft Windows 2003 Server Update
Update kb2998527 has been released for Microsoft Windows 2003. Therefore, the main problem is to translate the time zone where necessary. It is clear that this can be done manually. As well as deleting registry values and adding the necessary ones (for example, in the same way as for XP). To do this, on a reference machine with the update installed and the correct time zone, unload the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation registry branch and save it under the name 2.reg. Then create a 1.reg file with the following content[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation].
Apply the above method through group policy to Windows 2003 servers in the specified sequence. First file 1, then 2. And then the choice is either the command to change the current time zone or just reboot.
Update tasks in Outlook 2000-2007 calendar
And the last problem in the context of outdated Microsoft systems that I had to face when testing the switch to winter time is that in tasks that were created before the switch to winter time on dates later than October 26, the time “went” an hour ago. In other words, what was scheduled for 9am became scheduled for 8am after installing hotfix kb2998527 on dates later than October 26th. What is wrong. By the way, when testing on XP, where changes to the registry were applied directly (without “turning” the OS into Embedded), the calendars did not “go”. Where the update was put, everything is as it should - they left.Microsoft has a utility for this. There are actually two, one running on the client, the other running directly on the Exchange server. But since what is running on the Exchange server can break it (and MS hints at it) it's safer to run around the machines, if anything, than to conjure over the restoration of the database. Therefore, I will only consider a utility that runs on the client side. Also, I will not consider updating calendars in office mailboxes and public folders. All this is discussed in the MS article (it will be below) and the relation to the essence of this post is somewhat indirect.
Calendars "go" on almost all operating systems after changing the time zone with the version of Outlook from 2000 to 2007. Why practically, because it's worth checking. Maybe you are lucky and the tasks will remain in place. For example, in my experiments, the calendars in Outlook 2007 remained correct in Windows 7. But the official position of the MS is that these versions of Outlook will "go". The versions of Outlook 2010 and 2013 do not require actions. Everything is always fine there.
So, in order to fix the work of "traveled" tasks in calendars, we need to go to the site http://support2.microsoft.com/kb/930879/en and download either the 32-bit or 64-bit version of the Time Zone Data Update Tool package .There are no problems with this. The problem is in mass deployment and in mass execution. Officially, the MC literally says the following “install and run”. Which is not always convenient. Therefore, I faced the task of transferring all this to group policies.
As a result, it turned out that the tool for fixing calendars - OutlookTimeZoneMove.exe - is nothing more than an archive that can be opened with the same WinRAR. Which is what was done. TZMove.msi has been extracted from OutlookTimeZoneMove.exe. Unfortunately, the x64 and x86 versions are named the same, so don't forget to rename TZMove.msi to TZMove_32.msi and TZMove_64.msi, respectively.
After that, these files must be placed on a network share that is accessible to domain users for reading and a group policy must be created for distribution. You will have to create two group policies and configure them to run on the OS with its bit depth (for example, through WMI filters), but these settings are beyond the scope of this article.
After creating a group policy, open it for editing. Expand User Configuration - Software Settings. Click on the item Software installation, select the context menu item New - Package and add the TZMove.msi file to the network path. Press OK. In the right part of the policy editing window, double-click the created package and enter its properties. Go to the Deployment tab and set the distribution type switch to Assignrd and to the switch on the Install this application at logon item.
Click OK to close the Group Policy Editor window. Apply the created policy to the organizational unit that contains the target user accounts. After the PC restarts and the target user logs in, the Outlook Calendar Adjustment Tool will be deployed to the target PC for the target user.
And we only have to launch this tool, because it is quite difficult to force the user to do it himself. The complexity, at first glance, lies in the fact that the fix tool is installed in three paths to the executable file:
- For 32x OS - “%PROGRAMFILES%\Microsoft Office\Office12\Office Outlook Time Zone Data Update Tool\tzmove.exe”
- For 64x OS - “%PROGRAMFILES(x86)%\Microsoft Office\Office12\Office Outlook Time Zone Data Update Tool\tzmove.exe”
- For Outlook 2010 64x - “%PROGRAMFILES%\Microsoft Office\Office14\Time Zone Data Update Tool for Microsoft Outlook\tzmove.exe”
@echo off
IF EXIST "%userprofile%\ok1.file" (exit) ELSE ("%PROGRAMFILES%\Microsoft Office\Office12\Office Outlook Time Zone Data Update Tool\tzmove.exe" /quiet & “%PROGRAMFILES(x86)%\Microsoft Office\Office12\Office Outlook Time Zone Data Update Tool\tzmove.exe” /quiet & “%PROGRAMFILES%\Microsoft Office\Office14\Time Zone Data Update Tool for Microsoft Outlook\tzmove.exe” /quiet echo. 2>"% userprofile%\ok1.file")
The script will check if there is an ok1.file file in the user's profile folder and if it is, the script exits (it was already running). If the file does not exist, then the script tries to execute in "quiet" mode the tool for adjusting tasks in the user's calendar in all three possible ways. One will work. Not the Jedi way, but quickly implemented. Then it creates ok1.file and exits.
After creating a group policy, open it for editing. Expand User Configuration - Windows Settings - Scripts. In the left part of the policy editing window, double-click on the Logon item. In the window for editing the properties of the Logon item, click the Add button and add the previously created .cmd file to the network path.
Click OK twice and close the Group Policy Editor window. Apply the created policy to the organizational unit that contains the target user accounts.
After the target PC is restarted, the target user's logon PC will silently (require no user interaction) adjust the tasks in the Outlook calendar.
That's all I wanted to tell. I hope this helps those who are facing a similar problem. I will be glad to answer questions and comments.
Bonus for those who read to the end:
if you don't know if the checkbox was checked or unchecked on 2003 and XP OS where the fix will be installed, just delete one registry value by distributing a .reg file with the following content:
“DisableAutoDaylightTimeSet”=-
