Cancel DST for Exchange Servers
So, we will talk about the cancellation of DST for mail users located on the Exchange servers, namely, the processing of calendars to save the correct time of meetings and events. Yes, October 30 is already soon, and it may seem that it is too late to publish a similar topic, but, first, some of the administrators of mail systems might not have thought about the need for such actions before and they still have time to fix it. secondly, this is not the last abolition of DST in our world, and Russian-speaking people are everywhere, and thirdly, until yesterday evening, I did not have, unfortunately, all the necessary information to describe this process. (Of course, users can remake appointments and events manually, but automated it is always better, faster and more accurate, isn’t it?)
I do not have resource pb, so I omit the description of the process of their processing. The original video of the Exchange team, including on. and this issue can be viewed here .
I have not tested the applicability of this manual for Exchange 2007, only for Exchange 2003, but judging by the original Microsoft articles, there are no differences in the procedure. Despite the fact that on the page of the Help and Support Center for the transition to summer and winter time, there is a promise to release a special update for the Exchange servers, it is still not there, and Microsoft support doubts that it will be released before October 30.
')
I assume that the latest available service packs are installed on your Exchange servers.
1. Update Outlook calendars (only needed if you have users who deliver mail to .pst files):
1.1. Update all client computers by updating Windows time zones.
1.2. Install on all client computers with Outlook the appropriate version of the “Update Time Zone Data Tools” for Microsoft Outlook
1.3. Configure the automatic launch of “Tools ...” when a user logs on to Windows with, for example, the “/ quiet” command line parameter (I recommend that you check for the presence of an installed Windows update before installing / running the server). This will update the calendar at the default mail delivery location, which can be located either in the locally located PST file or in the Exchange database. It's okay when the server calendar is updated again with the Exchange Calendar Update Tool; each calendar item will be updated only once. Multiple launch of "Tools ..." also does not produce any destructive actions.
1.4 “The Time Zone Data Update Tool”, when processing an event, will automatically send all its participants notifications about time changes. Instruct users to accept these changes.
2. Preparation for updating server calendars:
2.1. Please note that despite the fact that the main article devoted to the problem of updating meetings and events in the calendars of Exchange users states that on the Exchange servers, before updating the server calendars, you need to install a time zone update for Windows, the Russian Premier support does not recommend doing so . Instead, they offer to install the OS update on the Exchange servers at the very end. The choice is yours. If you have a contract for Prime support, I recommend not to read it, but to contact them.
2.2. Prepare a custom user to update calendars located on the Exchange server:
2.2.1. Create a user in your AD domain (EXAMPLE \ DSTUpdate).
2.2.2. Create a user mailbox on one of the Exchange-servers.
2.2.3. Give him Exchange View Only Administrator rights for the entire Exchange organization.
2.3. Prepare your computer to run the Exchange Calendar Update Tool (DSTPC).
2.3.1. The computer must be installed:
2.3.1.1. Any of OS: Windows Server 2003, Windows XP, Windows Vista
2.3.1.2. Microsoft Office Outlook 2003 Service Pack 2 or Microsoft Office Outlook 2007 (Better, of course, 2007 SP2)
2.3.1.3. "Time Zone Data Update Tool" for Microsoft Outlook
2.3.1.4. Microsoft .NET Framework version 2.0
2.3.2. No Exchange management tools, such as the Exchange System Manager Console, etc. should be installed on the computer.
2.3.3. You can not prepare such a computer yourself, but use a pre-configured virtual machine . Of course, it will need to be included in your AD domain.
2.3.4. Add the user DSTUpdate to the local administrators group of this computer.
2.3.5. Install the Exchange Calendar Update Configuration Tool on this computer.
2.3.6. Login to DSTPC as DSTUpdate and:
2.3.6.1. Set the value of the HKEY_CURRENT_USER \ Software \ Microsoft \ Exchange \ client \ options \ PickLogonProfile (REG_SZ) parameter to "0".
2.3.6.2. Locate and rename the% USERPROFILE% \ Local Settings \ Application Data \ Microsoft \ Outlook \ extend.dat file as you please.
3. Unloading time zones from user accounts:
3.1. Log on to the DSTPC computer with the user DSTUpdate and run the Exchange Calendar Update Configuration Tool
3.2. Logging level leave Default. If you see errors in the log, switch to Verbose to figure it out, but just like that - no need to trash the output.
3.3. On the Time Zone Extraction page, select the desired servers. If you have a lot of servers, it may take several hours to go through everything.
3.4. After clicking Next, the Exchange Calendar Update Configuration Tool will try to unload users' time zones from the Exchange servers to the file output.txt, which, by the way, is RECORDED each time the application is launched and an attempt is made to upload data.
3.5. If the user, on whose behalf the application is running, does not have access to some pb, you will see the following entry in TimeZoneExtraction.log: [10/20/2011 10:26:02] [552]: HrProcessMailboxTable: Unable log grow user mailbox: Error 0x8004011D.). To solve this problem, use p.4, then unload time zones again.
3.6. Close the application and go to step 5.
4. Providing access to the user boxes for the DSTUpdate user:
4.1. On the computer with the Exchange management tools installed under the account belonging to the Domain Admins group and having Exchange Full Administrator rights to the Exchange organization, run the cscript script GrantMailboxPermission.vbs -Add EXAMPLE \ DSTUpdate ChangeRights.txt
4.1.1. The script is taken from the same article 941018, in the section REFERENCES.
4.1.2. The script takes the LegacyExchangeDN list from the ChangeRights.txt file and provides the EXAMPLE \ DSTUpdate user with Full Mailbox Access and Send As permissions for each mailbox specified in it.
4.1.3. The ChangeRights.txt file must be specially prepared (Microsoft Office Excel can help you):
4.1.3.1. As a blank, TimeZoneExtraction.log is taken. It should be edited so that the resulting file contains lines containing only the LegacyExchangeDN (/ O = EXAMPLE / OU = FIRST ADMINISTRATIVE GROUP / CN = RECIPIENTS / CN = IVANOV.II) without a point at the end, one per line. Empty lines, lines with any other content should not be. That is, you need to cut everything in front of LegacyExchangeDN (starting with “/”) and a period at the end.
4.1.3.2. All service mailboxes of the following type should be removed from the file:
/ O = EXAMPLE / OU = FIRST ADMINISTRATIVE GROUP / CN = CONFIGURATION / CN = CONNECTIONS / CN = SMTP (EXCHANGESERVER) / CN = {11111111-1111-1111-1111-11111111111111}
/ O = EXAMPLE / OU = FIRST ADMINISTRATIVE GROUP / CN = RECIPIENTS / CN = SYSTEMMAILBOX? 11111111-1111-1111-1111-11111111111111?
/ O = EXAMPLE / OU = FIRST ADMINISTRATIVE GROUP / CN = CONFIGURATION / CN = SERVERS / CN = EXCHANGESERVER / CN = MICROSOFT SYSTEM ATTENDANT
4.2. The output of the script is a set consisting of points and exclamation marks. An exclamation mark means an error, a period - everything is OK.
4.2.1. Errors are written to the GrantMailboxPermission.err file.
4.2.2. View error
ADMINISTRATIVE GROUP / CN = RECIPIENTS / CN = IVANOV.II in DC = example, DC = com.
LDAP path from / O = EXAMPLE / OU = FIRST ADMINISTRATIVE GROUP / CN = RECIPIENTS / CN = IVANOV.II
means that the user account in AD is not associated with the mailbox. If everything is correct, and the user really should not be assigned to the box, feel free to ignore these errors.
4.3. You can run the script an unlimited number of times.
4.4. Permission results are recorded in the GrantMailboxPermission.log file. Take care of it - for it then it will be necessary to cancel the granted permissions in Section 6.
5. Processing server calendars:
5.1. It is performed using the same Exchange Calendar Update Configuration Tool. Processing is performed on the output.txt, obtained in paragraph 3.
5.1.1. If item 3 has already been fully implemented:
5.1.1.1. On the mail server selection page, click the Skip button.
5.1.1.2. On the next screen, indicate the prepared output.txt
5.2. The output.txt should be properly prepared (an advanced text editor can help you):
5.2.1. All utility pb should be removed from the file.
5.2.2. On each line with the pb, the time zone must be indicated corresponding to the region:
/ O = EXAMPLE / OU = FIRST ADMINISTRATIVE GROUP / cn = Configuration / cn = Servers / cn = EXCHANGESERVER / O = EXAMPLE / OU = FIRST ADMINISTRATIVE GROUP / CN = RECIPIENTS / CN = IVANOV.II Russian Standard Time
5.2.2.1. If the time zone is not specified, you must specify it manually. If the time zone is incorrect, exclude such users from automated processing.
5.2.2.2. The names of the time zones correspond to the names of the sections of the registry section HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion \ Time Zones \
5.3. Further carry out all actions being guided by the simple master.
5.4. If you have a lot of client computers and not all of them have Windows update installed, you will have to update the calendars in the server pb several times, because non-upgraded users, meanwhile, could create meetings and events.
6. Cleaning after update.
6.1. Run the GrantMailboxPermission.vbs script with the "-remove" parameter. Using the data from the GrantMailboxPermission.log file, the script will remove the permissions granted to the DSTUpdate user on the mailbox of users.
6.2. Cancel the Exchange View Only Administrator permission for the user DSTUpdate.
6.3. Remove the user DSTUpdate from the group of local administrators of the DSTPC computer and from AD.
6.4. If necessary, remove the DSTPC computer from AD and uninstall the OS on it.
7. What you need to update manually:
7.1 The calendars in the public folders of Outlook, although they are located on the server, are not updated as part of the above actions. You must update them manually using the Time Zone Data Update Tool for Microsoft Outlook.
7.2 Calendars in PST files that are not the default mail delivery location will also have to be updated manually. You can instruct technical support or the users themselves how to use the “Time Zone Data Update Tool”.
7.3 Server calendars of users with the wrong time zones. With the help of the same "Tools ..."
I do not have resource pb, so I omit the description of the process of their processing. The original video of the Exchange team, including on. and this issue can be viewed here .
I have not tested the applicability of this manual for Exchange 2007, only for Exchange 2003, but judging by the original Microsoft articles, there are no differences in the procedure. Despite the fact that on the page of the Help and Support Center for the transition to summer and winter time, there is a promise to release a special update for the Exchange servers, it is still not there, and Microsoft support doubts that it will be released before October 30.
')
I assume that the latest available service packs are installed on your Exchange servers.
1. Update Outlook calendars (only needed if you have users who deliver mail to .pst files):
1.1. Update all client computers by updating Windows time zones.
1.2. Install on all client computers with Outlook the appropriate version of the “Update Time Zone Data Tools” for Microsoft Outlook
1.3. Configure the automatic launch of “Tools ...” when a user logs on to Windows with, for example, the “/ quiet” command line parameter (I recommend that you check for the presence of an installed Windows update before installing / running the server). This will update the calendar at the default mail delivery location, which can be located either in the locally located PST file or in the Exchange database. It's okay when the server calendar is updated again with the Exchange Calendar Update Tool; each calendar item will be updated only once. Multiple launch of "Tools ..." also does not produce any destructive actions.
1.4 “The Time Zone Data Update Tool”, when processing an event, will automatically send all its participants notifications about time changes. Instruct users to accept these changes.
2. Preparation for updating server calendars:
2.1. Please note that despite the fact that the main article devoted to the problem of updating meetings and events in the calendars of Exchange users states that on the Exchange servers, before updating the server calendars, you need to install a time zone update for Windows, the Russian Premier support does not recommend doing so . Instead, they offer to install the OS update on the Exchange servers at the very end. The choice is yours. If you have a contract for Prime support, I recommend not to read it, but to contact them.
2.2. Prepare a custom user to update calendars located on the Exchange server:
2.2.1. Create a user in your AD domain (EXAMPLE \ DSTUpdate).
2.2.2. Create a user mailbox on one of the Exchange-servers.
2.2.3. Give him Exchange View Only Administrator rights for the entire Exchange organization.
2.3. Prepare your computer to run the Exchange Calendar Update Tool (DSTPC).
2.3.1. The computer must be installed:
2.3.1.1. Any of OS: Windows Server 2003, Windows XP, Windows Vista
2.3.1.2. Microsoft Office Outlook 2003 Service Pack 2 or Microsoft Office Outlook 2007 (Better, of course, 2007 SP2)
2.3.1.3. "Time Zone Data Update Tool" for Microsoft Outlook
2.3.1.4. Microsoft .NET Framework version 2.0
2.3.2. No Exchange management tools, such as the Exchange System Manager Console, etc. should be installed on the computer.
2.3.3. You can not prepare such a computer yourself, but use a pre-configured virtual machine . Of course, it will need to be included in your AD domain.
2.3.4. Add the user DSTUpdate to the local administrators group of this computer.
2.3.5. Install the Exchange Calendar Update Configuration Tool on this computer.
2.3.6. Login to DSTPC as DSTUpdate and:
2.3.6.1. Set the value of the HKEY_CURRENT_USER \ Software \ Microsoft \ Exchange \ client \ options \ PickLogonProfile (REG_SZ) parameter to "0".
2.3.6.2. Locate and rename the% USERPROFILE% \ Local Settings \ Application Data \ Microsoft \ Outlook \ extend.dat file as you please.
3. Unloading time zones from user accounts:
3.1. Log on to the DSTPC computer with the user DSTUpdate and run the Exchange Calendar Update Configuration Tool
3.2. Logging level leave Default. If you see errors in the log, switch to Verbose to figure it out, but just like that - no need to trash the output.
3.3. On the Time Zone Extraction page, select the desired servers. If you have a lot of servers, it may take several hours to go through everything.
3.4. After clicking Next, the Exchange Calendar Update Configuration Tool will try to unload users' time zones from the Exchange servers to the file output.txt, which, by the way, is RECORDED each time the application is launched and an attempt is made to upload data.
3.5. If the user, on whose behalf the application is running, does not have access to some pb, you will see the following entry in TimeZoneExtraction.log: [10/20/2011 10:26:02] [552]: HrProcessMailboxTable: Unable log grow user mailbox: Error 0x8004011D.). To solve this problem, use p.4, then unload time zones again.
3.6. Close the application and go to step 5.
4. Providing access to the user boxes for the DSTUpdate user:
4.1. On the computer with the Exchange management tools installed under the account belonging to the Domain Admins group and having Exchange Full Administrator rights to the Exchange organization, run the cscript script GrantMailboxPermission.vbs -Add EXAMPLE \ DSTUpdate ChangeRights.txt
4.1.1. The script is taken from the same article 941018, in the section REFERENCES.
4.1.2. The script takes the LegacyExchangeDN list from the ChangeRights.txt file and provides the EXAMPLE \ DSTUpdate user with Full Mailbox Access and Send As permissions for each mailbox specified in it.
4.1.3. The ChangeRights.txt file must be specially prepared (Microsoft Office Excel can help you):
4.1.3.1. As a blank, TimeZoneExtraction.log is taken. It should be edited so that the resulting file contains lines containing only the LegacyExchangeDN (/ O = EXAMPLE / OU = FIRST ADMINISTRATIVE GROUP / CN = RECIPIENTS / CN = IVANOV.II) without a point at the end, one per line. Empty lines, lines with any other content should not be. That is, you need to cut everything in front of LegacyExchangeDN (starting with “/”) and a period at the end.
4.1.3.2. All service mailboxes of the following type should be removed from the file:
/ O = EXAMPLE / OU = FIRST ADMINISTRATIVE GROUP / CN = CONFIGURATION / CN = CONNECTIONS / CN = SMTP (EXCHANGESERVER) / CN = {11111111-1111-1111-1111-11111111111111}
/ O = EXAMPLE / OU = FIRST ADMINISTRATIVE GROUP / CN = RECIPIENTS / CN = SYSTEMMAILBOX? 11111111-1111-1111-1111-11111111111111?
/ O = EXAMPLE / OU = FIRST ADMINISTRATIVE GROUP / CN = CONFIGURATION / CN = SERVERS / CN = EXCHANGESERVER / CN = MICROSOFT SYSTEM ATTENDANT
4.2. The output of the script is a set consisting of points and exclamation marks. An exclamation mark means an error, a period - everything is OK.
4.2.1. Errors are written to the GrantMailboxPermission.err file.
4.2.2. View error
ADMINISTRATIVE GROUP / CN = RECIPIENTS / CN = IVANOV.II in DC = example, DC = com.
LDAP path from / O = EXAMPLE / OU = FIRST ADMINISTRATIVE GROUP / CN = RECIPIENTS / CN = IVANOV.II
means that the user account in AD is not associated with the mailbox. If everything is correct, and the user really should not be assigned to the box, feel free to ignore these errors.
4.3. You can run the script an unlimited number of times.
4.4. Permission results are recorded in the GrantMailboxPermission.log file. Take care of it - for it then it will be necessary to cancel the granted permissions in Section 6.
5. Processing server calendars:
5.1. It is performed using the same Exchange Calendar Update Configuration Tool. Processing is performed on the output.txt, obtained in paragraph 3.
5.1.1. If item 3 has already been fully implemented:
5.1.1.1. On the mail server selection page, click the Skip button.
5.1.1.2. On the next screen, indicate the prepared output.txt
5.2. The output.txt should be properly prepared (an advanced text editor can help you):
5.2.1. All utility pb should be removed from the file.
5.2.2. On each line with the pb, the time zone must be indicated corresponding to the region:
/ O = EXAMPLE / OU = FIRST ADMINISTRATIVE GROUP / cn = Configuration / cn = Servers / cn = EXCHANGESERVER / O = EXAMPLE / OU = FIRST ADMINISTRATIVE GROUP / CN = RECIPIENTS / CN = IVANOV.II Russian Standard Time
5.2.2.1. If the time zone is not specified, you must specify it manually. If the time zone is incorrect, exclude such users from automated processing.
5.2.2.2. The names of the time zones correspond to the names of the sections of the registry section HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion \ Time Zones \
5.3. Further carry out all actions being guided by the simple master.
5.4. If you have a lot of client computers and not all of them have Windows update installed, you will have to update the calendars in the server pb several times, because non-upgraded users, meanwhile, could create meetings and events.
6. Cleaning after update.
6.1. Run the GrantMailboxPermission.vbs script with the "-remove" parameter. Using the data from the GrantMailboxPermission.log file, the script will remove the permissions granted to the DSTUpdate user on the mailbox of users.
6.2. Cancel the Exchange View Only Administrator permission for the user DSTUpdate.
6.3. Remove the user DSTUpdate from the group of local administrators of the DSTPC computer and from AD.
6.4. If necessary, remove the DSTPC computer from AD and uninstall the OS on it.
7. What you need to update manually:
7.1 The calendars in the public folders of Outlook, although they are located on the server, are not updated as part of the above actions. You must update them manually using the Time Zone Data Update Tool for Microsoft Outlook.
7.2 Calendars in PST files that are not the default mail delivery location will also have to be updated manually. You can instruct technical support or the users themselves how to use the “Time Zone Data Update Tool”.
7.3 Server calendars of users with the wrong time zones. With the help of the same "Tools ..."
Source: https://habr.com/ru/post/130983/
All Articles