Stefan Goßner

Senior Escalation Engineer for SharePoint (WSS, SPS, MOSS, SP2010) and MCMS

Certain Microsoft SharePoint Server 2013 installation scenarios are not supported

Certain Microsoft SharePoint Server 2013 installation scenarios are not supported

  • Comments 5
  • Likes

If you are planning to use SharePoint 2013 you should be familiar with the following article which outlines unsupported Installation scanarios for SharePoint 2013:
http://support.microsoft.com/kb/2764086/en-us

As summary the following Scenarios are unsupported:

  • Installation on Resilient File System (ReFS) - only NTFS is supported
  • Installation on a machine which is not joined to a domain
  • Installation on a domain Controller
  • Installation on a Windows web Server
  • Installation on a Virtual Machine (VM) that uses Dynamic Memory

More Details are in the article listed above

Comments
  • <p>Hi Stefan,</p> <p>This is good stuff. I&#39;d also add on the list the fact that stretched farms are no longer supported in SP2013: </p> <p>&quot;All servers that belong to a server farm, including database servers, must physically reside in the same datacenter. Redundancy and failover between closely located data centers that are configured as a single farm (&quot;stretched farm”) is not supported in SharePoint 2013.&quot;</p> <p>Source: <a rel="nofollow" target="_new" href="http://technet.microsoft.com/en-us/library/cc262485(v=office.15).aspx#hwLocServers">technet.microsoft.com/.../cc262485(v=office.15).aspx</a></p> <p>This was supported in SP2010 so might come as a surprise if you&#39;re just doing migration using existing infrastructure :).</p>

  • <p>Hi Jussi,</p> <p>this is more or less a wording issue. We had lots of cases in the past on this. </p> <p>Our Software has been tested on in Scenarios of a single data Center.</p> <p>But if you System worked fine with SP 2010, then it will also work fine with SP 2013.</p> <p>If you are affected by this specific Scenario I would recommend to open a Support case with Microsoft to get into a discussion about the implications.</p> <p>Cheers,</p> <p>Stefan</p>

  • <p>Thanks Stefan! We&#39;ve had discussions with Microsoft and it seems the default goes here, as they point us back to the Technet article. I fully understand that, but it&#39;s problematic for customers already going the stretched farm-route, and now needing to change the architecture to conform to SP2013 recommendations. But as always, it depends and is often case by case.</p>

  • <p>Thanks for the post, so good to give others a heads-up warning. </p> <p>I&#39;d like to add one thing though: there&#39;s quite a lot of add-ons and peripheral software that might get broken by the upgrade. We&#39;re using this SharePoint add-on called Harmon.ie (<a rel="nofollow" target="_new" href="http://harmon.ie">http://harmon.ie</a>) and we decided to hang back with the upgrade until express assurance that it&#39;ll keep working as before, since the add-on is used on virtually all workstations.</p>

  • <p>Hi Stefan,</p> <p>I&#39;m asking this question with self-education in mind, not an operational situation.</p> <p>Why is SP2013 not supported on a VM that utilizes dynamic memory?</p> <p>Many thanks,</p> <p>Steven</p>

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
Raw Html Fix