Goal: Need a file that allows users to update their program folder file during quarterly releases manually when neccessary.
NOTE! These updates are typically pushed using software to distribute those files and that hits approx 95%. The tool used for updating can take a long time to update those files if the machine is not in a ready state when the initial push occurs. I do not administer that software nor have the ability to 'kick it' to speed up the process for those machines that did not get the update over the release weekend on Monday morning.
The Situation: there is currently a manual 'batch' file available to end users to update those appplication files when they did not get them over the release weekend. HOwever, the logic is set to copy from a source directory only those files that are of a higher modification date than what is currently on the local workstation. Normally this works just fine, however developers have now put out dll files that have an older date than what is on the local workstation thereby causing issues with the application because that one particular file never gets copied to the local machine.
The batch file is on a white list to allowed to run on Credit Card PC's that have additional security measures in place. I would like to get a file that meets the business need here, then go through the process of getting the new file on whitelist.
Wishlist:
1. I would like a vbs file that I can compile into a executable that would:
a. Check for Source folder location exist. If not, then receive message stating Source folder location not found.(meaning not connnected to the network or do not have permission)
b. Check for local Application folder exist. If not, then receive message stating Application not found.
c. Prompt user for 2 options.
i. 'Full Application Update'. Deletes all files contained in program folder location C:\Program Files\AppFolder then copies all source files into program directory. I would just do overwrite but this will be cleaner.
ii. 'Update Current Release Files Only', which will only copy over those files with newer modification date logic.
d. Logs to network share folder file; Username, Computername, [Date, Time(as seperate entries)], Whether Full or Just Update was selected, # Files Copied to workstation.
We are trying to get away from manually updating all together by working on more efficient distribution methodologies, however, having a file that would do the above would really allow us to offer up options when the developers do not follow the logic correctly when modifying the dll's and would allow us to track who is using the manual update so we could address those people and why they are not leaving PC's or laptops in place during release weekends.
Thank you so much for whoever can help with this. I am not an analyst and not a programmer so your help is greatly appreciated.
Also I am open to other languages if vbs does not really fit these requirements. But will like to keep ability to modify, then compile if there are future needs for that.
NOTE! These updates are typically pushed using software to distribute those files and that hits approx 95%. The tool used for updating can take a long time to update those files if the machine is not in a ready state when the initial push occurs. I do not administer that software nor have the ability to 'kick it' to speed up the process for those machines that did not get the update over the release weekend on Monday morning.
The Situation: there is currently a manual 'batch' file available to end users to update those appplication files when they did not get them over the release weekend. HOwever, the logic is set to copy from a source directory only those files that are of a higher modification date than what is currently on the local workstation. Normally this works just fine, however developers have now put out dll files that have an older date than what is on the local workstation thereby causing issues with the application because that one particular file never gets copied to the local machine.
The batch file is on a white list to allowed to run on Credit Card PC's that have additional security measures in place. I would like to get a file that meets the business need here, then go through the process of getting the new file on whitelist.
Wishlist:
1. I would like a vbs file that I can compile into a executable that would:
a. Check for Source folder location exist. If not, then receive message stating Source folder location not found.(meaning not connnected to the network or do not have permission)
b. Check for local Application folder exist. If not, then receive message stating Application not found.
c. Prompt user for 2 options.
i. 'Full Application Update'. Deletes all files contained in program folder location C:\Program Files\AppFolder then copies all source files into program directory. I would just do overwrite but this will be cleaner.
ii. 'Update Current Release Files Only', which will only copy over those files with newer modification date logic.
d. Logs to network share folder file; Username, Computername, [Date, Time(as seperate entries)], Whether Full or Just Update was selected, # Files Copied to workstation.
We are trying to get away from manually updating all together by working on more efficient distribution methodologies, however, having a file that would do the above would really allow us to offer up options when the developers do not follow the logic correctly when modifying the dll's and would allow us to track who is using the manual update so we could address those people and why they are not leaving PC's or laptops in place during release weekends.
Thank you so much for whoever can help with this. I am not an analyst and not a programmer so your help is greatly appreciated.
Also I am open to other languages if vbs does not really fit these requirements. But will like to keep ability to modify, then compile if there are future needs for that.