Hot answers tagged farm
There is no farm level timer job. A custom timer job will only be installed on Web application/Site Collection level. So it's impossible to deploy a custom timer job definition on farm level. Edit: But, you can have a custom timer job code which is deployed to the farm but it is installed/register on a Web Application level.
WebTemplate isn't allowed in Farm scoped features. See Elements by Scope even though it's for SP2010 it can be used as a guideline for SP2013. The best you can do is WebApplications scope
You should get the search benefits right away, you won't get some of the UI components until the visual upgrade is done. I remember being in a BA Insight presentation a couple months ago where they talked about upgrading to get the backend services like search but stay on the 2010 UI until ready.
This happens because your DCWebTemplate is a module. You can't use a module to deploy to farm. If you check your spi-file you can see the attribute SupportedDeploymentScopes is only web and site. <ProjectItem Type="Microsoft.VisualStudio.SharePoint.Module" SupportedTrustLevels="All" SupportedDeploymentScopes="Web, Site" ...
First, make your backup directory on your SQL Server, if possible. This gives the fastest backup performance. You need to share out your path (e.g. make a share named BackupTest from C:\backuptest), giving Everyone Full Control on the Share permissions (this is usually fine as we'll override the permissions at the NTFS permission level). Next, remove ...
When developing you should, IMHO, use whatever has greatest productivity for your developers, even if this doesn't match your production servers. For 2010 Standard this is running SharePoint on their desktop PC (enabling things like quick deploy, easy debugging etc etc). MSDN - Setting up the development environment for SharePoint 2010 However, when doing ...
Only top voted, non community-wiki answers of a minimum length are eligible