ICT_GUY

Hopefully it won't come to that. I am still hoping that someone from Meraki is going to get in touch and sort the mess out.

This is what we use.

I will start by saying that I purchased £20k of Meraki AP's and it has been a joy to install and get up and running with multiple vlans and SSIDS. However, trying to return the demo unit has been a nightmare. First there was Brexit which prevented us even being able to organize a pick up. Then 4 months later when Meraki finally allowed us to schedule the pick up it was picked up and then returned with incorrect customs paperwork a week later (we used everything that Meraki sent us). And then the threatening emails started to arrive. I tried rescheduling a pick up, but I was unable to do so as it was showing that the demo unit had been picked up and was in transit. Despite responding numerous times nothing seems to be moving forward and we are no closer to being able to return the kit. Our business manager is none too pleased at the prospect of a £800 bill for stuff we don't want/need. Just a heads up on the head aches these trials can now cause.

I push out the printers now with a combination of print manager and group policy. Print manager installs the drivers. Group policy attaches the network printer (sometimes). A shortcut on the desktop called "fixprinters" runs gpupdate which brings the printers back to life if they disappear. I assume that this issue will go away once the domain operational level is raised to at least server 2016 (we are currently 2012).

Sorry for not replying. Local profiles were introduced at beginning of term and log on times went down to 20 seconds. Not saving settings is unpopular, but the logon times with roaming profiles were ridiculous and varied between 2 minutes and never. The Microsoft Edge closing down after opening with the following errors The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. & Faulting application name: MicrosoftEdgeCP.exe, version: 11.0.17134.112, time stamp: 0x5b1a453b Faulting module name: EdgeContent.dll, version: 11.0.17134.112, time stamp: 0x162279b6 Exception code: 0xc0000409 Fault offset: 0x00000000000ad3ca Was finally fixed with a registry setting. I imported the following registry settings via a gpo "reg add “HKCU\Software\Microsoft\Internet Explorer\Spartan” /v RAC_LaunchFlags /t REG_DWORD /d 1 /f" Fixing that particular issue also allows windows 10 to open pdfs by default. Stress levels hopefully will subside a little. I thrive on fixing issues. Unfortunately when there are issues that defy logic and should not be there it drives me insane. I also wish I could just switch off the reverting to default app crap. That is such a bug bear.

I didn't have the luxury of testing. Live system had to be converted to windows 10. I tried a phased introduction but I could never get 10 and 7 to coexist well on the system. I am at the point now of having to upgrade our PDC from 2012 to 2016. Unfortunately I work term time only and I don't know how I am going to do that.

I have a network of 200+pcs 100 ipads and all the stuff that goes along with them. It's just me. Windows 10 just seems to be a non stop headache of that does not work. Does not work the way the documentation says it should. Things that frustrate teachers. Stuff that is broken for the sake of breaking it. App defaults resetting even with a preferences file in place. Windows update failing to take the server settings and instead restarting with 15 minutes notice that can't be stopped. App Data, roaming profiles that no longer work (I tried UE-V and followed all the instructions and could not get it to work). Updates that fail to install and lock the machine in a perpetual restart update loop. Edge opening doing nothing before shutting down. None of these issues would have given me much trouble before, but I am getting to the point where the whole system seems broken and poorly thought out / tested. On top of this is the day to day rubbish that a techie has to do on a live system. No money, no training, rubbish pay and high expectations way beyond the senior IT tech pay grade. Windows 10 has just about pushed me to walking out, I don't have the time to bodge stuff that used to work and should just work on an enterprise level network. With no one else to talk to for advice or help its getting to the point that I don't want to be here anymore.

And I just came here for the same reason. So far I have used a GPO for the defaultapps xml it seems to work then win 10 happily overides the settings almost instantly. I have heard that changing OEMDefaultAssociations.xml might fix the issue but I have not tested it yet. Why edge keeps wanting to open pdfs I don't know.

Currently we use WDS for imaging. We have only just moved over to windows 10 and eliminated widows 7from the network. We have approximately 200 pcs in a primary school. I am aware of SCCM and it was on the books to be looked into but I have zero experience with it. With this in mind do you have any advice as to where to start? The system works atm, most of the time but logon speeds for the laptops are terrible, something UE-V looks like it will solve. What do I need hardware and software wise and an idea of the amount of head aches I might encounter and maybe timescale would be really helpful. Also how disruptive would it be to implement on a live system. Sorry for the vagueness of the question, I am just trying to get an idea of what lies ahead and how painful its going to be to get working.

Ok, this would explain a lot of the issues that we have been having. Anything I should know beforehand or is it a question of just implementing it as per the instructions? :-)

A different user on the same machine and it all works, so this seems to be a corruption in the profile. Though it is inconsistent as a reboot on other users sometimes clears it. This is driving me insane.

Random users are having the issue where when you search for applications in the search bar nothing comes up or no local applications. Any idea whats going wrong? We having roaming profiles, build 1803 with all updates. Reenabling windows firewall and doing a gpupdate + reboot fixed the issue for a couple of users but not others. pls help!

We are issuing new drives that are pre encrypted with the recovery keys held securely. Already issued drives will have the data migrated to a wiped and encrypted drive. USB drives will be restricted in use to specific computers and users. So an authorized user cannot access a usb drive on a PC in a computer suite for example. This is to prevent the USB stick being lost because the user leaves it in a pc that is in an insecure location. Also we are deciding on if to enforce a white list of authorized removable drives and or not allowing any data tto be written to unencrypted drives.

A quick update, the issues with the update stalling seem to have been addressed and the update seems to be running smoothly. The fix windows update script fixes any that acquired the broken update. 1803 stability issues seem to have mostly been addressed with the update as I no longer get the black screen of borked login. Chrome still crashes though I have installed the very latest chrome MSI and am waiting to see if the constant stream of annoyed educators returns to normal levels.

From what I have found out about the issue and how I fixed it. The issue seems to be delayed group policy processing. I have a batch file on the desktops named FixPrinters (ico of a printer) which just runs GPUPDATE this brings back the printers. This keeps people happy. Most of the time the printers are either there or appear by themselves. The batch file just hurries it along some.

It worked sporadically here. In the end it was easier to re-image all of the pcs in the school.

There is an issue with KB4103721 cumulative update for 1803 and WSUS. For some reason random clients can get caught in a loop trying and failing to download the update. It will work fine on some but not all clients even if they are identical machines. The error is 2018-05 Cumulative Update for Windows 10 Version 1803 for x64-based Systems (KB4103721) - Error 0x80242006 They will happily update direct from windows update or you can manually install the update by downloading the update directly from MS. Also completely resetting windows update on the client machines will allow the update to run. I use this script which works well. Just thought I would post this as its been making my life hell as the instability issues with 1803 and Chrome have been causing rather a lot of upsetness in staff.

I have assumed that declining the update in our WSUS will forestall the 1803 "upgrade".

I have removed impero from the network (was not the latest version). On a fresh install with no impero and the 1803 ISO downloaded today and installed via WDS I had a black screen on login with an admin account after I ran windows update and rebooted. Rebooted again and it was ok. I have an inkling the issue might be profile linked.

Please elaborate. We have impero and 1803 won't install at the moment and we are getting black screens randomly on client machines.

It failed to install on 95% on my network. Its so bugged I had to decline it as PCs were stuck in a loop trying to get it to install.

My 2 pennies worth. Don't use the N (EU) version, its missing so many standard programs its almost crippled. en-uk en-uk en-uk en-uk en-uk GMT Standard Time This is on the second answer file.

Mine is a primary school, the date was set forward by a few decades or more, whatever the bios limit was. Can confirm that it was not a reset button issue as even ones I had in my room started to experience the issue. It was also confirmed as a bug by Lenovo, affecting "unsupported operating systems"

This was a recommended product from a well know supplier that specialises in schools. A hard lesson well learned. They will not be used again.

We have a multiple subnet campus with users switching between the two sites. We push out printers with gpo with targeting done within the gpo to a specific iprange. As such our gpo for the printers deletes all printers and then assigns them depending on what ip range the PC that they log onto is in. This has worked flawlessly until the windows 10 upgrade.