Hello,
I'm am upgrading a SP 2010 Windows Classic Mode Auth to SP 2013 (Using database attach method)
In the first attempt, I attached the Content DB to the Web Application I created via the Central Admin, ignoring the warning I got earlier saying that I was attaching a DB that was intended for a different kind of authentication ( DB is clasic mode, Web App is claims). That didn't go quite well of course; I was able to log in with the Site admin, however the other accounts couldn't log in. I figured out it was the inheritance. For instance, I had another account that belonged to the Owners group but when I checked this particular accounts permissions, it didn't have any.. it wasn't inheriting the permissions from the group it belonged to. I also found out that if I remove the account from the group, and add it again, it'd work just fine.
Second attempt I decided to create a SP 2013 Web app with classic mode via the Power shell (doing that will give you a huge warning about Classic Mode not being supported anymore or thereabouts; it will still crate the web app tho) and attach the DB.
That worked like a charm and the permissions were fine. Pretty much a successful upgrade.
However, I still wanted to obey Microsoft and convert my web application to Claims based just to make sure it was up to standards; so I decided to convert my SP 2013 classic mode auth fully functional web app using Powershell . This
time, after the process was finished, I couldn't log in with any account, not Admin accounts, or Farm account.. normal accounts, nothing was working. I would always get "Sorry, this site hasn't been shared with you"
So, it come down to - Does anybody know whats happening here? Is there another way of making the upgrade to work with claims base?? Is it even worthwhile going through all this to get the claims working or should I just leave what I had????
Pilsen
