All of the machines in my lab had the same problem, perhaps not surprising since they were built from the same Amazon Web Services AMI. By contrast, when I downloaded the HCW onto my Windows 10 desktop, it would fail because I didn’t have the right prerequisites installed, leaving me a log file full of juicy details.
Of course, since the C2R launcher itself wasn’t launching, there were no log files to use to troubleshoot the problem.
Downloading the HCW manually using the Start-BitsTransfer PowerShell cmdlet got me the manifest file, but it couldn’t be launched. When I clicked on the HCW link in Internet Explorer, the little “Scanning.” infobar would flash across the bottom of the window, but that was it. In my Exchange 2016 lab, that’s not what was happening. With that said, on a properly configured Windows box, as soon as you download the manifest, the C2R helper application does its thing it reads the manifest, streams the application, and launches it.
This ensures that everyone always gets the most up-to-date version, but it also introduces a few potential stumbling blocks.Ĭ2R application manifests aren’t executable themselves they’re just XML files that provide some metadata about the application. The biggest benefit to using C2R is that whenever you click the link (which downloads the application’s manifest file) you get the latest version of the HCW, streamed directly to you from Microsoft’s servers. The Office 365 team (hi, Tim Heeney!) made the wise decision to turn it into a Click-To-Run (C2R) executable. The HCW used to be a standalone Windows executable that you’d download. Hopefully this article will be a useful breadcrumb for future hybridizers. I recently ran into a bizarre problem with the Office 365 Hybrid Configuration Wizard, and solved it after a bit of trial and error.
0 kommentar(er)
