search

bryandam / SoftwareUpdateScripts

A collection of scripts related to Software Updates
GNU General Public License v3.0
45 stars 11 forks source link

Feature request - Default UseCustomIndex #7

Closed Skatterbrainz closed 6 years ago

Skatterbrainz commented 6 years ago

If UseCustomIndex parameter is recommended (as a default) it should be enabled unless explicitly requested. Maybe flip that around as -NoCustomIndex (switch param), so it runs by default unless the switch is invoked.

ChadSimmons commented 6 years ago

From my understanding, UseCustomIndex implements something that is highly needed but not supported by Microsoft. So my default position is that it should be off unless specified, even if 99% of implementations enable it. That being said, it really makes no difference to me which way it is implemented.

Skatterbrainz commented 6 years ago

That makes sense, but the verbiage should be updated to reflect that I think. Maybe the warning should be reworded or suppressed altogether?

bryandam commented 6 years ago

As Chad mentions, this is strictly not supported by MS although supposedly they do plan to add one (but not all) of those indexes into the product. So the only thing I'm adamant about is that the user has to take an active step to use them. Since they're super helpful in first-run scenarios I put a note of it in the log file. I always stress that users should use the WhatIf feature before doing anything, especially for the first time. So hopefully they run FirstRun with WhatIf, see the warnings, read the documentation (that I need to write yet), and decide if they want to use it or not.

Skatterbrainz commented 6 years ago

I completely understand the rationale. And I realize this is nitpicky of me. But my OCD feels like it should either be disabled by default, or enabled with a gentle warning. If disabled, maybe it should say it's recommended, even though not supported. I'm just thinking of 2 incidents last year where Microsoft closed a support request because the customer used a utility which applied an unsupported method. Maybe this one isn't that serious and I'm being silly, which is always likely. Anyhow, just a thought. No worries.

bryandam commented 6 years ago

If disabled, maybe it should say it's recommended, even though not supported

That's basically what it does. It's disabled but warns you that you should use it. When I release it I'll have documentation that will help users decide if they want to or not.

Skatterbrainz commented 6 years ago

That makes sense. I didn't mean for that to sound critical or snark. The scripts are fantastic and very helpful. I definitely appreciate them and the work you've put into it.

ChadSimmons commented 6 years ago

Snark?

I thought you were a snark and couldn't help it. You can't exactly read your blog and think, man, this guy is one of the most straight-laced, stoic people around! ;)

bryandam commented 6 years ago

Yep, no worries, we're cool. I'll probably add some mention of it being recommended but not supported ... go see the documentation.