How To Update MySite User Access Request e-Mail   Leave a comment

Share Point Administrators will often at times Pre-Provision User’s MySites once their information has been created in Active Directory.  However, when this is done I have noticed that the “Access Request e-Mail Address” was left with “”.  This causes an issue when users request access to someone’s MySite by throwing an “Undelivered” response back to the user’s InBox.

Here is a PowerShell scripting I recently wrote to enumerate through each active MySite and update the e-mail address.  The e-Mail is derived from the UserProfile settings. Feel free to use it or improve on it.  Happy SharePointing!

# Filename: SP-UpdateMySitesAccessRequest.ps1
# Author: Paul D. Fox
# Version: 1.1
# Last Modified: 12-26-2019
# Description: This script will Update the Access Request e-mail address
# for each MySite User based on their UserProfile Settings.
# Modifications: MM/DD/YYYY – Description
# Note: Requires entering the Web Application (root) Url for MySites
# Execution: Execute from Windows or SharePoint PowerShell
# (As Administrator) with the command:
# .\SP-UpdateMySitesAccessRequest.ps1
Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue
Write-Host “Microsoft.SharePoint.PowerShell Snap-In Added…” -ForegroundColor Green

$siteUrl = Read-Host “Enter the Web Application Url []” `n

$rootSite = New-Object Microsoft.SharePoint.SPSite($siteUrl)
$spWebApp = $rootSite.WebApplication
$count = 0

foreach($site in $spWebApp.Sites)
foreach($siteAdmin in $site.RootWeb.SiteAdministrators)
#Write-Host “$siteAdmin.ParentWeb.Url – $siteAdmin.DisplayName – $siteAdmin”
if ($siteAdmin.Email -ne “”)
#Get Site Collection Administrator e-Mail
$requestAccessEmail = $siteAdmin.Email
$count = $count + 1
foreach($web In $site.AllWebs)
$web.RequestAccessEmail = $requestAccessEmail
$web.MembersCanShare = $false

#Disable “Allow members to share the site and individual files and folders”
#Disable “Allow members to invite others to the site members group”
$groups = $site.RootWeb.sitegroups
foreach ($grp in $groups)
$grp.OnlyAllowMembersViewMembership = $false;
$grp.AllowMembersEditMembership = $false;
Write-Host “Updating AccessRequest eMail for: ” $requestAccessEmail -ForegroundColor Gray
Write-Host $count “Total Access Request e-Mails Updated!” -ForegroundColor Green

Posted December 26, 2019 by Bismarck in SharePoint 2016

How To Set Title to Required in Document Libraries   Leave a comment

SharePoint SearchThe SharePoint Search Service Crawler and Indexer uses the “Title” property first when content is indexed.  A new feature in SharePoint 2016 has the crawler picking up the first line or “header” of the document to help with indexing content.  By adding a Title to documents, SharePoint search will provide a better UX (User Experience) with SharePoint’s Search Results when users are searching for content.

By default the Title content in Document Libraries is not required, leaving many lazy users not filling out this field.  This could potentially give incorrect search results or results that are confusing.

You can easily set the Title to Required by going into the Document Content Type, but if there are many Libraries in Sites and Site Collections that could be cumbersome.

You can create a Feature (List Event Receiver) when a Library is provisioned to set the Title to required, and for existing libraries that can also be accomplished via PowerShell.

In this example, I have the Title property set during the provisioning process.

Public Class TitleRequired
Inherits SPListEventReceiver
”’ A list was added.

Public Overrides Sub ListAdded(properties As SPListEventProperties)

Dim sSiteUrl As String = properties.Web.Site.Url
Dim sWebUrl As String = properties.Web.Url
Dim sLibraryName As String = properties.ListTitle
‘Note: Making the Title Column (Field) Required in a Document Library is Different from a
‘      Custom List.  The “Document” Content Type Associated with the List requires the Change.

‘      If Deactivating this Feature, you will need to Manually Set the Title Required proprety
‘      through the “Document Content Type” under “Allow Management of Content Types”.
Using site As New SPSite(sSiteUrl)
Using web As SPWeb = site.OpenWeb()
                 Dim list As SPList = web.Lists.TryGetList(sLibraryName)
Dim contentType As SPContentType = list.ContentTypes(“Document”)
Dim titleField As SPField = list.Fields(“Title”)
Dim fieldLink As SPFieldLink = contentType.FieldLinks(titleField.Id)
web.AllowUnsafeUpdates = True
                fieldLink.Required = True
web.AllowUnsafeUpdates = False
            End Using
End Using
Catch ex As Exception
‘Throw a message in the ULS Logging
Microsoft.Office.Server.Diagnostics.PortalLog.LogString(“Exception Occurred ATI.SP.ER.SetTitleRequired: {0} || {1}”, ex.Message, ex.StackTrace)
End Try
End Sub
End Class

Posted June 29, 2017 by Bismarck in SharePoint 2013, SharePoint 2016

How To Resolve Issue Opening Visual Studio 2015 Projects in Visual Studio 2017   Leave a comment

I recently upgraded to the new Microsoft Visual Studio 2017.  When I tried to open projects created in the earlier version (Visual Studio 2015), I encountered a running issue where it continuously asked to install the Visual Studio Tools for Office.  The problem was that they are already installed with Visual Studio 2017 when I selected the Office Tools & SharePoint products during the Install.

It seems the versioning has not been updated correctly during either the Migration, or the Upgrade. Since this product is so new, I don’t know if this is the official remedy but here is how I fixed it.


Open the Project File (e.g. .vbproj or .csproj) file and update the “MinimumOfficeToolsVersion” to 14.   Sometimes I noticed the value varied from 14.5 to 14.6

Happy SharePointing!

Posted March 14, 2017 by Bismarck in SharePoint 2016

How To Resolve Publishing Pages Not Created in the Correct Location   Leave a comment


You may have come across this issue in your Intranet. Let’s say you create your Intranet with several Sub-Sites and utilize the Managed Metadata Navigation to manage the Top Link Bar. This Managed Metadata Navigation is inherited across and down through all of the Sub-Sites.


Now, when you click on the ‘Add a Page’ from the “Find it at: <URL>” displays the wrong address or at most the <Root> of the Site Collection.


What you want to happen in a Publishing site, is to have the New Pages Added, added to the Pages library of the site or Sub-Site you are creating it from.


Uncheck the “Create friendly URLs for new pages automatically” in the Navigation Settings of the Site or Sub-Site should resolve this issue.





If you have the Publishing Infrastructure and Publishing Feature enabled on a Team Site, it will default to “/SitePages”. This is because by default the “Wiki Page Home Page” Site feature is enabled by default when a Team Site is provisioned. Simply Disable this feature and your New Pages will be added to the “/Pages” Library.

Happy SharePointing!

Posted December 16, 2016 by Bismarck in SharePoint 2013, SharePoint 2016

How To Remove the Recent Node on the Quick Launch without Code in SharePoint 2016   Leave a comment

You can remove the Recent Node in the Quick Launch (Current Navigation) in SharePoint 2016 without having to write code or deploy CSS changes.  This should also work on SharePoint 2013 as well.


  1. First create a New SharePoint Security Group in your Site Collection.  This group only needs “Read” permissions.


2. From “Site Settings”, “Navigation”, select the Recent Link in the Current Navigation section and click on the “Edit” menu item in the Navigation box.


3. Next, select the “Target Audience” and add the New SharePoint Permission Group you created.

That’s it.  Now all you have to do is Add users to your new group if they need to see the “Recent Node”

Posted May 11, 2016 by Bismarck in SharePoint 2013, SharePoint 2016

How To Add a Feature Stapler to My Sites and Change the Blog Title   Leave a comment

I’ve been working with SharePoint 2013 for some time now and now eagerly reviewing the new SharePoint 2016.  I noticed that when users provision their Blogs on their My Sites, the title default to “Welcome to My Blog”.  The eventual result of this becomes more apparent when they show up in the search results.

Here I decided to incorporate a feature stapler while working on a custom branded My Sites Masterpage.  This feature will, when a My Site Blog is provisioned, renames the Blog Title to “Welcome to <DisplayName>’s Blog.  Now when you search on Blogs it makes it more clear as to who blog it is.

So I in my Visual Studio Project, I created an Event Handler called “MySiteWebProvisioning” with the following code:

Imports System
Imports System.Security.Permissions
Imports Microsoft.SharePoint
Imports Microsoft.SharePoint.Utilities
Imports Microsoft.SharePoint.Workflow
Imports Microsoft.Office.Server

Public Class MySiteWebProvisioning
Inherits SPWebEventReceiver

”’ <summary>
”’ A site was provisioned.
”’ </summary>
Public Overrides Sub WebProvisioned(properties As SPWebEventProperties)

Using targetWeb As SPWeb = properties.Web
Using rootWeb As SPWeb = targetWeb.Site.RootWeb

‘* Set MySite Blog Title to Display Name’s – Blog.  When these MySite Blogs
‘* are Crawled, they will have return “User DisplayName’s – Blog rather than just “Blog".

If properties.Web.Site.HostName = “” Then
If properties.Web.WebTemplateId = “9” Then

Dim spResource As SPUserResource = properties.Web.TitleResource
Dim sWebUrl As String = properties.ServerRelativeUrl
Dim sUserDisplayName As String = properties.UserDisplayName

properties.Web.Title = sUserDisplayName + “‘s – Blog”
properties.Web.AllowUnsafeUpdates = True

Catch ex As Exception
‘Throw a message in the ULS Logging
Microsoft.Office.Server.Diagnostics.PortalLog.LogString(“Exception Occurred Ascii.SP.ER.MySiteBranding: {0} || {1}”, ex.Message, ex.StackTrace)
End Try
End If
End If

‘Update Blog MasterPage
targetWeb.MasterUrl = rootWeb.MasterUrl
targetWeb.CustomMasterUrl = rootWeb.CustomMasterUrl
targetWeb.SiteLogoUrl = rootWeb.SiteLogoUrl
targetWeb.AlternateCssUrl = rootWeb.AlternateCssUrl

End Using

End Using

End Sub

End Class

Here is the Element.xml

<?xml version=”1.0″ encoding=”utf-8″?>
<Elements xmlns=””&gt;
<Receivers >

In my Feature Stapler, I associated it with the MySite Template.  The Elements.xml for this is displayed below:


<Elements xmlns=””&gt;
<FeatureSiteTemplateAssociation Id=”c4c9b0b4-c604-4ec0-8355-3136fd02411b” TemplateName=”SPSPERS#2″ />

Happy SharePointing!

Posted February 2, 2016 by Bismarck in SharePoint 2013, SharePoint 2016

How To Import New Managed Metadata Termsets   Leave a comment

Another method of getting your Termsets into the Managed Metadata Store is of course to just import them.  I have several pre-defined termsets that you can use.

Step 1 – From the Managed Metadata Store in SharePoint Central Administration, I created a “Global Term Properties” Group.  This will be where I create termsets to be used by everything in the entire farm.


Step 2 – Upload your defined terms saved a Microsoft Excel Workbook or Comma Delimited File (.csv)


Step 3 – Review your Imported terms


To show you how I created these Excel files, I have several below that you can download, experiment with, or just use.


Posted June 26, 2015 by Bismarck in SharePoint 2013