Jump to content
DeployCentral

All Activity

This stream auto-updates     

  1. Today
  2. Bumping this thread up as it would be a killer feature. Any hopes of revisiting this?
  3. Yesterday
  4. Keep on getting this error when capturing image

    Hello, Please send the following information to us at support (at) smartdeploy.com: -Whether there is any antivirus software running on the computer where SmartDeploy is installed -Whether there is any a/v installed on the VM you're capturing -Whether you have successfully captured a VM on this computer previously Also, please send your Capture Wizard log: C:\SmartDeploy\Logs\Capture.log Regards, Glenn SmartDeploy Support 888.7DEPLOY toll-free _____________________________ SmartDeploy® Learn about our award winning Windows deployment solutions www.smartdeploy.com www.deploycentral.com Twitter: @SmartDeploy Facebook: SmartDeploy Spiceworks: Spiceworks
  5. Last week
  6. Earlier
  7. SmartDeploy.iso

    I see it now, thank for pointing that out... I have always used the wds.iso that was provided initially 2.5 yrs ago now
  8. SmartDeploy has the ability to do console initiated deployments. If you install the SmartDeploy Client on a computer, and it can reach the SmartDeploy console system, you could "push" a deployment form the console to the remote computer. The caveat here, is remote/VPN network connections may not office the best performance and could lead to problems in the imaging process.
  9. SmartDeploy.iso

    The files in "C:\Program Files (x86)\SmartDeploy\SmartDeploy Enterprise" would be SmartDeploy_x64.iso and SmartDeploy_x86.iso. If those files are missing, then you'll need to re-install SmartDeploy. There's no official 'wds.iso' so I'm assuming that's just DVD boot media that was created by someone, and named as such. Whenever you update SmartDeploy, you have to re-create your boot media. I suspect your wds.iso if from an older version. Also; the absence of any wims/images following the 'get-mounted' is good, as it means there isn't a mounted image stuck. That would be related to a problem creating new boot media. But if the SmartDeploy_x64.iso and SmartDeploy_x86.iso files are missing; you need to re-install SmartDeploy.
  10. SmartDeploy.iso

    Good Morning Everyone, I have a Win10 v1709 Image built, and having a hell of a time with trying to capture it... when trying to use the wds.iso I have had for many releases up til now it has worked fine to perform the Warm Image Capture as out outlined here on Page 76 in the user guide I noticed on my server that runs the Smart Deploy it doesnt list the SmartDeploy.iso as mentioned by Support to use in the \Program Files(x86)\Smart Deploy\*.* directory anywhere.... So am wondering if there is a newer updated version I can obtain that would help, since currently I get a error that says "Image not created with Smart Deploy Capture Wizard" when trying to use for the Answer File and then cant continue and bombs out the process... And the Capture Wizard is not working either... and it isnt mounted on the server in the background processes at all, as I have run the following commands and it comes up clean: To troubleshoot the issue regarding the error and unmounting; Please send me the output from the following commands run from the server elevated command console prompt: dism /get-mountedwiminfo dism /get-mountedimageinfo If anything is listed; run dism /cleanup-mountpoints I am using the latest build of 2.0.2097 Enterprise
  11. W10 1709 Deploys as 1607?

    Hi Lee, We really need to see a log set in order to answer this question. Please go ahead and submit one via the Support Form link above. Regards, Glenn SmartDeploy Support 888.7DEPLOY toll-free _____________________________ SmartDeploy® Learn about our award winning Windows deployment solutions www.smartdeploy.com www.deploycentral.com Twitter: @SmartDeploy Facebook: SmartDeploy Spiceworks: Spiceworks
  12. W10 1709 Deploys as 1607?

    I meant from within the image. Importing the machine into the reference machine library seems to get stuck at 3%...
  13. W10 1709 Deploys as 1607?

    If the Windows version in the reference machine library is showing as 1607, then that is how the VM appears to SmartDeploy externally. You'll want to go ahead and power on the VM and run that winver command to confirm which version is installed. Regards, Glenn SmartDeploy Support 888.7DEPLOY toll-free _____________________________ SmartDeploy® Learn about our award winning Windows deployment solutions www.smartdeploy.com www.deploycentral.com Twitter: @SmartDeploy Facebook: SmartDeploy Spiceworks: Spiceworks
  14. W10 1709 Deploys as 1607?

    If you mean within the VM, you can confirm this by running the command winver. Determining this from the captured image (.wim) is also possible, but we'll need to have a look at the log set referenced above. Regards, Glenn SmartDeploy Support 888.7DEPLOY toll-free _____________________________ SmartDeploy® Learn about our award winning Windows deployment solutions www.smartdeploy.com www.deploycentral.com Twitter: @SmartDeploy Facebook: SmartDeploy Spiceworks: Spiceworks
  15. W10 1709 Deploys as 1607?

    Looking under my reference machine library tab it shows the OS as 1607. I am re-importing that VM now. Is that a step I missed?
  16. W10 1709 Deploys as 1607?

    That's what I thought too. I even deleted the old images from the WDS server but I'll double check it. Do you know offhand where I could tell within the image what the Windows version is by chance?
  17. W10 1709 Deploys as 1607?

    Hi Lee, There's really no plausible mechanism for this other than capturing the VM in the wrong state/snapshot (which you've ruled out above), or accidentally deploying an old image. Have you updated your answer file to point to the new image, recreated your WDS boot media, and replaced it on your WDS server? If you've omitted any of these steps, it's possible you're still deploying the old image. If you're not sure which image you deployed, you can retrieve a log set from the deployed device and we can take a look. 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 email to us at support (at) smartdeploy.com. Note that some organizations restrict sending zip files over email, so you may want to check with your IT department to make sure the email made it out with the attachment. Alternately, you can fill out our Support form, which includes a file upload option. Regards, Glenn SmartDeploy Support 888.7DEPLOY toll-free _____________________________ SmartDeploy® Learn about our award winning Windows deployment solutions www.smartdeploy.com www.deploycentral.com Twitter: @SmartDeploy Facebook: SmartDeploy Spiceworks: Spiceworks
  18. I never did say thank you, so thank you!
  19. Am I just missing something here? SDE v 2.0.2097 VirtualBox based image of Windows 10 Enterprise updated to 1709 no snapshots Deploying Image using WDS When I deploy the image it all goes OK but when I check the version of Windows it is at 1607? I've tried re-imaging about 5 times, have captured the image with the VM powered up and down to no avail.
  20. OK, thanks for the info Jeff. I have one further question, so how would it differ via VPN? I would not be able to access the system until updated into our network... Maybe I am missing something here that's obvious
  21. You can send them a USB drive with SmartDeploy boot media on it, but it's going to either follow the answer file as an unattended deployment, or require action from a user at the remote site. You could in theory perform deployments remotey, while using USB if you have VPN and KVM access to the systems.
  22. I am looking to see if it's possible to have my satellite office enter a USB we supply with SmartDeploy and have my office control the install and updates. Is this possible? I did not find anything via the "User Manual"... Of course we have deployed via USB but it's been hands on, and via the network. We need to do this with a new PC install that we can control the update remotely.
  23. Negative delta

    I would expect your assumption to be correct. But, as with most things, I'd recommend thorough testing.
  24. Dell Latitude 3580 - CTRL ALT DEL Screen Message

    This is a new feature in Windows 10 1709. Would need to be disabled via Group Policy, if that's possible.
  25. Hello, As part of my evaluation for SmartWim im trying to understand this case: Here are some points for clarification: We are using real PC in terms of creating WIM file for the partition C:\ (System OS – Windows 10) We want to discuss the next scenario Day 1 – we capture WIM file of partition C: - base WIM Day…10 – we performed some changes on this partition and delete a list of files from different paths. In other terms “Day 10” partition has less files comparing to base WIM. We create .dwm file, that SHOULD reflect the diff between base Day1 and Day10 partition file structure. We append .dwm file to base WIM (meaning now we have 2 indexes in the single base WIM Now we are going reimage partition C:\ on the destination PC : apply Index 1 (base WIM) apply Index 2 (.dwm) to the same partition What should we expect in this case on final C:\ partition? Real situation Day 1 Base WIM: Day 10 Folder TEST1 Folder TEST1 Files: Files: 1.txt 1.txt 2.txt deleted 3.txt 3.txt We assume that folder TEST1 on destination C:\ partition will contain all 3 files 1.txt 2.txt 3.txt Is our assumption correct? Please confirm. Of course we expect this TEST1 folder after partition reimaging will contain: 1.txt deleted 3.txt
  26. When I've re-imaged our Dell Latitude laptops, and we have group policy settings set to force CTRL ALT DEL to login, there is a different message: Press and hold the power button, then press the volume down button to unlock. (Or you can unlock by pressing Ctrl+Alt+Delete.) It's as if it thinks the laptop is a tablet. Not sure if this is a SmartDeploy Platform Pack issues, as a few forums are pointing this to HID Filter drivers and possible BIOS updates. Just thought iI'd put it out there in case others are having the same issue
  27. Win10: Calculator & other apps missing

    I've recreated my gold reference machine from scratch using the 1709 ISO, and all appears to working well now. I didn't update any apps or anything before capture.
  28. Win10: Calculator & other apps missing

    Yeah, we've just come across this too. Just came to light after deploying to only a few machines for end user testing. All Win 10 Pro images are 1709, and I've seen lots of TechNet threads going around about it and looking to try out a few solutions. Bit of a headache!
  1. Load more activity
×