Questions[outlook](server)

I have two users in Taipei time zone.

Both are using PCs with system time correctly set to Taipei time.

Both have an Office 365 E3 Enterprise account on the same tenant and have Office 2016 installed.

Both use Outlook 2016 for their email needs and connect to the same on-premises Exchange server.

For one user, all time stamps on email display correctly with Taipei time.

For the other user, all time stamps on email seem to be using PST time.

Why?

Everything I google seems to reference time zones in Outlook's calendar functions, but they don't even use their calendars. This is only in reference to the email time stamps.

Why is there a line through the recurring meeting symbol on an outlook calendar event?

We recently moved from Exchange 2003 to 2010, and have noticed a quirk that is annoying us.

If our exchange server (single server) goes down, ie it gets rebooted, or client loses connectivity (or for example a reboot is done overnight and the users computer is on at the time) they will be prompted to login, and will have to use the full domain\username notation in their username field in order to login again. Either that or reboot outlook.

Its not a big deal, but lots of inexperienced users are confused by this, and some dont realise they need to do something and thus their outlook sits there without receiving emails until they finally notice.

This used to be seamless, what do I have to do to get that back again?

Outlook and a number of other email clients now feature autodiscovery of mail server settings and it bugs me that I don't have this set up for our domains, but I'm not sure how to do it and a quick google hasn't turned up anything. I presume it's done with some kind of SRV record in DNS - is this correct and if so what's the correct format?

When a colleague tries to open attachments in her email (Outlook 2003 talking to an Exchange 2007 server) they take ages to open. The files are relatively small, all less than 1MB.

We've tried creating a new Windows profile for the user and tried creating new Outlook profiles, however that hasn't made any difference.

And we've tried accessing her account from someone else's PC, and the attachments open immediately there.

The only thing that might provide a clue is that Process Monitor shows Outlook on her PC trying to write the file to a folder within the user's "Temporary Internet Files" folder with FAST I/O DISALLOWED errors. Can't find a lot of useful information on that message online though.

What causes the FAST I/O DISALLOWED errors?

And would that make opening attachments so incredibly slow that opening a < 1MB file can take a matter of minutes?

UPDATE: Discovered that this isn't just an issue with Outlook. Other files being accessed over the network show the same FAST I/O DISALLOWED errors in Process Monitor. The problem is just more noticeable with Outlook, because although other applications take a while to open files it isn't a matter of minutes.