AD FS authentication fails when using Chrome

You can circumvent this problem by switching off ‘Extended Protection’ for the adfs/ls web application.

To turn Extended Protection off:

1. On the AD FS server, launch IIS Manager.

2. On the left side tree view, access Sites -> Default Web Site -> adfs -> ls.

3. Once you have selected the “/adfs/ls” folder, double-click the Authentication icon, then right-click Windows Authentication and select Advanced Settings.

4. On the Advanced Settings dialog, choose Off for Extended Protection.

Done!

Types of Web Pages in SharePoint 2010

Although SharePoint 2010 gives you a lot of helpful tools to work with content, the ability to communicate effectively with your team, starting with a customizable home page, pulls everything together. Using web pages and Web Parts is how you arrange and present information in a collaboration site. Team sites use wiki pages to make it easy for everyone on your team to share information.

Type 1: Publishing Page
Default Location: Pages library
Typical Usage Scenario: Complete control over look and feel; more granular content management.

Type 2: Web Part Page
Default Location: None; can reside in any library or folder
Typical Usage Scenario: To display Web Parts; no content management requirement.

Type 3: Wiki Page
Default Location: Site Pages
Typical Usage Scenario: Pages that look and function like the home page.

Unable to install Windows 8 – Error Code 0x0000005D

Issue:
When you try to install Windows 8 on a Pentium 4 or lower computer, but upon boot, you are getting the following error message:
Your PC needs to restart
Please hold down the power button
Error Code 0x0000005D
Parameters
0x030F0401
0x756E6547
0x49656E69
0x6C65746E

Description:
Unlike Windows 7 and its predecessors, Windows 8 is not compatible with all models of the Pentium 4 processor.

This is due to the fact that Windows 8 requires a processor compatible with the following functions: SSE2, PAE and NX bit. All Pentium 4 are compatible with SSE2 and EAP: the problem may come from the NX bit.

Exporting a SharePoint list in SharePoint 2010

To export a list from a SharePoint site you can follow the steps below:

• Ensure that the user account performing the process is a member of the farm administrator group.
• In Central Administration, on the Home page, click Backup and Restore on the left hand menu.
• On the Backup and Restore page, in the Granular Backup section, click on the Export a site or list option.
• On the Site Or List Export page, select the appropriate web application, site collection and list that you want to export.
• In the File location section enter the UNC path of the export folder. This should be a share on either the server or another network location.
• If the file already exists and you want to overwrite this, then select the Overwrite existing file check box.
• Select the Export full security check box if you want to export all the security and permissions settings with the select list or library.
• Click on the Start Export button when you are happy with the selected options.

Done!

How to select a federation service name?

The Federation Service Name must never equal any machine name in the Active Directory forest when you are deploying a AD FS 2.0 farm. This requirement is in place to allow Kerberos authentication to succeed for your Federation Service.

Scenario 1: Non-working scenario
The Federation Service Name is ADFS.POCOFFICE365.COM and the host names of the two Federation Servers in your farm are: ADFS.POCOFFICE365.COM and ADFS2.POCOFFICE365.COM. Kerberos authentication will fail because your AD FS 2.0 service account needs to have the following servicePrincipalName (SPN) registered: HOST/ADFS.POCOFFICE365.COM. Since you already have a computer in Active Directory named ADFS.POCOFFICE365.COM, the HOST/ADFS.POCOFFICE365.COM SPN is already registered to this computer account, which means that registering this SPN to your AD FS 2.0 service account is not an option.

Scenario 2: Working scenario
The Federation Service Name is SSO.POCOFFICE365.COM and the host names of the two Federation Servers in your farm are: ADFS.POCOFFICE365.COM and ADFS2.POCOFFICE365.COM. Kerberos authentication can succeed since your AD FS 2.0 service account can have the SPN HOST/SSO.POCOFFICE365.COM registered to it since neither the AD FS 2.0 servers nor any other account in the Active Directory forest have this SPN registered.

SharePoint 2010 – “Installation of this product is not permitted on this computer. Please contact your network administrator for more details.”

If you have the following entry in the register of the target server:

HKLM\Software\Policies\Microsoft\Shared Tools\Web Server Extensions\14.0\ SharePoint\DWORD DisableInstall

DWORD DisableInstall=00000001

Users who try to install SharePoint 2010 on that server will receive the following error message:

“SharePoint installation is blocked in your organization. Please contact your network administrator for more details.”

You will need to set

DWORD DisableInstall=00000000

to allow installation of SharePoint 2010.

Part 2 of 2: Upgrading a Report Server database used by older versions of Team Foundation Server

If you can take the report server offline, you can detach the databases to move them to the SQL Server instance you want to use. This approach preserves permissions in the databases. If you are using a SQL Server 2012 database, you must move it to another SQL Server 2012 instance. After you move the databases, you must reconfigure the report server connection to the report server database. If you are running a scale-out deployment, you must reconfigure the report server database connection for each report server in the deployment.

Use the following steps to move the databases:

1. Backup the encryption keys for the report server database you want to move. You can use the Reporting Services Configuration tool backup the keys.

2. Stop the Report Server service. You can use the Reporting Services Configuration tool to stop the service.

3. Start SQL Server Management Studio and open a connection to the SQL Server instance that hosts the report server databases.

4. Right-click the report server database, point to Tasks, and click Detach. Repeat this step for the report server temporary database.

5. Copy or move the .mdf and .ldf files to the Data folder of the SQL Server instance you want to use. Because you are moving two databases, make sure that you move or copy all four files.

6. In Management Studio, open a connection to the new SQL Server instance that will host the report server databases.

7. Right-click the Databases node, and then click Attach.

8. Click Add to select the report server database .mdf and .ldf files that you want to attach. Repeat this step for the report server temporary database.

9. After the databases are attached, verify that the RSExecRole is a database role in the report server database and temporary database. RSExecRole must have select, insert, update, delete, and reference permissions on the report server database tables, and execute permissions on the stored procedures. For more information, see Create the RSExecRole.

10. Start the Reporting Services Configuration tool and open a connection to the report server.

11. On the Database page, select the new SQL Server instance, and then click Connect.

12. Select the report server database that you just moved, and then click Apply.

13. On the Encryption Keys page, click Restore. Specify the file that contains the backup copy of the keys and the password to unlock the file.

14. Restart the Report Server service.