Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by tim.cummings@juhsd.net

  1. It turned out to be a windows update that broke WDS, after a lot of hair pulling and some research, we are back up and working again, it was just a coin incidence that it happens right when we tried a new type of computer we never imaged before. https://social.technet.microsoft.com/Forums/en-US/46e30b31-590e-47b4-b123-faf3776cfe74/windows-update-kb4489882-broke-wds-and-mdt?forum=mdt
  2. We just bought about 400ish new Lenovo ThinkCentre m720q computers, we cannot seem to boot into smartdeploy using PXE, it seems to freeze up at 5%, does anyone have expericne with lenovo thinkcentre's having this issues, also if someone has a matrix for bios settings.
  3. Still says local, not on same domain, not same internet, not on vpn
  4. It was in the console as a local connection type. I was not on prem, device is at a different location.
  5. I was able to get it to work with boot media, but I could not deploy with the agent, i could not get the computer to show up as a "cloud" device.
  6. I am a little fuzzy on how your supposed to be able to deploy over the cloud, say at a employees computer at home? How is that achieved without physically touching the machine?
  7. Hello, I just recently deployed 60 Dell Latitude 3050's with my technicians. We had some issues when leaving the computers set in UEFI mode. The PXE starts but hangs and moves really really slow loading the boot file. I left several booting went to lunch and came back and still didn't boot into smartdeploy boot file. After some word eating on my part, as my technicians recommend legacy mode instead, i insisted it wasn't necessary. But low and behold that worked flawlessly, after disabling secure boot and disabling UEFI boot options, legacy PXE worked fine. I did some quick research and I think it could be a driver issue with the PXE in winpe mode, some other people reporting having issues with WDS, but didn't really find any solution. So just fyi, as we have discovered, from model to model, UEFI seems to not work, and on some legacy doesn't work. I don't believe this anything to do with smartdeploy, but more WDS itself and manufacture drivers, not sure if anyone else has these issues as well. Perhaps experimenting with changing the driver in WINPE of the platform pack. I realize it could also be something simple as a bios update.
  8. Thanks for your help, with the one test machine I had it looks like not having "secure boot" enabled was causing the issue. Not sure if it was enable or disable from dell.
  9. Okay, I am checking now to see if this helps. I had some techs working on this for way too long and i found they changed a lot of settings all wonky in the bios.
  10. I got Sorry, there is a problem The page you are trying to access is not available for your account. Error code: 2C171/1 when clicking that link
  11. They were not in UEFI mode from the factory. I ended up factory reseting them and loading the recovery media, then install the smartdeploy agent, and deploy a package and that worked. But I will have to test further, the image was created in a vm, so uefi or legacy shouldnt matter.
  12. I was able to load the the OS from factory with t he DELL recovery usb, so not sure what the issue is here.
  13. after it looks like the image loads, the computer reboots and has no bootable device other then network nic. We were using pxe by the way not a usb boot disk.
  14. logs https://1drv.ms/u/s!AhwoICTP_02ug_URVLAl9mIbqXaZYg
  15. We recently received 10 Dell Latitude 7490, we are having trouble deploying the image on them, it cannot seem to see the SSD. Anyone have trouble with this or resolve this before?
  16. You know what it started doing the error again. I had to make a change in the image and tried to take the image all over again using the iso to put in the vm, and gets all the way to the end before i get the error. logs: https://1drv.ms/u/s!AhwoICTP_02ug-4oQrAIKNYyEhgxIQ
  17. I am just leaving them in, as I found in the past major issues when messing with them. I do have some GPO's though that push a custom start menu and desktop from some users.
  18. for 1709 I had to start over from scratch for my images.
  19. I got an error when trying to capture and new fresh image of windows 10 enterprise 1709 "the specified image does not contain a <customdata> node and cannot be used for deployment" not sure what the issue is here. Capturing from vm on ESXi 6.5 host using pxe boot and capture. see logs https://1drv.ms/f/s!AhwoICTP_02ug-4TJbBesh7u6f8z_g
  20. Thats a good point, yeah you will have to make your differencing image again if you modify the master wim
  • Create New...