SCCM woes (broke alot on update)

[gangaskan]

this has been a long battle and i hope to have this resolved soon!    

 

i installed 1802, but have been having this particular issue since i think when i migrated over to sql 2016.  when i migrated the SQL databases i restored everything from a full backup on sql, restored the  backup DB to the new server, then used the CM setup to switch SQL servers.  this was the correct action to take correct?  

bgb is not reporting properly. something with sql connection and certs  attached bgb log, sccm clients are not being shown as online (with the green marks, just either ? or X ), but i can still manage remotely, however, i dont know if policies are being enforced or software being pushed cause i have not deployed anything since this has happened.     

so a few things happened while i was diagnosing this .  did much googling and found that sql certs may not be on sccm and vise versa? see bgb server log  sql account and systemcenter server itself  has full rights to CM and the report server databases

bgb setup has no errors   

i only use HTTP on the SCCM server, i do have a ca server if its suggested we switch over to https, but as the server sits its just HTTP (there is a guide here to switch right?)  

i screwed up a bit, tried to reinstall SCCM on the primary site server thinking it would help.  it was a complete failure so i ended up restoring the OS from the last day backup, re extending the AD Schema, and making sure the MP shows up in the active directory container.  back to where i was in the first place! 

one thing i noticed is the sql server was pinging with the san address, i since changed that to not register and made sure the server nic that handles iscsi traffic is not registered in DNS.  

 

my other issue, which is my bigger issue is since the 1802 update i have huge issues deploying pc's with WDS  -- the server pushes the OS, it will join the AD Domain, but gets stuck on windows boot at some point.  possibly while deploying software?  i have yet to examine the logs on the computer.   if its a pre made WIM everything is fine. (without build and capture using DISM) 

 

 

if you need me to attach other logs that will help let me know, i noticed some pots asked for some on client side on the MS technet site.   

 

BgbServer.lo_