Office and its poor handling of slow-links

Office is and has been a core application for a quite a while within most Windows environments.  This is a small list of things that have been adopted to make the user experience better for users not located close to the file-servers, or articles that allow you to understand why things happens.

Slow network performance when you open a file that is located in a shared folder on a remote network computer
Known issues with Office if Desktop or My Documents is redirected
An Office program is slow or may appear to stop responding (hang) when you open a file from a network location
Excel workbooks may open slowly over the network
Slow performance when you browse the My Documents folder in the document library in Windows 7 or in Windows Server 2008 R2

and for the PST / OST-files;

Limits to using personal folders (.pst) files over LAN and WAN links
Network Stored PST files … don’t do it!

Access

Using a wan with ms-access? How fast, how far?

Office 2007 without Outlook

Part 2;
Well, Finally – here comes the complete article of howto deploy office without having Outlook as the default mail client

Part 1;

If you have deployed Office, you probably deployed it either with Outlook or without.

However, if you deployed it with Outlook – you probably wanted Outlook as the default mail-client. This isn’t the case for everyone, and that gave me a headache a while back. Loads of registry hacks and work later (and more work later on) I solved the issue thanks to a techician writing a bat-file resetting the registry keys.

Now I saw this blog-post where the Office Resource team actually will publish an article on howto resolve this automagically.

I wish I had that one year ago.