SSD Machines failed with BSOD

This can be fixed by installing KB 2990941 and then  kb 3087873

Update to add native driver support in NVM Express in Windows 7 and Windows Server 2008 R2

BSOD error 0x0000007E

STOP: 0x0000007E (parameter1, parameter2, parameter3, parameter4)

https://support.microsoft.com/en-us/kb/2990941

https://support.microsoft.com/en-us/kb/3087873

If you Get <![LOG[Setting wizard error: There are no task sequences available for this computer.] as in your SMSTS/log file then check these points...

Ø  The computer is not imported in the console if you are using known computers not unknown computers

Ø  If you are using unknown computers, delete any devices with the name unknown (but whatever you do DO NOT delete the two builtin unknown records)

Ø  Make sure that the TS is enabled

Ø  Make sure the device is in a collection with a TS deployed to it

Ø  Change the schedule of the deployment to yesterday

Ø  Check if the TS deployment is set to ‘configmgr client, media and PXE’

Ø  The computer is imported with a mac address that is already in the database (check the report ‘MAC computers for a specific mac address’

Ø  The computer still has a cached pxe advertisement

Ø  The computer is in the console but is not approved

Ø  The computer has incorrect date/time settings

Ø  Check if the DP certificates have not expired

Ø  The Boot Image associated to the TS has not been distributed yet

Ø  The ResourceId of the computer that boot’s is already used by another machine in the console (verify the ‘itemkey’ value from SMSPXE.log versus the result from select * from v_R_system where resourceid=’….’

Ø  The biosguid of the computer that boot’s is already used by another machine in the console (check the biosguid from SMSPXE.LOG versus the result from select * from v_R_system where smbios_guid0 LIKE ‘%…%’ (try with a part of the biosguid…)

Ø  Delete the device from the console and import it again

Ø  Check if there are any bad policy assignments in the sql db:

Ø  SELECT * FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL) if this returns anything then you have to delete the items with: Delete FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL)

SCCM / Configuration Manager Current Branch vs SCCM 2016

In December 2015 MS introduced Current Branch (CB) method for SCCM too., like we have for Windows 10.

What it means to me ? 

MS can deliver SCCM  moving from longer release cycles to regular updates designed to support the faster way of updates for Windows 10 and Microsoft Intune and align with these products & features updates support as it is Business support application tool. 

There is no Current Branch for Business (SCCM CBB)  for SCCM, it's only SCCM Current Branch. 

SCCM CB has Technical previews where it automatically appears in SCCM Console. 

You can use these technical previews, however you can't degrade one version number to other. Typically, new versions of the technical preview are available each month  In the admin console, new versions appear as “Configuration Manager Technical Preview YYMM.” 

All these Feedback & new features will be bundled with upcoming SCCM 2016 version, So do not think that there is no 2016.... it will be release soon......

Are we talking similar to Microsoft update ? Even though I do not use Windows 10 in my infra I must have to update? 

Yes, if you have SCCM CB, and it must go for regular updates regardless of you support it's supported products in your infra. 

Each version is supported to 12 months. Each incremental update version may fix some security updated and include some new features, Where as SCCM 2012 / R2 (not Current Branch) versions will get only CU's to fix the security or bug fixes ( So ideally the CB update versions and CU's are same however CB are more frequent with some excited new features other wise both are same).  Similarly windows 10 CB / CBB / LTSB will be supported if you update SCCM CB to N+1 and applications compatibility to N-1. 

Tip of the Day................>
selfhost testing : The first recipients of builds are Microsoft employees who begin what Microsoft calls selfhost testing

SCCM / Configuration Manager Current Branch vs SCCM 2016

In December 2015 MS introduced Current Branch (CB) method for SCCM too., like we have for Windows 10.

What it means to me ? 

MS can deliver SCCM  moving from longer release cycles to regular updates designed to support the faster way of updates for Windows 10 and Microsoft Intune and align with these products & features updates support as it is Business support application tool. 

There is no Current Branch for Business (SCCM CBB)  for SCCM, it's only SCCM Current Branch. 

SCCM CB has Technical previews where it automatically appears in SCCM Console. 

You can use these technical previews, however you can't degrade one version number to other. Typically, new versions of the technical preview are available each month  In the admin console, new versions appear as “Configuration Manager Technical Preview YYMM.” 

All these Feedback & new features will be bundled with upcoming SCCM 2016 version, So do not think that there is no 2016.... it will be release soon......

Are we talking similar to Microsoft update ? Even though I do not use Windows 10 in my infra I must have to update? 

Yes, if you have SCCM CB, and it must go for regular updates regardless of you support it's supported products in your infra. 

Each version is supported to 12 months. Each incremental update version may fix some security updated and include some new features, Where as SCCM 2012 / R2 (not Current Branch) versions will get only CU's to fix the security or bug fixes ( So ideally the CB update versions and CU's are same however CB are more frequent with some excited new features other wise both are same).  Similarly windows 10 CB / CBB / LTSB will be supported if you update SCCM CB to N+1 and applications compatibility to N-1. 

Quote of the Day................>
selfhost testing : The first recipients of builds are Microsoft employees who begin what Microsoft calls selfhost testing

Servicing Options - Microsoft products Life Cycle - CB CBB LTSB

Recently Microsoft introduced new product upgrades as Servicing Options.

In enterprise IT environments, the desire to provide users with the latest technologies needs to be balanced with the need for manageability and cost control. 

In the past, many enterprises managed their products up-gradation and Purchase new / Upgraded versions of products about every three to six years. 

Today, the rapid evolution of Technology experiences is causing businesses to rethink their strategies. Especially with the release of Windows 10 & Microsoft Azure, there are good business reasons to keep a significant portion of your enterprise's devices current with the latest release of Microsoft products.

Streamlined the Microsoft product engineering and release cycle so that Microsoft can deliver the features, experiences, and functionality customers want, more quickly than ever.

Created new ways to deliver and install feature upgrades and servicing updates that simplify deployments and on-going management, broaden the base of employees who can be kept current with the latest MS capabilities and experiences, and lower total cost of ownership.

Implemented new servicing options – referred to as 

1) Current Branch (CB)

2) Current Branch for Business (CBB)

3) Long-Term Servicing Branch (LTSB)

That provide pragmatic solutions to keep more devices more current in enterprise environments than was previously possible.

Windows 10 release CB & CBB & LTSB find the related article  https://technet.microsoft.com/en-us/windows/mt679505.aspx 

In just one word Software as a Service - SAAS is all about above lines.

Servicing option	Availability of new feature upgrades for installation	Minimum length of servicing lifetime	Key benefits	Supported editions
Current Branch (CB)	Immediately after first published by Microsoft	Approximately 4 months	Makes new features available to users as soon as possible	Home, Pro, Education, Enterprise, IoT Core, Windows 10 IoT Core Pro (IoT Core Pro)
Current Branch for Business (CBB)	Approximately 4 months after first published by Microsoft	Approximately 8 months	Provides additional time to test new feature upgrades before deployment	Pro, Education, Enterprise, IoT Core Pro
Long-Term Servicing Branch (LTSB)	Immediately after published by Microsoft	10 Years	Enables long-term deployment of selected Windows 10 releases in low-change configurations	Enterprise LTSB

SCCM Task Sequence WMI logic for Models Based Drivers Deployment

SCCM Task Sequence OS Drivers apply based on Models with help of WMI Query

For Models check we can write as NAMESPACE Root\CIMV2

Select *From Win32_ComputerSystem Where Model LIKE "%X260%"

The above is if WMI matches however if we want a query for not equals then ?

WMI query for if Model is not equals

Select * From Win32_ComputerSystem Where NOT Model LIKE "%M800%"

WMI Query for If Manufacture like

SELECT*From Win32_ComputerSystem WHERE Manufacturer LIKE “%Dell%”
SELECT * FROM Win32_ComputerSystem WHERE Manufacturer LIKE “%Hewlett-Packard%”

SELECT * FROM Win32_ComputerSystem WHERE Manufacturer LIKE “%Microsoft Corporation%” 

SELECT * FROM Win32_ComputerSystem WHERE Manufacturer LIKE “%VMware%”

WMI Query for If Manufacture NOT like

SELECT*From Win32_ComputerSystem WHERE NOT Manufacturer LIKE “%Dell%”
SELECT * FROM Win32_ComputerSystem WHERE NOT Manufacturer LIKE “%Hewlett-Packard%”

SELECT * FROM Win32_ComputerSystem WHERE NOT Manufacturer LIKE “%Microsoft Corporation%” 

SELECT * FROM Win32_ComputerSystem WHERE NOT Manufacturer LIKE “%VMware%”

Find  32 or 64-bit Operating System in task Sequence WMI logic
SELECT * FROM Win32_ComputerSystem WHERE SystemType LIKE “%x64-based PC%”
SELECT * FROM Win32_ComputerSystem WHERE SystemType LIKE “%x86-based PC%”

For BitLocker:

TO CHECK TPM model status active / this will be used for Pre-requisites for Bitlocker

NAMESPACE: Root\CIMV2\Security\MicrosoftTPM

Select * From Win32_TPM Where IsActivated_InitialValue = False

Select * From Win32_TPM Where IsActivated_InitialValue = True