Anilrgowda

After reading several MS KBs, Blogs, and yes, our very own EE, I am still confused on the DST changes needed to be made on our network. It consists of:
4-server2003
1-server2000 with sql 2000
1-server2000 running exchange 2000
clients running 2000pro and xp pro Total number approx 130
cilients running office 2003 and office xp (outlook used in both).

I have downloaded from my wsus (one of the 2003 servers) the KB 931836 rollup but have not installed on any servers yet. I have downloaded intelliAdmin and am thinking of perhaps using it.
Since my question requires( at least I think) a fairly substantial amount of information and typing and time is running out, I am awarding 500 points (unless I can give more) for the most: useful, easily applied, and hopefully least expensive solution(s). Having said this;
What is the impact of not doing anything for three weeks until the old DST change?
How would this manifest itself with Outlook and OWAs emails and calendaring?
Can you simply manually change times on the DC server or servers and let the time change propageate then adjust back an hour in three weeks when the old change takes place?
Does MS broadcast time correction to the servers creating and issue?
What will hapeen to clients receiving a time change from the server? Remote personal machines?

If I have to do DST patching, what are the options? What are the proper steps and each patch needed?
What is free and what will cost? I know the exchange server appears to be the real thorn so please explain options thoroughly.
Does anything I have now make patching easier and which one do I use?

I am sure I will have more questions so please be patient as I, probably like many, are frustrated, confused, and concerned about making changes to an operational system.

Thanks and good luck (if you choose to attempt this),

Anilrgowda

If you change the time on your servers (domain controllers) then you will break Kerberos authentication. Dependent upon how the phone system interfaces (ex - If you have a system that has a service account that needs to run to provide unified messaging) it may or may not impact you. Without knowing the specific specifics, I can't answer the question with an exact answer.

Regarding Exchange, the big problems are going to be with calendaring and third-party products that interface with CDO to provide calendaring information. If you do not update the OS and the server then you will deal with calendar items and delivery notifications that are an hour off. I haven't tested this particuarly configuration specifically, so I can't note if Kerberos breaks.

Worst case scenario is that you update the W2K Operating System using TZEdit and the script listed on the Microsoft support page and then deal with Exchange not reporting time stamps and delivery correctly. Exchange stores it's information in a .dll dedicated to CDO.

There are companies out there selling scripts/applications that make the same changes mentioned in the example script on the Microsoft website. This only affects the OS. Exchange 2000 requires a change to a .dll and not to the registry.

My thoughts are to save the $4000 and upgrade to Exchange 2003. Granted, that is easier said than done.