This message was deleted.

I can't speak to MCS, but at my old job we didn't do anything for the join outside of ensuring that the GPO was set to join. There's a built in scheduled task that already handles this, so I'm not sure if your task is missing something that this one is doing.

Well, I didn't remove anything, so the built-in task isn't working either. Looking

"Register domain joined computers as devices" is the GPO setting, in Computer\Windows Components/Device Registration

So, this is the proper method of doing it? Man, i'm so antiquated sometimes.

I don't even know if it's the proper way, to be honest. Just how we always did it in our W10 PVS non-persistent devices.

Thanks man. I will try this one.

Exclude Masterimage from AAD Sync and sync only the OU containing your MCS VM's. Be sure that the Masterimage is unjoined, remove all MCS VMs (including your Masterimage) from Azure AD and run dsregcmd /join on your MCS Clones at startup via BIS-F.

I don't use BIS-F. How is BIS-F doing this function?

I use BIS-F for this. The policy mentioned above if linked at whatever level will then need you to exclude any OUs for syncing (like master OU for sure). So sometimes I run into that policy that is org wide, sometimes not. But then BIS-F doing its thing (leave/join) and also making sure "worksplace join" scheduled task not disabled for reason and it seems to work fine then - this is excluding the whole conversation on the PRT ticket situation with FAS scenarios, but yea, just for hybrid joining, seems to work fine so far.

Yep let bisf doing this stuff for u.