共用方式為

Win2008 R2 BPA Updates Released for April 2010 wave

  • 發行項

Ahoy hoy. The BPA release release cycle has just ticked over once for Windows Server 2008 R2. This means that you can now install – through Windows Update or the Download Center – add-ons that snap into Server Manager and will tell you if you are following MS best practices for your installed roles. Simply install the update, look at the role, and click “scan this role”. After some noodling, BPA will kick out info.

For example, it appears I stink at running DFSN…

image

But I rule at running DFSR!

image

Here’s what just shipped:

  • Update for Best Practices Analyzer for HYPER-V for Windows Server 2008 R2
  • Update for Best Practices Analyzer for Network Policy and Access Services for Windows Server 2008 R2
  • Update for Best Practices Analyzer for Active Directory Rights Management Services for Windows Server 2008 R2
  • Update for Best Practices Analyzer for Application Server for Windows Server 2008 R2
  • Update for Best Practices Analyzer for File Services for Windows Server 2008 R2
  • Update for Best Practices Analyzer for DHCP Server for Windows Server 2008 R2
  • Update for Best Practices Analyzer for Windows Server Update Services for Windows Server 2008 R2

Download them all from here.

Read more about them all here.

You need Windows Server 2008 R2 to use any of this stuff, so add it to your list of reasons to upgrade if you haven’t already. More BPA’s coming out when they… come out. Including updates to these existing ones, in theory.

Hey Mahesh, where’s your post?

 

Ned “beat filecab to the punch for once”  Pyle

Comments

  • Anonymous
    April 29, 2010
    The comment has been removed

  • Anonymous
    April 29, 2010
    A bit. :-) The whole built-in Windows BPA framework only exists in Win2008 R2. It's a new feature. I doubt we'd ever make a version for 2008, it would canibalize business.

  • Anonymous
    April 30, 2010
    Very cool. No love for AD itself? A built-in ADST like the one that came with ADRAPs would be sah-weeeet.

  • Anonymous
    April 30, 2010
    The comment has been removed

  • Anonymous
    May 06, 2010
    The comment has been removed

  • Anonymous
    May 06, 2010
    Please provide detail around your repro steps and settings - step by step. Also provide what you are referencing that states this is correct. We've not been asked about this before, so I don't know yet what expected behavior will be or what would need to be set.

  • Anonymous
    May 06, 2010
    The comment has been removed

  • Anonymous
    May 06, 2010
    Now that's something I can work with. :) I'll get a local repro here when I have a chance and see what's what.

  • Anonymous
    May 11, 2010
    Yeah, I have a local repro. I'll see what I can do about this from our end. If you have a Premier contract please email your TAM to contact me about this.

  • Anonymous
    October 20, 2010
    The comment has been removed

  • Anonymous
    October 20, 2010
    FYI setting your ExecutionPolicy via GPO also causes issues with Exchange 2010, some of the installers break (support.microsoft.com/.../981474).  I just gave up and switched to a Group Policy Preference that sets the LocalMachine ExecutionPolicy (as opposed to the MachinePolicy).  I have a blog post detailing the steps I used: blog.whatsupduck.net/.../issues-with-configuring-powershell.html