Figured this might be interesting to those users that have limited bandwidth where KBOX is located and would prefer to have there field personnel updated from the internet via FTP and not the KBOX via http . Step 1 – Build repository on internet server All of your data (MIs, scripts, app updates, and etc.) will be synced to the public accessible internet server. Step 2 – Setup FTP on server from step 1. Step 3 – Build custom software package for each software title. A – FTP connect = %windir%\system32\ftp.exe -s:ftpscript.txt <hostname> B – FTP script file = <username> <password> cd <remote file path> lcd <local file path> get <software package> bye bye C – Download file(s) D – Unzip / Install Example: I use batch scripts to complete most of my items with everything in one zip file. 1) Download zip file from KBOX via http (usually small like 10 kb) Zip file contains 3 files = ftp.bat (connection) Ftpscript.txt (ftp parameters) Installer.bat (combines it all) 2) Once downloaded, MI launches “installer.bat” 3) “installer.bat” launches ftp.bat to download full software package according to the parameters file “ftpscript.txt” 4) Once downloaded, Rename full software package of “software.zip. 714b8a754d0bc37446a7bb06d81e419f” to “software.zip” 5) Un-compress “software.zip” to current directory 6) Last command of installer.bat is to launch the exe or msi for the full software package. We are utilizing this technique because our HQ has only 10 MB connection which when we go live with the KBOX will swamp the netowkr and hog all the bandwidth. When we go live most of our 100 field personnel will be downloading 2 to 5 GB immediately. By utilizing the internet repository via FTP, we moved initially ½ TB of data off the HQ internet … [:)]
0 Comments   [ - ] Hide Comments


Please log in to comment

There are no answers at this time
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity