Modern Attachments behind a web proxy

With Exchange 2016 a huge improvement in regards of document collaboration with OneDrive for Business was introduced when you have a Hybrid configured.

You can read more about it here:

When I introduced Exchange 2016, I was more than happy to configure and make this feature available to my end-users. But after I run through the prerequisites and steps, I wasn’t able to get the option in OWA and with Outlook I received the following error:

ModernAttProxy01

The same happened when I was using Outlook for Mac. As different clients, protocols and servers where affected, I assumed a general issue and started troubleshooting.

Continue reading

Tips and tricks for DSC:Purge logfiles

Starting with Exchange 2013 an Exchange server is logging a vast amount of data. As not every installation has enough space or there is a compliance rule, which forces you not to keep log files older than x days, you might need something to delete these files.

There are several methods to achieve this. One for example is the script from fellow MCM/MCSM Thomas Stensitzki Purge-LogFiles.ps1 (read more about it on his post here).

You can run the script manually or create a scheduled task.

But when you are using Desired State Configuration (DSC), why not add the task to purge those files to your MOFs?

Continue reading

Powershell Desired State Configuration(DSC):How to enforce a consistency check?

A few month ago I started digging into Powershell Desired State Configuration (DSC). I really had a steep learning curve. The outcome could be found here:

In terms of scripts I published some, which helps you to stay on top of the whole topic:

Today I’m writing about the topic how you can enforce/trigger a consistency check on your nodes. Besides this also something you should know when you are using the built-in DSC File Resource.

Continue reading

Automate Exchange installation and configuration with DSC Part 3:Automate creation and publishing to pull server

This is the third post of a serie around DSC and my personal journey:

Part 1: Pull server (setup and querying node status)

Part 2: Configure node’s LCM in a bulk operation reading GUID from AD and using individual certificates

Part 3: Automate creation and publishing to pull server of configurations reading Configuration and Environment Data files

In this post I will cover how to create MOF files reading a Configuration,  Environment data and one CSV file.

In general you create a Configuration and an Environment Data file. In the Environment Data file you will define dedicated properties for each node if necessary.

Continue reading

Automate Exchange installation and configuration with DSC Part 2:Configure node’s LCM

This is the second post of a serie around DSC and my personal journey:

Part 1: Pull server (setup and querying node status)

Part 2: Configure node’s LCM in a bulk operation reading GUID from AD and using individual certificates

Part 3: Automate creation and publishing to pull server of configurations reading Configuration and Environment Data files

In this post I will cover how you can configure the Local Configuration Manager (LCM) of the target nodes to pull their configuration from a pull server. The challenge was to keep track of the used GUID and not to use the same certificate on all nodes in order to Securing the MOF files.

Update 28.08.2015

Update 04.09.2015

Continue reading

Automate Exchange installation and configuration with DSC Part 1:Pull server

I’m currently involved in an Exchange 2013 project. One of the goals is to get things automated and to prevent configuration drifts later in the operating phase.

I thougt this would be a great chance to have a look into Powershell Desired State Configuration (DSC). And indeed: I really like it! Especially in combination with xExchange module authored by Mike Hendrickson, Jason Walker, Michael Greene.

I’m not going to write another blog post about the module. Mike’s posts are very good and there is nothing to add. This is the start of a serie around DSC and my personal journey in accomplishing the goals that have been set:

Part 1: Pull server (setup and querying node status)

Part 2: Configure node’s LCM in a bulk operation reading GUID from AD and using individual certificates

Part 3: Automate creation and publishing to pull server of configurations reading Configuration and Environment Data files

To create a pull server for DSC you need to make your first decision: What kind of pull server you are going to install? You can choose one of the following options: HTTP, HTTPS and SMB.

I picked HTTPS as I wanted to use the PSDSCComplianceServer component, which is anyways HTTP based. The server itself is based on Windows Server 2012 R2.

Continue reading