Hello,

im Testing Today the Upgrade to R2.

in  Step to Upgrade the Database  I become an Error xxx\Compuertname not found to add SQL Account

My Server name is xxx.de\computername an not xxx\computername (netbiosname with dot and same with DNS Name) .

Have anywhere an Idea as Workaround for me ?

What exact error message is logged in C:\ConfigMgrSetup.log?

Hello Torsten,

here now the Erro Message from the ConfigMgrSetup.log

INFO: Adding a login for ConfigMgr Site Server: IF NOT EXISTS (select * from master.sys.server_principals where name=N'mydomain\sccm$') CREATE LOGIN [mydomain\sccm$] FROM WINDOWS  $$<Configuration Manager Setup><12-05-2013 11:28:22.765-60><thread=772 (0x304)>
*** IF NOT EXISTS (select * from master.sys.server_principals where name=N'mydomain\sccm$') CREATE LOGIN [mydomain\sccm$] FROM WINDOWS  $$<Configuration Manager Setup><12-05-2013 11:28:22.777-60><thread=772 (0x304)>
*** [42000][15401][Microsoft][SQL Server Native Client 11.0][SQL Server]Der Windows NT-Benutzer oder die -Gruppe 'mydomain\sccm$' wurde nicht gefunden. berprfen Sie den Namen.  $$<Configuration Manager Setup><12-05-2013 11:28:22.777-60><thread=772 (0x304)>
ERROR: SQL Server error: [42000][15401][Microsoft][SQL Server Native Client 11.0][SQL Server]Der Windows NT-Benutzer oder die -Gruppe 'mydomain\sccm$' wurde nicht gefunden. berprfen Sie den Namen.  $$<Configuration Manager Setup><12-05-2013 11:28:22.778-60><thread=772 (0x304)>
INFO: Executing SQL Server command: <IF NOT EXISTS (select * from master.sys.server_principals where name=N'mydomain\sccm$') CREATE LOGIN [mydomain\sccm$] FROM WINDOWS>  $$<Configuration Manager Setup><12-05-2013 11:28:22.778-60><thread=772 (0x304)>
ERROR: Failed to execute SQL Server command, error <>~  $$<Configuration Manager Setup><12-05-2013 11:28:22.778-60><thread=772 (0x304)>
~~===================== Failed Configuration Manager 2012 Server Setup - Upgrade =====================  $$<Configuration Manager Setup><12-05-2013 11:28:22.779-60><thread=772 (0x304)>
<12-05-2013 11:29:35> *****************************************************

DNS = mydomain.de

Netbiosname = mydomain.de

Was an answer ever found for this issue? I'm experiencing the same error.

No Answer,

I have open call by MS an the answer was i must rename or migrate  my Domain.

This is no Option at this time for me.

In the next time i  make a copy of my Domain and SCCM and rename this copyed Domain. Then upgrade SCCM an move back the SCCM in the org. Domain by Rejoin the Computers.

I think this is my last Change be for new Installation.   

Getting the same error here it`s missing the 2nd part of the domain name

anybody found anything?

The official answer i am getting from Microsoft is that having a period in the netbios domain name is not supported and they drop whatever is after the .

i'm doing some tests right now but i found that if the DB is local it will use the NT AUTHORITY\SYSTEM account instead of the computer account, so moving the db to the site server to do the upgrade and moving it back afterwards might be an option.

otherwise creating a bogus entry in the DB with the domain\server as a name entry might work.

Real Answer: hunt down whoever did this in the first place and remove them from the gene pool -- permanently.

Unfortunatly since this was done in the days of windows NT and maybe even before that, there is a good chance the guy is probably dead... or at least retired

in other news, doing an install from scratch of the SCCM 2012 R2 does not bring up the error, so the issue is with the way their upgrade funtion works... will keep you posted as to what they say...

Microsoft support were no help...

I found a couple work arounds:

Move the database to the site server, do the upgrade, move the database back to the database server

Hack the DB:

• create a login with a valid user account on the master DB on the SQL server
• stop the sql server
• Start SQL in single server mode
   
  From an elevated cmd (Run as administrator), access the right folder where sqlservr.exe executable is located and execute below commands. Normally you will find it at C:\Program Files\Microsoft SQL Server\MSSQL[InstanceName]\MSSQL\Binn
• C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn>sqlservr.exe -m
• start SSMS in DAC mode: start SSMS, cancel the connection to the server,click on the Database Engine Query icon (to the right of the new query button),and put admin: in front of the server name
• run the following:
• select @@servername
  GO
  use master
  GO
  sp_configure 'allow updates', 1
  GO
  reconfigure with override
  GO
• then do this:

update master.sys.server_principals set master.sys.server_principals.name = 'domain\servername$' where master.sys.server_principals.name = 'domain.com\dummyaccount'

• restart the sql server
• upgrade SCCM
• keep in mind i am currently testing this solution to make sure it doesn't cause issues

• Edited by Carl_Meilleur Tuesday, July 22, 2014 6:13 PM missing a piece
• Proposed as answer by Carl_Meilleur Tuesday, September 02, 2014 6:01 PM

Microsoft support were no help...

I found a couple work arounds:

Move the database to the site server, do the upgrade, move the database back to the database server

Hack the DB:

• create a login with a valid user account on the master DB on the SQL server
• stop the sql server
• Start SQL in single server mode
   
  From an elevated cmd (Run as administrator), access the right folder where sqlservr.exe executable is located and execute below commands. Normally you will find it at C:\Program Files\Microsoft SQL Server\MSSQL[InstanceName]\MSSQL\Binn
• C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn>sqlservr.exe -m
• start SSMS in DAC mode: start SSMS, cancel the connection to the server,click on the Database Engine Query icon (to the right of the new query button),and put admin: in front of the server name
• run the following:
• select @@servername
  GO
  use master
  GO
  sp_configure 'allow updates', 1
  GO
  reconfigure with override
  GO
• then do this:

update master.sys.server_principals set master.sys.server_principals.name = 'domain\servername$' where master.sys.server_principals.name = 'domain.com\dummyaccount'

• restart the sql server
• upgrade SCCM
• keep in mind i am currently testing this solution to make sure it doesn't cause issues

• Edited by Carl_Meilleur Tuesday, July 22, 2014 6:13 PM missing a piece
• Proposed as answer by Carl_Meilleur Tuesday, September 02, 2014 6:01 PM
• Marked as answer by henrik.b Wednesday, June 17, 2015 7:40 AM

Yes it work's for me.

Stepps: in My Case With One Primary Site Server

1. Install SQL Server on Site Server an give the System Account Permissions

2. SCCM Preinst /stopsite

3.Detach DB an Move DBs and Log Files to SCCM Site SQL

4.Attach DB

5. Perform SSCM Maintenance or Site Reset --> Modify SQL Configuration

6. Test SCCM Server after Restart.

7. When SCCM Working  I Started  to Upgrade without errors.

After Testing I move back the Database to the Remote SQL Server  by step 2-6

I have Testing this  by LAB Environment before upgrade the Production Server :

Note: I have no Information that this Way is Supported and  no Warranty

  

Did this work? Did it cause any adverse affects?

I ran into this during testing of the System Center 2012 R2 SP1 upgrade. We also have a dot in our NETBIOS name too.

Hi Carl_Meilluer,

I wonder how did you come up with that workaround

anyway I'm stuck in a harder situation right now. I started to upgrade my SCCM to SP2 and I ran into the same error!

it tries to add my SCCM computer account is the DOMAIN\SCCM$ syntax! even though I have it already with the FQDN syntax.

I'm trying to figure out from what table \ wmi \ registry... where the hell the SCCM Setup thinks it need to add this LOGIN to the master db?

for me it's almost impossible to move the DB to another server and then bring it back. isn't there something simple I can do in order to over come this issue?

INFO: Adding a login for ConfigMgr Site Server: IF NOT EXISTS (select * from master.sys.server_principals where name=N'DOMAIN\sccm1$') CREATE LOGIN [DOMAIN\sccm1$] FROM WINDOWS
INFO: Executing SQL Server command: <IF NOT EXISTS (select * from master.sys.server_principals where name=N'DOMAIN\sccm1$') CREATE LOGIN [DOMAIN\sccm1$] FROM WINDOWS>
ERROR: SQL Server error: [42000][15401][Microsoft][SQL Server Native Client 11.0][SQL Server]Windows NT user or group 'DOMAIN\sccm1$' not found. Check the name again.

Hello Tamir,

Sorry about the delay in the answer, I was off the grid for a while.

I came up with the solution after exhausting all other options. and even the path to make it work wasn't a smooth one.

once I confirmed with Microsoft that this was a "feature" of the installer, I set about to add the entry to the database. Since domain\sccm$ didn't exist I could use the management studio to create the entry automatically. And it couldn't be created manually since it's a protected field. so I did the following:

• create a login with a valid user account on the master DB on the SQL server
• stop the sql server
• Start SQL in single server mode
   
  From an elevated cmd (Run as administrator), access the right folder where sqlservr.exe executable is located and execute below commands. Normally you will find it at C:\Program Files\Microsoft SQL Server\MSSQL[InstanceName]\MSSQL\Binn
• C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn>sqlservr.exe -m
• start SSMS in DAC mode: start SSMS, cancel the connection to the server,click on the Database Engine Query icon (to the right of the new query button),and put admin: in front of the server name
• run the following:
• select @@servername
  GO
  use master
  GO
  sp_configure 'allow updates', 1
  GO
  reconfigure with override
  GO
• then do this:

update master.sys.server_principals set master.sys.server_principals.name = 'domain\servername$' where master.sys.server_principals.name = 'domain.com\dummyaccount'