|
You should post this in an Exchange group; It's not an Outlook
question.
On Wed, 2 Jul 2008 11:13:01 -0700, Jon <Jon@discussions.microsoft.com>
wrote:
question.
On Wed, 2 Jul 2008 11:13:01 -0700, Jon <Jon@discussions.microsoft.com>
wrote:
>Hi,
>
>Currently all employees for our company are issued laptops. Employees are
>restricted from accessing work data (VPN, Outlook Client) to their laptops.
>The exception for home machine use is through OWA. RPC/HTTP is not enabled.
>
>We are wanting to enable RPC/HTTP to be used by users for their laptops to
>improve their mail experience. However, we're concerned about manual
>configuration of home clients to access work data and having OSTs/home PSTs
>created on non-corporate machines. How would be use certificates (or
>something else) to restrict users from enabling any machine for RPC/HTTP? We
>understand there are manual ways around transferring/storing data, but this
>is the one aspect we're asked to focus on.
>
>Thanks in advance for any suggestions/advice.
>
>
>
>Currently all employees for our company are issued laptops. Employees are
>restricted from accessing work data (VPN, Outlook Client) to their laptops.
>The exception for home machine use is through OWA. RPC/HTTP is not enabled.
>
>We are wanting to enable RPC/HTTP to be used by users for their laptops to
>improve their mail experience. However, we're concerned about manual
>configuration of home clients to access work data and having OSTs/home PSTs
>created on non-corporate machines. How would be use certificates (or
>something else) to restrict users from enabling any machine for RPC/HTTP? We
>understand there are manual ways around transferring/storing data, but this
>is the one aspect we're asked to focus on.
>
>Thanks in advance for any suggestions/advice.
>
>
| 02 Jul 2008 | RPC/HTTP and restricting personal machines | .Jon |
| 04 Jul 2008 |  Re: RPC/HTTP and restricting personal machines | .Jason C |
All times are in (US) Eastern Daylight Time (GMT -4:00)