Hot answers tagged

5

I can't see that you have run the SharePointBAC.ps1 in your script, which is downloaded from the Codeplex page SharePoint Backup Augmentation Cmdlets. The scripts Get-SPBackupCatalog Set-SPBackupCatalog Remove-SPBackupCatalog Export-SPBackupCatalog is not out-of-the-box native cmdlets in SharePoint Management Shell or PowerShell ISE with the reference of ...


4

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" xmlns="http://schemas.microsoft....


4

While recommended to install security updates as soon as possible, you will need to evaluate the security risk of not installing a particular security patch. This is something we will not be able to help you with. You do not need to install the Cumulative Update if you do not wish to install it. Yes, some non-CUs increment the farm build number due to an ...


3

This issue would occur if the user account "UserAccountName" or "Administrator" doesn’t have enough permission in the SQL server contents databases of SharePoint site collections in your machine. So, add the "UserAccountName" in to your MSSQL server by following the below steps: 1) Go to that server and open the SQL SharePoint instant using Management ...


3

That is not an official SP commandlet You can download it on codeplex https://sharepointbac.codeplex.com/ After downloading you install it by running the "SharePointBAC.ps1" included in the download Further Documentation


3

The Backup-SPFarm command should use a network share where The service accounts, Farm accounts and SQL Server service accounts have Full Control access to the share. This is because SharePoint uses SQL commands for running parts of the backup and these execute in SQL Server's context. More information: Prepare to back up and restore farms in SharePoint ...


3

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


3

You can find a list of possible values for the Microsoft.SharePoint.Administration.SPServerRole enumeration in the corresponding MSDN article. These are: Invalid: Specifies that the server does not have a registered role in the configuration database. WebFrontEnd: Specifies that the server is a front-end Web server within the SharePoint Foundation ...


3

if you ask for the best practice then: Create the SQL_Admin: The SQL Server service account is used to run SQL Server. It is the service account for the following SQL Server services: MSSQLSERVER SQLSERVERAGENT. SQL Admin on the SQL Server. it should be domain user with Local Administrator on the SQL Server. read more about the best practice: SharePoint ...


3

You already found out a lot of stuff regarding security updates, CUs and version number increments. There's nothing wrong in your post, but i would like to add some comments especially to your questions: It is valid to install security-patches for Windows including SharePoint specific security-updates (if there's one available that month). Theoretically ...


2

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.


2

AFAIK, in short there's no way to recover the passphrase. WHY? Because it was intended this way in the first place for security reasons. The answers that you find from other sites/people are all right to CHANGE the passphrase, not to recover them. So if you've forgotten your passpharse, the best you can do is to create a new one. Hope this helps you.


2

You are correct! http://office.microsoft.com/en-001/windows-sharepoint-services-it/managing-the-configuration-database-HA001160814.aspx The farm can contain several servers, applications and so on.. But it's all defined in THE configuration database.


2

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.


2

I dont do this, even you can rename the DB while restoring the from backup but still you are on your production server. Just think, more pressure on the SQL Server, resource fighting, and just a single mistake blow up your production Data. I would go for separate SQL server for this test.


2

You should use the Add-SPShellAdmin Cmdlet to grant such permissions for users on content DBs. You can remove the permissions via Remove-SPShellAdmin, or list the granted users via Get-SPShellAdmin.


2

No this is not possible. one server can have only SharePoint farm. But you have to mutliple farm's database on single SQL server.


2

First you test your database by running Test-SPContentDatabase -name WSS_Content_DB -webapplication http://sitename If you get errors, solve them. When you have no errors, continue with Mount-SPContentDatabase "MyDatabase" -DatabaseServer "MyServer" -WebApplication http://sitename This example mounts an existing database to the sitename web ...


2

The farm couldn't have been 'upgraded', but the databases certainly could have. For the Content Databases, you can run the following T-SQL query: SELECT * FROM Versions (NoLock) That will tell you the version history in the Version column.


2

There is no risk to applying the SP3 on the SQL server 2008. But you have to plan it.I would apply the patches in the following order. Schedule a Downtime for the SharePoint I will stop the IIS & timer services so that no connection should make to SQL server while patching. (In one of farm I shut down the server) Apply the Patch to SQL server, test and ...


1

Their are couple of ways you can do it. Method # 1 ( i am assuming you have the same kind of web application) take the backup of content DBs from Stagging restore into Dev farm, Detach the Old DataBase from SharePoint Dev farm Web App and Attach the New DB(stagging) deploy any solutions if you have. Make any changes to Web .config(if any). Method # 2 ...


1

Looks Like you problem is MMS 1 and MMS2 are not associtated with Central Admin Web App. Central admin > Application Management > Manage Web Applications > click on Central Admin web app and from Ribbon Click On Service Connections. Please make Sure MMS1 and MMS2 are associated with Central admin as Managed Meta Data service is.


1

Your SharePoint Servers are your "app" servers. You will create a wildcard CNAME record in your app domain that points back to your SharePoint server DNS record. Make sure that the the farm that receives it does not have host headers configured on the webapp that the requests will be delivered too. On production using SSL you will have to extend or ...


1

The first server will be a Web Front End (WFE) in part because the farm needs a server to run the Central Administration web when you first build it. What makes a WFE a WFE is that it runs the "Microsoft SharePoint Foundation Web Application" service. This is what vendors look for when they license various products per WFE servers. If you disable that ...


1

all roles can be switched after the installation. And you're right, the first server you install SharePoint on will have the Central Administration and allows you to configure your SharePoint farm. Nevertheless the Central Administration can be added to another server later on as well. An application server is typical a server which you dedicate to run ...


1

As Burrhus said farm is a collection of servers, e.g. Web, Applicatoin or DataBase servers. Companies do build different SharePoint farms in scenarios like when there data centers are based in different locations e.g. different countries or even contents. Understanding the Reasons for Deploying Multiple Farms


1

You need to reference SharePoint client DLLs into your remote VS project: - C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI\Microsoft.SharePoint.Client.dll - C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI\Microsoft.SharePoint.Client.Runtime.dll (replace "14" by "15" in these paths if SP2013) ...


1

You should use Client Object Model (.NET Framework redistributable assemblies): http://msdn.microsoft.com/en-us/library/office/fp179912(v=office.15).aspx


1

As per my experience same name for two content Database with different instance is not an issue. SharePoint always check against the Database GUID. If you create Wss_Content01 on sql instance 1(having unique GUID) and then create another DB WSS_Content01 on SQL Instance 2(again Unique GUID). You can attach both DBs to same web application or different web ...



Only top voted, non community-wiki answers of a minimum length are eligible