need help with a problem related to the system center
This problem started after the September database server update. I can't access the system center interface to view reports, see devices, check updates, track device status, etc. When I try to open it, I see the attached image. Has anyone else experienced this problem and resolved it? What is the solution for this issue?
OSD Tasksequence vs. update installation
Hi Everybody, In my OSD Task Sequences for deployment of Win 10 20H2 I have steps for the installation of software updates Software Updates are deployed to the collection "All Unknown Computers" The latest cumulative update plus a few other updates for Windows 10 20H2, dotnet fx and others are containded in the Software Update Group that is deployed to "All Unknown Computers" During the mentioned TS steps all updates except the CU for Windows 10 are properly installed. The CU is completely ignored Any hints? This behaviour is not only in connection with the latest CU, I observe it for several months now. Is it a known issue or "by design"? Best Sven
SCCM/MECM Stuck at "SQL Server service running account" prereq check
The issue: I'm not getting through the Prerequisite checks for MECM. The biggest struggle is the SQL check stating: SQL Server service running account "The logon account for the SQL Server service cannot be a local user account, NT SERVICE\<sql service name> or LOCAL SERVICE. You must configure the SQL Server service to use a valid domain account, NETWORK SERVICE, or LOCAL SYSTEM." Below a screenshot: The Configuration: This is a brand new CM setup (there was no CM in the past), so I've chosen to Install the primary site as a stand-alone site. All CM Roles on a single server named CM01 Database is a Named instance in our SQL server failover cluster (running with separate Domain accounts for the DBE and SSA) My Toughts: It seems that de CM Setup wizard is trying to perform it's prereq checks assuming that SQL is locally installed, and therefore it fails on this prereq check. What I've already tried/checked: - Of course I've searched the web for solution, and as stated above this has nothing to do with the SQL server instance running with local or system credentials - Double checked if SQL is running with a Static port, and made sure SQL has the right collation - No ports are blocking by Windows Firewall (on CM01 and the SQL server) - No ports are blocked by our network firewall (Checkpoint) - Made sure port TCP:1433, 4022, 1434 and UDP:1434 are open and reachable between CM01 and SQL and vice versa. I know that it's recommended to run the SQL DB on the CM server itself for performance reasons, but in this particular case it's needed to have it installed on the SQL Server Failover cluster (a company compliancy thing) What could be the cause of this issue? I'm really stuck on this one.
