exploresharepointfeatures

Moving from a domain authentication between ADFS authentication and on premise AD authentication is becoming a not uncommon activity these days, partly because incorporating ADFS into your on-premises farm is the first step in moving either completely or partially into SharePoint Online.

Step 1. You need to move the content db to the target farm and attach it. users wont be able to access until you do the user migration.

Step 2. User Migration – Script is given below for getting list of users and migrate.

#Start

Set-PSDebug -Strict
add-pssnapin microsoft.sharepoint.powershell -erroraction 0

# Select Options
Write-Host -ForegroundColor Yellow “‘Document’ will create a CSV dump of users to convert. ‘Convert’ will use the data in the CSV to perform the migrations.”
Write-Host -ForegroundColor Cyan “1. Document”
Write-Host -ForegroundColor Cyan “2. Convert”
Write-Host -ForegroundColor Cyan ” ”
[int]$Choice = Read-Host “Select an option 1-2: ”

switch($Choice)
{
1 {[bool]$convert = $false}
2 {[bool]$convert = $true}
default {Write-Host “Invalid selection! Exiting… “; exit}
}
Write-Host “”

$objCSV = @()
[string]$csvPath = Read-Host “Please enter the path to save the .csv file to. (Ex. C:\migration)”
if ((Test-Path -LiteralPath $csvPath) -eq $false) {
Write-Host “Invalid path specified! Exiting…”; exit
}

if($convert-eq $true)
{
$objCSV = Import-CSV “$csvPath\MigrateUsers.csv”

foreach ($object in $objCSV)
{
$user = Get-SPUser -identity $object.OldLogin -web $object.SiteCollection
write-host “Moving user:” $user “to:” $object.NewLogin “in site:” $object.SiteCollection
move-spuser -identity $user -newalias $object.NewLogin -ignoresid -Confirm:$false
}
}
else
{
[string]$oldprovider = Read-Host “Enter the Old Provider Name (Example -> Domain\ or i:0#.f|MembershipProvider|) ”
[string]$newprovider = Read-Host “Enter the New User Provider Name (Example -> Domain\ or i:0e.t|MembershipProvider|) ”
[string]$newsuffix = Read-Host “Enter the UPN suffix for the new provider, if desired (Example -> @domain.com) ”
[string]$newGroupProvider = Read-Host “Enter the New Group Provider Name (Example -> Domain\ or c:0-.t|MembershipProvider|domain.com\) ”

# Select Options
Write-Host -ForegroundColor Yellow “Choose the scope of the migration – Farm, Web App, or Site Collection”
Write-Host -ForegroundColor Cyan “1. Entire Farm”
Write-Host -ForegroundColor Cyan “2. Web Application”
Write-Host -ForegroundColor Cyan “3. Site Collection”
Write-Host -ForegroundColor Cyan ” ”
[int]$scopeChoice = Read-Host “Select an option 1-3: ”

switch($scopeChoice)
{
1 {[string]$scope = “Farm”}
2 {[string]$scope = “WebApp”}
3 {[string]$scope = “SiteColl”}
default {Write-Host “Invalid selection! Exiting… “; exit}
}
Write-Host “”
if($scope -eq “Farm”)
{
$sites = @()
$sites = get-spsite -Limit All
}
elseif($scope -eq “WebApp”)
{
$url = Read-Host “Enter the Url of the Web Application: ”
$sites = @()
$sites = get-spsite -WebApplication $url -Limit All
}
elseif($scope -eq “SiteColl”)
{
$url = Read-Host “Enter the Url of the Site Collection: ”
$sites = @()
$sites = get-spsite $url
}

foreach($site in $sites)
{
$webs = @() #needed to prevent the next foreach from attempting to loop a non-array variable
$webs = $site.AllWebs

foreach($web in $webs)
{
# Get all of the users in a site
$users = @()
$users = get-spuser -web $web -Limit All #added “-limit” since some webs may have large user lists.

# Loop through each of the users in the site
foreach($user in $users)
{
# Create an array that will be used to split the user name from the domain/membership provider
$a=@()
$displayname = $user.DisplayName
$userlogin = $user.UserLogin

if(($userlogin -like “$oldprovider*”) -and ($objCSV.OldLogin -notcontains $userlogin))
{
# Separate the user name from the domain/membership provider
if($userlogin.Contains(‘|’))
{
$a = $userlogin.split(“|”)
$username = $a[1]

if($username.Contains(‘\’))
{
$a = $username.split(“\”)
$username = $a[1]
}
}
elseif($userlogin.Contains(‘\’))
{
$a = $userlogin.split(“\”)
$username = $a[1]
}

# Create the new username based on the given input
if ($user.IsDomainGroup) {
[string]$newalias = $newGroupProvider + $username
} else {
[string]$newalias = $newprovider + $username + $newsuffix
}

$objUser = “” | select OldLogin,NewLogin,SiteCollection
$objUser.OldLogin = $userLogin
$objUser.NewLogin = $newAlias
$objUser.SiteCollection = $site.Url

$objCSV += $objUser
}
}
}
$site.Dispose()
}

$objCSV | Export-Csv “$csvPath\MigrateUsers.csv” -NoTypeInformation -Force
}

#End

csv format is as below.

You can use below scrip to update Audit settings in SharePoint online using powershell csom. For updating in all site, just loop through all site collections and update it.

#Load SharePoint CSOM Assemblies

[System.Reflection.Assembly]::LoadFile(“<dllPath>\Microsoft.SharePoint.Client.dll”) | Out-Null

[System.Reflection.Assembly]::LoadFile(“<dllPath>\Microsoft.SharePoint.Client.Runtime.dll”) | Out-Null

#$SiteUrl = “https://emiratesgroup.sharepoint.com/sites/spdev&#8221;

$Password = ConvertTo-SecureString “<enter pswd here>” -AsPlainText –Force

$User = “jo@domain.com”

$credentials = New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials($User, $Password)

$SiteUrl = $object.SiteCollection

$Context = New-Object Microsoft.SharePoint.Client.ClientContext($SiteUrl)

$Context.Credentials = $credentials

$spoSite = $Context.Site

$Context.Load($spoSite)

$Audit = $spoSite.Audit

$Context.Load($Audit)

$Context.ExecuteQuery()

$All = [Microsoft.SharePoint.Client.AuditMaskType]::All;

$None = [Microsoft.SharePoint.Client.AuditMaskType]::None;

$CheckIn = [Microsoft.SharePoint.Client.AuditMaskType]::CheckIn;

$CheckOut = [Microsoft.SharePoint.Client.AuditMaskType]::CheckOut;

$ChildDelete = [Microsoft.SharePoint.Client.AuditMaskType]::ChildDelete;

$CheckIn = [Microsoft.SharePoint.Client.AuditMaskType]::CopyCheckIn;

$Move = [Microsoft.SharePoint.Client.AuditMaskType]::Move;

$ObjectDelete = [Microsoft.SharePoint.Client.AuditMaskType]::ObjectDelete;

$ProfileChange = [Microsoft.SharePoint.Client.AuditMaskType]::ProfileChange;

$SchemaChange = [Microsoft.SharePoint.Client.AuditMaskType]::SchemaChange;

$Search = [Microsoft.SharePoint.Client.AuditMaskType]::Search;

$SecurityChange = [Microsoft.SharePoint.Client.AuditMaskType]::SecurityChange;

$Undelete = [Microsoft.SharePoint.Client.AuditMaskType]::Undelete;

$Update = [Microsoft.SharePoint.Client.AuditMaskType]::Update;

$View = [Microsoft.SharePoint.Client.AuditMaskType]::View;

$Workflow = [Microsoft.SharePoint.Client.AuditMaskType]::Workflow;

$Audit.AuditFlags = $Update, $Undelete, $SecurityChange

$Audit.Update()

$spoSite.AuditLogTrimmingRetention = 90

$spoSite.TrimAuditLog = $true

$Audit.Update()

$Context.ExecuteQuery()

write-host “updated for site:” $object.SiteCollection

Microsoft Teams

The new chat-based workspace in Office 365. Microsoft Teams is an entirely new experience that brings together people, conversations and content—along with the tools that teams need—so they can easily collaborate to achieve more. It’s naturally integrated with the familiar Office applications and is built from the ground up on the Office 365 global, secure cloud. 

Chat for today’s teams

A hub for teamwork

Customizable for each & every team

Security Teams Trust

• Microsoft Teams is available to Office 365 commercial customers with one of the following plans: Business Essentials, Business Premium, and Enterprise E1, E3 and E5. Microsoft Teams will also be available to customers who purchased E4 prior to its retirement.

Problem

This issue most frequently occurs because the Community Sites Feature site feature, the SharePoint Server Publishing site feature, or the SharePoint Server Publishing Infrastructure site collection feature is currently enabled or was previously enabled for the affected site. 

SharePoint doesn’t support creating a template from a site where publishing or community features were enabled

More Information

Resolution

In order to get around this issue you need to update a single property page value in your SPWeb object for the site you are trying to save as a template and you are good to go. The property is called SaveSiteAsTemplateEnabled. We need to set that property to true that’s all

You can use the below sample script for the same in SPO

#Load SharePoint CSOM Assemblies

[System.Reflection.Assembly]::LoadFile(“C:\***\Microsoft.SharePoint.Client.dll”) | Out-Null

[System.Reflection.Assembly]::LoadFile(“C:\***\Microsoft.SharePoint.Client.Runtime.dll”) | Out-Null

#Variables for Processing

$SiteUrl = “https://sharepointcollabs.sharepoint.com/sites/pdkmtest&#8221;

# Get a reference to the target site

$password = Read-Host –Prompt “Enter password” -AsSecureString

$credentials = New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials(“****@domain.com”, $password)

#Set up the context

$Context = New-Object Microsoft.SharePoint.Client.ClientContext($SiteUrl)

$Context.Credentials = $credentials

# Update the property bag value and set it  to the string value “true”

$Context.Web.AllProperties[“SaveSiteAsTemplateEnabled”] = “true”

# Commit the property change to server

$Context.Web.Update()

$Context.ExecuteQuery()

Now if you navigate to the Save site as a template page using the URL directly it will show fine and it will allow you to save the site as a template which stores a copy in the Solution gallery of the site collection

You can view the Crawl Logs in SharePoint Online using the Office 365’s eDiscovery site template and by granting the eDiscovery managers security group the appropriate permissions to read crawl logs from your tenant.

Create  a new subsite of eDiscovery case site template under eDiscovery site.

Navigate to your case site and now create a new eDiscovery set either using the left-side navigation or using the +new item under ‘Identify and Hold’ section.

•  Give it a name.
•  In the Sources section, click the ‘Add & Manager Source’ link, which will open a popup box. In this popup box, in the Locationssection, ensure you add all the Site Collection URLs that contain searchable content and for which you want to collect the crawl logs. After adding all the sources, then click Ok. Here is a screenshot from my tenant
• You can click on the ‘Get Statistics’ button to show the Items count and size.
• You can also click on the ‘Preview Results’ button which open a popup, then click on the ‘SharePoint’ tab to view the results listed.
•  Finally, ‘Save’ your eDiscovery set.

 Now create a new Query. You can do this from left-side navigation or using the +new item link under ‘Search and Export’.

• Give it a name
• For ‘Sources’ click on ‘Modify Query Scope’ and in the pop select the eDiscovery set that was created in step 5.
• Now click on the ‘Search’ button to see the statistics (items and size) updated under Sources and also check the results listed in theSharePoint tab down below.
• Save your query.

Open up your Query and click the ‘Export’ button at the bottom of the page. This will lead to Export: New item page. In this page, we don’t have to change anything as we are not concerned with Exchange mailbox logs or the versions of SharePoint documents.

Note: If you checked the ‘Include versions for SharePoint documents’ checkbox, then be aware that this could increase the file size of the export depending on the size of your libraries that has versioning enabled.

Click OK & Download the report