Jump to content


velnias

Established Members
  • Posts

    3
  • Joined

  • Last visited

Everything posted by velnias

  1. I was running into the same issue. In a nutshell, it looks as if once all of your DP's are migrated, this will go away. You may have already found this but here is an article relating to it. http://social.technet.microsoft.com/Forums/en-US/017cca70-f35a-45b2-892a-85dd5b2e3cc3/error-failed-to-decrypt-cert-pfx-data-distmgrlog?forum=configmanagermigration
  2. So I think I finally found a place to ask my question as I can't find any reference to it anywhere but I believe I'm having a similar issue... My question is, how does SCCM determine which boot file to use during WinPE/PXE boot? I realize that the Task Sequence uses the referenced boot file, but prior to that during PXE boot, which file does it pull? I ask because we have 4 boot images currently; two standard that came with the install of SCCM and two custom boot images (x86 and x64) based on a specific set of network drivers on newer model laptops. While I can't find any reference to how SCCM determines which boot file to use, I've been told that it only chooses the most recent boot file on the PXE enabled DP. However, if I don't have all 4 on the DP, inevitably an OSD Task Sequence will fail. I should note, that we only deploy 32bit OS and our custom boot file is basically just the stock SCCM boot files with the necessary added drivers for the new machines. I would have thought that this would boot any older models in addition to the newer laptops because we injected the drivers, but the reverse happens and it will no longer boot anything but the newer models. Certainly I don't have to inject every conceivable driver in our hardware list to make this work right? I'm sure I've got something wrong but I can't for the life of me figure it out.
  3. The SMSTS log is on the client itself and you will have to enable PXE Command support from the boot file. In your SCCM Console, Software Library, Operating Systems, Boot Images. right click on the boot file and choose properties. On the Customization tab, check the box at the bottom "Enable command support (testing only)". Save and update the boot file to your distribution points. Repeat this for both Boot files, x64 and x86. Once you've done this, when the error occurs on the client, press F8 and it will open a command prompt where you can navigate to the SMSTS log, and copy it off to a shared drive to review. The log file will be in different locations depending on where it fails in the OSD process. This site has a good overview on where to locate the files.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.