I setup everything as described. Template stored on a FileShare drive inside the library. It does show None in most relationships, the problem is I see the exact same thing on every Template, win or lin, on 5.7.2, 5.7.3, 5.8.0, etc. Get-SCVMTemplate retrieves everything from the library and where it is stored isn't defined in the template itself as near as I can tell. Is it not deploying as expected? Or is the presence of these fields just confusing the matter? If you run Get-SCVMTemplate -Name <template_name> I don't see anything to indicate where it is stored but it could be buried in there somewhere.
I've since confirmed we are definitely going something different that needs to be evaluated. I got a response via email from Jeff Cutter as follows: "We have been able to formulate a work around running some PowerShell commands against SCVMM post provision to get the network working. I will get those for you to share tomorrow hopefully. I'm still thinking something CF is doing maybe at least needs to be optional since it seems to work as expected through SCVMM."
(In reply to Jeff Teehan from comment #6) > I've since confirmed we are definitely going something different that needs > to be evaluated. > > I got a response via email from Jeff Cutter as follows: > > "We have been able to formulate a work around running some PowerShell > commands against SCVMM post provision to get the network working. I will > get those for you to share tomorrow hopefully. > > I'm still thinking something CF is doing maybe at least needs to be optional > since it seems to work as expected through SCVMM." The work around referenced is in response to a different issue (1463019) not this one.
Right. That second issues originally spawn out of the hotfix for this one. I was updating both at the same time. For this: All checks have been reconfirmed with 5.7.3.02 same tests as with customer who also confirmed the changes. This is working. Not only do the FileShares in datastore get displayed but I provisioned a VM to the FileShare as well and manually checked the locations of all files. Moving to verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:1601