Jump to content
DeployCentral

SmartDeploySupport

Administrators
  • Content count

    522
  • Joined

  • Last visited

Community Reputation

0 Neutral

About SmartDeploySupport

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male

Recent Profile Visitors

7,836 profile views
  1. SmartDeploySupport

    Sysprep fails on Lenovo T450s and T430u

    Please boot to SmartDeploy media on the affected device (ideally with USB boot media with no answer file, to avoid starting another deployment and wiping the previous logs), click the Collect logs option, save the resulting zip file to an external location, and send with your reply. Submit your ticket here.
  2. SmartDeploySupport

    PXE Boot Loop

    Interesting, thanks for finding that. What we saw before, at least on Microsoft Surface models, was that even if the firmware entries we're correct before the reboot, it would add an entry above the OS, like for a USB drive, and then automatically try to boot to that. With newer firmware updates on these machines though, they no longer do this. Dell seems to be the last one left that has this issue. I'm surprised that the /p switch would be able to fix it, but that's great if it can. We'll test and implement if it works out.
  3. SmartDeploySupport

    PXE Boot Loop

    Try updating your BIOS and see if this fixes it. We are going to look into this more and hopefully have a built in work around for the Dell issue. We appreciate your patience. Thanks, SmartDeploy Support
  4. If the virtual reference machine has any anti-virus installed on it, uninstall it and attempt to recapture. If that's not the case, then submit a support ticket here. Thanks, SmartDeploy Support
  5. SmartDeploySupport

    PXE Boot Loop

    Hello, It's certain machines, in UEFI, they automatically add a firmware boot entry for the USB and boot to it on the next reboot. It's unfortunate but something we cannot control at this time. SmartDeploy clears all the UEFI firmware boot entries, but it doesn't fix it, as it'll just update it on the next reboot. You could try updating the BIOS for those specific machines and see if that works. Lenovo has stopped doing this for the most part, but Dell certainly does. So, again, try updating the BIOS, or in the Deploy/Answer File Wizards you could select Advanced -> When Deploy Wizard Ends: Shutdown.That way you don't have to be at the machine at the time of the restart to pull the USB, but instead come by when you can and just start the machine back up and pull the USB then.
  6. SmartDeploySupport

    Copying or cloning imaging USB drives?

    Hi jmowrey, Our recommended approach here would be to install SmartDeploy on a different workstation, then run Media Wizard to create new USB media. The specific method for this will vary a bit depending on the media type you created previously. If you created NTFS-formatted USB offline deployment media previously, then the image and Platform Packs would be sitting in the z folder on your USB media - you can simply copy these items to the corresponding folders in the C:\SmartDeploy directory - Images and Platform Packs respectively, and then just re-run Media Wizard. If you created FAT32-formatted USB offline deployment media (which is the default media type, in order to support UEFI boot on target devices), then - if your image is >4GB in size - it will still be in the z folder, but it will be split into two or more split-wim (.swm) files. If this is the case, then you won't be able to create offline deployment media directly (there's no method available to "merge" split-wim files back into a single .wim file, and Media Wizard will not allow you to select a .swm file). But you can run Media Wizard to create USB boot media, then simply copy over the entire z folder from your old USB stick to your new one. You can actually use this method for NTFS as well - you'll just want to make sure you're creating the same media type that you created previously, as FAT32 has an absolute per-file limit of 4GB, so you will only be able to copy over an existing >4GB .wim file if your previous wim was NTFS, and the new one you're creating is also NTFS. I should also note, as a general practice, SmartDeploy's Media Wizard does not format your USB stick unless you tell it to switch file systems (from NTFS -> FAT32 or vice versa), and it will warn you before doing so. So if you simply wish to update your media to the latest version of SmartDeploy, you can run Media Wizard to create boot media, and then point to the drive letter for your existing SmartDeploy media. Even if it was offline deployment media to begin with, the z folder and its contents will remain untouched. If you have any questions feel free to email us at support@smartdeploy.com, and be sure to reference this DeployCentral thread. Glenn SmartDeploy Support
  7. SmartDeploySupport

    Media Wizard Unmounting Image Error

    Hi Al, Unfortunately, this is not an issue that has a single solution for every user, as the issues that cause it tend to be environment-specific (user permissions or security software interfering with the operations of Media Wizard are the most common issues). If you go ahead and send us your Media Wizard log, we can see what's going on. You can submit the log via the Support form here: https://support.smartdeploy.com/new Please be sure to reference this DeployCentral thread when you submit the form. If you have any issues submitting the form, feel free to email us at support@smartdeploy.com. Glenn SmartDeploy Support
  8. SmartDeploySupport

    Error message when deploy Windows 10 1803

    Hi John, I see you've submitted a support ticket as well - we'll reply to that thread. Glenn SmartDeploy Support
  9. Hello, Once you perform the registration of the dlls, you’ll need to re-initiate the download process, as the stuck download will not restart on its own. Launch the SmartDeploy Console, click Platform Packs, click + | Download a Platform Pack. Search for the pack, select it, and click Download. The download should proceed normally.
  10. SmartDeploySupport

    Image difference

    Hi Johnson, By default, SmartDeploy will capture all volume of the VM that you select, unless you indicate that the image is for WDS. A requirement of WDS is that it can only apply an image with a single partition. Assuming your reference VM just contains a single OS volume and and a system reserve partition, there is little practical difference once the image is applied to a target device. Glenn SmartDeploy Support
  11. SmartDeploySupport

    Windows 10 - 1803

    Our current beta will fix this issue. Download and install, then recreate your boot media via the Media Wizard and redeploy and let us know your results. https://www.smartdeploy.com/register/beta/
  12. SmartDeploySupport

    Adding additional Images to Media

    Currently there is no way of preventing the platform packs to be added to the boot media via the Media Wizard unless you don't select them during the process.
  13. SmartDeploySupport

    Windows 10 1709 error message on SmartDeploy

    John, How was this image created? From a fresh clean VM? Did you perform an inplace upgrade? i.e. Running Windows Updates from 1709-1803? Sometimes the in-place upgrades will create new partitions if the existing ones don’t line up with what the new version would have. If you were to create a new BIOS based VM, install the latest version of Windows 10 from VL media, once at the desktop shut it down and capture it, should work just fine.
  14. SmartDeploySupport

    Windows 10 1709 error message on SmartDeploy

    Hi John, According to your logs you're using a very old version of the platform pack. Extracting from Platform Pack: \\HKHQITS019\C$\SmartDeploy\Platform Packs\LenovoThinkPadT440-T440s-Windows10.ppk, Lenovo\ThinkPad T440-T440s\Windows 10 (x64)\* LastUpdated: 2/24/2016 12:00:00 AM Download the latest version of the platform pack and redeploy and let us know your results.
  15. SmartDeploySupport

    Smartdeploy network deployment

    Please be sure these ports are open on your network firewall. TCP 80 - HTTP TCP 443 - HTTPS TCP 8732 - ConsoleServiceWCF TCP 8733 - ClientServiceWCFF TCP 8734 - ConsoleServiceSLWCF TCP 8735 – ConsoleServiceMCWCF You can attach your log files here. Also, please send us your C:\SmartDeploy\Logs\Console.log from the SmartDeploy host and we can check that out as well. Thanks, SmartDeploy Support
×