The new solution is based on SharePoint 2010 Enterprise Edition. I started the the project in December 2011, and work part time on together with other tasks like a new corporate website plus multiple other projects.
To kick-start the project, I used AutoSPInstaller to install SharePoint. In previous SharePoint projects I have created the PowerShell scripts myself. Fun, to a point - but since I didn't want to spend time in developing and maintaining this now - I decided to go for AutoSPInstaller. A good choice.
The installation went quite smooth. After installation I needed to change the urls, in IIS host headers and SharePoint Central Admin's AAM.
Adding a application server, and moving services from WFE to APP server was more less only stop services on WFE and start them on the APP Server.
After this, it was more or less the standard SharePoint tasks like creating web application, site collections, adding permissions, etc....
My next task is now to configure SCOM, and tune that for SharePoint.
Experienced some problems:
- If Reinstalling, read: http://davidbajak.com/blog/post/2011/09/29/Fix-SharePoint-2010-Enterprise-Search-After-Using-AutoSPInstaller-Script-Installer.aspx
- If Uninstall (there are some guides, e.g. http://autospinstaller.codeplex.com/discussions/263025)
- Uninstall SharePoint 2010
- Drop databases on sql server
- Delete invalid IIS entry
- If you problem to run miisclient, you have to runAs uecc\spfarm.To be able to run "C:\Program Files\Microsoft Office Servers\14.0\Synchronization Service\UIShell\miisclient.exe", you have to RunAs e.g. uecc\spfarm
No comments:
Post a Comment