Some time ago, I have to update a post about the connection string for mirroring. Since then I have had other requests for connection string manipulations. So they in a post with an update for I will draw 7.6 Availability Groups and script updates.
XenDesktop 7.6
XenDesktop 7.6 introduced to the Analytics Service , which must be his DB connection string updated. The service is responsible for sending information to Citrix as part of CEIP
The only change to the commands in the previous blog, the need to also use cmdlets .:
Set-AnalyticsDBConnection
to update the DbConnection. If you run only after you use:
Set-SfDBConnection
then it should update correctly
Always On Availability Groups
Many customers have begun , Always On Availability Groups to use for their HA database solution. For the most part the use of availability groups is invisible to XenDesktop. However, there is a recommended setting that Microsoft say should be a part of the connection string MultiSubnetFailover = true . The option is recommended both a subnet and multiple subnets environments, and it speeds up recovery when an HA event occurs.
This option is in .NET versions only available that have been patched to close it. Depending on the version of XenDesktop you will use depends on the KB patch you must add support
.Net 3.5 SP1 , Patch with this KB :. Http://support.microsoft .com / kb / 2654347
.Net 4.0 update is recommended at least 4.0.2, but 4.0.3: http://support.microsoft.com/kb / 20211
.Net 4.5 , nothing to mend, the support has been built into this version of .NET.
When you run on a supported version of .NET, you need to update the connection strings. To do this, the changes for mirroring is very similar, you need the connection string zero, it then returns to the same set, but with additional option "; MultiSubnetFailover = true". not support
Tagged: 'MultiSubnetFailover'
Windows 7 or 08 R2, you can get the above error message on the node configuration of Studio. This is because the studio MMC used the .NET 7 and 08 R2 to use 3.5 SP1 runtime on Windows. To avoid the error, you need to apply the patch .Net 3.5 SP1. Note the services the .Net 4.x runtime. (This section was recorded on April 15, 2015)
Updated Script
I have the script also updates since the last post to include the analysis service. While doing so, I also broke the core functions in its own file and created some wrapper scripts to use these functions. New scripts are bundled into a .zip:
https://citrix.sharefile.com/d/sc237fc7d5ed4f0fb
The scripts PowerShell v3 actually need (I can be a part of it in a module and turn might be able to switch PowerShell v2, but is v3 needed to load the core script in the other scripts.)
tested the script on Server 2012 R2, with XenDesktop 7.5 and XenDesktop 7.6. Note that this The scripts provided are as a complete site administrator and local admin PowerShell window
DBConnectionStringFuncs.ps1 - that is the core script, and performs the actual. Job. It contains general functions that the following scripts then with
Change_XD_Failover_Partner_v1.ps1 - .. This is similar to the previous script that I wrote and is used to update the failover partner
Change_XD_To_ConnectionString PS1 - this is done in connection strings passed and uses it to create a very generic version
Change_XD_To_MultiSubnetFailover.ps1 -. This switches the adding and removing MultiSubnetFailover = true. IE is run once and the option is added, run it again, and the options away
Change_XD_To_Null.ps1 -. This is a reset of all connection strings on the local host as something went wrong. Note that because this is the connection strings set to zero, it is actually the ddc in an "initial" enabling state. IE if you run Studio, it will ask if you want to create a website, or accede to another ddc. This is useful, something has not gone right somewhere, and a reset is necessary because then again the connection strings can try set to.
If you do some kind of connection string manipulation, feel free to look at how the Change_XD scripts to perform the functions in DBConnectionStringFuncs.ps1 use
A disclaimer for the script applies. :
ThE SOFTWARE IS PROVIDED "AS IS" without warranty of any kind, either express or implied, INCLUDING, BUT nOT LIMITED TO THE WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER IN THE SOFTWARE.
0 Komentar