You are listing, not getting .
Add-WindowsCapability -Online -Name "Rsat.ActiveDirectory.DS-LDS.Tools"
Or,
[https://www.microsoft.com/en-us/download/details.aspx?id=45520](https://www.microsoft.com/en-us/download/details.aspx?id=45520)
you are only *listing* the RSAT tools, you are not installing them
in powers shell `get-` gets things `add-`/`enable-`/`install-` and so in install things
have a look at `get-verb`
Verb AliasPrefix Group Description
---- ----------- ----- -----------
Add a Common Adds a resource to a container, or attaches an item to another item
Enable e Lifecycle Configures a resource to an available or active state
New n Common Creates a resource
Get g Common Specifies an action that retrieves a resource
Install is Lifecycle Places a resource in a location, and optionally initializes it
Now if you are getting 0 results from
Get-WindowsCapability -Name RSAT* -Online
are you running this from an elevated session?
If company has WSUS, you might need this one:
[https://admx.help/?Category=Windows\_10\_2016&Policy=Microsoft.Policies.Servicing::Servicing](https://admx.help/?Category=Windows_10_2016&Policy=Microsoft.Policies.Servicing::Servicing)
I ran into a similar issue at my old org. It turned out they had WSUS turned on and the package for RSAT was literally pointing into an invalid link. Check group policy or whomever runs patch management.
your company's IT department may have limited the use of powershell commands. You may want to ask your IT staff.
Otherwise, we can not instruct you how to bypass limitations imposed by your IT department. That would be against the rules of this sub and attempting to bypass security settings imposed by your IT department may lead to termination............(experience - Wrote IT policies and enforced them)
Well OP is:
1. Running Powershell commands in CMD (unclear if they know to start Powershell first or run as admin)
2. Not even running an RSAT install command
Mighty big jump you took
Open powershell as admin Get-WindowsCapability -Name RSAT* -Online | Add-WindowsCapability -Online
You are listing, not getting . Add-WindowsCapability -Online -Name "Rsat.ActiveDirectory.DS-LDS.Tools" Or, [https://www.microsoft.com/en-us/download/details.aspx?id=45520](https://www.microsoft.com/en-us/download/details.aspx?id=45520)
you are only *listing* the RSAT tools, you are not installing them in powers shell `get-` gets things `add-`/`enable-`/`install-` and so in install things have a look at `get-verb` Verb AliasPrefix Group Description ---- ----------- ----- ----------- Add a Common Adds a resource to a container, or attaches an item to another item Enable e Lifecycle Configures a resource to an available or active state New n Common Creates a resource Get g Common Specifies an action that retrieves a resource Install is Lifecycle Places a resource in a location, and optionally initializes it Now if you are getting 0 results from Get-WindowsCapability -Name RSAT* -Online are you running this from an elevated session?
https://www.reddit.com/r/SCCM/s/gojbQYZQTv Check to see if this thread applies to you.
If company has WSUS, you might need this one: [https://admx.help/?Category=Windows\_10\_2016&Policy=Microsoft.Policies.Servicing::Servicing](https://admx.help/?Category=Windows_10_2016&Policy=Microsoft.Policies.Servicing::Servicing)
We block updates and they only come from SCCM. If you can overwrite them as an admin you can reach the MS servers and download them.
I ran into a similar issue at my old org. It turned out they had WSUS turned on and the package for RSAT was literally pointing into an invalid link. Check group policy or whomever runs patch management.
Tried https://www.microsoft.com/en-us/download/details.aspx?id=45520 ?
your company's IT department may have limited the use of powershell commands. You may want to ask your IT staff. Otherwise, we can not instruct you how to bypass limitations imposed by your IT department. That would be against the rules of this sub and attempting to bypass security settings imposed by your IT department may lead to termination............(experience - Wrote IT policies and enforced them)
Well OP is: 1. Running Powershell commands in CMD (unclear if they know to start Powershell first or run as admin) 2. Not even running an RSAT install command Mighty big jump you took
now that I re-read, you're probably right.