Joel's SharePoint Architecture Blog
SharePoint Server, SharePoint Online and Office 365 Training, Architecture, Administration and Development
by Joel Jeffery
Here’s a map with points of interest culled from Prometic’s site, hosted by those chaps at BatchGeo.com.
View Prometric Sites UK in a full screen map
Although you can book your exams easily enough at www.prometric.com, trying to find out if there’s one near you can be painful, to say the least.
This map shows all of the UK Prometric testing centres that hold Microsoft exams, as at 16 November 2013.
by Joel Jeffery
In this video, I walk through a the start of a scripted installation of SharePoint 2013, including how to install SharePoint 2013 prerequisites from an offline install location, such as a fileshare.
In the first part of this series, we walk through:
The full series of SharePoint 2013 Administration and Configuration videos comprises 9.5 hours of training, and is available here: http://bit.ly/sp13videos for purchase as immediate download or on DVD from $99. Tell your friends!
Your SharePoint setup account needs to have dbcreator and securityadmin server roles on your SQL Server. It also needs to be a local administrator of your SharePoint server to-be.
Your server needs to have both Application Server and Web Server Windows roles. You can achieve this with the PowerShell cmd-let
Add-WindowsFeature Application-Server,Web-Server -IncludeAllSubFeature
If you need to specify a path to the place you installed Windows from – or a new SXS location – you can use the -Source parameter to pass in the new path.
To install the prerequisites from the command line, you can either create a file called prerequisiteinstaller.arguments.txt and copy this into the same folder as your prerequisiteinstaller.exe file extracted from the setup image, or you can pass the following text as arguments directly when you call prerequisiteinstaller.exe from the command line.
/PowerShell:”prerequisiteinstallerfiles\WINDOWS6.1-KB2506143-x64.msu” /NETFX:”prerequisiteinstallerfiles\dotNetFx45_Full_x86_x64.exe” /IDFX:”prerequisiteinstallerfiles\Windows6.1-KB974405-x64.msu” /sqlncli:”prerequisiteinstallerfiles\sqlncli.msi” /Sync:”prerequisiteinstallerfiles\Synchronization.msi” /AppFabric:”prerequisiteinstallerfiles\WindowsServerAppFabricSetup_x64.exe” /IDFX11:”prerequisiteinstallerfiles\MicrosoftIdentityExtensions-64.msi” /MSIPCClient:”prerequisiteinstallerfiles\setup_msipc_x64.msi” /WCFDataServices:”prerequisiteinstallerfiles\WcfDataServices.exe” /KB2671763:”prerequisiteinstallerfiles\AppFabric1.1-RTM-KB2671763-x64-ENU.exe”
SharePoint 2013 makes extensive use of calling web services from the server on which they’re installed – for instance the Claims to Windows Token Service. This will cause the Windows Server Loopback Check to fail, and cause a continual cycle of authentication requests. To avoid this, you need to disable the loopback check. There are two options. You can either disable it for a specific domain name, by editing the BackConnectionHostNames registry value, or by switching it off entirely with the following PowerShell:
New-ItemProperty HKLM:\System\CurrentControlSet\Control\Lsa -Name “DisableLoopbackCheck” -Value “1” -PropertyType dword