|
|
Does ANYBODY have ANY info as to the bug that is affecting the WSUS 3.0 mmc
snap-in. I have seen numerous threads regarding the inability of the console
to load after the upgrade of WSUS 2.0 but no answers or possible workarounds.
I to am suffering from the CLSID: FX:{8b6499ed-0241-e032-6508-da4b1c879d7e}
error upon attempted open of 3.0. I have even seen a thread by a WSUS
developer who claims a fix yet the problem only returns again on attempted
reopen of the console. It frustrates me to know that the issue has been
apparent for several weeks and that I did not research and test this upgrade
before implementation. I guess that while reading up on the upgrade, I failed
to notice the section that said ( This install will fail because there is a
bug in our software.) But I guess no one has had time to add that section to
the user guide. I mean it has only been 3 weeks since it's release. Oh well,
all i want to say is if anyone from the WSUS development team and Microsoft
is reading this, thanks for trying to charge me $245.00 to call you to tell
you that you have a problem with your software! I can't believe what a
bargain you give to those who call to inform you of an issue with your
products. I don't even want to know what you charge for actual support but I
do have an unborn child on the way. Oh yeah and thanks for the hotfix for
your updates last week. We are very happy that our systems once again
function after the initial 30 minute or so lockup due to the intense taxing
of system resources by your update bug from patch Tuesday 2 weeks ago. I know
I may be beating a dead horse but it gets old after a while and I suppose
that's why I get paid the big Microsoft bucks to do what I do
everyday.....fix Microsoft products. My only limitation is my inability to
collect hundreds of dollars a minute to provide support for those that depend
on me. But rest assured...I'm on it!
Thanks!
Unhappy
|
|
|