Windows 2003 *R2* is crap quality - MMC crashes all over the place

Discussion in 'Windows Server' started by MikeC, Jan 28, 2006.

  1. MikeC

    MikeC Guest

    MikeC, Jan 28, 2006
    #1
    1. Advertisements

  2. MikeC

    Robert Moir Guest

    Robert Moir, Jan 28, 2006
    #2
    1. Advertisements

  3. MikeC

    MikeC Guest

    Robert - "So were you after some help"

    YES, a hotfix or hotfixes would be nice. It's been weeks now.

    All the same there is nothing wrong with letting people know the sorry state
    of M$ software quailty. Obviously M$ did NO TESTING on R2 with common
    utilities and applications!

    I have three open support calls right now. What is your suggestion to help?

    MikeC
     
    MikeC, Jan 28, 2006
    #3
  4. MikeC

    MikeC Guest

    Martin,

    1) A completely clean (formatted disk) install of R2
    2) These are development/test servers - I don't trust M$ that much to
    install directly into production! BUT - it makes no difference as it is
    clearly M$ fault for not doing SIMPLE tests with R2!!!!! Change schedules
    will be affected by M$ lack of quality software!
    3) Install Symantec Antivirus Corp Edition - open console - MMC 3.0 CRASHES
    4) Install Diskeeper - open console - MMC 3.0 CRASHES
    5) Install Backup Exec - open console - MMC 3.0 CRASHES
    5) ISA 2004 test - touch protocol tab - MMC 3.0 CRASHES
    6) Not to mention SQL05 install problems...

    How many more examples do you need?

    "The last phase of testing new things always belongs to the customer." -
    Assuming that the vendor has done SOME testing!!!! In the case of R2 – it
    looks like Microsoft has done NO testing. M$ deserves the rant!

    MikeC
     
    MikeC, Jan 29, 2006
    #4
  5. MikeC

    Ronny Ong Guest

    Although you may not be the only one experiencing problems, I can assure you
    that there are R2 users who do not have any problems whatsoever. Not
    everyone runs the same combination of 3rd party products and versions that
    you do. R2 was in beta testing for a long time, and there was a public
    preview freely downloadable, so there is no excuse for not participating to
    ensure that your particular configurations were represented. You are
    obviously very upset and having an emotional response; "NO testing" is a
    ridiculous claim which makes it less likely that people will want to help
    you.

    I have noticed that Diskeeper 10 (Build 593) has a problem with MMC 3.0, but
    I am not terribly surprised because Diskeeper's timing of this release seems
    to have been driven by marketing to coordinate with their 10th anniversary.
    SAVCE's snap-in has historically had problems with specific MMC versions
    (example: Symantec Support Doc ID 2003111909144448) so I wouldn't be
    surprised if they have an issue with MMC 3.0 which Symantec will eventually
    fix in a maintenance release.
     
    Ronny Ong, Jan 30, 2006
    #5
  6. I do not know if you did this or not, but from experience, if an MMC applet asks you if you want to upgrade the applet to the newest
    version of MMC, you should say no.

    --
     
    BerkHolz, Steven, Jan 30, 2006
    #6
  7. MikeC

    MikeC Guest

    Ronny,

    You are heaping R2 quality issues on *3rd party products* (M$ is in no way
    responsible for testing - VERY COMMON utilities) and my lack of participation
    in an M$ beta program!!!

    I suppose with this logic, that M$ is NOT at fault for NOT testing ISA 2004
    on R2 (ISA is "3rd party" to R2 after all). That bad M$ ISA team, they
    should have participated in the R2 beta program so ISA 2004 would not have a
    problem with R2...

    By the way, no "combinatino of products" is needed - any one installed by
    its self will fail. MMC 3.0 also FAILS with ISA 2004 and "3rd party
    utilities" when it is installed on XP.

    IF M$ did testing of programs that use MMC - and IF beta testers had the
    same RTM code and IF they reported problems, then M$ did some testing of MMC
    v3.0 (included on R2 RTM). Then we can assume that M$ knows about the
    problems but does not care - which in my book is worst than not testing!

    "...eventually fix in a maintenance release." Don't care to have well
    running systems do we?

    MikeC
     
    MikeC, Jan 30, 2006
    #7
  8. MikeC

    MikeC Guest

    Steven,

    No choice in R2, its MMC v3.0 or some hack install of an older version and
    who knows what problems that will bring to R2.

    MikeC
     
    MikeC, Jan 30, 2006
    #8
  9. What I meant was the snapin, not the MMC.

    I had an old firewall that was administered via MMC.
    It was an MMC 1.X snapin.
    Every time I close the MMC, MMC asks me if I want to upgrade the snapin to 2.0.
    If I say yes, the snapin crashes the MMC when opened later.
    If I say no, it works fine whenever I use it.


    --
     
    BerkHolz, Steven, Jan 31, 2006
    #9
  10. MikeC

    MikeC Guest

    Steven,

    Yes, upgrade the snap-in or not, it fails. Still no MMC fix from M$...

    Now this.

    ISA 2004 SP2 fixes the R2 MMC v3.0 problme with the ISA MMC. ISA04 SP2 then
    rudely breaks internal browsing and published websites with these errors:

    Error Code: 500 Internal Server Error. The HTTP request includes a
    non-supported header. Contact your ISA Server administrator. (12156)

    AND

    Error Code: 502 Proxy Error. The HTTP request includes a non-supported
    header. Contact your ISA Server administrator. (12156)

    Wow, lately M$ does not appear to do any real world testing before release!
    Glaring obvious bugs are becoming a common M$ practice!

    MikeC
     
    MikeC, Feb 10, 2006
    #10
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.