Tag Info

Hot answers tagged

11

or simply: $site = Get-SPSite http://YourSharePointSite $site.AllWebs.Count


4

if ($ver.Version.Major -gt 1) {$host.Runspace.ThreadOptions = "ReuseThread"} if ((Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue) -eq $null) { Add-PSSnapin "Microsoft.SharePoint.PowerShell" } $sites = Get-SPSite <SiteCollectionUrl> $noOfWebs = 0 foreach ($web in $sites.AllWebs) { $noOfWebs++ } If ($sites ...


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.


3

Using the following code, within the SharePoint Management Shell, you can get the count of Web Applications in the Farm, Site Collections in Web Application, Sites in Site Collection. Write-Host "Web Applications in Farm" $WebApplications = Get-SPWebApplication $WebApplications | Measure-Object | Format-List Count ForEach($WebApplication in ...


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

This error occurs since there is mismatch between Microsoft.Online.SharePoint.Client.Tenant.dll assembly and the Microsoft.SharePoint.Client.dll assembly versions that are referenced in project. Ensure the proper version of Microsoft.Online.SharePoint.Client.Tenant.dll assembly is referenced. For example, for SharePoint Online project the the following ...


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.


1

As per you requirement, what i understand, you want to create the a site for each customer. I would recommend to create a customer site collections, t his will seprate the customer data from your team. Your url lenght will be short for customer's sites For issue tracking list, as you already have the issue tracking list in the team site then you can ...


1

If you have the "bar" as managed path and you are trying to create a subsite under the root site collection ("/") then it will throw the following errors. "bar" cannot be used as a site name. Site names cannot contain certain reserved words and cannot begin with an underscore. Please enter a different name. But if you already created a web under ...


1

You can do it using below script $site = Get-SPSite http://siteurl $site.LastContentModifiedDate



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