For the most part, it works out of the box since we use the redirection. CONFIG settings for reading apphost/admon.config. However, for a detailed answer, it really depends on what scenarios you will be using:

• Shared Config using Local Content: Regular Windows or IIS users connecting to modify their local content and their web.config - there is nothing to do, everything should WORK out of the box.
• Shared Config using Remote Content using Windows Users: It should work, provided the Windows accounts have ACCESS to their content.
• Shared Config using Remote Content using IIS Users: For this scenario you must change the Identity of the service (WMSVC) to an ACCOUNT that has access to the remote content, since we use the process identity for accessing content. Note that apphost.config/admon.config will work, since we use redirection. Config
• Windows Administrator MANAGING a Server Connection: It should work, provided your Windows administrator has write access to the shared config.

For the most part, it works out of the box since we use the redirection. Config settings for reading apphost/admon.config. However, for a detailed answer, it really depends on what scenarios you will be using: