- This topic has 7 replies, 2 voices, and was last updated 5 years, 5 months ago by .
-
Posts
-
I have created a number of deployment software packages and have been successful. This week i am updating one of my packages and when deploying it, get stuck at “Deployment: Queued”. I don’t seem to be able to figure out how to proceed or execute the request.
OK, glad you got everything working.
Your support expiring would have no impact on the functionality of the app. I’m honestly not quite clear on what you’re describing with your licensed version vs the free evaluation. Are you saying that in your licensed version you encounter the issue but then you downloaded the free evaluation and you’re not encountering the issue there? It doesn’t really make a ton of sense because they are the same application… only the eval has some restrictions. But the actions themselves are all executed with identical code. What works in one will work in the other, so maybe you are launching them on different computers or under different user accounts, or are they different versions of the app? Those are the only things that could potentially produce different behavior from one to the other. I’m not quire sure from your description alone what’s really going on. I would suggest you start with this troubleshooting guide to narrow down what might be happening or where it’s occurring. The more info you’re able to provide to me, the more likely I’ll be able to help you get to the bottom of it. For example is it just that one package that is problematic? Or are all packages not working? And were all of these packages previously working and have now stopped without any changes to them?
Normally if you can get info like MAC address but can’t do Windows Updates, then the issue is something with PsExec. In your case it doesn’t really add up that Windows Updates works but Deployments are getting stuck. Generally it should be all or nothing. Either both should work or both shouldn’t. It’s peculiar that one would and the other wouldn’t. Seems like certainly one quick option for you would just be to move the licensed app over to the working computer. However, if you would rather get to the bottom of the actual issue on the problematic computer… to be precise which of these two messages are you seeing?
Deployment: Queued...Deployment: Queued file copy operation...Are you running BP as a different user than the logged-on user? I mean are you launching BP by right-clicking the batchpatch.exe and using ‘run-as’ to run it as a different user? Or are you logged on with the user account that is running BP? Or are you entering “alternate credentials” into a given row per target?
The things to look at relating to psexec are:
1. Is Windows blocking it from running or is Windows popping up a dialog in the background (or possibly hidden altogether if BP is being run as a different user than the logged on user) where Windows wants you to confirm that it’s ok to run the app. This can happen when you download an exe from the internet. Windows pops a “File insecurity” warning that it wants you to acknowledge, and there is a checkbox to either check or uncheck to prevent it from appearing again. Another way this manifests in Windows can be rectified by right-clicking on the psexec.exe and viewing the properties window. There is a “blocked” or “unblocked” or similar checkbox (I forget exactly how they word it) that can be checked or unchecked to unblock psexec.exe.
2. If you have some type of security related or anti-virus software that is blocking psexec, one option that frequently can be used to get around it is under ‘Tools > Settings > Remote Execution > Use PsExec -r switch to specify a remote service name.’ You can give it a custom name like BPExeSvc or similar. And if that doesn’t work you could try disabling or removing any antivirus or similar security related software altogether.
- You must be logged in to reply to this topic.