Jump to content


Search the Community

Showing results for tags 'software update deployment'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • Official Forum Supporters
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Windows Server 2008
    • Windows Server 2012
    • Windows Server 2016
    • Windows Server 2019
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 2 results

  1. I will give background about the scenario, we are in the process of Side-by-Side Migration from SCCM 2012 R2 to SCCM 1906 CB. As per the guideline, I have configured the products classification in the new site identical like the old site and synchronized. Now I am at the phase of the migrating Applications, Collections, ADR, Software Update Package and its deployment. For E.g.: I am trying to migrate Office 2010 Software Update Package and its deployment and it’s all associated collection and rules from SCCM 2012 R2 site to SCCM 1906 Site. Migration is failing and the error was that the destination site doesn’t have software updates with unique id: b2f2052b-d652-4895-bc2e-c5105acadb00, 10756e43-6c49-45c1-a897-12b4e89fdc11 Screenshot for your reference below as i couldnt paste it here I have given below a details screenshot of the error from the Migration manager log: The migration manager is complaining that file lib id b2f2052b-d652-4895-bc2e-c5105acadb00 doesn’t exist in the destination hierarchy so it couldn’t move the Office 2010 package from SCCM 2012 to SCCM 1906. I was looking for this update in the all software update group list. I was even unable to find that software update even in the SCCM 2012 R2 Hierarchy, which means that content_id is invalid and stale. It needs to be removed from the package id so the migration manager won’t look into it during migration Below is the screenshot for location the where all the software update deployment package are: When I open this package id, I was able to find all the references of all software update in it: screenshot given below for your reference: If you look at the screenshot above, the Office software deployment package has the reference of a software member (b2f2052b-d652-4895-bc2e-c5105acadb00) in it, so the migration manager is looking for it the new site. However i have checked Microsoft Catalog to see if the above unique_id is what software update, but even it is not in Microsoft Catalog. I think it is a stale unique Id which needs to be removed from the package. Due to the reference still exist in the Package, the migration manager is not able to migrate the package from SCCM 2012 R2 to SCCM 1906 CB. PS: I have used content library clean-up tool but it freed up only the orphaned contents in the DP. But it didn't remove the stale references from the Package. Also I have validated the package and even redistributed the content again to the DP to see if it fixes the issue. I used t-sql query to find the article Id and title information from in the SQL db, but there is no information. can you guys help me to fix the issue. The main agenda is to migrate all contents from current hierarchy to the new hierarchy.
  2. I am getting a message as "Not refreshing update presence state as error CI Info status received" when installing patches using Software Center. below is a snippet from Updatesdeployment.log ................................................................................​................................................................................​................................................................................​................................................. Raising client SDK event for class CCM_SoftwareUpdate, instance CCM_SoftwareUpdate.UpdateID="Site_5C2C7B9A-CCFC-436C-8EAB-8BB1CC0D9CA5/SUM_79270a15-031c-4c07-81a7-b1dcc0eea6d9", actionType 1l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l UpdatesDeploymentAgent Not refreshing update presence state as error CI Info status received UpdatesDeploymentAgent Raising client SDK event for class CCM_SoftwareUpdate, instance CCM_SoftwareUpdate.UpdateID="Site_5C2C7B9A-CCFC-436C-8EAB-8BB1CC0D9CA5/SUM_79270a15-031c-4c07-81a7-b1dcc0eea6d9", actionType 11l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l UpdatesDeploymentAgent CUpdatesJob({A811BD6B-4CFE-4398-BD2A-8F430649F9EF}): Delete job from WMI UpdatesDeploymentAgent IsRebootSetForScheduledUpdate - Scheduled update Site_5C2C7B9A-CCFC-436C-8EAB-8BB1CC0D9CA5/SUM_040f13b3-dce2-44cb-9673-5f2b00bab0f5 - Job options = 0 RebootImmediately = False UpdatesDeploymentAgent IsRebootSetForScheduledUpdate - Scheduled update Site_5C2C7B9A-CCFC-436C-8EAB-8BB1CC0D9CA5/SUM_e24d2431-1b85-495e-8b75-c339cdfc919b - Job options = 0 RebootImmediately = False UpdatesDeploymentAgent IsRebootSetForScheduledUpdate - Scheduled update Site_5C2C7B9A-CCFC-436C-8EAB-8BB1CC0D9CA5/SUM_6f0b3990-56cc-4bc0-87bb-c54d7fafaac8 - Job options = 0 RebootImmediately = False UpdatesDeploymentAgent IsRebootSetForScheduledUpdate - Scheduled update Site_5C2C7B9A-CCFC-436C-8EAB-8BB1CC0D9CA5/SUM_bbb2c1d5-4809-48ad-b569-bd9ea6617fa4 - Job options = 0 RebootImmediately = False UpdatesDeploymentAgent No installations in pipeline, notify reboot. UpdatesDeploymentAgent 9/15/2014 3:42:48 PM 6248 (0x1868) Notify reboot UpdatesDeploymentAgent EnumerateUpdates for action (UpdateActionInstall) - Total actionable updates = 79 UpdatesDeploymentAgent ................................................................................​................................................................................​................................................................................​................................................. Below are the error messages in WindowsUpdate.log ...............................................................................​................................................................................​................................................................................​................................................. 2014-09-17 12:32:45:154 6372 ce0 Handler CBS package identity: Package_for_KB2966825~31bf3856ad364e35~amd64~~6.2.1.4 2014-09-17 12:32:45:163 6372 ce0 Handler Installing self-contained with source=C:\Windows\SoftwareDistribution\Download\be5ae942269a9467c89b7ef1fa4ed938\windows8-rt-kb2966825-x64.cab, workingdir=C: \Windows\SoftwareDistribution\Download\be5ae942269a9467c89b7ef1fa4ed938\inst 2014-09-17 12:42:44:413 6372 20d0 Handler CUHCbsHandler::Cancel called with fReleaseThreadNow=0 2014-09-17 12:43:20:571 6372 17b4 Handler FATAL: CBS called Error with 0x800f0821, 2014-09-17 12:43:36:642 6372 ce0 Handler FATAL: Completed install of CBS update with type=2, requiresReboot=0, installerError=0, hr=0x80242008 2014-09-17 12:43:37:686 6372 ce0 Handler ::::::::: 2014-09-17 12:43:37:686 6372 ce0 Handler :: END :: Handler: CBS Install 2014-09-17 12:43:37:686 6372 ce0 Handler ::::::::::::: 2014-09-17 12:43:37:746 872 df0 Agent * WARNING: Exit code = 0x8024000B 2014-09-17 12:43:37:747 872 df0 Agent ********* 2014-09-17 12:43:37:747 872 df0 Agent ** END ** Agent: Installing updates [CallerId = CcmExec] 2014-09-17 12:43:37:747 872 df0 Agent ************* 2014-09-17 12:43:37:747 872 df0 Agent WARNING: WU client failed installing updates with error 0x8024000b 2014-09-17 12:43:37:747 3164 dd4 COMAPI >>-- RESUMED -- COMAPI: Install [ClientId = CcmExec] 2014-09-17 12:43:37:747 3164 dd4 COMAPI - Install call aborted 2014-09-17 12:43:37:748 3164 dd4 COMAPI - Reboot required = No 2014-09-17 12:43:37:748 3164 dd4 COMAPI - WARNING: Exit code = 0x80240FFF; Call error code = 0x8024000B 2014-09-17 12:43:37:748 3164 dd4 COMAPI --------- 2014-09-17 12:43:37:748 3164 dd4 COMAPI -- END -- COMAPI: Install [ClientId = CcmExec] ................................................................................​................................................................................​................................................................................​................................................. When I try to install the patch manually directly on the machine, it works but not via SCCM, the issue is on Windows 2012 Server Standard. There are 3+ servers they fail 2-3 patches but install rest of them. Few patches are common but few are not.
×
×
  • Create New...