In most SCCM 2012 projects, the engineers try to define a folder structure during the concept phase. At the end of the project or already during the implementation they find out, that they have forgotten some cases. Therefore we created a folder structure concept which is tested an already in production.
Our concept is based on two shares:
- Development Share: On this share the package engineers are working. There are all documentations, source files and produced package.
- Deployment Share: When an application is checked in to SCCM the produced package is copied without the documentation to the deployment share. The package engineers have no or only read access to this share. This means if an application is registered in SCCM and perhaps deployed we don’t modify the application, because this could end in an inconsistent environment. In case of a problem in the application package we create a new package version and update all clients to the new version if needed.
This concept also allows us to have different roles:
- SCCM Administrator: Is responsible for registering and deploying(Also pilot deployments) the application to devices.
- Package Engineer: Is creating Packages from Source Binaries, testing and documenting them on the development share.
This is useful if you have outsourced the packaging process for example.
- Build better pilot rings for Updates with MEM Intune - June 13, 2021
- Automatic Intune Documentation evolves to Automatic Microsoft 365 Documentation - May 25, 2021
- Build better pilot rings for Updates with MEMCM - March 14, 2021