UPN has broken PC deployment (I think)

[mikemcsharry]

Hello,

I use SCCM - latest reelase etc on a 2012R2 box and use task Sequence to build machines.

All was working fine until I added a UPN to the domain (reason is that the on premises domain was set as school.county.sch.uk and should have been school.city.sch.uk and the school email already in 365.

Since then, no Task Sequence builds have worked. i don't think I changed anything else since between a success and a failure.

Another thing I noticed is that multicasting became painfully slow.

The task sequences have a catch at the end to write the logs back to the server, that also failed.

The 'built' PC actaullay boots up, but nothing I try lets me log into it. It hasn't registered in dns, ad or config manager

 

What I've tried.

Turned off multicast - back to previous speeds

Applied last months patches and rebooted - no difference

Made a new wim (used dism to grab just the one I wanted) - lot smaller, so faster, so quicker to fail.

I can happily deploy software etc from Config Manager, but can't build any new machines.

 

Sure I spotted something one day on this, but can't find it anywhere.

 

Does anyone have any ideas?

Ta...

 

EDIT - oddest thing. Went to the PC about an hour later to try again, to discover it was sat there - domain joined.It is joined to the 'initial' (county) domain, not the extra UPN (city) domain. Also config manager not installed, part of boot.

Edited December 9, 2020 by mikemcsharry

[mikemcsharry]

Hello,

I use SCCM - latest reelase etc on a 2012R2 box and use task Sequence to build machines.

All was working fine until I added a UPN to the domain (reason is that the on premises domain was set as school.county.sch.uk and should have been school.city.sch.uk and the school email already in 365.

Since then, no Task Sequence builds have worked. i don't think I changed anything else since between a success and a failure.

Another thing I noticed is that multicasting became painfully slow.

The task sequences have a catch at the end to write the logs back to the server, that also failed.

The 'built' PC actaullay boots up, but nothing I try lets me log into it. It hasn't registered in dns, ad or config manager

 

What I've tried.

Turned off multicast - back to previous speeds

Applied last months patches and rebooted - no difference

Made a new wim (used dism to grab just the one I wanted) - lot smaller, so faster, so quicker to fail.

I can happily deploy software etc from Config Manager, but can't build any new machines.

 

Sure I spotted something one day on this, but can't find it anywhere.

 

Does anyone have any ideas?

Ta...

 

EDIT - oddest thing. Went to the PC about an hour later to try again, to discover it was sat there - domain joined.It is joined to the 'initial' (county) domain, not the extra UPN (city) domain. Also config manager not installed, part of boot.

 

Another update. I’ve rebooted and patched the SCCM server a few times since the original post and now things seem to be working (but not for all builds)