ETx13

They're all using the same image. So same OS version and same client version.

We've reimaged all of our student devices this summer (about 7000 or so) and have noticed that 50 or more of them come up with a blank Software Center when they try to open it. By blank, I mean that the window is white and locked up (have to terminate the process through Task Manager). I've uploaded the SCClient log for when that blank screen happens but I couldn't find anything too useful in it (maybe someone here can). When I try to uninstall/re-install the client through SCCM all I get is the old Software Center that fails to load anything. I've been trying to figure this out for a few days now, the only fix so far that works is to completely re-image the device again. SCClient@student_3.log

Looks like it was the network driver after all. Thought I had the latest (we're not in 2017 anymore? Oh boy..) but then found one from last year. Still a bit slow to connect after a reboot but it does so without logging in. As for the BIOS, I learned that LifeCycle from Dell doesn't update the BIOS to the latest version. Found a newer version on their site. Thanks for the tip! It's nice when someone tells you to check on basic things since we all sometimes forget

Recently (pass few months) I've noticed that after a restart the servers don't reconnect to the network. After I login, then it reconnects automatically. We just got 2 new Dell servers, fresh install of Server 2022 (not on domain yet) and the issue is still there. Every time I restart them, I have to use iDRAC to remote on to login and then I can RDP and keep working. Anyone else experiencing this or know why this is happening?

Is it distributed to the distribution point? In my image you can see that green circle in the bottom right (shows 4 targeted, 4 Successes), does yours show a green circle as well?

Pardon the black boxes, I'm not sure what should be kept hidden or not.

In Software Library expand Operating Systems, click on Boot Images, right click the x64 version and select Properties. Go into the Data Source tab and check off the box "Deploy this boot image from the PXE-enabled distribution point".

Yes I have. IIS is working except it says it's not secured because the certificate is using SHA-1 (this is expected behaviour from browsers). I did add my root cert as mentioned in the guide. Interestingly enough I decided to try again and now I only get this error: Call to HttpSendRequestSync failed for port 443 with status code 403, text: Forbidden SMS_MP_CONTROL_MANAGER 3/4/2024 10:17:40 AM 3460 (0x0D84) Which I guess is progress but I'm thinking it's still because we use SHA-1 certs instead of SHA-2... I could be wrong though.

I've been following this guide to a tee: How can I configure System Center Configuration Manager in HTTPS mode (PKI) but I've run into a snag. After switching the MP to use HTTPs, I looked into the logs to make sure it switched over properly but I've been getting this error: Couple notes: 1. I was getting a "Certificate doesn't have SAN2 extension" error so I found out that I had to add the "Client Authentication" extension to the SCCM IIS Certificate which got rid of that error. 2. Looking at the MPSetup log, I noticed that the install went through but required a restart for some reason. Even after a restart, that log didn't change. 3. I haven't found any notes about this but our CA is still using SHA-1 (I just found this out and have started the talks to switch to SHA-2) so I'm wondering if perhaps that's the reason it's failing to bind. 4. The certificate date is valid: Any help with this is greatly appreciated!

I believe it's because it has the builtin Classroom Notebooks feature that a lot of our teachers use.

So that worked for the deployment of the package for Software Center (thanks for that!) but didn't work during the OSD. I checked smsts.log and it reported as the install being successful. I'm starting to think that this is just not possible to deploy during OSD.

Dang, no it doesn't. I saw a post somewhere that says Appx files cannot be installed as system and must be installed to users. I guess I can force install the Software Center version to the devices I need it for. Unless you can think of a different idea? Thanks for the help so far anyhow!

Good question, I grabbed the installer from: https://store.rg-adguard.net/ How would I go about grabbing installer files for the new UWP apps?

My goal here is to be able to deploy this version of OneNote during imaging. We currently have it in Software Center as an available install but I've recently discovered that appx files are not supported during imaging. So I had an idea to package the files and deploy it via Powershell. My script has a single line: Add-AppxPackage -Path ".\Microsoft.Office.OneNote_16001.14326.21452.0_neutral_~_8wekyb3d8bbwe.AppxBundle" -DependencyPath ".\Microsoft.VCLibs.140.00_14.0.32530.0_x64__8wekyb3d8bbwe.Appx" In SCCM, my program has this line: Powershell.exe -ExecutionPolicy Unrestricted -File install.ps1 When I test this in Software Center, it reports as installed but it doesn't actually install. If I launch that script from ccmcache through terminal, the app installs fine. Does anyone know of any reason as to why this won't work?

I created the driver package and added it as an install during the imaging process and it seems to have run successfully (checked the logs) but the driver does not show up in Print Management. I'm guessing it's because the printer is a network one and therefore not attached to the device but I'm wondering if it's possible to put the driver on the device so that the user doesn't have to download/install the driver when they go to add printers the first time. Thanks!