I am running EMS 7.2 and have some 7.x clients to upgrade to 7.2.2
Created my Deployment rule as usual
Looks like the user no longer has the option to defer the reboot as previously but rather reboot immediately or defer for short time.
The only way around this from what I have seen, is to apply a scheduled time say 20:00
With this option, users will get a choice to:
Has anyone else seen this change of behaviour and suggest a better way round this? I chose 20:00 on the assumption that most users won't be logged on at this time so it is the least disruptive.
Any advice would be great.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Thanks for the response.
Indeed in order to achieve some notification, a sheduled time has to be set on the deployement.
Problem I discovered was the notification is not always promiment on the system tray for the user to take action against.
If they ignore or do not see the prompt, once the install time is reached the process begins and the reboot can only be dismissed for a short amout of time. Previously, a user could defer the reboot completely.
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1643 | |
1069 | |
751 | |
443 | |
210 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.