Remote user - unable to change out-of-office

[1DMF]

Hi,

We have a remote user that connects via VPN to our network and uses Outlook with his domain account, everything seems fine.

I reported the problem that a user was unable to set their out of office with the error.. 'server is not available', to our server support company, who said the problem is because they are not connected to the domain.

How can this be the problem? they use Outlook fine with a domain user account and password over secure VPN, their laptop isn't set up on the corporate domain, these are personal private laptops, so of course run under local standard WORKGROUP.

Why would Outlook work fine using his domain account for everything except setting out-of-office?

Is this a known bug in Exchange 2010?

NB. This is Exchange 2010 running under SBS 2011.

Thanks,
1DMF.

"In complete darkness we are all the same, it is only our knowledge and wisdom that separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!"
Free Electronic Dance Music

 

[1DMF]

I performed a remote session with a user and can confirm this bizarre behaviour.

Is there a work-a-round, setting or something that can be used to resolve this - other than using OWA, which is also bizarre that a non-domain computer using a web browser can change out of office but a VPN authenticated remote user using Outlook that is authenticated with a domain account cant?

"In complete darkness we are all the same, it is only our knowledge and wisdom that separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!"
Free Electronic Dance Music

 

[ntinlin]

Out of office is actually set via Exchange web services if memory serves rather than via MAPI.
I would check whether he can set it via Outlook Web Access rather than with the full client.
This should confirm connectivity to the CAS via http/https.

Neill

 

[1DMF]

Hi Neill,

They can perform this action via OWA, and I have been informed this is the only way to do it if their computer is not attached to the domain.

Seems bizarre behaviour to me that Outlook works with an authenticated domain account except for setting 'out of office', apparently it's to do with the way OOO works using Exchange Autodiscover Service and the fact their computer isn't attached to the corporate domain.

Recently we have replaced many remote users to have a corporate provided device, which will now be set up and attached to the corporate domain by the support company, which should eliminate this problem moving forward.

This will leave only two remote users that have their own devices having to use OWA to set 'out of office' auto replies.

Regards,
1DMF

"In complete darkness we are all the same, it is only our knowledge and wisdom that separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!"
Free Electronic Dance Music

 

[ntinlin]

May be more down to the way your VPN / DNS with VPN is configured then if it can't resolve the auto-discover entries

 

[1DMF]

Don't think so, everything else works fine and I have also implemented split tunnelling.

All access to resources via the VPN gateway is set as a route to ensure it knows where to go?

I have been told by the support company that they MUST be on the domain for this to work, who am I to argue!

The fact that someone can send, delete, read emails, access calendars, tasks, contact lists, public folder shares, shared mailboxes, send as / on behalf, you name they can do it via Outlook and our Exchange server over the VPN, it just seems the one thing they can't do is tell people when they aren't available via auto replies, it's ridiculous!

"In complete darkness we are all the same, it is only our knowledge and wisdom that separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!"
Free Electronic Dance Music

 

[ntinlin]

Well iOS 8 is supposed to finally catch up with Blackberry and allow setting the OOF message from the handset so maybe that will help them.