jbostoen's questions

I'm having a weird issue, when running gpupdate on a computer. It comes down to SYSVOL not being accessible. Client: Windows 10 buid 1709 / 16299.125

Situation: 2 domain controllers (Windows Server 2012 R2). - browse to \dc01\sysvol : works - browse to \dc02\sysvol : works - browse to \intranet\sysvol : works

Works intermittently (as in, I don't change anything, don't reboot, just try again at later points): - browse to \intranet.izegem.be\sysvol -> sysvol folder is visible but prompts credentials, even Domain Admin doesn't work - browse to \\sysvol -> sysvol folder is visible but prompts credentials, even Domain Admin doesn't work - browse to \\sysvol -> sysvol folder is visible but prompts credentials, even Domain Admin doesn't work

What could I check? Nothing weird visible when I check dcdiag /v

Update: for future reference, it seems to be a Windows bug: https://social.technet.microsoft.com/Forums/en-US/6a20e3f6-728a-4aa9-831a-6133f446ea08/gpos-do-not-apply-on-windows-10-enterprise-x64?forum=winserverGP

Strangely enough, even Microsoft comes to this conclusion. https://blogs.technet.microsoft.com/leesteve/2017/08/09/demystifying-the-unc-hardening-dilemma/

Domain Forest Level is now 2012R2 as well. No idea what the fix is besides those registry-keys, which seem to be a workaround/disabling.

I can't figure this out. I have 2 HP 2910 switches, interlinked (A1). VLAN 113 is management, I have an uplink to the core switch on port 20. Pinging and browsing works fine. However, I can't ping a storage device in VLAN 114. Other connected devices: StoreVirtual devices, ESXi hosts.

I can ping the management IP of the switch (on vlan 113) until I try to tag port 20 ( VLAN 114 - storage ). This only happens with VLAN 114, I tried another VLAN and the issue did not occur.

Config:

; J9145A Configuration Editor; Created on release #W.14.38

hostname "SAN-SW-01"
module 1 type J9145A
module 2 type J9165A
module 3 type J9008A
ip default-gateway 10.3.13.254
vlan 1
   name "DEFAULT_VLAN"
   no untagged 1-24,A1,B1-B2
   no ip address
   exit
vlan 112
   name "112_ESX"
   ip address 10.3.12.121 255.255.255.0
   exit
vlan 114
   name "Storage"
   untagged 1-19,22-24
   tagged 21,A1,B1-B2
   no ip address
   exit
vlan 113
   name "Management"
   ip address 10.3.13.98 255.255.255.0
   tagged 20-21,A1,B1-B2
   exit
snmp-server community "GlOyS39" unrestricted
snmp-server contact "IT Dienst Izegem"
loop-protect 1-19,21-24,A1,B1-B2
loop-protect disable-timer 3600
no autorun

I can't figure it out, since this configuration on a smaller independent switch does work. I can still ping/browse the management IP. I don't get it why it's a problem above but not with the small switch. Also quite surprised by the order of VLAN 113, 114 above, unsure why it's not in the right order - might that be the problem? Testing is difficult since these are the only 2 switches with that kind of interlink in my network and they are at a critical spot (storage).

; J9774A Configuration Editor; Created on release #YA.15.12.0007
; Ver #04:01.ff.37.27:ea
hostname "HP-2530-8G-PoEP"
ip default-gateway 10.3.13.254
snmp-server community "public" unrestricted
vlan 1
   name "DEFAULT_VLAN"
   no untagged 1-10
   no ip address
   exit
vlan 113
   name "Management_New"
   tagged 10
   ip address 10.3.13.99 255.255.255.0
   exit
vlan 114
   name "VLAN114"
   untagged 1-9
   tagged 10
   no ip address
   exit

Core switch is tagged 113, 114 and some other VLANs (permit all tagged).

Ports in use on this switch for storage (the second storage switch linked through A1 is more or less the same for redundancy )

01/04   01  down link   Storage System  StoreVirtual 2 - san-prod02
01/06   04  down link   Storage System  StoreVirtual 2 - san-prod02
01/08   03  down link   Storage System  StoreVirtual 1 - san-prod01
01/10   02  down link   Storage System  StoreVirtual 1 - san-prod01
01/12   04/04   down link   Server  ESX Server 2 - vmw02
01/14   03/04   down link   Server  ESX Server 1 - vmw01
01/16   03/04   down link   Server  ESX Server 4 - vmw04
01/18   03/04   down link   Server  ESX Server 3 - vmw03
01/19   02  down link   Server  bckp01
A1  A1  up link Network Device  SAN-SW-02

We're trying to link an existing on premises AD with an existing Office 365 (only mail).

We installed Azure AD Connect and went through the steps, we'd like our local AD passwords to be synced with Office 365 / Azure AD.

We set up filtering based on a group, in which we have one test user.

Questions:

• does syncing only delete users on Azure AD if the user has been deleted from the local AD?

• most importantly: our existing users on O365 which are not yet part of he filter (group) we use to configure the sync: they will NOT be deleted? (I'm assuming this but would like confirmation).

Thanks!