You know what they say, patience is a virtue...;-]
So, the following from a very reliable source regarding the GPEdit fix;
1. Windows 2000 (all SPs), Windows Server 2003 (including SP1), and Windows XP
(pre-SP2) are all affected by this problem. The fix is available separately for
each affected platform. Microsoft Support has had them available for a while.
The W2K fix is up on dowload.microsoft.com. The others are not (RC: yet, but
IMO, will likely be soon.)
2. Do not simply copy the W2K files onto W2K3 or XP (pre-SP2). If you need W2K3
or XP fixes, call Microsoft Support.
3. I'm assured that hotfixes are "supported", it says so in the KB itself ("a
supported fix is available...")
4. All reports I have received indicate that the fix is working smoothly.
I never said this problem prevented GPOs from working. Whether you apply this
fix or not, GPOs will continue to be delivered to all of your clients. This is
true even if you edit the GP to include XP SP2 specific information/templates.
The problem is simply in trying to edit GPs that include XP SP2 functionality
from a platform other than XP SP2. If you do, you receive repeated errors.
Further, if you do edit them from an XP SP2 system, and subsequently edit them
from another system, you will truncate the "Explain text" included with the XP
SP2 features.
None of this is life-threatening, but an annoyance and something that may cause
alarm to people already skeptical of XP SP2.
Maybe more importantly, it should have been addressed in a better way. Having
to call Microsoft Support to get a fix because you want to deploy XP SP2 isn't
ideal for many NTBugtraq subscribers. I called, and they were quick, and didn't
charge me for the call to ask for the fix. Others might not be used to such
ease with Microsoft Support, and still more can't easily call a North American
1-800 number and may not find Microsoft Support quite so easy from their home
country.
Cheers,
Russ - NTBugtraq Editor
-----
NTBugtraq Editor's Note:
Want to reply to the person who sent this message? This list is configured such
that just hitting reply is going to result in the message coming to the list,
not to the individual who sent the message. This was done to help reduce the
number of Out of Office messages posters received. So if you want to send a
reply just to the poster, you'll have to copy their email address out of the
message and place it in your TO: field.
-----
