Jump to content




anyweb

Root Admin
  • Content Count

    7,729
  • Joined

  • Last visited

  • Days Won

    285

anyweb last won the day on September 3

anyweb had the most liked content!

Community Reputation

424 Excellent

About anyweb

  • Rank
    Administrator
  • Birthday 11/24/1966

Contact Methods

  • Website URL
    http://www.niallbrady.com

Profile Information

  • Gender
    Male
  • Location
    Sweden
  • Interests
    Modern management of devices with Microsoft Intune and System Center Configuration Manager

Recent Profile Visitors

4,135,497 profile views
  1. thanks, this guide is about installing the current baseline (1802 at time of writing) not upgrading, but sure, upgrade away 🙂
  2. thanks ! you cannot add that account because that account is already a predefined Local Administrator,
  3. open either of the 2 files (stored in C:\Windows\Inf) with notepad, and see what the driver actually is, that should help you pinpoint the problem
  4. good point, @PaulWhite@pickens.k12 can you please share the configmgrprereq.log which detailed that your dp server OS was the issue please ? feel free to redact it
  5. you'll need to create a custom script to detect where that original system is installed, and use that for the apply operating system step (using a variable), but read my first comment in this thread....
  6. ah great to hear it, thanks for the update
  7. have you made sure to distribute both 32 bit and 64 bit architecture boot images to your pxe enabled distribution point what does the smspxe.log reveal ?
  8. did you browse to the link mentioned to see why ? and what does the Configmgrprereq.log say in the root of C:\
  9. you are welcome, it was one of the more difficult thing I've gotten around to blogging, and I did it to understand the process better myself and to teach others, I've done the lab 3 times already and I know it works :-), if you follow the next in the series you can also configure SCCM with HTTPS, links below How can I configure System Center Configuration Manager in HTTPS mode (PKI) - Part 1 How can I configure System Center Configuration Manager in HTTPS mode (PKI) - Part 2
  10. did Microsoft CSS explain why they thought your SQL was in such a bad state ?
  11. thanks for posting the solution, your SQL server configuration was well messed up though.
  12. you still have these issues, and until they are fixed there's no point trying to upgrade CONFIGURATION_MANAGER_UPDATE service is starting... $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.024+240><thread=2868 (0xB34)> Microsoft System Center Configuration Manager v5.00 (Build 8540) $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.024+240><thread=2868 (0xB34)> Process ID: 2844 $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.024+240><thread=2868 (0xB34)> Worker thread ID: 2868 $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.024+240><thread=2868 (0xB34)> Inbox source is local on abc.com $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.024+240><thread=2868 (0xB34)> Set inbox to C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.024+240><thread=2868 (0xB34)> This running on active site server abc.com. $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.024+240><thread=2868 (0xB34)> Inbox source is local on abc.com $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.040+240><thread=2868 (0xB34)> *** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'. $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.165+240><thread=2868 (0xB34)> *** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_MDC" requested by the login. The login failed. $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.165+240><thread=2868 (0xB34)> *** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'. $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.181+240><thread=2868 (0xB34)> *** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_MDC" requested by the login. The login failed. $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.181+240><thread=2868 (0xB34)> *** Failed to connect to the SQL Server, connection type: SMS ACCESS. $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.181+240><thread=2868 (0xB34)> ExecuteSqlCMUpdateInitScripts: Can't get SQL connection $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.181+240><thread=2868 (0xB34)> *** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'. $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.196+240><thread=2868 (0xB34)> *** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_MDC" requested by the login. The login failed. $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.196+240><thread=2868 (0xB34)> *** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'. $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.196+240><thread=2868 (0xB34)> *** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_MDC" requested by the login. The login failed. $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.196+240><thread=2868 (0xB34)> *** Failed to connect to the SQL Server, connection type: SMS ACCESS. $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.196+240><thread=2868 (0xB34)> ERROR: Can not get InstallationType from SetupInfo $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.196+240><thread=2868 (0xB34)> Failed to initialize.
×