Good news!
On Sep, 18 during the SIG community call, PnP Team shared their plans on PnP Sites Core library and PnP Core SDK.
“PnP Sites Core v4” library and “PnP Core SDK v1” with .net core support (.net Standard 2.0) – expected in December 2020!
PnP PowerShell v4 for SPO library built for .Net Standard 2.0 / PowerShell 7 will be released in Dec 2020 as well.
In Office 365 SharePoint admin can disable SubSites creation:
Well, agree, SubSites are not really disabled, but the button to create subsites is hidden: “This controls whether the Subsite command appears on the New menu on the Site contents page”.
Anyway, the result is: you are not able to create a SubSite (web) in SharePoint Online:
Actually there are at least 3 options to create a SubSite:
Step 1: Select “Site Contents” page
Step 2: Click “Return to classic SharePoint”
Step 3: Create SubSite
Step 1: Go to “Site Settings”
Step 2: Select “Sites and Workspaces” page (site/_layouts/15/mngsubwebs.aspx)
Step 3: Create a SubSite
Step 1: Install PowerShell PnP
Step 2: Connect to your site with PnP
Step 3: create a SubSite
Install-Module SharePointPnPPowerShellOnline Connect-PnPOnline -Url <your site Url> -UseWebLogin New-PnPWeb -Url "<new Web Url>" -Title "MySubSite" -Template "STS#3"
References:
See also: How to create a SharePoint Site in Office 365 if site creation is disabled
Microsoft SharePoint Migration Tool (SPMT) is installed under user profile, i.e. local administrator permissions are not required.
That means regular corporate user – site owner – can do self-migration from SharePoint on-prem to Office 365 SharePoint Online.
In Microsoft Office 365, under MS Teams, there are 3 team types:
Private team: you can only join the team if you are invited or know the team code.
You cannot see team name or description or content until you are team member (details).
Public team: you can join the public team if you wish. You can see public team name and description, but from MS Teams (desktop or web application) you cannot see public team content until you are team member.
Org-wide team: you join the team automatically (details)
From Teams – you can click on “Join or create a team” and you should be able to see some public teams (but not all):
But what if you are looking for a specific public team not in the list…
You know exact team name or at least some first letters.
Solution: You are lucky. Just start typing team name in search bar at top right and hit “enter”- you will see shortened list of public teams matching your search criteria:
NB: do not use wildcards, it will not work:
NB: do not use top search bar, it will not work:
You know (or guess) something about the team, like
Unfortunately, in this case both great Microsoft technologies – Search and Team – fail. You will not be able to find a public team:
Solution: use SharePoint search
SharePoint site is created once a team is created.
For public teams – SharePoint site has “Everyone except external users” by default in “Members” group:
which means literally “Everyone except external users” has access to the site with “Edit” permissions.
SharePoint search is security-trimmed, i.e. you will see the site content in search results only if you do have access to the site. So just go to the SharePoint or SharePoint search center and search for what you know or guess about the team:
You can use all the power of SharePoint search (wildcards, refiners, keyword query language KQL etc)
Once you found something – you can go to the SharePoint site:
Now from the site – look at the site name and hover the mouse over the site name – you’ll see pop-up window.
Now you know exact team name – and you can search for the team under Teams,
or, if you are so lucky you see “Join” button – just join the team.click site title or hove over the site title:
One moment – you cannot see team’s chat messages in SharePoint, as chats are kept in Azure. But you can search for chat content after you joint the team.
Somehow both – SharePoint Search and Teams Search are not working against site/team description. Hopefully this bug will be addressed.
You can also search for site Url in teams.
When you create a team – Office 365 generates a short team name (removes spaces and adds numbers if the team name is not unique; e.g. if the team name “Test” you might have “test381” as a short name, but if the team name is “This Is My Unique Team” – short name might be “ThisIsMyUniqueTeam”).
After you can change team name and/or SharePoint site name.
Team search under MS teams work for both names – short name initially assigned (kept as site specific Url) and new team name. But only starting with the beginning of the string.
In Office 365 under SharePoint Admin Center -> Settings -> Site Creation there is “Let users create sites from the SharePoint start page and OneDrive”:
Under classic settings page -> Site Creation it is called “Show the Create site command” with explanation “Display the Create site command on the SharePoint home page and in the sites list in OneDrive so users can create new sites”:
By default site creation is enabled and anybody can create a new site collection from SharePoint start page :
with two options: “Team site connected to an Office 365 group” and “Communication site”
SharePoint administrator might disable Sites creation, i.e. remove “Let users create sites from the SharePoint start page and OneDrive” or select “Hide the Create site command”. In this case user will not see “+ Create site” in SharePoint landing page:
The fun part is users are still able to create a new site collection from OneDrive, using “Create shared library”:
Direct link: https://changeThisToYourTenantName.sharepoint.com/_layouts/15/CreateGroup.aspx is another option:
and worth to mention that from under Teams anybody can create a Team and a corresponding SharePoint site:
The only way to limit self-site creation is to create a security group for users who need to create Microsoft 365 groups and via PowerShell Set-AzureADDirectorySetting command set “GroupCreationAllowedGroupId”.
Microsoft: “Manage who can create Groups“
Microsoft sells OneDrive as a personal cloud storage service… But There are actually two separate products behind the service, and each product provides more than “personal cloud storage service”…
When you login to Office.com, you can click on OneDrive icon:
and you will found yourself at OneDrive site, so
i.e. program that runs in the background and synchronizes files from your personal SharePoint site (“first OneDrive”) to your local machine and back:
Below is OneDrive desktop application in Windows File Explorer. Please notice how “test 01.txt” file and “test 02” folder are synchronized to first OneDrive.
Confused? No? Wanna more?
Using OneDrive desktop application you can synchronize your regular SharePoint site library with your desktop computer.
Here is a regular SharePoint site (Test23) with a LibUnderSharePoint library. You can click on the “Sync” button:
and see the magic! Now you have another folder on your local Windows machine:
– but this time OneDrive synchronizes it to regular SharePoint site.
There is also a “Personal OneDrive” – the same as regular OneDrive but free…
(again, do not be confused: initially there was just OneDrive – free personal version and OneDrive for Business – version you could have with Office 365 subscription; now they are Onedrive and Personal OneDrive π )
OneDrive is a Microsoft thing.
Google has “Drive File Stream” (Google drive)
Dropbox – Dropbox sync
If you are managing SharePoint search, specifically if you are customizing SharePoint search schema, especially in SharePoint Online (Office 365) – you know how slow it works and how tiresome it is to “Search for a crawled property name”.
Recently I found out that wildcard works. No, even two wildcards work!
In this example I need crawled property started from ows and contains doc and type:
SharePoint 2010/2013/2016/2019 product trial/evaluation keys
SharePoint 2019 Server is available to download from Microsoft Evaluation Center:
SharePoint Server 2016:
SharePoint Server 2016 @ Microsoft Download Center
Microsoft SharePoint Server 2013
Step-by-step guide – how to setup SharePoint with AutoSPInstaller
for developers: https://developer.microsoft.com/en-us/microsoft-365/dev-program (no credit card required)
Problem: When you patch SharePoint or perform database-attach migration or just do Test-SPContentDatabase, sometimes you can see errors with category “SiteOrphan”. Although it says “UpgradeBlocking : False”, Ignoring this error may cause severe issues, even data loss.
Continue reading
(the article is under construction)
the quick and easy way which can be used in your lab environment, as well in test and even in production and later be scaled-out, as performance and/or availability requirements grows up
Assume 3-tier topology – Front-End Server, Batch-Processing Server and SQL Server. Accounts according to least privilege principle.
Treat all server names, account names and domain names in this article are “for example”, i.e. you should use your own names.
What you must already have/get:
Prepare (request) hardware (virtual machines):
SP16SQL1 for SQL Server 2016
refer to Microsoft SharePoint 2016 requirements for hardware specifications, but as minimum:
Install MS Windows Server 2016 with GUI.
Configure time zone and time, static IP, name, language, region.
Add to domain.
Add App Server role, install updates, check event logs, resolve errors if any.
SP16WFE1 and SP16BPS1 for MS SharePoint
refer to Microsoft SharePoint 2016 requirements for hardware specifications, but as minimum:
Install MS Windows Server 2016 with GUI.
Configure time zone and time, static IP, name, language, region.
Add to domain.
Add App Server role, install updates, check event logs, resolve errors if any.
Create (request) AD accounts:
– SQL-Adm
– SQL-Svc
– SP-Adm
– SP-Farm
– SP-Svc
– SP-PortalAppPool
– SP-ProfilesAppPool
– SP-CacheSuperUser
– SP-CacheSuperReader
– SP-ProfileSync
– SP-SearchService
– SP-SearchContent
– SP-ExcelUser
– SP-VisioUser
– SP-PerfPointUser
and
– SP_farm_administrators security group
add SP-Adm (and personal admin accounts) to SP_farm_administrators group
provide “Replicate Directory Changes” AD permissions to SP-ProfileSync account (refer to this how to article)
SQL Server:
add SQL-Adm to local administrators
SP Server:
add SP_farm_administrators group to local administrators group
on SQL Server:
login as SQL-Adm to install MS SQL Server 2016
since “SQL Server Management Studio” is not a part of SQL Server, but distributed separately, you need to
on SharePoint Server:
login as SP-Adm
Generally, the steps are
AutoSPInstaller is able to handle all steps, but personally I prefer to install prerequisites and SharePoint manually, and use AutoSPInstaller only to create/configure farm. If so, we will need only “Automation” folder from autospinstaller.zip
Prerequisites
I’d recommend copy all content from source SharePoint image to a folder.
run prerequisiteinstaller.exe. It will take care of
(optionally, you can run powershell:
Add-WindowsFeature Web-Server,Web-WebServer,Web-Common-Http,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-App-Dev,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Health,Web-Http-Logging,Web-Log-Libraries,Web-Request-Monitor,Web-Http-Tracing,Web-Security,Web-Basic-Auth,Web-Windows-Auth,Web-Filtering,Web-Digest-Auth,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Tools,Web-Mgmt-Console,Web-Mgmt-Compat,Web-Metabase, WAS,WAS-Process-Model,WAS-NET-Environment,WAS-Config-APIs,Web-Lgcy-Scripting,Windows-Identity-Foundation,Xps-Viewer
an then prerequisiteinstaller.exe )
It might require you to restart the server, then prerequisiteinstaller.exe will continue until you see “Installation Complete” message. Finally you must see “Installation Complete. All required prerequisites have been installed or enabled” message.
Now run setup.exe
Be ready to provide your SharePoint product key. You can use SharePoint trial key from here for test or evaluation environment.
From Server Type choose “Complete” (for SharePoint 2013 only – option chosen by default).
NB! Choose File Location on “File Location” tab. I’d recommend install SharePoint on separate drive (e.g. E:).
Note that it says: “If you intend to use this computer as a search server, the search index files will be stored on the local drive. These files can be very large , so ensure that there is sufficient free space on the selected drive. To change where Microsoft SharePoint Server 2016 will store it’s index files…”
You might say that it is possible to configure index files location during provisioning Search Index component.
Yes, I absolutely agree. But! There is also Analytics Processing Component, and during it’s work, it generates temporary files under “C:\Program Files\Microsoft Office Servers\15.0\Data\Office Server\Analytics_GUID\AE\AnalyticsProcessingComponent1” which might be very big in size, and that location could not be “legally” changed. So if you miss this point, you might be required to reinstall SharePoint binaries later. See also this.
After binaries installed, you should see “Run Configuration Wizard” “To complete configuration of your server, you must run the SharePoint Product Configuration Wizard”…
Remove the checkmark “Run the SharePoint Product Configuration Wizard now” (untick this).
I.e. Do not run Product Configuration Wizard for now. Farm will be configured later via PowerShell AutoSPInstaller script.
If you need language packs – it’s time to install language packs.
Now you are good to install Cumulative Update. Latest for test/lab environment, latest tested for production. Check updates against regressions (e.g. with Todd Klindt).
Do not run Product Configuration Wizard.
Now let us have a closer look into AutoSPInstaller Automation folder.
Ρ AutoSPInstallerInput.xml ΡΠ±ΠΈΡΠ°Π΅ΠΌ Π°ΡΡΠΈΠ±ΡΡ “read only” ΡΠ°ΠΉΠ»ΠΎΠ²ΠΎΠΉ ΡΠΈΡΡΠ΅ΠΌΡ
AutoSPInstallerInput.xml ΠΏΡΠ°Π²ΠΈΠΌ ΡΠ°ΠΊ:
<PIDKey></PIDKey> Π²Π±ΠΈΠ²Π°Π΅ΠΌ ΠΊΠ»ΡΡ (ΠΌΠΎΠΆΠ½ΠΎ ΡΡΠΈΠ°Π»ΡΠ½ΡΠΉ ΠΎΡΡΡΠ΄Π°, ΠΏΠΎΡΠΎΠΌ Π²ΡΡΡΠ½ΡΡ ΡΠΌΠ΅Π½ΠΈΠΌ Π½Π° ΠΏΠΎΡΡΠΎΡΠ½Π½ΡΠΉ)
<SKU>Enterprise</SKU> Π²Π±ΠΈΠ²Π°Π΅ΠΌ Standard ΠΈΠ»ΠΈ Enterprise (ΠΊΠ»ΡΡ ΡΠΎΠ³Π΄Π° Π΄ΠΎΠ»ΠΆΠ΅Π½ Π±ΡΡΡ ΡΠΎΠΎΡΠ²Π΅ΡΡΡΠ²ΡΡΡΠΈΠΉ)
<AutoAdminLogon Enable=”false” Password=”” /> Π²Π±ΠΈΠ²Π°Π΅ΠΌ true ΠΈ ΠΏΠ°ΡΠΎΠ»Ρ, Π΅ΡΠ»ΠΈ Ρ
ΠΎΡΠΈΠΌ ΡΡΠΎΠ±Ρ ΡΠ΅ΡΠ²Π΅Ρ ΠΊΠ°ΠΆΠ΄ΡΠΉ ΡΠ°Π· ΡΠ°ΠΌ Π»ΠΎΠ³ΠΈΠ½ΠΈΠ»ΡΡ (ΠΏΡΠ΅Π΄ΠΏΠΎΠ»Π°Π³Π°Π΅ΡΡΡ Π½Π΅ΡΠΊΠΎΠ»ΡΠΊΠΎ ΠΏΠ΅ΡΠ΅Π·Π°Π³ΡΡΠ·ΠΎΠΊ)
<Passphrase></Passphrase> Π²Π±ΠΈΠ²Π°Π΅ΠΌ ΠΏΠ°ΡΠΎΠ»Ρ/ΠΊΠ»ΡΡ (ΠΈΡΠΏΠΎΠ»ΡΠ·ΡΠ΅ΡΡΡ Π΄Π»Ρ ΠΏΡΠΈΡΠΎΠ΅Π΄ΠΈΠ½Π΅Π½ΠΈΡ Π΄ΠΎΠΏΠΎΠ»Π½ΠΈΡΠ΅Π»ΡΠ½ΡΡ
ΡΠ΅ΡΠ²Π΅ΡΠΎΠ² ΠΊ ΡΠ΅ΡΠΌΠ΅)
<Account… Π²Π΅Π·Π΄Π΅, Π³Π΄Π΅ Π²ΡΡΡΠ΅ΡΠ°Π΅ΠΌ DOMAIN\ ΠΈΠ»ΠΈ @domain, ΠΈΡΠΏΡΠ°Π²Π»ΡΠ΅ΠΌ Π½Π° Π½Π°ΡΠΈ ΡΠ΅Π°Π»ΡΠ½ΡΠ΅ Π΄Π°Π½Π½ΡΠ΅ ΡΠ°ΠΊ:
<Username>DOMAIN\SP_Farm</Username> , Π·Π°ΠΌΠ΅Π½ΡΠ΅ΠΌ DOMAIN Π½Π° Π½Π°ΡΡΠΎΡΡΠ΅Π΅ ΠΈΠΌΡ Π½Π°ΡΠ΅Π³ΠΎ Π΄ΠΎΠΌΠ΅Π½Π°, ΠΎΡΡΠ°Π²Π»ΡΠ΅ΠΌ Π½Π°Π·Π²Π°Π½ΠΈΠ΅ ΠΈ ΠΈΠΌΡ ΡΡΡΡΠΊΠΈ (SP_Farm) ΠΊΠ°ΠΊ Π΅ΡΡΡ
<Password></Password> Π²Π±ΠΈΠ²Π°Π΅ΠΌ ΠΏΠ°ΡΠΎΠ»Ρ
<Email>spfarm@domain.com</Email> Π²Π±ΠΈΠ²Π°Π΅ΠΌ e-mail
<CentralAdmin Provision=”true”>… ΡΡΠ°Π²ΠΈΠΌ ΠΏΠΎΡΡ ΠΊΠ°ΠΊΠΎΠΉ ΡΠ΄ΠΎΠ±Π½ΠΎ, Π½Π°ΠΏΡΠΈΠΌΠ΅Ρ <Port>2013</Port>
<Database> ΠΏΠ΅ΡΠ²ΠΎΠ΅ ΡΠΏΠΎΠΌΠΈΠ½Π°Π½ΠΈΠ΅ Π΄Π΅Π»Π°Π΅ΠΌ ΡΠ°ΠΊ
<DBServer></DBServer> Π²Π±ΠΈΠ²Π°Π΅ΠΌ Π°Π»ΠΈΠ°Ρ Π΄Π»Ρ SQL Server (Π½Π°ΠΏΡΠΈΠΌΠ΅Ρ <DBServer>SP3SQLAL</DBServer>)
DBInstance=”SERVER\INSTANCE” ΠΏΡΠ°Π²ΠΈΠΌ Π½Π° ΡΠΎΠ»ΡΠΊΠΎ ΠΈΠΌΡ ΡΠ΅ΡΠ²Π΅ΡΠ° (Π½Π°ΠΏΡΠΈΠΌΠ΅Ρ, DBInstance=”SP3SQL1″)
<DBPrefix>AutoSPInstaller</DBPrefix> ΠΌΠ΅Π½ΡΠ΅ΠΌ Π½Π° ΡΠ΄ΠΎΠ±Π½ΡΠΉ Π½Π°ΠΌ, Π½Π°ΠΏΡΠΈΠΌΠ΅Ρ <DBPrefix>SP</DBPrefix>
ΠΎΡΡΠ°Π»ΡΠ½ΡΠ΅ ΡΠΏΠΎΠΌΠΈΠ½Π°Π½ΠΈΡ <Database> Π½Π΅ ΡΡΠΎΠ³Π°Π΅ΠΌ (ΠΎΡΡΠ°Π²Π»ΡΠ΅ΠΌ ΠΏΡΡΡΡΠΌΠΈ ΠΊΠ°ΠΊ Π΅ΡΡΡ)
<ManagedAccounts> Π΄ΠΎΠΌΠ΅Π½ ΠΈ ΠΏΠ°ΡΠΎΠ»Ρ ΠΌΠ΅Π½ΡΠ΅ΠΌ Π½Π° ΡΠ²ΠΎΠΉ, Π²ΡΡ ΠΎΡΡΠ°Π»ΡΠ½ΠΎΠ΅ β Π½Π°Π·Π²Π°Π½ΠΈΡ Π°ΠΊΠ°ΡΠ½ΡΠΎΠ² ΠΈ ΡΠ°ΠΌΠΈ Π°ΠΊΠ°ΡΠ½ΡΡ β ΠΎΡΡΠ°Π²Π»ΡΠ΅ΠΌ ΠΊΠ°ΠΊ Π΅ΡΡΡ
<Logging><LogDiskSpaceUsageGB></LogDiskSpaceUsageGB> ΠΏΠΎΡΡΠ°Π²ΠΈΡΡ ΠΏΡΠΈΠ΅ΠΌΠ»Π΅ΠΌΠΎΠ΅ Π΄Π»Ρ ΡΠ²ΠΎΠ΅Π³ΠΎ Π΄ΠΈΡΠΊΠΎΠ²ΠΎΠ³ΠΎ ΠΏΡ-Π²Π° Π·Π½Π°ΡΠ΅Π½ΠΈΠ΅, Π½Π°ΠΏΡΠΈΠΌΠ΅Ρ 5
<AppManagementService Π΅ΡΠ»ΠΈ Π²Ρ Π² ΡΠΎΡΡΠΎΡΠ½ΠΈΠΈ ΡΡΠΎ ΡΠ΄Π΅Π»Π°ΡΡ, ΡΠΎ ΠΎΡΡΠ°Π²Π»ΡΠ΅ΠΌ Provision=”true”
ΠΈ ΡΠ»Π΅Π΄ΡΠ΅ΠΌ ΠΈΠ½ΡΡΡΡΠΊΡΠΈΡΠΌ, Π½Π°ΠΏΡΠΈΠΌΠ΅Ρ Setting up your App domain for SharePoint 2013
ΠΈΠ½Π°ΡΠ΅ – ΡΡΠ°Π²ΠΈΠΌ Provision=”false”
ΠΠΎΡΠ»Π΅Π΄Π΅ΠΉΡΡΠ²ΠΈΡ:
<AutoAdminLogon Enable=”false” Password=”” /> ΡΡΠΈΡΠ°Π΅ΠΌ ΠΏΠ°ΡΠΎΠ»Ρ
<Passphrase></Passphrase> ΡΡΠΈΡΠ°Π΅ΠΌ
ΠΏΠΎΠΏΡΠ°Π²ΠΈΡΡ ΠΏΠ°ΡΠ°ΠΌΠ΅ΡΡΡ Π»ΠΎΠ³ΠΈΡΠΎΠ²Π°Π½ΠΈΡ ΠΏΠΎΠ΄ ΡΠ΅Π±Ρ
Π΅ΡΠ»ΠΈ Π΅ΡΡΡ exchange, ΠΌΠΎΠΆΠ½ΠΎ Π½Π°ΡΡΡΠΎΠΈΡΡ OutgoingEmail ΠΈ ΡΠ°ΠΌ Exchange
Notes:
if you plan federated SharePoint environment, i.e. having Publishing (Service) Farm and Consuming (Content) Farm – plan for SQL aliases carefully.
Sources:
Brian Lalancette: AutoSPInstaller
Technet: Account permissions and security settings in SharePoint 2013
Technet: Install SharePoint 2013
Technet: Hardware and software requirements for SharePoint 2013
CodePlex: Automated SharePoint 2010/2013 PowerShell-based installation script
Technet: virtual environment for SharePoint 2013
Setting up your App domain for SharePoint 2013
F5 Load Balancing for SharePoint 2016
Management Tools Basic+Complete;