Release 2.6.11

Issues fixed

Engine deployment from automation no longer requires Internet Explorer on the host
When deploying migration engines through the PowerShell automation module, the deploy could fail on a server or service account where Internet Explorer had never been initialized, with the error "The response content cannot be parsed because the Internet Explorer engine is not available, or Internet Explorer's first-launch configuration is not complete."

The automation module's file upload and download commands no longer rely on the legacy Internet Explorer response parser, so engine deployment and file transfers now work correctly on such hosts, including headless build and deployment agents.