danflynn

What we ending up doing for WVD Multi-Session hosts was putting the access group into the local Guest group on the host with a group policy (Computer Configuration\Preferences\Control Panel Settings\Local Users and Groups\). What this does is when the user logs out the data in the user profile is removed from the host basically making it a non-persistent profile. The one downside we did find with this is that all Microsoft Store based apps don't work as they can't be opened with a Guest use. The big one was calculator had to find a legacy calculator app (https://winaero.com/get-calculator-from-windows-8-and-windows-7-in-windows-10/). Could use a logoff script to delete the downloads that runs as the user but they would have access to delete their own downloads

We use the User Configuration/Preferences/Control Panel Settings for deploying printers and with using the FQDN of the print server (server.domain.edu) and have no issues with hundreds of printers GPPs and targeting groups, as others said you do need loopback processing if you are applying the GP to the computer not the user objects in AD. For the default printer that might be the Let Windows Manage Default Printer. GPP User Configuration\Administrative Templates\Control Panel\Printers\Turn off Windows default printer management Registry Key HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows LegacyDefaultPrinterMode D-Word Value = 0 https://www.tenforums.com/tutorials/26138-turn-off-let-windows-10-manage-default-printer.html https://answers.microsoft.com/en-us/windows/forum/windows_10-other_settings-winpc/group-policy-disable-let-windows-manage-my-default/789ff603-67a8-4247-bedf-bf5a6ea327a5

For the Device Based Activation you have to assign the license in Office 365 Admin portal (Now Microsoft 365 admin center (https://admin.microsoft.com/Adminportal/Home?source=applauncher#/homepage) to a Azure AD group and the device object be it Azure Hybrid or Full Azure Join has to be in that group. Note there can only be 1 group for this assignment. If you are using User authentication and after they log into an Office 365 app and still get requires activation then they most likely they have a A1 and not a A3/5 license. An A3/5 license is required for the full Office 365 apps A1 only gives you the web apps. The assigned user license is checked in the Office 365 Admin portal

I figured that just wanted to let the OP know that might also be the cause of their issue. I had only added .Net 3.5 after the 1803 update and forgot about it would figure MDT would just skip the package if it wasn't for that version. Do you know if you can load multiple .Net packages and it will just pick the correct one? Since we have a LTSB 2016 image that needs it and also a 1803/1809 image that needs it.

I was also getting the 0x80004005 error and I finally figured it out after building a new Deployment share. Check your Packages folder in MDT disable all of the packages in there and see if it runs. I had .Net 3.5 enabled.