It’s been many years since I read that SQL databases should use an NTFS volume formatted with at 64KB file allocation unit size (block size). So long that I didn’t remember why or if it is still considered best/good practice. It appears that it is according to Microsoft and the foremost authority on SQL with ConfigMgr.
keep reading at http://blogs.catapultsystems.com/chsimmons/archive/2016/12/23/configmgr-and-sql-ntfs-allocation-unit-size
Chad December 23, 2016
Posted In: ConfigMgr, Scripting, T-SQL
Several ConfigMgr scenarios require that the content Source Path be changed. This typically includes migrating to a new ConfigMgr environment (2007 to 2012, 2012 to Current Branch, etc.), and simply moving the source content to a new location such as a DFS Share or low-speed NAS device.
Updating the Source Path can be done manually via the ConfigMgr console. For Packages, Software Update Deployment Packages, Drivers, Driver Packages, Operating System Images, Operating System Upgrade Packages, Boot Images, and Virtual Hard Disks, just add the Pkg Source Path or Package Source Path column to the console view to review the paths, then edit the object’s Source Folder in the Data Source tab.
However, for Applications, you’ll have to step through each Deployment Type on each Application, view the properties and modify the Content Location in the Content tab.
This is all painfully slow if you have more then a handful to deal with. So, automate it!
The community has developed at least 5 solutions to this including
CoreTech and Nickalaj have the slickest solutions. Sometimes a GUI gives the visual feedback you need to be confident in the final outcome.
Either of these two tools should effectively handle the changes. As a bonus, both will actually copy the content files from the old to the new path. Awesome!
Chad September 28, 2016
Posted In: ConfigMgr, Scripting
When attempting to join Azure AD you are presented with the message “contact your system administrator with the error code 80180026”
Something went wrong. Confirm you are using the correct sign-in information and that your organization uses this feature. You can try to do this again or contact your system administrator with the error code 80180026. Try again.
keep reading at http://blogs.catapultsystems.com/chsimmons/archive/2016/09/07/azure-ad-join-error-80180026
Chad September 7, 2016
Posted In: Microsoft Intune
Azure AD, Microsoft Intune
Recently when attempting to perform an Azure AD Join with a Windows 10 v1511 computer I got the following error:
Something went wrong. The device is already enrolled. You can contact your system administrator with the error code 8018000a.
That didn’t make sense because I had recently disjoined the computer from Azure AD. I could find no reference to the object in the Azure portal either.
Keep reading at http://blogs.catapultsystems.com/chsimmons/archive/2016/08/26/azure-ad-join-error-code-8018000a
Chad August 27, 2016
Posted In: Microsoft Azure
I recently had a nasty issue with my seriously awesome laptop (Lenovo ThinkPad P50 with a Samsung 950 Pro NVMe n.2 SSD). After a full shutdown (hold Shift when shutting down Windows 10) on the next power on I got a BitLocker recovery prompt.
That’s happened before, so I just powered off and back on like I’ve always done. However, this time I was greeted with a foreboding BCD error:
Keep reading at http://blogs.catapultsystems.com/chsimmons/archive/2016/08/12/recovering-from-bcd-error-0xc000000d-with-bitlocker-and-hyper-v
Chad August 12, 2016
Posted In: Windows 10