Regarding the option to boot using the public Internet to reach a remote deployment server, I don't know about how that could be done in fact, for me that would be something quite interesting to learn about. Quite contrary, if there are few places were those machines are located, the more feasible this task will be for example, by preparing and testing a server, computer or laptop that you then carry to each of those few places and installing the new operating system. The more disperse they are, the more cumbersome this task will be. The network booting option, based on the PXE specification, should be supported by the motherboard of those machines and have higher booting priority than other devices, like CD drives, hard drives, etc.Īnother thing to consider for the couple of options I'm suggesting, is how are those 800+ distributed across the country. Boot the machines to install the new operating system.Properly enable network booting in the BIOS of each of the 800+ machines, unless it has already be done before.Please also note that both options require some network configuration, like DHCP server settings that work with the PXE protocol.Īlso, for your requirement, someone, a human being, would be needed to execute one or more of these tasks: I did a basic test of Cobbler and it worked fine in my environment, being this a way that would be more apt to deal with requirement changes. As long as the prepared base image doesn't change too frequently, the main time consuming tasks would be related with configuring the Clonezilla server and building that seed image.
Of those options, I have used Clonezilla with success. Cobbler, which works like a provisioning server for Linux based machines.Clonezilla, which works by replicating a previously prepared disk image to one or more computers booted inside a network segment.
0 kommentar(er)
