@AJKL and Mike: Disabling the Outlook Direct Booking feature via GPO is certainly a tactical option to work around this issue, since Outlook will never try to Direct Book a resource at that point. While this solution is feasible it should be used with caution. It may be difficult to ensure that the policy gets applied to all clients, especially any non-domain joined clients that may be connecting to Exchange. We will be releasing a revised script very soon that will address the root cause of this issue and we strongly recommend re-running the script with the -RemoveDirectBooking switch to rectify this issue permanently even if the outlook registry modification method has already been used. This will ensure the settings get permanently disabled.