SCCM 2012 installation is adding trace flags to SQL Server

Hi,
In my day-to-day job, I'm a SQL Server DBA, so I don't have much knowledge about SCCM.
I recently noticed when SCCM 2012 is installed, that the installation procedure is going to add 2 trace flags in the startup options of SQL Server -T4199 and -T8295.
Trace flag 4199 is known and often used, however, nobody has ever heard about the other trace flag 8295.
Can somebody help me to figure out why this trace flag is added and what it is actually doing?
Regards
Pieter

Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?
This is not something that can be handle within forums. I recommend that you either contact CSS directly for support or your Microsoft TAM to get this answer.
But honestly why does it matter?
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Similar Messages

SCCM 2012 R2 configure WSUS got error remote SQL Server 2012

Hi All,
I got question ask on when i want to configure the WSUS component it failed as per screenshot and my SCCM cant work with it.
SCCM Server : Windows Server 2012 R2 (WSUS featured installed)
SCCM Version: System Center Config Manager R2
Remote SQL Server : Windows Server 2012 R2
SQL Version: SQL Server 2012 SP1 -11.0.3153
WSUS Error:
SCCM Error:
Hope you all can provide me a good solution on it I had no clue on this.
Regards,
Sam

Sam,
Recommend you
Remove SUP
Remove WSUS role
Delete the SUSDB on the remote SQL server
Reboot the server
Reinstall WSUS feature
Reinstall SUP
Take a look at my blog on installing a SUP on 2012 from the section 'Install WSUS on the remote SUP server'
http://sccmentor.wordpress.com/2014/09/11/installing-a-remote-sup-in-sccm-2012-r2-on-windows-server-2012-r2/
Make sure you run the Post Install tasks as well.
Cheers
Paul | sccmentor.wordpress.com

SCCM 2012 installation problem..prerequisite fails

Hi there,
I am trying to install SCCM 2012 on Server 2012 and its seems that the prerequisite checker fails on 3 checks, all related to SQL.
SQL Server service running account
required SQL Server Collation
SQL Server sysadmin rights
And I wonder how exactly the installation of SCCM 2012 is looking for the SQL Server?
Is it through Active directory? What if i had 4 different SQL Servers. How can he knows where to look his server?
I do not remember that i entered during the wizard any SQL Server name.
I think i am getting those errors because, the installation can't find any SQL Server.
I have 3 Virtual machines:
1. Server 2012 as DC
2. Server 2012 as SQL Server 2012 RTM with CU3
3. Server 2012 as Sccm 2012 R2 x64
Any ideas how to troubleshoot this problem?
Log file
https://onedrive.live.com/redir?resid=D99573B9FC48B9D4!266&authkey=!AId9aroJCts64AM&ithint=file%2c.log
Thank you very much
Amir

Try removing Use typical installation options for a stand-alone primary site option.
When using this option, Setup automatically configures the site as stand-alone primary site, uses a default installation path, a
local installation of the default instance of SQL
Server for the site database, a local management point, a local distribution point, and configures the site with English and the display language of the operating system on the
primary site server if it matches one of the languages that Configuration Manager supports.
http://technet.microsoft.com/en-us/library/gg712320.aspx

Moving Default Trace File in SQL Server

How can I move the default trace file in SQL server?
SQL Server 2012?
Thanks in advance
ebro

Please have a look at these links:
Change path for default SQL Server trace
Steps to change the default location of SQL Server /SQL Server Agent - Error log files
DETERMINING DEFAULT TRACE LOCATION
Collecting the Information in the Default Trace
T-SQL Articles
T-SQL e-book by TechNet Wiki Community
T-SQL blog

Are there any differences between Server 2012 and Server 2012 R2 that might impact TFS or SQL server required for TFS?

Hi,
In the interest of just getting started and learning the basics of setting up TFS, I previously setup an IDE using a large workstation running Windows 8. I set up the required servers for TFS using VM's through Hyper-V. I am now transferring
everything to a new and separate physical server.
My question stems from a problem I had when I originally setup the TFS system the 1st time. I couldn't get SQL server to work using the Server 2012 R2 download from the subscription center. When I used Server 2012, it worked, so I proceeded that
way just to get going.
So now I'm setting things up anew on a new physical box, I want to ask up front, is there some difference in the R2 version that causes problems with either TFS or SQL server, or was there likely some oversight on my part when I did things the 1st time?
As an addendum to my question, I always assumed R2 merely means the Server software has progressed to a refined state and is ready for wide distribution and easy setup. I assumed that there are no differences between the Standard version and the R2
version. Is that understanding correct?
Thanks.

Hi Daniel,
Thanks for your response. That's a great link. I don't recall seeing a page that is so clear and easy to read back when I was doing this the 1st time, but I probably just missed it. That helps.
I am/was using TFS2013 and VS2013. As I recall, my problem was getting SQL Server to work, but I thought asking this question on this forum was wiser because I figured everyone using TFS would be well familiar with these issues.
At any rate, it seems as though TFS2013 is fine with Server 2012 standard or R2.
I was using SQL Server 2012, and it also seems as though it works on R2:
https://msdn.microsoft.com/en-us/library/ms143506(v=sql.110).aspx
Anyway, thanks for your support. I'll be trying this again and we'll see.

SQL Server 2012 unable to update cumulative update for sql server 2012

Here is the version
Microsoft SQL server 2012 11.02.2100.60X64
Trying to install the update to install sccm2012
Error
There are no SQL server instance or shared feature that can be update on this computer.

Hello,
You need CU2 for SQL Server 2012 RTM or later to be able to install SSCM 2012. You can install SP1 for SQL Server 2012 too.
CU2 can be downloaded from the following link:
http://support.microsoft.com/kb/2703275/en-us
When you click on the “Hotfix Download Available” button, make sure you make a click on the “"Show hotfixes for all platforms and languages
(8) " link, then download and install the following file:
SQLServer2012_RTM_CU2_2703275_11_0_2325_x64
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SCCM 2012 Installation Directory Registry Key chaning automatically to Old Installation Path

Hi Guys,
I have recently recovered SCCM 2012 SP1 CAS Site from Primary Site by reinstalling CAS site and database was replicating with Primary sites properly after CAS recovery. But we noticed that after approx. 2 hours of CAS site recovery database replication stopped.
After long digging into SCCM log files we found that SCCM installation directory was pointing to old CAS Site Installation Directory (Which was before recovery) instead of NEW Installation Directory so we changed SCCM CAS Site Installation Directory manually
to new installation path in below registry key and everything was running fine again on CAS Site.
HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Identification
But again when we restarted SMS_EXEUTIVE Service, SCCM Installation Directory again changed to old installation patch under above registry location and all is bad again. We are unable to figure out what is causing this and even we formatted our HDD before
installation CAS Site.
Can anyone please help to get rid of this issue. Our while CAS site is down due to this issue.
Thanks.

I think that you have to use the same installation directory in a site recovery scenario.
Torsten Meringer | http://www.mssccmfaq.de

SCCM 2012 Installation guide.

Hello Admin Team,
I am glad to install SCCM2012 in my organization, but i dont know how to implement.
can you please guide me how to install,requirement,configure for the same.
Thanks in advance for your support.
Bhautik Shah | MCTS.

while you are at it, do see the following guides which cover many aspects of this huge product including
standalone Primary
Hierarchy with CAS
Modern (Mobile) device management
http://www.windows-noob.com/forums/index.php?/topic/4045-system-center-2012-configuration-manager-guides/
however as Torsten has already stated, there are many factors that need to be taken into account to produce a working Configuration Manager 2012 installation, and the guides linked to provide one way of setting things up in a lab environment, you should
always consider the benefit of hiring a good Configuration Manager consultant, there are many that are active on these forums and their experience is invaluable.
cheers
niall
Step by Step Configuration Manager Guides >
2012 Guides |
2007 Guides | I'm on Twitter > ncbrady

SCCM 2012 - Installation

Hi,
I get the below error once i reach database information "requested registry access is not allowed ".
1. SQL connectivity is fine
2. ODBC connection successful
3. Remote registry enabled on the SQL machine
4. Able to telnet 1433 to SQL server
5. Installation account has local and sysadmin access on SQL server
Is ter anything i need to verify BUt only thing is unable to telnet 4022 (Will this be an issue)
Regards, Pratap

In my opinion this is caused by some kind of problem on the remote SQL server. It is telling you that you haven't enough permissions on a specific registry key on that server.
If you have already added the computer account and install account to local admin and sysadmin that would suggest to me that something is wrong. You need to identify the registry key with the problem.
Use Process Monitor on the SQL server and run the setup again. Then look for an "Access Denied" error to identify the key. You may have to manually give permissions to that key.
Download ProcMon here
http://technet.microsoft.com/en-ie/sysinternals/bb896645.aspx
Is it strictly necessary to use this remote SQL? At this stage why don't you install SQL locally. Trust me, it will be easier for you now and later.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Database instance for SCCM 2012 and WSUS on a single primary site server

I am going to install SCCM 2012 and its SQL database on a single physical server. This is going to be a single primary site server. The default SQL instance will be dedicated to SCCM 2012 with no other named instances to be added on the SQL server down
the road.
During the WSUS server role installation, there is the Database Options page asking for using (1) Windows Internal Database, (2) existing db server on this computer, or (3) an external db server.
Since SCCM 2012 doesn't share db instance with others, how should I handle the WSUS db that's going to be hosted on the same SCCM/SQL physical server? Do I really need to create a separate SQL instance just for the WSUS db?
Thanks and regards.

Even though you can do it, it is the best practice to have SCCM 2012 and WSUS installed on separate instances.
http://technet.microsoft.com/en-us/library/hh692394
When the Configuration Manager and WSUS databases use the same SQL Server and share the same instance of SQL Server, you cannot easily determine the resource usage between the two applications. When you use a different SQL Server instance
for Configuration Manager and WSUS, it is easier to troubleshoot and diagnose resource usage issues that might occur for each application.

Cannot publish Flash Updates Verification of file signature failed for file SCUP 2011, SCCM 2012 R2 and WSUS all on same Windows Server 2012 machine

I am attempting to distribute Adobe Flash updates using SCUP 2011, SCCM 2012 R2, WSUS ver4 and Windows Server 2012. Everything installs without error. I have acquired a certificate for SCUP signing from the internal Enterprise CA. I have
verified the signing certificate has a 1024 bit key. I have imported the certificate into the server's Trusted Publishers and Trusted Root CA stores for the computer. When I attempt to publish a Flash update with Full content I receive the following
error:
2015-02-13 23:00:48.724 UTC Error Scup2011.21 Publisher.PublishPackage PublishPackage(): Operation Failed with Error: Verification of file signature failed for file:
\\SCCM\UpdateServicesPackages\a2aa8ca4-3b96-4ad2-a508-67a6acbd78a4\3f82680a-9028-4048-ba53-85a4b4acfa12_1.cab
I have redone the certificates three times with no luck. I can import metadata, but any attempt to download content results in the verification error.
TIA

Hi Joyce,
This is embarrassing, I used that very post as my guide when deploying my certificate templates, but failed to change the bit length to 2048. Thank you for being my second set of eyes.
I changed my certificate key bit length to 2048, deleted the old cert from all certificate stores, acquired the a new signing cert, verified the key length was 2048, exported the new cert to pfx and cer files, imported into my Trusted publishers
and Trusted Root Authorities stores, reconfigured SCUP to use the new pfx file, rebooted the server and attempted to re-publish the updates with the following results:
2015-02-16 13:35:44.006 UTC Error Scup2011.4 Publisher.PublishPackage PublishPackage(): Operation Failed with Error: Verification of file signature failed for file:
\\SCCM\UpdateServicesPackages\a2aa8ca4-3b96-4ad2-a508-67a6acbd78a4\3f82680a-9028-4048-ba53-85a4b4acfa12_1.cab.
Is there a chance this content was already created and signed with the old cert, so installing the new cert has no effect? In ConfigMgr software updates I see 4 Flash updates, all marked Metadata Only (because they were originally published as "Automatic."
No Flash updates in the ConfigMgr console are marked as downloaded. I can't find any documentation on how the process of using SCUP for downloading content for an update marked Metadata Only actually works.
Comments and suggestions welcome.

SCCM 2012 R2 Install - Reporting Services Point, Remote SRS Server

Hi all,
Here's a brief run down of the setup so far. SCCM 2012 R2 installed on Windows 2012 R2 (SCCM01). SQL 2012 back end is off box, on a separate cluster (SQL01C01). Reporting Services for SQL 2012 is due to be installed on a different server (SRS01).
My question is, when I come to sort out Reporting Services in SCCM, will I simply need to add SRS01 into SCCM as a Site System Server and install the Reporting Services Point onto SRS01?
I realise I could simply wait for the sql guys to sort the install of SRS and then test it myself but it might be a while before that gets done so I thought I'd ask....Thanks for the help

will I simply need to add SRS01 into SCCM as a Site System Server and install the Reporting Services Point onto SRS01?
Correct, although the other way around. Remember you have to make SCCM01$ a local administrator on SRS01.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

SCCM 2012 deploy windows 7: how to manage network/server load?

Hi,
Hypotetically, if you would deploy Windows 7 to hundreds of pc’s at once, how could you manage that, regarding organizing the deploy, regarding network/server load? F.e. you deploy to a collection which has 500 pc’s, users can select when
to load the OS (Windows XP, we deploy the SCCM 2012 client, they can choose when to install)
*How can you be sure network is not overloaded?
*Can you limit in SCCM 2012 bandwith usage?
Please advise.
J.
Jan Hoedt

You need to be as local as possible. You can host a deployment point role on a client OS such as windows 7 so you could temporarily setup one machine hosting OS images and then rebuild it last as well.
On a 100MB LAN with DP's hosted in a datacenter (not on subnet) we get to about 75 machines building at once before we see TFTP timeouts on PXE booting due to load on the local network. I would get your build as quick as possible and then do them in increasing
block sizes whilst monitoring the network and server load.
To speed up builds you could...
Build and capture to get a WIM file with most apps and updates in it.
Change the TFTPBlockSize registry settings on the DP's (If PXE booting) to as high as it will go
Host WIM files on your DP's with the Package share settings configured and enable the "Access content directly..." option in the Apply Operating System part of your task sequence.
Hope this helps.
Shaun

SCCM 2012 PXE setup error PXE-E7B - Missing MTFTP Server IP Address

Have just configured PXE on our new SCCM 2012 server. Seems like it should be simple to setup. 66/67 options are setup as is IPhelper.
When PXE booting a client it hangs at the DHCP prompt and then throws the following error:
PXE-E7B - Missing MTFTP Server IP Address
Any ideas what the problem might be?
Thanks

PXE is enabled on DP and WDS service running fine. There are both 32 and 64 PXE enabled boot images uploaded on DP. When trying to PXE boot a VM on the same subnet as the SCCM 2012 server you see entries in the smspxe.log. The PXE doesn't
work because there's no DHCP scope available, but you can see PXE reacting and it throws a different error PXE-E52: No DHCP offers were received. When you try PXE booting on a different subnet nothing appears in smspxe.log, as you say it's like it's
not seeing the PXE traffic at all.
Network guys have confirmed IP helper setup for old and new SCCM servers. Discard, echo, and 4001 access allowed.

Why SCCM 20012 Install fails with remote 64 bit SQL Server but proceeds for remote 32 bit SQL Server

I have the following setup:
AD User accounts
- SQLAdmin (used to run SQL Services i.e. Database Engine)
- SCCMADmin (used to install SCCM 2012)
SPN registered for user account SQLAdmin
setspn -S MSSQLSvc/SQL.Domain_Name:1432 Domain_Naem\SQLAdmin
setspn -S MSSQLSvc/SQL:1432 Domain_Name\SQLAdmin
setspn -S MSSQLSvc/SQL.Domain_Name:1433 Domain_Naem\SQLAdmin
setspn -S MSSQLSvc/SQL:1433 Domain_Name\SQLAdmin
and checked with setspn -L TESTING\SQLAdmin
1 SERVER called SQL
32bit Server with SQL Server 2008 + SP3 + Cumulative Update 6
2 SQL instances - Default (MSSQLSERVER) and
SCCM2012
MSSQLSERVER instance uses TCP port 1433
SCCM2012 Instance users TCP port 1432 (no dynamic ports)
User accounts that have been given public and sysadmin SQL server roles
on both instances are: SQLAdmin, SCCMAdmin, Domain Administrator, Local Administrator and computer account SCCM
Client Protocols TCP enabled (and Named Pipes) (checked via SQL Server Configuration Manager)
Local Administrators Group on this server has members - SQLAdmin, SCCMAdmin, Domain Administrator, Local Administrator and computer account SCCM
Firewall turned on with access allowed on Ports 1432, 1433, 4022,445, and WMI - WMI-in, DCOM-in and ASync-iN builtin rules allowed\enabled.
1 SERVER called SQL3
64bit Server with SQL Server 2008 + SP3 + Cumulative Update 6
2 SQL instances - Default (MSSQLSERVER) and
SCCM2012
MSSQLSERVER instance uses TCP port 1433
SCCM2012 Instance users TCP port 1432 (no dymanic ports)
User accounts that have been given public and sysafmin SQL server roles on both instances are:
SQLAdmin, SCCMAdmin, Domain Administrator, Local Administrator and computer account SCCM
Client Protocols TCP enabled (and Named Pipes) (checked via SQL Server Configuration Manager)
Local Administrators Group on this server has members - SQLAdmin, SCCMAdmin, Domain Administrator, Local Administrator and computer account SCCM
Firewall turned off
1 SERVER called SCCM
64bit Server that is to be the Primary Site Server\MP for SCCM 2012
ODBC link to SQL\SCCM2012,1432
ODBC link to SQL3\SCCM2012,1432
ODBC uses SQL Native Client 10.0 (64 bit)
Both ODBC connections when TESTed pass and suggest connectivity to SQL Servers
Install process doe SCCM2012
Tried to install SCCM 2012 RC2 when logged in to SCCM Server as AD user account
SCCMAdmin, and when utilising the SCCM2012 SQL instance on
32 bit server of SQL install proceeds barring warning about 8GB rec, for SQL Server. Then fails on PKI certificate issue. Installation (chose HTTP for MP). I beleive the PKI failure as install starts is
due to the fact that SCCM 2012 needs its database server to b 64 bit ?
Thus i then tried to install SCCM 2012 RC2 when logged in to SCCM Server as AD user account SCCMAdmin, and
when using the SCCM2012 SQL instance on
64 bit server of SQL install proceeds but fails at checking stage and says:
SQL Server sysadmin rights FAILED SQL3.Domain_Name
Either the user account running Configuration Manager Setup does not have sysadmin SQL Server role permissions on the SQL Server instance selected for site database installation, or the SQL Server instance could not be contacted to verify permissions. Setup
cannot continue.
and
Site System to SQL Server communication WARNING SCCM.Domain_Name
A communication error has been detected between the specified site system and the site database computer. This error can occur when the site database server is offline or if a valid SPN has not been registered in Active Directory Domain Services for the SQL
Server instance hosting the site database. Setup cannot continue.
Why does the install of SCCM 2012 with 32 bit SQL proceed further than the install with 64 bit SQL, with the latter process failing as above error meesages show and yet both servers are set identically (apart from temporary turning off Firewall on the 64
bit server) and during the install the Databse Server specified is accepted ?

Thanks for the reply.
I can connect via ODBC to the the 32 bit SQL Server and the 64 bit SQL Server from the SCCM Server
The SQL Server Unit called SQL3 unit is a 64 bit SQL.
The SQL Server Unit called SQL is only 32 bit, but at least gets past the final checking stage and the error messages about sysadmin rights and Site System to SQL Server communication problem, and then fails with PKI certificate error message.
When trying to install SCCM specifying the 64 bit SQL Server as the Database Server it gives the 2 error messages at the final checking stage of the installation as listed.
So as I said what is confusing is the fact that if the SCCM install uses the remote 32 bit SQL Server it passes the final checking (although fails with PKI certificate message) but the 64 bit SQL Server set up exactly the same apart from the Firewall being
left off for the time being, fails at the final check stage with the 2 listed errors.
If I use a local 64 bit SQL Server the installation is fine.
Still would like to find out what cause the 2 issues for the remote 64 bit SQL Server, when ODBC seems fine, sysadmin rights have been given for the installer account and the SCCM computer account and SPNs have been set for the user account running the SQL
Services.

SCCM 2012 installation is adding trace flags to SQL Server

Similar Messages

Maybe you are looking for