SOLVED CONFIGURATION MANAGER 2107 INSTALL UPDATE PACKAGE IS GRAYOUT

Status
Not open for further replies.

PASCAL JOURDAN

Well-Known Member
45
2
8
Hy everyone
I recently did a prerequisite check for configuration manager 2013 hotfix Rollup kb10036164. the prerequisite is ok. However, the installation was not followed by the install update pack. since this observation version 2107 has arrived in ready to install.
the system is blocked because grayed out and I cannot validate the last version because 2103 is suspended for installation.
How to purge the update system proprerly
Thank you for your feedback
Pascal
 

Attachments

  • 1.PNG
    1.PNG
    367.7 KB · Views: 3
  • 2.PNG
    2.PNG
    248.5 KB · Views: 3
  • 3.PNG
    3.PNG
    182.3 KB · Views: 3
Solution
HI Prajwal,
1 I deleted first package because pb not resolved and reset primary package configuration manager 2013 hotfix rollup (kb10036164.)
2 By refresh update in console manager After few minutes the two last version was ready to do prerequsite check .
3 I run the prerequiste check for last version and prefered this option .
in progress now succesfully !!!!
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Command to deleted :
-a---- 4/18/2021 4:40 AM 71544 CMUpdateReset.exe


PS C:\Program Files\Microsoft Configuration Manager\cd.latest\SMSSETUP\TOOLS\CMUpdateReset> .\CMUpdateReset.exe -s...

Prajwal Desai

Forum Owner
Staff member
3,698
441
183
Yes, until the SCCM 2103 hotfix completes the prerequisite check step, you cannot install other updates. Can you check ConfigMgrPrereq.log to see what's happening.
 
OP
PASCAL JOURDAN

PASCAL JOURDAN

Well-Known Member
45
2
8
Hi prajwal ,

After control ADK 10 may be the pb
Need to install it will resolved the pb ?
tks for you answer .
find below log .
Best regards
Pascal
 
OP
PASCAL JOURDAN

PASCAL JOURDAN

Well-Known Member
45
2
8
HI Prajwal,
1 I deleted first package because pb not resolved and reset primary package configuration manager 2013 hotfix rollup (kb10036164.)
2 By refresh update in console manager After few minutes the two last version was ready to do prerequsite check .
3 I run the prerequiste check for last version and prefered this option .
in progress now succesfully !!!!
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Command to deleted :
-a---- 4/18/2021 4:40 AM 71544 CMUpdateReset.exe


PS C:\Program Files\Microsoft Configuration Manager\cd.latest\SMSSETUP\TOOLS\CMUpdateReset> .\CMUpdateReset.exe -s LRESVVRMGMT10.lealreunion.local -D CM_LRE -P afba5155-1a37-4a71-adc9-9a9e0b1d399a
[Warning]
You can use this tool when an in-console update has not yet installed and is in a failed state. A failed state can mean the update download remains in progress but is stuck and taking an excessively long time, perhaps hours longer than your historical expectations for update packages of similar size. It can also be a failure to replicate the update to child primary sites. When you run the tool, it runs against the update that you specify. If the package is in pre-installation state, it will delete it. If package is in replicating state, it will reinitiate replication. Are you sure you want to run the tool? Enter Y for Yes and N for No.
y
Running CMUpdateReset.exe tool ...
Verified that the SQL server FQDN belongs to the top level site.
Verified that the site servers run version 1606 or later.

Verified that replication is active.

Package is in pre-installation state. Attempting to clean up the package.

Verified that the service connection point is installed on the top level site.
Verified that the account has permission to service connection point share.
Verified that the account has permission to the inboxes\hman.box folder.

Service SMS_EXECUTIVE is Running on machine LRESVVRMGMT10.lealreunion.local.
Verified that service SMS_EXECUTIVE is running on machine LRESVVRMGMT10.lealreunion.local.

Service CONFIGURATION_MANAGER_UPDATE is Running on machine LRESVVRMGMT10.lealreunion.local.
Verified that service CONFIGURATION_MANAGER_UPDATE is running on machine LRESVVRMGMT10.lealreunion.local.

Verified that the package is not in post-replication state for all the child sites (if any).
Marking package in the package distribution list as deleted.

(1 row(s) affected.)
Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)
Marked package in the package distribution list as deleted.

Deleting update package afba5155-1a37-4a71-adc9-9a9e0b1d399a from EasySetupSettings table on site server LRESVVRMGMT10.lealreunion.local.

(1 row(s) affected.)
Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)
Update package is deleted from EasySetupSettings table.

Deleting update package afba5155-1a37-4a71-adc9-9a9e0b1d399a from cm_updatepackageSiteStatus table on site server LRESVVRMGMT10.lealreunion.local.

(1 row(s) affected.)
Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)
Update package is deleted from cm_updatepackageSiteStatus table.

Deleting update package afba5155-1a37-4a71-adc9-9a9e0b1d399a from CM_UpdatePackage_MonitoringStatus table on site server LRESVVRMGMT10.lealreunion.local.

(2 row(s) affected.)
Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)
Update package is deleted from cm_updatepackageSiteStatus table.

Verifying whether the table entries for package afba5155-1a37-4a71-adc9-9a9e0b1d399a is deleted on site server LRESVVRMGMT10.lealreunion.local.

Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)
Restarting replication from the top level site.

(1 row(s) affected.)
Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)
Replication is restarted on the top level site. Please follow the flowchart (https://docs.microsoft.com/sccm/core/servers/manage/update-replication-flowchart) to troubleshoot additional issues.
[Success]Successfully ran the CMUpdateReset.exe tool. If the tool deleted the package (check Updates and Servicing to see if the package is listed), you must restart the SMS_EXECUTIVE service on the top level site. Or, use Check for Update in console to redownload the package.
If the package is reinitiating replication or installation, DO NOT restart the SMS_EXECUTIVE service. You can use the flowchart at (https://docs.microsoft.com/sccm/core/servers/manage/update-replication-flowchart) to troubleshoot additional issues..
PS C:\Program Files\Microsoft Configuration Manager\cd.latest\SMSSETUP\TOOLS\CMUpdateReset>
 

Attachments

  • 4.PNG
    4.PNG
    291.8 KB · Views: 2
  • 7.PNG
    7.PNG
    125.6 KB · Views: 2
  • 6.PNG
    6.PNG
    361.4 KB · Views: 1
  • 5.PNG
    5.PNG
    219.5 KB · Views: 2
Solution
Status
Not open for further replies.

Forum statistics

Threads
4,514
Messages
17,668
Members
9,104
Latest member
KoreBreach