Kamsobe Posted June 5, 2019 Report Share Posted June 5, 2019 I do have several systems in remote offices that will be needing cloud deployments, however the last time I tried to deploy them, it was a catastrophe. Things worked fine when we were using Dropbox as our storage location, but something has gone awry since the change was made to Google Drive. Images and answer files have been changed since then too so this could very well be a configuration issue. My Question: I need to test these cloud deployments on a machine I can get back to Windows myself if things go wrong. However it seems that when the console detects that the machine is on the same network it refuses to initiate a cloud deployment, even if I have checked 'Prefer Cloud Connection'? Is this really intended, and is there any way around this for less risky testing of cloud deployments locally? Link to comment Share on other sites More sharing options...
SmartDeploySupport Posted June 5, 2019 Report Share Posted June 5, 2019 Hello Kamsobe, After clicking the 'Prefer Cloud Connection' option, can you confirm that the connection type changes to Cloud in the console? Here is our KB for cloud push deployment in case something may have been missed in this process. Performing a Cloud Push Deployment Link to comment Share on other sites More sharing options...
Kamsobe Posted June 5, 2019 Author Report Share Posted June 5, 2019 37 minutes ago, SmartDeploySupport said: Hello Kamsobe, After clicking the 'Prefer Cloud Connection' option, can you confirm that the connection type changes to Cloud in the console? Here is our KB for cloud push deployment in case something may have been missed in this process. Performing a Cloud Push Deployment Actually, that does seem to be the hangup. However, now it seems that the issue has to do with the client that was installed and the fact that it isn't showing online in the management console. This seems to be a consistent issue across multiple devices based on symptoms alone. I've only seen hard proof that the service may be botched on one though. Notice what I'm seeing below: The "SmartDeploy Enterprise Client Service" is running fine. However the "SmartDeploy" service was not running at all and was not even enabled. I enabled and set to auto start, and then tried to run. It has been hanging on START_PENDING for at least 30 minutes now. We do have Webroot as our antivirus installed. Although I do not see any logs indicating that it had any part in this, I am open to adding SmartDeploy to a whitelist to ensure that it isn't being blocked. Are there certain directories/files you recommend we whitelist, or an Md5 for the SmartDeploy client since that is supported as well? I'll remove AV altogether to see if that is the issue first. Link to comment Share on other sites More sharing options...
SmartDeploySupport Posted June 5, 2019 Report Share Posted June 5, 2019 Hi Kamsobe, Please go ahead and disable any antivirus software you have installed and try again. We've seen it cause issues with our services. You can also whitelist download.smartdeploy.com Link to comment Share on other sites More sharing options...
Kamsobe Posted June 5, 2019 Author Report Share Posted June 5, 2019 47 minutes ago, SmartDeploySupport said: Hi Kamsobe, Please go ahead and disable any antivirus software you have installed and try again. We've seen it cause issues with our services. You can also whitelist download.smartdeploy.com Removing AV altogether and a reboot later, SmartDeploy still refuses to list this device as a Cloud connection type despite "Pefer Cloud Connection" being checked. Is this intended? Link to comment Share on other sites More sharing options...
SmartDeploySupport Posted June 5, 2019 Report Share Posted June 5, 2019 Kamosobe, Can you restart the console service on the console host first, and then the client? Link to comment Share on other sites More sharing options...
Kamsobe Posted June 5, 2019 Author Report Share Posted June 5, 2019 21 minutes ago, SmartDeploySupport said: Kamosobe, Can you restart the console service on the console host first, and then the client? Boom. That was it... So simple. Still need to make sure AV isn't interfering, but that was the final step to get it to switch to Cloud mode. Now I can resume figuring out why the remote agent can't find the image stored on the cloud. Thank you. I've already sent off the most recent logs via email so hopefully we can get to the bottom of that too. Thanks again, now I know to restart the host service if all else fails. Link to comment Share on other sites More sharing options...
Kamsobe Posted June 27, 2019 Author Report Share Posted June 27, 2019 Unfortunately this is a problem again. I have reset the enterprise service on both the server and the endpoint. The machine still shows as grayed out in Computer Management... I have even tried re-installing SmartDeploy on the endpoint. Is the SmartDeploy service supposed to be eternally "Starting"? No matter what I have tried, re-installing, manually restarting the service, etc. I cannot get it to a state of "Running", it is always starting. Is that normal? Does this service have any impact on cloud deployments? Not only that but anytime SmartDeploy installs the client on the endpoint automatically (during cloning) so that it will appear in computer management, that install of SmartDeploy always seems to leave the SmartDeploy service stopped. I have a script I've prepared just in case that will install and then configure that service to at least automatically start on boot and then start it after install. Is that intended behavior or another bug? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now