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,411 profile views
  1. Config Mangler

    Bitlocker and MBAM

    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
  2. 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.
  3. 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.
  4. There's no upgrade path. You can only go LTSB -> LTSB
  5. 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.
  6. Config Mangler

    Surface Pro 4 PXE

    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.
  7. Caveat: Do not start deleting folders in SCCM without understanding the structure. If you are not short of disk space then leave it alone! That said :-) if you wanted to move something large like an OS .WIM file, in: Software Library | OS Images | Properties | Data Sources - note the existing path - copy the file to your new location - change the data source path to the new location then right-click Update Distribution Points - once you are happy it has replicated you can delete the file from the path you noted earlier.
  8. Config Mangler

    SCCM 2012 Boot Media certificate expired

    Assuming you are booting the VM from an ISO, just recreate the ISO and it will have a new certificate. Task sequences | Create Boot Media | Bootable Media | Site Based | CD/DVD Set - default is a year but you can make it longer
  9. So in Operating System Images you should see PS100091 as the image ID for your 1803 WIM. Click on content status then view status to see if there are any errors there. Guessing IIS is ok just giving an error as the content's not there.
  10. 80070002 is file not found - guessing your site is PS1 so the content it's missing 00091
  11. 1802 is baseline now so you can install that straight off. 16 core / 96 Gb is to support the maximum number of clients which is 50,000 when SQL is installed locally. It supports more clients if SQL is local . We're supporting 15,000 clients on an 8 core, 64Gb VM and performance is fine. SQL will take all the memory if you let it so that needs restricted.
  12. Config Mangler

    Upgrade to IE11 Issue

    Might it be this line "Setup exit code: 0x00009C4F (40015) - Wrong OS Version"
  13. Config Mangler

    Build failures on SCCM 1710

    This is now escalated with Microsoft for a code review. To be clear this failure only happens when rebuilding from Windows 10 to Windows 10 using the SCCM client. We think the failure happens when there are updates pending in Windows. It doesn't happen every time so it may be a combination of certain updates. My point with Microsoft is that the SCCM client should be able to handle this particularly if you are doing a wipe and load and don't care about updates.
  14. There is no choice here. You have to use the ADK to support your 1710 installation. https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/support-for-windows-10#windows-10-adk p.s. Not sure I would manage 7 and 10 alongside. Why not migrate them (install the client from new server) when you want to build Windows 10 then let the old server die out.
  15. Config Mangler

    PXE Booting Failure

    PXE doesn't work across subnets unless you have IP helpers / relay enabled on the routers. Can you test PXE on the same subnet initially to prove it's working?