About Me

My photo
Muthupet, TamilNadu, India
SharePoint 2010

Wednesday, December 23, 2020

Onedrive not provision new O365 user

As we have checked the the users Onedrive is not getting provisioned.

Hence would request you to check the below commands to provision the Onedrive and ask any Global admin to run the commands.

Connect-sposervice
Request-SPOPersonalSite -UserEmails $useremailid@domainname.com

Sunday, May 3, 2020

Take ownership over My Sites / Personal site SharePoint Online

Add an Administrator account (or, for example, Company Administrator group) into Site Collection Administrators list for each of Personal (i.e. My) Sites at SharePoint Online instance.

Under the SharePoint Online tenant admin portal, you can go to User Profiles -> Setup My Sites. From here, you can add additional owners to new My Sites and set the secondary owner of the site collection when it is deleted. As noted above, this would only apply the admin settings to new My Sites after the settings are applied.
Adding an additional admin after the site is created is a little trickier but can be done by the tenant administrator. 
The SharePoint Online PowerShell Management suite should be good enough to handle this task.
$tenant = "contoso"    
$site = "user1_contoso_com"  
$user = "admin@contoso.onmicrosoft.com"  
Set-SPOUser -Site https://$tenant-my.sharepoint.com/personal/$site `
    -LoginName $user -IsSiteCollectionAdmin $true

Tuesday, June 18, 2019

Nintex Workflow Not responding

I found the below solution to clear the workflow history

Here are the scripts we need to test in the test environment that will clear the workflow history.  In production I want to clear everything before January 1 2018.  We can be more aggressive than that in test. 

The only thing I ask is that we do not run this against Global Accounting in test.  I need to make sure they are no longer using this data for auditing purposes. 

The production scripts will need to be run off working hours. 

This make take a few days to complete for each site collection.


NWAdmin.exe –o PurgeHistoryListData -siteUrl <site collection URL> -lastActivityBefore 2018-01-01 00:00 -state COMPLETED

NWAdmin.exe –o PurgeHistoryListData -siteUrl <site collection URL> -lastActivityBefore 2018-01-01 00:00 -state CANCELLED??????????????

NWAdmin.exe –o PurgeHistoryListData -siteUrl <site collection URL> -lastActivityBefore 2018-01-01 00:00 -state ERROR

Cloud Collaboration

Exchange Online:

Exchange now support 150MB email message,
It's quite increase from previous limit as 35MB. But so as to user that
Kind of big size email in the actual environment we have lost of consideration
About their laptop performance, receiver's message inbound limit etc..

we can user Set-MailboxPlan and maxsendsize and maxreceivesize

Get-MailboxPlan | f1 name, maxsendsize, maxreceivesize, isdefault

Set-MailboxPlan ExchangeonlineEnterprise -ezoxx
-MaxsendSizw 10MB -MaxReceiveSize 10MB


Recover – Powershell
Get-mailbox -SoftdeletedMailbox

to get GUID (Mailbox GUID)

deleted get-mailbox -SoftdeletedMailbox -identity MBName | f1 'guid'

I plan to move this mail box to new mailbox

active get-mailbox -identity NEWMBname | f1 'guid'

get GUID for active and deleted mail box

New-MailboxRestoreRequest -SourceMailbox 'guid'
 -TargetMailbox guid -AllowlegacyDNMsmatch

----------------------------------------------------------------------------

Teams:

Teams in one of the communication platform in off 365.
Chat chat with team members (Managing complex project .. across the world we can work effectively
Groups Create own group or teams (creating groups rather than email) it will more powerful for our internal communication make a quick decision easily
Messages Calender's schedules and meetings notification
Files One drive file / team files
Teams are backed by O365 Groups, so when you create a team, you create a group. There are a set of cmdlets provided for operating on the core team and its settings (new-team, get-team, set-team), managing team users (add-teamuser, remove-teamuser), as well as cmdlets for managing the channels of the team (new-teamchannel, remove-teamchannel). All of these cmdlets can be run as end users, but they'll work only on the teams that you own or are a member of. If you are a Global Admin or Teams Service Administrator, you'll be able to act on all teams in your organization.
Channel get email id from channel and paste it outlook, it'll email shows in a team
Book mark and save the item, and add flag for that
Connector we use this connector to connect News, Twitter, Trello and facebook
Recording / Transcripts we can recording the teams voice, also we can transcripts the recording voice's to English and spanish
when you recorded your video, more open in microsoft steam and go to the edit option and under video languages and select English and select autogenarate caption file
Ex Powershell
New-Team
   -DisplayName <String>
   [-Description <String>]
   [-MailNickName <String>]
   [-Classification <String>]
   [-Visibility <String>]
   [-Template <String>]
   [-Owner <String>]
   [-AllowGiphy <Boolean>]
   [-GiphyContentRating <String>]
   [-AllowStickersAndMemes <Boolean>]
   [-AllowCustomMemes <Boolean>]
   [-AllowGuestCreateUpdateChannels <Boolean>]
   [-AllowGuestDeleteChannels <Boolean>]
   [-AllowCreateUpdateChannels <Boolean>]
we can add all o365 apps / and private app to teams..    [-AllowDeleteChannels <Boolean>]
   [-AllowAddRemoveApps <Boolean>]
https://www.youtube.com/watch?v=_Cw9uXfgTLQ    [-AllowCreateUpdateRemoveTabs <Boolean>]
   [-AllowCreateUpdateRemoveConnectors <Boolean>]
Powershell step by step    [-AllowUserEditMessages <Boolean>]
https://blogs.technet.microsoft.com/skypehybridguy/2017/11/07/microsoft-teams-powershell-support/    [-AllowUserDeleteMessages <Boolean>]
   [-AllowOwnerDeleteMessages <Boolean>]
   [-AllowTeamMentions <Boolean>]
   [-AllowChannelMentions <Boolean>]
   [<CommonParameters>]

SharePoint Online:


https://www.youtube.com/watch?v=rEy2mlFVWa4
http://powershell.office.com/get-started
Download the SharePoint Online Powershell
open windows ps as admin Best practices
Start-Transcript (entire transcript stored one text file c:\users\grant\doucuments\powershell_transcritps...txt) most use full to review
Get-ExecutionPolicy
Set-ExecutionPolicy RemoteSigned and say Y yes
cls
$credentials=get-credential enter credential
Azure:
Import-Module MSOnline
Connect-MsolServices -Credential $credential then test Get-MsolUser to show all the users [ to get all the command Get-Command -Module MSOnline ]
Skype:
SP
Import-Module LyncOnlineConnector Install-Module SharePointPnPPowershellonline
$lyncsesstion = New-CsOnlineSession -Credential $credential (Create session)
and Import-PSSession $lyncsesstion
SharePoint:
Import-Module Microsoft.Online.SharePoint.Powershell if any Warning user -DisableNameChecking..
then
Connect-SPOService -url https://adm.sharepoint.com -Credential $credential then test Get-SPOSite
Exchange Online:
test
Get-command -Module -tmp (tab)

Wednesday, May 15, 2019

Sharepoint Voice Search


Ever thought of implementing an shopping app like voice search in your Sharepoint site as a part of search? This neat little trick can help you achieve just that.

In the not so recent past, I was asked to improve a Sharepoint site by adding functionalities to it and keeping it up to date with the most recent trends. Voice search was one functionality that immediately came to my mind. When I found out that Microsoft did not offer it out of box, I jumped on the opportunity.

What I did here was convert the functionality into two parts. i.e. a) Voice to text conversion and b) Redirection after voice search.
Both of which were simple to achieve. For part a) , I implemented the voice to text webkit which is readily available in this link: https://tutorialzine.com/2017/08/converting-from-speech-to-text-with-javascript

The webkit allows you to start and stop recording and also auto stop if you want to specify a time period. I went ahead with auto stop and hooked the text thus converted with a redirect to the Sharepoint search page with the text as q query in the query string. i.e.https://xyz.sharepoint.com/sites/sp2013/search/pages/results.aspx?k=(Voice to text converted text)
Then its just a matter of hooking up the search functionality to the Sharepoint search box via the javascript that contains your webkit functionality. You can add a fancy mic like logo as a button for your voice search and add it inside the search box or outside.

For modern sites in Sharepoint Online we could go with creating an spfx webpart and implementing the same or creating a script editor webpart in spfx, adding it to the site and then pasting the script in the script editor (considering the site is not in "no script" enviroment).

Cheers!

Tuesday, June 26, 2018

Remove orphaned Site Collection URLS with no refrence to Content Database

During the Migration or Patching..

These sites assumes that content database got removed manually and site collection entries remains in config db. you need to type your corrupt site collection names in below $CorruptSites separated by comma in below script block and run as administrator in PowerShell.

This will fully remove referred site collection from Farm.

Add-PSSnapin Microsoft.SharePoint.PowerShell $CorruptSites = "http://rk-sps.com/sites/a","http://rk-sps.com/sites/b" Function DeleteCorruptSite { param($CorruptSite) Write-Host $CorruptSite : -foreground red $site = Get-SPSite $CorruptSite $siteId = $site.Id $siteDatabase = $site.ContentDatabase $siteDatabase.ForceDeleteSite($siteId, $false, $false) Write-Host --Deleted from Content DB -foreground green } foreach ($CorruptSite in $CorruptSites) { DeleteCorruptSite $CorruptSite }

Tuesday, June 12, 2018

Working with Request Manager in SharePoint 2013

 RM rules are applied per web app, just like throttling is done in SharePoint 2010. 

At a high level, the goals of RM are this:

RM can route to WFEs with better health, keeping low-health WFEs aliveRM can identify harmful requests and deny them immediatelyRM can prioritize requests by throttling lower-priority ones (bots) to serve higher-priority ones (end-users)RM can send all requests of specific type, like search for example, to specific machinesIsolated traffic can help troubleshoot errors on one machineRM can send heavy requests to more powerful WFEs

Routing and throttling rules are implemented like this:

Routing rules route requests and are associated with MachinePoolsMachinePools contain serversServers use weights for routing – static weights and health weightsStatic weights are constant for WFEs; health weights change dynamically based on health scores

Okay, so that’s the basic overview of what they are – there should be other documentation on TechNet if you want more details on the features and use for RM.  If you’re reading this, I’m assuming you know enough about it (or are curious enough about it) that you want to actually do some work with it.  So I’m just going to throw down some PowerShell here to help get you started.  These are cmdlets that I’ve found useful when working with RM.  The basic process you go through is something like this:

Get a reference to the SPWebApplicationGet a reference to the request management settings for the web applicationCreate one or more criteriaA request must match ALL criteria for a rule in order to match the rule (i.e. they are AND’d together)Get a reference to a machine pool, or create a new one if neededAdd the rule

Let’s walk through an example now:

#Get a reference to the SPWebApplication
$w = Get-SPWebApplication -identity http://foo

#Get a reference to the request management settings for the web application
$rmset = $w | Get-SPRequestManagementSettings

#Create one or more criteria
$criteria = New-SPRequestManagementRuleCriteria -Property Url -Value “.*\.docx” -MatchType Regex

#Get a reference to a machine pool, or create a new one if needed
$mp = Add-SPRoutingMachinePool -RequestManagementSettings $rmset -Name MyRulePool -MachineTargets ($rmset | Get-SPRoutingMachineInfo -Name WFE1)

#Add the rule
$rmset | Add-SPRoutingRule -Name “Word Doc Rule” -Criteria $criteria -MachinePool $mp

Let’s look at that routing rule now:
$rr = $rmset | Get-SPRoutingRule -Name “Word Doc Rule”

#see the criteria
$rr.Criteria

#change the expiration date and time of the routing rule
$rr.Expiration = “12/25/2013 5:00:00 PM”

There you go – now you have a routing rule.  Creating a throttling rule is very similar:

#Add a new criteria rule that looks for OneNote requests.  It can do this by examining the UserAgent in the request and looking for the header that OneNote uses.
$criteria = New-SPRequestManagementRuleCriteria -Property UserAgent -Value “.*Microsoft Office OneNote 2010*” -MatchType Regex

#Add a throttling rule that uses the criteria rule when the server health reaches a score of 8.  
#Note that throttle rules apply to the entire web application, #not to individual machines so you don’t 
#use a machine pool with it.
$rmset | Add-SPThrottlingRule -Name “OneNote Throttle Rule” -Criteria $criteria -Threshold 8

#now view all routing rules for the web application
$rmset.RoutingRules

#View all of the throttling rules
$rmset.ThrottlingRules 

 

Let’s look a little deeper at working with Machine Pools now:

#Get all routing machines that are available
Get-SPWebApplication | Get-SPRequestManagementSettings | Get-SPRoutingMachineInfo -Availability Available

#Get every machine in a specific pool
Get-SPWebApplication | Get-SPRequestManagementSettings | Get-SPRoutingMachinePool -Name yourPoolName | % { $_.MachineTargets} | Format-Table

#Add machine WFE1 to every machine pool for a particular web application; a million thanks to Tyler who helped me with this one – I ain’t a PowerShell guy really
$a = Get-SPWebApplication -Identity http://contoso
$b = $a | Get-SPRequestManagementSettings | Get-SPRoutingMachineInfo -Name WFE1
Get-SPWebApplication | Get-SPRequestManagementSettings | Get-SPRoutingMachinePool | % { $_ | Set-SPRoutingMachinePool -machinetargets ($_.machinetargets + $b) }

#Add machine WFE1 to a specific pool
$a = Get-SPWebApplication -Identity http://contoso
$b = $a | Get-SPRequestManagementSettings | Get-SPRoutingMachineInfo -Name WFE1
$pool = $a | Get-SPRequestManagementSettings | Get-SPRoutingMachinePool -Name yourPoolName
$pool | Set-SPRoutingMachinePool -MachineTargets ($pool.MachineTargets + $b)

#Remove WFE1 from every machine pool
Get-SPWebApplication | Get-SPRequestManagementSettings | Get-SPRoutingMachineInfo -Name WFE1 | Remove-SPRoutingMachineInfo

Okay, there you have it folks.  That should give you plenty to start working with.