SCCM / ConfigMgr, WDAC, OSD and the occasional trauma dump.
-
WINPE 10 Problems and work arounds
To successfully deploy Windows 10 Microsoft recommends using WINPE 10 however there has been a few issues with Powershell and .Net Framework You may see randomly the errors The operating system reported error 2147943401: Recursion too deep; the stack overflowed. The exception Illegal Instruction. An attempt was made to execute an illegal instruction. A…
-
MDT Bitlocker Step completes successfully however logs Verify %OSSKU% is defined.
Bitlocker is only supported on Windows Enterprise or Windows Ultimate or Windows Server Verify %OSSKU% is defined During the Bitlocker step a few checks are made including one that attempts to determine whether the install.wim is enterprise, to work around this define the task sequence variable OSSKU to ENTERPRISE. ALTERNATIVELY Use the SCCM built-in step…
-
/
Ensure the Operating System applys to C: drive not D: drive
This problem will increase more and more as everyone starts to use wim’s instead of the OS media in SCCM. There are a few workarounds for this problem however the best method is to force the new OS the reevaluate Drive Letters with 3 easy steps after applying the OS Create a Run Command Line step…
-
Windows 10 Upgrade installs stupid drivers.
UPDATE: Perhaps I should say the Intel network drivers are bad, and you have to work out which ones work, some need to be installed via setup, some shouldn’t be updated. When Windows 10 upgrades the machine it will replace drivers during the upgrade, sometimes replacing them with outdated drivers that don’t work correctly. Updating…
-
Windows 10 Upgrade stuck at 76%
One of the reasons the upgrade will stay at 76% percent is if you have the Client for NFS feature enabled before upgrading. To work around this you can run some commands before and after the Upgrade Windows step. Before: Dism /quiet /norestart /online /Disable-feature /featurename:ServicesForNFS-ClientOnly After: Dism /quiet /online /enable-feature /featurename:ServicesForNFS-ClientOnly Dism /quiet /online…
-
Azure Post
Site moved over
-
/
Bad Fat mifs in a multiple user environment
If you are getting alot of error 2719 under SMS_INVENTORY_DATA_LOADER in a multiple user enviroment such as a lab of computers consider tweaking the data you are collecting. Inventory Data Loader failed to process the file G:Program FilesMicrosoft Configuration Managerinboxesauthdataldr.boxProcessH5CCBXME.MIF because it is larger than the defined maximum allowable size of 5000000. Solution: Increase the…
-
/
Creating Collections to deploy ConfigMgr client updates (the easy way)
Get the Servicing Exstension from Microsoft NOW as it does all the work!!! http://blogs.technet.com/b/configmgrteam/archive/2014/12/09/now-available-microsoft-system-center-2012-configuration-manager-servicing-extension.aspx Once you have this, in the Admin node, there’s a site servicing section -> client targeting. You click ‘Create Query’ and it makes a nice query for your collections. Then you go about creating your collection. click next. Select Add Rule -> Query Rule…
-
/
Format failed (0x80070057) during task sequence.
Update: If this is happening to you I recommend importing the boot wim again creating a new one and only adding the network drivers (in the surface pro 3 case) and test using that boot wim with a copy of your task sequence. Then add existing sata/network drivers you need for other…
-
How To: Create Automatic Deployment Rules for Patch Tuesday Software Updates
Automatic deployment of updates is one of the best features of SCCM. Automation in general is awesome. The best way to use Automatic deployment rules (ADR) is to have them run on Patch Tuesday which is the second Tuesday of the month when Microsoft releases their updates generally before 11:00 PST/PDT (I am Australian based so…