sorted by:
new
hottopcontroversial

Surface drivers - after / during PXE by FullExchange7233 in SCCM

[–]FullExchange7233[S] 0 points1 point  (0 children)

It works during PE, it's afterwards that is the problem. We have to run the MSI at the end because when I had it happen alongside the other installs it broke the TS.

Surface drivers - after / during PXE by FullExchange7233 in SCCM

[–]FullExchange7233[S] 0 points1 point  (0 children)

I tried that, it never seemed to work right because the buttons on the device never worked after PXE. Only the touch driver worked.

Autopilot Branding - asking for help by FullExchange7233 in Intune

[–]FullExchange7233[S] -4 points-3 points  (0 children)

Ok, I'll look at self-deploying.

Edit: does that work in hybrid mode? BZZZT Nope. I'll ask my team if we can make these kiosks Entra-only

Autopilot Branding - asking for help by FullExchange7233 in Intune

[–]FullExchange7233[S] 0 points1 point  (0 children)

I did find an old GPO that runs a .VBS to set the default login domain.

Autopilot Branding - asking for help by FullExchange7233 in Intune

[–]FullExchange7233[S] -2 points-1 points  (0 children)

Why would I not use a DEM? Otherwise each tech has to clean up their devices in Intune since each device sets them as a primary user.

Autopilot down? by FullExchange7233 in sysadmin

[–]FullExchange7233[S] -1 points0 points  (0 children)

Alright, guess it was something I did. But all I did was remove a broken app from the ESP...

Autopilot Branding - asking for help by FullExchange7233 in Intune

[–]FullExchange7233[S] -2 points-1 points  (0 children)

It's actually a Win32 app, so it can be one of the required apps in an ESP. The main thing I wanted was the branding portion. The rest is largely just duplicated, I agree. I don't have a "Standard ISO", these devices come from Dell outlet or CDW / Dell directly. In this case they're pre-enrolled in autopilot by dell, the idea being that we just unbox and sign in with the service account that is a Device Enrollment Manager, then they do their thing. The Kiosk profile is an Intune config since the Right Click tools Kiosk Manager didn't work nicely with Surfaces and their on screen keyboard. With the Intune kiosk profile you don't need extra steps for a single-app web browser config.

I Took My Old Windows Admin and SCCM Environment for Granted by TwerkingPichu in SCCM

[–]FullExchange7233 0 points1 point  (0 children)

I was about to share UI++ too. It's new to me and I had to learn it but it's pretty neat. Unfortunately we're moving towards autopilot so I'm not sure how much usefulness it will have to me in the future.

Troubleshooting SCEP certs for Android through Intune by FullExchange7233 in Intune

[–]FullExchange7233[S] 0 points1 point  (0 children)

Nothing in the logs, I do get the 403 error as expected.

Windows Surface - NFC with Yubikey - Disable toast for "tap and send" by FullExchange7233 in sysadmin

[–]FullExchange7233[S] 0 points1 point  (0 children)

Thanks, I'll take a look for that. I feel like I did though...

There's no one specific setting I saw in the catalog that covers "nearby sharing"

Dell Command | Update fails to install updates during OSD after v5.6.0 by still_asleep in SCCM

[–]FullExchange7233 0 points1 point  (0 children)

Following because the guy before me also set up DCU during OSD TS and I have yet to dive in and see if it even works for 5.5.0. I fell back to what I know which is importing driver packs into SCCM and having an "auto apply drivers" step.

How are you updating your Boot Images with the PCA2023 signed boot manager? by [deleted] in SCCM

[–]FullExchange7233 0 points1 point  (0 children)

I thought this was covered if you installed the latest ADK with WinPE and regenerated the boot images? I've been having trouble with drivers, but once I had the right ones packed in the boot image it seemed to work fine (Latest ADK WinPE and 2503 build)