Allen Marsh

  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Allen Marsh

  • Rank

Profile Information

  • Gender
  1. Can't seem to find anything about a Latitude 7525. But, based on what you are describing sounds like it could be the network driver. What we would really need to do is create a platform pack for this model. And if you were to end up purchasing them, if you could ship us one with the dock then we could ensure it worked perfectly. Aside from that, you could try creating boot media from an existing pack that has the Dell Thunderbolt Dock Realtek USB Ethernet driver in it. The Precision 5510 pack would work for this. Download that pack, run through Media Wizard, and select just this 5510 pack to create boot media. That will get the correct Realtek driver in there. If that doesn't fix it, then it could be more complicated like needing Thunderbolt or other drivers. Email us back at support @ Thanks!
  2. Believe we have a fix for this error in the next release. If you want to email us directly at, we can send you some instructions to run that new piece of code before the next release comes out. Thanks!
  3. If you have any snapshots on the VM, then you might not be capturing the content you are seeing when the VM is running. If there are snapshots, then you can try to capture that VM by booting the VM to the SmartDeploy.iso and capturing it that way. This will capture the content of snapshots, where as capturing with it powered off will not.
  4. We recommend not installing the VMware Tools in your reference machine, because the uninstall process does not clean up everything. Drivers and services are left behind even after uninstall, and you'll then be deploying those things to all your endpoints. To verify if the VMware Tools are installed, we check the following registry locations. HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\{FE2F6A2C-196E-4210-9C04-2B1BC21F07EF} HKLM\SYSTEM\ControlSet001\Services\VMTools HKLM\SYSTEM\ControlSet001\Services\VMwareTools So, check your VM and if any of those exist, delete them. Capture Wizard will then work. Please feel free to email us directly at if you have any further issues. Thanks!
  5. In order to successfully deploy the Microsoft Surface Pro 3 with SmartDeploy, you'll need to use SmartDeploy version 1.1.5010 or later. Additionally, this UEFI Class 3 device automatically adds a BCD firmware entry for any present bootable USB media on each boot. This means that even with the UEFI "Alternate System Boot Order" set to "SSD Only", the machine will still boot to a bootable USB device on each boot. Therefore when deploying the machine via offline USB media, the machine would reboot back to SmartDeploy once the image had been applied and the machine rebooted for the first time. Not only is this not desired, but it causes an issue with the deployment if you then remove the USB stick, reboot the system, and let the deployment continue. To this end SmartDeploy 1.1.5010 adds an additional Deploy Wizard advanced feature to shutdown the machine when the Deploy Wizard ends. By selecting this, it will provide a chance to remove any bootable media, and then power on the machine. The deployment will then continue and complete successfully. If you use PXE boot either from the USB dongle adapter or the dock, and there is no USB boot media present, then you can let the machine reboot as normal. If you have any issues, please contact us at SmartDeploy Support.
  6. The current version of SmartDeploy, 1.1.3010 doesn't support UEFI. You can change the machines into Legacy mode in the BIOS to load them. The next version of SmartDeploy, 1.1.4000, will support UEFI and should be out very soon. When you purchase a machine with Windows preloaded on it, that is an OEM license. You can’t use OEM licenses for reimaging, so what you are supposed to do is purchase a single VL license. You then just need Microsoft to grant you activations on that VL key equal to the total number of OEM machines purchased. Which is outlined in the Microsoft reimaging guide. See FAQ #7. It's also discussed in this Microsoft blog. We have a couple resellers that understand this arrangement, that we can put you in contact with. Or, you can ask your preferred reseller about it. Just email us at if you need more information.
  7. You should be able to use the Deploy Wizard to generate an answer file that has multiple tasks. If you do so, it would look like... <tasks> <task> <phase>FIRSTLOGON</phase> <command>C:\Systemupdate506-01-15-2015.exe</command> </task> <task> <phase>FIRSTLOGON</phase> <command>msiexec.exe /i C:\logmein.msi</command> </task> </tasks> Need to preface the msi with the executible. Both of these would also need silent command line switches if you didn't want them to run interactively. In most Lenovo platform packs we do now try to include the ThinkVantage System Update utility. So, we can add that to a Lenovo pack if it is missing.
  8. Please submit all platform pack requests here. Thanks, SmartDeploy Support
  9. If you are using VMware virtualization products to build reference computers with SmartDeploy, and you want to create a Windows 8.1 or Windows Server 2012 R2 image, you'll need to follow these instructions. Through testing, we have noticed inconsistent shut down results from within VMware products. When using the Capture Wizard to subsequently capture an image of that machine, the resultant image file does not contain full metadata. If you then attempt to deploy this image, it will result in the following error. "The Platform Pack has support for this computer manufacturer and model, however it does not contain support for this operating system." As such, prior to capturing an image of a SmartDeploy reference computer that was created using VMware products, you need to do one of two things: Preferred method If you are using the Capture Wizard while the machine is powered off you must first perform a full shutdown of the VM. From a command prompt, run “shutdown.exe /s /t 0”. Or, you can use the Settings charm, Power, and then hold down the Shift key while clicking Shut down. Most customers use VMware Player or Workstation in this fashion. [*]Alternate method If you are using the Capture Wizard while the machine is powered on, you must first license and activate the virtual machine. Many customers use VMware ESX in this fashion.
  10. Try the following: Open an administrative command prompt Diskpart List Disk (determine which disk is your USB stick, probably disk 1 if you only have 1 physical hard drive) Select Disk 1 (use the correct disk number here) Detail Disk (ensure you have your USB drive selected) Clean (this destroys all data) Create partition primary Active Format quick fs=ntfs Assign letter e: (any available driver letter is fine) Exit Re-run the Media Wizard to create the bootable USB drive.
  11. We've seen issues with these new ThinkCentre's if the USB drivers are in PE. So, can you build boot media from just the single M73 pack from our website? Can't be combined with any other pack. This pack does not have USB drivers in the Windows PE node, and that has fixed the same issue on the M93. Thanks, SmartDeploy Support
  12. Seems like you can force detection with "wuauclt.exe /detectnow" but you'll probably need to have group policy configured to automatically install the updates you want in order for it to actually start installing any updates on its own.
  13. We've seen this before with certain VPN software installed in the virtual reference machine. But, using HP OEM install media could also be causing the problem.
  14. This is from UAC. Right-click on the Media Wizard and select Run as Administrator.
  15. Microsoft is doing some pretty cool things within Windows 8 to allow you to Refresh and reset your PC to a known good starting point. This should be a much cleaner WinRE implementation than the PC Manufacture's implementations with Windows 7. It also appears to have given us USMT Hard-Link Migration for the masses. In this related article, talking about improvements in Windows Setup, and more specifically about the new web based purchase/download/upgrade process... they mention the following: “After this optimized package is created we compress it using an improved compression algorithm specifically for Windows 8 setup, which provides an additional 28% savings. In this example (using the Windows 7 x86 ISO) the size of the download would be reduced from 2.32GB to 1.51GB.” Considering that the install.wim is nearly 90% of the ISO size, this seems incredible. There has to be some new .wim trickery, since modern compression algorithms run against .wim only produce low single digit percentages. Interesting! -Allen