Jump to content

Ted Pruitt

  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

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

Ted Pruitt's Achievements


Newbie (1/14)



  1. OK - good to know - after imaging - it's set to Automatic, consistently. This is across 4 different images, deployed to 4 different types of machines (desktops, laptops and workstations.) So this is not isolated to one image. I've been setting it to manual to get the PC to talk to the console - I'll change it to Disabled. I'm not sure I understand how this is an issue with the image itself. Is the SmartDeploy services installed from the image?
  2. As the title suggests, when I finish imaging a client PC, the SmartDeploy service is set to automatic - therefore it gets stuck "starting" and the client doesn't register with the Smartdeploy console. So, now I'm just in the habit of going into the services after I finish imaging a PC and setting the SmartDeploy service (not the SmartDeploy Enterprise Client) to manual. However, when the time comes to remotely image my machines, I can see this as being a huge pain. I'm on 2.0.3085, but this has been going on for awhile, at least several versions. Since the system installs the services AFTER the imaging, I would think it would get set correctly. Any ideas? Thanks --Ted
  3. @brendanshreve - essentially the issue was something disrupting the installation of the pack. SmartDeploy doesn't seem to handle the failure of an installation very well. What I found was this - let's say I pushed out an installation of Acrobat. If some portion of Acrobat was running in memory, the package itself would be copied to the end-user machine, when it would attempt to run on the user's computer, it would see a component running on the end-user computer, then it would just stop (likely the MSI erroring out) would stop the deployment. No error message on SmartDeploy, just stopped. SmartDeploy client then appears to report back that the deployment is "successful" - however, it leaves the package from the previous install in c:\windows\temp - because the previous install doesn't appear to have cleaned it up. Then, if you try to redeploy - the package sees the package there and - for whatever reason - doesn't use it and doesn't try to overwrite it with a new copy of the package. So on this particular computer, the solution was to go into C:\WINDOW\TEMP and delete the deployment package. Then go into c:\windows\syswow64\smartdeploy\sources and delete the files in there. Reboot the computer (to make sure there is no component running) and in the computer's "pristine" state of just being rebooted - THEN deploy the package. As a habit now, if I have a package to deploy, I ask users to restart their computers and then I deploy it and call them when it's done to tell them they can log in. If I have a mass-deployment, I ask all users to reboot and leave their computers in that state or I do a mass-reboot of PCs from PSShutdown and then deploy. If Jeff or any of the guys at SmartDeploy have another idea of a better way to deal with this - let me know! Hope this helps, Brendan.
  4. 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!
  5. 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
  6. 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"!
  7. 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?
  8. Just to add - even with application packs I've downloaded from SmartDeploy - they are hit or miss. I've pushed out FileZilla as an example. With no issue previously. Went to push it to someone today and it wouldn't push.
  9. Thanks Jeff - I've done this with other MSI installs - sometimes it works, sometimes it doesn't. I understand the process. But honestly, application deployment for me has been very hit or miss. It would be an awesome feature - but it's not terribly reliable. Perhaps I'm missing something. I don't seem to be able to troubleshoot it very well. The logs - at least where i'm looking don't really offer any help. And the event logs on the PC doesn't have anything. I've rebooted both the SmartDeploy workstation and my PC. Other pushes seem to work fine - driver updates for example. Not sure where to start with tracking this down.
  10. I've tried the .EXE and .MSI and can't get either to install - it doesn't even show up in the logs. So I'm not sure where I'm failing.
  11. We leave all ports open inside our network - and both the workstation and endpoint exist on this inside net. So ports aren't an issue.
  12. There is no connectivity issue in regards to the network. Can ping both directions. If there are no new drivers - that's fine, but would make some sense to reflect that either in the status or in the log. I'll look for your email. Let me know what logs you need.
  13. This is in the workstation csv log: 9/17/2019 11:29 WSSPI-23270 18:60:24:9D:23:8B 1 DriverUpdateMessageProcessor 2.0.3050 This request operation sent to net.tcp:// did not receive a reply within the configured timeout (00:01:30). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.
  • Create New...