ConfigMgr Frontline

When configuring an Windows Client and Server CI, be careful when choosing the OS that will assess the CI for compliance! Note that for Windows Server 2016 and Windows Server 2019 the phrasing says “and higher” after them. What this means is if you choose Windows Server 2016, the CI will apply to *both* Server 2016 *and* Server 2019 (even if you don’t choose “Windows Server 2019”)! As you can imagine, this can cause problems if you are wanting the CI to only apply to Server 2016! You can get around this by using the option “ Specify the version of Windows manually ”. However, that option does not appear if you choose “ This configuration item contains application settings ” under “ Windows Desktops and Servers (custom) ”. The only thing you can choose is “ This application runs only on computers that have 64-bit hardware ”. If you do not choose the "This configuration item contains application settings" you could then utilize a script to make sure it only appli...

1.) Login to the machine with the local administrator account or connect remotely from another server. 2.) Delete the profile for the user that's having the problem, i.e. C:\Users\User01 3.) Run Regedit, and remove the profile from HKLM>Software>Microsoft>Windows NT>CurrentVersion>Profile List>(SID) (you can right click on Profile List and do a search for the user name, i.e. User01. 4.) Once found delete the entire KEY for the user. 5.) Double check to ensure it's removed from System Properties>Advanced System Settings>Advanced TAB>User Profiles (Settings...) button> If you see the user in there, delete it too. 6.) Logoff as Local Admin and reboot. (Reboot not required but you may want to to be sure). 7.) Login with domain username.