Skip to content
Branch: master
Find file History
brookspeppin Update Create-Win10-Media.ps1
Fixed getting windows image info bug
Latest commit 1928b73 Aug 9, 2019
Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
Custom Settings Updated Chrome sample to new working sample Aug 7, 2019
Product Provisioning Revert "Revert "Merge branch 'master' of https://github.com/vmwaresam… Apr 29, 2019
Sensors Added BranchCache Mode Sensor Aug 6, 2019
Tools & Utilities Update Create-Win10-Media.ps1 Aug 8, 2019
README.md

README.md

EUC-samples

Windows-Samples

This section of the EUC-samples repository contains samples relating to Microsoft Windows endpoint management.

Some examples of items to submit for consideration and use by the community:

  • Custom XML Profile Payloads (use VMware Policy Builder for easy Windows 10 Custom XML generation)
  • Workspace ONE Sensors Samples
  • Scripts for Product Provisioning
  • Scripts to use as helpful tools

Submitting samples

Required Information

The following information must be included in the README.md or in the sample docstring in case README already exists in same folder.

  • Author Name
    • This can include full name, email address or other identifiable piece of information that would allow interested parties to contact author with questions.
  • Date
    • Date the sample was originally written
  • Minimal/High Level Description
    • What does the sample do ?
  • Any KNOWN limitations or dependencies

Suggested Information

The following information should be included when possible. Inclusion of information provides valuable information to consumers of the resource.

  • VMWare Workspace ONE UEM version against which the sample was developed/tested
  • Client Operating System version against which the sample was developed/tested (e.g. Windows Build number, or macOS Version and Build Number)
  • Language (Bash/Python/Powershell) version against which the sample was developed/tested

Contribution Process

Follow the GitHub process

  • Please use one branch per sample or change-set
  • Please use one commit and pull request per sample
  • Please post the sample output along with the pull request
  • If you include a license with your sample, use the project license

Code Style

We won't actively enforce any "official" style guides, but do ask that you do what you can to:

  • Make your samples easily readable
  • Make your samples easily reusable
  • Include in-line comments to help with readability

Resource Maintenance

Maintenance Ownership

Maintenance of any and all submitted samples is to be performed by the community. If you can make a sample better, please feel free to submit a pull request to improve it!

Filing Issues

Any bugs or other issues should be filed within GitHub by way of the repository’s Issue Tracker.

Resolving Issues

Any community member can resolve issues within the repository, however only the board member can approve the update. Once approved, assuming the resolution involves a pull request, only a board member will be able to merge and close the request.

VMware Sample Exchange

It is highly recommended to add any and all submitted samples to the VMware Sample Exchange: https://code.vmware.com/samples

Sample Exchange can be allowed to access your GitHub resources, by way of a linking process, where they can be indexed and searched by the community. There are VMware social media accounts which will advertise resources posted to the site and there's no additional accounts needed, as the VMware Sample Exchange uses MyVMware credentials.

VMware Resources

You can’t perform that action at this time.