From there you would like to move incoming mails directly to sub folders in your info@ mailbox. In a shared mailbox this is only possible using the message header. There are two ways to achieve this goal. First using Outlook / Outlook for the web and / or PowerShell.

CONFIGURATION with Outlook for the Web

Make sure you have the right permissions to manage the mailbox and open the shared mailbox (link to how-to).

Give a Name to the rule. Browse to When the message arrives, and or matches all of these conditions – It includes these words – in the message header – type in your alias for the mailbox (alias@mydomain.com)

Browse the condition Do all of the following – Move the message to a folder… Select your folder where the message should be moved to

If needed select Stop processing more rules and save (OK) the rule

The final result should look like this:

CONFIGURATION with PowerShell

First connect to Exchange Online using PowerShell. If you’re not familiar with connecting to Exchange Online using PoSh. please refer to this link.

My name is Alain Schneiter and I’m working in IT since more than 15 years now.

I work for itnetX AG as a Solution Architect and we’re a Service Provider located in Switzerland, focused on Microsoft Cloud & Datacenter, Modern Workplace and Service Management.

I’m focused on all the new and rising Microsoft Windows Client technologies. This includes stuff like, Microsoft 365, Windows 10, Intune, Enterprise Mobility & Security (EM&S), Configuration Manager (ConfigMgr), MS Teams, Azure Information Protection, Remote Desktop Services (RDS) and much more! All about the modern workplace. Any questions to me? Feel free to contact me using this blog or twitter!

All blog postings are provided “AS IS” with no warranties and is not supported by the author. All trademarks and copyright’s belong to their owners and are used for identification only. Also, the views expressed on this website/blog are mine alone and do not reflect the views of my employer.

And, don’t miss all the technical deep dives, technical news and also some fun stuff. Subscribe right now!

Microsoft releases KB4464330 for Windows 10 version 1809 to fix the issue that resulted in the deletion of user profile when upgrading to the OS Version 1809. After the release of Windows 10 1809 (October update), many users reported a serious issue with this update. As the users started to install the latest update, they reported that the upgrade process is wiping out their data from user profile. This included documents, pictures, and personal files along with other installed programs. After the upgrade, the data was not found and this annoyed the Windows 10 users.

The statement from Microsoft:

“We have paused the rollout of the Windows 10 October 2018 Update (version 1809)* for all users as we investigate isolated reports of users missing some files after updating.”

Azure AD Connect is a great tool to On-board your On-Premise Identities to the Azure Cloud. If you like to use a Hybrid Join of your Windows 10 Devices – Local Domain join & Azure AD join – you can configure Device Registration. What is the benefit if you enable this option?

PREPARE

Since a few version back of Azure AD Connect it allows you to use the wizard to configure the necessary options for you. First of all, make sure you use the latest version of Azure AD Connect. You can also check the Auto-Upgrade Option of the engine by using the PowerShell command on the server where AAD Connect is installed:

On the next step you will configure the Service Connection Point (SCP) to help your Windows 10 devices to find the necessary Azure Tenant information’s. To configure the SCP you need to provide Enterprise Admin Credentials. If you cannot provide this credentials during the wizard, you will be able to download the script to set the SCP in a later phase or offline.

This step helps you also to verify your current configuration. AAD Connect is checking the configured configuration on your AD. You can manually to that by browsing your ADSI Editor. Connect to the configuration naming context and then load the CN: “CN=ms-DS-Device-Registration-Service,CN=Schema,CN=Configuration,DC=xy,DC=xy”

Back to the wizard, provide the Enterprise Admin credentials and click “Next”.

Some of you maybe noticed, that the option Send to –> Mail recipient in the context menu from Windows 10 (several Builds) can cause crashing the File Explorer.
This is in combination with Office365 and Click-To-Run as the application is based on an App-V technology. The bug is not new and should really be fixed in a next CU of Windows 10, please MS. There is a very easy fix for that. Use a registry key to get it sorted. This is tested on many Windows 10 Enterprise 1709 Build.

*******************************************************************As always: Be careful when you do changes in the registry.

Copy the value from the reg key above to a notepad and save it as “FixSendToMail.reg”. Double click the reg file and import ist to the client with the issue. This will fix it immediately.

You can also add this step directly in your ConfigMgr Tasksequence. Just make sure you add the step after installing Office365. Use the reg key above and add it to your Customization Package for Windows 10.
Run a command line step in your Tasksequence by using the command bellow:

Yesterday the CMCE1710 event took place in Zurich, hosted by Mirko. It was a great community event with huge community power and great technical content delivered by the EM&S MVPs Roger Zander, Ronny de Jong and Mirko Colemberg.

Why I do the recap?

With this short blog post, I would like to call more attention on events like that! Specially for people in the Workplace Engineering and Office365 business. If you attend CMCE or other similar great Events, you will get a lot of information about new technologies, best practices. Having a chance to place your questions directly during the sessions to the experts about your current issues or opportunities. A similar Event in Switzerland is the Experts Live Café held in Bern.

What was the content?

First, the content was great! My first session attending, I gave Matrix42 another chance to satisfy me about their Enterprise Manager (EM). The EM is not a tool that replaces ConfigMgr, this was very important to David König – Chef Program Manager of the EM. The tool should help you to easy manage complicated tasks in ConfigMgr. Specially with Reports, Role Based Access and Rollout Plans. Matrix42 made a great effort with the new End-User Agent based on a Chrome Engine. This is how ConfigMgr should notify users in a modern way.

After a break, I was attending the Session from Ronny de Jong, MVP EM&S. As always, great content delivered here! Ronny was talking about all the possibilities of ConfigMgr and Cloud Services. ConfigMgr has currently nine direct connections to Azure based Applications. One topic he talked about, was the ConfigMgr Cloud Management Gateway(CMG). In my point of view, each customer with Mobile Users – doesn’t matter if they use a Laptop, Surface Book or Tablets – should use a Cloud Management Gateway. The Setup is much easier than the old way to get Internet based clients attached to your ConfigMgr Hierarchy. You don’t need any servers in your DMZ (you need an Azure Subscription instead) and the certificate handling is much more easier. If you not have looked at the CMG, do it now!

Ronny in Action!

The whole afternoon was just great, with real stuff and information delivered by David James (Director of Engineering ConfigMgr Microsoft Redmond), also known on Twitter as @djammmer.

David presented his personal IT career during the last years, specially at Microsoft and how the product changed from SMS to ConfigMgr. A really great story with a lot of great people working on that product. He took questions by the beginning and answers directly during the whole afternoon. Some topics where Telemetry Data, Co-Management with Intune, a REST-API currently in TP, Cloud Management Gateway and Client Health. I’m not able to cover everything here because this should be a short recap. But one of my favorite question from David to the audience was: “Do you think ConfigMgr is dead? Then raise your hand(s)”. Not one hand was raised!

David explained how many times SCCM was declared as dead but the history says something different!

Full house at CMCE1710

For me, it was a great honor to meet David personally, the director of the tool I mostly have in front of me: System Center Configuration Manager #ConfigMgr #SCCM. Thanks for being here!

Today I played around with my Android device and Intune using the remote control option in Intune. The initial reason was, that my sister was calling me yesterday to help her out with her new Huawei Android phone. She tried to configure her Office365 account and was not able to do so. Of course, I helped her, but using remote control on the phone would be much cooler :-).

So I logged in to the Azure Portal, went to “Intune” and under Devices I found the Option “Setup” TeamViewer Connector.

Before you can use TeamViewer to remote control your devices, you have to create an account or use an existing one to authorize Intune with TeamViewer. Go through the sign-in page from TeamViewer and authorize Intune. Make sure that the Connection Status in the portal is set to “Active”.

Don’t miss the message in the connector:“The TeamViewer service allows users of Intune-managed Android devices to get remote assistance from their IT administrator. Create TeamViewer sessions by first associating Intune with your TeamViewer account and then authorizing it to work with Intune. If you don’t yet have a TeamViewer account you will need to create one. “

After that, It would probably make sense to deploy the Andoird TeamVewer Quick Support app to all Android Devices from your Company. This can be done by creating an app in the portal an assign it to the devices. This is not covered in this blog post.

How can you now initiate a remote session?

On your Windows 10 Desktop machine download and install (or just run) the latest version of TeamViewer. In my case it is TV 12. After that, sign-in to the application with the user account you created earlier in the post:

Go to the Intune Portal, select the device you like to remote control, go to Overview and there on the upper right hand you will find the three-dot option “…More”. Select “New Remote Assistance Session”.

This will initiate a new session to your Android Device. Click “Yes”.

The user will have to go to the Company Portal and accept the request. The request is displayed in the notifications area of the Company Portal App.

TeamViewer Desktop creates a new category for you called “Intune” with all your remote control requests out from Intune. Just double click the invitation you recieved and from there you’re able to remote control the users device.

Be aware that the user will need to accept and confirm the session again. Now you can remote Control the Android device out from your TeamViewer Software. Very cool.

A great and nice option which should be used for remote supporting your android devices!