Jump to content
DeployCentral

SmartDeploySupport

Administrators
  • Content Count

    687
  • Joined

  • Last visited

Community Reputation

0 Neutral

2 Followers

About SmartDeploySupport

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling
  • Location
    Seattle Washington
  • Interests
    Deploying Windows with SmartDeploy

Recent Profile Visitors

9,165 profile views
  1. Hi Jay, I think we'll need to see some logs and ask a few more questions on this - can you submit a support ticket here, and we can assist further? Be sure to reference this DeployCentral thread. Glenn SmartDeploy Support
  2. Sent. Being able to ping both ways is encouraging, but there are specific port requirements that may not be met here (8733 is one of them, which is referenced in the error message above). We should be able to see what's going on in the event logs in any case; we'll be in touch. Glenn SmartDeploy Support
  3. Hi Ted, Sounds like it may be a connectivity problem, but if we can take a look at the Application event log from the endpoint, we can see if if received the command and tried to follow it. Also possible there simply weren't any newer drivers available, as everything installs silently, and the device only reboots if a particular driver requires it. I'll send you an email shortly. Glenn SmartDeploy Support
  4. Hello, We are glad you're happy with SmartDeploy! You were right in containing the security software as an application pack. Security software and anti-virus software can cause issues if installed on the image as it can break sysprep, capture issues, etc. You can also install it as a post image task. Most customers install applications on the image, or install the base applications all their users need, then deploy application packs for any unique machines that need a couple different applications. You could also make separate images for those users as well. It's really up to you. We recommend installing your applications on the image so you don't have to do any steps after the image is laid down. There is really no pro or con. I hope that answers your question! Thanks, SmartDeploy Support Devon
  5. Hi Scott, Yes, you will need to recreate your deployment package and select the updated answer file during the process. Thanks, SmartDeploy Support Devon
  6. Chris, Thanks for clarifying. You can install the SmartDeploy client on the Windows 7 machine. During the installation it will ask you for the SmartDeploy hostname or IP. Enter that and the machine will show up in Computer Management in the SmartDeploy console. You will then create a deployment package, which then can contain your answer file that migrates user data. You can find more information on page 57 in our user guide. Thanks, Devon SmartDeploy Support
  7. Hi Chris, Aaron is correct. You will want to do this via the answer file. You do not have to migrate it with WDS, but you can always add a migration answer file to your WDS boot media if needed. In order to migrate from a Windows 7 machine to Windows 10, you will want to create a new virtual reference machine with the latest version of Windows 10 media (1903). You will want to create an answer file via the Answer File Wizard. To get to the Answer File Wizard, open the SmartDeploy console, Activities - > Reimage Devices - > Create Answer File. When creating the answer file you will have the option to migrate user data. You can find more information on page 107 in our user guide. Thanks, Devon SmartDeploy Support
  8. We will need to look at the full log files to see what is going on. Also, did you run any 3rd party applications to customize the start menu or uninstall or remove any of the built in appx packages? Please send us log files from the instructions above. Thanks, Devon SmartDeploy Support
  9. Hi phildown, Yep, SystemFamily and SystemSKUNumber are newer properties within Win32_ComputerSystem, only supported in Windows 10 and Windows Server 2016 or later. This means the current version of the script will fail in an older OS, but it will run just fine in our WindowsPE environment. So the easiest way to get a wmi.txt for a system that is currently running an older OS would be to boot to SmartDeploy media (best option would be a boot media USB stick with no answer file). When the SmartDeploy splash screen appears, click the Collect Logs option. Select a location to save the zip file. A log zip file will be generated in that location, and you can find the wmi.txt file in [zip root]\X\Windows\Temp, then submit a Platform Pack request via the Support Form (here). If you have any issues with this process, go ahead and submit a support ticket and we'll be happy to assist further. Glenn SmartDeploy Support
  10. Hi wajtech, We'll need a few more details on this - I'll open up a support ticket and you'll hear from us shortly. Glenn SmartDeploy Support
  11. Hello andrew.holt With these PC's in computer management from the console, you can simply delete them from there and the clients (these machines) will receive the message to uninstall themselves.
  12. Hi Kamsobe, We'll reach out via email to assist further. Glenn SmartDeploy Support
  13. Hi Allen, We have a script that can assist with this - you won't be able to push it out with the new console, obviously, but if you have some other means of pushing it out to each endpoint, it would have the effect of pointing that endpoint toward whatever hostname or IP address you specify. I've opened a support ticket for you - please expect an email shortly. Glenn SmartDeploy Support
  14. Hi Kamsobe, If you reimage a computer with SmartDeploy, that machine is counted against your license count. With Per Machine licenses, you can reimage the same computer as many times as you wish without ever consuming more than 1 license per machine. A SmartDeploy license remains attached to that computer until you decommission it, which can be done via the SmartDeploy customer portal. This should only be done for computers that are leaving your environment permanently and will never again be reimaged with SmartDeploy. If you have any further licensing questions, please feel free to reach out to licensing@smartdeploy.com. Glenn SmartDeploy Support
  15. Hi Benjamin, They're one and the same - a search for Latitude 3189 only yields one result from Dell: https://www.dell.com/support/home/us/en/04/product-support/product/latitude-11-3189-2-in-1-laptop/overview When we're naming a pack, we tend to respect whatever model identifier is listed in the system firmware, which in this case is simply Latitude 3189. Dell is generally pretty good about making their online listings match what's in the system firmware, but there are exceptions, and this is one of them. Go ahead and download the pack and let us know if you have any issues - support@smartdeploy.com. Glenn SmartDeploy Support
×
×
  • Create New...