Alternatively, it would be fine as well if the server profile would be deleted immediately and the update process be prevented once.Or to put it differently: How can we ensure a specific user will receive a new, clean profile when he logs himself in the regkey, it is a per-machine configuration setting valid for all users logging on to your terminal servers, and thus probably undesirable.I support a product that doesn't work with roaming profiles.
I know it's a really simple question but how can I verify if an end user is using a roaming profile in Windows Vista?
I should clarify -- I don't manage the user's network...
Possible causes of this error include network problems or insufficient security rights.
If this problem persists, contact your network administrator.
The workstations gradually update to this year W10 (1607) - at the moment 7 of 20 are updated - and immediately after that they stop synchronize user roaming profiles with the server.