The Script

#Simple Server list
$servers = Get-Content C:\servers.txt
 
# Loop through all servers and check key 
foreach ($server in $servers) {
 
$REG = [Microsoft.Win32.RegistryKey]::OpenRemoteBaseKey('LocalMachine', $server)
$REGKEY = $REG.OpenSubKey("SYSTEM\CurrentControlSet\Control\Lsa")
$val = $REGKEY.GetValue("DisableLoopBackCheck")
 
# If the key is missing or not set it will be displayed in red
# If the key is set it will be displayed in green
 
if (!$val){
 
Write-Host $server "is not set"  -ForegroundColor Red
break
}
 
if ($val -ne "1"){
Write-Host $server "is not set properly"  -ForegroundColor Red
}
 
else{
Write-Host $server "is set" -ForegroundColor Green
}
}

What the Script Does

The Script:

#Modify Inputs

# Host and Drive to store the IISLogs
$Hostdir = "\\HOSTSERVER\c$" 

# Actual Location of the IIS Logs on the Server
$iislogsfolder = "c$\inetpub\logs\LogFiles\W3SVC1892304237"

#A wild card parameter to determine a file range
$thefiles = "*ex1906*"

# Create a target folder on host if does not exist
 $TARGETROOT = "$Hostdir\logs"
 if(!(Test-Path -Path  $TARGETROOT)){
 New-Item -ItemType directory -Path  $TARGETROOT
 }

# Create an export folder if it does not exist
$target = "$Hostdir\logs\export"
 if(!(Test-Path -Path  $target)){
 New-Item -ItemType directory -Path $target
 }

#Simple Server list
$servers = Get-Content C:\servers.txt

# For loop to do the work
foreach ($server in $servers)
{

#make a new folder by server name if it does not exist
 $TARGETDIR = "$target\$Server"
 if(!(Test-Path -Path  $TARGETDIR)){
 New-Item -ItemType directory -Path $TARGETDIR
 }

#Get the files
$iislogLogDir = "\\$server\$iislogsfolder"
$iislogName = Get-ChildItem "$iislogLogDir" -Recurse -Include "$thefiles" | Get-Item

#Start a loop to copy all the files to the host locatiion
foreach ($log in $iislogName) {
copy-Item -path $log $TARGETDIR
}

}
  

What the Script Does

1.  Use a list of servers to collect the data from.
2.  Create a "logs" folder on the specified drive.
3.  Create an "export" sub folder under "logs".
4.  Create a sub folder under "export" using  server name of each server.
5.  Use the wild card file name you specified to target specific files.
6.  Copy each targeted file to the correct serer name folder.

•  If you want to collet 1 file from each server, just specify use the full date name in the search input (ie 190606).
•  You can run this more than once if another file is needed and they will be added to the existing folders.
•  The "export" folder will contain all the files needed. Just compress the folder and your ready to share.

The script

# Specify which Log File
$EventLogName = “Application”
 
# Specify drive to store event logs
$drive= “c$”
 
# Specify server to store event logs
$dest = "SERVERNAME"
 
#Simple Server list
$servers = Get-Content C:\servers.txt
# For loop to do the work
foreach ($server in $servers)
{

# Create a target folder on host if does not exist
$TARGETROOT = "\\$server\$drive\logs"
if(!(Test-Path -Path  $TARGETROOT)){
New-Item -ItemType directory -Path  $TARGETROOT
}
 
# This is the WMI call to select the application log from each server
$logFile = Get-WmiObject -EnableAllPrivileges -ComputerName $server Win32_NTEventlogFile | Where-Object {$_.logfilename -eq $EventLogName}
 
# Creating a file name based on server, log and time
$exportFileName = $server + “_” + $EventLogName + “_” +(get-date -f yyyyMMdd) + “.evt”
 
# Perform the backup
$logFile.backupeventlog($TARGETROOT + “\” + $exportFileName)
 
# Create an export folder if it does not exist
$target = "\\$dest\$drive\logs\export"
if(!(Test-Path -Path  $target)){
New-Item -ItemType directory -Path $target
}
 
# Since WMI does the work on the remote machine you can’t copy to file share.
 
# This is a workaround to move to files to a single location after the backup
Move-Item $TARGETROOT\$exportFileName $target
}

# Since WMI does the work on the remote machine you can’t copy to file share.
# This is a workaround to move to files to a single location after the backup
Move-Item $TARGETROOT\$exportFileName $target
} 

What does it the script do?

1. This script will read a list of servers and backup the specified event logs to a local folder on the source servers.
2. After the backup is complete it will move the event logs files to network share specified by the destination, so all backed up files are stored in a single location.

What was done?

#########################
#Move Mail based on name#
#########################
$SrcDir = "c:\inetpub\mailroot\drop"
$DestDir = "c:\inetpub\mailroot\badmail\spmail"

if(!(Test-Path -Path c:\inetpub\mailroot\badmail\spmail)){
New-Item -ItemType directory -Path $DestDir}

$SearchString = "To: <docs72@sp2016.com>"
Get-Childitem $SrcDir -filter *.eml | ? {select-string $SearchString $_ -quiet} | move-item -Destination $DestDir

############################
#Move Mail after 10 minutes#
############################

$SrcDir = "c:\inetpub\mailroot\drop"
$DestDir = "c:\inetpub\mailroot\badmail\spmail"

if(!(Test-Path -Path c:\inetpub\mailroot\badmail\spmail)){
New-Item -ItemType directory -Path $DestDir}

Foreach($file in (Get-ChildItem $SrcDir))
{
If($file.LastWriteTime -lt (Get-Date).AddMinutes(+10))
{Move-Item -Path $file.fullname -Destination $DestDir}
}

How does SharePoint handle it?

Conclusion

How to modify the default experience for list and libraries as a user

How to modify the default experience for list and libraries as an Admin

To change disable / re-enable the modern user experience at the site collection level

#Site Collection Level Add-PSSnapin microsoft.sharepoint.powershell -ea 0 $site = Get-SPSite https://spwfe

#Disable modern Lists and libraies at the Site Collection Level $featureguid = new-object System.Guid "E3540C7D-6BEA-403C-A224-1A12EAFEE4C4" $site.Features.Add($featureguid, $true)

#Re-enable the moden expirence at the site collection Level. $featureguid = new-object System.Guid "E3540C7D-6BEA-403C-A224-1A12EAFEE4C4" $site.Features.Remove($featureguid, $true)

To change disable / re-enable the modern user experience at the web level

#Web Level Add-PSSnapin microsoft.sharepoint.powershell -ea 0 $site = Get-SPWeb https://spwfe

#Disable modern Lists and libraies at the Web Level. $featureguid = new-object System.Guid "52E14B6F-B1BB-4969-B89B-C4FAA56745EF" $site.Features.Add($featureguid, $true)

#Re-enable the moden expirence at the Web Level $featureguid = new-object System.Guid "52E14B6F-B1BB-4969-B89B-C4FAA56745EF" $site.Features.Remove($featureguid, $true)

To change disable / re-enable the modern user experience at the library level

Add-PSSnapin microsoft.sharepoint.powershell -ea 0 $web = Get-SPWeb https://spwfe $list = $web.Lists["Documents"]

#Classic setting $list.ListExperienceOptions = "ClassicExperience" $list.Update()

#Modern setting $list.ListExperienceOptions = "NewExperience" $list.Update()

#User Default $list.ListExperienceOptions = "Auto" $list.Update()

More Information

Let's look at the traffic behind the covers

Scenario 1: Auth working with port 587 over Kerberos

Scenario 2: Auth working with port 25 over NTLM

Scenario 3: Somewhat working with port 25 over NTLM

Scenario 4: Not working with port 587 over Kerberos

Why is this happening?

Get-ADUser spadmin

DistinguishedName : CN=SpAdmin,OU=SpService,DC=contoso,DC=com
Enabled : True
GivenName :
Name : SpAdmin
ObjectClass : user
ObjectGUID : 070d91df-5240-4569-8c1c-415bc9c20872
SamAccountName : SpAdmin
SID : S-1-5-21-1111111111-111111111-111111111-1111
Surname :
UserPrincipalName :

Set-ADUser spadmin -UserPrincipalName spadmin@contoso.com

Now Get it account one more time:

Get-ADUser spadmin

DistinguishedName : CN=SpAdmin,OU=SpService,DC=contoso,DC=com
Enabled : True
GivenName :
Name : SpAdmin
ObjectClass : user
ObjectGUID : 070d91df-5240-4569-8c1c-415bc9c20872
SamAccountName : SpAdmin
SID : S-1-5-21-1111111111-111111111-111111111-1111
Surname :
UserPrincipalName : spadmin@contoso.com

setspn -l contoso\spwfe

setspn -s SMTPSVC/spwfe contoso\SPWFE

Set the SPN with FQDN:

setspn -s SMTPSVC/spwfe.contoso.com contoso\SPWFE 

Checking domain DC=contoso,DC=com Registering ServicePrincipalNames for CN=SPWFE,CN=Computers,DC=contoso,DC=com: SMTPSVC/spwfe.contoso.com Updated object

Get the SPNs once again:

setspn -l contoso\spwfe

Registered ServicePrincipalNames for CN=SPWFE,CN=Computers,DC=contoso,DC=com: SMTPSVC/spwfe.contoso.com SMTPSVC/spwfe TERMSRV/SPWFE TERMSRV/spwfe.contoso.com WSMAN/spwfe WSMAN/spwfe.contoso.com RestrictedKrbHost/SPWFE HOST/SPWFE RestrictedKrb Host/spwfe.contoso.com HOST/spwfe.contoso.com

Summary

So why am I telling you this?

Issue:

Cause:

Workaround:

<system.serviceModel>
<serviceHostingEnvironment minFreeMemoryPercentageToActivateService="0" />
</system.serviceModel>

1. From IIS Manager, right click on the service web app and choose "Explore".
   
2. You will see a folder that contains the web.config.
   
3. Make a backup copy of the web.config (always a good practice).
4. Add the "minFreeMemoryPercentageToActivateService" section previously described just above the "</configuration>" closing tag.

     Example:
5. Save the changes and trigger an IISRESET.
6. Test the changes by accessing Central Admin and a Site Collection.
7. If all is good, you should be able to continue testing with your new settings.

Disable Memory Checking from a Site Web Application

<system.serviceModel>
<serviceHostingEnvironment aspNetCompatibilityEnabled="true" />
</system.serviceModel>

<system.serviceModel>
<serviceHostingEnvironment aspNetCompatibilityEnabled="true" minFreeMemoryPercentageToActivateService="0"/>
</system.serviceModel>

Important Takeaways:

• This is not a supported configuration and only should be used for testing functionally in test labs (not performance testing).
• Applying CU's may reverse this setting if web.config changes are present in the update.
• This is an IIS thing and not a SharePoint thing.
• Low memory can occur on production servers as well, even if your server is configured with 16GB's or more.
• Please do not use this setting on a production server, because if your server is running below 5% memory, it needs some attention and not a band-aid.

Incoming email automatic mode

As announced by the Windows Server team, Microsoft is deprecating the IIS 6 Management compatibility features in Internet Information Services (IIS). The automatic mode of the SharePoint incoming email feature relies on IIS 6 APIs to manage the IIS SMTP service. Because no alternative APIs exist to manage the IIS SMTP service, we are removing support for automatic mode in the incoming email feature of SharePoint Server 2019 Public Preview. Customers using incoming email are recommended to use advanced mode instead, which allows you to manually manage the IIS SMTP service and drop folder.

SMTP

SMTP and the associated management tools are deprecated. Though the functionality is still available in Windows Server 2012, you should begin using System.Net.Smtp. With this API, you will not be able to insert a message into a file for pickup; instead configure Web applications to connect on port 25 to another server using SMTP.

So, what does this all mean?

Wrapping it all up

Let's See the "Foreign Connector" solution in action!

Example:

New-ForeignConnector -Name "SharePoint Email" -AddressSpaces "SMTP:sp2019.net" -SourceTransportServers "exch-server"

New-ForeignConnector

https://docs.microsoft.com/en-us/powershell/module/exchange/mail-flow/new-foreignconnector?view=exchange-ps

Example:

Set-ForeignConnector "SharePoint Email" -DropDirectory "C:\Program Files\Microsoft\Exchange Server\V15\SharePoint" 

Set-ForeignConnector

https://docs.microsoft.com/en-us/powershell/module/exchange/mail-flow/set-foreignconnector?view=exchange-ps

Let's Recap

• SharePoint 2019 will only support "Advanced Mode" to configure incoming e-mail.
• SMTP Service is deprecated but still currently included with the latest version of Windows Server.
  Note: When products are deprecated, they can be removed at any time. So be ready.
• SharePoint does not require a local SMTP Server, only a drop location to process incoming email.
• An on-prem Exchange Server can utilize a "Foreign Connector" to route e-mail per address space to a drop location.
• Setting this up in a lab was a lot of fun. If you don't agree try it :) .

Configuration

Note: It's recommended to use account credentials that match the From address. If you wish to use credentials for a different account, ensure that account has "Send As" permission to impersonate the From address. Also, if you're using a Windows account to authenticate to the SMTP server, you can specify the user name using either the Universal Principal Name (UPN) format (user@domain.com) or the NT4 login format (DOMAIN\user). If you're using a non-Windows account to authenticate to the SMTP server, contact your email administrator to determine the correct user name format.

$key = ConvertTo-SecureString -AsPlainText -Force "application credential key"
Set-SPApplicationCredentialKey $key

Repeat the command on each additional SharePoint server in the farm, using the same application credential key.

Health Monitoring

One or more servers can't retrieve the outgoing email credentials (SharePoint Server 2019)

SharePoint Server 2019

Applies to: SharePoint Server 2019

Summary: Learn how to resolve the SharePoint Health Analyzer rule "One or more servers can't retrieve the outgoing email credentials" for SharePoint Server 2019.

Rule Name: One or more servers can't retrieve the outgoing email credentials.

Summary: At least one web application is configured to use authentication when sending email. There are one or more servers in this farm that can't retrieve the credentials used to authenticate to the outgoing email server. Without credentials, these servers can only send email anonymously.

Cause: The application credential key wasn't found on these servers or they don't have the same application credential key originally used to store the SMTP password. Every server in the farm must have an application credential key to store and retrieve the SMTP password. The application credential key must be identical on each server.

Resolution: Use the Set-SPApplicationCredentialKey command on each failing server to set the application credential key. If the current SMTP password was stored using a different application credential key, you must set the new application credential key on every server in the farm and then save the SMTP credentials again.

Testing Outgoing E-Mail with Authentication

Bonus Reading for Exchange Online Users