Instead you use an optimized local or mandatory profile (preferably use VMware OSOT) and save/restore only those settings you need, which prevents having the issues described for a roaming profile. But the whole concept of DEM regarding profile management is to not have a roaming profile (which may result in profile bloat, having to reset/delete complete profiles, slow logon/logoff, etc.). Regarding 'the same functionality of roaming profile/NTuser.dat', not sure what you mean with that. I assume you have your DEM infra/config in place (config share, profiles share, user gpo, DEM console, etc.) and all works. Not sure if I understand your question, but maybe we can start from the beginning. Let me know if you have any other questions. Regarding OneDrive, here's an article that may help you -> VDI Onedrive Windows 10. This prevents Active Setup from being executed every time a user logs on. In that case I choose to add the Active Setup config file template in DEM to save the changes made by Active Setup. I normally just remove them, unless really required for something. Instead, I choose what needs to run for the user during/after logon by using DEM. I also remove all run and run once stuff on both machine and user level.

This doesn't necessarily speed up the logon process, but gives you and the user additional info while logging on and in my experience seems faster for the user, instead of just showing 'Preparing Windows'. After a while you can disable roaming profiles.īy default I also enable the 'Display highly detailed status messages' GPO setting ->. This way the roaming profile is used and settings may be written to both DEM profile archives (ZIP) and the roaming profile. Migration from roaming profile -> It is possible to leave roaming profiles enabled (side by side with DEM) when you want to migrate to DEM. If your machines don't fully reset after logoff, but you want to have the local profile removed after logoff, you can use the DEM Advanced ADMX setting 'Remove local profile at logoff' -> Ĭlean start with DEM -> Don't forget to disable roaming profiles for the users logging on to the desktops that use DEM and must not use the roaming profile-> Techland: How to: Disable Roaming Profiles You can use them in both non-persistent and persistent environments. Each user logon will use this default local profile. I use OSOT to optimize the local default profile in the 'master image'. It is perfectly possible to use an optimized local profile. Yes indeed, I mean an optimized local default profile in the master image.

Where is ntuser dat