Granikos Technology Blog

Die Installation und Einrichtung eines Windows Servers den Betrieb von Exchange Server 2019 ist nicht kompliziert. Jedoch sind einige Dinge zu beachten und zu konfigurieren, bevor eine Installation von Exchange Server 2019 durchgeführt wird. In diesem Artikel finden Sie sowohl Informationen für die Vorbereitung des Windows Server 2019 Systems, als auch für die Installation Exchange Server 2019.

In diesem Artikel wird die folgende Konstellation betrachtet:

• Windows Server 2019, Desktop-Edition
• Exchange Server 2019, Postfach-Rolle 

Die unten aufgeführte Checkliste passt nicht auf jede Exchange Server Umgebung. Nutzen Sie diese Checkliste als Vorlage für Ihre eigenen Checkliste zur Installation von Exchange Server. Insbesondere für den Fall einer Recovery-Installation ist eine erprobte Standard-Checkliste hilfreich und stressmindernd. 

Auf GitHub finden Sie eine Excel-Checkliste, die Sie bei der Installation von Exchange Server 2019 unterstützt. Passen Sie Excel-Checkliste Ihren Bedürfnissen an.

Empfehlungen

• Die Installationsmedien für Exchange Server 2019 werden nur für das aktuelle und das vorherige kumulative Update (CU) über das Volumenlizenzportal (VLSC) angeboten. Daher empfehle ich Ihnen dringend, ein lokales Repository für die Exchange Server 2019 ISO-Dateien einzurichten und dieses Repository auch in eine Datensicherung mit aufzunehmen.
   
• Binden Sie die Exchange Server ISO-Datei immer auf einem zuverlässigen Weg ein.
  Die Einbindung über einen Netzwerkpfad ist keine zuverlässige Einbindung. Sollte die Netzwerkverbindung während der Installation von Exchange Server 2019 gestört werden, enden Sie mit hoher Wahrscheinlichkeit mit einer korrupten Exchange Server Installation. Solch eine Installation lässt sich weder weiter installieren, noch deinstallieren.
  Der bessere Weg ist das Kopieren der ISO-Datei in das lokale Dateisystem des Servers, auf den Exchange Server installiert werden soll, und die lokale Einbindung direkt im Dateisystem des Servers.
   
• Die Vorbereitung des Active Directory kann auf unterschiedlichen Computersystemen durchgeführt werden. Sie verfügen als Exchange Administrator eventuell nicht über die alle notwendigen Berechtigungen, um die notwenigen Anpassungen im Active Directory durchführen zu können. Wenn Sie über die Berechtigung zur Aktualisierung des Active Directory Schemas, der Gesamtstruktur und der Domäne verfügen, achten Sie unbedingt darauf, dass das Computersystem in der gleichen Active Directory Site platziert ist, wie der Domain Controller mit der SchemaMaster FSMO-Rolle.
  Weitere Informationen über die Active Directory Anforderungen finden Sie in der Exchange Server Online Dokumentation.

Vorbereitung

• Download aktuelles Exchange Server 2019 CU
• Download .reg-Dateien zur Anpassung der Registry für Exchange Server Best Practices
  • https://github.com/Apoc70/SetupExchangeServer2019
• Download Visual Studio C++ Blibliotheken
  • Visual C++ Redistributable Packages for Visual Studio 2013
  • Visual C++ Redistributable for Visual Studio 2012
• Installieren Sie immer die aktuellste verfügbare Version der jeweiligen C++ Bibliotheken
  • Prüfung auf mögliche Updates der C++ Bibliotheken
• Download .NET Framework 4.8
• Download PowerShell-Skript für Exchange Server HealthCheck nach der Installation
  • https://github.com/dpaulson45/HealthChecker
• Prüfen Sie, dass der Systemdienst "Remote Registry" nicht durch eine Gruppenrichtlinie deaktiviert ist
• Bereitstellung eines offiziellen TLS-Zertifikates für den gewünschten Exchange Namensraum der Domäne
  Das Zertifikat ist entweder:
  • ein Wildcard-Zertifkat,
    z.B.: *.varunagroup.de
  • ein SAN-Zertifikat mti einem Eintrag für den AutoDiscover-Endpunkt und einem Name für alle Client-Exchange-Dienste (https, POP, IMAP) und einem Namen für den E-Mail-Verbindungen (SMTP)
    z.B.: autodiscover.varunagroup.de, owa.varunagroup.de, mail.varunagroup.de

Checkliste - Exchange Server 2019 - Postfach-Rolle

Links

• GitHub-Seite für Feedback und Erweiterungswünsche
• Virtualisierung von Exchange Server 2019 in Zeiten von 48 Cores und MetaCache-Datenbank
• Vorbereitung von Active Directory und Domänen

Viel Spaß mit Exchange Server 2019!

In der Standardkonfiguration werden im Task Manager im Reiter Performance keine Informationen über die im Betriebssystem vorhandenen Disks angezeigt.

Um die Disk Performance anzuzeigen, gegen Sie wie folgt vor

1. Starten Sie eine administrative Kommandozeilensitzung
2. Rufen Sie den Task Manager über die Kommandozeile mit taskmgr auf
3. Führen Sie in der Kommandozeile folgenden Befehl aus: diskperf -Y
4. Schließen Sie den Task Manager und rufen ihn erneut mit taskmgr auf

Anschließend sehen Sie die Performance der Laufwerke im Reiter Performance.

Erfolgreiche Implementierung von Office 365 mit der Granikos GmbH & Co. KG http://www.granikos.eu.

Sometimes you have the same scheduled task configured for manual execution available across different servers. Instead of triggering the start manually on each server by logging on remotely, you can trigger the scheduled task on each server by using Remote PowerShell.

The following example triggers the configured scheduled task My-Manual-Task on server MYSERVER01 to MYSERVER06.

$cimSession = New-CimSession -ComputerName MYSERVER01,MYSERVER02,MYSERVER03,MYSERVER04,MYSERVER05,MYSERVER06

Start-ScheduledTask My-Manual-Task -CimSession $cimSession

Remove-CimSession $cimSession

Enjoy Remote PowerShell

You are unsure what Office 365 has to offer for your business? We are here to help you get the best out of Office 365. Contact us at info@granikos.eu or visit our website.  

Problem

After configuring Access Services you cannot deploy Access custom web apps from Access 2013 - an error with a Correlation ID occurs.

Reason

As if it´s not inconvenient enough to configure the SharePoint Access Services Requirements (e.g. AppStore with DNS), the SQL Server Configuration can be the cause, too. In the SharePoint Site Content overview you can see the faulty deployed App and in it`s details the following error:

The database server is temporarily unavailable.
Details: The sp_configure value 'contained database authentication' must be set to 1 in order to alter a contained database. You may need to use RECONFIGURE to set the value_in_use. ALTER DATABASE statement failed.

Solution

You need to enable the SQL Server 2012 Feature Contained Database Authentication if you receive this error. You can do this in the Management Studio via this T-SQL statement:

SP_CONFIGURE 'contained database authentication', 1;
GO
RECONFIGURE;
GO

Enjoy SharePoint!

The following PowerShell scripts have been published by our Exchange and Office 365 experts to the technical community at TechNet Gallery. Please use the GitHub repositories to report issues or to file feature requests.

General

• GlobalFunctions Module
  A module to provide centralized logging capabilities. This script is a *must have* for other Exchange 2013/2016/2019 modules if mentioned in the notes section of the script.
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/210/globalfunctions-shared-powershell-library
  • PowerShell Gallery: https://www.powershellgallery.com/packages/GlobalFunctions

Office 365

• Test Office 365 Domain Availability
  Using this script you can test the domain availability in Office 365 and Azure AD.
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/296/test-office-365-domain-availability 
  • Github: https://github.com/Apoc70/Test-DomainAvailability 
     
• Test thumbnailPhoto for Azure AD guest users
  Using this script you can update the default guest user profile photo.
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/1708/set-thumbnailphoto-for-azure-ad-guest-users 
  • Github: https://github.com/Apoc70/Set-GuestUserPhoto 

Exchange Server 2013 / 2016 / 2019

• Exchange Environment Report v2
  This script creates an HTML report showing the following information about an Exchange 2019, 2016, 2013, 2010, and, to a lesser extent, 2007 and 2003 environment.
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/1718/exchange-environment-report-v2
  • Github: https://github.com/Apoc70/Get-ExchangeEnvironmentReport
     
• Report for enabled client protocols
  This script gathers a list of enabled users for a selected Exchange Server client protocol.
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/1815/report-for-enabled-client-protocols
  • Github: https://github.com/Apoc70/Get-EnabledProtocolReport
     
• Export delegate and SMTP forwarding information for Exchange (Online) mailboxes
  PowerShell script to export mailbox delegates, SMTP forwarding inbox rules, and mailbox SMTP forwarding information or compliance auditing.
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/1693/export-mailbox-delegates-and-smtp-forwarding-information
  • Github: https://github.com/Apoc70/Get-DelegatesAndForwardingRules
     
• Manage Master Category List for Shared Mailboxes and Teams
  C# solution to export/import/copy the master category list to other users/shared mailboxes or even Microsoft Teams calendar.
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/1423/manage-master-category-list-for-shared-mailboxes-and-teams
  • Github: https://github.com/Apoc70/MailboxCategoryListManager
     
• Create a new Room Mailbox with Security Groups
  A script to create a new room mailbox with associated full access and/or send-as security groups.
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/337/create-a-new-room-mailbox-with-security-groups
  • Github: https://github.com/Apoc70/New-RoomMailbox
     
• Export all user mailbox permissions
  This script exports all mailbox folder permissions for mailboxes of the type UserMailbox. This is useful for documentation purposes prior to migration.
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/219/export-all-user-mailbox-folder-permissions 
  • Github: https://github.com/Apoc70/Get-MailboxPermissionReport 
     
• Remove Out-Of-Office rules from user mailbox
  This script searches for OOF rules created by users using the Outlook rule-tab in the OOF assistant and deletes existing OOF rules.
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/328/remove-out-of-office-rules-from-user-mailbox 
  • Github: https://github.com/Apoc70/Manage-OOF-Settings 
     
• Add resized user photos automatically
  This script supports resizing of user photos and storing the resized images in Active Directory, Exchange On-Premises, or Exchange Online.
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/307/add-resized-user-photos-automatically 
  • Github: https://github.com/Apoc70/Set-UserPictures 
     
• Parse email messages content for further processing
  This script fetches emails from a given monitoring mailbox by searching email messages for a given subject string.
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/322/parse-mailcontent 
  • Github: https://github.com/Apoc70/Parse-MailContent 
     
• Update OWA vDir config across multiple servers
  This script checks multiple Exchange Server 2013 OWA web.config files for the existence of IMCertificateThumbprint and IMServerName XML nodes required for Skype for Business OWA integration.
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/301/update-owa-vdir-webconfig-across-multiple-exchange-servers 
  • Github: https://github.com/Apoc70/Set-OwaIMSettings 
     
• Remove Orphaned HealthMailbox and SystemMailbox Accounts from MESO Container
  This script removes Active Directory objects for HealthMailboxes or SystemMailboxes in the Microsoft Exchange System Objects (MESO) container that do not have a homeMDB attribute set.
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/297/remove-orphaned-healthmailbox-and-systemmailbox-accounts-from-meso-container 
  • Github: https://github.com/Apoc70/Remove-OrphanedMailboxAccounts 
     
• Connect to Exchange Server 2013+ using remote PowerShell
  This script connects to a dedicated or a randomly selected Exchange Server using remote Powershell.
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/293/connect-to-exchange-server 
  • Github: https://github.com/Apoc70/Connect-ToExchange 
     
• Create Exchange internal/external Url based certificate requests
  This script helps to create certificate requests (CSR) based on hostnames used for internal and external URLs of Exchange Server virtual directories.
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/290/create-exchange-internalexternal-url-based-certificate-requests 
  • Github: https://github.com/Apoc70/Create-CertificateRequest  
     
• Export Messages from Transport Queue
  Script to suspend and export messages from a transport queue.
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/282/export-messages-from-message-queue 
  • Github: https://github.com/Apoc70/Export-MessageQueue  
     
• Simple import of multiple PST files for a single user
  A script to simplify the import of multiple PST files for a single user.
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/234/simple-import-of-multiple-pst-files-for-a-single-user
  • Github: https://github.com/Apoc70/Start-MailboxImport
     
• Create a new Team Mailbox with Security Groups
  A script to create a new shared mailbox with associated full access or send-as security groups.
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/239/create-a-new-team-mailbox-with-security-groups
  • Github: https://github.com/Apoc70/New-TeamMailbox
     
• Find and remove corrupt HealthMailboxes
  Script to find and remove or disable Exchange Server 2013 HealthMailboxes
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/212/find-and-remove-corrupt-healthmailboxes
  • Github: https://github.com/Apoc70/Fix-HealthMailboxes
     
• Change IIS Log File Settings
  Script to configure IIS log file location and other log file settings, especially for Exchange Server 2013/2016
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/220/change-iis-log-file-settings
  • Github: https://github.com/Apoc70/Set-Webserver
     
• Purge Exchange Server 2013/2016/2019 and IIS Log Files
  Script to purge Exchange Server 2013/2016/2019 and IIS log file remotely from a managing or job server
  • Blog: https://www.granikos.eu/de/justcantgetenough/PostId/208/purge-exchange-server-and-iis-log-files
  • Github: https://github.com/Apoc70/Purge-LogFiles
     
• Send emails for Transport Agent and Transport Rule testing
  A script for sending a defined number of emails of a certain type having a specific attachment for the testing of Transport Agents and Transport Rules
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/215/send-test-emails-to-validate-transport-rules-or-transport-agents
  • Github: https://github.com/Apoc70/Send-TestMail
     
• Copy a receive connector from one Exchange 2013 Server to multiple Exchange Servers
  Script to copy a configured Exchange Server 2013/2016/2019 receive connector from a source server to additional Exchange 2013/2016/2019 servers.
  • Github: https://github.com/Apoc70/Copy-ReceiveConnector
     
• Add remote IP-address ranges to an existing receive connector
  Add remote IP address ranges to an Exchange Server 2013/2016/2019 receive connector.
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/222/add-remote-ip-address-ranges-to-a-receive-connector
  • Github: https://github.com/Apoc70/Add-ReceiveConnectorIpAddress
     
• Copy anti-virus pattern to Exchange 2010/Exchange 2013 servers
  Script to copy anti-virus pattern files from a given source location to multiple Exchange 2010/Exchange 2013 servers
  • Github: https://github.com/Apoc70/Copy-AntiVirusPattern
     
• Gather Exchange Configuration Data
  Script to gather Exchange Org configuration data and export the configuration as text/CSV files
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/287/gather-exchange-configuration-data
  • Github: https://github.com/Apoc70/Get-ExchangeOrganizationDetails 
     
• Create a scheduled task for Exchange Server 2013+
  This script adds a new scheduled task for an Exchange Server 2013+ environment in a new task scheduler group "Exchange".
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/218/create-a-scheduled-task-for-exchange-server-2013
  • Github: https://github.com/Apoc70/New-ScheduledExchangeTask 
     
• Fetch all remote SMTP servers from Exchange receive connector logs
  This scripts fetches remote SMTP servers by searching the Exchange receive connector logs for the EHLO string.
  • Blog: -
  • Github: https://github.com/Apoc70/Get-RemoteSmtpServers
     
• Clear Private Flag on Mailbox Messages
  C# Executable to clear an item's private flag after migrating public folder content to a shared mailbox.
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/303/clear-private-flag-on-mailbox-messages
  • Github: https://github.com/Apoc70/RemovePrivateFlag 
     
• Set Mailbox Item Private Flag
  C# Executable to set an item's private flag after migrating public folder content to a shared mailbox from a legacy mailbox system.
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/379/set-mailbox-item-private-flag
  • Github: https://github.com/Apoc70/SetPrivateFlag 

Exchange Server 2007/2010

• Fetch recently created public folders
  This script gathers all public folders created during the last X days and exports the gathered data to a CSV file
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/304/fetch-recently-created-public-folders
  • Github: https://github.com/Apoc70/Get-NewPublicFolders
     
• Remove orphaned users and groups from legacy public folder ACLs
  Cleanup legacy public folder ACLs by removing orphaned other unproperly configured accounts
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/263/clean-legacy-public-folder-acl
  • Github: https://github.com/Apoc70/Clean-PublicFolderACL
     
• Exchange 2010 Public Folder Replication Report (UTF8 support)
  An updated version of the script originally posted by Mike Walker to support public folder with non-ASCII characters
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/211/exchange-public-folder-replication-report
  • Github: https://github.com/Apoc70/Get-PublicFolderReplicationReport
  • Original Post at TechNet Gallery: https://gallery.technet.microsoft.com/office/Exchange-2010-Public-944df6ee
     
• Add multiple legacy public folder replicas recursively
  Script to get more control of adding legacy public folder replicas recursively
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/217/add-multiple-legacy-public-folder-replicas-recursively
  • Github: https://github.com/Apoc70/Add-PFReplica

Other Stuff

• Convert Word documents using PowerShell
  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.
  • Blog: https://www.granikos.eu/en/justcantgetenough/PostId/353/convert-word-documents-using-powershell
  • Github: https://github.com/Apoc70/Convert-WordDocument

Please send comments, wishes, and ideas to support@granikos.eu.

Enjoy!

Need assistance with your Exchange Server Organization? You plan to upgrade your Exchange Server Organization? You plan to migrate to Office 365? Contact us: info@granikos.eu

Updates

Update 2020-10-05: Fetch all remote SMTP servers from Exchange receive connector logs added
Update 2020-05-25: TechNet Gallery links removed due to end of TechNet Gallery in mid-2020
Update 2020-02-07: Report for enabled client protocols, Exchange Environment Report - v2, Set thumbnailPhoto for AzureAD guest users added
Update 2019-05-07: Export mailbox delegates and SMTP forwarding information added
Update 2018-09-04: Add remote IP-address ranges to a receive connector added
Update 2018-06-16: Manage Master Category List for Shared Mailboxes and Teams added
Update 2018-04-29: Convert Word documents using PowerShell and Set Mailbox Item Private Flag added
Update 2018-01-24: Create a new Room Mailbox with Security Groups added
Update 2017-11-11: Export all user mailbox permissions added
Update 2017-09-22: Remove Out-Of-Office rules from user mailbox added
Update 2017-05-20: Parse email messages content for further processing and Update OWA vDir config across multiple servers added
Update 2017-03-18: Fetch recently created public folders and Clear Private Flag on Mailbox Messages added
Update 2017-02-22: Remove Orphaned HealthMailbox and SystemMailbox Accounts from MESO Container added
Update 2017-02-17: Test Office 365 Domain Availability added
Update 2017-02-13: Connect to Exchange Server 2013+ using remote PowerShell added
Update 2017-02-07: Create Exchange internal/external Url based certificate requests, Create a scheduled task for Exchange Server 2013 added
Update 2017-01-24: Gather Exchange Configuration Data added
Update 2017-01-05: Export Messages from Transport Queue added
Update 2016-11-29: Clean legacy public folder ACL added, Scripts categorized
Update 2016-11-28: Add multiple legacy public folder replicas added
Update 2016-08-18: Simple import of multiple PST files for a single user added
Update 2016-07-28: Change IIS Log File settings Github Url added, Create a new Team Mailbox with Security Groups added
Update 2016-06-04: GlobalFunctions added
Update 2015-06-18: Copy-ReceiveConnector updated
Update 2015-06-01: Exchange 2010 Public Folder Replication Report (UTF8 support)
Update 2015-05-21: Copy anti-virus pattern to Exchange 2010/Exchange 2013 servers added
Update 2014-12-10: Copy a receive connector from one Exchange Server to multiple Exchange Servers added

NoSpamProxy Azure Edition is the cloud based email security gateway of the successful NoSpamProxy family of products by Net at Work. The Azure edition of NoSpamProxy can easiliy be deployed using the Microsoft Azure Marketplace.

NoSpamProxy Azure easily connects an Office 365 tenant and offers an easy way to provide centralized email encryption and decryption with PGP and/or S/MIME for mailboxes hosted in Exchange Online. Additionally, NoSpamProxy Azure provides compliant anti-spam handling, an anti-malware component, and a large file portal.

The edition currently available in Microsoft Azure installs a NoSpamProxy single-server deployment. A single-server deployment combines the NoSpamProxy intranet role and the gateway role on a single server.

The NoSpamProxy Azure Edition is provided as BYOL (Bring Your Own License) deployment. In addition to the recurring fees for the Microsoft Azure VM you are required to buy a NoSpamProxy license. If you already own a NoSpamProxy Version 11 license, the license can be used for the NoSpamProxy Azure Edition as well.

Content

DeploymentOptions
Notes
Deployment
Links

Deployment Options

Due to the nature of a cloud service NoSpamProxy Azure can be operated in different scenarios in Microsoft Azure. By default the system is configured as a workgroup system without any Active Directory domain membership. The different operational scenarios for NoSpamProxy Azure depend on the existence of a Site-2-Site VPN between your Azure deployment and your on-premises IT infrastructure.

• Without Site-2-Site VPN to Microsoft Azure
   
  • An on-premises email server (e.g. Exchange Server or SmarterMail) utilizes NoSpamProxy Azure as an external relay for outgoing messages. Incoming messages are received by NoSpamProxy Azure and are forwarded to the on-premises email server via the internet.
     
  • Email addresses of internal recipients are maintained manually using plain text file. The file itself is imported automatically by NoSpamProxy Azure
    This is a viable option, if there aren't too many email addresses to maintain.
     
  • Good option for Office 365 customers running a cloud only deployment without any on-premises Active Directory users and mailboxes. The required import file can be created by exporting Office 365 recipients and email addresses.
     
  • RDP access to the Azure VM and NoSpamProxy Azure must be limited to an external IP address of the company network.
     
• With Site-2-Site VPN to Microsoft Azure
   
  • AN on-premises email server (e.g. Exchange Server or SmarterMail) utilizes NoSpamProxy Azure as an internal Relay for outgoing messages. Incoming messages are received by NoSpamProxy Azure and forwarded to the on-premises email servers using the Site-2-Site VPN.
     
  • Automated import of internal email recipients from a LDAP source (e.g. Active Directory)
    This option simplifies recipient maintenance, as recipients are automatically imported by NoSpamProxy Azure.
     
  • Perfect option for Office 365 customers maintaining user accounts on-premises and running Azure AD Connect or maybe even having a full Office 365 hybrid setup with centralized mail flow.
     
  • RDP access to the Azure VM and NoSpamProxy Azure restricted to internal company network(s).

Currently a direct connection to Azure AD is not supported, but it is planned for a future release.
 

Notes

• The Azure Service for NoSpamProxy Azure System requires a Reverse-DNS configuration, as any other public facing SMTP service. External SMTP servers must be able to perform a Reverse-DNS check successfully. A link on how to configure Reverse-DNS in Azure is listed in the Links section.
   
• The system name of the NoSpamProxy Azure VM should not follow internal IT naming conventions, as the name is publically resolvable. Otherwise you are going to expose your internal naming conventions.

Depending on the size of the Azure VM different throughputs can be reached in regards to emails per minute.

Tests have shown the following results for Standard A Virtual Machines:

Deployment

The following steps describe a simple deployment of NoSpamProxy Azure.

Go to Azure Marketplace and search for NoSpamProxy, select the NoSpamProxy Azure Edition.

Click Create to configure the NoSpamProxy Azure system.

Configure the required parameters as needed

• Name
  System name which is added to Azure DNS and externally resolvable.
• VM disk type
  When selecting SSD as VM disk type, you must choose an Azure VM supporting SSD in a following step.
• User name, Password
  User name of the local administrator account
  As the Azure VM is accessible via RDP from the internet by default, you should use a non-trivial user name and password.
• Subscription
  Azure subscription to add the Azure resources to.
• Resource group
  Resource group for the new Azure resources. The example creates a new resource group.
• Location
  Azure region for the new resource group.

Select an appropriate virtual machine type. NoSpamProxy Azure doesn't have extraordinary system requirements for processor and memory. SQL Server 2014 Express is downloaded and installed as part of the standard setup of NoSpamProxy. Even SQL Server 2014 Express can be run on a standard VM..

All other settings remain unchanged for this simple deployment. You can adjust the settings, if required for your individual deployment. Especially if you want to utilize exisiting resources.

• Storage Account
  Storage for Azure VM VHD files
• Virtual Network
  Azure virtual network for the new Azure VM
• Subnet
  Azure virtual network subnet
• Public IP Address
  External IP address
• Network Security Group
  Network firewall configuration

Verify the technical summary and click OK to add the configured system to your shopping cart.

Verify the selected Azure service offering and the configured virtual machine. Click Purchase to buy the selected subscription. The deployment is a so called BYOL Deployment and requires a valid NoSpamProxy trial license or an existing full license. After the NoSpamProxy setup as been completed in the virtual machine you will be redirected to a web page to request a trial license.

Connect to the newly deployed virtual machine using Remote Desktop. After first log on NoSpamProxy setup will start automatically as part of an scheduled task. The scheduled task will execute the following steps:

• Configure the preinstalled SQL Server Express Edition
• Download and setup of the most current release of NoSpamProxy
• Redirect to the NoSpamProxy Azure web page to request a trial license
• Removal of the scheduled task

Do not close or interrupt the Windows PowerShell window.

After the setup has finished the public web page of NoSpamProxy Azure Edition will be opened in Internet Explorer. After initial setup of the operating system Internet Explorer runs in secure mode. Therefore, a security warning is displayed. Just add the web page to the list of exclusions and request your personal NoSpamProxy trial license.

The program setup adds new security groups and adds the logged on account to these security groups. It is required to log off and log on again to reflect the new group memberships. This is mandatory to sucessfully manage NoSpamProxy.

After log on start the NoSpamProxy Configuration MMC to import the license.

The NoSpamProxy Configuration MMC displays the NoSpamProxy version.

After initial import of the license you can start configuring NoSpamProxy to suit your needs.

Links

• NoSpamProxy Azure
• NoSpamProxy Protection
• Blogartikel: Gateway based email encryption with Office 365
• Microsoft Azure Trial
• Microsoft Azure Reverse DNS
• Microsoft Azure Reverse DNS mit der CLI