Even if you run a Core version of Windows 2012, you can have access to the Best Practices Analyzer (aka BPA) to see if the roles you’ve added and configured follow the best practices.
As an introduction, you should have a look to the following articles:
I’ve got 2 other examples where I use a straightforward approach to show only problems you should be aware of and that you can solve:
Get-BpaModel | Where Name -eq "Hyper-V" | Invoke-BpaModel Get-BpaModel | Where Name -eq "Hyper-V" | Get-BpaResult | Where Resolution -ne $null | Format-List -property ResultNumber,Severity,Category,Title,Problem,Resolution
Recently, I’ve also quickly plugged a WSUS for testing purposes but the text for solving the issues doesn’t really help in this case:
Get-BpaModel | ? Name -match "Update Services" | Invoke-BpaModel
Get-BpaModel | ? Name -match "Update Services" | Get-BpaResult | ? Resolution | fl -p ResultNumber,Severity,Category,Title,Problem,Resolution
There warnings are actually correct but they use to old model of Windows 2008 R2. Here’s a more human readable version:
- WSUS: WSUS content should be installed on a nonsystem drive
- WSUS: WSUS database should be installed on a nonsystem drive
I’ve installed the built-in Windows Internal Database (WID) feature that comes along with the built-in WSUS on Windows Server 2012.
Moving the WID database to another partition is and will be another story.