********************* Vcheck version 50 ***************************

[td]

Anyone using the vcheck script to update extenders should consider downloading the latest version (50).   The hard coded domain in older versions will become unreachable for downloading purposes sometime before July 21, 2017.

[JTaylor]

Not sure if I am doing something wrong but when I installed the new version and told it to update the Postie Extender it just kept downloading it over and over again until I finally killed it.  I did run it through WinBatch Studio because it kept telling me I couldn't install the Extender with the current account, when running directly, so that is something different that I VERY rarely do but guessing that is still not how it is supposed to work.

Jim

[td]

Vcheck.wbt requires elevated admin privileges or it will not install an extender but that has been the case for at least 10 years.  This may explain your account issue.

I downloaded a fresh copy of vcheck.zip, unzipped it to my existing vcheck directory and it worked as expected - whether from the shell or WinBatch Studio.   Not being one to be deterred, I decided to installed it into an empty directory.  Voile! Infinite loop with no WinBatch Studio required.
   
As you may already know, vcheck requires the ver2001.all file to work correctly.  It will download a fresh copy if the current local copy is out of date or not present at all.  It appears that the new version of ver2001.all was overwritten by the older one on our FTP server.  This caused vcheck to repeatedly attempt to access a now defunct URL when downloading a zip file.

The new ver2001.all is now back on the server and all should work as intended.      My only defense is pointing out the admin post at the top of this board.

Thanks for reporting the problem.

[JTaylor]

Works now.

I was just providing "all" the info about the situation       Thought I had scripts default to a elevated manifest when running so that is the only reason that part was of note to me.

Thanks.

Jim

[td]

Good and may the schwartz be with you

[kdavies]

vCheck appears now to work only through the FTP protocol. Previous versions of vCheck worked through HTTP/HTTPS as well. (http://files.winbatch.com/downloads/padxml/ver2001.all results in a 404 error, but ftp://files.winbatch.com/downloads/padxml/ver2001.all works.) If the FTP protocol is the only way to download the latest extenders through vCheck, please let me know, and I can add FTP access as a requirement for using WinBatch (or at least vCheck). Normally, we block FTP ports on our workstations as a security precaution.

Thanks,

Kelly

[td]

You will have to use the FTP protocol.   BTW, the old server never transmitted the file encrypted (https).  It only supported http and ftp.

[td]

Take that back.  We added a new mime type to the site so it should, *theoretically*, work using http.

[kdavies]

HTTP is working. Thanks. (And I thought HTTPS might have been an option just based on comments in the vCheck code that I misread.)