(imported topic written by latchy91)
I wish to deploy a fixlet that displays a message to the users and then launches a HTML page with further instructions.
Can you advise?
(imported comment written by BenKus)
Do you know how to do this from the command line if you were sitting at the cmd prompt of the system?
Ben
(imported comment written by gjeremia91)
Why not create a fixlet with action:
run “\iexplore.exe” “URL”
Now deploy that fixlet and set a message on the action !!
(imported comment written by gjeremia91)
better yet use {default web browser} to deterine which browser to use to open the URL.
(imported comment written by BenKus)
Hey gjeremia,
I think this is a good approach, but there are a couple notes:
- On my Vista/IE7 computer when I tried this before, the IE window was unresponsive after it opened… not sure why.
- You probably need to “RunAsCurrentUser” (http://support.bigfix.com/cgi-bin/kbdirect.pl?id=392) to make sure the window appears to the user (or it might launch but not be visible to the user)… This is also important for security reasons too (or you will potentially give a user an IE window running as SYSTEM).
Ben
(imported comment written by latchy91)
Thank you all for your replies.
To answer Ben’s question “Do you know how to do this from the command line if you were sitting at the cmd prompt of the system?” the answer is unfortunately no.
Can you please tell me how do I “set a message on the action” as gjeremia suggested?
So far in my action I’ve got:
Setting “_BESClient_Resource_WorkIdle”=“125” on “{now}” for client
Setting “_BESClient_Resource_SleepIdle”=“375” on “{now}” for client
wait “{pathname of client folder of site “SecurityProd” & “\RunAsCurrentUser.exe”}” {pathname of regapp “iexplore.exe”} http://servicedesk.companyname.com/restofURLname
Setting delete “_BESClient_Resource_WorkIdle” on “{now}” for client
Setting delete “_BESClient_Resource_SleepIdle” on “{now}” for client
I want a windows message to appear with the message: “Your system is currently running an older version of X software. X does not support this old version anymore; we recommend you kindly upgrade to the latest version X.X The instructions to upgrade is provided in following URL"
The product owner doesn’t want the URL to just launch without a windows box first appearing explaining why the URL is showing up.
Thank you in advance. L
(imported comment written by gjeremia91)
if you want to use a windows message instead of a BES Client UI message, then I would suggest cobbling together a bit of VBScript and useing MessageBox
There seems to be another BES Utility (BFMsgBox.exe) that exists in another site that, if you have deployed, you may be able to use. Is it necessary that the message be a “windows message” or are you ok with it being a BES Client UI Message ?
How do you set a message on action:
When you deploy a fixlet the “Take Action” dialog is displayed. There are several tabs (Target, Execution, Offer, Message) - you want the “Message” tab. In this tab you can configure a message that the user should receive before the action is taken. You can even allow the user to cancel the action.
Information about the Messages Tab can be foud on p135 of the BES Console Operators Guide (http://support.bigfix.com/product/documents/BESConsoleGuide-72.pdf)
(imported comment written by latchy91)
Thanks gjeremia for your reply.
We use BDE to run fixlets as opposed to using BES Console. I tested it in our pre-prod BES Console and the message tab works so thanks for the tip!
If I could just incorporate that method into BDE it would be perfect.
L
(imported comment written by BenKus)
Hey latchy,
There is a way to embed an “action setting” message box in BDE (depending on your BES Client version), but you probably should route this question to your support contacts… BDE is not commonly used with BigFix customers (most with author using the BES Console). I believe the version of BDE that you are using will require you to embed XML into a custom field and encode some line endings to get this to work.
Ben
(imported comment written by latchy91)
Thanks Ben,
I have talked to my support contacts and they are automating this fix so fixlet is no longer required. Thanks for the info though.