Our users are given the ability to postpone the deployment of patches to there machine for a certain length of time. Once the patches start to deploy and the beginning message/reboot message is displayed all is going well. The question that I have is that our users will sometimes get the beginning messages about patches being applied but there is no required reboot so the users are not informed that Big Fix has completed. Any suggestions on how to have a message displayed telling users that Big Fix is finished?
In this situation I think the best you could do would be to display a message box while the action is running. That box will disappear after the action completes.
You do seem to need to do a restart to get a post action message box. The intended behavior was not to display a message after the action runs unless there is user interaction needed, like for a restart. This way the client is as silent as possible to the end user. Could you help us understand what the intended purpose for the post action message is if there is no restart?
A final possible solution would be to create a custom message box and add a post-action script to display it. This would take a little bit of custom work to do.
Here’s an action script I’ve used before to display a simple ‘Completed’ message (Windows only). You could use this as a post-action script for a multiple action group in BES 6.0:
delete _appendfile appendfile On Error Resume Next appendfile strComputer =
"." appendfile Set objWMIService = GetObject(
"winmgmts:\\" & strComputer & "\root\cimv2
") appendfile Set colItems = objWMIService.ExecQuery(
"Select * from Win32_ComputerSystem",,48) appendfile Dim curUser appendfile For Each objItem in colItems appendfile curUser=objItem.UserName appendfile Next appendfile
if curUser
"" THEN appendfile
' msgbox "There is a user logged in" appendfile Dim sTitle appendfile Dim sPrompt appendfile sPrompt =
"Patching Complete" appendfile sTitle =
" Status " appendfile msgBox sprompt, 0, sTitle appendfile
' wscript.echo("""" & curUser & """") appendfile end
if move __appendfile prompt.vbs run
"{pathname of client folder of site "BESSupport
" & "\RunQuiet.exe
"}"
"{pathname of system folder}\cscript.exe" prompt.vbs
Jason Honda from Bigfix states in another thread: “BES Client service does not run with “Allow service to interact with desktop” privileges. This was a change I believe Vista and later that services by default do not have that permission … with 8.0 and later of our platform.”
Use this actionscript to set your agents to interactive. Note that it will be effective the next time the service is cycled.
waithidden cmd /C sc config besclient type= own type= interact
we’re working on a way to do it temporarily, just for as long as you need to run the pop up… running with interaction is arguably not the most secure practice.
Jack, I understand it isn’t the most secure way, but it seems to be the only way to maintain full functionality on the client in 8.x. There are situations where we very intentionally need interaction. When the nuances of the “temporary interactivity” that you’re working on have been ironed out, I’ll be the first in line to try it. If I can maintain full functionality with the update, then I’ll turn down interactivity on the service. Any ETA on the fix?