Reported to engineering.
Create new user with
the login name "a&bâ.
Management Utility/User Management/Search.
a&b user is present, but you canât enable this
Potential work-around for containers:
Option 1 - Temporarily move the users on the affect
OU to a container without an ampersand character, enable the user
for iFolder and then move them back to the original OU. This will
allow you to enable the user for iFolder; the user can also
successfully login via the iFolder Client after moving them back to
the OU containing the ampersand character. It would appear the only
limitation with users in OUs containing '&' in the name is when
actually managing the user objects (enabling/disabling the user,
setting disk quotas, etc..)
Option 2- Enable the user's manually via Console One. Go to
the 'Other' tab for each user object and implicitly add a new
ObjectClass called 'iFolderUser' (without the
quotes... please note the case on iFolderUser). Next, create the'iFolderServerName' attribute with either an'*' (asterisk) or'iFolder_Server01;' as the value (without the
quotes... please note the case).
Formerly known as TID# 10084859