nerdexam
Microsoft

70-243 · Question #175

Your network contains a System Center 2012 R2 Configuration Manager Service Pack 1 (SP1) environment. The environment contains a primary site server named Server1 and a server named Server2 that…

The correct answer is A. Register the Service Principal Name (SPN) for the SQL Server service account of Server3. From. Restoring a ConfigMgr database to a new SQL Server requires registering the SPN for proper Kerberos authentication and then running ConfigMgr Setup to perform site recovery.

troubleshooting

Question

Your network contains a System Center 2012 R2 Configuration Manager Service Pack 1 (SP1) environment. The environment contains a primary site server named Server1 and a server named Server2 that runs Microsoft SQL Server 2012. Server2 contains the Configuration Manager database. Server2 fails. You install SQL Server 2012 on a new server. You name the server Server3. You need to restore the Configuration Manager database to Server3. What should you do?

Options

  • ARegister the Service Principal Name (SPN) for the SQL Server service account of Server3. From
  • BFrom Server3, run Microsoft SQL Server Managements Studio, and then restore the backed up
  • CRegister the Service Principal Name (SPN) for the SQL Server Service account of Server3. From
  • DFrom Server3, run Microsoft SQL Server Management Studio, and then attach the backed up SQL

How the community answered

(24 responses)
  • A
    46% (11)
  • B
    17% (4)
  • C
    29% (7)
  • D
    8% (2)

Why each option

Restoring a ConfigMgr database to a new SQL Server requires registering the SPN for proper Kerberos authentication and then running ConfigMgr Setup to perform site recovery.

ARegister the Service Principal Name (SPN) for the SQL Server service account of Server3. FromCorrect

When the SQL Server moves to a new machine (Server3), the Service Principal Name must be registered for the new SQL Server service account so the site server can authenticate via Kerberos. After SPN registration, ConfigMgr Setup must be run in site recovery mode, which restores the backed-up database and updates all internal site configuration references to point to Server3 - this is the only supported full recovery path.

BFrom Server3, run Microsoft SQL Server Managements Studio, and then restore the backed up

Restoring the database through SSMS alone skips SPN registration and bypasses the ConfigMgr Setup recovery process, leaving site configuration broken and Kerberos authentication unresolvable.

CRegister the Service Principal Name (SPN) for the SQL Server Service account of Server3. From

While this option also registers the SPN, the second step it prescribes differs from the required ConfigMgr Setup site recovery mode, meaning the site configuration would not be properly updated to reference the new server.

DFrom Server3, run Microsoft SQL Server Management Studio, and then attach the backed up SQL

Attaching raw SQL database files via SSMS is not a supported ConfigMgr recovery method and omits both SPN registration and the ConfigMgr Setup recovery workflow needed to restore full site functionality.

Concept tested: ConfigMgr site database recovery to new SQL Server

Source: https://learn.microsoft.com/en-us/mem/configmgr/core/servers/manage/recover-sites

Topics

#database recovery#SQL Server restore#SPN registration#site server recovery

Community Discussion

No community discussion yet for this question.

Full 70-243 Practice