Sheridan

Found a way using GPP: HKCU\Software\Microsoft\Windows\CurrentVersion\ImmersiveShell TabletMode(DWORD)=0 ConvertibleSlateModePromptPreference(DWORD)=0

Has anyone found a way to prevent the prompt "Do you want to switch to tablet mode" when a keyboard is removed/attached on a tablet/surface? We want some devices to remain fixed in desktop mode

Do you need to drive in the snow/slush/frosts? If so be prepared to put winter tyres on or you won't get it off the drive.

Might have to contact them, its a simple task to move a gsuite mailbox to another gsuite mailbox but I can't get past step 1!

I've moved everyone to Chrome now, but those use IE generally get "Certificate revocation" errors now as well (Smoothwall https inspection I presume,although Chrome doesn't mind and the CA is installed on all PCs) It doesn't seem that far back when we only provided IE7/8/9 and had very few issues! Now its a multi browser battle to find which works best with which!

Has anyone used the Data Migration tool to move Email from user to another user on your GAFE domain? I've tried to do this, and at the first stage where you enter your admin login it says "Authentication error. The username or password you entered is incorrect. Please verify" which isn't right as I'm logged into the admin site with the same details?

Everything else works fine, the other dozen or so vlans (wireless and lan) work ok - its just this one which is a seperate isolated vlan (i.e not routed) It now seems to be a specific problem with one model of the netgear switches, as testing on a older model of switch seems to work! So my nice new stacks are not working!

I've taken the smoothwall completely out of the equation now - a laptops running packet capture on the core switch port does not see dhcp requests coming from the client on the edge switch port. But both can ping each other when with fixed ip's - until I can actaully see the dhcp requests coming across to the core I'm guessing its a switch fault, as the smoothwall won't see any requests to respond to!

Well Netgear have had a look at this and are also confused! At the edge switch any device plugged in to a port configured on the vlan does not get dhcp leases from anything running dhcp on the port in the core switch. Assigning fixed IP's to both of the those ports shows connectivity (i.e ping) and packet capture shows the vlan is working as expected. If I run a packet capture on the dhcp host devices plugged into the core, it does not see any of the dhcp requests I can see being sent on the client device plugged into the edge switch, so somewhere the edge switch is blocking dhcp requests but neither me nor Netgear support can see why! Bizarre, but its also a major issue that will prevent me from setting up byod on our wireless - unless I replace our entire stock of switches with HP

Interesting list - my turn! Schools: 7 Student Number: 2900 Staff Number: 315 IT Staff: 3 (1 * NM, 2 * Tech) Servers: 22 Computers: Approx 1050 Laptops: Approx 215 iPads: Approx 300 Other Tablets: 40

Licensing Windows updates Java!

Another satisfied ReviveIT customer here - used them a good few times and has always been a reliable service.

The uplink ports are all default to untagged on the management vlan (1) - the only tagging on the uplink ports is the actual vlans themselves

Yes exactly that - Untagged for Vlan 80, no tagging for anything else. Its only destined to be part of vlan 80.

Yes - on the core switch the smoothie is plugged into port 1, if I assign PVID 80 to port 2 and plug a laptop into that I get a dhcp address. However, at the edge switche(s) if I configure a port with PVID 80, and have vlan 80 tagged on the trunk ports I get no dhcp address, but can ping the dhcp server when using a fixed IP - so it seems like something blocking dhcp requests across the switches. Netgear don't have a huge amount of options and we have a helper address set on the core switch which is working fine, but that shouldn't be a factor as this vlan is not routed and remains seperate. I'll see if I can pull off some screen shots to make sense of this, but this is how we have it: Core Switch Port 1 - Smoothie - VLAN 80, pvid 80 (ie completely seperate vlan 80) Port 2 - test port - PVDI 80, untagged - plugging into this works fine presumably as its on the same switch! Port 10 - Uplink from edge, tagged 80 (and other vlans not relating to this) Edge switch Port 1 - laptop - PVID 80, untagged (to test) Port 24 - uplink to edge, tagged 80 (again with other vlans not relating to this) In my mind the 80 vlan is then a distinct vlan with only the laptop port and the smoothie on it - so a dhcp request should be fine as the multicast is not trying to cross vlans?

Sorry about the delay - I've been away for a couple of days! Plugging into the smoothie direct gets an IP, but using the same laptop on a edge switch (with the vlans all configured) doesn't work. But assigning a fixed ip address on that laptop I can ping the smoothie, which suggests the vlan is correctly configured. I've got an ip-helper already on the core switch, but it only applies to the other 'domain' vlans and this seperate vlan shouldn't even connect to any of those - hence the reasons I'm using the smoothie for dhcp!

Well, I'm still stumped with this. I've plugged in a laptop to a port on one of the edge switches (with the port pvid set to 80 as a laptop NIC can't have a vlan set) and I can ping the smoothwall gateway from there - so the vlan appears to be good. I just can't get that same laptop to get a dhcp address from the smoothwall.

Oh dear, such a flash device and Windows 10 on it. Swing and a miss! Wonder if the start button hangs on this three grand device!?

All netgear here, I've tried untagging the core switch port that the smoothie is attached to but no difference so far. I feel like I'm so close!

Thats whats I've got, an VLAN interface tagged 80 on Port 5. The core switch has 6 ports with incoming edge switches attached - these ports have all the VLANS tagged (i.e other wireless and VOIP) and the smoothwall is attached to another port also tagged but only with the 80. I've tried a mixture of tagging and untagging but my brain is fried and I think I've forgotten everything about vlans!

We have the AP ports taggeds, the edge switch uplink ports tagged and the core switch ports tagged (which is where are the edge switches meet, plus the port that connects directly to the smoothie). The port on the smoothie has the same vlan tagged and DHCP active on there. The idea is this vlan is completely on the smoothie/wlan and doesn't route across our other subnets. Edit: When I plug a device into another port (untagged on the same VLAN 80) I don't get any dhcp address, only if Iplug directly into the smoothie port. So it looks like my smoothie doesn't work with vlans or my switches

I'm nearly there, set a new SSID on a new VLAN and set the tagging all the way back to the core switch. From the core switch a port connects directly to Port 5 on the smoothie which is running DHCP (and has the ip address) I've got no routing enabled for this vlan, so in theory all devices should hit the smoothie for dhcp (which I know is working if I plug into port 5 directly) but nothing is getting an ip address So basically I have: AP > vlan 80 > edge switch > vlan 80 > Core switch > directly to > smoothie (port 5) Any ideas where I've gone wrong? I've got the tagging set the same as our current 'domain' ssid and thats working ok.

Cheers I would be looking to simplify this in the future. The firewall is an old TMG which has been brilliant but in theory the Smoothie UTM could take over all of its duties.

Cracked it, moved the smoothwall to use an external IP on the same range as the firewall, and with a bit of switch config they both go out independently. Means http/s traffic goes out via smoothwall, anything else is handled by the firewall. Drops the throughput on the firewall as well and now my byod port is working as expected. Cheers for your comments and advice on this one, helped me sort out where I was going wrong!

I think I might restructure this to be: local network > Smoothwall (as default gateway) > private address on smoothwall as external Port > private address on firewall > external address on firewall (ISP). That way all traffic goes to the smoothwall as its the default gateway, and it then routes it through on private addresses to the firewall. That would mean nothing hits the firewall apart from the smoothwall. Assuming the smoothwall UTM is set to allow everything and not NAT the 'normal' traffic then the firewall rules would work as before. I think that might work!