Jump to content
DeployCentral

All Activity

This stream auto-updates     

  1. Yesterday
  2. Last week
  3. Aaron@Shared

    Recommendations for October 1809 Update

    Thank you for the quick reply and for your feedback.
  4. SmartDeploySupport

    Recommendations for October 1809 Update

    Hi Aaron, We appreciate you taking the time to evaluate SmartDeploy. We don't recommend upgrading to new versions of Windows 10 via in-place upgrades. i.e. Windows Updates. These new versions of Windows 10 are essentially new operating systems, so it's best practice to get the latest volume license media and then create a virtual machine and then capture/deploy that. You could let the PCs update after deployment and that shouldn't affect sysprep or anything on the deployment side, but just know your virtual reference machine will eventually need to be updated to the latest version anyway, and we recommend the above. Also, doing the above will provide you with the cleanest image. When in-place upgrades happens Windows 10 essentially backups the old operating system which can take a lot of space and will manually need to be deleted. Hope this answers your question. Thanks, SmartDeploy Support
  5. Senario: My company is looking to replace Ghost with SmartDeploy. I have been testing and imaged 4 computers with Windows 10 1803. Question: How would you recommend handling the new 1809 update that is coming out in October? 1. Update the VM and then the Image? 2. Let each PC get the update (if we allow it) on its own? Thoughts?
  6. Earlier
  7. I think I may have found out what was causing all the problems that I described above. After building a brand new VM on the new computer, I had the exact same problems with the new VM that I had with the other VM that I copied over from the old computer. After brainstorming with my supervisor we decided to copy the new VM to the old computer and try it there. No problems. Only difference, the version of SmartDeploy that is installed on both computers: New computer: 2.0.3010 Old computer: 2.0.3005 I hope this will help other who run into the same or similar issue.
  8. Keith Costello

    Download Packs & images

    Is there a solution to this? I'm having the exact same issue and it looks like the download packs never finalize as they all say .download at the end of them.
  9. Ok. I mean there must be some strange things in play here, and while you may be able to track them down eventually, I agree that a new VM is the shorter, less effort route to go.
  10. I tried the "warm capture" but I get the error "Unable to mount". You are right, it's probably more efficient to just re-do the VM on the new computer. Thank you for all of your help Jeff!
  11. If you're able to delete the lck file and boot the VM, then you should be able to do a warm capture. But deleting those files is normally something you don't want to do, as it may interfere with VMwares processes. You may consider just re-making the VMs in lieu of troubleshooting this for too long.
  12. Thank you for your suggestion Jeff, I will give this a try.
  13. Please try performing a "warm capture," by capturing an image with the virtual machine running, and saving the image to a network location. This process is detailed in appendix 1 of our user guide:https://www.smartdeploy.com/wp-content/uploads/SmartDeployUsersGuide_V2.pdf
  14. No snapshots. I just tested the VM on the original computer and captured an image, no problem on the original computer.
  15. Do you have snapshots on the virtual machines on the original VM host?
  16. I found a ".lck" file in the VMware folder of the VM. After deleting that, the VM runs without any problem. The only problem that is left now is SmartDeploy telling me "Device not ready" when I try to capture a new image of the VM. When I proceed I get this error: CaptureVirtualDisks.Mount returned: 21. The device is not ready. Any ideas what I can do to fix this error? Thank you!
  17. The new VM works fine, no problems. I deleted the old VMs, copied them over again to a new folder, then imported them into SmartDeploy. This time I did not try to open the VMs in VMware Player, I immediately tried to capture an image. This time I only received the message "Device not ready", but SmartDeploy was able to see the virtual disk volumes. Then I tried to open the VMs in WMware Player. Same issue as before, it says “Error while powering on: The operation was canceled by the user”. After I tried to power on the VM a few more times I got this error: The operation was cancelled by the user Cannot open the disk 'C:\SmartDeploy\Reference Machines\Windows 10 x64\Windows 10 x64.vmdk' or one of the snapshot disks it depends on. Module 'Disk' power on failed. Failed to start the virtual machine. Any suggestions or ideas? Thank you!
  18. Thank you Jeff, that's a good suggestion. I'm creating a new VM right now and will find out soon.
  19. I am also having this issue. Not sure why.
  20. Before you throw yourself on the rocks too much troubleshooting, spin up a new virtual machine and install windows, restart the VM and then shutdown and capture another image. This will help determine if it's the VMs you moved or if there's an issue with SmartDeploy your new setup.
  21. Yes, that's what I did. I followed this VMware KB article: https://kb.vmware.com/s/article/2030609 Thank you.
  22. Hi Tim, How did you copy the the VMS? Did you simply just copy the VM's folders and place them on the new computer?
  23. Hi everyone, I have SmartDeploy 2.0.3005 installed on a Windows 7 Pro 64-bit system. I have two reference images, two captured images and a few platform packs. I can edit my reference images with no problems in VMware player and then capture my changes with the SmartDeploy wizard to create a new image for deployment. I would like to move everything to a new computer. The new computer has Windows 10 Enterprise 64-bit installed. I installed SmartDeploy successfully. Then I copied the content from the old computer’s SmartDeploy folders (images, reference machines and platform packs) to the new computer. After I copied the data, I imported the content from each folder within SmartDeploy successfully. To that point, all worked well. But when I try to capture an image with the wizard, I get the error message “Unable to mount the virtual volume”. After trying it about 10 times, I get the error “Device not ready” but then the virtual disk volumes are listed. I also noticed after copying over the virtual reference machines, that VMware player gives me an error as well “Error while powering on: The operation was canceled by the user”. Strangely, when I keep trying to power it on (15 to 20 times), it will eventually power on. Did anyone run into the same or similar problems? Maybe the way how I moved everything over to the new computer was not the proper way, is there a “better” or “proper” way? Thank you for your help! Tim
  24. Bam

    Download Packs & images

    No change. My reference machine and answer file show up fine.
  25. Joseph Stickel

    Download Packs & images

    Hello Bam Please try adding a blank text document in each of the folders that are not showing info in the SD console, then close and reopen the console.
  26. My download packs appear to download and I see them in the correct file folder but they do not show up in the SmartDeploy Console, even during the download process. My image does not show in the SD Console either but it is in the correct file folder location. Any help is appreciated.
  27. JayM, Here is a great article that walks you through PS step by step. You can also add additional apps to the script fairly easily. https://winaero.com/blog/remove-all-apps-bundled-with-windows-10-but-keep-windows-store/
  28. perry

    Software Install Step

    What should not be installed on the virtual machine vs what should be installed via command line? Can I install Microsoft office to the virtual machine?
  1. Load more activity
×