Jump to content
DeployCentral

Kamsobe

Members
  • Posts

    7
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Kamsobe's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hi, I know how the licensing works. I understand that only devices that are going to be no longer used in any capacity should have their license revoked. That is not my question. One of my clients has many sites. So instead of shipping a decommissioned machine back, they may just dispose of it themselves at that location. I do not always get the memo... I want to know how the status indicator works so that I have another failsafe to catch machines that have been decommissioned without my knowledge. That way I can at least not waste a SmartDeploy license.
  2. I'm curious what the criteria for the "Active" status on the licensing page is? Over a hundred endpoints and all are green. While I don't think that's completely unlikely, I want to at least make sure I understand what the criteria is for a green "Active" status is so that no broken and old machines are still using up a license for too long. Is there a certain period of inactivity before the status will change color? Thanks
  3. 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?
  4. 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.
  5. 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?
  6. 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.
  7. 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?
×
×
  • Create New...