Chris Stauffer at myITForum.com

You want me to do What?

Syndication

News

Links to blogs i like

Links

February 2007 - Posts

Just got this. 

The Beta 2 of SystemCenter Configuration Manager (the new name for System Management Server (SMS)) has now been posted to http:connect.microsoft.com/

 Some highlights of this Beta 2 release of SCCM ’07:

·         Admin UI – New MMC3.0 support, Search Folders, Easy Task access, Feature Landing pages and multi select

·         OS Deployment – Complete deployment automation for Client and Server

·         Desired Configuration Management – Policy based, model driven state management of device roles and regulatory reporting

·         Software Update Management – Simplification of Patch Administration for MS, ISV and LoB applications.

·         Security integration to Longhorn NAP – Policy based perimeter security integration with NAP services

·         Internet Based Management – Manage your desktop, laptop, server or device anywhere anytime.

·         Device Management – Over the air management of Windows mobile devices

·         Software Distribution – Significant improvements in software distribution, adding granular control functionality to advertisements and collections.

 With the release of Beta 2 we are continuing to drive down the cost of running the enterprise.  From discovery and inventory through asset intelligence, through OS deployment and into operations -  CM ’07 delivers automation to all aspects of the organization.  We are continuing to prove we are the best platform for the deployment and management of Windows Vista and Office 2007, through enhancements in OS deployment using the task sequence engine, WinPE boot environment, WIM/WAIK integration and the driver catalogue.  Chaining OS deployment for all devices to areas like application distribution, patch management, desired configuration and the soon to be released NAP, System Center Configuration Manager 2007 will prove through a depth and breadth of feature set that this is the strongest tool available to deploy and manage the stack.

 We want you to see the power of this major release.  Open public beta 2 is now available on the Connect Site. Some mirror sites may not be up to date yet but should be completed by the end of the day 23 Feb 07.

 http://www.microsoft.com/technet/sms/2007/evaluate/download.mspx

Posted by cstauffer | with no comments
Filed under:

Just got this from my TAM.

Microsoft has updated two security bulletins: MS07-010 and MS06-058.  MS06-058 has just been updated on Feb 21 and should be re-applied.

 ********************************************************************

Title: Microsoft Security Bulletin Revisions

Issued: February 23, 2007

********************************************************************

 

Summary

=======

The following bulletins have undergone a minor revision increment.

Please see the appropriate bulletin for more details.

 

  * MS07-010

  * MS06-058

 

 

 

Bulletin Information:

=====================

 

* MS07-010

 

  - http://www.microsoft.com/technet/security/bulletin/ms07-010.mspx

  - Reason for Revision: Bulletin updated: "Frequently Asked

    Questions (FAQ) Related to This Security Update" section in

    "Executive Summary" for WSUS Windows Defender update process.

  - Originally posted: February 13, 2007

  - Updated: February 22, 2007

  - Bulletin Severity Rating: Critical

  - Version: 1.1

 

* MS06-058

 

  - http://www.microsoft.com/technet/security/bulletin/ms06-058.mspx

  - Reason for Revision: Bulletin updated: Further investigation of

    CVE-2006-3877 as originally revealed that the update was not

    effective in removing the vulnerability from affected systems.

    The Microsoft Security bulletin, MS07-015 has been issued to

    properly address CVE-2006-3877 and customers should apply the

    updates in this bulletin immediately.

  - Originally posted: October 10, 2006

  - Updated: February 21, 2007

  - Bulletin Severity Rating: Critical

  - Version: 1.1

Posted by cstauffer | 1 comment(s)

Anybody know why this blog addes all that extra space to an entry?

 When i paste in my larger blog posts it always looks fine in the preview but when it displays the block it looks messed up.

 a good example is my last post.

http://myitforum.com/cs2/blogs/cstauffer/archive/2007/02/23/enterprise-patch-management-report.aspx

Posted by cstauffer | 1 comment(s)
Filed under:

Explanation Of Request

I was asked to produce a Patch Status Summary report that would display the status of each Department that is presently tracked though SMS. This report was to contain the following:

 

 Agency 

 Patched 

 Total Requests 

 Total Clients 

 Percent_Compliant 

 Date_ran 

 

Agency = Department

Patched = A sum of all Critical Patches installed

Total Requests = A sum of all patches requested/required

Total Clients =  Number of clients represented in the scan

Percent Compliant = (Patched / Total Requests ) X 100

Date Ran = Date the report was last run

 

This report is only supposed to show critical patches that are older than 30 days. This part is addressed in the actual Stored Procedure query for each agency.

 

This sounds easy but in my environment I am responsible for reporting on 45 agencies.

Here are the problems I saw:

 

Problems

  1. Some of the agencies are under our main Domain and some of the agencies are under a resource domain that they control. So the report needed to list each of 45 agencies.

 

  1. The second problem is that each row in the report requires that the query for that data be altered to reflect each agencies collection. This isn’t that big of a problem but each row takes 5-6 min to run. So, it would take almost 4 hours to run this report.

 

  1. The third problem is caused by agencies that have not implemented ITMU yet. So I added a query to show those agencies that do not have ITMU data in the DB as of yet. Once, all of the agencies are reporting, that part of the report can be removed.

Read the attached Document to see how I resolved this issue.

Posted by cstauffer | 1 comment(s)
Filed under: ,
Microsoft has begun Daily Technical Chats with Microsoft experts. We’ll have a Q&A session everyday from 10:00am to 2:00pm PST. To participate in a technical chat with Microsoft subject matter experts on DST please visit our schedule.

 http://www.microsoft.com/communities/chats/default.mspx

 Or, you can view the technical chat schedule in addition to all of the Live Meeting sessions (live and on-demand) at this location:

 http://support.microsoft.com/gp/dst_webcasts

Posted by cstauffer | with no comments
Filed under: ,

Just got this from my TAM.  Smile

 ********************************************

 Windows Vista is here and customers are beginning to test and deploy it.  One of the stumbling blocks for many companies is IT adoption of Vista due to a lack of management tools.  Exchange Administrators will still want to use Terminal Services to manage Exchange Servers until Exchange tools are written (no ETA on this yet, I will continue to monitor for an update). 

 

The AdminPak (Windows Server 2003 SP1 Administrators Tool Pack) can be installed on Windows Vista, but following installation it is necessary to register some DLLs in order to get the MMC snap-ins to work.  Attached please find a text file which can be renamed to a BAT file. 

 

To install the AdminPak on a Vista machine please do the following.

 

1.       Download and install the executable containing the AdminPak.msi file  from: http://download.microsoft.com/download/6/8/1/681c9ba7-380f-4756-ac85-a3323437e6c3/windowsserver2003-kb304718-administrationtoolspack.exe

2.       Run the executable and install the Administrative Tools.

3.     Run RegisterAdminPak.cmd from an elevated command prompt. To do this, follow these steps:

a.

Click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

If you are prompted for an administrator password or for confirmation, type your password, or click Continue.

b.

At the command prompt, type C:\Users\UserAccountName\RegisterAdminPak.cmd, and then press ENTER.

For more information about the elevated command prompt in Windows Vista, visit the following Microsoft Web site:

http://www.microsoft.com/technet/windowsvista/evaluate/feat/uaprot.mspx (http://www.microsoft.com/technet/windowsvista/evaluate/feat/uaprot.mspx)

 

Known issues

When you install the Windows Server 2003 Administration Tools Pack on a Windows Vista-based computer, the following issues occur.

Context-sensitive help

When you click the ? icon in a property dialog box for all the tools that are included in the Administration Tools Pack, context-sensitive help does not appear.

Cluster administration tools are not supported

Administration of Windows Server 2003 clusters is not supported when you use the Windows Server 2003 management tools directly from a Windows Vista-based computer. This is caused by the network transport protocol that is used by failover clustering in Windows Vista. Windows Server 2003 uses remote procedure call (RPC) over User Datagram Protocol (UDP). Windows Vista uses RPC over TCP. No supported workaround is available.

User interface issues that affect Active Directory directory service snap-ins

The following user interface (UI) issues affect Active Directory snap-ins:

The icons in the results pane disappear after you click the pane.

The icons in the results pane are displayed as rectangles.

These UI issues affect the following snap-ins:

Active Directory Users and Computers (Dsa.msc)

Active Directory Sites and Services (Dssite.msc)

Active Directory Domains and Trusts (Domain.msc)

Additional issues that affect the Active Directory Users and Computers (Dsa.msc) snap-in

You cannot use the drag-and-drop feature in the Active Directory Users and Computers snap-in or in the Active Directory Sites and Services snap-in. For example, if you create a computer object in the Users OU, and then you drag the object to the Computers OU, the operation fails.

The Properties dialog box for users is missing the Terminal Services Profile tab.

The Terminal Services Profile tab does not appear.

Certification Authority (Certsrv.msc)

The Certification Authority snap-in cannot display the Certificates Template node.

Microsoft Internet Information Services

The following Microsoft Internet Information Services (IIS) scripts are installed. However, they do not work.

Iisapp.vbs

Iisback.vbs

Iiscnfg.vbs

Iisftp.vbs

Iisftpdr.vbs

Iisvdir.vbs

For more information about how to configure IIS by using command-line tools, visit the following Web site:

http://www.iis.net (http://www.iis.net)

Windows Internet Name Service (WINS) (Winsmgmt.msc)

When you create or edit a static mapping, you receive the following error message:

The stub received bad data

However, you can safely ignore this error message because the operation is successful.

Terminal Services Licensing (Licmgr.exe)

When you try to start a Terminal Server license server, you receive the following error message:

The License Server Activation Wizard cannot start. Close one or more programs, and then retry the operation.

Terminal Server Administrator (Tsadmin.exe)

The Terminal Server Administrator tool does not work on a Windows Vista-based computer because of an access violation. To work around this issue, run Remote Desktop from a Windows Vista-based computer, and connect to another computer that can use Tsadmin.exe. For example, connect to a Microsoft Windows XP-based or a Windows Server 2003-based computer that has the Administration Tools Pack installed.

Remote Storage Remote Administration tool

The Remote Storage Remote Administration tool (RSAdmin.msc) is not supported in Windows Vista.

The Connection Manager Administration Kit

In the Administration Tools Pack, you must start the Connection Manager Administration Kit (CMAK) by using one of the following methods:

Run CMAK from an elevated command prompt. To do this, follow these steps:

1.

Click Start, type cmd in the Start Search box, right-click cmd.exe in the Programs list, and then click Run as administrator.

If you are prompted for an administrator password or for confirmation, type your password, or click Continue.

2.

At the command prompt, type CMAK, and then press ENTER.

For more information about the elevated command prompt in Windows Vista, visit the following Microsoft Web site:

http://www.microsoft.com/technet/windowsvista/evaluate/feat/uaprot.mspx (http://www.microsoft.com/technet/windowsvista/evaluate/feat/uaprot.mspx)

Right-click the CMAK command or icon, and then click Run as Administrator.

Note If you start CMAK from a non-elevated command prompt or by double-clicking the CMAK icon, you receive the following error message:

To continue you must have read/write permissions to the directory Program Files\CMAK\Profiles.

Posted by cstauffer | with no comments
Microsoft IT Guidance

·         MSIT DST Assessment Checklist

·         MSIT DST Enterprise Response Plan

·         MSIT DST Patching Overview

·         MSIT DST Exchange TZ Update Tool Guidance

·         MSIT DST Outlook TZ Update Package Guidance

·          

·         Windows Server

·         February 2007 cumulative time zone update for Microsoft Windows operating systems

·         How to configure daylight saving time for the United States in 2007

·         Deploying Microsoft Windows 2000 updates for daylight saving time changes for worldwide use

·         How to configure daylight saving time for the United States and Canada in 2007 and in subsequent years on Windows CE-based devices

·         How to configure the daylight saving time start date and end date for Guatemala in Windows

·         FIX: U.S. daylight saving time changes in 2007 do not occur on the correct day on Windows CE 5.0-based devices

·         A hotfix is available to change the daylight saving time for the (GMT+02:00) Cairo time zone in 2006 for Windows XP and for Windows Server 2003

·         New time zone update for Sri Lanka

·         An update is available to remove the Australian daylight saving time 2006 912475 update

·         Description of Software Update Services and Windows Server Update Services changes in content for 2006

·         Description of issues that are related to time zone changes in Indiana

·         Microsoft products do not reflect Australian daylight saving time changes for the year 2006

·         Exchange Server

·         How to address daylight saving time by using the Exchange Calendar Update Tool

·         Update for daylight saving time changes in 2007 for Exchange 2003 Service Pack 1

·         Information about the changes to daylight saving time in 2007 for Exchange 2000 Conferencing Server

·         Virtual Machine for Microsoft Exchange Calendar Update Tool

·         You can no longer mount any of the Exchange databases after you apply hotfix 926666 to a computer that is running Exchange Server 2003

·         Update for daylight saving time changes in 2007 for Exchange 2003

·         Addressing the daylight saving time changes in 2007 using the Time Zone Data Update Tool for Microsoft Office Outlook

·         How to incorporate Indiana's time zone change in Outlook e-mail clients in Exchange Server

·         The time of an appointment that is contained in an e-mail message is changed when the message is sent or received by an Exchange 2000 computer that uses the Microsoft Exchange Connector for Novell GroupWise

·         Appointments appear off by one hour when you use Collaboration Data Objects to obtain calendar information from Exchange Server 2003

·         Microsoft Outlook Web Access and Microsoft Collaboration Data Objects (CDO) daylight saving time transition change for Australia in the year 2006

·         Microsoft products do not reflect Australian daylight saving time changes for the year 2006

·         The time settings in Outlook Web Access on Exchange Server 2003 may not reflect the change to Western Australia daylight saving time during the transition period

·         The time settings in Outlook Web Access on Exchange Server 2003 SP2 may not reflect the change to Western Australia daylight saving time during the transition period

·         After you configure the Jerusalem time zone settings to match the transition dates for daylight saving time, meetings are moved ahead by one hour when a user accepts a meeting request by using a CDO program in Exchange Server 2003

·         Meetings are unexpectedly moved one hour ahead in the last week of October in Exchange Server 2003

·         Meetings are unexpectedly moved one hour ahead in Exchange 2000 Server

·         Description of the Outlook 2003 post-Service Pack 2 hotfix package: October 24, 2006

·         Appointments appear off by one hour when you use Collaboration Data Objects to obtain calendar information from Exchange Server 2003

·         Australian daylight saving time 2006 update for environments that do not use Exchange Server has now expired

·         SharePoint Services

·         Description of the update for Windows SharePoint Services: January 9, 2007

·         How to configure time zone information in Windows SharePoint Services by modifying the Timezone.xml file

Posted by cstauffer | with no comments
Filed under:

I need a report that would show all of the server that are located in SMS and it needed to tell me how many server had the client and how many where missing.

 

This sounds easy but in my environment I am responsible for reporting on 42 agencies. Some of the agencies are under our main Domain and some of the agencies are under a resource domain that they control. So the report needed to list each of 42 agencies.

 

So how do I do it if there are additional domains?

 

I create a collection for each agency using the following criteria.

 

  1. Domain name
  2. OU location
  3. Site code

 

This allows me to get an accurate count for each agency even if they are in different domains.

 

I created all of the collections under a head collection called Agencies.

 

So it looks like this

 

All Agencies

àDOH

àDPW

àL&I

àetc….

 

So now I have a structure that I can use in SMS to control my reports.

 

In all of the reports that I have posted you may have noticed the variable for collid points to a query like this:

 

SELECT    v_Collection.CollectionID, v_Collection.Name

FROM         v_CollectToSubCollect INNER JOIN

                      v_Collection ON v_CollectToSubCollect.subCollectionID = v_Collection.CollectionID

WHERE     (v_CollectToSubCollect.parentCollectionID = 'PAC0004A')

ORDER BY v_Collection.Name

 

Basically what I am doing with this query is saying show me all of the collections listed under “All Agencies”

 

In order to get a count of servers I used this same type of query to give me the list of clients that are servers in each of these collections.

 

I want to thank Garth Jones for this next part.

 

He provided the knowledge for the basis of this report

 

http://smsug.ca/blogs/garth_jones/archive/2007/02/08/149.aspx

 

He also added a part to get rid of the temp table so it doesn’t view in SMS Web Reports.

 

http://smsug.ca/blogs/garth_jones/archive/2007/02/09/150.aspx

 

So now that I have a way to determine what agencies that I want to report on I needed a way to show how many server had a client and how many didn’t. I used a temp table based on what Garth posted above.

 

Here is the working report.

 

 

SET NOCOUNT ON

 

(SELECT      v_Collection.Name AS 'Department', COUNT(v_FullCollectionMembership.Name) as 'NOTok' into #SMSCliNot1

FROM         v_CollectToSubCollect INNER JOIN

                      v_Collection ON v_CollectToSubCollect.subCollectionID = v_Collection.CollectionID INNER JOIN

                      v_FullCollectionMembership ON v_Collection.CollectionID = v_FullCollectionMembership.CollectionID INNER JOIN

                      v_R_System ON v_FullCollectionMembership.ResourceID = v_R_System.ResourceID

WHERE     (v_CollectToSubCollect.parentCollectionID = 'PAC0004A') AND (v_R_System.Operating_System_Name_and0 LIKE '%Server%') AND

                      (v_R_System.Client0 is null )

GROUP BY v_Collection.CollectionID, v_Collection.Name)

 

 

 

(SELECT      v_Collection.Name AS 'Department', COUNT(v_FullCollectionMembership.Name) as 'CliOK' into #SMSCli1

FROM         v_CollectToSubCollect INNER JOIN

                      v_Collection ON v_CollectToSubCollect.subCollectionID = v_Collection.CollectionID INNER JOIN

                      v_FullCollectionMembership ON v_Collection.CollectionID = v_FullCollectionMembership.CollectionID INNER JOIN

                      v_R_System ON v_FullCollectionMembership.ResourceID = v_R_System.ResourceID

WHERE     (v_CollectToSubCollect.parentCollectionID = 'PAC0004A') AND (v_R_System.Operating_System_Name_and0 LIKE '%Server%') AND

                      (v_R_System.Client0 = '1' )

GROUP BY v_Collection.CollectionID, v_Collection.Name)

 

 

 

 

Select #SMSCli1.Department as 'Department'

                , CliOk as 'Clients installed'

                , NOTok as 'Clients missing' 

From

#SMSCli1 Full outer join #SMSCliNot1 on #SMSCli1.Department = #SMSCliNot1.Department

 

Where #SMSCli1.Department is not null

 

order by #SMSCli1.Department

 

drop table #SMSCli1

 

drop table #SMSCliNot1

Posted by cstauffer | 1 comment(s)
Filed under: ,

I’ve had a problem with the ITMU reporting for some time. The problem was associated with MS06-014. This patch was showing 10-15 times the numbers it should have been showing. I almost open a ticket with MS today because I needed to get my numbers correct because I had to make a new report that shows the overall status of the Different Departments. But since the numbers for MS06-014 are way off it was adding about a 5-10 % difference to them. So if the status showed they were at 80% they where actually 70-75% .

 

This is what I was seeing:

As you can see I only have 18926 clients in this report but it list 209650 requesting the patch 

2/9/2007 12:58:44 PM

      (Number of Records: 59)

 MS Number 

 Patched 

 Total Requested 

 Clients Reporting 

MS06-014 

 209609 

 209650 

 18926 

 

 

 

 

 

 The problem was cause by MS releasing a language pack for each of the languages that it supports. To resolve this I added the located ID for location 0 and 9 to the ITMU reports temp table “where” statement.

 

As you can see this fixed the issue.

 

2/12/2007 2:29:56 PM

      (Number of Records: 59)

 MS Number 

 Patched 

 Total Requested 

 Clients Reporting 

MS06-014 

 8838 

 8867 

 18908 

 I attached my new reports incase anybody was using the old ones.

Note: you will need to change the Collection ID query to reflect your environment.

 I also included my new Critical patch report. I will blog on that seporate.

 

The change is in red below.

 

SELECT DISTINCT

                ps.Bulletin AS Bulletin_No,

                ps.Retrying + ps.PreSuccess + ps.Uninstalled + ps.PendReboot + ps.Verified + ps.NoStatus + ps.Failed - ps.Verified AS Unpatched,

                ps.Retrying + ps.PreSuccess + ps.Uninstalled + ps.PendReboot + ps.Verified + ps.NoStatus + ps.Failed AS 'Total with Status',

        ROUND((100 * (ps.Verified + .00000001)) / (.00000001 + ps.Retrying + ps.PreSuccess + ps.Uninstalled + ps.PendReboot + ps.Verified + ps.NoStatus + ps.Failed), 0) AS '% Compliant',

                ps.Verified, ps.NoStatus, ps.Retrying, ps.PreSuccess, ps.Uninstalled, ps.PendReboot, ps.Failed, real_total.total, ps.CollectionID

FROM         (

                                SELECT     fcm.CollectionID,

                                                pse.ID AS Bulletin,

                                                SUM(CASE WHEN pse.LastStateName = 'No Status' THEN 1 ELSE 0 END) AS NoStatus,

                                                SUM(CASE WHEN pse.LastStateName = 'Install Verified' THEN 1 ELSE 0 END) / 2 AS Verified,

                                                SUM(CASE WHEN pse.LastStateName = 'Retrying' THEN 1 ELSE 0 END) AS Retrying,

                                                SUM(CASE WHEN pse.LastStateName = 'Preliminary Success' THEN 1 ELSE 0 END) AS PreSuccess,

                                                SUM(CASE WHEN pse.LastStateName = 'Uninstalled' THEN 1 ELSE 0 END) AS Uninstalled,

                                                SUM(CASE WHEN pse.LastStateName = 'Reboot pending' THEN 1 ELSE 0 END) AS PendReboot,

                                                SUM(CASE WHEN pse.LastStateName = 'Failed' THEN 1 ELSE 0 END) AS Failed

                                FROM         

                                                v_ApplicableUpdatesSummaryEx INNER JOIN

                        v_GS_PatchStatusEx pse ON v_ApplicableUpdatesSummaryEx.UpdateID = pse.UpdateID RIGHT OUTER JOIN

                        v_FullCollectionMembership fcm ON pse.ResourceID = fcm.ResourceID

                WHERE

                                                (pse.LocaleID In ('0','9'))

                                                AND (pse.QNumbers NOT LIKE 'None')

                                                AND (pse.ID NOT LIKE 'None')

                                                AND (fcm.CollectionID = @collid )

                                                GROUP BY pse.ID

                                                , v_ApplicableUpdatesSummaryEx.Type

                                                , fcm.CollectionID

                HAVING 

                                                (v_ApplicableUpdatesSummaryEx.Type = 'Microsoft Update')) ps

INNER     JOIN

                (

                SELECT DISTINCT ID0

FROM         v_GS_PATCHSTATEEX

WHERE   (Language0 = 'English' Or LocaleID0 In ('0','9'))

                 AND       ID0 <> 'none'

                 AND       Type0 = 'Microsoft Update'

                 AND       Severity0 = '10') As  PatchList

ON           ps.Bulletin = PatchList.ID0

 

 

 CROSS JOIN

 

                          (SELECT     CollectionID, COUNT(ResourceID) AS total

 

                            FROM          v_FullCollectionMembership

 

                            GROUP BY CollectionID

 

                            HAVING      (CollectionID = @collid )) real_total

 

ORDER BY ps.Bulletin DESC

Posted by cstauffer | 1 comment(s)
Filed under: ,
Installing this update enables your computer to automatically adjust the computer clock on the correct date in 2007 due to revised Daylight Saving Time laws in many countries. After you install this item, you may have to restart your computer.

KB931836

 

Update for Windows Server 2003 (KB931836)

Installing this update enables your computer to automatically adjust the computer clock on the correct date in 2007 due to revised Daylight Saving Time laws in many countries.

Update for Windows Server 2003 for Itanium-based Systems (KB931836)

Installing this update enables your computer to automatically adjust the computer clock on the correct date in 2007 due to revised Daylight Saving Time laws in many countries.

Update for Windows Server 2003 x64 Edition (KB931836)

Installing this update enables your computer to automatically adjust the computer clock on the correct date in 2007 due to revised Daylight Saving Time laws in many countries.

Update for Windows XP x64 Edition (KB931836)

Installing this update enables your computer to automatically adjust the computer clock on the correct date in 2007 due to revised Daylight Saving Time laws in many countries.

Update for Windows XP (KB931836) 

Installing this update enables your computer to automatically adjust the computer clock on the correct date in 2007 due to revised Daylight Saving Time laws in many countries.

It's not available on WSUS (yet).
Posted by cstauffer | with no comments
Filed under:

According to the web cast notes from Friday:

 

*       Windows Update: Patches are currently available as Optional updates.  They will be offered as Critical updates in mid-February.

 

Note: It does NOT say one way or the other if it will be available via SMS 2003 ITMU.

 

 

This is my favorite part of the presentation

 

*       “The Secretary of Energy will report the impact of this change (Energy Policy Act of 2005) to Congress. Congress retains the right to resume the 2005 Daylight Saving Time schedule once the Department of Energy study is complete.”

 

*       Be aware that there may be further changes to DST dates in the future based on a formal review by the Department of Energy.

Posted by cstauffer | 2 comment(s)
Filed under: ,

get lots of Vista gadgets here

 

http://gallery.live.com/default.aspx?l=1

 

Posted by cstauffer | with no comments
Filed under:

Impact of North American Daylight Saving Time changes in 2007 on BlackBerry smartphone users

http://www.blackberry.com/select/dst2007/

Posted by cstauffer | with no comments
Filed under:

 

http://blogs.msdn.com/stephen_griffin/archive/2006/12/06/outlook-2007-timezone-structures.aspx

 

Posted by cstauffer | with no comments
Filed under:

Addressing the daylight saving time changes in 2007 using the Outlook Time Zone Data Update Tool

http://support.microsoft.com/kb/931667/en-us

 

The following table describes the situations when you should download and run the Time Zone Data Update Tool:

Outlook 2007 Outlook 2003, Outlook 2002, Outlook 2000
You do not have to use the Time Zone Data Update Tool. However, we recommend that you run the tool because it includes many improvements over the tool that is included in Outlook 2007. Run the Time Zone Data Update Tool.
In environments running Microsoft Exchange, a special version of the Time Zone Data Update Tool may be used to update multiple Exchange mailboxes on the server. In environments running Microsoft Exchange, a special version of the Time Zone Data Update Tool may be used to update multiple Exchange mailboxes on the server.

Note: You do not have to run both the Outlook and Exchange versions of the Time Zone Data Update Tool. We encourage you to read all the documentation on each and determine which tool will best suit your specific environment and needs.

 

 

Q: When should I run the Time Zone Data Update Tool?

A:
The Time Zone Data Update Tool will have to be run manually at the discretion of the user or Administrator after the operating system time zone definitions have been updated.

It is better to run the Time Zone Data Update Tool or Exchange tool as close as possible to the time at which the operating system time zone update was applied (to all computers). This will minimize the chance of having single-instance appointments that were booked after the Windows time zone update was applied but before the Time Zone Data Update Tool or Exchange tool was run. Because Outlook 2007 has this functionality already embedded in it, the user is not required to manually run the Time Zone Data Update Tool. Outlook 2007 will automatically detect that the change is required and will prompt the user when it runs the tool.

However, the Time Zone Data Update Tool contains code changes that refine the experience and is the preferred method of updating your calendar. This can be done by canceling out of the dialog boxes that appear automatically in Outlook 2007 and following the instructions to download and run the Time Zone Data Update Tool instead.

Posted by cstauffer | with no comments
Filed under:
More Posts Next page »