All Activity

This stream auto-updates   

  1. Yesterday
  2. With unicast, it's essentially the same as 10 different user's trying to unzip a 10GB compressed file across the network. If that effects your network too much, then might just want to do multicast, or stagger the times at which the unicast deployments are happening. Below ~25 clients, mulitcast is supposed to be slower overall because Microsoft's WDS mulitcast first copies the image to the local disk, and it's then applied from there. But, it will only impact the network as a single file copy. Thanks, SmartDeploy Support
  3. Ensure you created your boot media with the HPElitePro600-800-G3-Windows7.ppk file selected. If you did, but also had many other packs selected, then try creating boot media with only the HPElitePro600-800-G3-Windows7.ppk file selected. If you still have issues, email your c:\smartdeploy\logs\media.log from where you ran the Media Wizard to support @ Thanks, SmartDeploy Support
  4. We recently got some HP EliteDesk 800 G3 SFFs. They have had nothing done to them as far as software is concerned, they are just as they came out of the box. We also have the most current platform pack available for these machines (they are also windows 7). When loading smartdeploy, in the right-hand side of the screen where machine information is displayed, next to "IP Address:" the word "Initializing..." appears for a short while and then goes blank, as if there is no IP address. Upon attempting to map any network drives, error 1231 comes up. We are able to ping the WDS and other IPs with success.
  5. While imaging less than 10 computers at a time (sometimes less than 5 computers), we are getting reports from our network infrastructure team that network bandwidth is maxed out and saturated to the point that all users on campus cannot utilize any network assets. We have a 1GB backbone/switches throughout campus and all imaging communication resides on premise inside our DMZ. We usually image via unicast to our WDS server and expect to be able to image up to ~25 without speed issues before going with multicast transmissions, but are still having network speed issues with less than 10 at one time. We have been able to image successfully in the past without speed issues, but we are trying to pinpoint what has changed since then causing our bottle-neck. Our image size has actually decreased in size to 10.4GB. Any input is appreciated.
  6. I'm pretty sure I didn't use the VMware easy install, but there was a significant update to windows 10 and maybe that caused it. In which case I'm sure others may have the same issue.
  7. The only way I can think it would end up like that is you used the VMware "Easy Install", which automates Windows setup and forces Windows to use a single partition. Then perhaps this VM was upgraded from one version of Windows 10 to another, like 1511 to 1607, and that process created the 450MB recovery partition at the end of the drive. Can't really fix the partitions now. Would need to create a new VM, not use the Easy Install, I.e. just select "I will install the OS later". Once the VM is created attach the latest Windows 10 .iso and install Windows. Or, you can just use the SmartDeploy Build Wizard to create your VM. Thanks, SmartDeploy Support
  8. It was just created in VMware workstation 12, just by using a iso to install windows just as you would baremetal nothing custom done. Should I try to fix the partitions?
  9. The console is expecting the partitions to be in the default Windows 10 order of a 500MB system and the rest of the drive as the boot partition. So, we've filed a bug to have the console find the correct index of the .wim that contains the Windows node and use the name of that Index. But, curious how your VM was created to end up with that partition structure? Thanks, SmartDeploy Support
  10. here you go
  11. Can you run diskmgmt.msc in the VM this image was captured from and send us what it looks like? Thanks!
  12. Last week
  13. sent info in pm
  14. 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
  15. Yeah that was like the first thing i tried. Console.log SmartDeploy.log
  16. You could try right-clicking on that image and select refresh. If that doesn't work could you send the following to support @ and we'll take a look. c:\smartdeploy\logs\console.log c:\windows\system32\SmartDeploy.sdf Thanks, SmartDeploy Support
  17. 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.
  18. Sorry for the delayed responses! I'm going to try this again today and post an update with logs
  19. 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) Regards, Glenn SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL
  20. 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) 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
  21. 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 ?
  22. 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?
  23. Earlier
  24. 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
  25. 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
  26. 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
  27. 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. 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) and we can advise further. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL
  28. 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 . . . .
  1. Load more activity