This is less of a question and more of an FYI for others who may come across this.
When you have untrusted Hyper-V hosts in your environment, updating the VMM agent is an involved process. (Described here: http://blogs.technet.com/b/scvmm/archive/2015/05/19/how-to-update-untrusted-hosts-in-system-center-2012-r2-virtual-machine-manager.aspx)
However, after this update I could no longer deploy a template from my Library server to these hosts, troublesome as they were hosting my Gateway servers and I was trying to add a second gateway for testing purposes. That's when I came across the famous 2912 error that seems to litter these forums. Specifically, mine mentioned a BitClientJob in the wsman failure. However, I followed the guidelines in the blog above to update my hosts, including exporting the cert from the untrusted host to the VMM server. Unfortunately, a file copy from a library server in the SCVMM domain to an untrusted host uses BITS over HTTPS when deploying the file over LAN. Therefore the cert that was imported to the VMM servers also needs to be imported to the Library server to authenticate the BITS transfer.
In short, when you export the cert after upgrading the Untrusted Hyper-V hosts, don't forget to also import the cert to the Trusted People container in the Library server.