This is the third post in a series of Best Practice recommendations, which I like to share with everyone. In the first part I have shared some pictures and descriptions for a folder structure. Now I will extend this to a poster of an actual version.
The intention to write this series of blog posts are, that I often see customer which have no naming convention behind their Configuration Manager projects. This means they didn’t have clear rules how to name a specific object in ConfigMgr. The result is often a little mess with .old, temp and files, which are never found again, because nobody would search them at their current location.
So we have created some basic rules which are tested in many projects and help the Configuration Manager administrators during their daily business and project.
If you have some inputs to optimize these poster, please contact me over any media…
Other Best Practice Blog Posts:
Latest posts by Thomas Kurth
- Configure Intune to deploy Microsoft Defender ATP for macOS - November 9, 2019
- Cleanup duplicated devices in Intune - September 17, 2019
- ConfigMgr with missing Boundaries is a content delivery nightmare - September 16, 2019