MVP - Most Valuable Professional
rss

Just can't get enough of IT

This blog is about mostly anything in IT. But the primary focuses are Microsoft technologies like Exchange Server, Microsoft 365, Microsoft Teams, and Cloud Security.
Thomas Stensitzki | MVP
Thomas Stensitzki | MVP

MVP LogoThomas Stensitzki is a leading technology consultant focusing on the Microsoft messaging and collaboration technologies and the owner of Granikos GmbH & Co. KG.

He is an MVP for Office Apps & Services since 2018.

Thomas is an MCT Regional Lead for Germany and delivers Microsoft Learning training courses for Office 365, Microsoft Teams, and Exchange Server.

He holds Master certifications as Microsoft Certified Solutions Master Messaging and as Microsoft Certified Master for Exchange Server 2010. These certifications make him a subject matter expert for any messaging topic related to Microsoft Exchange, Exchange Online, Microsoft 365, and hybrid configurations.

Follow Thomas: LinkedIn, Twitter

His sessions: https://sessionize.com/thomas-stensitzki

MVP Blog: https://blogs.msmvps.com/thomastechtalk
Personal blog: http://justcantgetenough.granikos.eu
Personal website: http://www.stensitzki.de
Thomas' Tech Talk: youtube.com/ThomasStensitzki

Contact Thomas at thomas@mcsmemail.de

 

On February 26, 2015
0 Comment
3986 Views

When you maintain a number of servers which require to trigger the same scheduled task manually, you can simplify the process by triggering the scheduled task remotely.

In this example, I assume that the script is being executed on a dedicated management server (aka job server) within an Exchange Server 2013 environment. The scheduled task must exist on all servers having the same name.

Create a simple PowerShell script at a file location of your choice (i.e. D:\Scripts\Start-RemoteScheduledTasks.ps1)

$cimSession = New-CimSession -ComputerName SERVER1,SERVER2,SERVER3,SERVER4
Start-ScheduledTask TASKNAME -CimSession $cimSession
Remove-CimSession $cimSession

Now create a new shortcut on your server desktop with the following configuration:

Target: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "& D:\Scripts\Start-RemoteScheduledTasks.ps1"

If required, select "Run as Administrator" in Shortcut -> Advanced settings.

Enjoy.

 


This post has been published originally on my legacy blog SF-Tools.

Read More »
Last updated: 2017-10-10

Picture of four audio cassettesDescription

This script removes the proxy address(es) for a selected protocol from mail-enabled public folders.

Any proxy address with a given protocol is removed from the proxy addresses list.

The script can fix the alias of mail-enabled public folders as well. The code used is based upon a blog post by Shay Levy.

 

Examples

# EXAMPLE 1
# Check mail enabled public folders for proxy addresses having "MS:" as a protocol type.
# Do not remove and update addresses, but log found addresses to RemovedAddresses.txt

.\Clean-MailEnabledPublicFolders.ps1 -ProtocolToRemove "MS:*" 

# EXAMPLE 2
# Check mail enabled public folders for proxy addresses having "MS:" as a protocol type.
# Remove and update addresses and log found addresses to RemovedAddresses.txt

.\Clean-MailEnabledPublicFolders.ps1 -ProtocolToRemove "MS:*" -UpdateAddresses

 

Version History

  • 1.0, Initial community release
  • 1.1, FixAlias added, cleanup logic changed
  • 1.2, Some minor PowerShell updates

 

Links

 

Follow

 

Additional Note

This Powershell script has been optimized using the ISESteroids™ add-on. Learn more about ISESteroids™ here.

 

 

Read More »
Last updated: 2020-03-12 | NOTE: If you are still using v2.1 update to themost recent 

 

Exchange Server 2013 Exchange Server 2016 Description

This script deletes all Exchange and IIS logs older than X days from all Exchange 2013+ servers that are fetched using the Get-ExchangeServer cmdlet.

The Exchange log file location is read from the environment variable and used to build an administrative UNC path for file deletions.

Optionally, you can use the Active Directory configuration partition to determine the Exchange install path dynamically, if supported in your Active Directory environment.

  • It is assumed that the Exchange setup path is IDENTICAL across all Exchange servers, when not using the UseDynamicExchangePaths parameter
  • The IIS log file location is read from the local IIS Metabase of the LOCAL server where the script is executed and is used to build an administrative UNC path for IIS log file deletions
  • It is assumed that the IIS log file location is identical across all Exchange servers
  • Use IsEdge switch when running on an Exchange Server holding the EDGE role

Examples

# EXAMPLE 1
# Delete Exchange and IIS log files older than 14 days 

.\Purge-LogFiles -DaysToKeep 14

# EXAMPLE 3
# Delete Exchange and IIS log files older than 7 days with automatic discovery

.\Purge-LogFiles -DaysToKeep 7 -Auto

# EXAMPLE 3
# Delete Exchange and IIS log files older than 7 days with automatic discovery and send email report

.\Purge-LogFiles -DaysToKeep 7 -Auto -SendMail -MailFrom postmaster@sedna-inc.com -MailTo exchangeadmin@sedna-inc.com -MailServer mail.sedna-inc.com

# EXAMPLE 4
# Delete Exchange and IIS log files older than 14 days, but copy files to a central repository and compress the log files before final deletion

.\Purge-LogFiles -DaysToKeep 14 -RepositoryRootPath \\OTHERSERVER\OtherShare\LOGS -ArchiveMode CopyZipAndDelete

# EXAMPLE 5
# Delete Exchange Server, IIS, and HTTPERR log files older than 7 days, and send an HTML email. Identify Exchange file paths using AD configuration objects.

.\Purge-LogFiles.ps1 -DaysToKeep 7 -SendMail -MailFrom postmaster@sedna-inc.com -MailTo exchangeadmin@sedna-inc.com -MailServer mail.sedna-inc.com -UseDynamicExchangePaths -IncludeHttpErr

Version History

  • 2.3 Option for HTTPERR added, Option for dynamic Exchange install paths added, Html formatting added, tested with Exchange Server 2019
  • 2.21 Issue #12 fixed
  • 2.2 Minor fixes, but no changes
  • 2.14 Issue #9 fixed | IsEdge parameter added
  • 2.13 Issue #7 fixed | SendMail switch query
  • 2.11 Issue #6 fixed | Missing Remove-Item cmdlet
  • 2.1 Logfile archiving and archive compressions added
  • 2.0 CopyFilesBeforeDelete implemented
  • 1.93 Minor chances to PowerShell hygiene
  • 1.92 Count issue fixed to run on Windows Server 2012
  • 1.91 Write DaysToKeep to log
  • 1.9 Global functions updated (write to event log)
  • 1.8 Support for global logging and other functions added
  • 1.6 Count Error fixed 1.7 Email report functionality added
  • 1.5 Sorting of server names added and Write-Host output changed
  • 1.4 Handling of IIS default location fixed
  • 1.3 Check if running in elevated mode added
  • 1.2 Auto/Manual configuration options added
  • 1.1 Variable fix and optional code added
  • 1.0 Initial community release

 

Requirements

  • This PowerShell script requires the GlobalFunctions module, described here.
    When using PowerShell 5 or later you can simply use Install-Module GlobalFunctions to install the module to your system.
  • Windows Server 2012 R2 or newer
  • ActiveDirectory PowerShell module
  • Exchange 2013+ Management Shell

 

Links

 

Additional Credits

Brian Reid, C7 Solutions, http://www.c7solutions.com/2013/04/removing-old-exchange-2013-log-files-html

 

Follow

 

Read More »

Exchange Server 2013 LogoUninstalling Exchange Server 2013 will fail if the PowerShell MachinePolicy or UserPolicy is set by GPO.

You will receive an error message referencing Microsoft KB article 981474, which refers primarily to Exchange Server 2010.

Screenshot showing the PowerShell Execution Policy Error

 

The following PowerShell command removes the GPO setting.

Set-ItemProperty -Path HKLM:\SOFTWARE\Policies\Microsoft\Windows\PowerShell -Name ExecutionPolicy –Value ""

After setting the ExecutionPolicy attribute to an empty string, Exchange Server 2013 can be uninstalled successfully.

 

Links

 


Do you plan to deploy Exchange Server 2016 or do you plan to go hybrid with Office 365?
Check out the enterprise technology services provides by Granikos http://www.granikos.eu/en

Read More »
Last updated: 2016-11-28

Description

The script sends a given number of test emails to a configured SMTP host for test purposes (primarily Exchange queues, transport agents, or anti-virus engines).

Do not forget to adjust script variables to suit your local Exchange infrastructure.

 

Examples

# EXAMPLE 1
# Send 10 normal emails
.\Send-TestMail.ps1 -Normal -MessageCount 10

# EXAMPLE 2
# Send an Eicar test email
.\Send-TestMail.ps1 -Eicar

 

Version History

  • 1.0, Initial community release

 

Links

 

Follow

 

 

Read More »