MicrosoftThis was originally posted in 2008. This is a solution to an obvious basic design flaw to system center deployments. (Yes, not being able to recover logs after a failure is an obvious flaw of careless design, that is not up for discussion.) This is a feature set that should have been stock, handled natively by system center out of the box. Yet, after 15 years we still have to create a patchwork custom user solution to getting the logs from a server software that depends on a centralized server that could very easily just collect the logs and collate them in the configuration manager console for us before the machine reboots? Who is developing this garbage? If Microsoft is going to depend on their user base to solve basic design errors, then leave it up to us to implement them, maybe the software should be free and open source instead of cash-gouging money pit that we are forced into since they deprecated their other small/medium solutions for Windows 11 deployment.
I appreciate the work around. I'm furious that the answer is a work around instead of a stock feature that was obviously needed on first release and hasn't been corrected in over a decade.
