one question. On your client PC that isn’t working, are you actually looking at it, or are you RDPed into it?
It is a VM that I am looking at via the VMWare vShphere client which should be as though I am sitting at a keyboard and mouse on the system (in theory at least). I know that I can also RDP into it and, at that point, it looks as though I were sitting at a local system with someone else RDPed into it.
one question. On your client PC that isn’t working, are you actually looking at it, or are you RDPed into it?
It is a VM that I am looking at via the VMWare vShphere client which should be as though I am sitting at a keyboard and mouse on the system (in theory at least). I know that I can also RDP into it and, at that point, it looks as though I were sitting at a local system with someone else RDPed into it.
Good. I asked because I know sometimes if you RDP into a server, you don’t always see the popups because the popup displays on the console desktop, not the RDP users desktop.
{quote:title=Jeremy Lam}It looks like you are using Windows 7 but want the Client to interact with the local user. Have you enabled the client to interact with the desktop?
There is a Fixlet in BES Support, Enable BigFix Client Interacting with Desktop (ID 540), that sets this.
{quote:title=Paul Haines}You might want to make sure you’re using the latest version of RunAsCurrentUser. I think the one you’re running is the oldest version.
Thanks Paul. I will report back with my findings.{quote}
Both with and without the interact with desktop fixlet applied (rebooting between fixlet applications…just to be sure), the Action Scrip utilizing the new runascurrentuser.exe fails to launch the Internet Explorer web page.
For the record, the new Action Script looks like this:
For what it’s worth, you’re giving the prefetch a (saved) name as RunAsCurrentUser.exe, so launch it as RunAsCurrentUser.exe rather than as RunAsCurrentUser-2.0.3.1.exe.
I’m testing out a portion of your action to see what happens.
{quote:title=smbober}{quote:title=Paul Haines}You might want to make sure you’re using the latest version of RunAsCurrentUser. I think the one you’re running is the oldest version.
Both with and without the interact with desktop fixlet applied (rebooting between fixlet applications…just to be sure), the Action Scrip utilizing the new runascurrentuser.exe fails to launch the Internet Explorer web page.
For the record, the new Action Script looks like this:
No problem.
Btw skipping the deploying of the patch, launching the browser did work for me. I’m also using Windows 7 (32-bit).
Paul
Yeah. If I recall correctly, at one point, I just commented out anything relating to the service pack, and it did work.
boggle
. Of course, that defeats the purpose of what I am trying to accomplish. Also, thank you for pointing me to the newer runascurrent user and also for testing this out.
{quote:title=Paul Haines}No problem.
Btw skipping the deploying of the patch, launching the browser did work for me. I’m also using Windows 7 (32-bit).
Paul
Yeah. If I recall correctly, at one point, I just commented out anything relating to the service pack, and it did work.
boggle
. Of course, that defeats the purpose of what I am trying to accomplish. Also, thank you for pointing me to the newer runascurrent user and also for testing this out.{quote}
Hmmm, I tested out the original item without any of the service pack actions and it also opened up a web page for me on a Server 2008 x64 system.
Are you giving enough time for the action to download and complete? Is the action returning “completed” without opening the web page? I ask because the service pack is over 900MB, which is going to take some time to download.
{quote:title=smbober}{quote:title=Paul Haines}No problem.
Btw skipping the deploying of the patch, launching the browser did work for me. I’m also using Windows 7 (32-bit).
Paul
Yeah. If I recall correctly, at one point, I just commented out anything relating to the service pack, and it did work.
boggle
. Of course, that defeats the purpose of what I am trying to accomplish. Also, thank you for pointing me to the newer runascurrent user and also for testing this out.
Hmmm, I tested out the original item without any of the service pack actions and it also opened up a web page for me on a Server 2008 x64 system.
Are you giving enough time for the action to download and complete? Is the action returning “completed” without opening the web page? I ask because the service pack is over 900MB, which is going to take some time to download.
I have taken the action and waited for the entire service pack to install. But, the latest round of testing with the new runascurrentuser.exe was done with an error in the Action Script where the prefetched item’s name did not equal the name of the .exe that I was trying to run. So, I am the process of re-testing.
I figured that out after actually fully and completely reading your modification to the prefetch section. I just assumed (I know. I know.) that you were like me in that name you pull from the web server=name you give the thing you are prefetching=name you call…not so much this case.
{quote:title=Jeremy Lam}{quote:title=smbober}
Yeah. If I recall correctly, at one point, I just commented out anything relating to the service pack, and it did work. boggle. Of course, that defeats the purpose of what I am trying to accomplish. Also, thank you for pointing me to the newer runascurrent user and also for testing this out.
Hmmm, I tested out the original item without any of the service pack actions and it also opened up a web page for me on a Server 2008 x64 system.
Are you giving enough time for the action to download and complete? Is the action returning “completed” without opening the web page? I ask because the service pack is over 900MB, which is going to take some time to download.
I have taken the action and waited for the entire service pack to install. But, the latest round of testing with the new runascurrentuser.exe was done with an error in the Action Script where the prefetched item’s name did not equal the name of the .exe that I was trying to run. So, I am the process of re-testing.
So, at long last (thanks to the fine people here), I have something that pops open an Internet Explorer page. Now, for the kicker, is there any way to get this web page to pop up prior to the user clicking the take action button? Or, would that have to be a separate fixlet set to run with no dialogs? The goal here (and I am taking baby-steps to it) is to pop a web page explaining to the user populace exactly what this action window is, how long the service pack will take, will it reboot the computer, yadda, yadda, yadda.
{quote:title=smbober}{quote:title=Jeremy Lam}
Hmmm, I tested out the original item without any of the service pack actions and it also opened up a web page for me on a Server 2008 x64 system.
Are you giving enough time for the action to download and complete? Is the action returning “completed” without opening the web page? I ask because the service pack is over 900MB, which is going to take some time to download.
I have taken the action and waited for the entire service pack to install. But, the latest round of testing with the new runascurrentuser.exe was done with an error in the Action Script where the prefetched item’s name did not equal the name of the .exe that I was trying to run. So, I am the process of re-testing.
So, at long last (thanks to the fine people here), I have something that pops open an Internet Explorer page. Now, for the kicker, is there any way to get this web page to pop up prior to the user clicking the take action button? Or, would that have to be a separate fixlet set to run with no dialogs? The goal here (and I am taking baby-steps to it) is to pop a web page explaining to the user populace exactly what this action window is, how long the service pack will take, will it reboot the computer, yadda, yadda, yadda.
Alternatively, I would take the ability to add a hyperlink in the various fields that can be filled out for Actions. And to head the questions off at the pass, the reason that I just don’t use the fields to display the message that I would like to convey, is because there is too much information that gets glossed over when the description field starts reading like a book. Finally, why not make it an offer? That would be cool, if the offer could be set to pop up and periodically nag the user. But, the way that it currently works is that the offer is popped up once and is either forgotten or it disappears before the user sees it. Since our users don’t know to look for offers on a periodic basis (90+ percent of our actions are done behind the scenes), the offer will go unnoticed.
Also, thank you for pointing me to the newer runascurrent user and also for testing this out.