Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

More useful OSD failure window

It would be super helpful if the OSD failure window can actually provide useful information - rather than just the error code of the last executed step. At least also display the name of the step where the failure occurred. I often get a screenshot of the error code and that doesn't help me at all.

So often when I troubleshoot OSD, it is with computers in remote site. While walking someone over phone through launching command prompt, cd here, copy these files there, etc - it is such a tedious process.

I would love to see a way to collect & zip up all the client logs, and also grab a bunch of basic hardware info (cpu/sn/host name/ip/etc) into a troubleshoot file that can then be copied over to SMB file share of your choice.

10 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Luke shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

1 comment

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • Tim commented  ·   ·  Flag as inappropriate

    A step or option to collect selected logs & machine info and dump it all in a network share would be great.
    Or even a simple GUI that pops up on failure that displays a list of available info and an option to select a save location.

Feedback and Knowledge Base