I’ve have a number of Hyper-V servers defined as VM Managers. They were originally configured to use HTTP but have since had valid certificates installed so now we can use HTTPS.
I’ve changed the URL from http://:5985/wsman to https:/:5986/wsman and have successfully tested afterwards. But the next time I look at the list of VM Mangers it’s back to HTTP on port 5985.
Has anybody run into this?
Not this specific issue but I’ve seen all sorts of weirdness around the timing of it all. Unfortunately, the VM Managers functionality stores the configurations on 2 different places - within the BFI database & within the root server with the VM manager tool installed, so how did you change them and tested them? Did you do it from within BFI UI which essentially sends “update” action with all connection to the root server and essentially syncs things up; OR did you open an individual config file on the VM manager and update & test it directly? If it is the latter, then BFI will override them for sure on pretty much every change because, as I said, you change one VM Manager connection it sends ALL down..
If you did it via BFI UI, is there any chance that the “update” action didn’t succeed (failed, timed out, etc) and the change was never propagated?
I changed them using the BFI UI. I watched the tasks and made sure they were successful.
Worth opening the case then. Maybe they can review the VM Manager tool’s logs and figure out what went wrong.