Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (11)
Similar to A deep dive into supporting xen desktop
Similar to A deep dive into supporting xen desktop (20)
More from solarisyougood
More from solarisyougood (20)
Recently uploaded
Recently uploaded (20)
A deep dive into supporting xen desktop
- 1. A Deep Dive into Supporting XenDesktop Download this slide http://ouo.io/zTW9Km Kim Ferrie, Mick Glover
- 2. © 2014 Citrix. Confidential.2 Agenda A Deep Dive into Supporting XenDesktop Architecture FMA Service States Service SQL Scripts Site Policies
- 4. © 2014 Citrix. Confidential.4 XenDesktop 7.x Architecture Controller Citrix Studio Citrix Director WCF [80] Virtual Desktop (VDA) Citrix Desktop Service [5985/5986] WCF [80] PoSH PoSH Citrix ICA Service (PicaSvc2.exe) SQL Server SQL Server Environment Test Service Configuration Service Host Service Monitor Service Machine Creation Service AD Identity Service Configuration Logging Service Storefront Service Broker Service Delegated Admin Service SQL Server Machine Creation Services Infrastructure Services Broker Service Machine Creation Services Feature & Integration Services SQL Server
- 6. © 2014 Citrix. Confidential.6 Viewing service states through Windows only tells half the story Example: Broker Service
- 7. © 2014 Citrix. Confidential.7 Validating a Service Status Get-BrokerServiceStatus (Broker) Get-ConfigServiceStatus (Configuration) Get-HypServiceStatus (Host Service) Get-AcctServiceStatus (AD Identity) Get-ProvServiceStatus (MCS) Get-MonitorServiceStatus (Monitoring) Get-AdminServiceStatus (Delegated Admin) Get-LogServiceStatus (Configuration Logging) Get-SFServiceStatus (StoreFront) Get-EnvTestServiceStatus (Test Service)
- 8. © 2014 Citrix. Confidential.8 Get-BrokerServiceStatus - Return Values Status Meaning OK The broker is connected to a database that is valid, and the service is running. DBUnconfigured The broker does not have a database connection configured DBRejectedConnection The database rejected the logon from the Broker Service. This may be caused by bad credentials, or the database not being installed. InvalidDBConfigured The database schema is missing (possibly just the stored procedures in it). DBNotFound The specified database could not be located with the configured connection string. DBMissingOptionalFeature The broker is connected to a database that is valid, but it does not have the full functionality required for optimal performance. Upgrading the database is advisable. DBMissingMandatoryFeature The broker is connected to a database that is valid, but it does not have the full functionality required so the broker cannot function. Upgrading the database is required.
- 11. © 2014 Citrix. Confidential.11 SQL Service Scripts 4 script types for each FMA service FullDatabase Instance Evict Login
- 12. © 2014 Citrix. Confidential.12 Examples of when to use each Script A Script for every occasion… FullDatabase • Manually create or script the creation of a new Site Instance • Manually add a controller to an existing Site Evict • Manually remove an orphaned Controller from a Site Login • Create DB Security Logon
- 13. © 2014 Citrix. Confidential.13 Generating Service Scripts Use the PoSH SDK Get-<ServiceAlias>DBSchema - DatabaseName -ScriptType • Broker, Config, Hyp, Prov, Acct, SF, Monitor EnvTest, Log & Admin Examples • Get-BrokerDBSchema -DatabaseName CitrixSynergy606 -Adminaddress DC2.training.lab - ScriptType instance | out-file c:join.sql • Get-ConfigDBSchema -DatabaseName CitrixSynergy606 -Adminaddress DC2.training.lab - ScriptType instance | out-file c:join.sql -append
- 14. © 2014 Citrix. Confidential.14 Generating Service Scripts Use the PoSH SDK Get-<ServiceAlias>DBSchema - DatabaseName -ScriptType • Broker, Config, Hyp, Prov, Acct, SF, Monitor EnvTest, Log & Admin Examples • Get-BrokerDBSchema -DatabaseName CitrixSynergy606 -Adminaddress DC2.training.lab - ScriptType instance | out-file c:join.sql • Get-ConfigDBSchema -DatabaseName CitrixSynergy606 -Adminaddress DC2.training.lab - ScriptType instance | out-file c:join.sql -append
- 15. © 2014 Citrix. Confidential.15 Citrix Studio uses the same Scripts FullDatabase & Login
- 16. Demo Manually joining a Controller to an existing Site
- 17. Site Policies
- 18. © 2014 Citrix. Confidential.18 XenDesktop Site Policies Overview Entitlement Policy (Pooled/Shared Desktops) • Get-BrokerEntitlementPolicyRule • Get-BrokerAppEntitlementPolicyRule Assignment Policy (Dedicated/Private Desktops) • Get-BrokerAssignmentPolicyRule • Get-BrokerAppAssignmentPolicyRule Access Policy • Get-BrokerAccessPolicyRule
- 19. Demo Restricting access to resources through Site Policies
- 20. © 2014 Citrix. Confidential.20 Tweet Tweet... Stay Informed with the latest XenDesktop Tips @XDinformer • Kim Ferrie @XDtipster • Mick Glover
- 21. © 2014 Citrix. Confidential.22 WORK BETTER. LIVE BETTER.
Editor's Notes
- Focus Point: To be able to support XenDesktop successfully, you first must understand the architecture and it’s capabilities.
- How the various FMA services interact with each other and the Site Database How to check the true state of FMA services and validate site functionality through PowerShell How to create various types of Service and Database Schema scripts How to configure Site policies to control access to resources
- Here is an example of PoSH being used to validate the status of the Super 6. Careful, as these naming conventions are not overly institutive. Click Basically, for frontline… the value you are looking for is OK If you get anything other than OK, there is a problem.
- Ref: http://support.citrix.com/static/kc/CTX127254/help/Get-BrokerServiceStatus.html
- Get-<ServiceAlias>DBSchema: Gets SQL scripts that can be used to create a new Citrix Broker Service database schema, add a new broker service to an existing site, remove a broker service from a site, or create a database server logon for a broker service. If no Sid parameter is provided, the scripts obtained relate to the currently selected broker service instance, otherwise the scripts relate to broker service instance running on the machine identified by the Sid provided. When obtaining the Evict script, a Sid parameter must be supplied. The current service instance is that on the local machine, or that explicitly specified by the last usage of the -AdminAddress parameter to a Broker SDK cmdlet. The service instance used to obtain the scripts does not need to be a member of a site or to have had its database connection configured. The database scripts support only Microsoft SQL Server, or SQL Server Express, and require Windows integrated authentication to be used. They can be run using SQL Server's SQLCMD utility, or by copying the script into an SQL Server Management Studio (SSMS) query window and executing the query. If using SSMS, the query must be executed in 'SQLCMD mode'.
- Get-<ServiceAlias>DBSchema: Gets SQL scripts that can be used to create a new Citrix Broker Service database schema, add a new broker service to an existing site, remove a broker service from a site, or create a database server logon for a broker service. If no Sid parameter is provided, the scripts obtained relate to the currently selected broker service instance, otherwise the scripts relate to broker service instance running on the machine identified by the Sid provided. When obtaining the Evict script, a Sid parameter must be supplied. The current service instance is that on the local machine, or that explicitly specified by the last usage of the -AdminAddress parameter to a Broker SDK cmdlet. The service instance used to obtain the scripts does not need to be a member of a site or to have had its database connection configured. The database scripts support only Microsoft SQL Server, or SQL Server Express, and require Windows integrated authentication to be used. They can be run using SQL Server's SQLCMD utility, or by copying the script into an SQL Server Management Studio (SSMS) query window and executing the query. If using SSMS, the query must be executed in 'SQLCMD mode'.
- Citrix Studio offers administrators the opportunity to generate two of the 4 service scripts: 1.FullDatabase 2.Login
- The above policies (Entitlement & Assignment) control access to resources and also the conditions (Access Policy) under which resources can be accessed. Assignment policies are useful if you are assigning users on first use at the Delivery Group level. No impact if you exclude the same user that you pre-assign to a desktop as the pre-assignment will override the exclusion.