You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/mem/configmgr/setup-migrate-backup-recovery/understand-troubleshoot-updates-servicing.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -190,8 +190,8 @@ DMPDownloader sends the `3 (VERIFIED_MANIFEST)` state message to confirm that th
190
190
191
191
Finally, DMPDownloader renames ConfigMgr.Update.Manifest.cab to ___CABConfigMgr.Update.Manifest.MCM, and then moves the renamed file to one of the following locations:
192
192
193
-
- If the SCP is remote from the Site Server, DMPDownloader stores the file at MP\\OUTBOXES\\MCM.box. The MPFDM component moves the file to the Site Server.
194
-
- If the SCP is co-located with the Site Server, the file is saved directly to inboxes\\hman.box\\ForwardingMsg.
193
+
- If the SCP is remote from the Site Server, DMPDownloader stores the file at MP\\OUTBOXES\\MCM.box. The MP File Dispatch manager (MPFDM) moves the file to the site server.
194
+
- If the SCP is co-located with the site server, the file is saved directly to inboxes\\hman.box\\ForwardingMsg.
195
195
196
196
During this process, DMPDownloader logs entries that resemble the following excerpt:
197
197
@@ -272,7 +272,7 @@ The following steps summarize this troubleshooting process. The steps vary depen
272
272
- **SCP in Online mode**
273
273
274
274
1. On the SCP, check the DMPDownloader.log file for any error messages that the DMPDownloader generated while it downloaded and processed the manifest .cab file.
275
-
1. Verify that the HMAN.log file contains entries that resemble the following excerpt:
275
+
1. Verify that the HMAN.log file contains entries that resemble the following excerpt:
276
276
277
277
```output
278
278
Extracting file E:\ConfigMgr\inboxes\hman.box\CFD\ConfigMgr.Update.Manifest.CAB to E:\ConfigMgr\CMUStaging\~
@@ -478,7 +478,7 @@ As a result of the previous step, the \\EasySetupPayload shared folder contains
478
478
479
479
Depending on the SCP configuration, DMPDownloader puts a so-called CMU file in one of the following locations:
480
480
481
-
- If the SCP is remote from the Site Server, DMPDownloader puts the file in MP\\OUTBOXES\\MCM.box. Afterwards, the MP File Dispatch manager (MPFDM) moves the file to inboxes\\hman.box\\ForwardingMsg for the Site Server.
481
+
- If the SCP is remote from the Site Server, DMPDownloader puts the file in MP\\OUTBOXES\\MCM.box. Afterwards, MPFDM moves the file to inboxes\\hman.box\\ForwardingMsg for the Site Server.
482
482
- If the SCP is collocated with the Site Server, DMPDownloader saves the file directly to the inboxes\\hman.box\\ForwardingMsg folder.
483
483
484
484
The file has a .mcm extension, and contains the information that marks the state of the update package as `State="262146"` (also known as `"DOWNLOAD_SUCCESS"`). The corresponding log entries resemble the following excerpt:
0 commit comments