we are using FRP in connection with ePO on prem, and, we are looking to upgrade our FRP clients from 5.0 to 5.3, and I was wondering what would be the best way to go about this.
Our user base is high-key and not very fond of reboots. Obviously, we would therefore prefer to just push the client down from ePO, install it silently over the old version without a reboot. However, the documentation mentions that for an upgrade you need to uninstall the old client and then install the new version. The uninstall section as well as the install section of the docs mention required reboots. That would mean to restarts just to upgrade FRP.
Documentation says deployment will force a reboot, so testing on 5 systems, I haven't seen a reboot took place after successful deployment. The client's FRP upgrades to 5.3, ePO reports the client has 5.3, however, if you look at the task log, still remains "In progress" until you manually reboot the system.
FRP installations require a reboot. When deployed through ePO, the reboot may not be enforced. I think this is also a setting in the Agent configuration. For us, some clients reported the version correctly immediately after installation. Others did not. We just deployed the FRP client out and waited for users to reboot. FRP continued to function between installation and reboot.
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.