├── CONTRIBUTING.md
├── Content
└── VMWare-Horizon-Icon.png
├── EndScript.ps1
├── GlobalVariables.ps1
├── Plugins
├── 00 Initialize
│ └── 00 Connection Plugin for View.ps1
├── 10 General
│ ├── 04 License Status.ps1
│ ├── 05 Connection Servers Status.ps1
│ ├── 06 Security Servers Status.ps1_disabled
│ ├── 07 Composer Servers Status.ps1_disabled
│ └── 08 Event Database Status.ps1
├── 20 Desktop
│ ├── 01 Pool Overview.ps1
│ ├── 10 Automated Pool Desktop Wrong Snapshot.ps1
│ ├── 11 Linked Clone Desktop Pool Information.ps1
│ ├── 12 Full Clone Desktop Pool Status.ps1
│ ├── 13 Dedicated Full Clones Assignment.ps1
│ ├── 14 Manual Desktop Pool Information.ps1
│ └── 15 Instant Clone Desktop Pool Information.ps1
├── 30 Pods
│ └── 00 Pod Health.ps1
├── 40 RDS
│ ├── 01 RDS Farm information.ps1
│ ├── 10 Automated Farm Wrong Snapshot.ps1
│ └── 21 RDS Farm health.ps1
└── 90 Various
│ ├── 01 AD Domain Health Status.ps1
│ ├── 01 SAML Health Status.ps1
│ ├── 02 vCenter Health Status.ps1
│ ├── 03 ESXi Host Health Status.ps1
│ ├── 04 Datastore Health Status.ps1
│ ├── 05 Gateway Health Status.ps1
│ ├── 25 Certificate SSO Connector Health Status.ps1
│ ├── 26 Certificate SSO Domain Health Status.ps1
│ ├── 27 Certificate SSO Template Health Status.ps1
│ └── 28 Certificate SSO Certificate Server Health Status.ps1
├── README.md
├── Select-Plugins.ps1
├── Styles
├── Clarity
│ ├── Header-vmware.png
│ ├── Header.jpg
│ └── Style.ps1
├── CleanGreen
│ ├── Header.jpg
│ └── Style.ps1
└── VMware
│ ├── Header-vmware.png
│ ├── Header.jpg
│ └── Style.ps1
├── plugins.xml
├── vCheck.ps1
└── vCheckUtils.ps1
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | # Contribute to the vCheck-vSphere repository
2 |
3 | Hi! We can't thank you enough for wanting to contribute; the community is what keeps the wheels moving on this awesome project.
4 | All we ask is that you follow some simple guidelines. The roots of these guidelines stem from the developer community and the actual document has been borrowed from [Microsoft's DscResources](https://github.com/PowerShell/DscResources) repository; they did an excellent job putting these guidelines together; why reinvent the wheel?
5 |
6 | ## Using GitHub, Git, and this repository
7 |
8 | We are working on more detailed instructions that outline the basics.
9 |
10 | ## Contributing to the existing vCheck-vSphere repository
11 |
12 | ### Forks and Pull Requests
13 |
14 | GitHub fosters collaboration through the notion of [pull requests](https://help.github.com/articles/using-pull-requests/).
15 | On GitHub, anyone can [fork](https://help.github.com/articles/fork-a-repo/) an existing repository into their own branch where they can make private changes to the original repository.
16 | To contribute these changes back into the original repository, a user simply creates a pull request in order to "request" that the changes be taken "upstream".
17 |
18 | #### Lifecycle of a pull reqeust
19 |
20 | * **Always create pull requests to the `dev` branch of a repository**.
21 | For more information, learn about the [branch structure](#branch-structure) that we are using.
22 |
23 | 
24 |
25 | * When you create a pull request, fill out the description with a summary of what's included in your changes.
26 | If the changes are related to an existing GitHub issue, please reference the issue in your description.
27 | * Once the PR is submitted, we will review your code
28 | * Once the code review is done, and all merge conflicts are resolved, a maintainer will merge your changes.
29 |
30 | ### Contributing to documentation
31 | One of the easiest ways to contribute to a PowerShell project is by helping to write and edit documentation.
32 | All of our documentation hosted on GitHub is written using [GitHub Flavored Markdown](https://help.github.com/articles/github-flavored-markdown/)
33 |
34 | *We are at lest working on shifting things over to GFM, for 'core' documentation. Some things may still live on the GitHub wiki, but using GFM allows the documentation to exist in the repo, so you always have a local copy to reference ;)*
35 |
36 | To [edit an existing file](https://help.github.com/articles/editing-files-in-another-user-s-repository/), simply navigate to it and click the "Edit" button.
37 | GitHub will automatically create your own fork of our repository where you can make your changes.
38 | Once you're finished, save your edits and submit a pull request to get your changes merged upstream.
39 |
40 | If you want to contribute new documentation, first check for [issues tagged as "Documentation"](https://github.com/alanrenouf/vCheck-vSphere/labels/documentation) to make sure you're not duplicating efforts.
41 | If no one seems to be working on what you have planned:
42 | * Open a new issue tagged as "Documentation" to tell others what you're working on
43 | * Create a fork of our repository and start adding new Markdown-based documentation to it
44 | * When you're ready to contribute your documentation, submit a pull request to the *dev* branch
45 |
46 |
47 | #### GitHub Flavored Markdown (GFM)
48 |
49 | All of the articles in this repository use [GitHub Flavored Markdown (GFM)](https://help.github.com/articles/github-flavored-markdown/).
50 |
51 | If you are looking for a good editor, try [Markdown Pad](http://markdownpad.com/) or
52 | GitHub also provides a web interface for Markdown editing with syntax highlighting and the ability to preview changes.
53 |
54 | Some of the more basic GFM syntax includes:
55 |
56 | * **Line breaks vs. paragraphs:** In Markdown there is no HTML `
` or `
2 |
3 |
118 | |
120 |
_HEADER_ |
vCheck v$($vCheckVersion) by Alan Renouf generated on $($ENV:Computername) on $($Date.ToLongDateString()) at $($Date.ToLongTimeString()) |
_TITLE_ |
_COMMENTS_ |
_PLUGINCONTENT_ |
Back To Top 142 | |
124 | |
126 |
127 | |
129 |
_HEADER_ |
vCheck v$($vCheckVersion) by Alan Renouf generated on $($ENV:Computername) on $($Date.ToLongDateString()) at $($Date.ToLongTimeString()) |
_TITLE_ |
_COMMENTS_ |
_PLUGINCONTENT_ |
Back To Top 151 | |