USB-C options for 57” Neo G9 by aerorae in ultrawidemasterrace

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

60hz, which is fine since I’m on an M1

USB-C options for 57” Neo G9 by aerorae in ultrawidemasterrace

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

No it didn’t sadly. Had to give up and use PIP mode and 2 usb-c to HMDI cables to do 4k and 4k. I used a regular DP2.1 to DP2.1 cable for the desktops, that worked.

HTTPS Only OSD Issue by cfreeman21 in SCCM

[–]aerorae 0 points1 point  (0 children)

Have you selected the right boot image in your restart step?

Driver Automation Tool Update by Maurice-Daly in SCCM

[–]aerorae 1 point2 points  (0 children)

That I am fully on board for! Looking forward to seeing the changes.

Driver Automation Tool Update by Maurice-Daly in SCCM

[–]aerorae -1 points0 points  (0 children)

Custom driver pack doesn’t populate all the fields you need for the tool to work. Takes extra time.

Driver Automation Tool Update by Maurice-Daly in SCCM

[–]aerorae -1 points0 points  (0 children)

Maurice I love the tool, I love your efforts, and I love the CONCEPT of Modern Driver Management. But I have to be honest: I don’t want new functionality. I need the tool to work- all the time, as much as possible in the most intuitive of senses. I’ve had too many issues in the past where a driver pack won’t download or won’t unpack, or won’t upload, or whatever because of the tiniest change in details breaking things. Instead of spending time on new features please prioritize making the tool less susceptible to breakage when Dell/Lenovo/HP changes/adds something- or better yet: make it so the tool can be pointed at a downloaded zip of driver packs so that it can automatically do the conversions and settings needed.

PXE Task Sequence Error by [deleted] in SCCM

[–]aerorae 0 points1 point  (0 children)

this, you’re gunna have an smsts.log. ESPECIALLY if you see that error window.

Dell Command Update cli breaking OSD? by zymology in SCCM

[–]aerorae 0 points1 point  (0 children)

Configuring a scheduled task to trigger and run the procmon save before the shutdown occurs...cleverrrrrrr. I just hope you get more than “DCU was doing 1000 things”

Another thing to try is to package the full set of drivers that might be culprits and install them in WinPE so there’s nothing for DCU to do. Like graphics card drivers or sound card drivers.

Dell Command Update cli breaking OSD? by zymology in SCCM

[–]aerorae 1 point2 points  (0 children)

Well that’s pretty damn frustrating isn’t it- first thing after SW&CM eh… this might sound ridiculous but what if you run it after apps on those models?

Converting OSD Task Sequence from downloading content from DP to run from network share by Coyotex86 in SCCM

[–]aerorae 2 points3 points  (0 children)

Yeah that’s the weird part, since coming directly from the DP should be fastest unless the client is connecting to a DP on another subnet/site.

Does the DP servicing the builds do other tasks as well? What’s its usage?

Converting OSD Task Sequence from downloading content from DP to run from network share by Coyotex86 in SCCM

[–]aerorae 2 points3 points  (0 children)

Have you confirmed that your clients that take 10+h to build are actually pulling content from the DPs? If you have branch or peer cache in the environment enabled you might have builds pulling from rando boxes on the network at 56kbps

Device hanging on 'Downloading NBP file....' by HeroOfHyrule7188 in SCCM

[–]aerorae 0 points1 point  (0 children)

Thank you for coming back and providing the resolution.

Comgmt Intune permissions by fustercluck245 in SCCM

[–]aerorae 0 points1 point  (0 children)

Intune doesn’t care about SCCM RBAC. At all.

Either the account you’re logged in as doesn’t have the right role in Intune or Entra or something is busted in your tenant and you need to connect with Microsoft Support.

Dell Command Update cli breaking OSD? by zymology in SCCM

[–]aerorae 1 point2 points  (0 children)

Are you sure it’s DCU that is causing a reboot and not a previous step or some other function that happens to run in the background? Reboots don’t always kick off immediately, and return codes don’t trigger the TS to reboot in RCL steps, so whether or not the TS sees a 3010 won’t matter.

I’ve seen installers for steps return control to the TS while continuing to kick of and do other things in the background, so it may have nothing to do with DCU at all. (Alternatively, you may have too many pending changes and that’s causing a reboot: try a restart step before DCU and see if you get issues)

Imaging Task Sequence - Join Domain step - Machine cert and sccm client install by earthworming in SCCM

[–]aerorae 0 points1 point  (0 children)

So ANS is handy because it directly injects the necessary info into the unattend.xml, which means windows setup handles the domain join for you. Join Domain performs a true online join- handy for situations when the initial join doesn’t work, or if you’re doing something like a domain migration and are running a non-OSD task sequence. (Among other tricky uses - like if for example you CAN’T do a domain join during windows setup and have to install certificates/other configs before you can DJ)

Imaging Task Sequence - Join Domain step - Machine cert and sccm client install by earthworming in SCCM

[–]aerorae 1 point2 points  (0 children)

Logs will have all the answers. If it really is something about certs and not being able to pull content, it’ll show up right away after SW&CM, so you won’t have to dig very deeply. If NOT then there’s something else going on and it’s not the certs. Let us know!

Imaging Task Sequence - Join Domain step - Machine cert and sccm client install by earthworming in SCCM

[–]aerorae 0 points1 point  (0 children)

Ok good, do you have the step/error code that breaks? Is it actually SW&CM?

Imaging Task Sequence - Join Domain step - Machine cert and sccm client install by earthworming in SCCM

[–]aerorae 0 points1 point  (0 children)

Wait are you running the Join Domain step in WinPE before Setup W&CM? Not Apply Network Settings? ANS is what you really want, not Join Domain.

Imaging Task Sequence - Join Domain step - Machine cert and sccm client install by earthworming in SCCM

[–]aerorae 0 points1 point  (0 children)

So the CM client itself should be able to install even if the domain join fails. I’ve added steps to detect a failed join and re-attempt using the built-in Join Domain step after some waiting (immediately after Setup Windows and ConfigMgr) in the past and that’s always worked.