This file is generated AFTER logs are already copied, so it must be put in f. Results.xml - Just the error\success log of the entire TS, trying to find the failures in BDD\SMSTS.log was always a pain so having this makes it easy to see what is failing during a TS, then using that to dig into other logs for specific failure codes\reasons helps. It shouldn't matter much where they are put as they shouldn't be used in these files elsewhere. I did declare all my variables at the beginning of the functions, but for simplicity they are shown in the code\screenshots. I'm running MDT 8456, should work for most recent versions but I've not tested on older versions. I wanted BIOS update logs along with a few others, so spent some time to get these saved centrally for QA purposes. I did this some time ago to get more info and usability from logs. If you have suggestions for the sidebar, let us know! We're always looking for great resources.įair warning, unless you know what you are doing and how to fix it, or have a test\lab deployment server built, I recommend not trying this. SCConfigMgr (previously known as DeployEverything). ![]() Repeat offenders of any of the above rules will be banned.Ī few blogs that can help you get started if you're new to MDT or you need help on specific deployment issues: Be here to help others, not hurl insults across the room. We will never over-moderate, but just don't be a jackass. Mod-discretion on this one for heavily reported posts.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |