

Create your Windows Installations (native) or MasterImages in your main office.ģ. Set up a on premise server in your main office (hq)Ģ. What our Unified Endpoint Management solution baramundi Management Suite could offer you in a case like that is the following workflow:ġ. So easier (but with more preparations required) would be to set up a PXE and TFTP server in you subsidiary to offer a WinPE Image from a network boot.

… and the user has to boot from it on his own. The issue here is you have to be sure, that this stick is up-to-date and also correct for the hardware-type you want to install. You could do this by creating a full bootable USB stick with WinPE and a unattended.xml. Main point for an installation (from usb stick or remote) is to boot a PE on the workstations. If you want to really manage them, you need a bit more infrastructure. You have to decide whether you just want to start remote sessions, so a KVM solution like mentioned before would be good. To manage a remote site can be laborious.
