SmartDeploy Launching Agent always runs on clients since 3060?

[Ted Pruitt]

Is this by design? Since I installed .3060 - and SmartDeploy pushed the new agents, all of my clients have their SmartDeploy launching agent in "Automatic" mode - I thought it was supposed to be manual? It also seems to be perpetually "starting"

If I log into an individual user and kill the agent task, go into services and set it to manual and then restart the machine, it seems to work correctly.

Any ideas?

[Ted Pruitt]

Oh - and more fun -- I just installed .3065 to see if that might fix the problem and all of my clients are getting the orange exclamation triangle saying "install error"!

[Ted Pruitt]

ok - so, something fixed after I rebooted the deployment workstation - so now .3065 has install on the remote PCs. I'll check a few and see if it installs properly. But could you please clarify if it's still supposed to be "manual" or "automatic"?

Thanks

[Jeff Harris]

Hi Ted, 

I can confirm that there were some instances observed where the "SmartDeploy" service was stuck on 'Starting" on systems deployed with .3060. This is a service that's used in deployment and should be expected to be disabled, and not running. 

To be clear, this is different than the "SmartDeploy Enterprise Client Service" service that will only be present if the option to install the Client was enabled in the Answer File, or manually installed after deployment. This service should be set to Automatic (Delayed), and running. 

[Ted Pruitt]

And do you believe this was fixed in 3065? I just looked at a small sample in my enterprise - but they do now seem to be running as expected with the service set to manual. And, yes, aware of the difference between the 2 services. Thanks!