locked
MSE now supports WHS RRS feed

All replies

  • Great news! Thanks!! Finally .. ;-)

    It's now checking my WHS V1 (full scan)..


    .
    .
    .
    .

    "artfudd" wrote in message news:e5fdc443-21da-41d5-87f0-e856bdceb1a2@communitybridge.codeplex.com...

    Version 2 public beta of MSE does now support both WHS v1 and Vail beta.

    http://www.wegotserved.com/2010/07/20/whs-microsoft-security-essentials-working/?utm_source=WGS+Daily&utm_medium=email&utm_campaign=9cfb2d7771-RSS_EMAIL_CAMPAIGN <http://www.wegotserved.com/2010/07/20/whs-microsoft-security-essentials-working/?utm_source=WGS&#43;Daily&utm_medium=email&utm_campaign=9cfb2d7771-RSS_EMAIL_CAMPAIGN>

    https://connect.microsoft.com/securityessentials

    Art [artfudd] Folden

    --


    Have a nice day!
    Wednesday, July 21, 2010 8:41 PM
  • Version 2 public beta of MSE does now support both WHS v1 and Vail beta.

    http://www.wegotserved.com/2010/07/20/whs-microsoft-security-essentials-working/?utm_source=WGS+Daily&utm_medium=email&utm_campaign=9cfb2d7771-RSS_EMAIL_CAMPAIGN

    https://connect.microsoft.com/securityessentials

    Art [artfudd] Folden


     

    It's not "supported" (as that would require installation through an add-in), it just happens to work.  TBH, I don't see it ever being officially "supported" at all.
    Thursday, July 22, 2010 4:03 AM
    Moderator
  • Yes, I suppose "support' was not the right word to use.. 'works' would have been better.
    However, I did not say that WHS supports MSE, I said MSE supports WHS... so semantics
    aside, it could be said I suppose that if MSE made it to work with WHS, then it 'supports'
    it. :)

    Art [artfudd] Folden
    --
    "kariya21 [MVP]" wrote in message
    news:microsoft.en-US.whsvailbeta!22e1503d-37d5-4627-b422-3c036e2561f2@social.msdn.microsoft.com...



    MVP; Stars: 5; Post: 7150;

    Version 2 public beta of MSE does now support both WHS v1 and Vail beta.

    http://www.wegotserved.com/2010/07/20/whs-microsoft-security-essentials-working/?utm_source=WGS+Daily&utm_medium=email&utm_campaign=9cfb2d7771-RSS_EMAIL_CAMPAIGN

    https://connect.microsoft.com/securityessentials

    Art [artfudd] Folden





    It's not "supported" (as that would require installation through an add-in), it just
    happens to work. TBH, I don't see it ever being officially "supported" at all.



    Thursday, July 22, 2010 7:29 PM
  • If MSE installs on WHS then I'd say MS HAS revised MSE to support WHS. So I'm with you Art.
     
    Wilkes
    "artfudd" wrote in message news:df197894-a1e6-46b5-bd0b-640a8041a8fa...
    Yes, I suppose "support' was not the right word to use.. 'works' would have been better.
    However, I did not say that WHS supports MSE, I said MSE supports WHS... so semantics
    aside, it could be said I suppose that if MSE made it to work with WHS, then it 'supports'
    it. :)

    Art [artfudd] Folden
    --
    "kariya21 [MVP]" wrote in message
    news:microsoft.en-US.whsvailbeta!22e1503d-37d5-4627-b422-3c036e2561f2@social.msdn.microsoft.com...



    MVP; Stars: 5; Post: 7150;

    Version 2 public beta of MSE does now support both WHS v1 and Vail beta.

    http://www.wegotserved.com/2010/07/20/whs-microsoft-security-essentials-working/?utm_source=WGS+Daily&utm_medium=email&utm_campaign=9cfb2d7771-RSS_EMAIL_CAMPAIGN

    https://connect.microsoft.com/securityessentials

    Art [artfudd] Folden





    It's not "supported" (as that would require installation through an add-in), it just
    happens to work. TBH, I don't see it ever being officially "supported" at all.



    Friday, July 23, 2010 4:59 AM
  • Support, in this context, is a nebulous concept. My take: if the MSE development team supports it on Windows Home Server, it's "supported". If not, then it's "at your own risk", where "risk" isn't well defined because nobody tests this scenario.

    The general "it's not supported" is because most software that people want to install on their server (transcoding, office suites, etc.) is designed for interactive (i.e. desktop) use. By design, the Windows Home Server desktop isn't to be accessed regularly by end users.

     


    I'm not on the WHS team, I just post a lot. :)
    Friday, July 23, 2010 12:15 PM
    Moderator
  • I agree... and since it is also beta on beta, not usually a supported scenario in most
    cases, it should definitely be considered 'at your own risk'. :) That said I am not seeing
    any problems with it on WHS v1, or Vail for that matter, however I am not using Vail
    presently because I cannot get it to accept the password - or rather get the clients to
    accept the server password, even after a new clean install of Vail. I think I will just
    wait for the next drop.
     
    Art [artfudd] Folden
    --
    "Ken Warren [MVP]" wrote in message
    news:9f106bce-8ae9-4c5f-9562-6f24867d7ae5@communitybridge.codeplex.com...
     
    Support, in this context, is a nebulous concept. My take: if the MSE development team
    supports it on Windows Home Server, it's "supported". If not, then it's "at your own
    risk", where "risk" isn't well defined because nobody tests this scenario.
     
    The general "it's not supported" is because most software that people want to install on
    their server (transcoding, office suites, etc.) is designed for interactive (i.e. desktop)
    use. By design, the Windows Home Server desktop isn't to be accessed regularly by end
    users.
     
    I'm not on the WHS team, I just post a lot. :)
     
     
    Friday, July 23, 2010 12:51 PM
  • since it is also beta on beta, not usually a supported scenario

    Even a beta is not supported.
    Btw, there is a wide range of what "Supported" actually is and what can be expected of support and who does the support and how....


    .
    .
    .
    .

    "artfudd" wrote in message news:0fbe6343-9b92-4adc-b43a-4329bf640742@communitybridge.codeplex.com...


    I agree... and since it is also beta on beta, not usually a supported scenario in most
    cases, it should definitely be considered 'at your own risk'. :) That said I am not seeing
    any problems with it on WHS v1, or Vail for that matter, however I am not using Vail
    presently because I cannot get it to accept the password - or rather get the clients to
    accept the server password, even after a new clean install of Vail. I think I will just
    wait for the next drop.

    Art [artfudd] Folden


    "Ken Warren [MVP]" wrote in message
    news:9f106bce-8ae9-4c5f-9562-6f24867d7ae5@communitybridge.codeplex.com...

    Support, in this context, is a nebulous concept. My take: if the MSE development team
    supports it on Windows Home Server, it's "supported". If not, then it's "at your own
    risk", where "risk" isn't well defined because nobody tests this scenario.

    The general "it's not supported" is because most software that people want to install on
    their server (transcoding, office suites, etc.) is designed for interactive (i.e. desktop)
    use. By design, the Windows Home Server desktop isn't to be accessed regularly by end
    users.

    I'm not on the WHS team, I just post a lot. :)


    Have a nice day!
    Friday, July 23, 2010 4:48 PM
  • Looks like it is no longer viable...

    Notice to Windows Home Server Users: Microsoft Security Essentials Beta is not supported on Windows Home Server (WHS). Beta testers who have installed Microsoft Security Essentials on WHS should uninstall Security Essentials to avoid potential incompatibility problems. Those who plan to beta test Microsoft Security Essentials unsupported should wait until the next Windows Home Server update rollup.

    bummer, clamscan is kinda a pig...

    Friday, December 3, 2010 5:12 AM
  • Chiming in with verification. I installed the MSE beta onto my Vail system. It ran great, but when Windows Update tried to install the new release of the beta, it kept failing with an error code that I couldn't track down. I manually downloaded the update package and installed by hand and got the "MSE is not supported on this platform" error. Oh well. Back to clam for me too.
    Friday, December 3, 2010 8:03 PM