Upgrade single instance from 2008 R2 SP2 to 2012 SP1

We have a central SQL 2008 R2 server that has multiple named instances, one each for System Center Configuration Manager 2012 R2, System Center Operations Manager 2012 R2, Virtual Machine Manager 2012 R2, App Controller and one for CRM 2013 SP1.
Can we easily upgrade just the CRM instance to 2012 SP1? Any suggestions how to approach this.

I feel it's a risk taking process because there is lot of dependency and complexity in your current setup. Some of the shared components will also get upgraded and rollback process is going to be harder enough to bring back the old setup. I would not
recommend you to go with In-place upgrade.
You can try side by side Upgrade strategy:- Move the CRM instance to a different instance.
Upgrading CRM is not straight forward. It has dependency and you require to modify few registry keys and requires lot of changes to be done to the configuration at the app Server.
I'll recommend you to go through the support and upgrade document of CRM.
--Prashanth

Similar Messages

WSUS wants our SQL server (running 2008 R2 SP2) to install SP1. Why?

We just installed a bunch of Windows Updates on our servers (that were pushed out from WSUS). One of the updates -- SQL Server 2008 R2
SP1 -- failed to install on our SQL server. But that's because it already had
SP2 installed. I ran a Discovery Report, and all of our SQL Server 2008 R2 components are at SP2. And yet, WSUS wants this server to install SP1.
Any suggestions as to why? I'd rather not re-install SP2 if it's not necessary.
Thank you!
p.s. I do see the following in the Sumary.txt file produced by the Discovery Report:
Package properties:
Description:                   SQL Server Database Services 2008 R2
ProductName:                   SQL Server 2008 R2
Type:                          RTM
Version:                       10
SPLevel:                       1
Installation edition:          EVAL
What is this "EVAL" version? I don't think we ever installed an evaluation version of SQL, though I suppose that's possible

Hi,
A similar thread discussed below was caused that reporting service didn’t work properly. And the solution is to run
Sp2 setup again and just select reporting service for upgrade.
For more information please refer to:
SQL Server 2008 R2 SP2 wants to install SP1 again via WSUS
http://social.technet.microsoft.com/Forums/en-US/6e711903-7c2c-4bec-a9d8-c0b56ba0f9f8/sql-server-2008-r2-sp2-wants-to-install-sp1-again-via-wsus?forum=sqlsetupandupgrade

Upgrading SQL 2008 R2 to SQL 2012 SP1

Hi everyone,
We are testing some upgrades in a lab environment. We have upgraded to SCCM 2012 R2 and are now looking at upgrading to SQL 2012 SP1 from SQL 2008 R2. Both SCCM and SQL are on one server. (The next step is to split SCCM and SQL but that's another topic)
The question we are asking is, what should be our process for the upgrade? Do we need to stop SCCM services before doing the SQL upgrade? If, so, which ones?

Hi,
You need to stop all Configuration Manager services at the site.
For the process of the upgrade, you could check the following document.
http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigUpgradeDBSrv
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Migrate CA from 2008 R2 to Server 2012

I currently have our CA on a 2008 R2 DC and I am in the process of migrating CA to a new server that is not a DC. The computer name is not going to be the same and I cannot figure out what steps are needed to ensure a smooth migration to the new CA dedicated
server.
I have been reviewing a TechNet article but it fails to discuss new computer name.
CA Migration
If anyone can guide me in the right direction I would greatly appreciate it. Thank you in advance!

See this.
Upgrading the PKI from Windows Server 2008 R2 to Windows Server 2012-Different Host Name-Part-1
http://social.technet.microsoft.com/wiki/contents/articles/21076.upgrading-the-pki-from-windows-server-2008-r2-to-windows-server-2012-different-host-name-part-1.aspx
Sl.
Steps
1
Back up the CA templates list (required only for enterprise CAs).
2
Record the CA's CSP and signature algorithm
3
Publish a CRL with an extended validity period.
4
Backing up a CA database and private key
5
Backing up CA registry settings
6
Backing up CAPolicy.inf
7
Removing the CA role service from the OLD server
8
Removing the OLD server from the domain
9
Joining the NEW server to the domain
10
Adding the CA role service to the NEW server
11
Restoring the CA database and configuration on the NEW server
12
Restoring the source CA registry settings on the NEW server
13
Restoring the certificate templates list
14
Granting permissions on AIA and CDP containers
15
Verifying certificate extensions on the NEW CA
16
Verifying certificate enrolment
17
Verifying CRL publishing
18
Retrieving certificates after a host name change
19
Roll Back if needed
Also you can Download ADCS migration white paper "AD_CS_Migration_2008_R2.pdf". Steps are same for 2008R2 to 2012.
http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=17877
Also find some Videos
http://blogs.technet.com/b/xdot509/archive/2013/04/01/upgrading-your-pki-to-windows-server-2012-part-i-video.aspx
http://blogs.technet.com/b/xdot509/archive/2013/04/01/upgrading-your-pki-to-windows-server-2012-part-ii-video.aspx
http://blogs.technet.com/b/xdot509/archive/2013/04/14/upgrading-your-pki-to-windows-server-2012-part-iii-video.aspx
Regards~Biswajit
Disclaimer: This posting is provided & with no warranties or guarantees and confers no rights.
MCP 2003,MCSA 2003, MCSA:M 2003, CCNA, MCTS, Enterprise Admin
MY BLOG
Domain Controllers inventory-Quest Powershell
Generate Report for Bulk Servers-LastBootUpTime,SerialNumber,InstallDate
Generate a Report for installed Hotfix for Bulk Servers

WSUS SP2; SCCM 2012 SP1; Sync failed: WSUS update source not found

Hi,
I have installed the Fresh SCCM 2012 SP1 and WSUS 3.0 SP2 + KB2720211 + KB2734608. However, still the Sync is getting failed. This is what I am getting in the wsyncmgr and WCM logs:
wsyncmgr:
Sync failed: WSUS update source not found on site PR1. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource
SMS_WSUS_SYNC_MANAGER 1/9/2015 12:00:00 PM
3668 (0x0E54)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=3668 GMTDATE=Fri Jan 09 18:00:00.537 2015 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found
on site PR1. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 1/9/2015 12:00:00 PM
3668 (0x0E54)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER
1/9/2015 12:00:00 PM 3668 (0x0E54)
WCM:
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER
1/9/2015 11:19:03 AM 4176 (0x1050)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Checking runtime v4.0.30319... SMS_WSUS_CONFIGURATION_MANAGER
1/9/2015 11:19:03 AM 4176 (0x1050)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Supported WSUS version not found SMS_WSUS_CONFIGURATION_MANAGER
1/9/2015 11:19:03 AM 4176 (0x1050)
STATMSG: ID=6607 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=4176 GMTDATE=Fri Jan 09 17:19:03.489 2015 ISTR0="DEF.XYZ.net" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Remote configuration failed on WSUS Server.
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=4176 GMTDATE=Fri Jan 09 17:19:03.515 2015 ISTR0="DEF.XYZ.net" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
I have used the default port numbers 80 and 443 still the sync is failing. Please provide your advise to fix this issue.
Regards,
Malwinder

WCM:
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
It's not only a matter of installing the console, but also those hotfixes on a remote server ...
Torsten Meringer | http://www.mssccmfaq.de

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"

Side effect of SQl server upgrade from 2008 R2 to Server 2012, logical name of log file changed for one database

I came to know that name has changed when I tried to shrink the file. Here is the error message I got:
Shrink failed for LogFile "Tfs_TESTTFS_Log'. (Microsoft.SqlServer.Smo)
Additonal information
An exception occured while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.COnnectionInfo)
Could not locate file 'Tfs_TESTTFS_Log' for database 'Tfs_TESTTFS' in sys.database_files. The file
either does not exist, or was dropped. (Microsoft Sql Server, Error: 8995)
This is test environment upgrade and I checked on production environment which is still on SQL 2008R2, shrink works fine.
Please help.

I did in place Upgrade.
Before Upgrade
Logical Names
Database Name: Tfs_TESTTFS
Database Log: Tfs_TESTTFS_Log
After Upgrade
Logical Names
Database Name: Tfs_TESTTFS
Database Log: TfsVersionControl_Log
Thx

Upgrade our CRM 2011 SQL server from 2008 R2 to SQL 2012

Can anyone please let me know what the steps involved are?
Thanks,
Red.

please see if this helps.
https://social.technet.microsoft.com/Forums/sqlserver/zh-CN/e614c52c-fbd7-4877-8e26-03d4d58f61ed/how-to-restore-sql-server-2008-r2-databases-on-sql-server-2012?forum=sqlsetupandupgrade
regards
Jithesh

How to migrate logins from 2008 SQL server to 2012 SQl server

Hi,
How to migrate all logins from default SQL server2008(enterprise edition) to 2012 SQl server(enterprise edition)default

Hi BomaSri,
Have you tried v.vt’s suggestion? That article describes how to transfer the logins and the passwords between instances of Microsoft SQL Server 2005, of Microsoft SQL Server 2008, and of Microsoft SQL Server 2012 on different servers. The commands apply
to SQL Server 2005, SQL Server 2008 and to SQL Server 2012.
Allen Li
TechNet Community Support

Upgrading domain controller from Server 2003 to Server 2012 R2, how will this affect Exchange 2010?

Hi All,
Below is an AD and Server related post that I had submitted last week. While I did receive valid responses for the post, I was advised to check with the Exchange forums for the Exchange related question in
bold. All responses are welcomed, thank you!
===========================================================
Hi All,
I am hoping that someone could perhaps provide some insight on this topic as I apparently can't seem to google the best answer.
I have recently acquired an AD domain that is running on a 2003 domain controller. I have been tasked with upgrading our existing domain structure with 2012 R2 domain controllers for our main office and remote offices.
The domain name is company.mynetwork.com, and it is the default first site name. We have multiple offices throughout the US with their own domain controllers (i.e. FL.mynetwork.com, NY.mynetwork.com, DC.mynetwork.com, etc.).
Our main office, and default first site has one domain controller (mynetdc1) running Server 2003 R2. It is also our only DNS server for the main office. It also has an additional domain controller called mynetmaster3 which is running Server 2003.
Both mynetdc1 & mynetmaster3 NTDS settings show them as global catalogs under AD Sites & Services. Both servers are also in the AD Domain Controllers OU, along with all of the other satellite office domain controllers.
Additionally, our main office is running Exchange 2010 with the latest service pack. My questions are:
Can we demote and retire mynetmaster3, then replace mynetdc1 with a newly promoted 2012 R2 global catalog domain controller without harming anything in the domain tree and interrupting connectivity to the other offices (this of course goes without saying
after a 4 hour maintenance window to get the task completed has passed)?
Should we upgrade the satellite offices first after raising the functional level for mynetdc1, or should we do the opposite (upgrade main office, then satellite offices)?
MS Exchange 2010 is heavily dependent on AD, what effect will this entire project have on our email server? What steps should we take beforehand to ensure email continuity?
Finally, is there any shame for a Net Admin to suggest that we hire an implementation specialist for this task? :)
Any advice would be greatly appreciated!

As long as the operating system on your Exchange servers isn't upgraded, and as long as you do the Active Directory domain and forest updates in the supported manner (the following link is a good example -
http://blogs.msmvps.com/mweber/2012/07/30/upgrading-an-active-directory-domain-from-windows-server-2003-or-windows-server-2003-r2-to-windows-server-2012/), Exchange will happily operate behind the scenes. Exchange 2010 is supported in the Windows
forests (domain controllers, domain functional level and forest functional level) mentioned in the following TechNet article, which includes both Windows 2003 and Windows 2012.
http://technet.microsoft.com/en-us/library/ff728623(v=exchg.150).aspx
Due to this, you should be good as long as you do the domain controller, domain, and forest upgrades carefully. Oh, and before you start each step, get a nice backup.

Frequency migrate data from the operational database SCOM 2012 SP1

What is the frequency with which
information is migrated from the operational database
to the data warehouse database,
are in separate servers and should perform
maintenance tasks such as defragmentation to optimize
disk space, this is recommended?
thank you very much

Hi
Refer below link for data sync from DB to DW
http://blogs.technet.com/b/jonathanalmquist/archive/2010/01/24/how-and-when-is-data-written-or-synchronized-to-the-data-warehouse.aspx
Dataware house
http://blogs.technet.com/b/stefan_stranger/archive/2009/08/15/everything-you-wanted-to-know-about-opsmgr-data-warehouse-grooming-but-were-afraid-to-ask.aspx
Regards
sridhar v

Upgrade FIM 2010 R2 Sp1 Databases from SQL 2008 R2 to SQL 2012

Hi,
I want to upgrade my SQL from 2008 R2 to SQL 2012.
FIM Databases
1) FIMService Database
2) FIMSynchronizationService Database
Mentioned above are my FIM databases running on SQL server 2008 R2 . Now I was looking for some article which could tell me if SQL can be upgraded without affecting my existing databases of FIM or if i can move these databases to a new server having SQL
2012
Activity I want to perform : Create a fresh Server of SQL 2012 and move my FIM 2010 databases over it by restoring the backups. but as per the link below it seems not possible!
http://social.technet.microsoft.com/wiki/contents/articles/5465.fimilm-how-to-move-the-backend-sql-server-synchronization-service-database.aspx

Hi Shivam,
Please take a look here: Release Notes for Forefront Identity Manager 2010 R2 SP1.
In the table you have tasks to upgrade SQL for FIMService and FIMSych.
FIM Service:
Upgrade FIM Service servers to FIM 2010 R2 SP1
Stop FIM Service on all servers
Backup Database [in case rollback needed]
Upgrade SQL to SQL Server 2012
Start FIM Service on all servers
FIM Synch:
Upgrade FIM Sync to FIM 2010 R2 SP1
Stop FIM Sync
Backup Database [in case rollback needed]
Upgrade SQL to SQL Server 2012
Start FIM Sync
If you are not making in-place upgrade, I would do something like here:
Stop FIM Services
Backup the databases at SQL 2008
Restore backed up databases on SQL 2012
Make sure SQL Agent Jobs are moved (FIMService)
Make sure Broker is enabled on FIMService database
On FIM machines create SQL alias using cliconfg utility. Alias should have the name of "old(sql2008) SQL" and point to new name/instance.
Start FIM Services - they would use "old" name to connect, but it would be translated to new location. So they would start.
If you found my post helpful, please give it a Helpful vote. If it answered your question, remember to mark it as an Answer.

Upgrade to SP3 from sql server 2008 R2 SP2 and SharePoint server 2010 known issues

Hi Guys,
We are planning to upgrade SQL server to SP3 from 2008 R2 SP2 and would like to known if there are any known issues with SharePoint 2010 server and office web apps.
Though I was searching blogs and forums and could not find any noteworthy but wanted to look if any noted SharePoint issues after the upgrade.
VM

Hi Venu,
There should no issue for SharePoint 2010 with install SP3 for SQL2008R2 (also like comments mentioned in article below), I searched from internal and internet, there seems no document/article mentioned the known issue for SharePoint about this, you can
back up your environment and test the SP3 in a test environment before touching the production environment.
https://habaneroconsulting.com/insights/SharePoint-SQL-Server-Support-Matrix#.VSTY-nkfr4Y
http://blogs.msdn.com/b/glsmall/archive/2014/12/03/list-of-fixes-in-sql-server-2008-r2-sp3.aspx
Thanks
Daniel Yang
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

SQL Server std 2008 R2 SP2 upgrade to 2014 std fails, SSRS issue?

I’m trying to make an in place upgrade from 2008 r2 sp2 to sql 2012. With old installation everything (including Reporting Services) works fine, there is only one instance named MSSQLSERVER and all stuff is on one server, ssrs is native mode, compatibility
level of databases is 100.
When I start upgrade process al things go fine till “Feature Rules” where “No Custom Rendering Extensions” fails (it says “The Report Server has some custom rendering extensions configured”). Into Windows Application Log appears the following “Report Server
(MSSQLSERVER) cannot connect to the report server database” and installation stops. We have not installed any extensions as far as I know. I’ve done some tweaking with RSReportServer.config but without success.
Any good advice?
Pekka

Hello,
Please verify you don’t have extension elements added on the RSReportDesigner.config file too.
Use the following article to remove any possible rendering extensions:
http://msdn.microsoft.com/en-us/library/ms152821(v=sql.105).aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Upgrade Sharepoint 2010 SQL Reporting Services from 2008 R2 to 2014

I'm about to do the upgrade of SharePoint 2010 Reporting Services from 2008 R2 to 2014. The instructions say it can be done "in-place" with no downtime. I've seen this article:
http://whitepages.unlimitedviz.com/2012/03/upgrading-sql-server-reporting-services-to-2012-in-sharepoint-integrated-mode/
It covers 2012 so I assume the same holds true for 2014.
I'd like to get the low down from anyone who has actually performed the upgrade of SSRS from 2008 R2 to 2014. Anyone done this upgrade? Any issues?
David Jenkins

So far I would have to say that the upgrade can be done "in-place" but there is a "DOWNTIME".
This article has helped a lot:
http://blogs.catapultsystems.com/tlingenfelder/archive/2012/07/10/upgrading-sql-server-reporting-services-2008-r2-to-sql-server-reporting-services-2012-in-sharepoint.aspx
In the article it tells you about a bug in the SQL Upgrade process where
the Domain account you use will not work. When you type in the password it fails. On top of that it will lock the Domain account because of a bad password! There is probably something wrong with the authentication process and it garbles the password.
Anyway, you end up having to change the account to the "Network Service" account before you can do the upgrade. This means the services get restarted which means???
DOWN TIME! He goes over other errors. I haven't reviewed these issues yet.
The other thing I learned is that everything needs to be SQL Server 2008 R2 SP2 in order to upgrade. You don't find this out until almost the last step in the installation process.
Now I have to wait until next week to actually do the upgrade because I have to schedule an SP2 install. :(
David Jenkins

Upgrade single instance from 2008 R2 SP2 to 2012 SP1

Similar Messages

Maybe you are looking for