Hot answers tagged

8

Probably it occurs since you are using App-only policy type for authorization . According to App authorization policy types in SharePoint 2013: App-only policy—When the app-only policy is used, SharePoint checks only the permissions of the app principal. Authorization check succeeds only if the current app has sufficient permissions to perform the ...


7

First, you can change the O365 landing page, but you can't specify a URL for the new landing page, it's a dropdown menu. See https://blogs.office.com/2014/09/18/new-office-365-home-page-fast-access-services/ for details. Second, this setting is a per-user one. An admin cannot change this setting for all or specific users at this time. As it's said in ...


6

CSOM Using the ClientContext, get your Site object and check its URL SPContext.Current.Site.ServerRelativeUrl : if == "/" JSOM For that you can use the _spPageContextInfo variable. To check if user is in root site collection vs any other site collection, check this variable : _spPageContextInfo.siteServerRelativeUrl : if == "/", then is the absolute ...


5

As Steven stated there is no way to do this OOTB but you can do it with powershell. Get the lists from different Sites: $targetWeb = Get-SPWeb http://sitecollection/site1/ $sourceWeb = Get-SPWeb http://sitecollection/site2/ $targetList = $targetWeb.Lists.item("Target List Name") $sourceList = $sourceWeb.Lists.item("Source List Name") Add the Lookup field ...


4

The users are stored per SiteCollection, so there will no other way as to iterate through all of them.


4

For this process to work, the following must be true The destination content database must already exist. The source content database and destination content database must be located on the same instance of SQL Server. The source content database and destination content database must be attached to the same Web application. Steps Add a content database ...


4

You can detach the content database from central admin and then reattach using the correct SQLCluster Name. You dont need to delete anything. Attach or detach content databases in SharePoint 2013


3

things are as simple as you mentioned in your question. Here are the steps. You have to perform the SQL backup of the Content Database from Source Farm Move the back file to destination server(sql) Restore the Database on destination SQL Server now you have two options over here if you overwrite the destination dB while restoring, then no need to attach ...


3

There are couple of ways to find it. simple one is Go to the view source of the SharePoint page >> Search for "SiteTemplateID" to find site template name SharePoint 2010. USe command Line tool stsadm.exe -o enumallwebs -databasename <content-db-name> > Template.txt Now, Open the template.txt file and check for template Use SharePoint Manager ...


3

Do not remove the site collection from the database! Just remove it via the GUI (Site settings -> Delete site) or use the PowerShell cmdlet Remove-SPSite (outlined here). This will make sure it is deleted the right way


3

You can use: New-SPSite -Url $url –ContentDatabase $ContentDatabase -Name $WebsiteName –Description $WebsiteDesc -Template $Template -OwnerAlias $PrimaryLogin –OwnerEmail $PrimaryEmail see: https://social.technet.microsoft.com/forums/sharepoint/en-US/89c90032-5be1-4fe6-8546-0114eaf018ca/site-collection-in-a-particular-content-database


3

Similar to the other posts, I recommend a single site collection for customers, and a subsite per customer. As far as sharing columns and such, use the Content Type Hub and load up your content types and throw those in your issues lists. If you don't have a site provisioning process, get one ;) this can handle your CTs and lists for you. Then using search ...


3

I depends on many factors. Some of the rules I follow are Create Site Collections - For not related entities (Ex - Departments) Create Site Collection if we are dealing with large amount of data. This will enable us to split Content Database per site collection In all other cases I simply create site based on the organization structure.


2

Yes, it is possible to get it. You can use REST calls to get the required information. The following code shall help you: I have created respective arraylists to store the subsite, document library and folder information. Once the information is collected in the arraylists we can display it as per out requirement. Get subsites: $.ajax({ url: siteUrl + ...


2

The list instance was created on the site on which you activated the feature. Your list should be in a web-scoped feature. Site-scoped features are for site scoped things like master pages, content types and web parts. They will not cause web-scoped things like lists to become automatically provisioned on subwebs. This means every subsite you want the ...


2

You can try Managed Metadata fields in this scenario where the admins for Taxonomy are separate set of users with in SharePoint. Let me know if you have any questions.


2

Use SPWeb.SiteUsers to get all users in the site collection.


2

This is expected behavior because.. You make it hidden through the content type page. Now when everything is working fine you decide to change default value of field. For this, you go to, list setting and then that particular column. If you look at the window where you change default value. we have one section "Require that this column contains ...


2

My mantra is use a structure like that for publishing type sites, where it is all about information you are trying to display publicly for the users of the company. There generally isn't a ton of content there, it is things like displaying company news, IT Service catalogs, things like that. Then I have site collections for each of the departments for ...


2

In my opinion, I'd build it for growth off the bat and have each department in a site collection, with a managed path--"sites" is fine http://sharepoint/sites/hr http://sharepoint/sites/finance http://sharepoint/sites/operations With each site collection there will be a site collection specific, generated set of SharePoint groups--Visitors, Members, and ...


2

There isn't anything native to do this. We have it included as part of a provisioning commandlet that follows our business logic for quotas and architecture. You could do it like this using SharePoint Online PowerShell module to update existing sites, and just include the Set-SPOUser in your provisioning: $sites = Get-SPOSite -limit all foreach ($site in ...


2

Publishing Portal maps to "BLANKINTERNETCONTAINER#0" and not "BLANKINTERNET#0", which is specific to subsites. You can verify this or any other site template from the site creation page by using your browser's dev tools and looking at the select option that represents the site you're trying to create:


2

Save your site as template manually. Then find the template guid id. Now create your site using CSOM. See more here internal void CreateSite(String targetUrl, String title, String owner, String siteTemplate) { var ctx = new ClientContextWrapper(targetUrl); var tenant = new Tenant(ctx); //Create new site var newsite = new ...


2

SharePoint adds the number because the name still exists because of the site collection not being completely removed from the content database. If you would try to create a third, it would be called ABC-3 and so on. Changing the title, the site collection will still be named ABC-2 internally. When you remove a site collection from the UI, the site ...


2

If both primary and secondary owners are set, the only other way to add additional Site Collection admins is to use the New-SPUser command and include the switch parameter -SiteCollectionAdmin. New-SPUser -UserAlias 'Contoso\Jdow' -DisplayName 'Jane Dow' -Web 'http://contoso.com' -SiteCOllectionAdmin


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

One workaround is: Enable the Publishing feature at site collection now browse this page sitecolelction/_layouts/15ChangeSiteMasterPage.aspx Now you can change the master page for all subsite.


2

If I understand correctly, there's never been a root-level site collection in your Web app (otherwise, you "/" would not have been an option when creating a new collection, "/sites/" would have been the only-and-default option. So, to delete it, you can simply go to Central Administration, "Applications management", "Delete a site collection", select the ...


2

You have to Create your Content Type as Content Type Hub after that your Content type will appear in all site collection of your web application for more info about you can refer below links http://www.sharepointpals.com/post/How-to-Use-Content-Type-Hub-in-SharePoint-2013 ...


2

I would do this way( i am guessing you are developer). Create a List in SharePoint with all required column( Site collection name, url, Owners, Site template etc)as per your requirement.One special field which will indicate whether this request processed or not( true/false type). Now create PowerShell Script, which will read from List and create the site ...



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