Jump to content

Config Mangler

Established Members
  • Content Count

  • Joined

  • Last visited

  • Days Won


Config Mangler last won the day on November 2 2017

Config Mangler had the most liked content!

Community Reputation

4 Neutral

About Config Mangler

  • Rank
    Advanced Member

Recent Profile Visitors

1,726 profile views
  1. So you get some content some times? If it was something like boundaries you wouldn't anything. Dodgy NIC driver on your physical machines then? Import latest NIC driver into WInPE.
  2. Failing hash check is a corruption so dodgy network or corrupt content. You could try deleting the package and redistribute it again.
  3. 80070002 is file not found. Getting content hash value for reference package P010001E Is that package distributed to the DP?
  4. Never seen one with no tabs! Maybe re-import the boot image. Should be in \\servername\SMS_site\OSD\boot\x64 Could be Windows ADK not installed properly or wrong version - I would look at that too.
  5. First have you got command support enabled on the boot image (F8). If not do that next. If yes hit F8 as it's preparing network. Do an IP config. Does it show a network driver and IP?
  6. I don't specify the product key at all at that stage. Leave it blank is my suggestion!
  7. Full WMI code for these is definitely "HP Compaq 8200 Elite SFF PC" However I think you might have other problems with this model further down the line. They are ancient!
  8. I don't see a problem with this. Install the MBAM client in your build or distribute after build time. Set up MBAM server and associated group policy. When it joins the domain you'll get group policy and the MBAM client will kick in and prompt the user for a PIN and encryption will start. You need to add some REG keys to make this happen quickly [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\FVE\MDOPBitLockerManagement] "ClientWakeupFrequency"=dword:00000001 "StatusReportingFrequency"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MBAM] "NoStartupDelay"=dword:00000001
  9. Not sure how mature peer cache and branch cache are. I'm also interested to see if anyone is making it work! We use 1E Nomad for this purpose and have done for years. We have 1 main DP for 12,000 users because of this. If you want to do an OSD at a slow site you build a master PC and ship it to that site. The clients can then pull everything from that PC and not go back to the DP.
  10. No you can't patch it up a full release version. you need to use the in-place upgrade task sequence for existing machines or download the 1803 ISO and drop that into your wipe and load TS.
  11. I've had that when driver source files have been removed so next time you do an update it can't find them and errors. Look at the properties of the boot image and note what's under the drivers tab. Remove some or all of the drivers and update the boot image. If that's clean then import your NIC drivers again from source.
  12. I never got the Surface 4 to PXE boot. I didn't take it much further as we don't have very many. The later Surface Pro does PXE in exactly the same environment.
  • Create New...