On 06/05/17 05:08, Mike Tomlinson wrote:
> En el artículo <
en36ma...@mid.individual.net>, Adrian Caspersz
> <em...@here.invalid> escribió:
>
>> A similar issue exists in Server 2016, I'm chasing down and can't find a
>> reason whey this hasn't been quashed ...
>
> maybe, as post #8 says, "you might consider simply living with the error
> message; it appears to have no negative consequences"
>
> Is it causing you a problem? From what I've read of the link you gave,
> it's just one of many errors that Windows (in fact, any OS) throws in
> normal day-to-day operation without any deleterious effect.
>
Hi Mike,
Just my delirious style of OCD in trying to master a clean system. You
are right, I routinely ignore other things but found this one came of
interest since it's visible in the Administrative Events view, whereas
others are sanely buried...
I've also just been through a Server 2016 (evaluation) 'Best Practices
Analyser' session also with an aim to get configured things in ship
shape, and think that Microsoft are now giving recommendations on how
best to break their technology - not fix it.
For instance, an example BPA recommendation tells me 'SMB service should
be set to on demand'. So I do that, restart and I receive the subsequent
recommendation 'SMB service should be running'.
Digging further, I think BPA recommendations have been left set as
baked-in for Server 2008 SMB 2.0 practices, maybe don't apply for SMB 3.0
Why am I chasing jobs in this? :-|
--
Adrian C