Basic steps:

• configure your processor per chief's startup guide
• get all zumnet jbox online
  • use built in dhcp from processor control subnet
  • if using proc without control subnet, use showrunner dhcp
• use crestron toolbox device discovery to create a Device Summary
• use chief tools tm tool to generate various zum wired load scripts
  • (need to determine exact process for this; will need to add IP-ID and new hostname to device summary somehow)
  • (will likely generate two versions of the loadscripts; one connecting by default hostname and one connecting by new hostname)
  • (intend to require SR license for zwired LS generator, if only to get the proc mac address)
• if firmware is old, run "zwms master/zum (def. hostname)" loadscript to make all ZUMNET JBOX primary and in app mode in order to enable discovery of devices on zumlink
  • devices will reboot
  • per crestron, 1.0006.00012 and newer ship in primary mode (tbd if they will ship in app mode?)
• connect to a few devices in device discovery tool to ensure that all zumlink devices were automatically readdressed and there are no conflicting cids
  • firmware 1.0001.00081 is new enough that this works correctly
• run "fw update (def. hostname)" loadscript to update the fw for all devices
  • will take up to several minutes per room, but will be able to do up to 10 rooms simultaneously
  • devices will reboot, possibly multiple times
  • check loadscript manager for any failures and re-run script for those devices if necessary (a rebooting zumnet box will temporarily disrupt online status for downstream zumnet jboxs and potentially interrupt the firmware update)
• run "ip config (def. hostname)" loadscript to update device IP-IDs and hostnames
  • devices will reboot
  • devices will now have new hostnames, so any further loadscripts should use (new hostname) versions
• if using a processor without control subnet, run the "static ip config (new hostname)" script
  • this loadscript is necessary, as the showrunner DHCP server is only intended for commissioning. It must always be manually started after program restart and should not be used in production
  • (will probably need a lot of extra steps + alterations to how we make configs since static IPs require a lot more information as well as corresponding modifications to SrConfig.json)