Standalone Installation of SharePoint 2013 : experience

, , Leave a comment

In continuation to the struggle ( ) to get started with SharePoint 2013 with all features, I invested this weekend with all sort of stuff to have SP2013 work like shown in official demos and hence thought of sharing the experience.  I don’t have the courage to do it again for demo/video/screencast purpose so sorry folks if you landed here in search visual tutorial.

OK, so this is what I did following to complete SP13 standalone

1. First thing first (hard to digest) but you do need Active Directory  to experience full features of SP13. You trying to install SP13 as standalone or complete  in Workgroup mode, will more or less land you in issues with no return (such was the pain that I had to re-build my machine approx 4-5 times in last couple of days). I will recommend for dev purpose you to install Active directory in your host machine and then create a VHD for SharePoint 2013. I installed Windows Server 2012 R2 in host machine and ran another version of Win2012 as VHD with Hyper V. (SP13 installation in workgroup is no more support  Refer link). Also you can refer the best practices regarding installing SP13 in Virtual Environment by referring this Link.

Also make sure you install AD on fresh Win 2012 host or else like me you might land up in issues like

Windows Server 2012 AD-DS can not be configured or uninistalled (Microsoft.Directory.Services.Deployment.DeepTasks.DeepTasks not found)

2. After you are done with AD and VHD with Win 2012, I recommend you to copy SP2013 setup in VHD rather than installing through network. This will save lots of issues for you when system is restarted during Prerequisite installer run.

3. After prerequisites are installed, you can run the SP13 setup. I chose Standalone mode, you can try Complete mode for which you will need Windows SQL Server 2008 R2 or above.  ( I didn’t face much issues with this but if you do, please share and I’ll try to help)

4. Once you done with the setup (and logged in as AD user) you might want to run SharePoint Powershell for Administrative tasks like changing Managed Account for AppFabricService etc. and when you open PowerShell you might see “The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered.” . Don’t panic, you can back to PowerShell and “Run it as Administrator”  and Powershell should now load SP cmdlets.

5. Now most of the features in SP13 will work fine even when you install SP13 in a workgroup mode( previously discussed by me at but there is big struggle to have MySite work properly (which at-least I couldn’t do successfully). There is an excellent blog post by Adis Jugo about creating & configuring MySite (after you have followed 1-4 steps) – Blog Link

I hope this post help you in a way or two !!! Do share your views & comments