Tag Info

Hot answers tagged

7

You're within the limitations of SharePoint (http://technet.microsoft.com/en-us/library/cc262787.aspx) in either scenario, which is good. Some of my thoughts As far as performance, I don't think you'll see much in way of improvement going from one DB to multiple DBs, unless you can move the DB files to different disk arrays. 100GB is a reasonable size for ...


5

Here are two ways to tell the robots to not crawl your site: Adding robots.txt with the following content in the root folder with SharePoint Designer (All Items in SPD) User-agent: * Disallow: / Adding meta tag in your master page's Head section as below should prevent the robots from crowling you site. <meta name="robots" content="noindex" > ...


5

There are a couple of things you can try... such as 1. Get-SPDeletedSite & Remove-SPDeletedSite You may already have restored this site before. In that process you also deleted the site first (automatically), which you can find running the command... >Get-SPDeletedSite You'll see the site (or sites) listed, like this: WebApplicationId : ...


4

SPContentDatabase.ForceDeleteSite http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.administration.spcontentdatabase.forcedeletesite.aspx use this method to force a delete: SPWebApplication spWebApplication = SPWebApplication.Lookup(new Uri("http://mywebapplication")); // insert the webapplication ...


4

From a technical point they're exactly the same. The only difference is the way users think of site collections beneath each of them. So it's common to use "/teams/" for site collections for individual teams and "/sites/" for everything else (in SharePoint Online, On-Premises often create their own) "/sites/" and "/teams/" is what is called managed paths in ...


4

The accepted answer is not correct. You can create multiple root sites in one web application. Additionally, each root site does not have to have a url of www.domain.com/path/site1. Using Host Named Site Collections, each root site can have it's own sub domain name. If your company name is contoso, and you create a web application at webapp.contoso.com, You ...


3

Yes, You can have three different site collections based on three different templates. It doesn't matter if they are based on custom templates or not. In a web application you can create 750,000 (500,000 Personal Sites and 250,000 other sites per farm) The maximum recommended number of site collections per farm is 500,000 Personal Sites plus ...


3

There is an admin web service for 2010 and 2013: http://msdn.microsoft.com/en-us/library/websvcadmin.admin.createsite%28v=office.14%29.aspx http://Site/_vti_adm/Admin.asmx


3

Basically yes, that includes everything (blob storage). You can go over that limit, but there are some very specific requirements if you do. Take a look at the requirements in these links: http://technet.microsoft.com/en-us/library/cc262787%28office.14%29.aspx#ContentDB http://technet.microsoft.com/en-us/library/hh307867%28v=office.14%29.aspx Here ...


3

Do you have the backup of your content Database which are attached to web app(deleted) if yes. 1) from central admin create new Web Application and mention the same port(6666). 2) configure the Web Application settings i.e object cache settings, adding appPool account to USer Profile, AAM etc. 3) now detach the Content DB you created during the web ...


3

Check if you're having sufficient permissions in SQL server to perform restore Double check the managed-path try restoring to different paths like http://servername.com/sites/yousitecollection Ensure all the customizations (WSPs) are deployed to destination (if any). Check ULS logs for additional pointers


3

After searching over internet four hours I found one thing. That it is not possible to make alias of the url because the site collections lie within same web application. So, that way was not possible for me. The final solution is to create an HttpModule for web application that checks specific url, if it meets the condition then redirect that request to ...


2

If all you want is to use the SP2010 Management Shell without restrictions, have you tried to add the user account to the Sharepoint_Shell_Access (or, as Microsoft calls it: to configure least privilege rights to manage SharePoint with Windows PowerShell)? Try this: Run SharePoint 2010 Management Shell as Domain Admin and run the following commands: ...


2

First of all you will create a web application with URL looking like this, (HostName as referenced by yourself) portal.companyName.com //we call it host header, this URL looks like a intranet www.companyName.com //if its going to be a public site Then you create Managed paths, which you referenced as Drop Down List in your question. I just found this ...


2

In one web application, can we create multiple root site collections ? No, only one 'root' can exist, if you mean at the root of the URL i.e. http://domain.com/. You can create many more at http://domain.com/path/site1, http://domain.com/path/site2, etc. I just wanted to clarify the use of the word 'root'


2

There is no real difference, it is a matter of taste and consistency, I for example would create my projects and team sites under /teams, and other types of site collections under /sites This blog seems to describe Managed Paths in an Office 365 context quite well: http://schakrabortytcs.blogspot.se/2011/10/office-365-sharepoint-online-managed.html?m=1


2

Ok so the Get-SPFeature works differently depending on what parameters you pass it. The following line is asking which features are enabled at the Web Scoped level. $webFeature = Get-SPFeature -Web $spSiteCollection | Where-Object.... However, if you want to see if your feature is installed then you need to use Get-SPFeature without passing any scope to ...


2

You only need to run one line of PowerShell to set all the site logos on SharePoint sites in a site collection (much easier than setting them by hand). (Get-SPSite http://SiteCollectionUrl).AllWebs | foreach {$_.SiteLogoUrl = "the path of your logo.gif"; $_.Update()}


2

make sure the solution deployment job was finished before you activate the feature. have a look at this blog: Programmatically waiting on SharePoint Solutions to deploy


2

You can use spweb.ensureuser Ensure user checks whether the specified logon name belongs to a valid user of the website, and if the logon name does not already exist, adds it to the website. MSDN Ensureuser


2

You can't do that with 2010 client object model but it is now possible with 2013. For promoting a user to Site collection admin we need to: Set the IsSiteAdmin property to true. Having said that you can't set the IsSiteAdmin property via 2010 client object model. However, it is quite possible to do it via: Server side object model PowerShell


2

The two most common ways I do this are: The following commands in Powershell: Backup-SPSite http://yoursitename.com/site -path d:\yourfile.bak Restore-SPSite http://whereveryouwantyoursitetogo.com/site d:\yourfile.bak For this, you do want to note that you can't have two sites with the same GUID in the same web application. What this means, practically ...


2

You can find a great article that explains the cross-domain / cross-site collection issues and how to resolve them on the MSDN: Solving cross-domain problems in Apps In the link above the following explanation can be found: Cross-site collection calls A different problem that is often lumped into the same cross-domain category is issuing calls to ...


2

Some points to consider moving your site (SPWeb) to site collection (SPSite): Shared permissions (usually span across multiple sites and lists) Galleries for templates Content types (Content types are provisioned at site collection level) Web Parts Shared branding Common navigation scheme Site collection quotas (to control storage limits) with ...


2

If you just need that list from the old contentdb / site collection, just create a new Site Collection where you want the data to be, export the list from the old location and import it at the new location http://technet.microsoft.com/en-us/library/ff607895.aspx If you do not need the entire site collection, dont move it.


2

Things are a little different on SharePoint Online (SPO) than on SharePoint Server. You find features in the Site Settings page (equal to server version). But in the SPO version, the manage site feature link is located in the section Site Actions. You can browse to it directly via the URL https://<site collection url>/_layouts/15/ManageFeatures.aspx ...


2

Simple answer of this question is: Farm Administrator is the father and Site Collection administrators the kids. Farm Administrator have full control on SharePoint farm; can create services applications, Web Application, manage quota, deploy solutions, configure the farm level settings, run PowerShell scripts etc. While site collection administrators, only ...


2

How to retrieve sub webs under root web The following REST endpoint https://contoso.sharepoint.com/_api/site/rootWeb/webinfos will return the collection of sub webs (WebInfo objects) under root web How to retrieve sub webs under relative web Assume the following site structure: -- Root | -- Community | -- Feedback Then the ...


2

You can activate SharePoint Server Publishing Infrastructure features on the site collection level. Then Go to the site settings of your subsite and find Navigation link in Look and Feel section. In Current Navigation settings select Display the same navigation items as the parent site


2

Create a custom 404 page for your site collection, then either add code behind to it with your own logic as when you want to create a subsite and when not.. OR in SharePoint 2013 create a custom error page, add a content editor webpart to it, and some javscript code which will create a subsite for you, but there is a lot of things that you will require to ...



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