current scenario - I am uploading an exe file to the BigFix server through “Windows Software Distribution Wizard”, which in turn creates a task with action script to download it. After that I am updating the script for other funcionalities like copying the exe to the required location on the server, executing it and executing other tools. Everytime I install a new version of the application I have to do all the above steps right from opening the Wizard.
Required - I need to upload the exe to the BigFix server through Action scripts instead of “Windows Software Distribution Wizard”, so that for every installation I only need to update the action script for the file name and the path. Is there any command to be used in action script to upload the exe to the BigFix server?
If you have any other ideas to automate this uploading part, would be much appreciated.
Does the exe change every time or does the sha1 remain the same. If the sha1 remains the same, you can just right click on the task genereated by the wizard and choose edit to manually make changes without going through the wizard again.
If the exe changes the easiest way to get the files to the server is using the software distribution wizard, but you could also manually place the files on the server somewhere in the wwwrootbes directory. After manually caching the files you can then edit the distribution task manually to reference the new file paths.
I dont have access to the BigFix server to copy the files manually over there. I want to do it through BigFix console preferably using action scripts as the end user(Deployment team) finds it difficult to upload the file using wizard and then updating the scripts (for post installation tasks) everytime. They want it in a way that the task has to be created only once and from the second time (next version of build) only the existing task has to be modified. No new tasks are generated.
Note: The name of the exe changes for every version.
Is ther any plug ins or third party tool to automate(or executing the task everytime with minimal change instead of of going through the wizard again ) the uploading task ?
The root server has a client on it … couldn’t you run a task that copies the file from a network location (could take some work to make this work as the client runs under a local service account which by default does not have acess to network locations … you could use http to transfer it) and then create and copy it to the required folder in the wwwrootbes.
You should be able to get the sha1 and rest of the file paramters ahead of time so that you can then just go in and modify the existing task with the updated file references.
Then the only question is whether or not the system account has access to the required folders … if it does not … then this is mute as there is no way to do it via BigFix unless you have admin credentials on the server, which if you did then this would not be an issue.