Note: Idea description updated to correct functionality after further testing. Roaming at registration is fine. Upgrade to roaming afterwards is not for our service desk.
We currently delegate user registration to the service desk and desktop levels.
We would also like to delegate roaming upgrades to the service desk as well.
They can currently enable roaming at registration as long as it is done as a background process. It does generate an error in the local log.nsf "Creation of the sub-directory servername!!roaming\username failed with the following error: You are not authorized to create file system folder"
However, to upgrade an existing person to roaming, the Database Administrators role is required on the Security tab of the server document so the folder can be created. Roaming upgrade fails immediately. The local log.nsf reports "Roaming Tool Error: For user XXX: You are not authorized to create file system folder"
Given all of the other privileges that go along with Database Administrators, it would be great if either the create folder privilege only could be granted, and more specifically to the roaming folder OR if the privilege were not needed at all and adminp could create the folder in the background to complete the roaming upgrade for existing people.