Cookdown.EasyTune- 'Tuning Packs' is BLANK

Hi Everyone,
I have imported into our SCOM 2019 UR2 (console says 10.19.10407.0) instance Cookdown.EasyTune-
Step 1 states “Tuning packs contains recommended tuning for one or more MPs”

However, there are no MPs showing in the Tuning Packs window.

Am I missing something here?


Hi Steve,

Are you behind a firewall, proxy, etc.? Sounds a little bit like it can’t connect out to the repository. You might have to get an exception put in if so. It goes off to the raw version of GitHub - cookdown/easytune_overrides: This repository contains the community provided Tuning Packs for Easy Tune via a rebranding link.

Otherwise you can set yourself a fileshare or something like that as your custom store, clone down the repository, and then run a small script to convert it into the correct format. There’s a support article on that here.

Yes, Server is behind a firewall with no outbound connectivity.


Offline method now shows my Custom Store using the CustomStoreFormat (as CSV/json)

I have specific overrides in space for disk space alerting etc.

Can those overrides be maintained alongside EasyTune ‘essentials’?

Depends what you’re targeting with those overrides really.

Generally yes Easy Tune will apply overrides that sit comfortably alongside existing SCOM tuning. There’s no need to remove overrides to get Easy Tune to work.

Using your disk tuning example, if my memory serves me, the default Server tuning packs don’t meddle with disk tuning (it’s pretty organization specific). So these should sit comfortably alongside your tuning.

However if there is overlap with your existing tuning and a Tuning pack the standard SCOM order of application still rules. So depending on the conditions you may find Easy Tune wins in some cases and the existing tuning wins in others. If you are worried about it you could just use the enforced flag on your existing tuning rather than letting it come down to some of the woollier tie breakers such as depth from root node. Easy Tune will flag up if it finds other overrides against the same workflow on the same target, so you would be able to see if there is some sort of conflict (non-managed overrides is how it flags them). But this is done after tuning is applied.

The Enterprise version does have some additional mitigations for this, and you can pull existing tuning into a tuning pack to re-apply with Easy Tune.

Additionally the tuning packs are just CSVs under the covers as you’ve seen, so if there are any workflows you definitely want to steer clear of, you can just select those rows and delete them from the tuning pack, or add in your own level and re-apply them!

Thank you for the additional information. I will tune ADDS first using Easy Tune against the AD DC Group (Microsoft Windows Server 2016) and slowly work my way down the list.

1 Like