[Today's tip comes to us from Damian Leibaschoff]
Please note that this is an ongoing issue that is under investigation.
UPDATE: This issue is fixed in WSUS 3.0. More information on WSUS 3.0 here.
If you have installed SBS 2003 R2 back when Vista was still in beta (before November of 2006), and you are using the Update Services provided by R2 (The Green Check of Health), you might not be getting all the updates that would be expected.
To make sure you are getting all your updates for your SBS R2 domain joined Vista machines, please follow these steps:
You should start getting all the Vista updates for your clients down through your R2 server after it all gets synched up.
As we said before, this issue is under investigation and we will keep everyone updated on our findings and potential long term solutions.
[Today's post comes to us courtesy of Chris Puckett]
[Contains updated information: Modified Step 4 on when the Update Tools should be run depending on heavy OWA usage for creating appointments. Added link in Step 6 for an update for Exchange 2003 SP 1 installs. New links in Additional Information section.]
[Update 2: Referenced new Sharepoint 2.0 update 933738 in step 7.]
Extended Daylight Saving Time, SBS 2003, and You
The U.S. Energy Policy Act of 2005, passed by the U.S. Congress July, 2005, extended Daylight Saving Time (DST) in the U.S. by approximately four weeks. As a result, beginning in 2007, DST will start three weeks earlier on March 11, 2007, and end one week later on November 4, 2007, resulting in a new DST period that is four weeks longer than previously observed. These four weeks are referred to in this article as the "extended DST period".
Unless certain updates are applied to your computer, it is possible that the time zone settings for your computer's system clock may be incorrect during this four week period. This depends on where you live and which time zone you have selected.
Microsoft Daylight Saving Time Help and Support Center
http://www.microsoft.com/windows/timezone/dst2007.mspx
Before you Begin:
Rapid succession of steps is important: It is preferable to run the Outlook Time Zone Update tool or its Exchange counterpart as soon as possible after the time that the Windows operating system time zone patches are applied to all machines. If meetings between March 11, 2007 and April 1, 2007 are scheduled after the operating system patches are applied but before the tool is run, they will erroneously be moved one hour earlier. To correct such calendar items, organizers should manually update such meetings to ensure they are scheduled accurately for themselves and all invitees.
Updates for SBS 2003
931836 February 2007 cumulative time zone update for Microsoft Windows operating systems
http://support.microsoft.com/default.aspx?scid=kb;EN-US;931836
3. If you have any Mac clients with Entourage 2004, install the Entourage 2004 update. See Microsoft Office 2004 for Mac 11.3.3 Update.
Please consider uninstalling update KB 926666 (applies only to Exchange 2003 SP 2) or KB 931978 (applies only to Exchange 2003 SP 1) from Add or Remove Programs prior to running the Outlook or Exchange Time Zone Data Update Tools (in Step 5). Then reinstall the appropriate update (in Step 6) once you have run the tools.
Recurring calendar items in Outlook Web Access will read from the system time of the Windows system clock on the Exchange Server computer. So at the time that you run the update tools, they will not correctly detect the time zone or time zone rules under which the recurring item was created. If users in your environment create many calendar items using Outlook Web Access and you have already updated your calendars, we recommend advising users to carefully review their calendars and to manually correct any items that might not reflect the correct time during the extended DST period.
5. Run the Outlook and/or Exchange Calendar Update tool(s) to adjust calendar appointments in the extended DST period. This is not required. You may optionally have users manually adjust their appointments in the extended DST period.
Outlook Time Zone Data Update Tool
931667 Addressing the daylight saving time changes in 2007 using the Outlook Time Zone Data Update Tool
http://support.microsoft.com/default.aspx?scid=kb;EN-US;931667
[update from previous post]] After installing the Outlook Time Zone Data Update Tool, you might also install an update for the tool that provides additional functionality.
933146 Description of the hotfix package for the Time Zone Data Update tool for Microsoft Office Outlook
http://support.microsoft.com/default.aspx?scid=kb;EN-US;933146
Exchange Calendar Update Tool
Note 1: This tool must be run from a client that has been updated with 931836 with a user account that has full mailbox rights to all mailboxes. You should not run this tool on the SBS 2003 server. KB 930879 below provides a script to give a user full mailbox rights to all users. When you are done, you can run the script again to remove the full mailbox rights.
Note 2: This tool requires the Outlook Time Zone Update Tool and .Net Framework 2.0 to be installed on the client computer.
Note 3: This tool does not update public folders. The Outlook tool is the only way to update public folders.
930879 How to address daylight saving time by using the Exchange Calendar Update Tool
http://support.microsoft.com/default.aspx?scid=kb;EN-US;930879
6. Install the appropriate Exchange 2003 update to the SBS 2003 server and all Exchange 2003 servers on the network.
If you have Exchange 2003 SP 2 installed, you should install KB 926666. (High-priority update on Microsoft Update on 2/13/2007).
926666 Update for daylight saving time changes in 2007 for Exchange 2003
http://support.microsoft.com/default.aspx?scid=kb;EN-US;926666
[update from previous post] If you have Exchange 2003 SP 1 installed, you should install KB 931978.
931978 Update for daylight saving time changes in 2007 for Exchange 2003 Service Pack 1
http://support.microsoft.com/default.aspx?scid=kb;EN-US;931978
7. Install the Sharepoint 2.0 update to the SBS 2003 server. This requires Sharepoint SP 2.
924881 Description of the update for Windows SharePoint Services: January 9, 2007
http://support.microsoft.com/default.aspx?scid=kb;EN-US;924881
[update from previous post]
933738 is cumulative and includes the 924881 update above.
933738 An update is available that addresses an issue in which items that use the Date field and the Time field are off by one hour in Windows SharePoint Services
http://support.microsoft.com/default.aspx?scid=kb;EN-US;933738
8. Install the SQL 2000/2005 Notification Services Update if SQL Notification Services is installed. If you are not sure if you have SQL Server Notification Services
installed, open KB 931815 and click the link: How to determine whether Notification Services is installed.
931815 2007 time zone update for SQL Server 2005 Notification Services and for SQL Server 2000 Notification Services
http://support.microsoft.com/default.aspx?scid=kb;EN-US;931815
9. Install the Dynamics CRM update, when it becomes available, if Dynamics CRM is installed in your network. If it is not currently available, you can skip to the next step.
925874 Changes to daylight-saving time in 2007 for Microsoft Dynamics CRM
http://support.microsoft.com/default.aspx?scid=kb;EN-US;925874
10. If users have a Windows Mobile device, the device will also need an update.
See steps 3 and 4 here:
http://www.microsoft.com/windowsmobile/daylightsaving/default.mspx#followsteps
923953 How to configure daylight saving time for the United States and Canada in 2007 and in subsequent years on Windows Mobile-based devices
http://support.microsoft.com/default.aspx?scid=kb;EN-US;923953
Additional Information:
To determine if any other Microsoft Programs you might have installed are affected, visit the Microsoft Daylight Saving Time Help and Support Center.
Exchange/Outlook webcast
932046 Support WebCast: The impact of daylight saving time on Microsoft Exchange Server and Microsoft Office Outlook
http://support.microsoft.com/default.aspx?scid=kb;EN-US;932046
Video Demos for running the Exchange and Outlook DST 2007 tools
http://msexchangeteam.com/archive/2007/02/21/435543.aspx
Windows 2000 webcast (Applicable for SBS 2000. Not applicable for SBS 2003).
Jorge Lopez' Support WebCast on Daylight Saving Time and Windows 2000:
http://support.microsoft.com/kb/930688/en-us
How to do the DST change in Windows 2000: 12:40-32:10 (manual method)
GPO method: 34:30-39:10
Q&A 46:50 -1:21:00
Webcasts for daylight saving time changes in 2007
http://support.microsoft.com/gp/dst_webcasts
[Today's post comes to us courtesy of Mark Stanfill]
There has been a large amount of discussion in the community about the release of the Ripcurl update to allow Vista clients to participate in SBS domains (also known as the "Update for Windows Small Business Server 2003: Windows Vista and Outlook 2007 Compatibility (KB 926505)"). The updates you need are now available for download.
Getting Started
First, start with the 31 page white paper at here. The white paper includes links to the downloads you need, as well as the manual steps you have to perform on the client and the server. The six downloads are:
Notes, Highlights, and Gotchas from the White Paper:
[Today's tip comes to us from Mark Stanfill.]
There is a fairly innocuous, but annoying issue with Exchange System Manager (ESM) on servers that you have installed IE7 on. When you click on help in ESM (and only ESM has this issue), and click on one of the help items in the drop-down menu, you receive a Dr. Watson crash message like the following (click on image for full size):
The text of the error will be something similar to:
AppName: exadmin.dll AppVer: 6.5.7638.1 AppStamp:430e730eModName: unknown ModVer: 0.0.0.0 ModStamp:00000000fDebug: 0 Offset: 0003bdc8
If you're seeing this, first let me commend you on actually trying to read the help file :) You can still open the help files directly by navigating to %programfiles%\exchsrvr\bin and double-clicking on chm files.
The crash occurs because of a file (PSAPI.dll) that is updated in IE7, but also exists in system32. To fix this issue, the older version in exchsrvr\bin can be safely renamed. To do this, use these steps:
1) Stop All Exchange and IIS services by stopping the Exchange System Attendant Service and the IIS Admin Service from the Service Control Manager (services.msc).
2) Rename the PSAPI.DLL in the %programfiles%\exchsrvr\bin directory to PSAPI.DLL.OLD
3) Restart all Exchange and IIS services
[Today's post comes to us from Chris Puckett]
There is a bit of a delay in getting the update released for KB 926505 that was originally scheduled for around the end of January. We will update the community with a new date shortly. In the meantime, you may follow the steps listed in KB 926505 to manually join Vista clients to an SBS 2003 domain.
926505 You cannot use the Windows SBS 2003 client deployment tools to join a Windows Vista-based computer to a Windows SBS network
http://support.microsoft.com/default.aspx?scid=kb;EN-US;926505