Showing posts with the label SCCM

SQL Query to get Mobile Device and Primary Users from Microsoft Configmgr

Following query will give you list of the mobile device managed by Intune and its user from Configmgr. SELECT        dbo.v_R_System.Name0, dbo.v_GS_DEVICE_COMPUTERSYSTEM.IMEI0, dbo.v_GS_DEVICE_COMPUTERSYSTEM.PhoneNumber0, dbo.v_GS_DEVICE_COMPUTERSYSTEM.DeviceManufacturer0,                           dbo.v_GS_DEVICE_COMPUTERSYSTEM.DeviceModel0, dbo.v_GS_DEVICE_COMPUTERSYSTEM.SerialNumber0, dbo.v_GS_DEVICE_COMPUTERSYSTEM.TimeStamp AS Expr1,                           dbo.v_GS_DEVICE_COMPUTERSYSTEM.FirmwareVersion0, dbo.v_GS_DEVICE_COMPUTERSYSTEM.SoftwareVersion0, dbo.v_R_User.Full_User_Name0, dbo.v_R_User.Name0 AS UserID,                           dbo.v_R_User.User_Principal_Name0 FROM            dbo.v_GS_DEVICE_COMPUTERSYSTEM RIGHT OUTER JOIN                          dbo.v_R_System INNER JOIN                          dbo.v_UsersPrimaryMachines INNER JOIN                          dbo.v_R_User ON dbo.v_UsersPrimaryMachines.UserResourceID = dbo.v_R_User.ResourceID ON dbo.v_R_Sys

ConfigMgr Task Sequence Error 0X8004005

I am working on couple of exciting SCCM Projects and still learning something new every day. I have been figuring out why SCCM task sequences are not deploying to workstations. Client was showing following error prior to showing option to select task sequence. Usually, you receive error 80004005 if time is not set correctly on computer or there is mismatch between SCCM DP/Primary site time and client time. In may case issue caused due to SHA1 Certificate chain. Somehow client have not upgraded their certificate authority to Sha2 due to some limitation with one of the applications. SCCM has been configured with SHA1 Certificates.  However, i forgot to untick the box 'Require SHA-256'.As a result , Boot image was failing to communicate with SCCM Management. To fix the issue untick 'Require SHA-256 from \Administration\Overview\Site Configuration\Sites. As shown below. Happy SCCM....

Dell Latitude 7480 Unable to Detect NVMe Drive

Dell Latitude 7480 Unable to Detect NVMe Drive while PXE booting using UEFI secureboot. To fix the issue download ' Intel Rapid Storage Technology Driver and Management Console' drivers from Dell Website.   Extract all drivers files, go to Drivers\Prodcution\Windows10-x64.  Inject iastoreAC.INF file drivers using DRVLoad command during PXEboot or in the bootimage. i.e Drvload \path\iastoreac.inf

ConfigMgr 1610 Windows Store for Business Integration Failed

ConfigMgr 1610 Windows Store for Business Integration Failed to encrypt client secret key. Windows Store for Business Integration is failing when I attempted to integrate Windows Store for business from ConfigMgt1610 Primary Site. In my scenario SCCM MP is hosted on remote server configured with SQL replica databases. Remote MP Servers do not have ConfigMgr Console Installed. It seems installing Configmgr console might fix the issue but not sure ! I am currently seeking solution for this. I have tried Configuring WSFB integration from SCCM Primary Site without MP Role but integration failed. Also, tried from remote console on server but not site server, Integration failed. I will try to install console on DP, will inform outcome. Issue explained in  TechNet . System.Security.Cryptography.CryptographicException Failed to encrypt client secret key. Stack Trace: at Microsoft.ConfigurationManagement.AdminConsole.Wsfb.WindowsStoreForBusinessDataHandl

SCCM 1606 Software Centre Old and New Best of Both Worlds

SCCM  1606 Software Centre Changes SCCM (ConfigMgr) 1511 has introduced new software center.  Some organisation might face challenges to deploy new software center. However, you can use run both software center side by side.  New Software Center executable is located under C:\Windows\CCM\ClientUX\ scclient.exe. You can still continue to use old software center and application catalog using old Software Centre. Simply publish another shortcut to all users pointing to C:\Windows\CCM\SCClient.exe. This might helpful to the organisation who is heavily using Software Centre\ Aplication catalog and user training / change management could be daunting task.  You can run both Software Center side by side.

Unable to PXE Boot Surface Pro 2 ?

Unable to PXE Boot Surface Pro 2 ?  Surface Pro 2 driver pack is available from download from Microsoft Website. This driver pack does not include the Ethernet Adaptor drivers to inject in WinPE boot image for PXE Boot. Initially I had trouble finding the driver to inject in Boot CD, driver is not included in Surface Pro 2 driver pack or any other official Microsoft link . I managed to identify driver from driverstore and inject in SCCM. The same driver package was  injected in Win PE boot image from SCCM 2012 R2 or SCCM 2012 SP1 CU3 using DISM command on Windows 8.1 machine . Driver can be downloaded from here . Thanks Pratik Dave 

Network Driver for HP Elitebook 840 G1

Network Driver for HP Elitebook 840 G1 Issue :  HP elitebook 840 G1 does no PXE boot when network drivers are injected in boot image. environment SCCM 2012 SP1. Answer: To build HP elitebook 840 G1  inject the Windows 8 network driver.  Please see post below from Niall C. Brady on how to inject or test drive during task sequence. Thanks Niall C. Brady for this article: . TO\o Download Driver click here   Unzip the file using 7 zip, go to \sp63299\Setup\Win8x64  folders and inject driver in boot image  from SCCM or using drvload command as explain in article.  Happy Days....