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" ...


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

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 ...


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

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

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

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 ...


2

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 ...


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

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 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

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

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

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

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 ...


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

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 ...


1

Disaster Recovery plan depend upon business requirement. First you have to setup your farm with high availability options Load balanced Web front end Redundant Search service server Always-On SQl Server. High availability is generally used to describe the ability of a system to continue operating and provide resources to its users when a ...


1

The short answer is no. The long answer is it might be useful if we understood what you are trying to do. Why would you want multiple farms on a single server? If you need multiple URLs you can create several web applications or use host named site collections. If it is a security concern then this again can be achieved with separate web applications and ...


1

I figured out that there properties are disabled by design (really? lol). The values in the MachineIP column and in the MachineName column appear as NULL because of privacy concerns. By design, Windows SharePoint Services 3.0 works in this manner. I think is it possible to trace these information looking into IIS Logs. Auditing for a site collection in ...


1

For a development environment, no I don't see any reason you couldn't shrink it (though you should never shrink databases in production, unless you're going to gain back 40%+ space and you need it -- shrinks fragment the indexes). I would say for your dev environment, you probably want to disable most usage logging, unless you need it for a specific ...


1

You can shrink a SharePoint SQL Server database just like any other SQL Server database using SQL Server Management Studio. This is fine in a development environment, since you are likely the only person using it (might want to give a heads up to the team if there's more than one of you). Of course, there will be a performance impact on SharePoint itself ...


1

It's a good practice to implement a form of load balancing from a failover perspective, but not necessarily ideal if you only have two servers in your farm. As an example, if there's a high search load, then you may want that second box dedicated to services. It's not generally the best practice to run web and app roles on all of the servers in your farm. It ...


1

To append to the answer above: the server that hosts Central Administration will be the application server by default. It'll hold all the services - also by default. It's recommended as best practice to have multiple servers that can host Central Administration, so an option is to start the SERVICE "Central Administration" on your web front end, in case the ...


1

You can have both type of authentication on one WFE. Authnetication is basically for Web Application scope not the server scoped. I would Like to know how many user will access the SharePoint for both apps? When you create a web application during that process you will see the Public Url option, which is typically server name & port number( server name ...


1

The reason for introduction of Sandboxed Solutions was giving ability to work on a partially trusted environment. Without disturbing the Farm Administrators, the Site Collection Admin can handle the deployment. This runs under a set of security policies said CAS Policies. Also with this Sandboxed solutions come under several limitations. Here are some ...


1

thats from a blog, refer to microsoft technet for more uptodate version info: September 9, 2014 update for SharePoint Server 2013 (KB2889864) This article describes update KB2889864 for Microsoft SharePoint Server 2013 that was released on September 9, 2014. This update includes stability and performance improvements. ...



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