Description

This script converts Word compatible documents to a selected format utilizing the Word SaveAs function. Each file is converted by a single dedicated Word COM instance.

The script converts either all documents in a single folder of a matching an include filter or a single file.

Currently supported target document types:

• Default --> Word 2016
• PDF
• XPS
• HTML

The conversion is handled by Word itself, utilizing the SaveAs method.

The Word.Document.SaveAs method supports the following wdFormat values:

Implemented document formats are shown in bold.

Examples

# EXAMPLE
# Convert all .doc files in E:\temp to Default

.\Convert-WordDocument.ps1 -SourcePath E:\Temp -IncludeFilter *.doc 

# EXAMPLE
# Convert all .doc files in E:\temp to XPS

.\Convert-WordDocument.ps1 -SourcePath E:\Temp -IncludeFilter *.doc -TargetFormat XPS

# EXAMPLE
# Convert a single document to Word default format

.\Convert-WordDocument.ps1 -SourcePath E:\Temp\MyDocument.doc

Version History

• 1.0, Initial community release

Links

• Download and follow at Github: https://github.com/Apoc70/Convert-WordDocument
• Download and like at TechNet Gallery: https://gallery.technet.microsoft.com/scriptcenter/Convert-Word-documents-5ccc1067
• WdSaveFormat Enumeration

Follow

• Twitter @stensitzki
• LinkedIn
• Xing

When you run software solutions that make use of TLS secured communication channels the applications need to have access to the certificate's private key. The private key is part of the certificate stored in the local certificate store of the computer. In most cases the software solution creates a new self-signed certificate and configures access rights appropriately.

When establishing TLS communication channels to external partners, the use of a public SSL/TLS certificate is a must have requirement.

The following step-by-step instructions describe how to assign Read permisson for the Email Security Solution Gateway NoSpamProxy. In this case the solution does not utilize a classic service account, but a so-called virtual service account. Virtual service accounts provide a much better access security when executing Windows services.

Step-by-Step Instructions

Step 1

Open the local computers certificate store using the MMC Snap-Ins.

Step 2

Select the certificate to use and open the context menu (right click).

Select Manage Private Keys to manage the private key permissions.

Step 3

Click Add and add the required service accounts.

In this case the virtual service accounts are part of the local computer entity. Select the local computer and not the Active Directory domain as source when searching accounts. Virtual accounts us the prefix NT Service.

Add the follow accounts to configure read access for NoSpamProxy on a server having the Gateway and Intranet role installed.

NT Service\NetatworkMailGatewayIntranetRole
NT Service\NetatworkMailGatewayManagementService
NT Service\NetatworkMailGatewayGatewayRole
NT Service\NetatworkMailGatewayPrivilegedService

Add the follow accounts to configure read access for NoSpamProxy on a server having the Gateway role installed only.

NT Service\NetatworkMailGatewayManagementService
NT Service\NetatworkMailGatewayGatewayRole
NT Service\NetatworkMailGatewayPrivilegedService

Click Check Names to verifiy the existence of the entered service accounts.

Step 4

When correctly resolved the accounts names are replaced by theis respective display names. Click OK to add the accounts. 

Step 5

Configure read access for all added service accounts and click OK.

The software solution is now capable of accessing the private key of the certificate.

Link

• Service Accounts Step-by-Step Guide, https://technet.microsoft.com/en-us/library/dd548356(v=ws.10).aspx

The SMTP Simulator project has been started due to a specific demand during a customer project. We needed a solution to test native transport of Exchange Server 2013 and third party addons to Exchange in an isolated lab envrionment having no internet access at all.

While it is pretty easy to send test emails using PowerShell, we wanted to create an automated service which is capable of:

• replies to incoming emails
• has configured internal and external SMTP domains
• creates random local email addresses
• sends emails depending on a schedule to simulate user behaviour
  • fixed number of emails per timeframe
  • random number of emails per timeframe
  • send misformed emails
• adds attachments to outgoing emails
  • documents 
  • archives / password protected archives
  • EICAR files
• simple testing of POP3/IMAP4 remote connections 
• runs as a Windows service
• has a nice web interface for simplified administration
  • access to SMTP send/receice logs

The SMTP Simulator can be used with any Message Transfer Agents (MTA), not only with Exchange. Besides testing the MTA itself, we needed to test some of the following third-party solutions:

• Anti-Malware solutions using an Exchange transport agent
• SMTP gateway solutions

Architecure overview

Web client interface

The Visual Studio solution creates a MSI installer file. The MSI package created installs the SMTP Service itself, but not the required web application (see issue #49).

Documentation is provided by the SMTP Simulator Wiki.

Open Source

The code has been published as open source at Github. Feel free to fork the solution and contribute to the code.

Report any issues or feature requests at Github.

To-Do's

The project still has some open ends and needs some love and attention. Open issues are part of the issue tracker at Github.

• https://github.com/Granikos/SMTPSimulator/issues

Main topics are:

• Authenticated login
• Rebuild of the installer to include the main service component and the web client required for management
• Enhance wiki documentation

Links

• SMTP Simulator project at Github: https://github.com/Granikos/SMTPSimulator
• SMTP Simulator Wiki at Github: https://github.com/Granikos/SMTPSimulator/wiki

The GlobalFunctions PowerShell module has been updated to support writing of log messages to the PowerShell output pipeline.

When writing to the PowerShell output pipeline, the severity level is not written to the pipeline. In most cases you will use this option for debugging purposes.

Example

# Import module first
Import-Module -Name GlobalFunctions

# Create an instance of the logger
$ScriptDir = Split-Path -Path $script:MyInvocation.MyCommand.Path
$ScriptName = $MyInvocation.MyCommand.Name
$logger = New-Logger -ScriptRoot $ScriptDir -ScriptName $ScriptName -LogFileRetention 14 

# Write an informational message to the log file only
$logger.Write('Some informational message')

# Write an informational message to the log file only
$logger.Write('Some message to log and console',0,$true)

# Write a warning level message to log file and the message only to PowerShell output pipeline
$logger.Write('Some warning message',2,$true)

Note

Remember to add the severity level when writing to console.

Read more about the GlobalFunctions module here.

You can get the source code here:

• Import from PowerShellGallery: https://www.powershellgallery.com/packages/GlobalFunctions
• Download and follow at Github: https://github.com/Apoc70/GlobalFunctions
• Download and like at TechNet Gallery: https://gallery.technet.microsoft.com/Centralized-logging-64e20f97

When you run the following cmdlet to prepare Active Directory for the installation of an Exchange Server Cumulative Update (in this case CU17) you might encounter a System.UnauthorizedAccessException. 

D:\tmp\Cu17>setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms

Microsoft Exchange Server 2013 Cumulative Update 17 Unattended Setup


Unhandled Exception: System.UnauthorizedAccessException: Access to the path 'C:\
Windows\Temp\ExchangeSetup\ExSetup.exe' is denied.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.File.SetAttributes(String path, FileAttributes fileAttributes)
   at Microsoft.Exchange.Setup.CommonBase.SetupHelper.DeleteDirectory(String pat
h)
   at Microsoft.Exchange.Bootstrapper.Setup.BootstrapperBase.CopySetupBootstrapp
erFiles()
   at Microsoft.Exchange.Bootstrapper.Setup.Setup.Run()
   at Microsoft.Exchange.Bootstrapper.Setup.BootstrapperBase.MainCore[T](String[
] args)
   at Microsoft.Exchange.Bootstrapper.Setup.Setup.Main(String[] args)

There is a simple reason for the the System.UnauthorizedAccessException:

• .NET Framework Optimization Service 

The required .NET Framework 4.6.2 had been installed just minutes before executing setup.exe. Preparation of the Active Directory schema ran without any issues. But when the /PrepareSchema call finished, the temporary folder in C:\Windows\Temp\ExchangeSetup could not be fully cleaned up, as mscorsvw.exe had an open file handle on ExSetup.exe.

Additionally, when you run Setup.exe and the folder C:\Windows\Temp\ExchangeSetup exists, the setup will not try to copy required installation files. Regardless if the folder files exists in the folder or not.

Solution

• End both mscorsw.exe processes or wait until both process have finished optimizing your .NET Framework applications
• Manully delete the folder C:\Windows\Temp\ExchangeSetup
• Run the required Exchange setup step again

D:\tmp\Cu17>setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms

Microsoft Exchange Server 2013 Cumulative Update 17 Unattended Setup

Copying Files...
File copy complete. Setup will now collect additional information needed for
installation.

Performing Microsoft Exchange Server Prerequisite Check

    Prerequisite Analysis                                     COMPLETED

Configuring Microsoft Exchange Server

    Organization Preparation                                  COMPLETED

The Exchange Server setup operation completed successfully.

Enjoy Exchange!