<?xml version='1.0' encoding='UTF-8'?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:blogger="http://schemas.google.com/blogger/2008" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" version="2.0"><channel><atom:id>tag:blogger.com,1999:blog-1962846729636742616</atom:id><lastBuildDate>Mon, 07 Sep 2026 05:29:16 +0000</lastBuildDate><category>Exchange 2010</category><category>Exchange 2013</category><category>Exchange 2010 SP1</category><category>Exchange 2007</category><category>Office 365</category><category>Exchange 2010 SP2</category><category>Exchange 2013 SP1</category><category>Exchange 2010 SP3</category><category>PowerShell</category><category>Exchange</category><category>Exchange 2003</category><category>update</category><category>tool</category><category>Exchange 2016</category><category>Outlook 2010</category><category>SBS2003</category><category>Server 2012</category><category>Forefront</category><category>Outlook 2007</category><category>Vista</category><category>KEMP</category><category>Lync</category><category>Outlook 2003</category><category>Server 2012 R2</category><category>Outlook 2013</category><category>virtualisatie</category><category>Diversen</category><category>Hyper-V</category><category>Office</category><category>Server 2008 R2</category><category>Azure</category><category>Outlook 2016</category><category>Server 2008</category><category>Skype for Business Online</category><category>VMware</category><category>Exchange 5.5</category><category>Forefront UAG</category><category>Office 2010</category><category>SharePoint</category><category>Windows 7</category><category>Windows 8</category><category>Cloud PBX</category><category>Windows 8.1</category><category>Windows Phone</category><category>DPM 2007</category><category>Microsoft Teams</category><category>NetScaler</category><category>Server 2008 R2 SP1</category><category>Server 2016</category><category>Surface Hub</category><category>Windows Azure</category><category>XP</category><category>ISA</category><category>Linux</category><category>LoadGen</category><category>MOSS</category><category>Microsoft Azure</category><category>Microsoft Stream</category><category>MigrationWiz</category><category>MySQL</category><category>Phone System</category><category>SBS2008</category><category>SBS2011</category><category>Sysprep</category><category>TechEd</category><category>Visio</category><category>WSS</category><category>Windows 10</category><title>Jetze&#39;s blog</title><description>My personal blog on Exchange, Office 365 and other Microsoft technologies.</description><link>http://jetzemellema.blogspot.com/</link><managingEditor>noreply@blogger.com (Jetze Mellema)</managingEditor><generator>Blogger</generator><openSearch:totalResults>443</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1962846729636742616.post-6728619705121416427</guid><pubDate>Tue, 05 Mar 2019 11:40:00 +0000</pubDate><atom:updated>2019-03-05T12:41:04.376+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Microsoft Stream</category><category domain="http://www.blogger.com/atom/ns#">Office 365</category><title>How to access the Microsoft Stream Admin settings</title><atom:summary type="text">While reading up on Live events (preview) in Microsoft Stream, I noticed a mention off the Stream Admin settings.I was not able to locate this in the Microsoft Stream web interface, so went to the Microsoft 365 Admin center instead. But no reference to Stream here either…Turns out that the Stream Admin settings are only accessible through Stream. In order to access the Admin settings the </atom:summary><link>http://jetzemellema.blogspot.com/2019/03/how-to-access-microsoft-stream-admin.html</link><author>noreply@blogger.com (Jetze Mellema)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjedire-PWy-bfwOBd0X3PjtQtHWnEUFz8o8a_m7W3qBa9XBZH8N6i6naqaytq5ZhYprmX1nTvo-SybAE9uYqs9_Hqd-FpNrihrE0BvwPH8scULQX1AIJ7SdnlJqvO_ve6jM6O8jXg2ZA/s72-c?imgmax=800" height="72" width="72"/><thr:total>2</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1962846729636742616.post-1850852406214509594</guid><pubDate>Sat, 30 Jun 2018 13:35:00 +0000</pubDate><atom:updated>2018-07-13T09:55:00.770+02:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Exchange</category><category domain="http://www.blogger.com/atom/ns#">Office 365</category><title>Updated Connectors section in Exchange Online admin center</title><atom:summary type="text">Update July 13th, 2008: It looks like Microsoft reverted this change for now.“Constant change is here to stay.” Office 365 administrators may have noticed that Microsoft is revamping the Connectors area of the Exchange Admin Center. This section used to be a single list that displayed all connectors, which meant that it could be hard to identify the connector you were looking for.The biggest </atom:summary><link>http://jetzemellema.blogspot.com/2018/06/updated-connectors-section-in-exchange.html</link><author>noreply@blogger.com (Jetze Mellema)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjJg4dMXgknHMAH7n5iHTun__nhGMwyHn9O2rA9J41Rt1_2Hh-nEGtrThp17ixS0hgwIaxYZ2agBMzVCTsLZgSafqHR8iNQJLGKY7S9Hz2sqELgt4wNzkJNNM9gTKpSZE-XS-bcNqZjIw/s72-c?imgmax=800" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1962846729636742616.post-7360939495430921171</guid><pubDate>Tue, 22 May 2018 08:40:00 +0000</pubDate><atom:updated>2018-05-22T10:40:29.213+02:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">PowerShell</category><category domain="http://www.blogger.com/atom/ns#">tool</category><title>How to monitor a log file in real-time</title><atom:summary type="text">Recently I was working on a task where I had to monitor the log files from a ftp server. At one point I had to find out if a certain client had downloaded a file with a specific name, or look for entries from a client with a certain IP address.One way to do this is opening the log file with a text editor and use the search function. Unfortunately this approach is not an easy way to detect updates</atom:summary><link>http://jetzemellema.blogspot.com/2018/05/how-to-monitor-log-file-in-real-time.html</link><author>noreply@blogger.com (Jetze Mellema)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgP_1A8hvMnFeP71aJovpq2G-2sX6GMdpAgAuYpdaqUVur9aqJDXbdrId3k746J0Uddmsnq8wDMNo7GouG_vbcDTGYybbshznib3NKSKFMRB7sS-xpZFj0XVWAVQw1HINV57_H1S4JdMg/s72-c?imgmax=800" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1962846729636742616.post-8380619897720553717</guid><pubDate>Wed, 16 May 2018 09:09:00 +0000</pubDate><atom:updated>2018-05-16T11:09:26.727+02:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Microsoft Teams</category><category domain="http://www.blogger.com/atom/ns#">Office 365</category><title>Microsoft Teams not working for K1/F1 users</title><atom:summary type="text">I recently ran into an issue where some users could not access Microsoft Teams, even though a license was assigned. This only happened to users with a Microsoft Teams license from the ‘Deskless Worker’ suite, also known as the Kiosk, K1 or F1 SKU.The reason for this is that the tenant-wide control to enable or disable Microsoft Teams by default does not include Deskless Workers. An admin has to </atom:summary><link>http://jetzemellema.blogspot.com/2018/05/microsoft-teams-not-working-for-k1f1.html</link><author>noreply@blogger.com (Jetze Mellema)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEipH44VvW6G6uvqS867oDPZHgyqgjR0vmOOr2Ip7kKSvFVFqZRSa0ixxYta0Rlfg0U9qLAtTy2ozrM2I80AqcaXm1WZr22ZHQxvQC0AerafjWLh8_XMVRpjBh1guuU0TecERXrBS_NwTA/s72-c?imgmax=800" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1962846729636742616.post-4335902000193904923</guid><pubDate>Tue, 27 Mar 2018 12:28:00 +0000</pubDate><atom:updated>2018-03-28T10:41:38.985+02:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Exchange</category><category domain="http://www.blogger.com/atom/ns#">Office 365</category><title>Exchange Admin Center can’t handle duplicate display names</title><atom:summary type="text">If you’re managing a larger organization, or even a smaller one, chances are that some of your coworkers share the same name. From an Exchange perspective this is not supposed to be an issue as the displayName attribute does is not required to be unique. End-users who try to locate the right person in their address book can look at the additional properties such as department or email address to </atom:summary><link>http://jetzemellema.blogspot.com/2018/03/exchange-admin-center-cant-handle.html</link><author>noreply@blogger.com (Jetze Mellema)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjIAAjjD0atkV9upiJvPc2F0IFP_8-uCNq1338mpqinLFkJ8A4CaSL8WjHML-iQCHLEfv8jQCtoLvPyIOUhjd5zsFB4jCSjgEayV9J0jzshouc2_GKnf-V22zZ5NAtykXksdDRA_FsFqg/s72-c?imgmax=800" height="72" width="72"/><thr:total>2</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1962846729636742616.post-8706249479259921040</guid><pubDate>Tue, 27 Feb 2018 16:09:00 +0000</pubDate><atom:updated>2018-02-27T17:12:16.996+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Cloud PBX</category><category domain="http://www.blogger.com/atom/ns#">Office 365</category><category domain="http://www.blogger.com/atom/ns#">Phone System</category><title>Office 365 Phone System numbers, how to convert from User to Service?</title><atom:summary type="text">When porting numbers to Office 365 Phone System, the admin has to specify if the number should be a service number or a user number. The same applies when new numbers are requested. What’s the difference between the two number types, you may ask. The answer is easy.A user number is assigned to a single user.A service number is connected to a call queue, a conference bridge or an auto attendant </atom:summary><link>http://jetzemellema.blogspot.com/2018/02/office-365-phone-system-numbers-how-to.html</link><author>noreply@blogger.com (Jetze Mellema)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEihfi8X4GL-hA30ywlgvSfUgBia9SOVWKAY9Vs_zeYegQJK6SFZHkMS2FDqPLbWhYm_Ea8bIUCt5HgFYdzE6EtoZ6IY9Q4Uc-fZ3vVAd23EY_44GtgjGeDw9zbpk0ekIikqNX97USqW7g/s72-c?imgmax=800" height="72" width="72"/><thr:total>2</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1962846729636742616.post-7274852124605532493</guid><pubDate>Fri, 23 Feb 2018 14:46:00 +0000</pubDate><atom:updated>2018-02-23T15:46:10.462+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Cloud PBX</category><category domain="http://www.blogger.com/atom/ns#">PowerShell</category><category domain="http://www.blogger.com/atom/ns#">Skype for Business Online</category><category domain="http://www.blogger.com/atom/ns#">Surface Hub</category><title>Disable voicemail on a Skype meeting room accounts</title><atom:summary type="text">If you ever had to create user accounts for modern meeting room devices such as Microsoft’s Surface Hub or 3rd party devices such as the Polycom Trio 8800 you may have noticed that process is basically the same. Create a Room Mailbox with an enabled account and a password, then enable the account for Skype for Business with the Enable-CsMeetingRoom cmdlet.Recently a coworker transferred a Skype </atom:summary><link>http://jetzemellema.blogspot.com/2018/02/disable-voicemail-on-skype-meeting-room.html</link><author>noreply@blogger.com (Jetze Mellema)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEirAONxboCFXloy8FpQFVfxQ70B6dWpR1dTbp-2HrODDIzaiUO9U4Krf9OXx14ClBIOW0rW16HKjl12HzE9UKhm35dpv-cyIfEg-7Xini__KhZxeOGmWLW7tZVYdxcmGkOX3XNSSnK2Ng/s72-c?imgmax=800" height="72" width="72"/><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1962846729636742616.post-6523221923612904945</guid><pubDate>Fri, 16 Feb 2018 07:59:00 +0000</pubDate><atom:updated>2018-02-16T08:59:25.545+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Exchange 2013</category><category domain="http://www.blogger.com/atom/ns#">Exchange 2013 SP1</category><category domain="http://www.blogger.com/atom/ns#">Exchange 2016</category><category domain="http://www.blogger.com/atom/ns#">Office 365</category><title>HCW does not ‘remember’ mail transport configuration</title><atom:summary type="text">Centralized mail transport (CMT) is a hybrid mail flow scenario where all outbound email from Exchange Online is routed through on-premises servers first before sending it to the internet. It’s not really common but there are organizations with specific requirements that can be met with centralized mail transport.As you probably know, when the HCW is run for the first time, the entered </atom:summary><link>http://jetzemellema.blogspot.com/2018/02/hcw-does-not-remember-mail-transport.html</link><author>noreply@blogger.com (Jetze Mellema)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhhnzyiRHCVJHsOM2SJDBv-mNwp8H24wLMT7FUk4S6OlZ_SH0M0l0p75Az0PC0fk_XRk-coxIRChMz7MTT3pzrzZBTmb3wLmpqAz31pnin6-3FFKVje7rMx8PrTgd8J9Na1GCq_MvrtdA/s72-c?imgmax=800" height="72" width="72"/><thr:total>3</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1962846729636742616.post-8632309236872528494</guid><pubDate>Wed, 04 Oct 2017 09:47:00 +0000</pubDate><atom:updated>2017-10-04T11:51:09.545+02:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Exchange</category><category domain="http://www.blogger.com/atom/ns#">Exchange 2010</category><category domain="http://www.blogger.com/atom/ns#">Exchange 2010 SP1</category><category domain="http://www.blogger.com/atom/ns#">Exchange 2010 SP2</category><category domain="http://www.blogger.com/atom/ns#">Exchange 2010 SP3</category><category domain="http://www.blogger.com/atom/ns#">Exchange 2013</category><category domain="http://www.blogger.com/atom/ns#">Exchange 2013 SP1</category><category domain="http://www.blogger.com/atom/ns#">Exchange 2016</category><category domain="http://www.blogger.com/atom/ns#">Server 2012</category><category domain="http://www.blogger.com/atom/ns#">Server 2012 R2</category><category domain="http://www.blogger.com/atom/ns#">Server 2016</category><category domain="http://www.blogger.com/atom/ns#">tool</category><title>Project Honolulu and Exchange servers</title><atom:summary type="text">Recently Microsoft announced a new web-based server management console, it’s called Project Honolulu. Looking at the documentation and screenshots this is going to be a huge step forward from the native sever management consoles that we have seen from Server 2008-2016.A technical preview of Project Honolulu is already available for download: https://aka.ms/HonoluluDownload Project Honolulu can be</atom:summary><link>http://jetzemellema.blogspot.com/2017/10/project-honolulu-and-exchange-servers.html</link><author>noreply@blogger.com (Jetze Mellema)</author><thr:total>2</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1962846729636742616.post-707189268974763496</guid><pubDate>Mon, 01 May 2017 09:12:00 +0000</pubDate><atom:updated>2017-05-01T11:12:41.111+02:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Exchange</category><category domain="http://www.blogger.com/atom/ns#">PowerShell</category><title>Exchange Remote PowerShell behind a proxy server</title><atom:summary type="text">Today I ran into the following issue. I tried to open a Remote PowerShell session to Exchange Online but the module failed to load with the error message:  New-ExoPSSession : Create Powershell Session is failed using OAuth  Initially I suspected that the customer’s firewall performed some kind of traffic inspection or recognized and denied the traffic as a blocked ‘application’. I was able to </atom:summary><link>http://jetzemellema.blogspot.com/2017/05/exchange-remote-powershell-behind-proxy.html</link><author>noreply@blogger.com (Jetze Mellema)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhAN1_jxN3kobcqZ2_iDBvaofLwYUH1Srox2cBa-ntT3S2f6uAPytc_0hWk1RWcQ9sgQHMqNfmuc0MlCsE4cVRG5OgSAI39NElVXo2FfMGKJewtQzaz1NtJ1jaP0puudNoNCZmik3xJ3g/s72-c?imgmax=800" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1962846729636742616.post-4635855839745313291</guid><pubDate>Tue, 11 Apr 2017 11:21:00 +0000</pubDate><atom:updated>2017-04-11T13:21:54.123+02:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Exchange</category><category domain="http://www.blogger.com/atom/ns#">Office 365</category><category domain="http://www.blogger.com/atom/ns#">PowerShell</category><title>Some feedback on the new Exchange PowerShell cmdlets</title><atom:summary type="text">As someone who has been working pretty much dedicated with Exchange since ~2000 I have witnessed quite a few changes. The single most important one is the move to PowerShell as the primary management interface. The Exchange team was the first within Microsoft to switch for the full 100% to PowerShell and at least two version of Exchange have seen their release slightly delayed because they had to</atom:summary><link>http://jetzemellema.blogspot.com/2017/04/some-feedback-on-new-exchange.html</link><author>noreply@blogger.com (Jetze Mellema)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjPnObgv9YQIuzj_jL5boEcTQ4EJJA0t4hKTtg5jLRNSEiZSdZtvaTE8zWRka0ouQMvJukbHloV6WZfGhiFlHANjbabNFYQ5vGZZB6snBL_af3zyPRpp3JA_4pkW8YOBpdK0oKePrC9sw/s72-c?imgmax=800" height="72" width="72"/><thr:total>2</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1962846729636742616.post-2930673757734496477</guid><pubDate>Fri, 24 Mar 2017 10:50:00 +0000</pubDate><atom:updated>2017-03-24T11:50:45.926+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Exchange 2016</category><title>Let’s not run Exchange 2016 Edge Transport on Windows Server 2016…</title><atom:summary type="text">Another example where old technology meets new technology. Old is in this case the Content Filtering agent on an Edge Transport server, new being Windows Server 2016. In short, the SmartScreen technology that is used in the Content Filtering agent conflicts with SmartScreen implementation in Windows Server 2016 operating system. At this point this is known to prevent a proper uninstall of </atom:summary><link>http://jetzemellema.blogspot.com/2017/03/lets-not-run-exchange-2016-edge.html</link><author>noreply@blogger.com (Jetze Mellema)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1962846729636742616.post-5487627899313251846</guid><pubDate>Thu, 16 Mar 2017 09:23:00 +0000</pubDate><atom:updated>2017-03-16T10:23:55.521+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Office 365</category><category domain="http://www.blogger.com/atom/ns#">PowerShell</category><title>New Exchange Online PowerShell module with MFA support no longer in Preview</title><atom:summary type="text">In a previous article I wrote about the new PowerShell module with support for Modern Authentication and Multi-factor Authentication. The Preview status was a reason for many organizations to hesitate to take the new module into production. Yesterday Microsoft released an updated version of the Hybrid Configuration Wizard with MFA support, the HCW now requires installation of the new PS module to</atom:summary><link>http://jetzemellema.blogspot.com/2017/03/new-exchange-online-powershell-module.html</link><author>noreply@blogger.com (Jetze Mellema)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1962846729636742616.post-3634844739820963170</guid><pubDate>Tue, 07 Mar 2017 10:39:00 +0000</pubDate><atom:updated>2017-03-07T11:39:05.686+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Lync</category><category domain="http://www.blogger.com/atom/ns#">Office 365</category><category domain="http://www.blogger.com/atom/ns#">Skype for Business Online</category><category domain="http://www.blogger.com/atom/ns#">Surface Hub</category><title>Surface Hub devices and the Skype for Business Trust Model</title><atom:summary type="text">I’m sure that most Lync or Skype for Business admins, users as well, are familiar with the Trust Model. The Trust Model is responsible for the ‘Skype for Business cannot verify that the server is trusted for your sign-in address’ warning. This warning is thrown when the clients tries to create a secure TLS connection with a server and the domain suffix of the server is different from the user’s </atom:summary><link>http://jetzemellema.blogspot.com/2017/03/surface-hub-devices-and-skype-for.html</link><author>noreply@blogger.com (Jetze Mellema)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhQHtb0lTYEF4QwsoXqOUzJNhmppoLf-0NjD_PkQ_4-6II9pc_DNvw2GzL_BuuYikOd3COWiEKdplDU1s9qAszih47uFCloHrjLIsvqjbcaX7IakbLfdF05OMtGhq3OYMU99vhWUzbb_Q/s72-c?imgmax=800" height="72" width="72"/><thr:total>4</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1962846729636742616.post-5304722243638129449</guid><pubDate>Mon, 06 Mar 2017 15:34:00 +0000</pubDate><atom:updated>2017-03-06T16:34:59.008+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Office 365</category><category domain="http://www.blogger.com/atom/ns#">Skype for Business Online</category><title>Skype for Business PSTN Calling in Preview for The Netherlands and Ireland</title><atom:summary type="text">PSTN calling is an add-on telephone service that, when combined with Skype for Business Cloud PBX, can become your phone system. This is currently available for users in the United Kingdom, United States, Puerto Rico, France and Spain. Microsoft now introduced this feature in Preview for The Netherlands and Ireland. To nominate your organization, make sure you’re prepared to deploy PSTN Calling </atom:summary><link>http://jetzemellema.blogspot.com/2017/03/skype-for-business-pstn-calling-in.html</link><author>noreply@blogger.com (Jetze Mellema)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiy_4KG_9_UbeFBFtL4jGK6Y93O2vuMNboQScpyvhjTmrfyhrIdJGVsukEdzDn0JCcVrjGprClK0bgtuY_gOFleq_kPTjomuLU3BzeNBISlYe5vjwJN5pjSh02SUF05ZHAxvO4ut4zMUQ/s72-c?imgmax=800" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1962846729636742616.post-8161803209781756764</guid><pubDate>Tue, 07 Feb 2017 09:25:00 +0000</pubDate><atom:updated>2017-02-07T10:25:57.235+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Office 365</category><title>New 100 GB mailbox limit currently being rolled-out to your tenant</title><atom:summary type="text">In early December (2016) Microsoft announced that the default mailbox limits in Exchange Online would be raised to 100 GB, a massive increase from the 5 GB that we considered to be huge in the BPOS era. Who needs such a large mailbox? Well, we do now apparently.  While discussing this with my peers last week we noticed that most of us did not saw the change reflected in their tenants. Today I </atom:summary><link>http://jetzemellema.blogspot.com/2017/02/new-100-gb-mailbox-limit-currently.html</link><author>noreply@blogger.com (Jetze Mellema)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh7hQJ7cOqpG4wixn6fh8mmiUnYlO-_SPtEA4W7m2ahH5CF46efRjqbSY_mKMbfhYIvtB2YJ0cZK9B-EOnWcoJffNU5m3N9PHPbKhxmo2Pm5ACa2VmS6FTua8KshgfZg_b06p0D84fW8A/s72-c?imgmax=800" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1962846729636742616.post-6150891543782410609</guid><pubDate>Mon, 06 Feb 2017 15:31:00 +0000</pubDate><atom:updated>2017-02-06T16:31:34.386+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Lync</category><category domain="http://www.blogger.com/atom/ns#">Office</category><category domain="http://www.blogger.com/atom/ns#">Office 365</category><category domain="http://www.blogger.com/atom/ns#">Skype for Business Online</category><title>Fix for the Skype for Business hangs</title><atom:summary type="text">The latest update for Office 2016 in Current Channel contains a fix for Skype for Business issue where the interface stops responding when the user has multiple IM windows open.  The build number is 7668.2074, my Office 365 ProPlus was still on a slightly older build so I had to start the update process manually.  For more information about the latest updates for Current, Deferred and First </atom:summary><link>http://jetzemellema.blogspot.com/2017/02/fix-for-skype-for-business-hangs.html</link><author>noreply@blogger.com (Jetze Mellema)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjWNc0I-2-OPXH31POGuW-n0JT5yPCIHhjyZKD6WBHmeJQwyTvNY73uxyhSuQLHgqECxflB-y9hXmPX5krAHeTilKWnz326V7pjeo_u8s2v7mSuxG-CDBageDC-t4unsYcTIw5FJ8P-Eg/s72-c?imgmax=800" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1962846729636742616.post-4282411984057850530</guid><pubDate>Thu, 26 Jan 2017 12:55:00 +0000</pubDate><atom:updated>2017-01-26T17:07:23.617+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Azure</category><category domain="http://www.blogger.com/atom/ns#">Exchange</category><category domain="http://www.blogger.com/atom/ns#">Exchange 2007</category><category domain="http://www.blogger.com/atom/ns#">Exchange 2010</category><category domain="http://www.blogger.com/atom/ns#">Exchange 2013</category><category domain="http://www.blogger.com/atom/ns#">Exchange 2016</category><title>A few notes on running Exchange in Microsoft Azure</title><atom:summary type="text">Earlier this week Microsoft published a very interesting article: Exchange 2016 dev/test environment in Azure. I’m not a big fan of the how-to format of articles when the topic is around deployment because the guidance and specifics tend to change with later updates. There’s the risk of your article becoming obsolete sooner than planned. The article contains an excellent real-world example of how</atom:summary><link>http://jetzemellema.blogspot.com/2017/01/a-few-notes-on-running-exchange-in.html</link><author>noreply@blogger.com (Jetze Mellema)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiG1T6Xjwmq9QMGNacMxVmKoSe_wUzKiWJzJbs158rnrm_Q4Qi1qlgFkjIN2bXxWew92J-tfXDM69jIYJNsVb4R3RNGpxwm80kkjQ3rHJaVcGOCQXWj6JHhOTHhjA0-eX4g8SW4zLiusA/s72-c?imgmax=800" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1962846729636742616.post-9067299582638541345</guid><pubDate>Fri, 20 Jan 2017 11:43:00 +0000</pubDate><atom:updated>2017-01-20T19:12:44.911+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Exchange</category><category domain="http://www.blogger.com/atom/ns#">Exchange 2010</category><category domain="http://www.blogger.com/atom/ns#">Exchange 2010 SP3</category><category domain="http://www.blogger.com/atom/ns#">Exchange 2013</category><category domain="http://www.blogger.com/atom/ns#">Exchange 2013 SP1</category><category domain="http://www.blogger.com/atom/ns#">Exchange 2016</category><category domain="http://www.blogger.com/atom/ns#">PowerShell</category><title>Windows Management Framework (WMF) 5.1 Released, do not install on Exchange</title><atom:summary type="text">Today the PowerShell team announced the release of version 5.1 of the Windows Management Framework, for most people better known as PowerShell 5.1. While Windows Server 2016 already contained WMF 5.1 when the product was released, the download released today allows administrator to install WMF 5.1 on older operating systems such as Windows Server 2008 R2, 2012 and 2012 R2. This is a reminder that</atom:summary><link>http://jetzemellema.blogspot.com/2017/01/windows-management-framework-wmf-51.html</link><author>noreply@blogger.com (Jetze Mellema)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjfgQ9sPIiYHbhMfqYK-OCkS_mUIhHe9YOSroyoUWjjGYssaYput781MwrWz8G6x_Jvfdg6-oBVdYdG5OD3XWN3PUkGYLj4P2JrK4pxGDtijJfTfNr-RXwSbULUlLr8U585tnBqbBZ_Tw/s72-c?imgmax=800" height="72" width="72"/><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1962846729636742616.post-3923596174005744119</guid><pubDate>Mon, 16 Jan 2017 19:45:00 +0000</pubDate><atom:updated>2017-01-16T20:51:11.671+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Cloud PBX</category><category domain="http://www.blogger.com/atom/ns#">Lync</category><category domain="http://www.blogger.com/atom/ns#">Office 365</category><category domain="http://www.blogger.com/atom/ns#">Skype for Business Online</category><title>Microsoft about to release new Skype for Business IP Phone firmware for Polycom VVX devices</title><atom:summary type="text">LCS/OCS/Lync/Skype has a long history when it comes to management of IP phone firmware updates. OCS 2007 R2 introduced the Device Update Service and greatly simplified the process and the required infrastructure. In the Lync 2010 timeframe the 3rd party IP phone (3PIP) certification added support for non-Microsoft firmware such as Polycom UC Software.  In Lync Server 2010 for instance, an admin </atom:summary><link>http://jetzemellema.blogspot.com/2017/01/microsoft-about-to-release-new-skype.html</link><author>noreply@blogger.com (Jetze Mellema)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjt6Omghcl8CIrcI-Zc1zv3UxbD54mJE3ZshUUPKmKy0qPSKN62tMLNxhyphenhyphenzcyaQr286yi11uvsBv_Wm_Nf5vEfKYVRTA3agKA7YVG8EPGe3h54MoP0jOEzTCRy0t8TbtYNCLe3M8m6Ekg/s72-c?imgmax=800" height="72" width="72"/><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1962846729636742616.post-9121953296505388867</guid><pubDate>Wed, 11 Jan 2017 19:25:00 +0000</pubDate><atom:updated>2017-01-11T20:25:16.557+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Exchange</category><category domain="http://www.blogger.com/atom/ns#">Office 365</category><category domain="http://www.blogger.com/atom/ns#">PowerShell</category><title>New Exchange PowerShell module with Modern Authentication support now available in Office 365 Portal</title><atom:summary type="text">Many organizations are enabling multi-factor authentication (MFA) for all their accounts, or a subset such as for instance user accounts with an admin role. Especially with how easy this is with Office 365, even with the basic MFA feature that’s included with the license. Unfortunately enabling MFA on an admin account breaks the ability to use PowerShell to administer Exchange Online, Skype for </atom:summary><link>http://jetzemellema.blogspot.com/2017/01/new-exchange-powershell-module-with.html</link><author>noreply@blogger.com (Jetze Mellema)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEimTops5F68v1Bd65mPphCzsGTRhH7U5aUenzkoupbPIgQvbim7cWIl-beeuAth1EVLhGnuUNjDvpGATyT10FjFHkAT1fIF51FMc6INhJxh_Ynn9oQfbuLJKV125rq4mT0WDLp7B_YkTA/s72-c?imgmax=800" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1962846729636742616.post-1917139649552750714</guid><pubDate>Fri, 23 Dec 2016 13:13:00 +0000</pubDate><atom:updated>2016-12-23T14:13:57.383+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Hyper-V</category><category domain="http://www.blogger.com/atom/ns#">Server 2012 R2</category><category domain="http://www.blogger.com/atom/ns#">Server 2016</category><title>Error 0xE0000100 when installing Server 2016 in a virtual machine</title><atom:summary type="text">Today I ran into an issue while creating a new VM on a Windows Server 2016 Hyper-V host. The VM will run Server 2016 as well but throws an error message when Windows Setup loads:   Windows installation encountered an unexpected error. Verify that the installation sources are accessible, and restart the installation. Error code: 0xE0000100&quot;  I downloaded a fresh copy of the ISO, deleted and </atom:summary><link>http://jetzemellema.blogspot.com/2016/12/error-0xe0000100-when-installing-server.html</link><author>noreply@blogger.com (Jetze Mellema)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhmPCjycYvpT44o_I3EeIkXKZX8winb-orLcFZ-elRRjltymOJKcTtqZ162JGgj8oxxsoGlBR9XUmSRIWONFZKywmTxctljus2di0c3P-Vr1itujpnpXBPFisi5wsMRWqEF2waOVoil2A/s72-c?imgmax=800" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1962846729636742616.post-887684663206828994</guid><pubDate>Fri, 04 Nov 2016 13:15:00 +0000</pubDate><atom:updated>2016-11-04T14:16:00.212+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Exchange</category><title>Friendly reminder: /RecoverServer to an older OS version is not supported</title><atom:summary type="text">In case you missed it, it’s currently not recommended to deploy Exchange 2016 on Windows Server 2016. The Windows Server team added a section dedicated to Exchange in their Windows Server 2016 Release Notes:  If you attempt to run Microsoft Exchange 2016 CU3 on Windows Server 2016, you will experience errors in the IIS host process W3WP.exe. There is no workaround at this time. You should </atom:summary><link>http://jetzemellema.blogspot.com/2016/11/reminder-recoverserver-to-older-version.html</link><author>noreply@blogger.com (Jetze Mellema)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgcwoVs6dDG08l0Osa_9NHHZ1xCX48860B-UGaFS2SHFHJ2syWgXQpHP6cOLXEUJ7hG2IIftQcMgkBykbRUbs4wUMddLY3jToORyqDUNjd0dCHjuX_C76NPnRqjnjuesDPIi8K-RFfo8Q/s72-c?imgmax=800" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1962846729636742616.post-4411743455890781176</guid><pubDate>Fri, 04 Nov 2016 11:54:00 +0000</pubDate><atom:updated>2016-11-04T12:54:22.912+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Microsoft Teams</category><category domain="http://www.blogger.com/atom/ns#">Office 365</category><title>Microsoft Teams, here’s the admin guidance</title><atom:summary type="text">Yesterday Microsoft released a preview version of Microsoft Teams, the new product to compete with Slack. It will be very interesting to see Teams integrate in Office 365 as yet another collaboration product next to Skype for Business, Exchange, Yammer, SharePoint Newsfeed and Office 365 Groups. Currently Microsoft Teams is not enabled by default, a tenant admin has to enable the application in </atom:summary><link>http://jetzemellema.blogspot.com/2016/11/microsoft-teams-heres-admin-guidance.html</link><author>noreply@blogger.com (Jetze Mellema)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgsyIW6YEBf8M1fsmb3qXAKcPmOt9tRyh89UinXKVrGi4r50-SS6f5MAM104N614w1DB9DuV_y3tjhy1JdgcJ7HNeto4khsSbcWOiydsIJ3b_E-nU77eJ1Fx4G8fjs9_3zKbhyGr8cb3A/s72-c?imgmax=800" height="72" width="72"/><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1962846729636742616.post-7632819158353207994</guid><pubDate>Fri, 04 Nov 2016 11:17:00 +0000</pubDate><atom:updated>2016-11-04T12:17:29.062+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Exchange</category><category domain="http://www.blogger.com/atom/ns#">Office 365</category><category domain="http://www.blogger.com/atom/ns#">PowerShell</category><title>Office 365 MFA is awesome! Unless you’re an administrator…</title><atom:summary type="text">For some reason I have never worked with MFA with Office 365 until last year. And I must say, it is awesome! Even the free version of Azure MFA that’s included with the Office 365 subscription meets the requirements of most organizations. It’s very easy to setup and configure and the end-user experience is pretty good too, supporting text messages, phone call or the Azure Authenticator app.  </atom:summary><link>http://jetzemellema.blogspot.com/2016/11/office-365-mfa-is-awesome-unless-youre.html</link><author>noreply@blogger.com (Jetze Mellema)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjf5BUfAyCEirqAAcI88TGk5LnjBhqub9Rg5HJEakG1_HBB9hK4KQSlREsiOg3fcctCIq_K6yTMzdAcsrCwIpyIOQeFlrFgN-SzteEBYYRCucdOGXUrFUNg5Go_X1h-6SL-68Lo2X9YDw/s72-c?imgmax=800" height="72" width="72"/><thr:total>0</thr:total></item></channel></rss>