IT Consultant Everyday Notes

Just some problems/solutions storage

SCCM: What NOT to do when upgrade SCCM CB

Gerry published a piece of wisdom from Prod Team:


  1. Do NOT manually clean up EasySetupPayload folder for CM update that is being downloaded/processed.
  2. Do NOT manually clean up CMU without confirming the correct state and content library for the Easy Setup package.
  3. Do NOT restore the CM database/CM site server if there is an error with CM update (fix the issue and “retry installation”).
  4. Do NOT reinstall the Service Connection Point if an update is in progress.
  5. Do NOT use 1602 cd.latest to install a standalone primary site (Note: you can use this method to install a child primary to a 1602 CAS).
  6. Do NOT use 1602 cd.latest to upgrade a 1511 site or R2 SP1 (or earlier) site.
  7. Do NOT manually clean up any CM_Update* tables.
  8. Do NOT restart CMU service during installation.
  9. Do NOT keep the CMUStaging\<Guid> folder open during installation.
  10. Do NOT copy files in CMUStaging.
  11. Do NOT restart SMSEXEC during payload download (dmpdownloader.log shows if the package content is downloading). The Notification can get lost in that scenario.

Azure: Journey to ARM

Azure: Working with Templates in Azure Resource Manager

Azure: Use Azure Key Vault to save passwords

OSD: Microsoft Surface Deployment Accelerator

Video on a new Surface Deployment Accelerator (native MS tool integrated with MDT 2013 Upd 1) :

Nokia Lumia 835: Camera application failed “Something went wrong”

I tried to make a quick photo and got “Something went wrong” error on my phone Sad smile

I searched Intenet a bit and it looked like the issue is wide spread and people most often send the device to service since it a hardware issue.

I was almost there, but decided to think again if I changed anything recently. Sure enough I tested Microsoft Intune mobile device management and subscribed my phone to it. Even though “Camera off” policy was not enabled there it looks like it broke the device somehow.

So, I un-enroll from Intune and tried camera again. Now it works! Smile

Bottom line, I am not saying it will fix the issue in all cases, but at least worth to try to un-enroll you device from any sort of Mobile Device Management solution (if you have rights) and try without it.

SCCM: Remove Built-in apps when creating a Windows 10 reference image

SCCM: Upgrade TS does not process post-upgrade section

SCCM: How to extract drivers from an existing machine for later OSD

Michael published a quick-cheat for that. You can extract drivers to a folder, import them to SCCM or MDT and deploy back to bare-metal machines.


powershell command is:

Export-WindowsDriver -Destination “C:\Drivers\$((Get-WmiObject -Class win32_computersystem).Model)” -Online


more details here:

SCCM: OSD tattoo script

Jason Sandys  published a nice script for tattoing imaged machines.


Get every new post delivered to your Inbox.