-
Title
Is it possible to migrate from Schemaless mode to R2 mode? -
Description
Is it possible to migrate from Schemaless mode to R2 mode?
-
Resolution
Yes it is possible, however migrating from schemaless to R2 schema is not easy as each user will need to be migrated to the R2 attributes. This could be done with a powershell script. We recommend our Professional Services team assist if this is being considered. For information on how to contact them please visit https://support.oneidentity.com/professional-services-product-select
When switching from Schemaless to R2 in the Control Center this only changes which attributes QAS clients and management tools use. All of the previously-enabled users will suddenly be Unix disabled because the R2 attributes have no values. You can use Powershell to migrate the attributes from Schemaless to R2. There is a –Schema parameter that you can pass to Set-QasUnixUser/Group which will override the configured schema allowing you to copy attributes from one schema configuration to another.
For example, with Schemaless set as the current schema in Control Center:$r2 = Get-QasSchemaDefinition | where {$_.Id –eq "Windows 2003 R2"}Get-QasUnixUser <username> | Set-QasUnixUser –Schema $r2
Get-QasUnixGroup <groupname> | Set-QasUnixGroup –Schema $r2
That should copy the Unix attributes from Schemaless to R2 then you can make the switch in Control Center.
The default R2 schema is
Id : Windows 2003 R2
UserName : sAMAccountName
UidNumber : uidNumber
PrimaryGidNumber : gidNumber
Gecos : gecos
HomeDirectory : unixHomeDirectory
LoginShell : loginShell
GroupName : sAMAccountName
GidNumber : gidNumber
If you wanted to use different mappings you can do the following. In the example, we are use uid instead of samaccountname.
$custom = Get-QasSchemaDefinition | where {$_.Id -eq "Windows 2003 R2"}
$custom.UserName = "uid"
Get-QasUnixUser <username> | Set-QasUnixUser –Schema $custom
echo $custom
Id : Custom
UserName : uid
UidNumber : uidNumber
PrimaryGidNumber : gidNumber
Gecos : gecos
HomeDirectory : unixHomeDirectory
LoginShell : loginShell
GroupName : sAMAccountName
GidNumber : gidNumber