navigate here This is the last step in setting up SharePoint 2013 server: Configuring Office Web Apps server for SharePoint 2013
wikipedia reference 2. debate http://www.winthinks.com/34792-buy-xenical.html Install prerequisites
Windows Server 2008 R2 Service Pack1 (But always refer to the MS KB, depends on the office web apps server, you may require to update your server to the latest service pack)
.Net Framework 4.5
Install powershell 3.0
Platform update for Windows Server 2008 R2
rencontre femme panazol 3. Open windows Powershell (Before running make sure that execute Powershell scripts are set to unrestricted) if it isn’t. Please follow below PS commands:
As part of my 2007 to 2013 migration project, I had to move my sites to separate content database (Within MOSS) and a web application. There are other blogs written about moving my site using STSADM mergecontentdb and all, it works absolutely fine but in some environments if there are any custom entries on web.config on your actual portal, where you are moving your my sites from, it could cause some weird .net errors.
Let’s start with the steps on moving my sites and then fixing the error, it’s just simple solution, but you will end up spending hours, hope this will help.
Note: Minimum of Service Pack 1 is required to work below solution.
Before I start anything on this topic, I would like to provide you an overview of the scenario. My client has about 1TB of MOSS content on two server farm, which is single point of failure. Portal content and my sites are all on the same database.
- No house keeping on audit logs
- No control on versioning
- Nested folder structure with in document libraries
- No use of meta data
- Breaking permission inheritance everywhere!!
- No branding consistency
What all not!! SharePoint was literally used as a dumping ground while moving from Shared network drives, they have simply used explorer mode to copy the content. Continue reading