Call me simplistic but...
The NZDST issue with windows seems to me to be over complicated.

Here is my current situation:
An external (very competent) sys admin contractor is telling me that we need to apply numerious MS patches to enable MS products to handle new NZDST cutovers...  At the same time he too is questioning the complexity of such patch requirements... We have so far had quite some discussion about the issue.

We are a small company running exchange and the windows domain basics (small by MS standards, perhaps medium sized by NZ standards).
We have no international 'appointment scheduling'.
Appart from myself, we have no appointment scheduling outside the domain... In fact most of our staff would not even know that you can send appointment and meeting invites, let alone outside the domain.
Our Exchange and all the Outlook clients are almost fully insulated from the 'big picture international data colaboration' that MS would like us to believe is the world reality.

So...  What is wrong with this...

Next Sunday night we 'disconnect' our servers from any automated time update information.
We manually roll the time forward one hour.
One week later (on the Windows 2003 server expected date) we roll the time back one hour and allow Windows to do the DST change that it expects to do on that date. (We are not a 24x7 operation, so an hour or two in the middle of the night that has timestamp problems is neither here nor there).
We then have another 6 months or so to either do the patches required by MS or allow them to figure out an automated process that works...

Any feedback on my flawed (or not) plan would be appreciated...

Thanks in advance.