Friday, August 16, 2013
Monday, August 5, 2013
My Conclusions on Installation and Configuration of SharePoint 2013 Farm (& Related) and Development Efforts
This blog is part of Series : Comprehensive SharePoint 2013 Development Environment Installation and Configuration
With the past several weeks of (Retries over Months) effort on trying to establish an orderly process for Installing and Configuring SharePoint 2013 Farm for the purpose of Development (Equally applies to most QA/Stage/Production environments as well), I wanted to capture some of my conclusions on the overall process and the effort involved.
- The overall SharePoint install involves several downloads (depending on other sub components you choose to install more software to be downloaded)
- Other than basic SharePoint Install, typical farm installation process is very comprehensive (like this main series blog itemized)
- Certain installations and configurations can be done only with a PowerShell Scripts and as you can experience following this blog series, there are several of them.
- I have gone through several installation missteps before I got it right (some of feature to work properly). So the sequence of installation and configuration is important to get it right.
- Weather you are following the installation and configuration wizard or combination of PowerShell scripts, it it very critical to ensure appropriate configuration parameters are used.
- So by the time you had completed the baseline install and configurations, you would probably start jumping in to to start your development.
- During this initial development effort uncover several security and further configuration requirements.
- So what is the outcome: “Inefficiencies in starting an effective development”
Now having said that, don’t get me wrong, I am hardcore developer, but this “Time To Build” is too tedious. By the time IT learns all the details and get their environment ready for developers it will be a while!