> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-powershell-api-guide/parallels-ras-powershell-admin-module/commands/get-rasvcenterdatastores.md).

# Get-RASVCenterDatastores

## NAME

Get-RASVCenterDatastores

## SYNOPSIS

The cmdlet returns a list of VCenter Datastores.

## SYNTAX

**Get-RASVCenterDatastores** \[[ProviderId](#providerid-string)] *(uint)* \[*(*[*CommonParameters*](#commonparameters-string)*)*] \*\*

**Get-RASVCenterDatastores** \[[TemplateId](#templateid-string)] *(uint)* \[[TemplateObjType](#templateobjtype-string)] {RDSTemplate | VDITemplate | AVDTemplate} \[*(*[*CommonParameters*](#commonparameters-string)*)*] \*\*

## DESCRIPTION

The cmdlet returns a list of VCenter Datastores.

## PARAMETERS

## ProviderId (uint)

Provider ID from which to retrieve the VCenter Datastores.

```
        Required?                    true

        Position?                    0

        Default value                0

        Accept pipeline input?       false

        Accept wildcard characters?  false
```

## TemplateId (uint)

Template ID from which to retrieve the VCenter Datastores.

```
        Required?                    true

        Position?                    0

        Default value                0

        Accept pipeline input?       false

        Accept wildcard characters?  false
```

## TemplateObjType ([TemplateObjType](/landing/ras-powershell-api-guide/parallels-ras-powershell-admin-module/types/templateobjtype.md))

Template Type from which to retrieve the VCenter Datastores.

Supported values: RDSTemplate, VDITemplate.

Possible values: RDSTemplate, VDITemplate, AVDTemplate

```
        Required?                    true

        Position?                    1

        Default value                0

        Accept pipeline input?       false

        Accept wildcard characters?  false
```

(CommonParameters)

```
        This cmdlet supports the common parameters: Verbose, Debug,

        ErrorAction, ErrorVariable, WarningAction, WarningVariable,

        OutBuffer, PipelineVariable, and OutVariable. For more information, see 

        about_CommonParameters documentation. 
```

## INPUTS

-none-

## OUTPUTS

[VCenterDatastore](/landing/ras-powershell-api-guide/parallels-ras-powershell-admin-module/types/vcenterdatastore.md)

**---------- EXAMPLE 1 ----------**

Get-RASVCenterDatastores -ProviderId 1

Retrieves a list of Datastores that are available to the specified Provider.\
**---------- EXAMPLE 2 ----------**

Get-RASVCenterDatastores -TemplateId 2 -TemplateType RDSTemplate

Retrieves a list of Datastores that are available to the specified Template.

## RELATED LINKS

-none-


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parallels.com/landing/ras-powershell-api-guide/parallels-ras-powershell-admin-module/commands/get-rasvcenterdatastores.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.