All Activity

This stream auto-updates   

  1. Today
  2. Can you run diskmgmt.msc in the VM this image was captured from and send us what it looks like? Thanks!
  3. Yesterday
  4. sent info in pm
  5. Need the SmartDeploy.sdf, not SmartDeploy.log. Also, the image metadata would be helpful. Open the "SmartDeploy Enterprise Command Prompt" as admin, and run the following command against the image in question and send us the output. smartwim /info your.wim
  6. Yeah that was like the first thing i tried. Console.log SmartDeploy.log
  7. You could try right-clicking on that image and select refresh. If that doesn't work could you send the following to support @ smartdeploy.com and we'll take a look. c:\smartdeploy\logs\console.log c:\windows\system32\SmartDeploy.sdf Thanks, SmartDeploy Support
  8. I am having a bug where one particular image in my library keeps showing a hashed name instead of the simple image name. Imaging still works fine, just some weird bug and was wondering if anyone else had this or new a way to resolve it.
  9. Sorry for the delayed responses! I'm going to try this again today and post an update with logs
  10. Last week
  11. Hi all, This just came up on an unrelated support thread, and I just wanted to let everyone know that as of several months ago, we've added several bugfixes and performance improvements to SmartDeploy to address this issue, so if you're experiencing it, go ahead and update to the latest version of SmartDeploy, recreate your media, and retry deployment, and let us know if the issue persists - support (at) smartdeploy.com. Regards, Glenn SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL
  12. Hi there, Domain joining failures can occur for a variety of reasons relating to network connectivity, syntax, or user permissions. On a target device that has experienced this issue, boot to SmartDeploy media and click the Collect logs button. Save the resulting zip file to an external location, and send it to support (at) smartdeploy.com. Once we have your logs in hand, we can advise further. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL
  13. Seems no matter what I do SmartDeploy answer file will not join my machines to the network using Client deployment abilities. Have to manually go over to the machines and join them. Typed in everything right, domain\AdminUser and password. Nothing Anyone else finding this to be an issue too ?
  14. No joy sorry: I took the base VM, updated it, logged in using a different admin account, updated all the Store apps, re-captured and re-deployed - same issue, and same count for "Get-AppxPackage | measure" (47). Any other suggestions?
  15. I got it working! So I forgot to check the box for WDS when I created my image. while it worked fine for a USB drive and Remote imaging - WDS ignored it because I didn't check that box
  16. What error message are you receiving? Is this error happening when attempting to import your install image into the WDS role? If so, ensure when you captured your virtual reference machine you selected For Use With WDS. That will strip off any additional volumes such as the system reserve so you can import it into your WDS server. WDS only allows one volume images. Thanks, SmartDeploy Support
  17. I have done all of those steps and my current .wim has been working perfectly fine creating images via USB and a SDClient remote install. WDS just refuses to use any .wim made by SD
  18. Earlier
  19. Hi there, For reference, here is our white paper on how to integrate SmartDeploy with WDS - you'll want to make sure that you're adding the WIM that you captured to the Install Images node in WDS. https://www.smartdeploy.com/wp-content/uploads/SmartDeploy_WDS.pdf If you're receiving this error while adding your image, this most likely indicates that your image file is invalid or corrupt. Please reach out to support (at) smartdeploy.com and we can advise further. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL
  20. Appears that after all this work of making a .wim that's work perfectly fine for deploying the OS with the drivers from SD - WDS doesn't understand SD's .wim files at all. When I go into WDS and use the Add Image Wizard and point to the .wim I've been using with SD all this time it says "The file does not contain a valid install image." /sign . . . .
  21. Hi there, There is a script to automate this process - you can review Network Deployment starting on P. 39 in the User's Guide. The section on deploying with Group Policy (which includes the script that you can download and modify to specify the host name) is on P. 43. If you have any questions or issues, please feel free to reach out to support (at) smartdeploy.com. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL
  22. So you can deploy the SD Client out to any machine easily using PDQ but there doesn't appear to be a way to tell each PC the Host name. Even with GPO you still need ot visit each machine manually to update that xml file. Anyone find a better way of doing this? Can't fly to London and update 300 machines manually - looks like I'll have to remote to every C: drive and updated the xml file at this point...
  23. Mark, Currently there is no plans on supporting capturing UEFI based VMs. You can capture a BIOS based VM, and then deploy to a BIOS or UEFI enabled machine. Thanks, SmartDeploy Support
  24. Hello, We have seen this if the virtual machine was updating the Windows Store applications during the capture process. Try starting your virtual reference machine, running Windows Updates, then open the Windows Store and update all the applications there as well. You may have to restart a couple of times and keep updating until all updates are complete. Then capture/deploy and let us know your results. Thanks, SmartDeploy Support
  25. Hi, I have been deploying Windows 10 builds 1607 & 1703 to staff laptops successfully for a while now. Last week a staff member asked how he could get the calculator app to run. After checking and confirming that the problem is real I'm scratching my head as to why I'm see this. Symptom: try and run calc.exe on a SD-deployed PC and you get the error message "You'll need a new app to open this calculator". On the original 1703 image, "Get-AppxPackage | measure" returns a count of 84; the same on the deployed PC returns a count of47. "Add-AppxPackage -register" throws an error of "Add-AppxPackage : Deployment failed with HRESULT: 0x80080205, The Appx package's block map is invalid." Source VM runs in VMWare Workstation 12.5.5. SDE version is 2.0.2050. Hardware is Dell Latitude or Dell Precision with latest platform pack. Any advice appreciated, Thanks,
  26. We have not received any reports of this effecting deployment and the above way would be the supported way to customize your Windows 10 desktop when copying the default profile. Thanks, SmartDeploy Support
  27. HI In 1703 things may have changed looks like settings my be in the reg...trying to find out more https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2150422 https://social.technet.microsoft.com/Forums/en-US/2cbfcabe-7a02-4874-ad13-84a1ead67a60/layoutmodificationxml-not-applying-in-v1703?forum=win10itprosetup There is indeed a cached version of the Start menu in the registry as of v1703. Removing the cache and the TileDataLayer folder will allow Windows to apply your Start menu modification if you're using manual user customizations in audit mode. The key is HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\CloudStore. For the default user in a clean WIM file from Microsoft, there are no subkeys here, so feel free to delete the "Store" key you see under CloudStore. For me, since my image was already created, I had to mount the WIM file, load ntuser.dat from the Administrator user, remove this key, unload the hive (never forget to unload hives!), then commit the changes to the WIM. During deployment, the CopyProfile flag will copy the Administrator user to the Default user and all will be well! 😁
  28. HI There are changed in 1703 not sure how this now effects things. Settings now in reg.. https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2150422 https://social.technet.microsoft.com/Forums/en-US/2cbfcabe-7a02-4874-ad13-84a1ead67a60/layoutmodificationxml-not-applying-in-v1703?forum=win10itprosetup There is indeed a cached version of the Start menu in the registry as of v1703. Removing the cache and the TileDataLayer folder will allow Windows to apply your Start menu modification if you're using manual user customizations in audit mode. The key is HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\CloudStore. For the default user in a clean WIM file from Microsoft, there are no subkeys here, so feel free to delete the "Store" key you see under CloudStore. For me, since my image was already created, I had to mount the WIM file, load ntuser.dat from the Administrator user, remove this key, unload the hive (never forget to unload hives!), then commit the changes to the WIM. During deployment, the CopyProfile flag will copy the Administrator user to the Default user and all will be well! 😁
  29. https://www.smartdeploy.com/download/smartdeploy/ Thanks, SmartDeploy Support
  1. Load more activity