Correction on that first paragraph: Meant to say "not applying that setting to Windows 8.1/2012R2 and later."
(There'll be a lot more where that came from. It's an age thing....) On Tue, Oct 24, 2017 at 2:39 PM, Charles F Sullivan < charles.sulliva...@bc.edu> wrote: > I'm not sure why MS seems to make kind of a big deal about not applying > that setting to down level OSes. It's the exact setting that Window > 2012R2/8.1 and later has by default even with SMB1 enabled, so it won't add > or change anything. I just don't see how it would cause a problem. > > On a side note, I was cautious about *removing* SMB1 altogether as a > feature from my Windows 2012R2 and 2016 images because those servers would > be linked to a GPO that *disables* SMB1. I went ahead and did that anyway > on a test machine and there are no errors in the Event Logs, etc, despite > the fact that it added some registry settings (AFIK). > > Side note number 2: For some reason it seems that even after refreshing a > newly linked GPO and rebooting, I had to refresh GP yet again to get the > mrxsmb1:start=4 setting to apply. I've seen this on a few machines anyway. > > > On Tue, Oct 24, 2017 at 1:56 PM, Kennedy, Jim < > kennedy...@elyriaschools.org> wrote: > >> What happens with a setting that is in a GPO applied to a non-supported >> OS. So for example the SMB setting below is on an OU with Win 10 boxes in >> it. Is it just ignored? So it will get ignored and not mess up the Win 10 >> dependencies..correct? >> >> >> >> > > > -- > > Charlie Sullivan > > Sr. Windows Systems Administrator > > Boston College > > 197 Foster St. Room 367 > <https://maps.google.com/?q=197+Foster+St.+Room+367%0D+%0D+Brighton,+MA+02135%0D+%0D+617&entry=gmail&source=g> > > Brighton, MA 02135 > <https://maps.google.com/?q=197+Foster+St.+Room+367%0D+%0D+Brighton,+MA+02135%0D+%0D+617&entry=gmail&source=g> > > 617-552-4318 <(617)%20552-4318> > -- Charlie Sullivan Sr. Windows Systems Administrator Boston College 197 Foster St. Room 367 Brighton, MA 02135 617-552-4318
