#Modern Workplace

I recently encountered an issue in a customer's envrionment where SQL Server Reporting service in ConfigMgr had broken down. On launching the Report Manager url and then running a report resulted in the following error. Similar errors were noticed when trying to run the reports from the ConfigMgr console. The error indicated that the issue is with the report service account credentials so that is where I started looking. It appears that the customer had updated the password of the report service account in AD, but the same was not updated in ConfigMgr. So the first thing I tried was to update the password and test the connection.  Well that was pretty easy. Atleast so I thought. The moment I clicked on Apply to commit the changes, I was presented with another error indicating an issue with the report server database. On checking further, I noticed entries in the SQL dump logs related to Transaction log being full due to SQL backup. library!ReportServer_0-1!5338!01/04/2022-23:16:38...

If you have HA setup to use SQL Server Always on availability group, then this blog may just help you. Recently, I needed to perform a Current Branch update in ConfigMgr to 2010 and as part of the preparation, I ran the pre-requisite checker. Almost immediately it threw an error pointing to Failover Availability group not being in correct state . This is a customer's environment so I was only getting to know the specifics of the configuration. That is the beauty of the pre-requisite checker in ConfigMgr, it flags up such issues and allows you to address and correct them before installing the actual update. In order to fix the issue, one needs to switch the Failover from Automatic to Manual against the Availability Group . According to Microsoft , this is needed when installing ConfigMgr updates. Also, as far as I know, this is also needed when performing any kind of site maintenance. After the change was made in SQL, I ran the pre-requisite checker again and everything passed wit...

Picking up from my last post that covered the issue involving CMG Azure cloud resources and Tags, my battle was half won in the implementation project of CMG that I was carrying out for one of my customers. After the cloud service was created and the service reported the status as ‘Connected’, the next logical step was to test and verify the connection. This is where things started to go south. On running the ‘ CMG Connection Analyzer’ against the Client Authentication Certificate, I received the following error. SMS Cloud Proxy Connector log indicated the same. In my experience, that looked like a communication issue between the connection point and the HTTPS server configured to accept CMG requests. The ConfigMgr environment has a Standalone Primary (Co-located SQL) configured to cater to HTTP requests. Cloud management gateway connection point was also configured on the same server. Another server was stood up to cater to HTTPS requests. This server would...