Open Control Panel > Programs > Default Programs > Associate a file type or protocol with a program. Navigate to the .ps1 file extension and select it.  Click Change Program and navigate to the PowerShell ISE executable, which is located at C:\Windows\System32\WindowsPowerShell\v1.0\powershell_ise.exe.  The change is saved automatically after selecting the application.

1. On your ADFS server, open the ADFS snap-in, click Authentication Policies from the left tree navigation. 
2. In the Authentication Policies section on the right panel, choose Edit Global Primary Authentication.
3. Under the Intranet section, uncheck the Windows Authentication option.
4. Save the changes.

If you are receiving the following error trying to use the spell check feature in SharePoint 2010 or SharePoint 2013, chances are the issue is due to insufficient security permission on an installation folder.

This feature requires that the <server name>\Users group on the local server has Read permission to the OFFICE14/OFFICE15 folder in your installation path.  Windows grants this permission to the root of the drive by default, so if it’s missing in your installation it’s likely due to security hardening on the local server. 

To resolve the issue, grant the <server name>\Users group at least Read permission to the <drive>:\Program Files\Microsoft Office Servers\OFFICE14\ or <drive>:\Program Files\Microsoft Office Servers\OFFICE15\ directory.  Here is a snippet of what the default permissions for the <server name>\Users group looks like on a SharePoint 2013 installation, installed on the F: drive.

Exception while creating personal site: (https://personalsites.contoso.com/personal/username/) for (CONTOSO\username):
(Microsoft.Office.Server.UserProfiles.PersonalSiteCreateConfigurationException:
A failure was encountered while attempting to create the site, wildcard inclusion used to create personal sites does not exist.     at
Microsoft.Office.Server.UserProfiles.UserProfile.<>c__DisplayClass2.<CreateSite>b__0()     at
Microsoft.SharePoint.SPSecurity.<>c__DisplayClass5.<RunWithElevatedPrivileges>b__3()     at
Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)     at
Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)     at
Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)     at
Microsoft.Office.Server.UserProfiles.UserProfile.CreateSite(String strRequestUrl, Boolean bCollision, Int32 overrideCompatLevel, Int32 lcid)     at
Microsoft.Office.Server.UserProfiles.UserProfile.CreatePersonalSiteWithSQM(String mySitePortalUrl, Int32 overrideCompatLevel, Int32 lcid)).

Exception during creation of personal site from MySiteInstantiationWorkItemJobDefinition::ProcessWorkItemCore() for i:0#.w|CONTOSO\username
Microsoft.Office.Server.UserProfiles.PersonalSiteCreateConfigurationException: A failure was encountered while attempting to create the site, wildcard inclusion used to create personal sites does not exist.     at
Microsoft.Office.Server.UserProfiles.UserProfile.<>c__DisplayClass2.<CreateSite>b__0()     at
Microsoft.SharePoint.SPSecurity.<>c__DisplayClass5.<RunWithElevatedPrivileges>b__3()     at
Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)     at
Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)     at
Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)     at
Microsoft.Office.Server.UserProfiles.UserProfile.CreateSite(String strRequestUrl, Boolean bCollision, Int32 overrideCompatLevel, Int32 lcid)     at
Microsoft.Office.Server.UserProfiles.UserProfile.CreatePersonalSiteWithSQM(String mySitePortalUrl, Int32 overrideCompatLevel, Int32 lcid)     at
Microsoft.Office.Server.UserProfiles.UserProfile.CreatePersonalSite(Int32 lcid)     at
Microsoft.Office.Server.UserProfiles.MySiteInstantiationWorkItemJobDefinition.ProcessWorkItemCore(SPWorkItemCollection workItems, SPWorkItem workItem, MySiteInstantiationWorkItemJobState timerJobState) StackTrace:  at
Microsoft.Office.Server.Native.dll: (sig=2e6bd61f-fab5-45d9-95e0-1298f4064064|2|microsoft.office.server.native.pdb, offset=131CE) at
Microsoft.Office.Server.Native.dll: (offset=21BFD)

MySiteInstantiationJob:ProcessWorkItem: ProcessWorkItemCore for My Site Instantiation for: 'i:0#.w|CONTOSO\username' failed.
Error Message: A failure was encountered while attempting to create the site, wildcard inclusion used to create personal sites does not exist.

Now, you may be scratching your head knowing that you have the personal site managed path created on the web application hosting the Personal Site site collections, so why can't it find the correct managed path.  Well, in fact the User Profile application is not looking at the list of managed paths on the web application, it’s looking at the list of managed paths defined on the SPContentService.  To find out what managed paths you have defined on your Content Service, you can run this bit of PowerShell from a SharePoint PowerShell console window:

Get-SPManagedPath -HostHeader

This will likely output the following:

Notice you don’t see the "personal” Wildcard Inclusion managed path you are likely expecting to see, which is the cause of our failure.  To add the necessary managed path, execute the following PowerShell from a SharePoint console window:

New-SPManagedPath -RelativeURL "personal" -HostHeader

To verify the command added the managed path correctly, re-execute the following PowerShell from a SharePoint console window:

Get-SPManagedPath –HostHeader

You should now see the new HH managed path, of type WildcardInclusion:

To better understand the types of messages you can craft to users, below are samples of some of the different message options, and the corresponding PowerShell variables used to create the message.  The PowerShell code at the end of the page will leverage the sample variables and set the message on every content database in the SharePoint 2013 farm.

Single Day Maintenance Planned

$maintenanceStartDate  = "9/28/2013 08:00:00 AM" # Date when the maintenance will start
$maintenanceEndDate    = "9/28/2013 02:00:00 PM" # Date when the maintenance will stop
$notificationStartDate = "9/23/2013 06:00:00 AM" # Date when the message will start being displayed
$notificationEndDate   = "9/28/2013 10:00:00 PM" # Date when the message will stop being displayed
$maintenanceLink       = ""                      # This link will only appear if the maintenance duration is defined.
$maintenanceType       = "MaintenancePlanned"    # OPTIONS ARE: MaintenancePlanned | MaintenanceWarning
$readOnlyDays          = 0   # duration days
$readOnlyHours         = 0   # duration hours. 
$readOnlyMinutes       = 0   # duration minutes only appears if days and minutes are both zero

Multi-day Maintenance Planned

$maintenanceStartDate  = "9/27/2013 08:00:00 AM" # Date when the maintenance will start
$maintenanceEndDate    = "9/28/2013 02:00:00 PM" # Date when the maintenance will stop
$notificationStartDate = "9/23/2013 06:00:00 AM" # Date when the message will start being displayed
$notificationEndDate   = "9/28/2013 02:00:00 PM" # Date when the message will stop being displayed
$maintenanceLink       = ""                      # This link will only appear if the maintenance duration is defined.
$maintenanceType       = "MaintenancePlanned"    # OPTIONS ARE: MaintenancePlanned | MaintenanceWarning
$readOnlyDays          = 0   # duration days
$readOnlyHours         = 0   # duration hours. 
$readOnlyMinutes       = 0   # duration minutes only appears if days and minutes are both zero

Single Day Maintenance Warning

$maintenanceStartDate  = "9/27/2013 08:00:00 AM" # Date when the maintenance will start
$maintenanceEndDate    = "9/27/2013 02:00:00 PM" # Date when the maintenance will stop
$notificationStartDate = "9/23/2013 12:00:00 AM" # Date when the message will start being displayed
$notificationEndDate   = "9/27/2013 02:00:00 PM" # Date when the message will stop being displayed
$maintenanceLink       = ""                      # This link will only appear if the maintenance duration is defined.
$maintenanceType       = "MaintenanceWarning"    # OPTIONS ARE: MaintenancePlanned | MaintenanceWarning
$readOnlyDays          = 0   # duration days
$readOnlyHours         = 0   # duration hours. 
$readOnlyMinutes       = 0   # duration minutes only appears if days and minutes are both zero

Multi-day Maintenance Warning

$maintenanceStartDate  = "9/27/2013 08:00:00 AM" # Date when the maintenance will start
$maintenanceEndDate    = "9/28/2013 02:00:00 PM" # Date when the maintenance will stop
$notificationStartDate = "9/23/2013 06:00:00 AM" # Date when the message will start being displayed
$notificationEndDate   = "9/28/2013 02:00:00 PM" # Date when the message will stop being displayed
$maintenanceLink       = ""                      # This link will only appear if the maintenance duration is defined.
$maintenanceType       = "MaintenanceWarning"    # OPTIONS ARE: MaintenancePlanned | MaintenanceWarning
$readOnlyDays          = 0   # duration days
$readOnlyHours         = 0   # duration hours. 
$readOnlyMinutes       = 0   # duration minutes only appears if days and minutes are both zero

Single Day Maintenance Warning With a Duration Greater Than Zero

$maintenanceStartDate  = "9/28/2013 08:00:00 AM" # Date when the maintenance will start
$maintenanceEndDate    = "9/28/2013 02:00:00 PM" # Date when the maintenance will stop
$notificationStartDate = "9/23/2013 06:00:00 AM" # Date when the message will start being displayed
$notificationEndDate   = "9/28/2013 02:00:00 PM" # Date when the message will stop being displayed
$maintenanceLink       = ""                      # This link will only appear if the maintenance duration is defined.
$maintenanceType       = "MaintenanceWarning"    # OPTIONS ARE: MaintenancePlanned | MaintenanceWarning
$readOnlyDays          = 1   # duration days
$readOnlyHours         = 6   # duration hours. 
$readOnlyMinutes       = 0   # duration minutes only appears if days and minutes are both zero

Single Day Maintenance Warning With a Duration Less Than Zero and a Hyperlink

$maintenanceStartDate  = "9/28/2013 08:00:00 AM" # Date when the maintenance will start
$maintenanceEndDate    = "9/28/2013 02:00:00 PM" # Date when the maintenance will stop
$notificationStartDate = "9/23/2013 06:00:00 AM" # Date when the message will start being displayed
$notificationEndDate   = "9/28/2013 02:00:00 PM" # Date when the message will stop being displayed
$maintenanceLink       = "https://www.bing.com"   # This link will only appear if the maintenance duration is defined.
$maintenanceType       = "MaintenanceWarning"    # OPTIONS ARE: MaintenancePlanned | MaintenanceWarning
$readOnlyDays          = -1  # duration days
$readOnlyHours         = 0   # duration hours. 
$readOnlyMinutes       = 0   # duration minutes only appears if days and minutes are both zero

Single Day Maintenance Warning With a Duration Greater Than Zero and a Hyperlink

$maintenanceStartDate  = "9/28/2013 08:00:00 AM" # Date when the maintenance will start
$maintenanceEndDate    = "9/28/2013 02:00:00 PM" # Date when the maintenance will stop
$notificationStartDate = "9/23/2013 06:00:00 AM" # Date when the message will start being displayed
$notificationEndDate   = "9/28/2013 02:00:00 PM" # Date when the message will stop being displayed
$maintenanceLink       = "https://www.bing.com"   # This link will only appear if the maintenance duration is defined.
$maintenanceType       = "MaintenanceWarning"    # OPTIONS ARE: MaintenancePlanned | MaintenanceWarning
$readOnlyDays          = 1   # duration days
$readOnlyHours         = 6   # duration hours. 
$readOnlyMinutes       = 0   # duration minutes only appears if days and minutes are both zero

Multi-day Maintenance Warning with Duration Less Than Zero and a Hyperlink

$maintenanceStartDate  = "9/28/2013 08:00:00 AM" # Date when the maintenance will start
$maintenanceEndDate    = "9/29/2013 10:00:00 PM" # Date when the maintenance will stop
$notificationStartDate = "9/23/2013 06:00:00 AM" # Date when the message will start being displayed
$notificationEndDate   = "9/29/2013 10:00:00 PM" # Date when the message will stop being displayed
$maintenanceLink       = "https://www.bing.com"   # This link will only appear if the maintenance duration is defined.
$maintenanceType       = "MaintenanceWarning"    # OPTIONS ARE: MaintenancePlanned | MaintenanceWarning
$readOnlyDays          = -1  # duration days
$readOnlyHours         = 0   # duration hours. 
$readOnlyMinutes       = 0   # duration minutes only appears if days and minutes are both zero

This PowerShell code leverages the variables used in the samples above to set the message on every content database in the farm.

$maintenanceWindow = New-Object Microsoft.SharePoint.Administration.SPMaintenanceWindow
$maintenanceWindow.MaintenanceEndDate    = $maintenanceEndDate
$maintenanceWindow.MaintenanceStartDate  = $maintenanceStartDate
$maintenanceWindow.NotificationEndDate   = $notificationEndDate
$maintenanceWindow.NotificationStartDate = $notificationStartDate
$maintenanceWindow.MaintenanceType       = $maintenanceType
$maintenanceWindow.Duration              = New-Object System.TimeSpan( $readOnlyDays, $readOnlyHours, $readOnlyMinutes, 0)
$maintenanceWindow.MaintenanceLink       = $maintenanceLink

Get-SPContentDatabase | % {
    $_.MaintenanceWindows.Clear()
    $_.MaintenanceWindows.Add($maintenanceWindow)
    $_.Update()
}

Get-SPContentDatabase | % { $_.MaintenanceWindows.Clear(); $_.Update() }