Uninstalling SQL server 2012 in SCCM 2012

I am facing issues while uninstalling MS SQL server 2012 throw SCCM 2012.Since it is a exe installation settings msi has been targeted to create package. There is no error in SCCM log since Uninstall.cmd completely removes the settings msi. But SQL server remains
in the system.
Contents of Uninstall.cmd is
"%Programfiles%\Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012\setup.exe" /QUIET /ACTION=Uninstall /IACCEPTSQLSERVERLICENSETERMS /FEATURES="SQLENGINE,REPLICATION,FULLTEXT,DQ,AS,RS,DQC,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,DREPLAY_CTLR,DREPLAY_CLT,SNAC_SDK"
MsiExec /X {DA388E40-A359-4345-9184-01ED96928FB6} /qn
MSIEXEC /x {D411E9C9-CE62-4DBF-9D92-4CB22B750ED5} /qn
MSIEXEC /x {83F2B8F4-5CF3-4BE9-9772-9543EAE4AC5F} /qn
MSIEXEC /x {C3F6F200-6D7B-4879-B9EE-700C0CE1FCDA} /qn
MsiExec /X {8F3AB164-B4F3-45B1-A85A-F5E5815A44E1} /qn
MsiExec /X {FA0A244E-F3C2-4589-B42A-3D522DE79A42} /qn
MsiExec /X {DA1C1761-5F4F-4332-AB9D-29EDF3F8EA0A} /qn
MSIEXEC /x {CC8B009A-98C9-497F-99AF-CEBE35D8C0CF} /qn
MsiExec /X {9169C939-ED01-446A-BD0C-29873BAF4E48} /qn
Msiexec /X {DA388E40-A359-4345-9184-01ED96928FB6} /qn (Settings MSI)
its working fine with pstools. but not thro SCCM 2012.
Any suggestions ?

The only unique thing about running things in ConfigMgr is that it uses the local System account. Other than that, ConfigMgr simply runs what you tell it to run so if it's not meeting your expectations, then what you are telling it to run is what needs to
be troubleshot.
You should add logging to the msiexec commands and should review the event logs. Beyond that though, this is specific to SQL Server uninstallation and thus for support on troubleshooting SQL Server uninstallation, you should post in a SQL Server forum.
I know that doesn't explicitly help, but the problem doesn't lie with ConfigMgr so there's not much more to say. You could try running this using a task sequence though with a single run command-line task that specifies alternate credentials to avoid running
it as local System.
Jason | http://blog.configmgrftw.com

Similar Messages

Unable to uninstall sql server 2012 from Windows 7(ultimate) 64-bit SP1 version.

I am trying to install sql sever 2012 on my m/c but it's giving me error after partial installation.
Now I have successfully installed Sql Server 2008 R2 on my machine but when I am trying to uninstall 2012 sql server from my machine its giving an error regarding unsupported OS. However as mentioned earlier I have Windows 2007 Ultimate SP1 (64-bit) installed
on my machine which is included in valid platform for sql server 2012. Also I installed visual studio 2013 on my machine but it existed with error SqlServer\LocalDB not installed.

Hi pritamk,
According to your error message, as other post, you can uninstall SQL Server from command line, inaddition, another workaround is that change the compatibility mode of setup.exe to Vista SP2, then run “Remove” option from the control panel. You can refer
to the following steps.
Browse to your SQL setup bootstrap folder, For SQL Server 2012, this is the path "C:\Program Files \Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012\".
Go to Setup.exe file and right click on Setup.exe. Then go to properties and click on "Compatibility" tab. Under "Compatibility mode", click on Run this program in compatibility mode for "Windows Vista (Service Pack 2)". Then Click on "Apply" then "OK".
After that go to control panel -> Programs and Features -> and remove SQL Server 2012
There is similar issue about uninstalling SQL Server 2012 RC0 from control panel. You can review the following post.
https://connect.microsoft.com/SQLServer/feedback/details/707706/unable-to-uninstall-sql-server-2012-rc0-from-control-panel
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Cannot uninstall sql server 2012 on Windows 7

This is the error a co-worker gets when trying to uninstall SQL Server 2012. She is running Windows 7 Professional
Service Pack 1, 64 bit OS. She had SQL 2008 installed and then installed 2012 Enterprise as well, because she needed it for a project. The problem is we don't have a license for local instances of Enterprise, so we need to install it. However,
2012 Setup is telling us we don't have the minimum requirements to *install* 2012. Which leads to some interesting questions:
1) Why does the 2012 installer allow you to install but not uninstall when you don't meet system requirements?
2) How does that make any sense?
3) Does she really need to install more software to be able to uninstall? Since SP1 is already installed, what would that be?
Thanks!
Joe

Hello,
In theory, if Windows 7 has SP1 then it is compatible with SQL Server 2012.
Please try to use the procedure explained on the following article:
http://msdn.microsoft.com/en-us/library/ms143412.aspx
If that article does not help, please perform the following steps to manually uninstall SQL Server 2012:
1. Uninstall all SQL Server 2012 components you can using Control Panel -> Programs and Features
2. Backup the registry.
3. Delete the following keys in regedit:
--HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
--HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
4. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and delete all the sub-keys referencing SQL Server.
5. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services and delete all the keys referencing SQL Server.
6. Rename all the SQL Server folders in the computer like
C:\Program Files\Microsoft SQL Server and subfolders.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Uninstall SQL Server 2008 Express R2 and SQL Server 2012 unsuccessfully

HI
I want to uninstall SQL Server 2008 R2 and SQL Server 2012 but it was successful.
When I try to uninstall 2008 R2
It shows the sqlsupport.msi can't find
Warning 26003. Microsoft Server 2008 R2 Setup Support Files cannot be uninstalled because the following products are installed:
SQL Server 2008 R2 SP2 Common Files are installed
SQL Server 2008 R2 Dabtabase Engine Shared
Microsfot SQL Server R2 RsFx Driver
SQL Server 2008 R2 SP2 Database Engine Services
When I uninstall 2012, it shows the SQL Browser has been installed.
Warning 26003. Microsoft SQL sERVER 2012 Setup Support Files cannot be uninstalled because the following products are installed:
SQL Server Browser for SQL Server 2012

I tried to uninsall SQL Server 2008 R2 and SQL Server 2012.
Yes, I did what you said : right click on Microsoft SQL Server 2008 R2 and then uninstall.
System pop up window says :
Warning 26003. Microsoft SQL Server 2008 R2 Setup Support Files cannot be uninstalled because the following products are installed:
SQL Server 2008 R2 SP2 Common Files are installed
SQL Server 2008 R2 Dabtabase Engine Shared
Microsfot SQL Server R2 RsFx Driver
SQL Server 2008 R2 SP2 Database Engine Services
I hope you are uninstalling from Add remove program. Can you first uninstall
SQL Server 2008 R2 SP2 Common Files are installed
SQL Server 2008 R2 Dabtabase Engine Shared
Microsfot SQL Server R2 RsFx Driver
SQL Server 2008 R2 SP2 Database Engine Services
And then uninstall the
Microsoft SQL Server 2008 R2
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Uninstall SQL Server 2012 in Command Prompt

I need to make an uninstall script for SQL Server 2012 Express but I can't figger it out.
After I uninstalled the SQL instance with following command:
C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012\setup.exe /Action=Uninstall /FEATURES=SQL,AS /INSTANCENAME=SQLEXPRESS /QUIETSIMPLE
There are still a couple of programs that I want to remove:
Microsoft SQL Server 2008 Setup Support Files
Microsoft SQL Server 2012 Transact-SQL ScriptDom
Microsoft SQL Server 2012 Native Client
SQL Server Browser for SQL Server 2012
Microsoft VSS Writer for SQL Server 2012
Microsoft - SQL Server 2012 Express
Microsoft SQL Server 2012 Setup (English)
Can someone please help me removing them without using 'Add or Remove Programs'
and preferably without any interaction.

Hi Michael1105,
Are there any other instances except SQL Server Express in your system?
To completely uninstall SQL Server Express include the Browser, Writer and other SQL Server components, I recommend you use the
ConfigurationFile.ini file. Below is an example for you.
Firstly, you can perform the following steps to generate a configuration file.
1. Right click SQL Server 2012 from control panel and select Remove
2. Follow the wizard through to the Ready to Remove page. The path to the configuration file is specified in the
Ready to Remove page in the configuration file path section.
3. Cancel the setup without actually completing the uninstallation, to generate the INI file.
Secondly, you can specify the configuration file at the command prompt and uninstall SQL Server 2012 Express, or you can change the scripts in configuration file to meet your requirement, then copy the scripts
in command prompt to uninstall SQL Server 2012 Express.
Reference:
Install SQL Server 2012 Using a Configuration File
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Top 4 basic issues that are encountered in SCOM 2012 and SCCM 2012

HI,
I need to give a presentation on the basic issues that are encountered in SCOM 2012 and SCCm 2012.
Can anyone help me out with this?
Thanks in advance
Rohith Kumar

Hi,
I am not familiar with SCCM, so I will give some issue I encounterred in SCOM:
1. Not monitored and grey agent, here is an article for your reference:
http://technet.microsoft.com/en-us/library/hh212723.aspx
2. Failed to discover and install agents, this may caused by the action account or install account does not have proper permissions to install the agents. Some time maybe the discovery rule is not enabled.
3. Failed to import Management Pack, this may caused by references MPs are not imported to the management group, or sometime the proper referenced MPs are imported, but there may be incorrect typing in the XML file which defines the management pack.
4. Runas account and Action account fail. If you change password for action account, you may also need to change the password everywhere the account is used in SCOM. For run as account, if the account does not have enough right to run some tasks, we may
encounter errors. You may refer to the below link which take SQL mp for example:
http://blogs.technet.com/b/kevinholman/archive/2010/09/08/configuring-run-as-accounts-and-profiles-in-r2-a-sql-management-pack-example.aspx
Regards,
Yan Li
Regards, Yan Li

Steps involved in Uninstalling SQL Server service packs

Hi,
Came to know that we can uninstall sql server service packs from SQL 2008 SP1 onwards.
Question is, for suppose i have installed SQL 2008 SP3 and found problem. Now I want to uninstall SP3, what are the steps involved to uninstall a service pack? Can we also uninstall QFE, Cummulative updates and hotfix's as well?
How does sql server does the rollback or uninstall of service pack behind the scenes?
Appreciate your help.
Thank you.

Hello,
@Cheer08: When SP1 CU3 and SP1 CU4 were released we found that some SQL Server users had issues with SSIS and SSRS, when these CUs were
uninstalled we found the issues continue, and we were back to normal when we reapplied SP1 or SP1 CU2.
@Samantha: About the Resource DB, it certainly plays a factor on applying updates and upgrading process, which is explained
here. About how it is used to allow rollback of updates
in SQL Server, the Resource DB seems to be used to copy back the objects and semantics to system databases as explained in the following article.
http://extremeexperts.com/sql/yukon/resourcedatabase.aspx
@Samantha: no official documents to my knowledge, I just have a real world experience on this as I mentioned to @Cheer08.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Problem uninstalling SQL Server 2008 r2

Hi,
when trying to unistall SQL Server 2008 R2, the unistaller returns error "long path names to files on sql server installation media not applicable", and the I can`t continue the unistallation process.

There is no complete way to remove the whole setup of Sql server and you can set up Sql server 2008 R2 within a new Windows OS instead of trying to uninstall it.
Many Thanks & Best Regards, Hua Min
Totally irrelevant answer please consider and think a lot before writing such replies. You are saying one should not uninstall SQL server but instead create a new instance which IMO is totally wrong answer.
Pavel,
Can you please refer to below link for solution
Long path name not applicable
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

How to deploy Visual Studio 2012 with SCCM 2012

Hi All,
Does anyone know how can I deploy Visual Studio 2012 withc SCCM 2012(step by step).
Best regards
Nick

Hi,
It worked for me,
http://fearthemonkey.co.uk/how-to-deploy-visual-studio-2012-using-configuration-manager-2012-and-the-application-method/
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

How can I uninstall SQL Server 2012 SP2

I have installed the SQL Server 2012 RTM and then SQL Server 2012 SP2 on top. I was under the impression that the "Programs and features" would allow me to uninstall the SP2 if necessary. There, I couldn't see any SQL Server 2012 SP2 but all
the components at the 11.2.5058 level, i.e. Microsoft SQL Server 2012 Setup? So, does it mean that I have to uninstall all components on the list from 11.2.5058 levels and presume that everything will rollback to 11.2.2100...? Thanks.

I have installed the SQL Server 2012 RTM and then SQL Server 2012 SP2 on top. I was under the impression that the "Programs and features" would allow me to uninstall the SP2 if necessary.
There, I couldn't see any SQL Server 2012 SP2 but all the components at the 11.2.5058 level, i.e.
Microsoft SQL Server 2012 Setup? So, does it mean that I have to uninstall all components on the list from 11.2.5058 levels and presume that everything will rollback to 11.2.2100...? Thanks.
This is because you are looking at wrong place. Yes you need to go to add remove program but when you open that page there is no information about SP/CU updates. On top left side you need to click on
View installed updates and different screen would come there you can find SQL Server 2012 SP2
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

SQL Connection Failed for SCCM 2012 R2 (Unable to load user-specified certificate)

We've recently completed an upgrade from SCCM 2012 SP1 to 2012 R2 and have been running in the new environment for about a week. As of this morning, The consoles failed to connect to the CAS' and one of the Primary Site's database. The issue was resolved
easily enough by addressing a certificate issue in SQL, but I'm left wondering if there's a correlation between the SP1-to-R2 upgrade that would cause the cert to fail. Anyone have experience with this?
2014-01-21 22:10:11.81 Server      The server could not load the certificate it needs to initiate an SSL connection. It returned the following error: 0x8009030d. Check certificates to make sure they are valid.
2014-01-21 22:10:11.81 Server      Error: 26014, Severity: 16, State: 1.
2014-01-21 22:10:11.81 Server      Unable to load user-specified certificate [Cert Hash(sha1) "haaaaassssshhhh"]. The server will not accept a connection. You should verify that the certificate is correctly installed. See
"Configuring Certificate for Use by SSL" in Books Online.
2014-01-21 22:10:11.81 Server      Error: 17182, Severity: 16, State: 1.
2014-01-21 22:10:11.81 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
2014-01-21 22:10:11.81 Server      Error: 17182, Severity: 16, State: 1.
2014-01-21 22:10:11.81 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
2014-01-21 22:10:11.81 Server      Error: 17826, Severity: 18, State: 3.
2014-01-21 22:10:11.81 Server      Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2014-01-21 22:10:11.81 Server      Error: 17120, Severity: 16, State: 1.
2014-01-21 22:10:11.81 Server      SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

We got the same certificate related error events after a fresh install of SCCM 2012 R2 on a new server. It happened during the first reboot after SCCM was installed. In the Certificates mmc, I right-clicked on the certificate used by SQL and chose Manage
Private Keys. Giving the service account that runs the MSSQLSERVER service read rights to the private key allowed SQL to start. However, after a day or so we rebooted the server again, and SQL wouldn't start. Something had removed the service account's read
permission. Since the SCCM configuration wasn't that far along, we uninstalled SCCM. After giving the service account read rights again, and rebooting several times over a few days, and SQL started every time. We then installed SCCM 2012 R2 again, and checked
the certificate's permissions before rebooting. The service account still had read permissions when the install completed, but as soon as the server was rebooted, it lost the permissions again.
The Certificates mmc was then used to request a second computer certificate and then SQL was configured to use that new certificate via SQL Server Configuration Manager. After several days and a number of reboots the SQL services have started normally every
time so the second certificate seems to have fixed the issue. I have kept the original certificate for fear that removing it will cause whatever part of SCCM 2012 R2 that modifies the original certificate to start removing permissions from the new certificate
as well.

Upgrading SQL Server from 2008 to 2012 doesn't respect existing install / instance paths

Basic Information : Running Microsoft Windows Server 2008 with MS SQL Server 2008 (version 10.0.5869), trying to upgrade to SQL Server 2012. Currently working in a cloned
VM of our production server (so I can try things and not worry about affecting our production system).
Current server setup:
C Drive: Operating System (About 7 GB of 50 GB free)
J Drive: Program Files (About 65 GB of 78 GB free)
F Drive: SQL Databases (About 120 GB of 195 GB free)
Issue: I am trying to do an upgrade of our existing MS SQL Server 2008 install. I am using the GUI method, and choosing "Upgrade from SQL Server, 2005, SQL Server
2008, or SQL Server 2008 R2" in the Setup GUI:
All the checks & rules run with no issues. When I get to the "Instance Configuration" screen in the setup GUI, it is not respecting where my SQL Server instance is already installed (which is on the J drive). Instead it wants to install EVERYTHING
(including Instance Directory, which should be on the F drive, and the install folder, which should be on the J drive) on the C drive under C:\Program Files\ and there is no option in the GUI to change that, as it's grayed out.
I tried using a Configuration File to do the upgrade, but when I tried to specify the specific paths, it says those variables are not allowed to be used in an upgrade. If I allow the install to go through, it seems to install fine, but only leaves me with about
1.5 GB free on the OS drive (Drive C) and all of SQL Server is now installed on Drive C, which is not what I want or need.
Looking in the Registry Editor, I can see that under HKLM\SOFTWARE\Microsoft\Microsoft
SQL Server\MSQL11.MSSQLSERVER\ that the SqlProgramDir key
has changed from "F:\" to "C:\Program Files\Microsoft SQL Server\" and that the SQLPath and SQLDataRoot have
changed from "F:\MSSQL10.MSSQLSERVER\MSSQL" to "C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL". SQLBinRoot has
also been changed "F:\MSSQL10.MSSQLSERVER\MSSQL\Binn" to "C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn".
It doesn't seem to want to follow where the existing Install and Instance Directories are. Am I missing something here? I've done a decent amount of research, but can't find anything that talks about this. So I'm at a loss as to what to do from here.

I haven't touched the registry. Here is the ConfigurationFile.ini from the original install (I've scrubbed sensitive info out of it) showing the paths:
;SQLSERVER2008 Configuration File
[SQLSERVER2008]
; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will reflect the instance ID of the SQL Server instance.
INSTANCEID="MSSQLSERVER"
; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter.
ACTION="Install"
; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, and Tools. The SQL feature will install the database engine, replication, and full-text. The Tools feature will install Management Tools, Books online, Business Intelligence Development Studio, and other shared components.
FEATURES=SQLENGINE,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK,OCS
; Displays the command line parameters usage
HELP="False"
; Specifies that the detailed Setup log should be piped to the console.
INDICATEPROGRESS="False"
; Setup will not display any user interface.
QUIET="False"
; Setup will display progress only without any user interaction.
QUIETSIMPLE="False"
; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system.
X86="False"
; Specify if errors can be reported to Microsoft to improve future SQL Server releases. Specify 1 or True to enable and 0 or False to disable this feature.
ERRORREPORTING="False"
; Specify the root installation directory for native shared components.
INSTALLSHAREDDIR="J:\Program Files\Microsoft SQL Server"
; Specify the root installation directory for the WOW64 shared components.
INSTALLSHAREDWOWDIR="J:\Program Files (x86)\Microsoft SQL Server"
; Specify the installation directory.
INSTANCEDIR="F:"
; Specify that SQL Server feature usage data can be collected and sent to Microsoft. Specify 1 or True to enable and 0 or False to disable this feature.
SQMREPORTING="False"
; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the SQL Server Database Engine (SQL), Analysis Services (AS), or Reporting Services (RS).
INSTANCENAME="MSSQLSERVER"
; Agent account name
AGTSVCACCOUNT="NT AUTHORITY\SYSTEM"
; Auto-start service after installation.
AGTSVCSTARTUPTYPE="Automatic"
; Startup type for Integration Services.
ISSVCSTARTUPTYPE="Automatic"
; Account for Integration Services: Domain\User or system account.
ISSVCACCOUNT="NT AUTHORITY\SYSTEM"
; The name of the account that the Analysis Services service runs under.
ASSVCACCOUNT="NT AUTHORITY\SYSTEM"
; Controls the service startup type setting after the service has been created.
ASSVCSTARTUPTYPE="Automatic"
; The collation to be used by Analysis Services.
ASCOLLATION="Latin1_General_CI_AS"
; The location for the Analysis Services data files.
ASDATADIR="F:\MSAS10.MSSQLSERVER\OLAP\Data"
; The location for the Analysis Services log files.
ASLOGDIR="F:\MSAS10.MSSQLSERVER\OLAP\Log"
; The location for the Analysis Services backup files.
ASBACKUPDIR="F:\MSAS10.MSSQLSERVER\OLAP\Backup"
; The location for the Analysis Services temporary files.
ASTEMPDIR="F:\MSAS10.MSSQLSERVER\OLAP\Temp"
; The location for the Analysis Services configuration files.
ASCONFIGDIR="F:\MSAS10.MSSQLSERVER\OLAP\Config"
; Specifies whether or not the MSOLAP provider is allowed to run in process.
ASPROVIDERMSOLAP="1"
; Specifies the list of administrator accounts that need to be provisioned.
ASSYSADMINACCOUNTS=""
; Startup type for the SQL Server service.
SQLSVCSTARTUPTYPE="Automatic"
; Level to enable FILESTREAM feature at (0, 1, 2 or 3).
FILESTREAMLEVEL="0"
; Set to "1" to enable RANU for SQL Server Express.
ENABLERANU="False"
; Specifies a Windows collation or an SQL collation to use for the Database Engine.
SQLCOLLATION="SQL_Latin1_General_CP1_CI_AS"
; Account for SQL Server service: Domain\User or system account.
SQLSVCACCOUNT="NT AUTHORITY\SYSTEM"
; Windows account(s) to provision as SQL Server system administrators.
SQLSYSADMINACCOUNTS=""
; The default is Windows Authentication. Use "SQL" for Mixed Mode Authentication.
SECURITYMODE="SQL"
; Provision current user as a Database Engine system administrator for SQL Server 2008 Express.
ADDCURRENTUSERASSQLADMIN="False"
; Specify 0 to disable or 1 to enable the TCP/IP protocol.
TCPENABLED="1"
; Specify 0 to disable or 1 to enable the Named Pipes protocol.
NPENABLED="0"
; Startup type for Browser Service.
BROWSERSVCSTARTUPTYPE="Disabled"
; Specifies which account the report server NT service should execute under. When omitted or when the value is empty string, the default built-in account for the current operating system.
; The username part of RSSVCACCOUNT is a maximum of 20 characters long and
; The domain part of RSSVCACCOUNT is a maximum of 254 characters long.
RSSVCACCOUNT="NT AUTHORITY\SYSTEM"
; Specifies how the startup mode of the report server NT service. When
; Manual - Service startup is manual mode (default).
; Automatic - Service startup is automatic mode.
; Disabled - Service is disabled
RSSVCSTARTUPTYPE="Automatic"
; Specifies which mode report server is installed in.
; Default value: “FilesOnly”
RSINSTALLMODE="DefaultNativeMode"

SQL Service error on SCCM 2012 R2 Evaluation VHD

Hi
I've downloaded the VHD SCCM 2012 R2, but, SQL Server evaluation is out of date
http://www.microsoft.com/en-us/download/details.aspx?id=40840
I've one error "SLQ Server 2012 has expired...."
How I do now ?
Thanks at all
Scorpio92

Or you could fix this Microsoft?
This issue is at least 2 years old going back to the previous product (SCCM 2012 SP1):
https://social.technet.microsoft.com/Forums/en-US/151f6aa0-5391-4396-998f-d5d5782ed08f/system-center-2012-service-pack-1-configuration-manager-evaluation-vhd
How was this not fixed when you created the 2012 R2 VHD?
This is literally unfathomable how you could do this even once - you create a VHD for evaluation with a date specific eval of SQL? But then you imbeciles manage to do it at least a second time?
None of you at the team behind this deserve your jobs.

Required Ports to connect remote SQL named Instance for SCCM 2012 R2

Hi,
I have allowed the TCP 1433,1434,135 and 80 but still unable to connect the remote SQL named instance DB for the SCCM 2012 R2... and getting below error..can you please suggest if any other port required for the same, i have turned off the windows
firewall and RPC service is running ob Remote SQL and SCCM 2012 R2 server..
CCMsetuplog
Shailendra Dev

During the installation you need more ports. You would also need the (dynamic) RPC ports. See for a complete list (section Site Server --> SQL Server):
https://technet.microsoft.com/en-us/library/hh427328.aspx
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

SQL Editions and Migrating SCCM 2012 R2

Hey guys looking for a bit of info here...
We have an existing hierarchy of 1 CAS and 3 Primary sites, along with 13 secondary sites attached to 1 of the Primary Sites. I just learned that during the setup of these sites SQL 2012 Enterprise Evaluation Edition was used to install all the sites. Now the
Evaluation Edition on the CAS SQL server has expired... oops... Obviously I don't want to pay for Enterprise licenses if I don't need them, so I'm looking for a way to get to SQL Standard.
I have found some information about moving SCCM Sites to a new SQL server but am a bit nervous doing that from what I've read on how picky SCCM is with not changing SQL stuff. I have a guy here who is a bit of a SQL guru that feels like we should be able to
migrate to a new SQL database pretty smoothly, but I'm a tad skeptical since he doesn't know much, if anything, about SCCM.
My thought was to build a new hierarchy and use the built in migration feature of SCCM 2012 R2 to move data to the new hierarchy. Are there any caveats to the migration? Are there things that can't be transferred using a migration job? Will I have to re-install
all of our clients once we migrate?
Has anyone done this, or could anyone provide some insight on which route to pursue? I'm leaning more towards the migration since it's built into SCCM and it is meant to do that sort of thing, rather than trying to rip the SQL DB out from behind SCCM and trying
to connect it to a new instance.
Thanks in advance for any help.

Actually, your SQL guru is right. It's easy enough to do it underneath it all. Just stop all of the CM stuff before they rip and replace. Can't hurt to make sure you have a good SQL backup of your CM database on the CAS in a safe place
just before he starts, too. The main thing is to keep as much as you can in the exact same places, (although that isn't that big of deal either); but the fewer things you change the better; like tempdb or how your files for sql are laid out for your
CAS--don't move them about just because you're reinstalling SQL.
We did do that in CM07; moved from SQL ent to SQL Std because we didn't really need ent.
Worst case scenario, if CM doesn't wake up well post-reinstall, you have to run through Site Recovery / restore from your SQL backup (which you carefully remembered to take, right after shutting down SMS services but before the SQL guy started ripping out
the old eval version).
Standardize. Simplify. Automate.

Uninstalling SQL server 2012 in SCCM 2012

Similar Messages

Maybe you are looking for