Endpoint Protection

I have a few servers that I'd really like to upgrade from v12 - v14, but they won't be rebooted until sometime next month.  Is it ok to install v14 over v12 and leave the client in a "needs to reboot" state for a few weeks?

I've done that on a test server, and it seems as though v14 is working fine - getting new definitions, reporting to SEPM 14, etc.

Thanks!

You're fully protected, even when a reboot is needed so it's ok and will function as expected, including pulling down content and uploading logs. When 14 is upgraded over 12.1, it will need to replace all the necessary files to complete the install so obviously a reboot is needed. But overall protection/functionality does not change.

Its ok to postpone the restart for few days

SEP 14.0 also employs a side-by-side, replace on reboot installation strategy. Side-by-side means that new files are written to a new folder, referred to as a silo, isolated from the existing operational folder. Because the two versions are separated from each other, during a migration the older software is left running unchanged until the next reboot.

The primary benefit of side-by-side installation and replace on reboot is that the system continues to be protected by the existing software until the new version is in operation after the reboot.

https://www.symantec.com/connect/forums/upgrading-client-12x-14

Is it ok to do with when upgrading from SEPM MP1 to MP2 as well?

Yes but 12.1 to 14 requires a reboot so the sooner the better to take advantage of all of the SEP 14 features.