Resolution

Parallels Operations Automation team uses the following testing and publishing method for Windows security updates.

All internal testing environments used by QA and Development departments are configured to install all Windows security updates as they arrive. It is done using pre-configured WSUS policy.
QA department performs regress testing at least once a week. It means that all updates are tested not later than one week after they were available on WSUS.

If any update affecting a provisioning will be found during these tests, it will be included into this KB.

If one installs updates and they affect live provisioning system, then a support case should be opened. Support team will analyze the case and the update will be included into this KB article if it really affects provisioning.

List of Windows updates affecting POA provisioning

Date	KB number	KB description	Issues found
Oct 26, 2009	KB968930	Windows Management Framework Core	Description: After KB968930 (Windows Management Framework Core) is installed on MPS node, some Hosted Exchange provisioning tasks are failed with error "A parameter cannot be found that matches parameter name 'Alias '". Reason: Exact reason still not found. How to fix: Uninstall the KB on MPS node(s) and reboot.
Aug 24, 2009	Download	Exchange Server 2007 Service Pack 2	Description: Some Public Folders related provisioning tasks fail after installing Exchange 2007 SP2 on MPS nodes. Reason: Property names were changed in Public folder oriented cmd-lets used by provisioning tasks. How to fix: Do not install the SP2 on MPS node(s). Use previous latest version instead (SP1 with Rollups). The note is also added into POA Hosted Exchange Deployment guide.
Sep 10, 2009	KB970162	Update Rollup 9 for Exchange Server 2007 Service Pack 1	Description: Some providers enable non-secure POP3 and IMAP4 authentication for end customers. In such configuration the Rollup installation resets service settings and denies authentication using plain text. Reason: Default (more secure) authentication settings are applied to POP3/IMAP4 services during the KB installation. How to fix: If non-secure configuration is needed, call following cmd-lets on CAS servers to fix it: Set-PopSettings -LoginType PlainTextLogin Set-ImapSettings -LoginType PlainTextLogin

Below is the list of other sources with HMC updates testing status:

• Windows Update Compatibility tests by HMC team from Microsoft: HMC 4.0, HMC 4.5
• Hosted Messaging and Collaboration Knowledge Base Articles: HMC 3.5, HMC 4.0 and HMC 4.5. These articles outline the fixes and updates that have been tested by Microsoft and are certified to work with the respective HMC offerings.

Previous version is moved into KB6623.