u/Bored_at_work_67

We have a frontend app our techs enter the computer name and such that happens after the disk partition steps in our OSD Task Sequence. The computer name gets written to OSDComputerName. I've noticed that on our images that connect to the domain the naming works fine, but for the computers that use the "Apply Network Settings" step that just has "Join a Workgroup" the OSDComputerName doesn't stick, the computer will just be named [SITENAME]-[SERIAL].

What is happening behind the scenes of this network step that requires joining the domain for the OSDComputerName variable to take effect?

Or is the problem with the frontend app? It was proprietary from the MSP that helped us setup our server a while back but there's no support for it.

Thanks!

Can anyone help me understand how Software Updates function within Configuration Manager/the MCM server?

Specifically, I'm trying to figure out why I have a File Explorer folder on my Data drive for WSUS that has new .cab files in it on a weekly basis, even though every ADR I have is set to "No deployment package"

https://preview.redd.it/y9dhs9rqeu8h1.png?width=617&format=png&auto=webp&s=fec9a5806d8cd56b3f39925faaf8146b3aa693c3

The only thing I can think of is that in the Update Services app on the server, in Update Files and Languages, the "Store update files locally on this server" option is checked.

Update Services window

I know for a fact that we did not configure Update Services at all when setting up the server, so my assumption is that these settings are managed by Config Manager? Can I change the setting in here without messing up the updates in MCM?

TL;DR - If the software updates in Config Manager are configured to not download, why do I have ~125GB of .cab files in a WSUS folder (starting in April 2026) on my data drive?

I'm trying to wrap my head around what is probably a pretty simple concept.

I have an application (OG) that has a new update. For various internal reasons, I've been tasked with creating a separate application of the updated software (Young Blood/YB) and deploying it to devices. There shouldn't be a need to uninstall the OG, as the YB installer will do that automatically.

I've already created a deployment type (DType - Plain) that I'm using to install the YB on computers without the OG installed. However...

Caveat: I don't want to run the YB installer if the device is connected to our VPN. So I created a new deployment type (DType - Fancy) that has a very basic PS script to check for the VPN IP address and return $true/$false for the requirement. I also added a dependency for the OG. My thinking was, I only care about the VPN condition if they already have the OG installed.

The question is, if I make the DType - Fancy first priority, if a device in a new deployment doesn't have the OG installed, will DType - Plain run? Or does it automatically fail since the DType - Fancy's conditions weren't met?

Additional question: If I have a required deployment for this application that fails because the device was on the VPN, is there a way for it to automatically retry the deployment to try and catch the device when it's not on the VPN?

I'm sure this will be obvious to most of you, but I wanted to post just it case it helps someone.

The Scenario:
I have an OSD Task Sequence that is deployed to "All Unknown Computers"

I was imaging a few new Dell Pro Max Premium laptops that only have USB-C ports. I used an ethernet to USB-C adapter to connect it to the network for PXE boot.

The first device imaged fine, no issues. I unplug that laptop and plug the new one is. I attempt to PXE boot, but when it tries to Connect to Server it stalls out. The SMSPXE.log file shows the client sending requests, but also showing the "no advertisements" line.

I made no changes to the task sequence or deployment, the laptop model is exactly the same, there shouldn't be anything preventing this new device from connecting to the PXE server.

The Culprit:
The device record for the first computer contained the MAC address of the USB-C to Ethernet adapter. Because I was using the same adapter, it was reading as the same device...

The Solution:
Either, after imaging the first device power it on and connect to a different network and then run a Data Discovery Cycle scan, or Create a device collection looking for the IP range that you're plugged in to and deploy the OSD Task Sequence to that collection alongside the All Unknown Computers.

I hope this helps someone in the future!

Out of a scan of active clients active within the past month I got about 1/5th not reporting any Hardware Scans (~100/500). The rest have last reported scans of 6 months or older. Some are older devices but a lot are relatively new to the environment, if that makes a difference.

Our default and custom client settings have a daily Hardware Inventory scan and Software Inventory scan.

Default Client Settings Hardware Inventory:

• Enable hardware inventory on clients: Yes
• Hardware inventory schedule: Occurs every 1 days
• Maximum random delay (minutes): 240
• Maximum custom MIF file size (kb): 250
• Collect MIF files: None

(Note: The Custom Default settings have the same above, but missing the "Maximum custom MIF file size and Collect MIF files options)

If I do a manual Right-click > Client Notification > Collect Hardware Inventory, it will *sometimes* pull a hardware inventory scan, but not always.

I'm still a novice in the WMI world so I'm not really sure what I'm looking for. For instance, what is and where is the configuration.mof file? I've seen that mentioned some places, but usually just "make sure the file is correct!" which doesn't help me a whole lot. Any tips for specific details I should be on the lookout for in log files or such?

P.S. I know I've been posting to this subreddit frequently lately and I just gotta express my gratitude and appreciation for this community. You guys have definitely helped me dive off the deep end of Config Manager. Thanks!!

What's the general consensus about nesting Task Sequences during OSD? I have multiple computer roles that need different applications, OU placements, etc. Initially I was putting everything in one task sequence but it's starting to get pretty messy. Are there any downsides to nesting task sequences during OSD?

When we migrated servers we did a robocopy of all of our Source data but did not migrate all of our apps and packages. So we have files in our Source folder that we don't need.

What I'd like to do is get a .csv of all of the content locations and then match that to the directory in Powershell. Then I can go in and delete what's not in SCCM without having to go through manually.

I'm barely a powershell novice, but I can't seem to get the xml parsing for SDMPackageXML to work for me. Anyone have any tips?

I'm trying to troubleshoot Modern Driver Management v10 but when I look at the status message for my OSD deployment, the error line for the step is half in (what I assume) Chinese.

https://preview.redd.it/7u6dgn1j6qxg1.png?width=505&format=png&auto=webp&s=12da664b7c276d3b9fdd64a2751079ee776219d3

Does this have to do with the script output, or is it a weird setting in Config Manager?