24H2 OSDComputerName not applying during task sequence

[Shaun_Dark_Lord]

Hi All

 

One of our schools has a very old SCCM server that is now causing a headache.

 

W11 21H2 task sequence had been setup by a previous tech. This seems to be running fine.

 

24H2 is required for some new clients. I've done the normal build and capture, copied the 21H2 TS and replaced the Windows image with the newly created 24H2.

 

The main issue is that the clients are not renaming to the OSDComputerName value - They're just sticking with the randomly generated MINIT one.

 

Other issues include a random prompt half way through the TS to ask why the client just rebooted (the TS told you to), and all the W11 bloat that we were getting rid of is remaining.

 

Any ideas on the naming issue? If we can get past that, the other bits can probably be figured out.

[mikes]

Have you upgraded SCCM to the latest version? we were also running a real old SCCM version but upgraded it via the sccm console until we got to the latest version now our 24H2 builds seem to be working fine including picking up the right name. I didn't set up the task sequence however our contractor did it so I can't say too much about how it was made - looks like they just captured a totally stock Win 11 24H2 ISO to me.

 

getting rid of the bloat was annoying - we used a powershell script in the task sequence using e.g. "Get-AppXPackage *BingNews* | Remove-AppXPackage -AllUsers" to get rid of most of the stuff we didn't want like the mobile sync stuff. But other users say they deny access rather than remove these packages (e.g. getting rid of the game overlay/xbox package made minecraft/gamemaker throw up errors for us)

[Shaun_Dark_Lord]

Yes - Updated to the latest (2409), and rebuilt the boot images with the latest ADK.