Attaching a Content Database from a Classic Web Application to a Claims-enabled Web Application does not automatically convert the users contained within that Content Database from Classic to Claims. When you run Test-SPContentDatabase, it performs quite a few tests against the target Content Database, including a test to check if users within the UserInfo table are Claims-enabled on a Claims-enabled Web Application (and vice versa). [crayon-5479e586b68c3262094330/] When a Test-SPContentDatabase is executed (without additional switches), it runs the following T-SQL against the UserInfo table of the Content Database being tested: [crayon-5479e586b68dc482096796/] If it returns any results, the message above will be displayed. So what is the solution, here? Just migrate the users… [crayon-5479e586b68f5525880571/] This will migrate any valid users within the database from Classic to Claims. Running Test-SPContentDatabase should now succeed without any warning message, unless… Any Site Collection Administrator has been deleted from Active Directory and cannot be converted! In that case, identify all Site Collection Administrators in the Content Database (e.g. [crayon-5479e586b68ff087404048-i/]), remove them from the Site Collection Administrators and as an optional step, delete them from the Site Collection. This way, they will no longer be marked as [crayon-5479e586b6907328386092-i/] and will not fulfill the requirements of the Test-SPContentDatabase query on the UserInfo table.
The post Test-SPContentDatabase Classic to Claims Conversion appeared first on Nauplius.
