Microsoft 365 learnings

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....

SCCM site backup was failing with following error,  smsbkup.log showing following error. Cannot find the dependent writer. The dependant component cannot be backed up. AddDependentComponent(pDependency) failed. Error code = 0x80,004,005.Error description = . Error: GatherWriterMetadata failed. 1. To fix this issue  Run 'VSSAdmin list writers' command. 2. Ensure following writers listed. 3. If you identify these two writers are not listed, restart 'SQL Server VSS Writer' if SQLServierWriter' is missing or 'SMS_Site_VSS_Writer' if SMS writer is missing. 4. 'VSSAdmin list writers', ensure both services are listed. 5. start sms_site_backup service to start backup, monitor smsbkup.log, ensure backup completed successfully.

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 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

Recently I upgraded iTunes to 12.5.1 on Surface Pro 3 with Windows 10 Pro build 14393. iTunes couldn't detect connected iPhone. Noticed Windows Device Manager is not showing Apple Mobile Device under 'Universal Serial Bus Controllers', However iPhone was listed under Portable Devices. 10 Steps to fix iPhone detection issues in Windows 10. 1.      Connect iPhone to PC and Open iTunes. 2.      Right Click on Start Menu, Select 'Device Manager ' or Search Device Manager in Cortana.  3.      Expand Portable Devices. 4.      Right Click on Device i.e. Apple iPhone in this case. 5.      Choose 'Update Drive Software'. 6.      Select 'Browse my computer for drive Software'. 7.      Go to C:\Program Files\Common Files\Apple\, Ensure 'Include Subfolders' option  is ticked. 8.      Click Next, Close to finish Installation of driver. Confirm Apple Mobile Device USB Driver are installed successfully

Recently i have attempted to upgrade MobileIron Core from 7.x and Sentry 7.x latest version. Here is my experience with the product and upgrade, i hope this will be useful to MI Admin. Prerequisites: 1. Ensure you have console access to MI Core and Sentry access. 2. Ensure you can connect using Putty to MI Servers. 3. Ensure you have admin credentials to the server. Attempt 1  We decided to upgrade using following plan with the rollback plan i.e Snapshots. Upgrade Core from 7.0.0.1 to 8.0.1.0. Upgrade Sentry from 7.0.1 to 7.5.1 Upgrade Core from 8.0.1.0 to 9.0.0.0 Upgrade Sentry from 7.5.1 to 8.0.1.  Upgrade Core from 9.0.0.0 to 9.1.0.0 Outcome : Failed ! MobileIron Core upgrade failed with schema mismatch error. It seems MI databases have multiple entries that needs to added,deleted, amended to resolve schema mismatch issues. MI Support informed this is issue across the board.  Learning 1 - Never attempt to upgrade without snapshot ! Learning 2 - Keep M

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.