Unboxing SharePoint Server 2013 Preview

By -
Although SharePoint Foundation/Server Preview 2013 has been out for quite some time now, I have decided to make a clean install and share the results.

Software Requirements
Requirements are Windows Server 2008 R2 w/ SP1 or Windows Server 2012 RC.
Things may get hairy if the wrong version is used, so we should make sure that doesn't happen:
- Get Windows 2008 Server R2 (not R1/RTM) w/ SP1, 64 bit, English, Standard/Enterprise/Data Center
- Don't use the "core" versions, which seem to be minimalist setups, not for "hands-on"
- Don't use checked/debug builds. I did and I kept getting "update is not applicable to your computer"
- Avoid other versions (Web), builds (x86) and languages
- Avoid trial versions, that when burned may ask for CD/DVD drivers and get stuck on the install process

Install Procedure
If you have sucessully downloaded and burned a working copy of W2008 Server R2 x64, and SP1 is installed (ootb or manual install), just enable Internet access and the prerequisites should install fine:
- Enable the Wireless LAN Service feature so that your WIFI links work.
- Activate the OS
- Run the Prerequisite checker/installer (should ask for a single restart after the .NET Framework 4.5)

- Actually install SharePoint Server 2013
- Run the configuration wizard (here comes trouble. running the below will fix future issues)

Issue #1 - substatus error
Run under SharePoint Management Shell,
psconfig.exe -cmd Configdb create SkipRegisterAsDistributedCacheHost


Issue #2 - sddl error
Run under SharePoint Management Shell,
$SearchServ = Get-Credential [Your Search Account]
New-SPManagedAccount -Credential $SearchServ


- Even if the configuration still fails on "creating sample data", both the Central Admin and the port 80 sites will be working correctly.

Now we can:
- Add the sites to the IE Local Intranet zone list to avoid password request on the host machine
- Change the user display name

Comments

Post a Comment

Popular posts from this blog

Breaking down document locking in SharePoint

By -
Image
This is a topic I've been meaning to discuss in a while. We open, change and close documents almost every day, and sometimes we collaborate with other people at the same time on those documents. SharePoint brings all co-authoring features we need, straight out-of-the-box, but sometimes, there are problems. While things are starting to look better on the cloud side, the concept of document locking is still very much up-to-date and understanding how it works and what to do when things go wrong is crucial. In an article that has since disappeared the Microsoft Knowledge Base (but still available here ), Microsoft explains it best: When a document is opened by a client program, Windows SharePoint Services puts a write lock on the document on the server. The write lock times out after 10 minutes. Users cannot modify the document during the time when the document is locked. In a scenario where the program that opens the document unexpectedly quits or crashes and you try to open the do
Read more

Working around X-Frame-Options for iframes

By -
Image
The problem: One of the first things we noticed after migrating to SharePoint 2013 was that our iframes have stopped working, giving the error: "Refused to display 'http://contoso/pages/home.aspx' in a frame because it set 'X-Frame-Options' to 'SAMEORIGIN'." Quickly we could see that this is in fact a security mechanism to prevent click-jacking and others: "The X-Frame-Options HTTP response header can be used to indicate whether or not a browser should be allowed to render a page in a frame or iframe. Sites can use this to avoid Clickjacking attacks, by ensuring that their content is not embedded into other sites." Soon we realized that, starting SharePoint 2013, an HTTP Module is adding the header " X-Frame-Options " by default, with the value " SAMEORIGIN ". This is effectively preventing the rendering of pages outside the scope of the current web application. The (attempted) solution: So what to do?
Read more

Document ID not being generated

By -
Image
Problem In a scenario where we have many document Content Types, we may want to enable Document ID - aka "Permanent Links" - which is a feature in SharePoint that assigns a specific ID for each document. That ID never changes even if the document is renamed or moved to another location. In this scenario, the Document ID field was being generated for some libraries/content types, but not others, which is a surprisingly common problem. Background There are several stages we need to go through to enable use this mechanism. Stage 1 We enable the feature in the Site Collection Features. Stage 2 Under Site Collection Administration > Document ID Settings, we need to enable the assignment and pick a prefix. The IDs use the format: PREFIX-LISTID-LISTITEMID ( ref ) Where: PREFIX: the preconfigured prefix for the site collection, which can be any set of numbers and letters between 4-12 characters LISTID: the property docid_msft_hier_listid of the list
Read more