Search the Community

I am in the process of upgrading our SCCM infrastructure from Svr2008R2 and SQL2008R2 to 2012R2 so I can upgrade to current branch. We are doing in-place upgrades, to 2012R2 on our Primary Site and also our separate DB server. Our DBA is going to start by upgrading our SQL version to 2014 on the box and they have asked the question where do these facets attached to the database come from and how are they generated, as the DBA plans on detaching backing up and re attaching the DB, they said these facets will not be carried over. Are these facets generated by SCCM and will they continue to exist after the version of SQL is upgraded and the database reattached?. I have attached a screenshot of the facets in question. Thanks

Looking to upgrade current SCCM environment from 1610 and skip over 1702 going directly to 1706. Current Configuration Below SCCM Current Branch 1610 ADK 1607 MDT 8443 Actively Deploying Windows 10 1607 and light Testing with Windows 10 1703 deployments. Looking at current support docs it looks like ADK 1607 is not compatible with SCCM Current Branch 1706. https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/support-for-windows-10 However, it is recommended that if you are actively deploying Windows 10 1607 via OSD that you stay on ADK 1607. Trying to determine what are the best steps to upgrading without breaking the OSD/Task Sequences environment. 1. Should I only upgrade the environment to SCCM 1702 Current Branch and stay on ADK 1607 till our Client team(handles OSD) is comfortable moving to Windows 1703 Deployments? The article above says SCCM CB 1702 is backwards compatible for ADK 1607. 2. Or is it recommended, even though we are still actively deploying Windows 10 1607 for Prod, to upgrade the ADK to 1703 and then move to SCCM CB 1706? Trying to better understand, if the recommendation is to stay on ADK 1607 if you are actively deploying Windows 10 1607 in your environment, what are potential risks in upgrading to ADK 1703. 3. Final concern to list here is the what are the risks in upgrading to the either SCCM CB 1702 or 1706 as it relates to MDT 8443. What has the potential in breaking? Any info would greatly be appreciated. Just want to move forward with a better educated decision. I have been reading articles and going through forums to confirm potential risks but looking for a little advice based in the current environment setup.

Does anyone know if its possible to build Stand Alone Task Sequence Media for a Win10 Upgrade TS via SCCM CB 1606 that works? I added a Boot WIM to my Win10 Upgrade TS and I was able to create the media... but when I run the Upgrade TS off the USB stick it fails to copy over drivers locally into a custom location or into the TS Working directory. Are there any special settings to make the Upgrade work via TS Media? Looking for a way to get my remote users to be able to upgrade to Win10 1607. Thanks in advance

Hello, As i'm planing to upgrade out SCCM from 1606 to 1702 ,I started running some prerequisites tasks, however the Testdbupgrade failed ,here is what i've done so far : 1- I installed SQL Server 2012 Standard Edition SP1 (Same version we have on the production SCCM) on a VM. 2- Upgraded to SQL Server 2012 Standard Edition SP2 as it's required to upgrade to 1702. 3- Restored the database from the daily backup file.successfully 4- Ran a testdpupgrade and got the error below : ERROR: SQL Server error: [42000][468][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the not equal to operation. Configuration Manager Setup 5/9/2017 10:57:20 AM 3304 (0x0CE8) INFO: Executing SQL Server command: < MERGE [dbo].[LU_LicensedProduct] AS TARGET ~ using (select [LicensedProductID], [ProductPool], [ProductName], ~ [FamilyName], [VersionSequence], [VersionCode], ~ GETUTCDATE() , N'$CD' ~ from tempdb.dbo.temp_LU_LicensedProduct) ~ as SOURCE ( [LicensedProductID], [ProductPool], [ProductName], ~ [FamilyName], [VersionSequence], [VersionCode], ~ [LastUpdated], [SourceSite]) ~ ON SOURCE.[LicensedProductID] = TARGET.[LicensedProductID] ~ when matched and (~ TARGET.[ProductPool] != SOURCE.[ProductPool] OR ~ TARGET.[ProductName] != SOURCE.[ProductName] OR ~ TARGET.[FamilyName] != SOURCE.[FamilyName] OR ~ TARGET.[VersionSequence] != SOURCE.[VersionSequence] OR ~ TARGET.[VersionCode] != SOURCE.[VersionCode] OR ~ TARGET.[SourceSite] != SOURCE.[SourceSite]) ~ then ~ UPDATE SET ~ [ProductPool] = SOURCE.[ProductPool], ~ [ProductName] = SOURCE.[ProductName], ~ [FamilyName] = SOURCE.[FamilyName], ~ [VersionSequence] = SOURCE.[VersionSequence], ~ [VersionCode] = SOURCE.[VersionCode], ~ [LastUpdated] = SOURCE.[LastUpdated], ~ [SourceSite] = SOURCE.[SourceSite] ~ when not matched by TARGET then ~ INSERT([LicensedProductID], [ProductPool], [ProductName], [FamilyName], [VersionSequence], [VersionCode], ~ [LastUpdated], [SourceSite]) ~ VALUES(SOURCE.[LicensedProductID], SOURCE.[ProductPool], SOURCE.[ProductName], ~ SOURCE.[FamilyName], SOURCE.[VersionSequence], SOURCE.[VersionCode], ~ SOURCE.[LastUpdated], SOURCE.[SourceSite]); ~ TRUNCATE TABLE tempdb.dbo.temp_LU_LicensedProduct ~> Configuration Manager Setup 5/9/2017 10:57:20 AM 3304 (0x0CE8) ERROR: Failed to execute SQL Server script: MERGE [dbo].[LU_LicensedProduct] AS TARGET ~ using (select [LicensedProductID], [ProductPool], [ProductName], ~ [FamilyName], [VersionSequence], [VersionCode], ~ GETUTCDATE() , N'$CD' ~ from tempdb.dbo.temp_LU_LicensedProduct) ~ as SOURCE ( [LicensedProductID], [ProductPool], [ProductName], ~ [FamilyName], [VersionSequence], [VersionCode], ~ [LastUpdated], [SourceSite]) ~ ON SOURCE.[LicensedProductID] = TARGET.[LicensedProductID] ~ when matched and (~ TARGET.[ProductPool] != SOURCE.[ProductPool] OR ~ TARGET.[ProductName] != SOURCE.[ProductName] OR ~ TARGET.[FamilyName] != SOURCE.[FamilyName] OR ~ TARGET.[VersionSequence] != SOURCE.[VersionSequence] OR ~ TARGET.[VersionCode] != SOURCE.[VersionCode] OR ~ TARGET.[SourceSite] != SOURCE.[SourceSite]) ~ then ~ UPDATE SET ~ [ProductPool] = SOURCE.[ProductPool], ~ [ProductName] = SOURCE.[ProductName], ~ [FamilyName] = SOURCE.[FamilyName], ~ [VersionSequence] = SOURCE.[VersionSequence], ~ [VersionCode] = SOURCE.[VersionCode], ~ [LastUpdated] = SOURCE.[LastUpdated], ~ [SourceSite] = SOURCE.[SourceSite] ~ when not matched by TARGET then ~ INSERT([LicensedProductID], [ProductPool], [ProductName], [FamilyName], [VersionSequence], [VersionCode], ~ [LastUpdated], [SourceSite]) ~ VALUES(SOURCE.[LicensedProductID], SOURCE.[ProductPool], SOURCE.[ProductName], ~ SOURCE.[FamilyName], SOURCE.[VersionSequence], SOURCE.[VersionCode], ~ SOURCE.[LastUpdated], SOURCE.[SourceSite]); ~ TRUNCATE TABLE tempdb.dbo.temp_LU_LicensedProduct Configuration Manager Setup 5/9/2017 10:57:20 AM 3304 (0x0CE8) ERROR: SQL Server error: <> Configuration Manager Setup 5/9/2017 10:57:20 AM 3304 (0x0CE8) ERROR: FAILED to import data to table LU_LicensedProduct Configuration Manager Setup 5/9/2017 10:57:21 AM 3304 (0x0CE8) ERROR: Failed to import data from CSV files Configuration Manager Setup 5/9/2017 10:57:21 AM 3304 (0x0CE8) ERROR: Failed to import Asset Intelligence data into the site database. Configuration Manager Setup 5/9/2017 10:57:21 AM 3304 (0x0CE8) <05-09-2017 11:01:01> Failed to create process of SetupWpf.exe. return value 1 1/1/1601 12:00:00 AM 1991659531 (0x76B6500B) I'm waiting for MS to get back to me ,but wondering if you ever had this issue before. Thanks

Hi There any one upgraded sccm 2012 sp1 to sccm 2012 R2? i need to upgrade it on production. any suggestions would be appreciated. Regards Ravi

Hi, We have SCCM 2007 R3 with FEP 2010 installed. And its integrated with SCCM. How can we upgrade SCCM 2007 to 2012 with FEP 2010 installed? Thanks Prakash