syswow64 blog

Scenario: I wanted to package the Office 365 Activation Troubleshooter ( Officeact.diagcab ) for Office 365 users with activation issues. I needed to find out the commands to use as well as the appropriate Detection Method. 1. Download: Officeact.diagcab https://aka.ms/diag_officeact 2. Create a PowerShell (Diagnostics.Office365.ps1) script to call the officeact.diagcab file. See example below 3. Create an SCCM Script application calling the Diagnostics.Office365.ps1 script powershell -ExecutionPolicy Bypass .\Diagnostics.Office365.ps1 Select the Detection Method tab and select radial next to "Use a custom script to detect the presence of the this deployment type". Select the Edit option on the right and set the script type to PowerShell and the script content as appropriate to the application. The script below will look at all running processes and filter out all processes that equal msdt; if a process matching this string is found the client will return an exit code of 0 ...

SYMPTOM : ====================================================================================== MP Control Manager detected management point is not responding to HTTP requests.  The HTTP status code and text is 403. ====================================================================================== CAUSE : ====================================================================================== Client certificate revocation was enabled. ====================================================================================== RESOLUTION : ====================================================================================== In order to resolve the issue We followed a series of steps. 1. Checked the Virtual directories of the management Point. 2. We were getting Error 403.2, 500.19, 403.14 while browsing the SMS_MP virtual directory. 3. We corrected the error 403.2, by enabling the READ permission on HANDLER MAPPINGS. To correct the Error 500.19, we added authenticated users and giv...

SYMPTOM : ====================================================================================== MP Control Manager detected management point is not responding to HTTP requests.  The HTTP status code and text is 403. ====================================================================================== CAUSE : ====================================================================================== Client certificate revocation was enabled. ====================================================================================== RESOLUTION : ====================================================================================== In order to resolve the issue We followed a series of steps. 1. Checked the Virtual directories of the management Point. 2. We were getting Error 403.2, 500.19, 403.14 while browsing the SMS_MP virtual directory. 3. We corrected the error 403.2, by enabling the READ permission on HANDLER MAPPINGS. To correct the Error 500.19, we added authentica...

ConfigMgr 2012 Service Pack Upgrade (SCCM 2012 R2 SP1 upgrade) I was performing the initial Test Database command from the SMSSETUP\BIN\X64 directory of the installation media run the following command: (Setup.exe /testdbupgrade <database_name> ) Once the Pre-requistite check runs it references 'Unsupported ConfigMgr database version' and log states 'Failed to connect to SQL Server to verify site version'. If you search else where you may think this is a permissions based issue (definately check) but in my case this was not the case and i knew the database was supported. ===== INFO: Prerequisite Type & Server: SQL: ===== <<<RuleCategory: Database Upgrade Requirements>>> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>> INFO: CheckTestDBVersion start ... ERROR: Failed to connect to SQL Server to verify site version. Unsupported ConfigMgr database version;    Error;    For the site database u...

ConfigMgr 2012 Service Pack Upgrade (SCCM 2012 R2 SP1 upgrade) I was performing the initial Test Database command from the SMSSETUP\BIN\X64 directory of the installation media run the following command: (Setup.exe /testdbupgrade <database_name> ) Once the Pre-requistite check runs it references 'Unsupported ConfigMgr database version' and log states 'Failed to connect to SQL Server to verify site version'. If you search else where you may think this is a permissions based issue (definately check) but in my case this was not the case and i knew the database was supported. ===== INFO: Prerequisite Type & Server: SQL: ===== <<<RuleCategory: Database Upgrade Requirements>>> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>> INFO: CheckTestDBVersion start ... ERROR: Failed to connect to SQL Server to verify site version. Unsupported ConfigMgr database version;    Error;    For the ...