Quantcast
Channel: THWACK: All Content - All Communities
Viewing all articles
Browse latest Browse all 13537

VMAN Update URL Repository

$
0
0

I can't imagine why no one else has asked this question before, but how in the world do you get the Update Repository "Use Specified Repository" feature to work in the VMAN Admin console??  I tried just putting in a simple UNC path and it says you have to have a HTTP URL.  So I looked up how to create a Virtual Directory in IIS to allow directory browsing via http and I successfully got the directory served via HTTP.  Unfortunately I'm now getting an error from the VMAN console saying that the requested URL returned error: 404 because the manifest-latest.xml file was missing from the manifest directory (which I hadn't created because no instruction on setting up virtual directories in IIS mentioned a manifest directory being needed). 

 

To my further dismay there are not only no instructions for this feature in the Admin guide, there is absolutely zero mention in the admin guide about this nor is there a Thwack post or support article talking about it.  Even just something in the Admin guide saying this feature isn't currently supported or something like that would be appreciated.  Although if it isn't supported it kind of seems silly to have it.  Just remove it if that's the case.

 

But, if it is supported can somebody please post some danged instructions?  I'm quite frustrated since our VMWare admins are being really tight with permissions and really slow to mount the ISO themselves.  Like us being able to mount an ISO on our own VM's would really be some kind of security risk or something...  It's quite silly.  I was hoping thought that this URL Repository feature would allow me to work around them but the lack of documentation has dissolved that hope.

 

Here is the feature I'm talking about in case it's unclear:

 


Viewing all articles
Browse latest Browse all 13537

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>