Migrating SCCM 2007 R2 database to SQL 2012

Am I able to migrate my SCCM 2007 R2 database from SQL 2008 (running in 2005 compatibility mode) to SQL 2012? Is it even supported to run a 2012 instance with compatibility set to 2005? Or will I need to upgrade the database at some point to get this to
work.
Currently, my attempts fail and the errors in the ConfigMgrSetup.log suggests an issue with compatibility:
Incorrect syntax near '99900'. : ins_upd
Incorrect syntax near '99901'. : ins_upd
-which led me to a hotfix (http://support.microsoft.com/kb/2676776) that, upon installing, indicated that it failed to completely install.
For whatever it's worth, the SCCM server is running 2008 x64 and the SQL server is 2008 R2.

See the caveats at http://technet.microsoft.com/en-us/library/ee344146.aspx listed under the SQL Server Site Database Configurations section:
"To use SQL Server 2012 to host the site database, you must install the following updates as described in the Microsoft
Knowledge Base:
Article 2676737
Article 2676776
Additionally, to use SQL Server 2012 for the site database, you must upgrade the instance of SQL Server in use at a site from SQL Server 2008 or SQL Server 2008 R2 to SQL Server 2012. It is not supported to install a new Configuration
Manager 2007 SP2 site with SQL Server 2012. It is also not supported to install Configuration Manager 2007 R3 when SQL Server 2012 is in already in use for the site database."
Jason | http://blog.configmgrftw.com

Similar Messages

Unable to move SCCM 2007 database to SQL 2012 SP1

Hi ,
We want to Move
SCCM 2007 R3 database to SQL Server 2012 SP1.
SCCM server Version :
4.00.6487.2000
Build Number : 6487
But it says fatal error during the move wizard.
In ConfigMgrSetup.log it says :
***SqlError: [42000][102][Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near '99901'. : SiteControl_ins_upd
***SqlError: [42000][102][Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near '99901'. : SiteControl_ins_upd
I already installed following updates on SCCM server , but still it failed to move.
2676737
2676776

This would be manual process. The simplest way to fix them is to reinstall the reporting point.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

How to force site code discovery on all the clients, Migration SCCM 2007 to SCCM 2012

HI,
I migrated SCCM 2007 to SCCM 2012 SP1, but the clients does not update the New Site Code Automatically, if I click on Discovery option the client find the new site, but I need do this automatically because are too many clients.
This registry key does not exist on client computers.
HKLM\Software\Microsoft\SMS\MobileClient\GPRequestedSiteAssignmentCode
HKLM\Software\Microsoft\SMS\MobileClient\GPSiteAssignmentRetryInterval(Min)
HKLM\Software\Microsoft\SMS\MobileClient\GPSiteAssignmentRetryDuration(Hour)
Any Help?
Thanks.

Hello ICH-CR,
Thanks for writing to the SysCtr ConfigMgr forums.
I think there are multiple solutions to this issue and you can choose whatever fits best to your scenario.
1. While upgrading the clients from SCCM 2007 to 2012 you can assign the clients to your ConfigMgr 2012 site.
http://technet.microsoft.com/en-us/library/gg682060.aspx#BKMK_AutomaticAssignment
You just need to ensure that you have a boundary group and boundaries. More details on
http://technet.microsoft.com/en-us/library/13694ac5-8f3b-42a9-8040-b23f21c79637#BMBK_CreateBoundaryGrp
I would suggest the first method because if you create another child site, you shouldn't have to reassign the clients back again. If that is unlikely then use the following script which is method no 2
2.
http://gallery.technet.microsoft.com/scriptcenter/Change-sccm-configmgr-cf6e0327
This is a VBSCRIPT and can be ran from a network location using the PSEXC
3. Here is a smaller script
'Replace with your Site Code sSiteCode = "EnterNewSiteCode"
sMachine
= "."
set oCCMNamespace
= GetObject("winmgmts://"
& sMachine & "/root/ccm")
Set oInstance
= oCCMNamespace.Get("SMS_Client")
set oParams
= oInstance.Methods_("SetAssignedSite").inParameters.SpawnInstance_()
oParams.sSiteCode
= sSiteCode
oCCMNamespace.ExecMethod
"SMS_Client",
"SetAssignedSite",
oParams
You can use this script as a logon script .
Anurag
Microsoft Certified Professional| Microsoft Certified Technology Specialist (ConfigMgr)
This posting is provided 'AS IS' with no warranties or guarantees, and confers no rights.
My Blog
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

WSUS Server settings and Migrating SCCM 2007 Clients to SCCM 2012 R2

I am in the process of migrating a site from SCCM 2007 to SCCM 2012 R2.
Whilst doing this I came across the following issue:
The first issue is the workstations are woefully out of date, patch and update-wise, some have never had a patch applied as the branch IT staff are building them from the original disk. The policy is set in the SCCM 2007 client to point the machines at
the 2007 WSUS server, which is not set to deliver any updates to 2007 clients and hasn't been for a while. So as soon as the client is installed they lose the ability to get updates from Microsoft and don't get them from the 2007 WSUS server either.
Issue number 2 is the machines are a mixture of hand-built machines to SCCM 2007 delivered images, the SCCM image is patch using offline patching so they are somewhat up-to-date, but the hand-built machines are not and as there is no standardization on
the Microsoft Update client settings, the IT person on-site sets it to whatever he/she feels like, as it makes no difference once the client is installed and the policy applied.
So, when I come to update the client from 2007 to 2012, the following occurs
The Client uninstalls, and the GPO policy settings for Windows Update are removed.
Depending on the setup of the client initially, some machines are then going to Microsoft for their updates (literally 100s) and although the new client is installed the policy update does not fire to update the Windows Update Policy settings, sometimes
for hours after the install finishes. My thoughts are that it just can't run the policy as it is bogged down by patches updating and, in some cases, rebooting and then updating some more.
As a workaround I have had to go in an physically disable Microsoft Update on these machines, which stops the downloading and eventually allows the policy to apply, after which the machine then begins to receive patches from WSUS in a controlled method during
maintenance windows.
I have tried a number of approaches, even setting the Global Group Policy for Windows Update, but the install still removes the keys and basically sets Windows updates back to whatever it was set before the policy was applied and stays that way until the
new client is installed and the Machine policy reapplied. This can be speeded up by initiating it on the client obviously, but that would mean going to each client or using right-click tools on each machine, which is not an option.
What I would like to know is if there is something I am missing from my methods or is it just that I have never been on a site with such out of date workstations built in such different ways.
Any help would be appreciated.

First note that clients do *not* get updates from WSUS in ConfigMgr. The Windows Update Agent (WUA) must point to the WSUS integrated into ConfigMgr (by virtue of having the SUP installed on it) but this is only to make the update catalog/metadata available
to it. Approving updates in WSUS is unsupported for ConfigMgr.
What you've described above is all working as designed although these clients are falling into a gap between the 2007 and 2012 configuration and thus they are reaching out to Windows Update during this gap and installing updates. To prevent this, you
need to disable automatic updates via a domain group policy. This will prevent all automated WUA activity including installing updates from any source automatically. This will not interfere with ConfigMgr Software Updates in any way though.
Jason | http://blog.configmgrftw.com | @jasonsandys

SCEP install and policy issue (after migration SCCM 2007 to 2012)

Hi,
We have some terminal services which were connected to SCCM 2007.
I migrated 3 of them (via "install client" in SCCM 2012), what worked fine. Since they become member of the Windows server group + terminal services group, they get the scep-client as well as a specific policy.
Now we have 1 terminal server which did not install the scep client.
Logfile:
Failed to get EP event code under registry key SOFTWARE\Microsoft\CCM\EPAgent   EndpointProtectionAgent   21/08/2014 11:19:42   43640 (0xAA78)
Failed to get EP event message under registry key SOFTWARE\Microsoft\CCM\EPAgent   EndpointProtectionAgent   21/08/2014 11:19:42   43640 (0xAA78)
State 1, error code 0 and detail message are not changed, skip updating registry value   EndpointProtectionAgent   21/08/2014 11:19:42   43640 (0xAA78)
File C:\Windows\ccmsetup\SCEPInstall.exe version is 4.5.216.0.   EndpointProtectionAgent   21/08/2014 11:19:42   43640 (0xAA78)
Sleep 10 seconds and retry read ProductName of the AM solution   EndpointProtectionAgent   21/08/2014 11:19:42   43640 (0xAA78)
Sleep 10 seconds and retry read ProductName of the AM solution   EndpointProtectionAgent   21/08/2014 11:19:52   43640 (0xAA78)
Sleep 10 seconds and retry read ProductName of the AM solution   EndpointProtectionAgent   21/08/2014 11:20:02   43640 (0xAA78)
Sleep 10 seconds and retry read ProductName of the AM solution   EndpointProtectionAgent   21/08/2014 11:20:12   43640 (0xAA78)
Sleep 10 seconds and retry read ProductName of the AM solution   EndpointProtectionAgent   21/08/2014 11:20:22   43640 (0xAA78)
Unable to query registry value (ProductName), return (0x80070002) means EP client is NOT installed successfully.   EndpointProtectionAgent   21/08/2014 11:20:32   43640 (0xAA78)
So I installed the client manually via "SCEPInstall.exe /policy z:\client\ep_defaultpolicy.xml" (after a pushd \\sccmserver\c$\...client\).
2 things:
1.any idea why it wouldn't install "failed to get EP event code under reigstry key" ..?
2.specific scep terminal server policy will be applied afterwards (file exclusions etc), right (don't see it yet and refreshed policy several times)?
J.
Jan Hoedt

Hi,
I have seen a temporary solution, created a package with the command line: REG add “HKLM\SOFTWARE\Microsoft\Microsoft Security Client” and deployed this program to the Client.
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.

File opening throws RBS exception after migrating to a new farm with sql 2012

We have successfully migrated the SP 2010 -sql 2008 r2 wss_content to a new sp2010 farm with sql 2012. The old and new farms are configured for RBS - FIlestream.
In the new farm when tried opening a document we see the below exceptions in event viewer. The documents open fine for admin users and fail for others. I have verified all the permissions on the blob store file location and it looks good. Users have no
issue uploading new files over and below the set the file size limit.
Any suggestions on how to debug this would be great, do we need to rerun the .migrate() to realign any of the blob file references, we played around setting the max file size couple of times.
Event vwr on DB server -
FILESTREAM file named with GUID '00311100-0000-51eb-f3a8-0b387bc5c5ce' that belongs to FILESTREAM data file ID 0x10001 does not exist or cannot be opened.
Event vwr on Front end -
Message ID:20, Level:ERR , Process:10580, Thread:36
Blob store <FilestreamProvider_1> threw this exception:
Operation: Unknown
BlobStoreId: 1
Log Time: 5/5/2014 8:00:49 PM
Exception: Microsoft.Data.SqlRemoteBlobs.BlobStoreException: There was a generic database error. For more information, see the included exception. ---> System.Data.SqlClient.SqlException: A transport-level error has occurred when receiving results from
the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
   at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParserStateObject.ReadNetworkPacket()
   at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
   at System.Data.SqlClient.TdsParserStateObject.ReadByteArray(Byte[] buff, Int32 offset, Int32 len)
   at System.Data.SqlClient.TdsParserStateObject.ReadInt64()
   at System.Data.SqlClient.TdsParserStateObject.ReadPlpLength(Boolean returnPlpNullIfNull)
   at System.Data.SqlClient.TdsParser.ProcessColumnHeader(SqlMetaDataPriv col, TdsParserStateObject stateObj, Boolean& isNull)
   at System.Data.SqlClient.SqlDataReader.ReadColumnHeader(Int32 i)
   at System.Data.SqlClient.SqlDataReader.GetBytesInternal(Int32 i, Int64 dataIndex, Byte[] buffer, Int32 bufferIndex, Int32 length)
   at System.Data.SqlClient.SqlDataReader.GetBytes(Int32 i, Int64 dataIndex, Byte[] buffer, Int32 bufferIndex, Int32 length)
   at Microsoft.Data.BlobStores.FilestreamBlobStore.FilestreamStoreLibraryBase.ReadBlob(Byte[] storePoolId, Byte[] storeBlobId)
   --- End of inner exception stack trace ---
   at Microsoft.Data.BlobStores.FilestreamBlobStore.FilestreamStoreLibraryBase.ReadBlob(Byte[] storePoolId, Byte[] storeBlobId)
   at Microsoft.Data.BlobStores.BlobStore.ReadBlobInternal(Request request)
BlobStoreException Code: OperationFailedAuthoritative
-Mash "http://sharepointxperiments.wordpress.com"

Migration - its a content db backup/restore/mount to new farm with sql 2012 from sql 2008 r2
Okie here are the results after we tried to narrow down the issue to few steps-
This issue happens on documents that are already existed in the content db prior to migration. we picked two docs from one library. DOC A and DOC B of close to same size..
DOC A - file size 64k, rbs max size set to 1mb.
Regular User and SPAdmin both can open fine, check out n check in successfully.
no entries made in event vwr of front end and DB server
DOC B - file size 64k, rbs max size set to 1mb
SPAdmin - can check out n open fine, but cannot check in back - file not available error
Regular User - cannot open the file - file not avialable at the url
          Both users can view doc properties at lib level..
Errors found in event vwr of DB server -
"FILESTREAM file named with GUID '00311100-0000-51eb-f3a8-0b387bc5c5ce' that belongs to
FILESTREAM data file ID 0x10001 does not exist or cannot be opened."
and
"The operating system returned the error '2(The system cannot find the file specified.)' while attempting 'FsDoHandler::CreateFile' on 'H:\Blob_Store\a06953ae-6f49-43b1-9c2d-fefb13bda9fe\1c581a4a-b450-4143-bc3d-8d419b49b0fb\0000eb20-000066ff-0002'
at 'fstrman.cpp'(2075)."
I incline to believe that the references for documents in blob store could have been corrupted for some documents during the migration. Any new docs uploaded to content or to blob are all accessible fine.
I'm not sure running .migrate() will re align the blob file references? Any ideas on how to effectively get this resolved..
-Mash "http://sharepointxperiments.wordpress.com"

Migrate and Upgrade ReportServer database from SQLServer 2012 to SQLServer2014

Hi,
Today I migrated one reporting service from sql server 2012 to new server which running sql server 2014.
Firstly I back up encryption key and restored to new server, then follow the https://msdn.microsoft.com/en-AU/library/ms156421.aspx (e.g. backup, restore reportserver). In section "How to Configure the Report Server Database Connection" , I
cannot pass this step as it complains it is not a report server, please see error below:
However I can see my original reports/data srouces in below url and I can create new items like data source:
http://sydwt-ssql-1/ReportServer
http://sydwt-ssql-1/Reports/
Anyone knows what happened?
Here are the version information:
- From
Microsoft SQL Server 2012 (SP1) - 11.0.3412.0 (X64)
Mar 2 2014 01:25:09
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: )
- To
Microsoft SQL Server 2014 - 12.0.2480.0 (X64)
Jan 28 2015 18:53:20
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: )
Thanks,
Albert

Hi
As Alberto’s post, it's not supported to run a Windows Server Update Services (WSUS) database on SQL Server 2012 in Server 2008 R2. Since your application requires SQL Server 2012 Express as a minimum, you can try the following method:
1. WSUS in Server 2012 supports SQL Server 2012, if you want to upgrade WSUS database supports SQL Server 2012, you need to upgrade WSUS 3.0 SP1, operation system and so on. For more information, you can post the question about WSUS in the
Windows Server forums. It is appropriate and more experts will assist you. In addition, upgrade SQL Server 2005 to SQL Server 2012, as Shanky’s post, you need to make sure that your SQL Server 2005 has been applied Service Pack 4.
2. However, if you don’t want to upgrade WSUS database from SQL Server 2005 to SQL Server 2012, I recommend you to install a new instance of SQL Server 2012 on Windows Server 2008 R2.
In addition, before installing SQL Server 2012 or upgrading to SQL Server 2012, your system should meets the following prerequisites:
• The Windows Installer service must be running.
• Microsoft .NET Framework 3.5 SP1 and .NET Framework 4.0 are required.
• Windows PowerShell 2.0 or later is required if you're upgrading the database engine.
For more information about the prerequisites for installing SQL Server 2012, please review the following link:
Hardware and Software Requirements for Installing SQL Server 2012:
http://msdn.microsoft.com/en-us/library/ms143506(v=sql.110).aspx
Thanks
Lydia Zhang

MOSS 2007 native mode on SQL 2012 with compatibility mode?

We are on MOSS 2007 SP 3 64-bit (just native, it is not SSRS integration mode) running on SQL 2008 R2 SP2 64-bit. Can the databases move to SQL 2012 with compatibility mode?

Hi,
As far as I know, SQL 2012 is not listed as compatible with SharePoint 2007 on the
technet articles. If you want to upgrade to SharePoint 2010, then you can move the databases and upgrade the database. If you just want to use SQL 2012 with SharePoint 2007, I think it is not applicable.
For more information, please refer to these sites:
SQL Server 2012 not supported on WSS 3.0/MOSS 2007 and versions previous than SharePoint 2010 SP1:
http://blogs.msdn.com/b/calvarro/archive/2012/04/27/sql-2012-not-supported-on-wss-3-0-moss-2007.aspx
SQL Server 2012 support:
http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/02fd7238-9cc2-43fc-a46c-afbfca21210b
Thanks,
Entan Ming
TechNet Subscriber Support in forum
If you have any feedback on our support, please [email protected]
Entan Ming
TechNet Community Support
Will it work with the database set with the compatibility mode ?
/* Server Support Specialist */

Fulltext search of binary files outside of database in SQL 2012/Server 2012

This may be more of a Windows Server 2012 question but I'm not sure.
I have a system that holds large amounts of binary files (pdf, doc, etc.). The files themselves are held outside the database in a folder and a SQL table holds the metadata. I used the Indexing Service available through Windows Server 2008 to
create a catalog called "EFCATALOG" to index the contents of the external folder, then created a linked server called MYIDXS which allowed me to query that external indexing catalog from within SQL with a query like this:
EXEC sp_addlinkedserver MYIDXS, 'Internal App', 'MSIDXS', 'EFCATALOG'
SELECT * FROM MYDOCS
LEFT JOIN OPENQUERY(MYIDXS,'SELECT FILENAME FROM SCOPE() WHERE CONTAINS (''test'')') AS MYTBL
ON MYDOC_FILE_NAME = MYTBL.[FILENAME]
With Windows Server 2012, I'm missing the functionality to create the indexing service catalog. I've added the Windows Search Service and see how I can configure folders for searching, but there is no naming functionality for this and I don't see how
I can get the above query/structure to work in Windows Server 2012/SQL Server 2012 environment. In fact, there isn't much at all online regarding the search service or the relationship back to the older versions in 2008 and before.
Is there any way to continue this structure in 2012? I would like to avoid recoding my application to work with a different structure. I'm afraid that changing everything to work with the FILETABLE/FILESTREAM functionality added in SQL 2012
will be necessary which is fine long term, but not convenient right now.
Thanks in advance for any suggestions/help.

Thank you Fanny Liu, based on your link the syntax has changed dramatically. I need to query SYSTEMINDEX now and the structure is very different. It still seems that this new syntax requires creating a linked server of a different type.
I've tried:
EXEC sp_addlinkedserver @server = 'TEST', @provider = 'Search.CollatorDSO.1', @datasrc = 'SYSTEMINDEX', @srvproduct = '', @provstr='Application=Windows'
SELECT FileName FROM OPENQUERY("TEST", 'SELECT Filename FROM SYSTEMINDEX')
Msg 7302, Level 16, State 1, Line 1
Cannot create an instance of OLE DB provider "Search.CollatorDSO.1" for linked server "TEST".
I've also tried using just "Search.CollatorDSO"as the provider since that is the provider name listed in management studio but basically the same error comes back.
So I have 2 questions:
1) Is it possible for my original process to work in Windows Server 2012 in any way (meaning that the OPENQUERY example I provided can remain relatively unchanged)?
2) If change is necessary using this new SYSTEMINDEX and linked server combination, why is my linked server definition failing? I'm using SQL Server 2012....Microsoft SQL Server 2012 - 11.0.2100.60 (X64)
Feb 10 2012 19:39:15
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
Thank you.

Migrating OBIEE Repfrom Oracle database to SQL server database in Solaris.

Hi,
I need inputs in how we would migrate our connections in Repository from Oracle database to SQL server database in Sloaris server.
Is there a complication here.
Regards,
Bhavik

Well that makes more sense, you probably have phrased your question better. Microsoft SQL Server Connectivity Components are not supported in any other operating system than Windows. So you will not be able to use the SQL Server native drivers to connect to your SQL Server. ODBC it's an option but there aren't many ODBC drivers for Unix systems. Luckily for you OBIEE includes the DataDirect ODBC drivers and supports using them to connect to a SQL Server. Check [the documentation|http://download.oracle.com/docs/cd/E10415_01/doc/bi.1013/e10416/general_101331.htm#sthref9] on how to use them. Having said that I would say that whoever is pushing to move your DWH to SQL Server should consider also moving OBIEE to a Windows server to be able to use the SQL Server native drivers to connect to SQL Server.
PS: No needs to post 3 times. :-)

Help me how migrate SCCM 2007 queries into SCCM 2012 queries

Hi,
I know query migration is not possible to 2012 SCCM. Any possible way ..?
Like powershell or script?

Hi,
These might be helpful for you to create your own script.
http://msdn.microsoft.com/en-us/library/hh949058.aspx
http://msdn.microsoft.com/en-us/library/cc145430.aspx
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.

Migrating SCCM 2007 Secondaries to 2012 DP's and Contant Status is showing Unknown instead of Success

It looks like the packages converted with the DP and are being pulled from the client properly. When I went into Administration | Distribution Points the object "packages" at first did not show all the packages. After I scheduled a validation
they did show up. However the Content Status of the package is still showing Unknown. I've seen posts that others have had this issue. However I haven't seen the solution.
Help Appreciated!
Thanks

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?
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Powershell command to migrate Exchange 2007 mailbox databases with a legacy name, & import them into a new 2007 instance, with a new name.

Hi All. I am currently at the later stage of provisioning a new CCR Exchange 2007 migration (to
virtualise old Exchange 2007 hardware) for 5,000 users & have a quick question.
I have created around 15 newly named storage groups, & have named 1 new DB per group, with the same name (let's say New-DB-1), residing within them. The problem I have, is the old legacy DB's have different names (let's say Old-DB-1) & I need
to import them into the new storage groups, to match the new names. So far I can import/export between old & new OK if both old & new DB names\folders etc. names marry up perfectly, but are unable to if there not the same. Does anyone have any thoughts
on how best to tackle this, as this is one of the final hurdles stopping the migration? Many Thanks, John

Hi All
Many Thanks for the feedback.
The terminology 'migrate' was used based around the fact I will be decommissioning the old 2007 physical environment. This is after moving all DB's over to the new newly created Virtual environment that will host all roles.
The solution I ended up using yesterday, was the following:
1) Dismounted the relevant named DB (NEWDB) in the new environment.
2) I then ticked the 'This database can be overwritten by a restore option' box.
3) Copied over the old named DB (OLDDB) to the same location, & overwrote using the new name (NEWDB).
4) Re-mounted the (NEWDB).
5) Ran the following 2 PowerShell commands:
Get-mailbox –database OLDDB | move-mailbox –targetdatabase NEWDB -configurationonly:$true
Get-MailboxDatabase NEWDB | ResetSearchIndex.ps1 -force
6) Checked to make sure the clients were working ok, in the now the new (NEWDB) environment.
Rich: Many thanks for your PS script, which I will test with future DB moves & provide feedback
J
John.

Installing IBuySpy Database using SQL 2012 Express

Hi,
I am attempting to install a store application called IBUYSPY from a script file I received from the a book - Pro WPF 4.5 with C#. I get an error as follows:
Program Location:
   at System.Data.SqlTypes.SqlBinary.get_Value()
   at Microsoft.SqlServer.Management.UI.VSIntegration.DebugSession.DebugCallbacks.OnSqlInitializeDebuggingEvent(ISqlInitializeDebuggingEvent sqlInitializeDebuggingEvent)
   at Microsoft.SqlServer.Management.UI.VSIntegration.DebugSession.DebugCallbacks.Microsoft.VisualStudio.Debugger.Interop.IDebugEventCallback2.Event(IDebugEngine2 debugEngine, IDebugProcess2 debugProcess, IDebugProgram2 debugProgram, IDebugThread2
debugThread, IDebugEvent2 debugEvent, Guid& riidEvent, UInt32 attribute).
I just simply double clicked the Store.sql script provided. Any suggestions on how to fix this would be appreciated The script is rather long but I can supply that if needed. Thank you.
Soincerely,
Om

Are you trying to install application or sql server 2012 ? Can you explain us with more details, this error doesnt looks like a sql installation related...
Raju Rasagounder Sr MSSQL DBA

Recently decomissioned old SCCM 2007 server and replaced with 2012 R2- How do I point everything to the new SCCM server?

I've tried many things that I've found in articles. Gone as far as ADSI edit. Not sure what else I can do. The old server was setup by someone else and never really worked correctly. I'd basically like to start fresh with this new install.
Thanks
James A+, Network+, MCP

Follow my R2 install guide to get your site up.
http://sccmentor.wordpress.com/2014/01/08/sccm-2012-r2-step-by-step-installation-guide/
You won't need to extend the schema if this has already been done for the 2k7 site. The System Management container could already exist. If so add in permissions for the new site server. If not create and follow the guide. Once done set up your boundaries
and discovery methods accordingly. Once you start to populate the console with clients then installing the client will remove the old 2k7 client (if it was installed) as part of the 2012 client install.
Cheers
Paul | sccmentor.wordpress.com

Migrating SCCM 2007 R2 database to SQL 2012

Similar Messages

Maybe you are looking for