This might be elementary but I can't find a related topic or howto after searching for a bit.

When our IT dept "services" our VM Windows server 2008 they do not log back in as our user. This stops all jobs from running.

Is there a way to test for who is logged in, log them out if need be, and log back in as our user (who has permissions to various job components)?

Regards,
Daryl

Anybody?
This has the potential to cause havoc on a random basis. 😞

Please let me know if I'm just being dense 😕 and/or if it's not possible.

I'm looking for (and please excuse my syntax)
1. query server to see who is logged in, or if it is in a logged off state
2. if the incorrect user is logged in, log them out and log in the correct user
3. if no user is logged in, log in the correct user

Regards,
Daryl

What you are trying to do seems hard. I think we need to find out what the main problem is - I mean, there is no particular reason that Jobs should fail just because someone logs in?

1. Are you using Foreground Tasks?
   
2. Is the VisualCron service running as SYSTEM?
   
3. What errors do you get in the log when this happens?

---

What you are trying to do seems hard. I think we need to find out what the main problem is - I mean, there is no particular reason that Jobs should fail just because someone logs in?

1. Are you using Foreground Tasks?
   
2. Is the VisualCron service running as SYSTEM?
   
3. What errors do you get in the log when this happens?

1. Yes, but until today that was not a problem. The issue of ITS department logging out the one credentialed user was resolved with a visualcron routine.

2. I'm fairly certain, but please see attached picture regarding how the visualcron service is running to make sure we're on the same page.

3. The error message across all jobs is "Exception in task: Could not find the specified Connection for Foreground execution." No problem with Foreground execution until now.

Ok, you have probably set the Foreground settings too narrow (perhaps limiting to a certain session). Please post a screenshot of those settings.

---

A little background: I have access to the AD directory but have created a local user to act as administrator (gsatech).

All job setups regarding foreground/background execution are set identical to the attached screenshots.