LUSH-PEDIA

Obtain the “SharePoint Root Authority” certificate as a physical (.cer) file  a) Launch the SharePoint 2010 PowerShell window as Administrator b) $rootCert = (Get-SPCertificateAuthority).RootCertificate c) $rootCert.Export("Cert") | Set-Content C:\SharePointRootAuthority.cer -Encoding byte Note: The  .cer  file exported in this step can be used on other servers in the farm without having to run the Powershell commands again. 2. Import the “SharePoint Root Authority” certificate to the Trusted Root Certification store a) Start > Run > MMC > Enter b) File > Add/Remove Snap-in c) Certificates > Add > Computer account > Next > Local computer > Finish > OK d) Expand Certificates (Local Computer), expand Trusted Root Certification Authorities e) Right-click Certificates > All tasks > Import f) Next > Browse > navigate to and select C:\SharePointRootAuthority.cer > Open > Next > Next > Finish > OK ht...

stsadm.exe –o activatefeature –url <site collection url> -filename ViewFormPagesLockdown This will enable the lockdown feature on your site collection. If you already had anonymous access enabled, you'll need to go disable it, then enable it again. Go to the _layouts/setanon.aspx page, switch anonymous access off, click OK, then go back and set it to on, click OK. You should now get an authentication prompt when you try to navigate to a forms page http://blogs.msdn.com/b/ecm/archive/2007/05/12/anonymous-users-forms-pages-and-the-lockdown-feature.aspx  

Install 32-bit Reporting Services on a 64-bit Computer

ERROR: TITLE: Microsoft SQL Server Management Studio ------------------------------ Restore failed for Server 'DBSERVER'.  (Microsoft.SqlServer.Smo) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00& EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Restore+Server&LinkId=20476 An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo) The backup set holds a backup of a database other than the existing 'DB' database. RESTORE DATABASE is terminating abnormally. (Microsoft SQL Server, Error: 3154) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=3154&LinkId=20476 SOLUTION Create a database and then try this command: RESTORE DATABASE  AdventureWorks FROM DISK = 'C:\ BackupAdventureworks ...

I> Create or Convert existing web applications to use Claims Based Authentication II> Create User IDs in SQL Database III> Modify web.config file IV> Give Permissions to users present in SQL database Create or Convert existing web applications to use Claims Based Authentication Note: -  Web Application has to be created from the Central Administration console or PowerShell, however it should be using  Claims Based Authentication . A. Creating web application using Central administration Open Central Administration Console. Click on Manage Web application Under Application Management. Click on new on the Ribbon. Chose Claims based Authentication From the top of the page. Choose the port no for the web application. Click on  Enable Forms Based Authentication (FBA)  Under Claims Authentication Types. Windows Authentication is enabled by default and if you dont need windows authentication then you need to remove the check...

$App = get-spwebapplication “URL” $app.useclaimsauthentication = “True” $app.Update() Example:- $App = get-spwebapplication “http://sp1:8000” $app.useclaimsauthentication = “True” $app.Update()

Solution 1 :    web.config <PeoplePickerWildcards>       <clear />       <add key="fbaMembers" value="%" />      <!--added by umair-->       <add key="AspNetSqlMembershipProvider" value="%" /> </PeoplePickerWildcards> Solution 2: web.config <PeoplePickerWildcards>       <clear />       <add key="membership provider" value="%" />       <add key="role provider" value="%" />       <add key="AspNetSqlMembershipProvider" value="%" /> </PeoplePickerWildcards> Solution 3: Set db_owner permissions for AppPool account in provider database.