SCCM Cannot Build Unknown Machines

Update: Microsoft suggest (despite the ambiguous wording) that the latest hotfix does resolve this issue. It may also be worth updating your boot images after applying the hotfix to ensure the fix applies. This is a bug introduced in SCCM version 1702 where unknown machines can not be built as they cannot find a task

SCCM cannot encrypt Windows 7 during OSD

I came across this problem which manifested itself differently in a few cases but the most common result is something like this: Windows 10 1511 (build 10586) includes a new bitlocker encryption, XTS-AES encryption algorithm, which cannot be read by earlier versions of Windows including Windows 7, 8/8.1 and 10 older than v1511. The fix

MDT and Language Issues

New issue here with deploying an automated MDT build of Windows 7. I found after deploying that the clock was in US format, the keyboard – US, everything defaulted to US. I couldn’t find an obvious quick way of rectifying this through MDT, so here is the easiest solution, no rebuilds necessary. Not something I’d

Citrix Receiver install script

This is my script for installing Citrix Receiver. The reg changes are to stop it launching on startup and to stop the nag for a user e-mail address that it needs on first run. This still cannot be prevented (to my knowledge) if the user is logged on during install, so either make it available

App-V 5 Recipe: Anaconda

Key points of sequencing Anaconda: use a PVAD Install Anaconda to C:\Anaconda_x_versionhere\ After installing, in the sequence do the first run tasks, change preferences and change any settings to point the PVAD. Screenshots planned.. one day. Sorry for the briefness!

App-V 5 and JDK Stuff

Just sequenced Android Studio in App-V 5.0 Sp3 successfully. Here’s how: Use the default GUID based PVAD and install JDK and Android Studio in the same package, all to the PVAD. Job done 🙂 This lync may be of use too if Java has any issues trying to update itself and other bits and pieces:

MDT Won’t Capture the WIM

So MDT won’t capture. Towards the end of BDD.LOG I get this:

The problem here became pretty much obvious on going just a few lines up: About to run command:

Due to the default naming of the captured WIMs, you cannot capture the same task sequence twice in a single day without deleting/moving/renaming

App-V 5.0 SP3 Server Install

Recently tasked with upgrading App-V 5 SP1 servers to SP3 I ran into difficulties with the database, deleting a table it wanted to later update. This was down to Microsoft getting the order of execution wrong in their readme file. Here’s the correct order, a solution I found on technet: 1. CreateTables.sql 2. CreateStoredProcs.sql 3.


Recently attempting to repair a Windows 8.1 laptop, having trouble running sfc /scannow from a repair cd with this error: “There is a system repair pending which requires reboot to complete. Restart Windows and run sfc again.” Doing some searching I managed to find this useful tip and thought it was worth a share: This