-
Understanding the Citrix Virtual Apps and Desktops Administration Model
-
-
-
-
-
-
-
-
-
-
-
-
-
Set-OrchDBCredentials
-
-
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Set-OrchDBCredentials
Configures the database server SQL credentials for the Orchestration Service.
Syntax
Set-OrchDBCredentials
[-Credentials] <PSCredential>
[-LoggingId <Guid>]
[<CitrixCommonParameters>]
[<CommonParameters>]
<!--NeedCopy-->
Set-OrchDBCredentials
[-Login] <String>
[-Password] <SecureString>
[-LoggingId <Guid>]
[<CitrixCommonParameters>]
[<CommonParameters>]
<!--NeedCopy-->
Description
Specifies SQL credentials to be used by the currently selected Citrix Orchestration Service instance to authenticate with the database server. By default Windows authentication is used and no SQL credentials are required.
If used, SQL credentials must be specified before the service’s schema is obtained and created, and before the database connection string is set. The credentials must also be specified for each additional Orchestration Service prior to it being added to the site.
If the database connection string is already set and Windows authentication is in use, it is not possible to specify SQL credentials, however, if SQL credentials are already in use then they can be changed.
The current service instance is the one on the local machine, or the one most recently specified using the -AdminAddress parameter of a Orchestration SDK cmdlet.
Examples
EXAMPLE 1
Prompts for SQL credentials and sets them for use by the current service instance.
Set-OrchDBCredentials
<!--NeedCopy-->
EXAMPLE 2
Prompts for SQL credentials and sets them for use by the current service instance. This form is useful where the same credentials are being used multiple times.
$sqlCred = Get-Credential
Set-OrchDBCredentials $sqlCred
<!--NeedCopy-->
EXAMPLE 3
Sets the SQL credentials to the explicitly specified login and password values.
$password = ConvertTo-SecureString 'P@ssW0rd' -AsPlainText -Force
Set-OrchDBCredentials 'CvadLogin' $password
<!--NeedCopy-->
EXAMPLE 4
Clears previously set SQL credentials and reverts to use of the default Windows authentication. This can only be done if no connection string is set.
Set-OrchDBCredentials $null
<!--NeedCopy-->
Parameters
-Credentials
A PSCredential object containing the SQL credentials to be used. This can be created using the Get-Credential cmdlet. The credentials required are the SQL server login and its associated password.
| Type: | PSCredential |
| Position: | 2 |
| Default value: | None |
| Required: | True |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-Login
The SQL login to be used for SQL authentication.
| Type: | String |
| Position: | 2 |
| Default value: | None |
| Required: | True |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-Password
The password to be used for SQL authentication.
| Type: | SecureString |
| Position: | 3 |
| Default value: | None |
| Required: | True |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-LoggingId
Specifies the identifier of the high-level operation this cmdlet call forms a part of. Citrix Studio and Director typically create high-level operations. PowerShell scripts can also wrap a series of cmdlet calls in a high-level operation by way of the Start-LogHighLevelOperation and Stop-LogHighLevelOperation cmdlets.
| Type: | Guid |
| Position: | Named |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
CitrixCommonParameters
This cmdlet supports the common Citrix parameters: -AdminAddress, -AdminClientIP, -BearerToken, -TraceParent, -TraceState and -VirtualSiteId. For more information, see about_CitrixCommonParameters.
CommonParameters
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters.
Inputs
None
You cannot pipe input into this cmdlet.
Outputs
None
By default, this cmdlet returns no output.
Related Links
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.