#Microsoft activesync 3 update#
#Microsoft activesync 3 software#

Now that we've gone through the theory, let's talk about how we would do this in practice. In restrictive organizations, this can be used to see who is trying to work around policy and also gauge demand from 'Bring Your Own Device' (BYOD) users. In a permissive organization, quarantine can be used so that IT administrators know what devices, and which users, are making new connections. Both permissive and restrictive organizations may choose to employ this mechanism. Quarantining devices is useful when an IT department wants to monitor new devices connecting to their organization. Whether it's testing a new device before rolling it out to the organization as a supported device, or an exception made for an executive, we wanted to give you the ability to make an exception without allowing all users with that device to access your organization's email and PIM data. Of course, if you are limiting the devices that connect to your organization, there's almost always a need for an exception. All other devices, including the unknown devices, are given access.

#Microsoft activesync 3 update#

In these cases, the IT department can identify the misbehaving device and block that device until a fix or update for that device brings it into compliance. This is useful if there's a security vulnerability or if the device is putting a particularly heavy load on the Exchange server. In these cases, the ABQ list can help organizations block a particular device or set of devices from connecting. Permissive organizations allow all (or most) to connect to their Exchange Server. It's important to note that a restrictive organization is created by specifying a set of allowed devices and blocking the unknown. In this case, the IT department will only choose to allow the particular devices they support and all other devices are blocked. Restrictive organizations follow a more traditional design where only a set of supported devices is allowed to connect to the Exchange server. Below are some descriptions and 'how-to's for using the ABQ list in these different ways.

#Microsoft activesync 3 software#

Since we always want to make our software as flexible for IT as possible (as we know there are a lot of you folks that are using our software in a lot of different ways) we created this feature so that no matter which type of organization you are (or even if you are one that is in between these two extremes) we could help meet your needs. What we realized is that there is a continuum of organizations from permissive organizations that let employees connect whatever device they have to their Exchange Server, all the way to restrictive organizations that only support specific devices. When we designed the ABQ list, we talked to a lot of organizations to find out how all of you use (or wanted to use) this kind of technology. If you're curious as to what devices OS support which policies, the Wikipedia article we blogged about is a good place to look.ĭifferent device access models for different folks The easy takeaway is that Exchange ActiveSync policies allow you to limit device access by capabilities while the Allow/Block/Quarantine list allows you to control device access by device type. Policy controls allow you to control and manage device features (such as remote wipe, PIN passwords, encryption, camera blocking, etc.) whereas the ABQ list is about controlling which devices are allowed to connect (for example, there may be a lot of devices that support EAS PIN policies, but some IT departments only want to allow certain devices to connect to limit support or testing costs). It is important to understand that the ABQ list is not meant to displace policy controls implemented using Exchange ActiveSync policies. Some of you may remember my previous post on this topic dealing with organizations that do not have Exchange 2010 and thus I wanted to show you the far better way you can do this in Exchange 2010 (which is also what you will see in Office 365 and Exchange Online if you are looking at our cloud-based offerings). With this feature, organizations can choose which devices (or families of devices) can connect using Exchange ActiveSync (and conversely, which are blocked or quarantined). This feature was designed to help IT organizations control which of the growing number of Exchange ActiveSync-enabled devices are allowed to connect to their Exchange Servers. In Exchange 2010 we added a feature called the Allow/Block/Quarantine list (or ABQ for short).