Pro-tips exist to help you get work done faster, better and with less errors. Many people run into issues with deploying multiple computers, so this is dedicated to tips that might save you time and money.
When I say "multiple systems," I mean more than five computers at once or if you have plans to do identical deployments at other sites. These can be new copper, laptops, virtual machines or desktops. Most systems deal with Microsoft, so I will focus on that.
Document
As usual, you can save a lot of time if you document the exact requirements of your task beforehand. Perhaps you know that you need to get thirty laptops with TIA Portal, Putty, Notepad++ and Office for use in an air-gapped system. Before you do anything else, ask yourself some questions...
Are you using Active Directory?
If you are using Active Directory, you can probably deploy with it. If you are not sure what Active Directory is, check this link out.
Which components and versions of each software are you using?
Team members often make the same mistake: adding the wrong software version or leave it in the wrong place! Staff unfamiliar with the software they are installing can also get the wrong versions, which is compounded when they are tired, rushed and/or inexperienced... For example, TIA Portal has a separate software for the HMI and drive configuration. This is something to figure out before you start installing.
Are the laptops identical?
If so, you might be able to get away with imaging everything, rather than more complicated deployments.
Confirmation
Once you have answers, write everything down and get all stakeholders to agree. I would really put this in an email, with a comment "Please respond only if you disagree, including corrections, by close of business on MM/DD/YYYY."
Save future you time
While you go through an installation, take extra time to take screenshots while you go. Invest the time in documenting your method, mistakes and corrections. If you are only doing these installations once every few years, future you will be grateful.
Automating your deployment
Deployments can be done manually. If you are trying to train new staff, I actually encourage you to have them do at least some of this by hand. However, time spent clicking "next" is time they could be spending on other tasks, so you want to balance it out.
To automate things, you need to know the customer requirements, variations and hardware.
Imaging identical hardware
An image is an identical copy of your hard drive. With this set up, you completely set up all software on one machine. After that, you "clone" it and then "restore" it on each of your other computers. Yes, it is that easy!
If you are going to use imaging, I strongly recommend Clonezilla or RedoRescue. Both are very user friendly. In the event you are stuck working on older machinery, you may need to use RedoBackup instead. The interface is similar but you may have some digging to find it.
Installation options on differing hardware
If you look up "software deployment," you will find a number of paid options. Some are free or built in. You will need to check out these in more detail.
Windows has an option built-in: client provisioning packages. This allows you to make a general installer, which will be rolled out on individual client devices. You can set up a lot using this. (If you like this, check out Powershell, which is a fabulous way to up your IT game!)
The paid option I have heard the most about is Acronis. This will allow you to back up your system, deploy variations to different devices, etc. It even has a free trial (as of the time this was written)!
Pilot testing
Before you do all devices, try doing a dry run on 2-3 of your units, with each variation. Make sure it works, so you do not have to re-do this process with your full set!
I hope this helps you
Comments