1,382 votesplanned · AdminMark Silvey - ConfigMgr Product Team (Engineering Manager, ConfigMgr, System Center Configuration Manager) responded
Saw a working demo of this recently so updating to planned.
Totally agree. Having realtime visibility into what boundaries clients are in RIGHT NOW, and thus which DPs (and peer clients) they will use is critical. We’ve been talking about this internally for awhile. There are innovations on our roadmap in this area.
Thanks for the feedback. We have made some improvements to the task sequence monitoring – adding columns for Exit Code and Action Output to the status view.
We’ve more work to do replacing use of Generic E_FAIL with more meaningful error codes.
Updated by bobmn for sangeev/OSDNicke commented
Spit out the packageid or even better - the friendly name when a content chevk fails...
149 votesNoted · 5 comments · Ideas » Setup and Server Infrastructure · Flag idea as inappropriate… · Admin →
27 votesNicke commented
Forgot to mention:
Main concern with using the PATCH-property today is that the recommended method is either to perform a pre-copy operation to local disk or referencing a UNC-path.
With the pre-copy you obviously need the usage of additional patch files and the copy might not be as effecient as using the download from a local DP (again - copying from a UNC-path) and using the reference to a file-share might not be as effecient as using the download from a local DP.
And since the UNC-path might be in a high-latency / low-bandwidth scenario (VPN through a coffee-shop, the remote office which has no local infrastructure etc etc) a triggered repair would of course try to use this remote patch-file. In such a scenario this is a very common failure:
MSI: Action 1:44:18: InstallFiles. Copying new files ccmsetup 2015-08-02 01:44:18 8560 (0x2170)
MSI: Internal Error 2902. ixfAssemblyCopy ccmsetup 2015-08-02 01:44:20 8560 (0x2170)
MSI: Action 1:44:21: Rollback. Rolling back action: ccmsetup 2015-08-02 01:44:21 8560 (0x2170)