I have a server which was joined to an AD Domain, then installed with SQL Server 2008 R2 and System Center Operations Manager 2012's Reporting Server on it. The same server had the Active Directory DS, CS, DNS Server, IIS Server installed.
Now someone just removed all the role from this server which includes AD DS, AD CS, IIS, DNS, all gone, what only remain is the SQL Server only. To solve the issue, I installed the IIS Server on it, however instead of installing ADDS here, I have installed it to another machine with Windows 2012 R2, the new machine has AD DS, AD CS and DNS Server.
During the System Center(SCOM) install, I created some users on the old AD for the SCOM, three users and all users on a group named OMAdmins. (where the DB is also installed). They had different permissions to SQL Server and to SCOM (SCOM Management server and console are installed on another machine, which too unfortunately losses its integration to old AD).
Now I re-created the same users, same groups, with same old password on new separate AD machine I have, and authenticated all the services with the right users on the SQL Server machine and on SCOM machine.
My issues are: I cannot take any backup of DB, I was able to login to SQL Server Management Studio using NT Authority, but when I try to do backup, it says permission denied, when I check the Security -> Logins on the Studio, I see many users are missing (those SCOM Users, the groups those user was on, some NT Authority and the SCOM computer which was also on the AD). I only see two users now BUILTIN/Administrator and sa. I tried to add new users to add those missing users from AD, but SQL server fails with error message on permission denied.
Any help to bring my server back> I was able to start the services with new AD user's authentication but it looks like it is just a forced authentication. The original authentication SQL server had is missing. I need some to help to get it back to work and so for the SCOM which is also down too. I even tried SCOM Management Server recovery, but it failed and the log says SQL connection was established but existing database is already there as error, so cannot proceed with the recovery of SCOM either. It is the SQL Server which first needs an urgent fixes or recovery.