Jump to content

Jeff Harris

  • Posts

  • Joined

  • Last visited

Everything posted by Jeff Harris

  1. Please contact us in support, and we can investigate the issue. We'll want to make sure that the MongoDB service is starting, and add a dependency for the SmartDeploy API service to not start until the MondoDB service has also started. We're releasing a new version that addresses this and other bugs discovered since release soon, but the command to add that dependency is: sc config sdapiservice depend= mongodb We have also discovered that some users have a service that's using port 8080, which affects the SmartDeploy API service. Running netstat -ab will give you a list of everything that's using a port and you can determine if this the case for you. We're working on a solution for this in situations where users cannot remove the other application that's using port 8080.
  2. George, you were downloading an app pack that pre-dates the Application Pack wizard. Because we cannot redistribute Adobe installers, we have to prompt you for the installer. Those are available here; https://get.adobe.com/reader/enterprise/ I've also replied to your email in Support.
  3. You can try either creating a blank text file and copying it into the folders, or cut/pasting the files out and back into the SmartDeploy folders to refresh the console. I'd also confirm that the console is remembering your username and password when you open it. If it's not despite checking the box, it could indicate there's an issue with reading the database.
  4. The error in the Media.log I see is; "Exception Message:Key not valid for use in specified state." This is due to a certificate issue on the SmartDeploy host. Please follow these steps to fix your issue and make sure that you are removing the certificates from Local Computer, not Current User. 1. Uninstall the SmartDeploy console for your new computer. 2. Go to settings and search for "Manage Computer Certificates" 3. Delete the SmartDeploy Console certificate from Local Computer - Personal - Certificates 4. Delete the SmartDeploy Console certificate from Local Computer - Trusted Root CA - Certificates 5. Reboot your computer 6. Make sure your antivirus software is disabled and reinstall the SmartDeploy console Then try re-creating your media. If you still have problems, please contact SmartDeploy Support directly.
  5. You can certainly email screenshots to Support (or share them here if you like) but I would recommend adding the registry changes as direct tasks in an Application Pack. Here's a sample one I just made that would add or change a reg value named "Enabled" and set it to 1 in the key you see here. This method works pretty well.
  6. 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.
  7. 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 screenshots of your Application Pack to Support and we'll help figure out what's going on.
  8. 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.
  9. 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 local workstation.
  10. Keep in mind that this will not work if you are creating Offline USB media.
  11. 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.
  12. 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.
  13. 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.
  14. 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.
  15. 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 detail here: What SmartDeploy Users Should Know About Microsoft Reimaging Rights : Support Center
  16. 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.
  17. 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.
  18. This is probably a limitation of the method of installation, being silent command-line as system.
  19. 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?
  20. 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. If you're still having trouble, reach out to support@ and we can look up your account and see what's happening.
  21. When you choose 'Platform Pack Request' on our form, instructions will appear for you to download a VBS script from us. This will gather the hardware information we need, saved as wmi.txt in the same folder that the script is run from.
  22. We typically do not build Platform Packs for new models as they release, unless it happens to be a model/device that we use in house. We rely on customers to request new Platform Packs, and providing us with WMI information. If you need a Platform Pack for the 440 G8 to be created, please submit a Platform Pack request on our support portal: Submit a ticket : Support Center (smartdeploy.com) We officially state 5-10 business days from receiving the request before a pack is created, however depending on the current queue, it is much faster than that.
  23. Copying form the other thread, you will want to get Win 10 v2004 installation media and install to a new virtual machine, add your software as needed and capture a new VM. Updating Reference Virtual Machines to new major Windows 10 versions often leads to problems in deployment, and/or performance afterwards.
  24. You will want to get Win 10 v2004 installation media and install to a new virtual machine, add your software as needed and capture a new VM. Updating Reference Virtual Machines to new major Windows 10 versions often leads to problems in deployment, and/or performance afterwards.
  25. If it's doing it after you log back in, I would guess that there were multiple deployments send to your clients. Each time you click through the steps to deploy an image or application, it creates a message for the client to do so. You can have multiple deploy messages queued and the client will continue to process them one after the other if there. You can email support@smartdeploy.com and we can confirm if this is what's happening.
  • Create New...