Solved

Exchange 2010 OWA access from Domain Joined verses non-domain joined

Posted on 2014-02-04
4
232 Views
Last Modified: 2014-04-03
I have a client that currently uses messageware but we would like to remove this requirement. The function that we need to replace and find a solution for using Exchange 2010 is that currently, messageware scans the user's registry that is accessing OWA and tries to locate a entry that identifies the computer as domain joined. This registry setting is distributed to all domain joined workstations using Group Policy. This allows the organization to give different access to company owned computers that are domain joined, and non company owned computers are restricted. Specifically, only the domain joined PCs are allowed to have full access to download attachments. These machines are really not restricted at all. The non-domain joined however are restricted in many ways, caching, attachments and so on... Is there any inherent way I can duplicate this with Exchange 2010 OWA mailbox policies and segmentation? I cannot find anything based on the couple of hours I have spent searching the web...
0
Comment
Question by:Robguad
  • 2
  • 2
4 Comments
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
ID: 39832974
There isn't that functionality built in to the product which is why MessageWare have it in their product. I cannot think of a feature in Messageware that is available in the native OWA.
The only option you have is the Public/Private computer option on the OWA, but that depends on the end user selecting the correct option. While you can default it to Public, once users realise that changing the option allows them to do what they like, it is useless.

OWA doesn't really make a distinction between internal and external users other than that option. Policies usually apply at a mailbox level and are designed for controlling the user, not the connecting computer.

About the only suggestion I can come up with is to have two separate servers, one for internal traffic, one for external, which have a different configuration on them. That will of course mean additional Exchange licences. I don't think having it in a different web site on the same server would work.

For domain machines that are outside the network, they would have to VPN in to use OWA unrestricted.

Simon.
0
 

Author Comment

by:Robguad
ID: 39964013
I've requested that this question be deleted for the following reason:

No one answered the question
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39964014
I disagree that the question wasn't answered - I have fully answered the point that you asked about - simply put, it isn't possible.
0
 

Author Comment

by:Robguad
ID: 39975818
Im sorry, I didnt read the question... I had two open... i thought this was the other one where I didnt receive any replies
0

Featured Post

Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
A list of top three free exchange EDB viewers that helps the user to extract a mailbox from an unmounted .edb file and get a clear preview of all emails & other items with just a single click on mailboxes.
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
In this video we show how to create an Address List in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Organization >> Ad…

808 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question