Login Scripts
Not having a good week, I'm sure it's related to the Bank Holiday. Brain frazzled.
I'm having a bit of trouble with the Scripting side of things now.
What I want is to use NirCMD in our Modern Languages Lab to reset the Volume settings everytime a user logs into the machine.
I've created the script and it works perfectly when I do a Run Now, however, when I set it to "Don't run on a Schedule" with the "Also Run at User Login" option ticked it wont actually run.
When you log into that workstation, you'll see the KACE Splash screen but the script doesn't actually run.
The log says "Skipping <Script Name> because no user is logged into the system."
It's almost as if the script is running too soon.
Should I be adding a verify or something to make it wait for the login process to finish?
I'm having a bit of trouble with the Scripting side of things now.
What I want is to use NirCMD in our Modern Languages Lab to reset the Volume settings everytime a user logs into the machine.
I've created the script and it works perfectly when I do a Run Now, however, when I set it to "Don't run on a Schedule" with the "Also Run at User Login" option ticked it wont actually run.
When you log into that workstation, you'll see the KACE Splash screen but the script doesn't actually run.
The log says "Skipping <Script Name> because no user is logged into the system."
It's almost as if the script is running too soon.
Should I be adding a verify or something to make it wait for the login process to finish?
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
cblake
12 years ago
Can you not specify a user to run as? Not sure what your script looks like, sharing that might help debug?
Posted by:
Arcolite
12 years ago
All sorted. I didn't change anything, but overnight I suddenly started working. I suspect the script update hadn't happened yet and I was being impatient.
Posted by:
snissen
12 years ago
I don't think you were impatient; I think you're seeing the same thing I'm seeing. When I have an Online Kscript (for a large number of Windows computers) set to run as the logged-in user, it fails about 10% - 20% of the time with this "no user is logged into the system" message, even though I can see, and the KBOX can see, that a user is logged in.
Run the same script over and over again on the same group of computers over several days, and it fails at about the same rate, but on different machines at different times. Running KBScriptRunner.exe or AMPReset.exe on the client doesn't necessarily "fix" the condition, and neither does a logout/login or a reboot. And since the problem is intermittent, I haven't been able to capture a debug log on the agent.
I have a sense, but cannot prove, that this message occurs most often on machines that have been up and running for more than a day. These machines may have had the same user logged in all this time, and may have been locked and unlocked several times. These machines may even have been slept (power options: sleep) and awakened multiple times since the last reboot. But this is not exclusive: I've also seen this "no user" message on newly booted machines with fresh user logins. It's driving me crazy.
Right now, we're still using the KBOX Agent version 5.1.31311 on most machines. I'm testing the newer 5.1 agent on a few machines, hoping this is one of the problems that might be fixed. If anyone out there has a solution, or even an explanation, I'd like to hear it! Sande
Run the same script over and over again on the same group of computers over several days, and it fails at about the same rate, but on different machines at different times. Running KBScriptRunner.exe or AMPReset.exe on the client doesn't necessarily "fix" the condition, and neither does a logout/login or a reboot. And since the problem is intermittent, I haven't been able to capture a debug log on the agent.
I have a sense, but cannot prove, that this message occurs most often on machines that have been up and running for more than a day. These machines may have had the same user logged in all this time, and may have been locked and unlocked several times. These machines may even have been slept (power options: sleep) and awakened multiple times since the last reboot. But this is not exclusive: I've also seen this "no user" message on newly booted machines with fresh user logins. It's driving me crazy.
Right now, we're still using the KBOX Agent version 5.1.31311 on most machines. I'm testing the newer 5.1 agent on a few machines, hoping this is one of the problems that might be fixed. If anyone out there has a solution, or even an explanation, I'd like to hear it! Sande
Posted by:
KevinG
12 years ago
Hi Sande,
I would still continue to upgrade your clients to the latest 5.1 version, since the one you are using has other issues that can affect the performance of your KBOX.
To resolve the "Run As" issue you will need to wait until the 5.3 server and 5.3 client is released.
I would still continue to upgrade your clients to the latest 5.1 version, since the one you are using has other issues that can affect the performance of your KBOX.
To resolve the "Run As" issue you will need to wait until the 5.3 server and 5.3 client is released.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.