Todd Cramer’s Blog bio picture
  • Welcome to my Blog!

    Thank you for visiting my incredibly awesome site! My name is Todd Cramer, and this is my Blog where I plan to document and archive technical issues, solutions and other interesting topics that I come across.

    Feel free to read through my posts and comment with your thoughts or questions.

If you are trying to use the Excel 2016 Power Maps add-in and get a message saying all online content in Office is blocked, you should first check the setting under Options>Trust Center>Trust Center Settings>Privacy Options>>Let Office connect to online services from Microsoft.  It should be enabled.  If this does not resolve the problem, there […]

View full post »

We have all been there…you receive a software update and continue to postpone the reboot as long as possible.  When the reboot deadline hits you are still not ready to reboot.  This leaves you with 2 options.  You can either let the scheduled reboot take you to wonderland or follow these instructions and stop the reboot […]

View full post »

You come into the office Monday morning to find someone deleted your AD machine account.  First, it’s no surprise as it is Monday.  Rather than logging in locally to re-join the domain, you can use the Restore-ADObject PowerShell cmdlet to quickly restore the account. Verify the machine account exists in the Deleted Objects container: *replace […]

View full post »

When you build a task sequence in SCCM and MDT you can use WMI queries to run steps for specific computer models.  This is especially useful when installing driver packages or BIOS updates.  Here is an example of a WMI query to detect only Surface Pro 4 devices: SELECT * FROM Win32_ComputerSystem WHERE Model Like […]

View full post »

  • October 27, 2016 - 1:55 am

    Yunar - Hi Todd,
    Thank you. I found it is very useful to run command in local machine “Get-WmiObject Win32_ComputerSystem”
    How to get the same information for remote machine?ReplyCancel

    • October 27, 2016 - 9:59 am

      Todd - Hey, you can run on remote computer by using the -ComputerName parameter. See the below command…replace MyPCName with the remote computer name.

      Get-WmiObject Win32_ComputerSystem -ComputerName MyPCNameReplyCancel

      • October 28, 2016 - 1:40 am

        Yunar - Excellent, it works. Thanks a lot.ReplyCancel

        • October 28, 2016 - 9:07 am

          Todd - Happy to help!ReplyCancel

The default SCCM boot media background image is plain and boring… I think most of you would agree.  The other day I found myself with a few minutes for some creative time so I decided to create a retro inspired background image.  I wanted to post for anyone who shares my love of 16-bit awesomeness!  Click […]

View full post »

Good morning!  Today I am in the process of certifying new Dell models for Windows 7.  This is normally a pretty simply task but the Dell Precision 7710 is fighting back.  I have created a driver package using the latest drivers available and set it up in OSD.  However, after installing the drivers and rebooting […]

View full post »

  • September 29, 2016 - 1:06 am

    Bo Nygren - Hi,

    BIG thanks for this blogpost 🙂

    I have applied the “fixes” but i can’t find my NVMEdrive (NO C:).
    All drivers are applied as usual but no luck.

    So i got my ipadress but i can’t get a systemdrive, my TS can’t continue and goes to the black hole.

    Do you have any clue what i done wrong?ReplyCancel

    • September 29, 2016 - 9:26 am

      Todd - Hey, if you’re not seeing your local disks when booting to the SCCM boot media you’ll need to add the proper mass storage controller drivers to your boot media. It’s the same process if you were missing network drivers. 1) Download the correct drivers from the vendors site. 2) Test the drivers to confirm they indeed function in WinPE. 3) Import the drivers and add to your boot media. 4) Update the content for the boot media you modified.

      Note: It’s always advised to check the logs to get a better idea of what’s happening. In your case you should review the smsts.log file.

      Hope this helps!ReplyCancel

  • April 3, 2017 - 5:58 pm

    Tim - Hi – Awesome Blog and guide.

    Ive encountered this same issue for our new HP probook 640 G3

    I get the same BSOD screen above, during the Bootup (in safe mode) the last driver it gets stuck on is the amdkmpfd.sys – AMD PCI Root Bus Lower Filter.

    I have updated, chipset and graphics. Im having trouble finding the correct NVME driver for it (if thats even what im needing)

    any ideas?ReplyCancel

    • April 3, 2017 - 7:10 pm

      Todd - hey, thanks Tim. I have some steps I was going to recommend but then stumbled across this HP KB document. This seems spot on, let me know if this resolves your issue. You’ll also want to confirm the hotfix I described above installs successfully. If you are getting the 0x0000007E (not 7B) then you’ll also need to install KB2990941.

      To workaround this issue, perform the following steps.
      F10 BIOS Settings

      Set Fast Boot disabled
      Set Secure Boot disabled
      Set Legacy Support enabled

      Download the softpaqs (aka. updated drivers)

      USB 3.0 Driver
      Network Driver

      HP Document ID: c05040446ReplyCancel

      • April 5, 2017 - 1:49 am

        Tim - Thanks mate, I know its definitely the hot fix that is required to run. (have tested it manually and win7 proceeds to install)

        however when im running the package via the TS it will stall, then fail with the error code x00000003

        what steps did you take to create the package?
        Ive done a “standard program” with the command line
        wusa.exe filename.msu \quiet \norestartReplyCancel

        • April 5, 2017 - 11:10 am

          Todd - I would first review the smsts log file as that will give you more details on why it failed to run. Looking at your command (maybe it was a typo in your message), you need forward slashes with the command line switches (/quiet /norestart).

          I had created a package with the hotfix files but did not create a program…instead I used the ‘Run Command Line’ step in the task sequence. I referenced the package that I created and installed using DISM.
          DISM /Image=C:\ /Add-Package /PackagePath:”.\KB2990941.msu”ReplyCancel

  • April 6, 2017 - 8:02 pm

    Tim - Found what it is. in the task sequence the ” ” in this part (DISM /Image=C:\ /Add-Package /PackagePath:”.\KB2990941.msu”) were causing it to fail.

    deleted the quotation marks and it imaged successfully.

    thanks for your help! and hopefully it helps others with this model HP as well.ReplyCancel

    • April 6, 2017 - 8:12 pm

      Todd - That’s great!!! Thanks for the update…glad you were able to get it working!ReplyCancel

  • April 24, 2017 - 3:01 pm

    Patrick - So, this may be en elementary question, but I’m getting a task sequence error when it gets to the point of the TS where I’ve added this step. I’m trying to image a Precision 5510 w/ a NVMe SSD.

    The error on the smsts.log isthis:

    Failed to run the last action; Error in the task sequence. Execution of task sequence failed. The system cannot find the file spedified. (Error: 00000002; Source: Windows)

    I’m guessing it’s because I didn’t package the .msu file correctly in step 2 above. Could you assist with how you did that? I removed the quotation marks from the DISM cmd as noted in the comments above as well.ReplyCancel

    • April 24, 2017 - 3:22 pm

      Todd - Hey, sure lets see if we can figure this out. There are several things that could be causing your issue…basically the task sequence step isn’t finding the hotfix where it should be. Here are a few things to try.
      1) Is the hotfix at the root of your package source directory?
      2) Did you distribute the package content to your DPs?
      3) Is your task sequence deployment set to access content directly from a distribution point? If so, you’ll want to make sure the hotfix package content was also copied to the package share on the DP. A lot of people miss this one.
      4) If everything above looks good, double check the task sequence step to make sure you’re referencing the correct package and there are no typos in the command. Shoot me a screenshot and I can review with you. todd@thecramers.usReplyCancel