Hi all
We're migrating from 8.8 to a brand new 9.0 SP2 core and database. Having read the "Best Known Methods for Agent Config & Deployment" (http://community.landesk.com/support/docs/DOC-7474), we discovered the agent, unlike previous versions, requires a reboot. LANDesk Support confirmed this is because of the new v8 AV engine. I have checked the state of a deployed agent and all is fine except the AV service (and system tray icon) are no running until after a reboot. It doesn't matter whether it was a full client push, Advance Agent or GPO deployment; the machine still needs to be rebooted to start the AV service. This poses the obvious deployment headache surrounding how we reboot users machines. We could:-
1) Select "do not reboot devices after configuration" but it is not uncommon for many users not to reboot their machines for days or weeks or even longer.
2) Select "reboot devices if necessary" but this forcibly reboots the machine without any warning and will cause users to loss unsaved work, which is not an option.
3) Select "reboot with user option to cancel" but the message is ambiguous so users will be inclined to select cancel; they will likely cancel even if they understand the consequences. The options to delay or reboot (without cancel) would have been better here.
4) Deploy the Advance Agent MSI as a computer GPO during the startup scripts which installs the agent then reboots the machine before the user can logon. Despite having to rely on users rebooting their machines, this may be the best option we can think of but we need to test it works in our environment where all users do not have admin rights.
Would others agree? Is there a better deployment option we have overlooked that would install the agent & reboot with minimal of disruption please?
Thanks in advance
Scott