Hello - check out the Windows Integration Guide in the Documentation section of Infosight. I just did an upgrade of NWT to a Windows server and a reboot is definitely required. Unfortunately I didn't read this until after, otherwise I would have payed closer attention to the iSCSI connections on that server. Below is a snippet from page 7 of the latest version of that guide.
I've never had any issues with Hosts establishing connections to the Volumes after a reboot. Configurations are preserved during the NWT upgrade.
we have two clusters and two sans (for the corporate: 3x GUI'd Windows Server 2012 R2 running Hyper-V and for the lab: 2x Core'd Hyper-V Server 2012 R2) each running 126.96.36.199, we just upgraded the nimbleOSs from respectively 2.1 and 2.2 to now both being 188.8.131.52-364135-opt & want to also upgrade the Nimble Connection Manager sw on the hosts (the Nimble Connection Manager will be installed from within the Nimble Windows Toolkit download yes? latest online i saw was Setup-NimbleNWT-x184.108.40.206.287.zip)
from what i could gather, going from 2.0 to 2.3 will require a uninstall / reboot / install / reboot of the hosts (please correct me if i'm wrong)
also, since this is the 1st time upgrading the NCM, am curious on how the hosts will see the existing connections that are connected to the cluster during and after the update, will new connections need to be made, will windows the windows hyper-v hosts see the same drives (almost all are CSVs, but two are pass-thru disks for DFS'd file servers)
if need be we can do this during a planned patch / reboot window for the servers
thanks in advance