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
Azure AD Join error code 80180026
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
Azure AD join error code 8018000a
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
Recovering from BCD error 0xC000000D with BitLocker and Hyper-V
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
Using a Task Sequence Secret Value when changing a local password
At one time it became routine to manage Windows local account passwords with a Group Policy Preference. However, some time ago the process was was discovered to have a significant venerability and Microsoft released security bulletin MS14-025 to address the
ConfigMgr fails to distribute a package… failed to create instance of IRdcLibrary
Awhile back I had an issue distributing a new Package in ConfigMgr (SCCM). There didn’t seem to be anything unique about the package, it just didn’t want to process. Digging into the SMS Distribution Manager log (distmgr.log), I noticed a
SSRS Error 401.3 Access is denied
So, you’ve been denied! It’s OK. It happens to the best of us. Server Error in ‘/Reports’ Application. Access is denied. Description: An error occurred while accessing the resources required to serve this request. You might not have permission to
Downgrading SQL from Enterprise Edition to Standard for ConfigMgr
At a recent client engagement we discovered that Microsoft SQL Server Enterprise edition was installed on the ConfigMgr Primary Site Server. Technically this is not a problem, but it is only needed if you expect to have more than 150,000