Often times users will setup CS and right along with that will be their SystemAdministrator account giving them full site access, and right after that they will install the single sign-on module allowing them to be authenticated directly through their Active Directory. However, often users will hit a brick wall finding themselves locked out of the site without Administrator access. Generally I recommend two ways to go around that.
1) Temporarily disable SSO by changing the authentication section within the root web.config so that the mode is not equal to Windows, but Forms. Like below:
<authentication mode="Forms">
<forms name=".CommunityServer" protection="All" timeout="60000" loginUrl="login.aspx" slidingExpiration="true" />
</authentication>
Then log back into your control and and run a search on your user account that was created after you logged on through acive directory. Add the SystemAdministrator role to that user, and then reverse your web.config changes to put Windows authentication back into affect. Now your new SSO account will have full System admin rights.
2) Enable Windows Role mapping so that you are automatically given site admin rights after logging in through Active directory with an administrator role from AD. Doing that will require that you alter your communityserver.config file to include those mappings, and then enter your appropriate windows network details and role name. If you don't want to automatically allow all users to obtain the CS admin role off the active directory, you should turn this on just before you log in, then once your account is created remove the windows mapping tags.
