Mobile Device Ghost in Exchange 2013

Everybody knows the “problem” that an administrative account can’t use Active Sync (Keyword: AdminSDHolder / Active Directory Inheritance). But a few time ago I got into a new situation. Over the ECP I couldn’t open/delete a mobile device, because the device couldn’t be found.

In the next step I saw that also the access to the device was denied.

So I thought it was the familiar problem from Exchange 2010 with the changed organization unit. In this case the console use the wrong path to the device, but you can still delete the device over the PowerShell.

But also PowerShell wasn’t able to find the device:

The interesting thing is that I got statistics to that device:

My next step was to check the user container in Active Directory.

Also empty!

With ADSI-Edit I could only find information from the statistics like the Blocked Device ID:

Finally I found a way to delete the mobile device.

Connect with the tool “MFCMapi” to the affected profile.

In the “Root Container” under “ExchangeSyncData” you can delete the device.

Regards

Arno

Why should I use Azure?

In this topic I will answer the question why you should use Azure. First I will describe why most of the admins use virtualization.

Why do most admins use virtualization?

Cost reduction

  • Energy costs
  • Investment costs

Faster reaction to performance / Upgrade requirements

  • Grow the HDD capacity
  • Add CPU resources
  • Add memory

Increase uptime

  • Failover in case of hardware failure (Cluster)
  • Disaster recovery (hardware-Independent)
  • Isolation of services ( for every service a single VM)

These are several good and common reasons for using virtualization.  So let’s get back to the Topic.

Why should I use Azure?

If I want to use a cloud service, I should choose one with experience and a good reaction time in case of trouble. I think to tread this path with Microsoft is the best way you can do it!

So let’s take a closer look at the single points of the benefits of virtualization.

Cost reduction
With an Azure VM you don’t need a server in your office (local). Also you only pay for the needed infrastructure. You don’t need to invest in hardware that you sized for the next years.

Faster reaction
You never need to expand a server to get more space for HDDs and so on.

Increase uptime
You don’t need to setup a cluster to get high accessibility. So for small and medium enterprises it is a cheap way to get a good availability.

You see it increases the benefits of virtualization!

So going in the cloud with azure is the most sensible way you can handle your infrastructure.

Also a point where you can use Azure is getting off-site backups. In case of disaster it is good to have a backup not in the same location – but further more in following topics.

I hope you enjoy my first post.

Arno

Exchange 2013 receive strange mails in journaling mailbox – inboundproxy@contoso.com

If you are Using Exchange 2013 and you take a look in the journaling mailbox, maybe you’ll find some strange mails like inboundproxy@contoso.com or something@inboundproxy.comThose mails are generated by the Exchange Server itself. Exchange Server 2013 is using a new self monitoring system. Each database has a hidden „HealthMailbox“. Exchange generates periodically mails and is sending them to those mailboxes, to gain Information about system health and performance.

If your journaling-rule is configured to journaling all mails, Exchnage is also journaling those system mails.

If don’t like that you have two options:

1.) disable the overall mechanism to generate those mails

2.) create a distribution group, add all users you need to this group and reconfigure your journaling-rule to only journaling mails which are sent to or sent by a member of this group.

There is also a Microsoft KB about this topic. KB2823959

VPN Devices for Azure Site-2-Site VPN

Hello Community,

in all our Projects we choose a „Dynamic Routing“ for the Virtual Networks in a Azure Subscriptions. Because most of our Customers need more then One Site-to-Site VPN and they often need mobile VPN for Administration or some Users.

The Problem from „Static Routing“ in Azure is that they only supports one Site-to-Site and no mobile VPNs (Point-to-Site).

At the moment you can choose „Fortinet Fortigate, Cisco ASR/ISR, Juniper SRX/J-Series, ISG, SSG or Windows Routing and Remote Access Service) or a device which supports IKEv2 for VPN.

Link to Microsoft Azure Documentation:
https://msdn.microsoft.com/en-us/library/azure/jj156075.aspx

Install Microsoft .NET Framework 3.5 on Azure Virtual machine

Everyone knows the Problem, with the .NET Error 0x800F0906 and 0x800F081F on machines.

Just open a Windows Powershell as Administrator and install .NET 3.5 with this command
Add-WindowsFeature NET-Framework-Core