Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About gleep52

  • Rank
  1. No one else has this problem or knows why this is happening?
  2. I am using hyper-v to build a windows 7 image (installed from scratch MVL disc), installed all of the windows updates, then using a windows 10 ADK boot file, I create the capture media and try to capture the image. This is how I've always done this in the past and it works fine with Windows 10. But so far I've tried this on three computers and each time the system runs it's sysprep, reboots, starts in PE, scans the volumes, then starts capturing them. But shortly into the second (OS partition) volume, it craps out and hyper-v just restarts for no reason, no warning, no ability to press F8 t
  3. Did you ever find out what the problem is here with this? I'm getting this on a lot of my older deployments... not sure what the deal is though?
  4. Well at some point I was able to get past the winload.efi error by recreating my boot images - though I don't recall the process and since then something else has changed where the same winload.efi error is rearing it's ugly head again. I need to use uefi on these laptops, and it DID work previously. What version should my boot.wim file be? Mine says 6.2.9200.16384... isn't that the WinPE 4.0 version? When I try to add a boot.wim file directly from the windows media it fails. Google reveals others with the same issue and their work around was to use the boot images that came with
  5. We have CU2 installed and the update packages are in place - I've assigned them to our respective x86 and x64 container collections, however - when I go to the default push client - it still says the registered version is build .1000 instead of build .1300... how do I change that so it installs the latest version instead of depending on the upgrade each time? Is there a way? Or is this a normal/standard setup?
  6. When we push out ANY of our images we've created with SCCM - it's hit or miss if the client will talk with SCCM properly. The client gets installed, the software center has our custom text on it, all the actions show up on the control panel on the client, everything looks absolutely normal, except updates never get pushed down, and endpoint does not install either. When looking at the config manager console, it shows the computer is there, but the client type is listed as "none" instead of "computer"... The client's control panel shows the right site code so I'm not sure what the hang up is.
  7. When I try to create a new task in the windows task scheduler, it fails with the error: An error has occurred for task <task name>. Error message: A task or folder with this name already exists. The strange thing is, I've got this happening on a lot of my servers now... I have no idea what I changed, but apparently I cannot create new tasks now - this is a brand new freshly installed windows box as well. On one of our servers, I have created many scheduled tasks, but I can no longer create new ones on that server either. We use SCCM 2010 SP1 as well, with endpoint protection -
  8. We just got our sample unit in for our school district's next 300+ machines... it's UEFI - has legacy option in the bios. But if I switch it to legacy, the thing won't boot or do ANYTHING except stay at a boot manager screen (built in, not SCCM). If I switch it to UEFI, it boots normally, but if I plug in the Ethernet, it boots directly from it stating PXE boot IPv4... clever! Or is it? The WIM files load, but after the bar slides across the bottom, when it usually will start the server 2012 boot logo, instead it chirps and crashes. It says: Windows failed to start. A recent hardw
  9. Thank you so much for posting your solution here. It didn't work exactly as you have listed for me, I had to do an extra sync between unselecting the classifications in SUP and running the reset command - but I did manage to get it working again thanks to you! Bravo!
  • Create New...