Jump to content


h4x0r

Established Members
  • Content Count

    149
  • Joined

  • Last visited

  • Days Won

    5

h4x0r last won the day on March 29 2017

h4x0r had the most liked content!

Community Reputation

9 Neutral

About h4x0r

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  • Location
    West Kentucky
  1. I believe the reason is that the RemoteInstalls folder does not get removed simply when the WDS role is uninstalled...as a result, you have an overlap of files that are corrupt and the new ones you need to implement. Don't forget that you need to have both the x32 and x64 images distributed to your DP. Glad I could help!
  2. They do have USB ports, and I had forgotten to mention the USB NIC as a consideration as well. I have not had great success using USB NIC's in the past...as you point out, there will be a limited number of supported devices there. Thanks!
  3. Are you PXE booting these via legacy or UEFI? I have seen instances where if a device is PXE booted via legacy, but is operating with UEFI, that the format drive step can bugger things up and the apply OS step can't find the partition...but, network boot with UEFI and it formats correctly, and the OS is able to apply. Also, there is this thread regarding UEFI PXE booting issues.
  4. A colleague of mine had a similar issue with his configuration. I think we ended up solving the issue by removing WDS (un-check option on your DP to respond to PXE), renaming the RemoteInstall directory (RemoteInstall.old), *edit* re-enable PXE support on the DP, and then re-creating his boot images (he had MDT integration, so we used that). We did this for both x32 and x64 boot images.
  5. Good day everyone, I would like to pick the brain of the proverbial community think-tank here on the forums. The product We are looking at purchasing a number of (what I am calling) WInBooks for students (Dell 3180's, Lenovo N22, etc). These are basically Windows 10 versions of their ChromeBook counterparts. 11" screens, Celeron/Pentium procs, 4GB RAM with 64/128GB SSD's...and wireless only. The IDEAL solution Generally speaking, I think the solution to provisioning these would be using InTune, but that is not on the table due to budgetary reasons. As such, I
  6. I'm in 100% agreement with you there There are a number of school districts in our state who have inherited a ConfigMgr setup, either due to being a new hire or someone leaving the department, and they get handed management of CM...I am always telling them: test, test, and then test again.
  7. Thanks for this write up, Niall...I was actually getting ready to start work on this very project here This is particularly useful in my scenario, for a number of reasons. I work for a K-12 school and the AD/network structure is...different, from most places. I do not have access to my WSUS server, AND it sits in the DMZ behind my internet filter (don't get me started). The entity controlling the approved patches for Windows 10 has them on a delayed schedule due to the fact that they test all patches first to make sure that they are compatible in our environment. I have the potential
  8. Thanks Tregelen...you mention different approaches...do you mean thick vs thin images being deployed?
  9. Thanks Rocket Man...I agree that 4min seems ludicrous...I'm sure there are things we could do to better optimize our OSD...but there's no way I could bring it down to that. Do you mind if I shoot you a PM with a couple other questions?
  10. Good day everyone, Let me provide some background...I work for a school district, and we use CM for imaging, software deployment, endpoint security, reporting, etc...fairly standard in my book. In a recent session with some other districts, another tech mentioned that they were able to image a workstation in 4 minutes using their FOG server (FOG is a free imaging tool, runs on Linux...look it up if you are curious). Now, there are a lot of factors that could come into play there...network congestion, SSD vs SATA drive, etc...but part of me is sitting here going, there's no way that
  11. Ha, gotta love that I mean, it is a fairly small inconvenience all things considered, but it makes me wonder what the real culprit is.
  12. Well I ran across some interesting information the other day...I forget why I was looking at this thread on reddit, but from what I can tell, this may be the issue: Hyper-V VM's need to Gen 2 for deploying Windows 10 successfully/correctly. I'm using the same VM that I have for years at this point, and hadn't even thought of changing/checking the VM generation. I updated to the 1511 ADK the other day and noted that I was still experiencing the issue. When I created a new gen 2 VM on my workstation, however, it worked like a charm. I hope this helps for anyone else who might run into
  13. Thanks for the info...I have it on my to-do list to get that upgraded, but have not had the time just yet. I will update to the latest versions of those and see if that makes a difference in my environment.
  14. Reviving a semi-old thread here...I'm also having the same experience with imaging my hyper-V VM with my captured Win10 image. I haven't had a chance to test this on a physical station however. Other thread that I've come across all share the same issue, but there is never a defined resolution. Has anyone made progress on this?
  15. I would start by checking your site and component status to see if there is anything that needs to be resolved there.
×
×
  • Create New...