VB script via gpmc doesn't use pop-up message

September 14, 2012 at 05:59:11
Specs: Windows 7
I have aVB script which contains pops up a message. I need to push this script out as a scheduled task through gpmc. The GP works fine, but the pop up message doesn't show. The scripts ultimately does what it's suppose to do, but the pop-up message just won't show up. The scripts runs fine if you run it directly and/or manually assign to a workstation.

See More: VB script via gpmc doesnt use pop-up message

Report •

#1
September 14, 2012 at 10:17:45
Are you sure the popup isn't popping up? Have you checked to see if it's showing up on a desktop other than the one attached to the local user? Because that's far more probable.

How To Ask Questions The Smart Way


Report •

#2
September 14, 2012 at 10:57:40
I only have one computer in the OU for testing purposes and there is nothing open on the desktop. I've tested it locally and even if applications are open the pop-up still shows.

Report •

#3
September 14, 2012 at 11:17:31
What account does it run under? The same one as the user? Is the job configured to interact with the desktop?

How To Ask Questions The Smart Way


Report •

Related Solutions

#4
September 14, 2012 at 11:40:20
It under the Computer Configuration so it runs under the SYSTEM account. I have tried to specify different accounts for it to run, but that didn't work either. The users don't have admin rights on the machines, but if I manually add the schedule task on a non-admin user workstation it runs properly with the pop-up messages. I have applied the //I switch in the arguments of the scheduled task.

Report •

#5
September 14, 2012 at 13:00:48
I'm talking about the job definition, not the task (wscript).

Let's take a step back. Desktops are tied to the login session, and not any physical hardware. Log in locally to the server? You get a desktop. RDP into that session? Your desktop moves from the local console to your RDP session. Someone RDPs into the server at the same time? Another desktop separate from yours. He disconnects without logging off? His desktop is there, not touching any active sessions. The point? The SYSTEM account has its own desktop. It's a desktop that isn't attached to any user sessions. Now, being the SYSTEM account, it can do anything it wants, including attaching itself to your desktop. And that's what setting the job to interactive mode does.

How To Ask Questions The Smart Way


Report •

Ask Question