SharePoint and Artificial Intelligence

Cognitive Search – Azure Search with AI – 15 minutes video by Scott Hanselman and Rob Caron

Follow the blogs:

Chris McNulty, Microsoft – Enrich your SharePoint Content with Intelligence and Automation

Eric Dixon, Microsoft – Intelligent Search: Adding AI to SharePoint Search

David Lavenda, Harmon.ie – Is Microsoft Search the Solution to Finding Information in Office 365?

 

ecm.kz domain for sale

Домен ecm.kz выставлен на продажу.
Прошу 1млн 200 тыс тг.
Отвечу на разумное предложение.

Связаться со мной можно через форму:

Allow commenting on modern pages in SharePoint Online

Microsoft: “You can also select to allow or prevent commenting on modern pages. If you allow commenting, it can be turned on or off at the page level

By default both
– Allow users to create new modern pages
– Allow commenting on modern pages
are turned on (enabled)

Tenant or SharePoint admin can find settings under
SharePoint Admin Center -> Settings -> Pages

When you are creating a modern site page – there is an option “Comments” turned On by default:

And page with comments looks like:

Comments on site pages (aka modern pages) can be enabled or disabled at each of the levels:
– Tenant level
– Site (aka site collection) level
– Web (aka subsite ) level
– Page level
Here is how it is done:

LevelHow it’s doneWho can do it
TenantGUI ( SharePoint Administration)
or PowerShell
Global Administrator or
SharePoint Administrator
Site (Site Collection)PowerShellGlobal Administrator or
SharePoint Administrator
Web (Subsite)PowerShellSite Collection Administrator or Owner
(Full Control rights to web)
PageGUI (Page Editing screen)Site Member
(Edit right to page)

If commenting on modern pages disabled at higher level – lower level settings do not work. E.g. If you disable “Allow commenting on modern pages” at tenant level (it takes minutes) – the functionality will gone from all modern pages of all sites.

When you switch page comments Off – all existing comments will be hidden (but not deleted).
If you later turn comments On – comments will reappear, including Likes.

If “Allow commenting on modern pages” disabled at tenant or web level – you will not see “Comments On/Off” switch while editing page.
If “Allow commenting on modern pages” disabled at site collection level – you will see “Comments On/Off” switch while editing page, but you will not be able to turn it ON.

PowerShell

When you disable “Allow commenting on modern pages” at tenant level –
PowerShell Object (site/web) property “CommentsOnSitePagesDisabled” will not be changed for any site/web.
You can still with PowerShell set it to True/False:
“Set-PnPWeb -CommentsOnSitePagesDisabled:$false”
but it does not take any effect.

If you enable “Allow commenting on modern pages” at tenant level (it takes ~10 minutes) – the functionality will return to all modern pages and
all webs and sites properties “CommentsOnSitePagesDisabled” will ???.
You can change it with PowerShell:
“Set-PnPWeb -CommentsOnSitePagesDisabled:$false”.

# having Site Collection Admin Permissions:
# disable Comments On Site Pages for a subsite:
$webName = "SubSite_02"
Set-PnPWeb -Web $webName -CommentsOnSitePagesDisabled:$true 
# enable Comments On Site Pages for a subsite 
# (only if comments enabled at tenant level):
Set-PnPWeb -Web $webName -CommentsOnSitePagesDisabled:$false


# having global admin or SharePoint admin permissions:
# site collection:
Set-PnPTenantSite -Url $siteUrl -CommentsOnSitePagesDisabled:$true
# tenant-level Comments:
Set-PnPTenant -CommentsOnSitePagesDisabled:$true # disable
 comments
Set-PnPTenant -CommentsOnSitePagesDisabled:$false # enable comments

# does not work:
Set-PnPSite -CommentsOnSitePagesDisabled:$true

How do I know if if the page is modern page or classic page (PowerShell)?

$list = Get-PnPList "Site Pages" -Includes ContentTypes, Fields
$list.ContentTypes | ft -a
$cType = Get-PnPContentType -List $list | ?{$_.Name -eq 'Site Page'};
$cType.id
$queryString = "<View><Query><Where><Eq><FieldRef Name='ContentTypeId'/><Value Type='Text'>" + $cType.Id.StringValue + "</Value></Eq></Where></Query></View>"  
$modernPages = Get-PnPListItem -List $list -Query $queryString
$modernPages.count
$modernPages | ft -a

How do I know if the page is a Home Page (PowerShell)?

# web object contains relative link to the web's Home Page:
$web = Get-PnPWeb -Connection $siteConnection -includes WelcomePage
$web.WelcomePage

References

– Microsoft “Allow users to create and comment modern pages

See also:
Allow users to create modern pages

Note:
We did not discuss “Wiki Pages” or “Web part Pages”, we discussed only “Modern Pages” (aka Site Pages).
I have tested it all personally using Communication sites.
MS-Team (group-based) and standalone SharePoint (no-group) sites – TBP.

UPA to UIL sync

[Microsoft.Office.Server.UserProfiles.WSSProfileSynch]::ScheduleSiteForFullSynchronization()

[Microsoft.Office.Server.UserProfiles.WSSProfileSynch]::ClearSyncDataForContentDatabase()

 

SPO vs SharePoint on-prem

Microsoft “cloud first” initiative led us to the situation where SharePoint on-prem (SharePoint 2019) is just a branch (sub-project) of SharePoint Online project.

So “Hybrid” SharePoint environment is just a combination of two similar products – one in on-prem and the other one – in the cloud.

TBC…

Office Online Server (OOS)

Office Online Server unattended setup

Scenario:
1) you need to install Office Online Server as a part of process (Powershell script or DSC configuration)
2) you cannot use system (C:) drive. I.e. OOS must be installed on, e.g. D: drive

Solution: use “config.xml”.

Config.xml example:

<Configuration>
    <Logging Type="verbose" Path="d:\tmp" Template="OOServerSetup(*).log"/>
    <Display Level="none" CompletionNotice="no" />
    <INSTALLLOCATION Value="d:\Program Files\Microsoft Office Servers\"/>
    <Setting Id="USINGUIINSTALLMODE" Value="0"/>
    <Setting Id="SETUPTYPE" Value="CLEAN_INSTALL"/>
    <Setting Id="SETUP_REBOOT" Value="Never"/>
</Configuration>

Command-line run example:

setup.exe /config d:\config.xml

Powershell script example:

Start-Process "d:\source\OOS\setup.exe" -ArgumentList "/config d:\config.xml" -Wait

Powershell DSC configuration example:

include ” <INSTALLLOCATION Value=”d:\Program Files\Microsoft Office Servers\”/>”
into “d:\source\OOS\Files\SetupSilent\config.xml”, so when your LCM will run

        OfficeOnlineServerInstall OOSInstall
        {
            Ensure = "Present"
            Path = "d:\Distrs\OOS\setup.exe"
        }

by default “d:\source\OOS\Files\SetupSilent\config.xml” will be used.

 

 

 

 

===============================================================================

references:

https://docs.microsoft.com/en-us/officeonlineserver/deploy-office-online-server

 

note: 
Install the following software:
Visual C++ Redistributable Packages for Visual Studio 2013
Visual C++ Redistributable for Visual Studio 2015
Microsoft.IdentityModel.Extention.dll
is not required?

I.e. OOS farm will work, but report Unhealthy…