CHiLL

I can't recommend SalamanderSoft enough for automating user accounts from the MIS system. We have SIMS, though according to their page, they also support Bromcom.

Just like how we're now a "paperless" school?

We just have a shared OneNote document, splitting the documentation up in different pages and tabs. The information within OneNote is searchable and you can include attachments (though they aren't searchable).

Here's a thread created yesterday about the issues mentioned by @bondbill2k2: http://www.edugeek.net/forums/enterprise-software/220874-urgent-disable-updates-sccm.html

I think the best way to remove the update from your SCCM Software Update Groups (instead of removing the update deployment entirely): Software Library > Overview > Software Updates. Search for the update in question, select the update(s) from the list (can select multiple). Right click and select Edit Membership. After the list populates, remove the check from all groups that the update is listed in and press OK. When you search for the update again, the "Is Deployed" column should change from "Yes" to "No".

Since no official time-frame was provided, we've said the student keeps it until after they've completed their GCSEs or gets their own laptop first. If it's a Year 7 student, they may well have it for 5 years.

I'm not sure why that's happening. I have found that the update also KB5000802 is also deployed to my Office 2019 and SCEP ADR groups, I'm not sure why. I might have to disable those too.

Great. We have Kyocera MFDs as our follow-me fleet and I can see that our SCCM synced updates last night (being patch Tuesday and all). The easiest way to stop the updates to clients would be to remove the deployment: Software Library > Overview > Software Updates > Software Update Groups. Then select the ADR baseline/update group, select the Deployment tab in the bottom window and remove the collection that the ADR has been deployed to. Thanks for the warning though. I'll remove our Windows 10 updates ADR from clients now.

About 80% of websites appear to be loading correctly for me now, though some still getting tunnel connection errors.

We're having issues with all our Internet services, including SIP telephone lines. It appears Virgin Media are experiencing issues affecting their business users, including packet loss and intermittent page loading. We initially thought it was our Sophos filtering, but that seems fine and Wave9 (who we have our Sophos from) confirm they'd had other reports of school connection issues.

At least they've located it! I'm a big fan of those collapsible Ethernet port covers

Yeah, the HP 250 G7 and HP 255 G8s we received all had Ethernet ports on them too.

The form is now showing the email field. I've signed up and got the confirmation email.

I'm seeing the same form layout as @DJ-1701

I'm not, I've used Edge and Chrome on my PC, and my phone's Chrome via my mobile data. PM Sent. Does it ask for an email for confirmation? My link doesn't!

Excellent! I'm completing the form and submitting, though the page just does a little refresh and I don't get any confirmation of registration. (Or it has worked and it's registered me several times) Thanks on behalf of all stretched techies this week!

I set up our site team with another instance of Spiceworks Cloud. Sure, it's mainly IT focused, but as a free basic helpdesk, it meets their needs. Plus it has AD authentication.

I'm one step further, though not entirely sure how. IP helpers are in place on the core switch and none of the edge switches. With the DHCP scope options disabled and using IP Helpers, the client was just hanging. I managed to get the IP helper method to get an IP by changing a setting on WDS on the SCCM server: WDS > Server > Properties > PXE Response > Respond to all client computers (known and unknown). This was originally set as 'Do not respond to any client computers'. With DHCP scope options defined, the client was getting a DHCP address. Now I have an IP only using IP Helpers, the client is getting the same error that it was when using DHCP scope options. The message displayed is: Downloaded WSDNBP from Press F12 for network service boot Architecture: x64 Contacting Server: TFTP Download: boot\x64\pxeboot.n12 Once that downloads, I get a Windows Recovery error screen saying: Your PC/Device needs to be repaired The Windows Boot Configuration Data (BCD) file from the PXE server does not contain a valid operating system entry. Ensure that the server has boot images installed for this architecture. File: \Tmp\x86x64{GUID}.bcd Error code: 0xc0000098 You'll need to use recovery tools. If you don't have any installation media (like a disc or USB device), contact your PC administrator or PC/Device manufacturer. I have attempted to rebuild the boot image from the ADK. I've redistributed the ADK on the DP. I have re-deployed my x64 TS to all unknown computers. I've unchecked 'Deploy this boot image from the PXE-enabled distribution point', waited, and then re-enabled it.

We have some clients that operate BIOS and some UEFI.

Oh sorry, missed that bit. Yeah, both x86 and x64 are distributed.

Our core is a HP ProCurve 5406zl (layer 3) and our edge switches are HP ProCurve 2530 (which are layer 2 I believe). The IP helpers specify my domain controllers for DHCP and the SCCM server. When I remove the DHCP scope options, the client just sits waiting on the DHCP screen when attempting to PXE boot. Then times out with PXE-53: No boot filename received. SMSPXE.log can see a connection attempt, but the IP reads as 000.000.000.000. Whereas with the DHCP scope options, it will show the client's DHCP address. My boundaries haven't changed in 5 years, but they are defined as: 10.22.0.1 - 10.22.255.254 (which covers all our VLANs) and our Active Directory site. Both have been combined into a boundary group.

They're just self-signed certificates.

HTTP is Access Denied HTTPS works: 9040

I was on 2006 prior to the 2010 upgrade. Unfortunately I've already tried both rebuilding the boot image, including with the latest 20H2 ADK and also disabling PXE and re-enabling it, neither worked. I also disabled PXE and manually uninstalled WDS and renamed the RemoteInstall folder, again, no luck

Since upgrading to SCCM 2010, I'm having issues with the distribution point, where known working Task Sequences were failing due to a variety of reasons, such as content not available, etc. As part of my diagnosing, I removed the Distribution Point and reinstalled it. I took this opportunity to remove the DHCP options 66 & 67 for PXE boot and look at the IP-Helper route. I have added the IP addresses of both DHCP servers and the SCCM server on the core switch, and all edge switches (HP ProCurve range). However, the client I'm testing with won't PXE, it's just sat on the DHCP screen until it times out. SMSPXE.log reports the following: Operation: BootRequest (1) Addr type: 1 Addr Len: 6 Hop Count: 1 ID: 762B58D7 Sec Since Boot: 16 Client IP: 000.000.000.000 Your IP: 000.000.000.000 Server IP: 000.000.000.000 Relay Agent IP: 010.022.100.001 Addr: ec:b1:d7:58:2b:76: Magic Cookie: 63538263 Options: Type=53 Msg Type: 1=Discover Type=55 Param Request List: 0102030405060b0c0d0f10111216171c28292a2b3233363a3b3c42438081828384858687 Type=57 Max Msg Size: 04ec Type=97 UUID: 003db2dcb4cc44e86484eeb8d042385490 PXE::MP_GetList failed; 0x80070490 PXE::MP_LookupDevice failed; 0x80070490 PXE::MP_GetList failed; 0x80070490 PXE::MP_ReportStatus failed; 0x80070490 PXE Provider failed to process message. Element not found. (Error: 80070490; Source: Windows) EC:B1:D7:58:2B:76, B4DCB23D-44CC-64E8-84EE-B8D042385490: Not serviced. Does the IP-Helper need to be configured on all edge switches, or just the core? Do I just specify the IP of the server for helpers, or do I have to include the ports? I can't figure out what I'm missing to get IP-Helpers to work. If I put the DHCP scope options back in, it will PXE but then have problems loading the boot image. I have completely removed the PXE and WDS roles from the server and reinstalled them, which didn't resolve the issue.