Jump to content
DeployCentral

Jeff Harris

Administrators
  • Content Count

    250
  • Joined

  • Last visited

Community Reputation

0 Neutral

2 Followers

About Jeff Harris

  • Rank
    Support Team

Recent Profile Visitors

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

  1. A user does not need to log in for Application Packs to begin processing. Following Sysprep, the SmartDeploy client is installed and starts processing App Packs in the background.
  2. We will have a better way to track Application Pack deployments in v3 which should release this Summer. You can look at the Application Log in Event Viewer to see the SmartDeploy Client events regarding the pack being run, and you can also look at the C:\Windows\SysWOW64\SmartDeploy\ClientService.Console.log file to confirm that the Application Pack was extracted and run correctly. (Go to the bottom) However if it's running and the application is still not installing, you'll need to enable installation logging, or test your command in a prompt. You can also send that log and screen
  3. I actually have a Dell Command Update pack (v3.1.3) that I've made for another customer that you can download. It's not an MSI, but an EXE. https://drive.google.com/file/d/1zXTNqB3DcYIMsKAxfLRmcmt64Qj52ka7/view?usp=sharing MSI installs should be pretty easy to do, especially if you use the new Application Pack Wizard. You can always send screenshots of your App Pack config pages to Support and we can help that way as well.
  4. If you're going to make offline media, then you want to copy the image to your local machine. If you're on the same local network as the console host, you can still change the Platform Pack and Application Pack directory to a network share on your console, and the Answer File as well, to pull them down where they'll be copied to your USB media. If you're remote/VPN, then I'd download/copy the image and Answer File to your local workstation. Assuming your direct internet connection is faster, just re-download the Platform Packs via the SmartDeploy Console. Then create your media on the lo
  5. Keep in mind that this will not work if you are creating Offline USB media.
  6. Want to make sure that deployment packages are updated (Right-click > Edit) after a server upgrade to the latest version as well. I'd also send screenshots of the client in Computer Management with the version showing, and the C:\Windows\SysWOW64\SmartDeploy\ClientService.Console.log file to support@smartdeploy.com so we can investigate further.
  7. This error message pops up here and there, and usually doesn't break the process. It could be a problem parsing the Answer File, but you'd want to file a ticket with support and send in the related log for us to look at.
  8. It indicates that the console has not heard from the client for a number of heartbeat intervals. You can still create deployment jobs for these clients, but it will remain in the "scheduled" state until the client checks back in. Sometimes cloud-connected clients can incorrectly appear faded, which we're looking into addressing in the next major release.
  9. Yes, you'd have your image built on the VL media, and the 1 VL key. As long as your image matches the SKU that your OEM license is for, you don't need to re-purchase a license for that machine and it counts as a valid license. Your the vendor for your volume license should be able to square this all up for you.
  10. Technically, Microsoft does require you to be using an image created with VL media, with a VL key to deploy Windows. We don't enforce this, as we simply pass the key that you specify (or no key) to Windows. Many customers rely on the OEM/sigital license with success, and others find that is doesn't work, depending on the installation media used. This particular issue seems to be more common looking at past couple of months. Did you create your Windows installation ISO using this tool?: Download Windows 10 (microsoft.com) We have a KB article that explains reimaging rights in better
  11. That is strange, and not a common issue. If you deploy again and see it happen, we'd be interested to see the C:\Windows\SysWOW64\SmartDeploy\ClientService.Console.log file if you could email that into support.
  12. Following a deployment, the SmartDeploy service should be disabled. This service is used to do a few functions post deployment only, and should disable itself. The SmartDeploy Enterprise Client is a separate service that should be set to Automatic (Delayed) - but will only be there if the client installation was enabled in the Answer File. I've never seen any instances where one affected the other, but if you contact support we can take a look at your image for you and investigate.
  13. This is probably a limitation of the method of installation, being silent command-line as system.
  14. Since it's installing in a pack, it's doing so as System and may not create shortcuts. Are you able to find the exe in the program files dir?
  15. When you create your SDClientSetup.msi package, make sure that you're using the non-FQDN hostname of your console host, and not an IP, or otherwise any other externally resolvable name/IP. The client needs to fail to reach your console host on the network, so that it switches to connect to our cloud broker service. Cloud clients should appear in the console 10 minutes after starting, however sometimes there can be delays upwards of about 25 minutes. Sometimes restarting the console host can force a 'nudge' of the agent that monitors your cloud clients table and get it to refresh faster.
×
×
  • Create New...