SharePoint Secrets

Change SharePoint Central Administration Account On servers running SharePoint Central Administration site run the following command: stsadm -o updatefarmcredentials -userlogin DOMAIN\USERNAME -password PASSWORD On other servers not running SharePoint Central Administration site run the following command: stsadm -o updatefarmcredentials -userlogin DOMAIN\USERNAME -password PASSWORD -local Run iisreset /noforce to restart IIS To make sure that this operation completed, open SharePoint Central Administration site >> Operations >> Timer job definitions and wait until Administration Application Pool Credential Deployment timer job disappears from the list. Change Application Pool Accounts There are two ways to change application pool accounts in SharePoint: first one using GUI, and the second using STSADM command. To change application pool accounts using GUI: 1.Open SharePoint Central Administration site >> Operations >> Service Accounts (under Security Configurat

In order to do a MOSS (aka Sharepoint) 2007 install using best practices, Microsoft recommends creating and using service accounts. Click here for Microsoft article I will summarise the long article into more relevant details (and for futher reading, you can click the link above) Following are the service accounts I created and the permission levels specified for MOSS to install and function properly. 1. MOSS Setup Account (MOSS_Setup) Typically, this is the account used to do a MOSS/Sharepoint install and setup. This account is used for a lot of tasks – MOSS installation, creating new IIS sites and SQL Server databases. It must belong to the Local Administrators group. Also, this account must be a Domain User, have access to the SQL Server instance to be used, with securityadmin and dbcreator roles. 2. SQL Server Service Account (SQL_Svc) This is the account used to install the SQL Server instance to be used for MOSS databases. I have used the account to run the SQL Server Service &

Microsoft Office SharePoint Server 2007 SharePoint Server 2010 Office client required to view and edit documents uploaded to document libraries (Download and open) Office Web Application enables Word, PowerPoint, Excel and Visio documents, using Silverlight or HTML with JavaScript (Depending on Browser Support) No Co-Authoring Capability Co-Authoring Capabilities available for Word, PowerPoint (with client software) and Excel (Available over the web) Lot of post backs Fewer post backs for default actions – more Ajax usage No inherent support of Ajax or Silverlight Fully supported Static themes. You just pick a theme and its applied across the site, no preview You can select a theme , customize it and preview before applying it on the site No bookmarking, tagging or rating capability Its all there Content Types scoped to site collections New concept of having a Content Type hub which can be shared across web applications Media files would have to be downloaded before playing Progress d