I very recently had the same issue with Nintex Workflow 2010: It wouldn't install properly from my App server because this service was turned off.
Other than that, yes it's a good way to turn an application server into a true application server, and prevent it from running and serving the content web applications and IIS sites.
Have a look at the "...
SharePoint Server 2013 SP1 supports Windows Server 2012 R2. I see no reason why you shouldn't run your SharePoint Server on a 2012 R2 Server. Just make sure you install SP1 correct before adding logic, solutions and content to your farm.
Currently, Microsoft SharePoint Server 2013 is not supported for installation on computers running the Windows Server ...
If you are limited by Memory, you can share the same App Pool between several Web applications. This will allow you to save some memory. Sharing AppPools will allow you to pool that "base" memory per app pool.
The total amount of requiered RAM cannot be dertermined by just the number of WebApps, but is also affected by many other factors.
A valid reason to ...
Leave it on, as it provides flexibility.
You should already be directing traffic to your WFEs with DNS or a load balancer, so other servers won't have traffic hitting them. But leave it on. Down the road you'll need to perform some sort of troubleshooting, and this will come in handy.
"Well, then turn it on when you need to!" I hear you say. The problem ...
I'd make separate site collections per vendor. Permissions will be easier to manage and you don't risk exposing information to other vendors by accident.
Bog it down is rather vague. It might make things slower for other users if one vendor is storing a lot of data.
Yes there is. You should turn your browser to FastTrack which does exactly what your asking for - all in one place: https://fasttrack.microsoft.com/office
If you have more that 150 users, Fast Track is for free.
SharePoint 2010 Service Pack 1 does support content databases up to 4TB, if upgrading to Service Pack 1 is one of the things available in your SharePoint road map, let's do it to utilize maximum its capability.
I've found a white paper "Managing Multi-Terabyte Content Databases with SharePoint 2010" written by MCM, Sr. Technical Product Manager Bill Baer. ...
The biggest factor in choosing to go with sites is size. A single site
collection cannot span multiple content databases. Microsoft
recommends that a single content database should not grow beyond 200
Gigabytes. This isn’t a hard limit, and with expensive hardware (Disk
sub-system performance of 0.25 IOPs per GB. 2 IIOPs per GB) you can ...
The following whitepaper details all enterprise-only features and how they are used with SharePoint:
It also includes a table that relates SQL Server editions with SharePoint functions.
The most complete overview of SQL Server features can be found at
The thing to remember is that on x64 systems, an app pool can consume a lot of memory, if unchecked, 1GB+. On x86 systems, ASP.NET is capped at 900MB by default. Setting a memory cap is useful, but will cause the app pool to recycle if the app tries to go over it, basically bringing your app down for a few seconds. If bad code (Undisposed SPSite objects etc.)...
Before the release of Microsoft SharePoint Server 2013 Service Pack 1 (SP1), Microsoft did not support the installation of SharePoint Server 2013 in a Windows Server 2012 R2-based environment. However, with the release of SharePoint Server 2013 SP1, this configuration is supported in Windows Server 2012 R2.
Use SharePoint permissions. SharePoint search, all versions, is security trimmed. If the user does not have permissions to the content, then they can't find it in search.
If all of the problem content is in the same library, just edit the permissions on that library. Break inheritance, delete existing users access, and then grant back only the permissions ...
You can use a combination of eDiscovery and Search Result Removal. The eDiscovery component would help you discover the infractions and the Search Results Removal is the FASTEST way to remove the content from the index.
To be honest, this all really begins with proper training. Nearly all companies that face this issue MUST have a policy in place AND a ...
Be careful here - Chris is correct in that 200MB is an absolute minimum amount of RAM that an app pool might use. On the flip side, if you had say 5 very busy app pools you could quite conceivably hit 24GB + RAM usage. I wrote a blog on app pools on this a while back which goes into a little more detail (which includes some input from Steve Smith, MVP).
You could use WFE's to cache, but ensure you have enough RAM assigned in each of the servers to cater for the needs of App Fabric and SharePoint. Performance will drop if the servers run out of RAM and start paging. The main motivator to run on the same servers should be cost driven.
Some possible reasons to run App Fabric caching on seperate servers are in ...
There are a few things you can try like:
Cross-site publishing (new)
If you're using SharePoint 2013, be sure to check out cross site publishing!
In any case, you'll still have to deploy your customizations to both sides.
Go to Central administration - Application Management - Under Service Applications click Manage Services on Server .
On the top Right corner you will see the server name. Click on it. Select CA server.
The most important services that have to be stopped are
"Microsoft SharePoint Foundation Web Application" (that prevent the server from hosting web app)
It is possible to host multiple SharePoint farms within one SQL instance, but there are a few things to keep in mind.
Unless you already used a shortened SQL alias in creating your existing farms, you will need to use an alias of the old [Server][Instance] name to allow the existing farms to communicate with the new SQL instance using the new [Server][...
If possible , you can using office protect document feature if the file is office file , say before user up load the confidential file to SharePoint , user can edit the document with "protect document" , once document upload to SharePoint and after crawl , these files will not show up in search result .
As others have stated, SharePoint will automatically handle search and indexing according to your specified security settings, and password protected office files should prevent file content from being included in a search index.
If files are truly confidential, however, they should be stored as securely encrypted archives. I would never consider password ...
I am currently using windows server 2012 R2 and sp2013 fundamentals SP1 currently. As far as I can say everything is working very good with SP 2013 SP1 in Windows server 201 r2. It is not very fast since I am using a virtual machine in my pc, but as a virtual machine its performance is very satisfactory. The only drawback is that I am having problems with ...
Well as you say, SharePoint 2013 SP1 is released now with support for Windows Server 2012 R2. So if you want to leverage some new feature in 2012 R2 there should be no problem using it for both SQL and SharePoint.
Targeting audience is also dependent on the User Profile service application, which again is not available in Foundations. Beyond this point, the Publishing Infrastructure is really a complex endeavour with many features, content types, web parts deployed with it.
In your situation, you might want to consider relying on either Permissions Levels assigned to ...
Finally i found the answer.
my mistake is i chosen
document library settings > Versioning settings > Document Version History > Create major versions.
but the solution is
after activating the above features in document library settings > Versioning settings > Document Version History > we have to choose "Create major and minor (draft) versions".
That limit isn't a hard limit, it's just a recommendation based on the difficulty of SQL operations like backup / restore. You can have multi TB content databases if you want to and if your SQL environment can handle it. I would suggest a netapp type SAN with dedupping and fast backups connected to a very beefy SQL cluster.
It's hard to say how to break ...