Jump to content
DeployCentral

Ted Pruitt

Members
  • Content Count

    28
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Ted Pruitt

  • Rank
    Member

Recent Profile Visitors

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

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. And the console still shows as updating drivers - nearly 2 hours later...
  6. 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.
  7. This is in the workstation csv log: 9/17/2019 11:29 WSSPI-23270 192.168.160.48 18:60:24:9D:23:8B 1 DriverUpdateMessageProcessor 2.0.3050 This request operation sent to net.tcp://192.168.160.48:8733/Design_Time_Addresses/SmartDeploy.ClientServiceWCF/Message/ 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.
  8. Title pretty much says it - I have a workstation that has driver updates available. I push it out from the console - console acts like it is deploying. Nothing happens on the workstation end. I've rebooted both the workstation and the SmartDeploy machine. I never get an error and if I leave it, the "deploying" status just continues.
  9. Alright - so as part of my troubleshooting, I uninstalled the smartdeploy client from the machine I was using to test the app deployment - deleted it from "Computer Management" and then reinstalled the smartdeploy client. Now it doesn't show up at all in Computer Management. Both services are running on the Client PC. I can ping in both directions. Any ideas?
  10. So, nada. Although, this showed up in the event log:
  11. Tried that too. I'll give it another go though and report back. Thanks!
  12. ok, I've tried every permutation I can think of - what's the trick to running an MSI in an application pack. EXEs, I have no trouble with - MSIs just fail with no explanation. Attached is the run command - I've tried with a mapped drive and by putting in the full location (e.g. \\servername\folder\msifile.msi) Any help would be appreciated.
  13. I found GPO super unreliable. In most of my cases, it would install but the service wouldn't run so it would back out. I think the client is still a little buggy for GPO install at this stage. Also, to be fair, most of my issues were with Win 7 - since we've pushed out Win10 1809, it was less so, but on new systems, I just invoked the imaging process via PXE boot.
  14. Hey Devon - thanks for the clarification. I think you're right, I'll just recapture the whole image, it's pretty fast. Your advice, however, is slightly contradictory to some of the blog posts that talk about using the differencing wims as a way to have multiple version (e.g. base image, IT image, graphic artist image - each with different software being loaded.) My thought was that it seems silly to create a complete reimage for just (in this case) three little updates. But if that is what you recommend, that's fine. Also - this is the 1903 "LTSC" - NOT the "retail" version of Win10 1903 - so technically, it's 1809, they just named it based on the fact that they released it in March. SmartDeploy even labels it as 1809 in the images listings. Thanks
  15. So I have my base image of Win 10x64 1903 LTSC -- I pushed out a bunch of updates and instead of making a whole new image, i wanted to make a differential of just the updates so I didn't need to create a whole new image, figuring I would do this for every group of updates and then quarterly I would create a new whole image. When I pushed the image as a test, the test machine didn't have any of the updates. So perhaps I'm not understanding the concept. Do I have to push the DWM separately? Does it require making a deployment package and an answer file? Or is there maybe a special naming convention I missed? It appears to me that the computer I pushed to simply received the base image, nothing more. The documentation on differential imaging is pretty sparse. Also, as a future request, would it be possible to do something like they do with snapshots in VM-Ware - in which I could take the delta image and incorporate it into the final image, eliminating the need to recapture everything? Any help would be appreciated. Ted
×
×
  • Create New...