Skip to content

Latest commit

 

History

History
47 lines (34 loc) · 2.42 KB

README.md

File metadata and controls

47 lines (34 loc) · 2.42 KB
Raw
    ____      __                      _____ __         ____   _____           _       __      
   /  _/___  / /___  ______  ___     / ___// /_  ___  / / /  / ___/__________(_)___  / /______
   / // __ \/ __/ / / / __ \/ _ \    \__ \/ __ \/ _ \/ / /   \__ \/ ___/ ___/ / __ \/ __/ ___/
 _/ // / / / /_/ /_/ / / / /  __/   ___/ / / / /  __/ / /   ___/ / /__/ /  / / /_/ / /_(__  ) 
/___/_/ /_/\__/\__,_/_/ /_/\___/   /____/_/ /_/\___/_/_/   /____/\___/_/  /_/ .___/\__/____/  
                                                                           /_/

Intune Customer Experience Engineering Shell Script Repo

This repository is for Intune Shell Script Samples. It is maintained by the Microsoft Intune Customer Experience Engineering Team. The samples provided here are for education and showing the art of the possible. You are encouraged to download, test and enhance for your own use.

The Repo is split into scripts for Linux and macOS

   |-Linux
   |---Custom Compliance
   |---Misc
   |
   |-macOS
   |---Apps
   |---Config
   |---Custom Attributes
   |---Custom Profiles

Disclaimer

Understand the impact of each sample script prior to running it; samples should be run in a non-production or "test" environment.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.