I'm managing a script that's scheduled to run on several machines across different data centers. Each time I update or modify this script, I need to ensure that every machine has the latest version. However, using a network file share isn't feasible since these machines are spread out in various locations. I've attempted to implement a solution where the script checks for updates and pulls the new version when available, but I'm struggling to find a reliable approach. Currently, I use an SMB share for machines within the same data center to check modification dates, but this solution falls short for machines in separate data centers. Has anyone else faced this challenge, and what strategies do you use to manage script updates effectively?
1 Answer
Keeping it simple could be key! If your data centers aren't interconnected, you could set up DFS (Distributed File System) and reference your script through a UNC path for local access. It simplifies administration significantly. If you want to dig deeper, consider hosting the script on a web server and creating a version-checking script that updates the local copy, but that adds complexity and risks.
I think limiting the number of locations is essential. I've tried one script per data center but realized I'm still managing multiple copies. Now, I use a macro to connect via RDP or SSH into machines for updates—it's time-consuming but it gets the job done.