2012 Products with SCCM

[Rocket Man]

Has anyone set up SCCM 2012 SP1 beta on Sql 2012 CU3 and Server 2012 on hyper-v 2012?

 

I am beginning to think that I should have tried it on Sql 2k8R2SP1 cu6 and server 2k8r2 sp1 and hyper-v 2k8r2.

 

having some difficulty with the famous error 0x80070570 when trying to load in a TS to a couple of VMs.

 

Solution:

Blow away the VMs and create new ones and viola it works......sometime later try and deploy it to the same VMs after deleting the computer accounts from SCCM DB and making them unknown again and the same error occurrs....delete the VMs and re-create and all is good again.

 

Could this be a hyper-v 2012 problem with its virtual switches?

 

Has anyone had similar experiences?

 

Also SUP site component has a critical error on it but yet it is syncing fine and deploying ADRs also....i set up a seperate instance for the susdb in sql..it connected fine to the DB when configuring WSUS. I check the error messages on the critical site component and it says to check the WCM log and all I see in here is that it was all successful connecting to server on specific port?

[Rocket Man]

OK......just thought I would bring this thread back up.

 

With the release of SP1 RTM yesterday I set up a testing lab last night with the same set up as before SCCM 2012 SP1 RTM with Server 2012 and SQL2012 CU2 with 2 instances, one for the ConfigMgr DB and one for WSUS.

Could not believe it, the same error again as above with the 2 seperate instances. Very frustrating to say the least as both instances are setup the same way as I would set up a SCCM implementation on a single instance, using a domain account for all SQL roles etc......and after reverting my Beta lab to a single instance after the 1st error and seeing this worked great with no errors even made it more frustrating.

 

Anyway as Peter suggested it was a security issue. After digging arround in the SQLWSUS log folder I came across an ERROR log and in it was the reason:

 

2013-01-04 01:04:16.04 spid55 Failed to verify Authenticode signature on DLL 'e:\Program Files\Microsoft SQL Server\MSSQL11.WSUS\MSSQL\Binn\msxmlsql.dll'.

2013-01-04 01:04:30.95 Logon Error: 18456, Severity: 14, State: 38.

2013-01-04 01:04:30.95 Logon Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database 'SUSDB'. [CLIENT: <local machine>]

2013-01-04 02:01:31.28 Logon Error: 18456, Severity: 14, State: 38.

 

I never assigned the system account to the SQL setup so I do not know why it was complaining about this(especially when everything works great on one instance).

What I have done(not sure if it is correct but it worked), I opened up the WSUS instance via SQL server Management studio and went to security....Logins and properties of the system account, and sure enough it was not mapped to any database, so I ticked the SUSDB on the mapping node, restarted the SCCM site server and all nice green ticks now on the site components(software update point) with no errors in the WSUS components either.

 

Hopefully it may help some-one else in similar circumstances. Now I can go about setting up my new SCCM 2012 SP1RTM production site feeling comfortable!

 

Rocket Man

[anyweb]

how did you install SQL ? did you use a scripted setup like I provide in the CAS guide or did you install it manually ?

[Rocket Man]

Hi Niall it was a manual install for both instances then I installed the CU2 on top of this which successfully updated both instances.

 

Now the second instance for WSUS is it also a prereq for the collation to be SQL_LATIN1_GENERAL_CP1_CI_AS?

 

My thinking is YES as this is the collation for a single instance hosting both DBs.

 

For all SQL roles i specify a single domain account just to keep it simple. Just to add I did set this implementation up using the system account for all roles and even this had the same outcome but if I use just one instance for both DBs it has no errors and works with both the domain account credentials for all SQL Roles\service accounts and also works with the system account.

 

I also will add I have 4 seperate smaller SCCM 2012 non SP1 sites sitting on server 2K8R2 SP1 and SQL Server 2K8 Sp1 CU6 with 2 instances using domain credentials and these have no problems.

 

EDIT: it is CU3 that i am using and not CU2 as mentioned

 

Thanks