Stringent

Completely forgot about Senso. Ever since we went to v2 its been a lot better (and not) in areas. I have added these exclusions and so far ... So good. Thank you guys.

We have their NextGen seminar this afternoon. I am dubious as always!

For those of us who are Dinosaurs still and have an on Prem SIMS server (we do use Edulink as a wrapper and it works really well in our case), I had them look at our SIMS server for a health check as was the usual slow downs and memory hog. SO a few things I picked up which I thought I would share here. 1. We have SQL 2016 (Windows Server 2019) and he set it to compatibility mode referenced here SIMS - SQL Server - SQL 2016 Compatibility Mode (support-ess.com) as it was running in 2016 native mode. If you have a higher version of SQL (2019 currently supported, 2022 in summer) I'd check if this needs to be done as well. 2. The Server RAM as a guide was set to the database size + 5GB. So ours is about 20GB (Secondary with 1400 students), so RAM set to 25GB 3. Ran the housekeeping routines, Reindex Patch, Update Statistics, ShrinkDBlog you may have to ask for these. 4. SQL Memory usage, the minimum was set to 0 and the maximum was set to 20GB (database size) Since then our memory usage droped from 80-92% usage -> 45% this morning and has held so far. It used to bottle out every month or so. Anyway, hope this may help a few people out. Have a good one.

Companies are quick to blame others. I think Sophos did change their scanning method last year which led to issues, our PDQ took a massive hit as well. But this has mostly been resolved and I am seeing better transfer rates than I used to. Debating to fire up my old Heimdal Trial on the Remote Desktop JUST to rule out Sophos. It was fine on our old 2016 RDS server so I am also wondering if Microsoft have done something in an update as well which has messed Senso up.

Hi It did, then something else went awry and it messed up again. We are currently on Sophos Version 2022.4.2.1 for clients and it now seems to be OK, although Senso now has another issue with Fast User switching where the Internet Browser just doesn't work for another logged in user. Has proliferated to our RDS too (Now on Windows 2022 Server). Senso are aware of a fast user switch issue (have disabled it for now on clients, cue complaints!), but didn't think it expanded to Server. Had to remove it off the server, not going to remove Sophos for obvious reasons to test it out.

Some amazing wins today. So happy. Managed to get Windows 10 to deploy via SCCM to my test machine. Building an image in a VM worked, and even the driver injection worked! Also the new switching arrived for the new build and I get a local link via 10GB Fiber, so heres hoping it will work in the remote building when I hook it all up. Ahh a breather for the weekend. Thanks again guys. I'm off to have a coffee. Nespresso. What else.

Well capturing the physical machine just isn't happening. It goes though the Sysprep and just as its about to reboot, BSOD. No drivers, didn't even run any fancy scripts to remove the app provisioning (start somewhere and work on!) I have a VM captured so will try and deploy that. Silly question, do I enable legacy boot for the new machine and deploy the image with 2 partitions (old school), or try and deploy just the OS to partition 4 with UFEI boot enabled?

Hey Homer (saying that is just fab btw, even said with a Moe voice in my head!) thanks for the suggestion, if this fails then I'll probably look into it. Having created a new capture media from the 1607 ADK my VM machine has rebooted and looks like its capturing ... So thats progress on one level! Just going to try the capture media in the new actual machine I built and see what happens. Thanks all for your support so far. I work in a secondary school, we used to have more than one Network Manager, but due to cuts, its now just me managing ... Well everything. From our VMWare System, to Exchange, SCCM, support etc etc and now a new build to deploy with the switching infrastructure ... Its all very crazy. So to have some sane voices just reminding me of other things is appreciated! I'll also try to help others where I can.

Looks like the VM image is capturing ... It rebooted into WindowsPE and then I get the Error 0x80220014. I just noticed that the Boot Images are still on the previous version despite updating the ADK. Updating the distribution point gives an error as well ... So looks like I'll have to update the boot images manually. Is it worth applying Hotfix 3143760 on my Configuration Manager as well? I know its specifically for 1511 fixing network issues as Snagrat said, but as I'm on SCCM 1606, surely that would have been included?! Sigh. Seems like all this advancement is causing a lot of headaches. Too much, too young, too fast ...

Hi Snagrat, Oh forgot about that! So much else going on here at the moment! I've got version 10.1.10586.0 which was done pre 1607 ... So I'll also try that. Still compiling my VM image as well as a backup.

I am actually trying that now. Using VMWare Workstation, so will see if that grabs up OK. One step at a time, then see if I can get it to deploy correctly, to the correct partition.

After punting for Windows 10 build 1607 on our new machines, I installed and configured Windows 10 Edu on it, installed drivers and software required. Made sure SCCM was up to date (version 1606) and made new Capture Media. Took the new PC off the domain, enabled local admin account, no password, removed any profiles off the machine and ran the created CD. Progress bars go through fine, then just as the PC is about to reboot after sysprepping I get a BSOD (WHEA UNCORRECTABLE ERROR) and the machine reboots. It doesn't go into Windows PE and continue the capture process. It is using Secure Boot on the BIOS. Disable and use legacy boot instead? I've looked through error logs, and can't find anything obvious as to why its doing this. Any pointers/suggestions? Its an HP Pro 400 All-in-One PC. My gut is thats its driver related ... But do I just uninstall them and try sysprepping again?