Tag Info

Hot answers tagged

6

$site = Get-SPSite http://intranet.sharepoint.com/ $site.RootWeb.Author where SPWeb.Author property gets a user object that represents the user who created the website


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

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


4

Yes use Author property of the web object associated with site collection $siteCollectionUrl = "http://sitename:portnumber" $site =new-object Microsoft.SharePoint.SPSite($siteCollectionUrl) $web = $site.RootWeb $creator =$web.Author


4

Using a pure Sandboxed solution this is not possible. A sandboxed solution has absolutely no access outside the current site collection, that's the whole point of sandboxed solutions. On-premises If you're solution is developed for on-premises SharePoint where it's "just" politics which require the solution to be Sandboxed. Then there is the possibility of ...


4

No, you can't have different web.config for different site collections, however you maybe be able to add tweaks e.g. HttpModule and HttpHandlers configurations to it depending on your requirements...


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

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

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

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


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

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


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


3

To list them, this actually gives you all sites under the path though: Get-SPSite "http://awesome.com/workspaces*" -Limit ALL To delete you should be able to use Get-SPSite "http://awesome.com/workspaces*" -Limit ALL | Remove-SPSite -Confirm:$false You can use Remove-SPContentDatabase -Identity {GUID} to remove a content database


3

If your production and development environment is patched to the same version, you can just go to sql management studio and take a backup of the content database, move it the dev environment and restore it using sql management studio, and then use Powershell to mount it to a web application ( Use Test-Spcontentdatabase before this step ): Use the ...


3

I know your original question was about doing a backup and restore of the content DB. But here is another way of doing it using backup and restore. You want to use the flag -UseSqlSnapshot in case users are currently using the prod site. Backup-SPSite -Identity https://urltomyprodsite –Path "c:\backups\myProdSite.bak" -UseSqlSnapshot Copy the backup ...


3

Maybe you're site is still listed as a SPDeletedSite? Get-SPDeletedSite & Remove-SPDeletedSite You may already have used this site name before and deleted it. Check by running the following script: >Get-SPDeletedSite You'll see the site (or sites) listed, like this: WebApplicationId : 009c1289-392b-43a6-8222-146117074738 DatabaseId : ...


2

you should find "SharePoint Server Publishing Infrastructure" under "Site settings" > "Site Collection Administration" > "Site collection features" you wont find it under site feature or you can access it through this link : https://{sharepoint server}/_layouts/15/ManageFeatures.aspx?Scope=Site


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

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

No it is not possible, you can have many site collections per content database, but not the other way around


2

To manage site collection size growth, I would recommend to create an Archive site collection (with separate Content database). Use the primary site collection to store only "actual" data. Steps: Create an additional site collection that contains archive data Implement archiving process for moving expired data into archive About archiving process ...


2

I found an answer, just for site collection created on web application root. Use this command to backup a site collection Backup-SPSite -Identity "http(s)://your-site-collection-url" -Path "C:\backups\your-site-collection-backup.bak" It's important to use an absolute path as -Path parameter. Then create a new web application and then run the following ...


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


2

there are couple of options you can try to remove the orphan in the databases. Did you try to run the restore with force parameter? Detach the content DB wait for couple of min and re attach it try to repair the Content DB if you have site id (returning while running get-spsite) then you can forcefully delete it from SharePoint via powershell or stsadm ...


2

You can do it all from C# using the excellent post found here: http://blah.winsmarts.com/2014-4-Get_list_of_site_collections_using_CSOM_in_Office365.aspx This example is, I believe, from within a SharePoint app but you can do it similarly from a console app. First you'll need to add a reference to Microsoft.Online.SharePoint.Client.Tenant.dll which you ...


2

You can implement like the following: $web = Get-SPWeb http://sharepoint.contoso.com/sites/sitecollection $web.AnonymousState = [Microsoft.SharePoint.SPWeb+WebAnonymousState]::Enabled $web.Update()


2

You can create site collections in SharePoint Online with C# using the client side object model. You will need to install the SharePoint client SDK first which includes the CSOM libraries and the all important Microsoft.Online.SharePoint.Client.Tenant.dll. There is a full walkthrough on how to get the client SDK and use the CSOM libraries with C# to create ...



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