ProfessorMS DHCP DataSouces need Explicit Sessions
I've posted about it in the past, but using remote powershell in a windows environment with an implicit session causes a profile to be loaded even if you tell it not to do so. These all need to be done using "-session" rather than "-computername" to target the remote entity. This will allow setting the no profile flag in a way that actually has the expected behavior.
This has caused issues in the past overloading the mount request queue and breaking profile loads for normal users causing them to receive temp profiles rather than their own. In this case, luckily, it doesn't tend to target systems that users would be logging into... but this is the mechanism that allowed me to help uncover a thirty year old buffer overflow bug with windows. (MS didn't give me a bug bounty :( ).
I'll look up the thread I had here and link it in a follow on comment.
