Citrix Addresses Windows 2000 SP4 Issues

In late June, Microsoft released Service Pack 4 for Windows 2000. Within hours, support forums and web boards became abuzz with problems experienced in Citrix MetaFrame environments after the Windows Service Pack was installed.

In late June, Microsoft released Service Pack 4 for Windows 2000. Within hours, support forums and web boards became abuzz with problems experienced in Citrix MetaFrame environments after the Windows Service Pack was installed. As seen on the THIN list, public newsgroups, thin planet, and the Citrix knowledge base, most of the problems had to do with extremely slow logons once the service pack was installed. These issues were so bad that Roy Tokeshi (of the Citrix MetaFrame Thin Client Support Community) even created a support site dedicated to the problems.

Microsoft has acknowledged the problems in Citrix MetaFrame environments and released a post-SP4 hotfix.

All of these issues lead to one question--if Citrix and Microsoft work so closely together, how could there have been such a major issue with new a Microsoft service pack that broke just about every MetaFrame environment where it was installed?

During the press conference at iForum last week, I posed this question to Citrix's CTO Bob Kruger. He responded by basically saying that he wasn't aware of any issues and that Citrix and Microsoft work closely together on new software. (Click here for the full transcription of my question and Kruger's response.)

A lot of readers sent me email saying that they were shocked at Kruger's response. I added some of their comments to the end of the transcript. On Friday, I received an email from Bob Kruger.

In his email, Kruger pointed out that there aren't enough hours in the day for him to stay on top of the message boards and fulfill both his roles at Citrix, so he depends on the support folks to keep him clued in to the major problems. He said that "While the boards might be abuzz with stuff about SP4, the percentage of calls related to SP4 have been negligible."

He further committed that "your question in the press session and the comment on your site have led me to challenge things and I do intend to find out what’s really transpired." He said that his team has a meeting with the Microsoft Terminal Services product group very soon and that he'll be verifying that nothing went awry with their processes and procedures. Kruger closed the email by saying that he took the issue to heart, and that he agrees that a service pack shouldn't have broken MetaFrame.

All in all, I personally feel that this is great news. While it's too late for anything to be done about SP4, I think that the issues have been raised to the right people within both companies, and hopefully we won't see any other "out-of-the-box" problems of this magnitude in the future. (After all, Microsoft did name Citrix as their "Global ISV of the Year.")

Join the conversation

1 comment

Send me notifications when other members comment.

Please create a username to comment.

This message was originally posted by an anonymous visitor on July 2, 2004
I don't think SP4 infact broke MetaFrame specifically. There were a number of issues related to SP4 that simply broke Windows and infact other software including RDP.
Cancel

-ADS BY GOOGLE

SearchVirtualDesktop

SearchEnterpriseDesktop

SearchServerVirtualization

SearchVMware

Close