Collection is improper word

[Deltron61]

The word "Collection" is incorrect, the real word is "Farm," or possibly "Pool"

The collection would be a third parameter specified. For example, when the broker is HOCRDS01.OLVBVS.LOCAL, Adding the session host to it does not add to its "Collection." rather pool or farm. The collection msut otherwise be specified.

here are example outputs of these commands

Get-RDSessionCollection:

CollectionName Size ResourceType CollectionType CollectionDescription

---

OLVC Apps 2 RemoteApp programs PooledUnmanaged
eCR 2 RemoteApp programs PooledUnmanaged
OLVHS Apps 1 RemoteApp programs PooledUnmanaged
OLVBVS Network (RDSERV) 1 Remote Desktop PooledUnmanaged RDSERV Remote Desktop Sessions

Get-RDSessionHost:

CollectionName SessionHost NewConnect
ionAllowed

---

OLVHS Apps BVSRDS03.OLVBVS.local Yes
eCR BVSRDS01.OLVBVS.local Yes
eCR BVSRDS02.OLVBVS.local Yes
OLVC Apps HOCRDS02.OLVBVS.local Yes
OLVC Apps HOCRDS03.OLVBVS.local Yes
OLVBVS Network (RDSERV) RDSERV.OLVBVS.local Yes

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: a262c79c-68c5-c90a-d6b8-62eb287b2aaa
• Version Independent ID: 43b92fd7-7262-08c7-ac0a-595533534d9d
• Content: Add-RDSessionHost (RDMgmt)
• Content Source: docset/winserver2022-ps/rdmgmt/Add-RDSessionHost.md
• Product: w10
• Technology: windows
• GitHub Login: @JasonGerend
• Microsoft Alias: jgerend

[officedocspr5]

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.

As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.

If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.

With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.

Here's what the new experience looks like.

Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.

First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful	Article was unhelpful

Finally, select Submit and you're done!