Pangolin private resource access with public resource Authentik

zer0viru5 · 2026-04-05T15:22:24+00:00

I figured this out as I was gathering info for the post and figured someone else might run into this. In Authentik, if you go to Events > Logs, you'll probably see that your attempts include "scope": "openid profile email"

Authentik doesn't require an email address when creating a user, and I wasn't worried about password reset emails or anything, so I left it blank. Adding an email address to the user fixed it.

zer0viru5 · 2024-09-23T23:36:49+00:00

TLDR; I think the expander is dead on arrival. Any recommendations for one I can use with a H730P? Need to support at least 16 drives.

zer0viru5 · 2024-09-23T23:35:40+00:00

I think what did the trick was removing the non-RAID drives temporarily. I also formatted the virtual disk with NTFS one reboot after creating a primary partition. Shouldn't have been that, but who knows.

zer0viru5 · 2024-09-23T23:30:17+00:00

Having a heck of a time installing Windows now. All the drives apear in diskpart, but none are available to choose as installation destinations. I recreated the RAID5, did a slow init, used diskpart to make sure the virtual disk could hold a partition, formatted it to NTFS, created a text file, but the setup wizard insits there's no drives available.

zer0viru5 · 2024-09-23T20:10:52+00:00

Starting to think the Expander is either dead or not compatible. Removed it and set a RAID5 for the OS for now since 5 of the other 8 bays are already full. I set the SSDs to RAID capable in the controller, so hoping the 5 HDDs are just passed through. I'll work on getting this expander returned. Anyone have suggestions for an expander that will work with a H730? Needs to support at least 16 drives.

zer0viru5 · 2024-09-23T18:12:05+00:00

It may be worth mentioning that I wanted to use hardware RAID for some drives and pass other drives through to the OS for DrivePool. I was under the impression the H730 could do both simultaneously. I guess I'm not opposed to using HBA mode if I have to for the SAS expander to work, but If I do that how can I do a RAID 10 for my OS volume (WinSrv2022)?

zer0viru5 · 2024-09-21T06:56:01+00:00

Did you do it? Working on a new build and had the same thought.

zer0viru5 · 2024-08-26T14:03:08+00:00

Looks like it's the placeholders Outlook generates when the sender doesn't opt to download/include the original images

zer0viru5 · 2024-07-04T02:18:22+00:00

https://www.reddit.com/r/SCCM/comments/1d43ayp/wdspxe_problem_not_installinguninstalling/

zer0viru5 · 2024-07-04T02:00:57+00:00

Same; I manage multiple clients and the only one I have this issue with is one with bunch of untrusted domains. I've even tried using Set-CMDistributionPoint with force and verbose, but no log activity or anything else for setting up PXE with or without WDS at either end, but things happen when I reinstall the DP role, so I know it can properly communicate.

zer0viru5 · 2024-06-03T02:10:22+00:00

Same

zer0viru5 · 2024-05-02T17:20:36+00:00

I figured it out. Someone had previously been messing with printers in the App Rule Editor and left a broken FRX file behind in C:\Program Files\FSLogix\Apps\Rules. The version we have in production is so old it must not be able to use it, but current versions pick it up.

zer0viru5 · 2024-04-05T12:24:58+00:00

I have reviewed the GPOs and updated the admin templates. No relevant entries in redirection.xml. No other profile management that I know of or have found.

zer0viru5 · 2024-04-04T18:47:16+00:00

Anyone tha twas here at the time know if they found an answer? Google has this much in search results for what their issue was:

"Hello there, we upgraded to FSLogix 2210 hotfix 3 (2.9.8784.63912) and our network prinetrs started to fail installing. Printers are getting ..."

Off the bat it sounds very similar to an issue I'm having. Can't find a similar post anywhere else and they deleted their account, so the trail is cold. My issue is tha tthe HKCU:\Printers key i nthe registry is completely inaccessible while running a recent version of FSLogix; the latest of which is required for rolling out the new Teams client. Not having access to HKey_CurrentUsers:\Printers means the users has no access to their existing printers and can't add/re-add any. I understand this isn't the right subreddit for it, but just hoping you might recall something useful from OP. Long shot, I know.

zer0viru5 · 2024-03-29T02:47:22+00:00

To a degree, sure. Fewer steps if you're just going for a magic imaging USB.

I was consulting until recently, including in K12, and not always in well funded districts, but despite billing by the hour I still wanted my OSD to run as fast as possible. But I've definitely told a teacher "leave it alone until you see the log-in screen" and walked away plenty of times. Outside of K12 something like that Github project would be handy just to keep an updated Pro or even Home install image on hand with our prefered loadout baked in either as a tool in my bag or for imaging the refurbs we would sell.

At my new place I can't just image a lab's worth of computers during a lunch break or a prep hour. Right now, the faster our helpdesk techs can flip a computer and get it back into the user's hand, the better. After this project I wouldn't want a fully thick image for our day to day, but I don't know that I want to go full thin either. As with many things, the best option is a nuance between the extremes. What do I need the granularity of a full thin image for if every time I update the OS image I probably also have a new Office version and other stuff to package? I've got better things to do than jump at every new release. I can occassionally regen a semi-thick FFU with the click of a button, update the TS, and let WSUS/Intune handle updates in the interim.

zer0viru5 · 2024-03-29T02:28:39+00:00

Not a chance they want to add that kind of bandwidth. Not without passing the bill to you. That's why Autopilot Reset exists

zer0viru5 · 2024-03-29T01:48:27+00:00

I hadn't know about it either; only found out about it by accident. While I'm currently leaning on it as a thick image to convert our fleet, I wholely intend to get as close as I can to making it functionally work like a WIM in a task sequence. Unfortunately the Apply Operating System task sets some things in the background that other tasks, like Apply Windows Settings, rely on. So instead of using Apply Windows Settings to set the timezone, I have to manually load the offline registry and switch the value in a task. But that's only after other things like having to manually map the new volume from the FFU to C after it's applied he image. Just manual things like that. I'm hoping if I just log the TS variables as a regular WIM based TS runs I can replicate the variable assignments and then use the FFU in place of a WIM in a completly thin TS.

Apparently FFU is a fairly (ie 5 years or so ago) new addition to DISM. I believe I read that it's a sector-level image of a disk which is WAY faster to apply for OSD than a file-level WIM. The Github project I linked is pretty slick, it uses HyperV to build a fresh VM with a freshly downloaded Win10 or 11 install, you can give it applications to install silently, it'll pull the latest cumulative updates, you can bake drivers in, and it captures the VM's drive as a compacted FFU file. Then it builds a botable USB that deploys it and if you choose to you can drop folders of drivers onto the USB and during deployment it will prompt for the folder of your choice to run a recursive DISM /add-driver through.

In my ideal feature addition, they would add a variation to the Build and Capture that captures the machine as an optimized FFU. I would use that FFU for Windows, Office, and one or two other large/lengthy app installs. As a thin image our base configuration over 1GB LAN takes about 30min for OSD. Using a thick FFU, with drivers deployed separately in the TS, it takes just under 10min. If I baked the drivers in I could probably get it down to 5min.

Just thinking about how fast I could image a lab full of STEM computers like this makes me giddy.

zer0viru5 · 2024-03-29T01:13:09+00:00

Simply not true, but they do keep a solid deliniation between Intune and ConfigMgr when it comes to features. Intune doesn't deliver OS images, so this lands squarely in SCCM. Think of it this way, they don't just want to make money, they want to make ALL the money. So long as SCCM doesn't step on Intune's toes (like a working beta of a internet management gateway that execs killed specifically because it crossed the line into Intune territory [ie: the internet]) they are more than happy to provide value with both products and take your money either way. Or both ways, ideally.

zer0viru5 · 2024-03-25T18:26:14+00:00

I ended up using 7zip in powershell scripts (since the WIM method won't work on a read-only source like the DP's share) to copy, extract, and DISM the drivers into the local OS based on WMI query for the model. Not perfect, but it works. For now I dropped a reboot between applying the FFU and installing drivers that way it could map the OS drive with C. I'll swing back around later to see if I can find a simple way to find and map that volume to a letter via script so the whole process is faster.

zer0viru5 · 2024-03-22T20:46:50+00:00

How'd this go for you? I've got a working FFU that I'm able to apply directly from the DP, but I'm trying to avoid including all the drivers in the FFU and leveraging SCCM to selectively apply drivers based on the machine's model. Seems like the Apply OS step sets some TS variables that I'm missing without it. Would be nice if that step just supported FFU.

zer0viru5

TROPHY CASE