Announcing the Release Candidate of Citrix Melio 6! -

We are pleased to announce the Release Candidate of Citrix Melio 6, the first version of Citrix Melio since acquiring Sanbolic in January 2015

Melio 6 is the enterprise storage and data virtualization software platform for high availability and scale-out of XenDesktop and XenApp. With the introduction of Melio 6, will enhance our position as an industry leader of business mobility and the introduction of business continuity in the data and storage layer. 6 Melio allows customers to improve the efficiency and resiliency of their existing server and storage infrastructure, the perfect convergent or creating Hyper convergent IT environment.

Melio 6 is available on our Desktop and App customers looking for reduced image management, high availability of PVS / MCS, databases and user profiles. Melio 6 will also be available with more than one site for geo-distribution of data and is convergent toward Hyper infrastructure for customers.

Because our clients mobile workspaces are adopting, the demand for easy-to-implement and easy-to-use infrastructure on the rise. More data means more data management headaches and legacy storage infrastructure is no longer cut. System administrators are concerned about not being able to access information when they need it, at the speed they need it.

Melio 6 is the answer-a pure software solution, optimized for Citrix workloads, it cuts costs for IT and Business and reduced infrastructure and data management.

Melio 6 is a major upgrade. It includes a new Citrix user interface and improved performance and scalability for Hyper-converged architectures. The Enterprise Edition includes the new, patent-pending, storage protocol ISA Citrix Independent Storage Architecture.

Melio ISA identified storage resources on all Melio driven servers on the network and aggregates them into a common storage pool, which is then shared with all servers that expect high availability provide customers. This means no more dependency on external memory or expensive and proprietary connectivity. By ISA, customers receive a genuine stock control, provided equivalent to the cost savings and ease of use of cloud provider.

Citrix Melio will continue to work well for all environments SAN / DAS and hybrid storage. Customers will get a high availability for PVS / MCS, SQL and file servers and activate functions by Melio the company, they can offer the application services need their business users. It also allows customers multisite environments for geo-distributed data or disaster recovery (DR), providing availability and set up guarantees and accelerated access to applications and data.

customers interested in the purchase Melio 6 can contact for more information their CSA or salespeople. If you want to evaluate 6 Melio, you can download the software at the following address http://www.citrix.com/downloads/melio.html .

Melio 6 sold as stand-alone and is not included with other Citrix products. It is licensed per server (physical or virtual) to access all or part of the shared memory pool. with active support contracts eligible to Melio to update all existing Melio Enterprise customers 6 with ISA.

We look forward to working with you!

Eva Helén

Show me all the plans -

There is a scene in the film The Aviator where Howard Hughes, played by actor Leonardo DiCaprio, repeats the sentence ". Show me all plans" and If you are over and over again not familiar with it, you can see it here:

is exactly what I will do today to show the designs.

Ok, well not exactly shows to them, but to explain to you what is a design and what you can do with it in Citrix lifecycle management. If you really want to see the plans, you must log in / registration for Citrix Workspace cloud and check it out.

What is an action plan?

The Merriam- Webster dictionary defines a plan: " noun blue · pressure - ˌ pressure 1. a photographic print showing how something (like a building) will be 2. made a detailed plan how to do something "

Add Citrix Lifecycle management, the second definition is most applicable. Add CLM is the "something" every software infrastructure (I'll abbreviate from here). You can plan your on clouds like AWS and Azure and XenServer, vSphere or Hyper-V runs deploy in your own data center. Deployments can be run on Windows or Linux operating systems, not to mention already baked virtual appliances as NetScaler VPX.

The composition of a blueprint

A plan in CLM is to do a series of steps, the steps can be categorized in four different ways "something." -. 1) cloud-steps, 2) utility steps 3) and 4 scripts) plans

cloud steps are the games that ignite the fire. The most commonly known as the "Server" step to start a VM. Your design will probably start with this step, and can also include steps to restart, mount volumes and exit VMs. orchestrate all basics of cloud or virtual environment are here.

Utility steps you have control over the flow of the plan. You can have conditional steps, wait steps and approval steps. Your plan could have the option to install Active Directory or integration into an existing.

Scripts are the bread and butter of the Plan. This is where you keep it simple dead or completely carried away. A script is any executable code that will perform a logical action on the server. CLM is programming language agnostic, so you can write batch or PowerShell scripts for Windows or Bash, Perl or Ruby scripts on Linux. You can also upload binary executable files and run also. Scripts can take parameters from the end user, when in use. So, if you have a script that installs a database, you can ask the user for a schema name.

Now, where this gets really powerful when you add maps to your plans. Yes, you can nest a design in your design!

So what do you do when you take a domain controller design, design Delivery Controller, storefront design, VDA design, SQL Server design and NetScaler plan? That's right, you now have a blueprint XenDesktop. But it does not stop there. Next, you can use your master plan and add create your XenDesktop and XenMobile plans. As you have the full suite. Sweet! have

plan also functions that allow you to tear your deployment at the end of the day and / cope Scale-up from a plurality of load.

The crack-down steps usually consist of any cleanup or deallocation for your infrastructure through a stop Server step to do away. This is very useful if the proof of concepts provide you clean up when your review is complete. As you might guess, scale-up will allow you to start additional servers, either manually or automatically controlled according to thresholds, the CLM. You can run scripts while a scale up that adds the newly started servers to the cluster. Scale down let Reverse scale actions when the madness has subsided.

What now?

The world is your oyster. The possibilities are limitless. If you are using XenDesktop or XenApp, provides CLM large out-of-the-box plans for a PoC or production grade infrastructure. You can take these plans and change them to your hearts content and XenDesktop / XenApp deploy infrastructure that meets your business needs. Yes, the infrastructure, the weeks now took up can be used in hours!

If you're a Linux guru and how to build things from scratch, you can do that too. Create plans an Apache webserver, PHP environment, and MySQL server to create. Combine together to create it a LAMP design. Mix it up with Postgres, Tomcat, Jetty, NGINX and more. If you have set up your own virtual appliance, you can create a plan to start and configure the well. Share it with the community to get rich, retire ... you'll thank me later!

Streamlining business processes with Citrix Share File -

"Improving your company's workflow is the most beneficial lift, you can give your business and how you manage your workflow, says a lot about your with the increasing demand for companies to make Brendan Goleby

more efficient, companies prioritize workflows begin their automation - businesses "..

But to automate the process a workflow difficult and many companies may not make it past the design phase. The Citrix Share File Professional Services team develops workflow offerings to help businesses to overcome the hurdles of automation through documentation, design and implementation of automated workflows.

The first phase of the workflow automation is discovery. To start this process, a Citrix Certified Engineer reviewed the manual processes within an organization and document the current state. If the manual workflow so far has not been identified, the engineer is to discover current manual workflows in workshops with the relevant business units / departments.

After the discovery phase, a custom automated workflow designed and implemented for each customer. Below is a diagram of an automated expense management process and Share File automate custom coding with the approval workflow. The manual process took about 13 steps. After automation, the process took only 6 steps. This reduces the time to process a charge settlement by half. In addition, the automation to about $ 20 per workflow or more than $ 10,000 / year when 500 cost reports will be submitted this year to save.

As you can see, Citrix Share File is more than just sharing! Let started today! Everyone can save time and money with automated workflows.If a custom created automated workflow want or one of our representatives, email SharefileProfSvcs@citrix.com

to speak

Mobility Experts: A step-by-step instructions for setting XM 10.1 Setup the SSL offload mode with Storefront XenApp -

Description:

the purpose of this site is to provide, together with NetScaler load balancing using XenMobile 10.x virtual servers configured in SSL offload mode for registration with enumeration of applications of XA together with the applications activated in XenMobile Server WorxHome.

[1945001DieserLeitfaden] provides steps to configure Server (XMS and NS) defined on the basis of the architecture in the document. It includes the following, but client (app) configurations shortly be updated.

1. prerequisites required XenMobile
2. XenMobile to implement architectural
3. firewall ports requirement
4. XenMobile initial
5. NetScaler configurations
6. NetScaler gateway configurations on XenMobile
7. adding XenApp STA on NetScaler
8. storefront configurations
9. XenMobile integration with storefront
10. End User Experience
11. Appendix

audience:

1. Citrix XenMobile product Deployment Administrators
2. Citrix partners
3. Citrix customer
4. Citrix SE
5. who XenMobile 10.x

want to distribute download link : A step-by-step instructions for setting XM 10.1 Setup the SSL offload mode storefront XenApp

Please do not hesitate to contact me if you have any questions about each step in the document.

Thanks,

Roshan Smith,
Lead Systems Engineer MET-MPG .

Troubleshooting Linux VDA registry problems -

By far the most common Linux VDA support issue the VDA-registration is not. This is often caused by incorrectly configured Active Directory integration or Kerberos authentication issues. In this article I'll try to explain how the Linux VDA Active Directory and Kerberos used and what is commonly goes wrong.

is a nice feature of the Linux VDA that they in the same storefront slots, Delivery Controller (Broker) and Active Directory infrastructure you already have available. The familiar user SSO experience of logging on storefront and get access to applications and desktops, without the credentials again prompted applies to Linux VDA.

The challenge for Linux that do not play on Windows, and it's nice in a Windows domain environment, is inherently difficult. Whether you have chosen Winbind, Quest or Centrify as Active Directory Integration Platform or in fact on one leg away, trying SSSD or PowerBroker, the conditions for a clean Linux VDA Setup remain the same.

There are other some other great sources of information about the registry problems for the Windows VDA, including support articles CTX126992 and CTX126992.

much of this information is still relevant to the Linux VDA and worth reading. This article builds on this and adds the Linux flavor.

hostname

Bad host names that are too long or contain invalid characters can cause, either very obvious or annoying subtly problems in an Active Directory environment. Windows is strict with host names; However, many Linux distributions dangerously liberal, what they allow. Best Practice is:

• limiting hostname avoid length to 15 characters or less to NetBIOS name truncation
• az, AZ, 0-9 and the hyphen (-) characters only, especially avoid underscores, spaces and other symbols
• not start a host name with a number and not end it with a hyphen.

hostname short form of the need to be different FQDN of the DNS domain name contains dot notation. Running the command hostname should display a short name, such as myvda01 while running hostname -f should have its corresponding FQDN as myvda01.workers display. mycorp.net .

The host name and SAM account name of the computer in AD must match, if you ever change the host name, you need to unite the VDA the domain again. Of course, it is best your hostname to get sorted out before anything else to do.

DNS

Bad DNS configuration is a common problem. Before it is good practice, your VDA machine's network settings point to the correct DNS server and DNS server are again reasonable results to ensure. Check if you query the DNS domain name of the VDA. If in a multi-domain or cross-forest environment, also check the other domain names. For example:

 nslookup mycorp.net nslookup nslookup workers.mycorp.net central.mycorp.net 

Multi-homed VDAS

For Linux VDA 1.0, support for multiple network interfaces was limited and should be avoided. The selection of the network interface and the IP address with the broker the communication was not deterministic, which can lead to irregular registration failures.

This problem has been fixed in Linux VDA Version 1.1. To use the network interface, to communicate with the broker a configuration setting has been added to allow specific. For example, make eth0 your primary network interface:

 sudo ctxreg -f -k HKLM / Software / Citrix / Virtual Desktop Agent  -v Primary Ynet Work Interface  -t REG_SZ  -d eth0 sudo create service ctxvda new start 

If you use multiple network interfaces (no loopback interfaces) on your VDAS, it is strongly recommended that this set. If you leave the setting blank, gives way to the VDA to v1.0 behavior unpredictable selection.

Domain Membership

Perhaps obviously to register for Linux VDA with the broker, it must be joined to the domain. The join process varies between AD integration products, but mainly the result is the same - a computer object for the VDA has created in AD. is without the domain connected, the VDA and brokers will not be able to establish a security context and thus not be able to communicate with each other.

There's nothing special about a computer object in AD for Linux machines. It has seen a SID, a DNS name, a SAM account name, and other attributes that are set on a Windows computer object. If you are using Winbind, there are several commands that you can run to verify that the machine is connected and the computer object attributes are valid:

 sudo net ads TESTJOIN sudo net ads info sudo net ads status 

most other AD integration products provide similar instruction tools.

Cross domain and cross-forest

in complex environments with multiple trusted AD domains, with either the VDAS and Delivery Controller are in the same domain, or a 2-way trust relationship located in domains. From Linux 1.1 VDA these trust relationships can cross forest boundaries, use either forest or external trust types.

must be located for HDX session authentication as VDA or in an outbound trusted domain in the same domain user accounts. In other words, the VDA is to rely on the users' domain but do not necessarily have to trust the VDA domain the user's domain.

For more information, search the Active Directory planning manuals for the use of Linux VDA in complex AD environments.

sync

Kerberos is very time-sensitive. If clocks between servers drive more than a few minutes, breaking down the Kerberos authentication system. It is important that all servers and domain controller time are synchronized with each other.

a common architecture is all domain controllers synchronized either by a common internal time server or from the public pool time cluster, and all domain member servers synchronized with the domain controllers.

For virtual machines, it is generally best practice that the time will not be synchronized with network time servers rely solely on the hypervisor-time synchronization.

synchronize for each server with a time server, make sure that you select a cluster that is geographically close. It was observed that NTP may last synchronization time when network latency or jitter is too high.

system keytab

The VDA and brokers use Kerberos to mutually authenticate and secure communication with each other. Each side is the identity of the computer account to use, which create the need for the admin service accounts in Active Directory. Under Windows Kerberos keys are used to secure the machine and the authentication with the domain controller identify are stored and managed by the LSA service. The equivalent on Linux is the system keytab file named usually /etc/krb5.keytab .

The keytab file is typically created when the Linux machine is connected to the domain, and only with the root user. Note that if you use Winbind, the default configuration will not create the keytab file by default. Before joining a domain, make sure that in the /etc/samba/smb.conf

 kerberos method = secrets and keytab 

You can check the list of keys available, even if the keys have been created by running as root:

 klist -ket 

Note that since the VDA communication broker is bidirectional, where on both sides can initiate or accept connections, the VDA both client (UPN) and service (SPN) used keys of the computer account. UPN keys (eg MYVDA$@WORKERS.MYCORP.NET ) used to establish a security context with the broker and SPN-keys (eg host/myvda.domain.net@WORKERS.MYCORP . NET ) are used to accept a connection request from the broker.

for the VDA to decrypt incoming messages is important that the FQDN of the VDA FQDN matches exactly contained within the SPN. The FQDN in the SPN is after host / prefix and before @REALM suffix.

 hostname -f 

For example, if an SPN for the VDA is host/myvda.domain.net@WORKERS.MYCORP.NET , then the above command will need return myvda.domain.net . If they do not match, VDA will fail registration. It might be necessary to combine the machine to the domain again every name to troubleshoot problems.

Kerberos server location

It is important that Kerberos on the Linux VDA has its own domain configured properly to locate domain controllers and if the working cross-domain, the domain controller of the domain of the broker. This is achieved by domain name to KDC server assignments. These assignments are either statically configured in /etc/krb5.conf on each VDA or DNS SRV records retrieved.

For example, the following /etc/krb5.conf file shows how a VDA, residing in workers.mycorp.net domain, could communicate with brokerage services in the foreign central.mycorp.net domain are configured.

 [libdefaults] default_ccache_name = FILE: / tmp / krb5cc _% {uid} default_realm = WORKERS.MYCORP.NET dns_lookup_kdc = false [realms] = {WORKERS.MYCORP.NET KDC primarydc.workers.mycorp. net KDC backupdc.workers.mycorp.net} = {CENTRAL.MYCORP.NET KDC primarydc.central.mycorp.net KDC backupdc.central.mycorp.net} [domain_realm] = workers.mycorp.net wORKERS.MYCORP. NET. workers.mycorp.net = WORKERS.MYCORP.NET central.mycorp.net = CENTRAL.MYCORP.NET .central.mycorp.net = CENTRAL.MYCORP.NET 

The assignment of DNS domain names to KDC server is more than two hops. The DNS maps domain names to the Kerberos realm name (under the [domain_realm] section) and the Kerberos realm name maps to the KDC server (under the [realms] section) ,

This is difficult on any VDA configuration and does not scale well. The better option is to use the DNS SRV records that were created by domain controllers. These records are identified by the prefix _kerberos._tcp. to the DNS domain name. For example, to verify that the DNS SRV records for both VDA and broker-domains are available, perform the following steps:

 host -t SRV _kerberos._tcp.workers.mycorp.net -t SRV _kerberos._tcp host. central.mycorp.net 

These commands should list for the two domains Kerberos ticket distribution services capable of all domain controllers. If no SRV records are returned, this could the DNS service records show are not for the domain released, or there is some other underlying DNS problem. It might be necessary to consider /etc/krb5.conf with static configuration in instead file.

If you use the DNS SRV records, open / etc / krb5 conf and make the following change in the context of [libdefaults] section:

 dns_lookup_kdc = true 

Testing Kerberos

the easiest way to ensure that your VDA properly connected to the domain, your system KEYTAB file is valid and the Kerberos services are localized and operable manually authenticate the computer account. myvda.workers.mycorp.net For our fictitious VDA, we perform:

 sudo kinit -k MYVDA  $ @ WORKERS.MYCORP.NET 

Since WORKERS.MYCORP .NET configured as the default region, we could have something to do saved us by the suffix omission:

 sudo kinit -k MYVDA  $ 

If all goes well, the TGT ticket was fresh through the KDC marked and stored by the VDA in the cache. To view the cached ticket, run:

 sudo klist 

The start time of the ticket should be the time kinit reflect was performed

Ports

the default port for VDA-communication Broker is TCP port 80. connections are established in both directions, this incoming port on the firewall on both the broker and VDA must be open. If you use a port other than the default, you must specify this port as part of the configuration ctxsetup.sh

order by ctxreg check the configured port tool .:

 ctxreg -k HKLM / software / Citrix / Virtual desktop Agent  -v controller Registrar Port 

This is the interface in hex to display. A value of 0x00000050 80 decimal.

port 1494 on the firewall should be open to accept for HDX session traffic from the receiver.

Test Controller Endpoint

To test whether the brokerage service is available, listening and processing requests to the configured port, you can empty HTTP POST requests to the registrar service Broker grant.

 curl -i -d "X"  H: A simple way is that  curl  tool to use is "Content-Type: application / soap + xml"  -H " expect: 100-continue " http://mybroker.central.mycorp.net/Citrix/CdsController/IRegistrar

If the first line is displayed HTTP / 1.1 100 further , and the Broker service responds. This will be followed by a HTTP / 1.1 400 Bad Request response that can be ignored.

Another way to get the broker is to explore using the new Linux XDPing tool that will I describe later.

reintegration into the domain and stale service tickets

Under certain circumstances, if a VDA offset the domain and a fresh set of Kerberos keys are generated, suggests the broker to create a security context with the VDA. This is often caused by the broker a cached out-of-date VDA service ticket based on the previous series of Kerberos keys. This is not the VDA stop to the broker by the compound, but the broker is not be able to establish a secure connection back in the opposite direction to the VDA. The usual symptom VDA fails registry.

This problem is finally resolved if the VDA service ticket finally expires and is renewed, but service tickets are durable as a rule. This could potentially hours.

If you experience registrations problem after VDA on the domain re-entry, the solution of the broker ticket cache must be deleted. You could simply start the broker new, but a less drastic measure is the following run on the broker at a command prompt as an administrator:

 klist -li 0x3e4 Purge 

This will clean up all service tickets in the LSA cache by the rather major network service, under the Citrix Broker service is running. This is service tickets for other VDAs and possibly remove other services. This is harmless - this service tickets will be from the KDC reacquired if needed again

LDAP configuration

The Linux VDA query its domain controller to obtain information about the computer's it. runs. This was indirectly carried out by specially crafted Winbind Quest or Centrify call shell scripts Before Linux Virtual Desktop 1.1. As of version 1.1, which was rationalized into a single direct LDAP query, eliminating the need for special AD integration product scripts can be dispensed with.

For both methods, this will usually only work without administrator intervention. However, if you use Linux Virtual Desktop 1.1 or later, there are a few LDAP service needs to be aware of:

• The LDAP service must be running on the domain controller
• The LDAP service must be hosted on standard port 389
• LDAP tunneled over SSL / TLS (ie LDAPS) is not supported
• The LDAP service endpoints using DNS SRV records be discoverable must

the last element test described earlier similar Kerberos service endpoint for the location. For example:.

 host -t SRV _ldap._tcp.workers.mycorp.net 

If you experience problems registering, look out for any LDAP errors in the VDA logfiles

known bug

if you are using the older Linux VDA 1.0 release, note there is a known issue when the OpenJDK using 1.7.0.85 or later that the registry cause failures. The resolution is either to update the VDA to the v1.1 version or the OpenJDK back to 1.7.0.79 or degrade earlier.

Soft-registration

If the VDA logs show that only "soft-registration" has been achieved, it probably means the Linux VDA has been added to a machine or catalog delivery group. Soft-registration means that the VDA and brokers are to communicate securely with each other, but not to provide setup meetings.

If your VDA experienced Soft registration under the domain reentry while before your VDA registered hard, either a controller configuration change was made to a new AD identity or the VDA has taken after. At the reentry domain You can use the new VDA computer object to the machines catalog and delivery groups.

Linux XDPing

Based must add to the success of Windows XDPing tool, developed by Citrix Support again, we have developed our own validation tool for Linux environments. Under some artistic license by our colleagues in support, we called it the Linux XDPing tool. This is carried out extensive tests on the system and is invaluable to capture at frequently asked questions, including also described many of the items in this article.

Summary

that the most frequently asked questions Registration covers we know. Anything we missed?

to read more of the Linux Virtual Desktop Team, please see here the rest of our posts.

New! Citrix XenApp / XenDesktop on FlexPod Express with Cisco UCS Mini -

For companies geographically dispersed offices, such as remote offices / branch offices (Robos) or other satellite positions, a turnkey solution have for desktop virtualization can accelerate the deployment of enterprise-class.

a new Cisco Validated Design (CVD) for Citrix XenApp and XenDesktop uses a predefined, self-contained platform the FlexPod Data Center with Cisco UCS Mini -This makes it easy for the provision of reliable and Desktops applications from 350 to 700 users.

The FlexPod Data Center, co-designed by Cisco and NetApp, calculate integrated server, network fabric and hybrid storage components, an independent Creating drop-in VDI / SBC solution that can be installed in remote locations yet centrally managed.

A flexible solution

FlexPod Data Center with Cisco UCS Mini is the building block underlying the provision of simplified while density growth to support and proven mixtures of XenApp and XenDesktop workloads. While FlexPod provides a cookie-cutter solution this CVD shows how the solution is also very versatile.

Deployments can share a common architecture, component design, configuration procedures and management. At the same time user capacity can scale and expand the number of hosted shared desktops (RDS) or hosted pooled virtual desktops to increase (VDI). This scalability also benefit small and medium enterprises-they start small and grow as many as 700 users from 350 to.

The CVD describes a basic 4-leaf FlexPod with Cisco UCS Mini configuration, the 350 users supported (150 RDS and VDI 0 users). Cisco UCS B0 M4 Blade servers have been added to this basic configuration workload expansion and scale density support. All configurations followed by a fault-tolerant N + 1 design for infrastructure and RDS / VDI VMs. The size and density Validate combinations we performed single and multiple blade server scalability tests with Login VSI software. The complete CVD documenting the step-by-step process, we used the test environment to create the test configurations and contains all the test results

Fig. 1: Reference architecture components in the FlexPod with Cisco UCS Mini

solution Overview

Figure 1 shows the major components in the CVD reference architecture, including:

• Citrix XenApp and XenDesktop 7.6 software . Since Citrix XenDesktop 7.6 combines the functionality of previous XenApp and XenDesktop frees determination, the same software and the same PVS-Setup Wizard can both RDS sessions (Windows Server 2012 R2) and pooled hosted VDI desktops (with Microsoft Windows 7 or Windows 8). In the CVD entire infrastructure and RDS / VDI workload Server 100% were virtualized on VMware vSphere ESXi 5.5 Update 2
• Cisco UCS Mini . The Cisco UCS Mini combines servers, storage and a 10-Gigabit Ethernet network fabric in one easy-to-deploy, compact form factor. The chassis can support up to eight half-width Cisco UCS B0 M4 blade servers, each with two 10-Core 2.6 GHz Intel Xeon (E5-2660v3) processors and 256 GB. In this CVD, between four and seven blade servers 6324 fabric interconnects rack were for different testing cases.Two Cisco UCS provide redundant high bandwidth LAN and storage connectivity for the blade servers and the chassis configured and can connect optional servers, as also . Cisco UCS Manager manages all Cisco UCS Mini software and hardware components and Cisco UCS Central multiple UCS Manager domains for a comprehensive policy control and centralized management.
• Cisco Nexus 9372 Switches aggregate. support order 10 GbE connectivity for FlexPod solution, this Layer 2 / Layer 3 access switches come with 48 10:01-Gbps Small Form Pluggable Plus (SFP +) ports and 6 Quad SFP + (QSFP +) uplink ports. In addition, 9373, the Nexus is Cisco ACI capable.
• NetApp FAS2552 storage hybrid . The NetApp FAS2552 is a dual-controller storage system that combines low-latency SSDs for caching and cost-effective SAS drives for capacity. The array configuration in the tests used included four 0GB SSDs and twenty 00GB SAS drives. The array controllers have support for file system access via 10 GbE ports blade server boot over iSCSI and NFS / CIFS connectivity.

Key advantages of the solutions

The CVD architecture offers significant advantages in enterprise edge or small business implementations:

• Self-sufficient and compact solution . The FlexPod with UCS Mini architecture defines a completely self-contained "all-in-one" solution with the infrastructure needed to support a mix of up to 700 Citrix XenApp and XenDesktop users. The solution consumes only 10 rack units and fits in less than a single data center rack, preserving valuable rack space.
• Cost and scalable desktop virtualization for the enterprise edge . Powerful Cisco UCS blade servers enable high user density at low cost per seat. By adding additional blade server to the chassis, a basic 4-server configuration 350 user support easily scalable 350 more additional XenApp and XenDesktop user support. The NetApp storage array has a combination of low-latency flash devices and a tray with less expensive SAS drives, for economical I / O over an end-to-end Ethernet fabric.
• fault tolerant design . The architecture defines redundant infrastructure and workload VMs on multiple physical Cisco UCS blade servers to keep users productive availability to optimize.
• to implement and manage Simple . UCS Manager can monitor in the management domain and manage Cisco UCS servers in the FlexPod solution along with other Cisco UCS blade and rack servers. Cisco UCS Central Management via Cisco UCS Manager domains extend management across multiple remote sites to centralize.
• Fully validated and proven solution . The CVD defines a reference architecture that tested under harsh usage scenarios, including boot and login storms. mandatory testing that each configuration Boot tested within 15 minutes and complete applications in 48 minutes at the peak user density.

test cases and main results

Test engineers conducted five different test cases (Figure 2). The first two single server scalability for RDS and VDI tested or recommended maximum density for each workload type on a single Cisco UCS B0 Blade M4 to determine with Dual Intel® E5-2660 v3 processors and 256GB of RAM. The other three tests the performance of mixed workloads on multiple blade servers analyzed

. Figure 2: Five test cases single server and multiple server scalability

[zuuntersuchenwurdendurchgeführt

Several blade tests showed that the configurations for mixed workloads densities under simulated stress conditions (cold start -Boot and simulated login storms) could support. In this test case, the FlexPod led configured with UCS Mini solution under the RDS / VDI user mix, provides reasonable response times with the Login VSI clerk workload. treated NetApp hybrid storage easily IOPS with an average read and write latencies less than 5 ms. For all tests, extensive performance metrics were collected and are in full CVD published.

The test results show how easily enhance FlexPod with UCS Mini configurations and flex, so that installations to grow larger at the enterprise edge and supporting RDS and VDI capacity. To learn more about the solution and our test, you can download the complete CVD here

-. Rob Briggs, principal solutions architect, Citrix Systems, Inc. Follow @Briggs_Rob

- Frank Anderson, Senior Solutions Architect, Cisco Systems, Inc. Follow @FrankCAnderson

Cloud Bridge 8.1 WAN 仮 想 化 エ デ ィ シ ョ ン リ リ ー ス 開始 -

Cloudbridge 8.1 WAN 仮 想 化 エ デ ィ シ ョ ン が リ リ ー ス 開始 さ れま し た.
8.1 の 主 な 変 更 点 は 下 記 に な り ま す.

① 対 応 プ ラ ッ ト フ ォ ー ム の 拡 充
仮 想 ア プ ラ イ ア ン ス VPX の サ ポ ー ト
· VPX10, VPX20, VPX50, VPX100
· 対 応 ハ イ パ ー バ イ ザ ー: XenServer, ESXi
· AWS BYOL (Bring your own license) 対 応

対 応 HW ア プ ライ ア ン ス の 追加
· Cloudbridge 4000 プ ラ ッ ト フ ォ ー ム へ 2Gbps の 追加
· Cloudbridge 400 シ リ ー ズ の 追加 (CloudBridge8.0.1 よ り サ ポ ー ト)

② マ ネ ー ジ メ ン ト と セ キ ュ リ テ ィ の 強化
Cloudbridge WAN 仮 想 化 ア プ ラ イ ア ン ス は, Master Control node (以下 MCN) と client node に 分類 さ れ ま す .MCN か ら 全 て の ア プ ラ イ ア ン ス (client Node)のコンフィグレーションを行うことができます。そうすることで、物理的に距離の離れたWANサービスにおいても、現地で作業することなくリモートから全て設定を行うことができます。また、MCNから全ての設定を行うことにより、対向での設定の整合性もチェックすることができ、オペレーションミスも軽減することができます。このようなSD-WANアーキテクチャに加えて、CloudBridge8.1でリリースしたVirtuelle WAN-Centerでは、設定だけでなくモニタリングも含め一元管理できるようになりました。設定に関しては、従来通り、MCNからも行うことができますし、Virtual WAN Center 経 由 で MCN の 設定 を す る こ と が で き ま す.

また、セキュリティ機能の強化については、複数のWAN回線を束ねるWAN仮想化(SD-WAN)ソリューションでは、閉域網とインターネット網を組み合わせることが一般的です。その際、インターフェースはFirewallと同様にTrusted、Untrustedの属性を付与します。Trustedのインターフェースでは、暗号化するか非暗号化のまま通信するかの選択が可能ですが、Untrustedでは、必ず暗号化するようになります。従来は、AESで暗号化していましたが、標準のIPSecをサ ポ ー ト し セ キ ュ リ テ ィ の 機能 も 強化 し ま し た.

関 連 情報

Citrix Cloud Bridge 製品 ペ ー ジ

Citrix Cloud Bridge デ ー タ シ ー ト

WAN 仮 想 化 ホ ワ イ ト ペ ー パ ー

SD WAN の 導入 で 最大 80% ネ ッ トワ ー ク コ ス ト を 削減

無料ハンズオンセミナー開催中！：SD-WANを試してみませんか？

Windows 10 Application Compatibility Deep Dive -

Windows 10 is very well tolerated.

In my previous post, I discussed an overview of the Windows 10 application compatibility and a single application found that worked on Windows 8.1 64-bit, which is not more than 10 64-bit Windows does not work.

which is a really high degree of compatibility, no matter how you look at it, but that's enough ... well not necessarily there are many problems that can cause applications to not work on a new platform and obviously the greater the variation the greater the risk.

What factors affect application compatibility?

There are various factors that can affect application compatibility, generally speaking:

• The age of the application; The older he gets, the less likely it is with a modern operating system and the restrictions in place as UAC, Session 0 Isolation, OS Versioning controls and the more likely will depend on outdated or removed technologies
• work the transition from 32 bits to 64 bits is application compatibility to decrease, there are still many 16-bit applications and components even in applications in circulation
• the platform was developed on Microsoft .Net application-tends to work well because of the platform they are developed on (this is not to say developers can not do bad things, it's just less likely). You would expect that Java would be in the category, but not the sheer number of changes between JRE versions, it is a nightmare breaks in the most complex environments to manage
• The knowledge and skills of software engineer who wrote it

AppDNA can all the problems mentioned above in the detection (ok, except for the skill level software engineer), regardless of whether the application is in the house or not ,

But Windows 10 64-bit and Windows 8 64 bit are highly compatible, so why should I AppDNA?

It is highly unlikely that you have a homogeneous environment where all users are using an operating system image and all its applications in Windows 8.1 64-bit. If they are, then perhaps you are in this great location where you can move only at low risk, or can you?

Perhaps not, if we consider the results further confirmed by a search a little deeper into the AppDNA database, we can see that directly between Windows 7 64-bit and Windows 10 64-bit, there are 3321 PE files missing (or moved), this means there are potentially 3321 files that are to import your applications, and the API calls are obviously not present when these files are missing, or have a non-library loading point.

missing files between Windows 7 moves 64-bit and Windows 10 64-bit: 3321

And when we start a little deeper digging for more subtle changes, where the files are present, but they have special API calls had to be removed, we find that 4052 API calls are missing! Many of them are certainly benign and probably does not support your applications or published not use API calls or do they !?

Missing API calls between Windows 7 64-bit and Windows 10 64-bit: 4052

As usual, there are no guarantees but fortunately Citrix AppDNA a category of algorithms in the OBSOLETE group that applications can recognize that. to depend these files or API calls

it when you import your own customized operating systems AppDNA a delta comparison between them do it automatically would be even better to identify any missing PE file or API calls between the builds, especially important if you high customized builds.

If you are a XenDesktop or XenApp Platinum customers or partners Download AppDNA today you are on Windows 10 to help the migration

How resilient is your cloud? Part 1 -

Some of the questions are asked most often by cloud administrators:

• How many resources you can create in a cloud managed by Citrix Cloud Platform?
• How far can I stretch my cloud and yet provide quality of service for my clients available?
• How many virtual machines can I use a set of hosts or edit?
• How many accounts can be managed?
• How many areas can I have?
• can handle How many VPCs Cloud Platform?
• What is the reaction time to list say 10,000 Virtual Machines over 500 hosts distributed?

And so on. You get the idea.

This blog series will address some of these issues in the course of several installments. The idea is to set up advice and information for cloud administrators the cloud so that Cloud Platform can orchestrate resources efficiently and at the same time address incoming API requests with an acceptable response time.

The first part focuses on the performance of the most common and basic use cases in a scaled environment. Some examples are implementing virtual machine and response time for important and frequently ListAPI queries in a scaled environment up to 00 hosts.

configuration

For a high scaled setup with about 00 hosts used, it is obviously impractical to organize such an infrastructure. Therefore, the most sensitive way to test a cloud of this magnitude for performance is the built Cloud Platform simulator to be used. The simulator can be used to mock resources, including hosts, storage pools, virtual machines, etc., and behaves the same as the actual resources in most cases.

Insofar as concerns the Cloud Platform management server, so there is no major difference between an actual resource and a simulated resource. For most tests, which are independent hypervisor, this is our goal.

The configuration here is considered to be a scaled environment with approximately 00 Simulator hosts and more than 4,000 accounts. Let us consider the redundant virtual router deal, so we. Two routers per network

Use Case 1

, the above configuration, which will be given the time to implement a virtual machine?

I had a total of 100 Simulator virtual machines in use and monitors the time taken to use for the first VM to the last VM to the VMs. This test is conducted on 4.3.0 version of Cloud Platform and uses the following configurations for the management server:

Metric: Time to implement Virtual Machine

This is the taken time to finish the job deploy VM Async the virtual machine to run state and to bring.

Here is a chart showing the trend of the times is taken 100 for provisioning of virtual machines. It shows the Time in seconds Taken to deploy virtual machines - from the first start up 100th

As can be seen above from the diagram, the management Server. takes about 5-10 seconds to select a deployment target and implement the VM. The peaks in the early part of the graph is (elected two routers per network since RVR deal) for the virtual router made in any network to implement time to see a share.

The other observation is evident that over 10K VMs that time is higher as compared to the first few VMs. This is to be expected, since most of the hosts are already running full of virtual machines and the management server spends some time looking for available hosts. And the result is established earlier in all the baselines

Metric :. Time for deployVirtualMachine API response

I also have the response time of deploy VM API measured. This is different from the job Async reaction time in the sense that the API reaction time is made substantially the time for the management server to do the initial processing of the API and react with a job ID.

Here is a diagram showing that to see response time in seconds for deployVirtualMachine API from the first 12,000 to VM

As evident from the results is, the majority of the APIs take between 0 and 1 tick to process the request and take a few of them for about 5 seconds.

Use Case 2

Another important application in a scaled environment is the time for the various ListAPIs taken to give a response. This is also the UI performance directly affects as this is the most common API that is triggered obtained if the user can see the user interface.

A number of important list APIs were considered for this test and here is the result.

The graph below shows response time in seconds for visits to various list API.

The above mentioned data for different values ​​of page size is according to the listAPI query.
, for example, there were 12K VMs, 4K accounts, 8K router, 20K events, 2K hosts, 4K user and 12K volumes in the test setup. The list visits were made without limit for the page size, so that it fetches all the objects.

In order to achieve a cloud of this magnitude with Cloud Platform setup, it is important to note that there are only a few configurations that must be coordinated so that Cloud Platform can orchestrate the cloud effectively.

Few of the tuning parameters are mentioned below.

• had, for example, the test setup 3 management server, any management server is a 16G RAM server with dual-core 4-processors and a total of 3 of these management servers. It is recommended to add a management server for each 6-7k VMs, we also take into account load balancing at every turn overs take should
• The cloud database on a remote server with 32G of RAM is hosted and 8 processor server
• the database buffer pool size (innodb_buffer_pool_size) was set at 80% of the RAM
• also note that as many hosts and VMs and the management server to implement these many resources orchestrate, we need the Java heap size is set to at least 8 GB.
• cloud.maxActive compounds was placed in db.properties 1000

This brings us to the end of the first part of this blog series. Look out on the next parts that have more metrics on the latest Cloud Platform Performance, Tuning and Notes Your Cloud to make a better performance!

Red Hat OpenStack & Citrix NetScaler simplify implementation of L4-L7 services -

to the possibility of application delivery network services of OpenStack automate the customer has Citrix with Red Hat worked integrate NetScaler with its OpenStack distribution.

Many organizations build private cloud platforms as a way to increase the agility of the IT infrastructure and to increase the efficiency of processes to support their mission-critical applications. In recent years, we have an increasing shift to the provision of OpenStack seen that an open source cloud management platform in production environments.

with Red Hat OpenStack By integrating Citrix NetScaler makes available to the many organizations that use them this popular OpenStack distribution

When organizations use OpenStack providing servers to automate storage and to link you are looking also to automate the deployment of L4 -. L7 services. To do this they need to create the integration of their devices with OpenStack in a manner that provides in infrastructure-as-a-service their network equipment vendors.

These challenges include scalability, flexibility, performance involved use challenges involved and flexibility / control over resource allocation. Citrix NetScaler built Control Center to facilitate as a way to integrate NetScaler with LBaaS Service in OpenStack. The Citrix LBaaS solution enables IT organizations the performance and availability service level guarantees (SLA), and redundancy and seamless elasticity whilst providing running quickly line of business applications in open bag.

[1945001[ key features within NetScaler Control Center

Capacity pooling in all infrastructure NetScaler - Pooling of infrastructure is the first offer step infrastructure as a service and forms the underpinning of the economic benefits of the cloud model. NCC is designed capacity for all NetScaler appliances including physical (MPX), virtual (VPX) and multi-tenant (SDX) to bundle form factors efficiently and manage. Without platform limitations and compatibility with multiple NetScaler firmware versions, NCC based orchestration offers full investment protection for customers with existing NetScaler installed base

End-to-end automation of all NetScaler appliances -. NCC is designed to enable a true "as-a-Service" model, in which the complexity of the deployment and the use of ADC functions on a large pool of NetScaler appliances completely hidden in both the cloud provider as well the cloud tenant. NCC automation features include:

• Car instantiating new VPX appliances as Nova instances and SDX instances on demand, without manual intervention
• . automation of licensing started on new VPX instances.
• policy-based resource allocation to "right size" the car installed instances (both VPX and SDX instances.)
• Auto-provision of Admin partitions on MPX, SDX and VPX appliances
• data plane service insertion -. innate intelligence of the neutron and the ability to dynamically attach both VPX and SDX instances Neutron networks
• Service Level Assurance -. Cloud providers need the performance and availability SLAs to different cloud tenants, to ensure. NCC provides granular control over resource allocation policies ADC, the provider flexibility in creating differentiated SLAs for cloud tenant needs based on their application.

A simple and intuitive Workflow "service packages" to construct for different tenants levels simplifies the creation process SLA. Service packages can be defined using the following parameters and can be individually customized per tenant .:

• Device Type - The target device on which a logical NetScaler instance for the tenant is created
• insulation type -. Option between fully dedicated instances, common instances or individual Admin partition for each tenant
• to select resources hard walling - The amount of CPU, memory and SSL capacity for each tenant dedicated instance assign
• software version -. The specific version of NetScaler firmware for each dedicated instance of the tenant - enables version and upgrade independence between tenants [
• HA pair vs. single instance - (. Guarantees availability SLAs for tenants) choosing a single NetScaler instance or an HA pair for each tenant specified

integration with OpenStack KeyStone for a single sign-on authentication - NCC integrates natively with Keystone, OpenStack the authentication service and can retrieve related information directly from KeyStone tenants. This simplifies the tenant-specific policy management and avoids the expense and potential security problems relate explicitly OpenStack tenants credentials with NCC registration

Flexible placement algorithms -. Cloud providers need to have a control over the placement of new ADC policy fully automated environment a potentially large fleet of NetScalers from. NCC offers a wide range of options for placement algorithms, including the following:

• Simple round robin
• usage metrics (VIP number, average CPU, SSL, storage, throughput capacity) [1945011[
• Affinity -. Option separate device groups to create physical affinity to an availability zone, pod, data center or region to indicate
• External input - are plug-in mechanism for the placement algorithm provider placement rated algorithm and fed into NCC as input

Central visibility and reporting -. NCC a single pane of glass provides deep insights into the operations of the ADC services NetScaler is running in the OpenStack environment. Information about the status, statistics and health through a comprehensive set of metrics helps central visibility and monitoring, and basic troubleshooting. Granular be made pro-tenant usage data available for reporting and charge back

High Availability -. The NetScaler OpenStack LBaaS solution guarantees redundancy through automated delivery of NetScaler HA pairs on both virtual and physical devices. In addition, NCC itself is available as a fully redundant active standby HA pair with full state synchronization and fault tolerance

VPX on Nova -. The NetScaler virtual appliance is optimized for operation as Nova Example and new VPX instances can by simply calling Nova APIs heat started templates on-demand are automation suites such as OpenStack. The virtual appliance provides options for automatic bootstrapping the instance, including support for the OpenStack Config drive bootstrap information to obtain.

For more information on NetScaler Control Center please see more information visit , http://www.citrix.com/netscaler
cooperates for the announcement, Citrix with Red Has on new product integrations for building OpenStack Clouds

Nuage Networks and Citrix Collaborate to Application Delivery with SDN and OpenStack -

The application landscape is changing. Enterprise companies use complex scale-out applications.

These applications, many components that must work together. An application architecture can include a legacy component that resides on a mainframe, it can service-oriented architecture, components, and there may be services new micro to fulfill specific tasks.

The network infrastructure will be changed in response.

Most applications are running on a virtual server infrastructure. Network services are migrated to virtualized network infrastructure. Network services now exist as virtual appliances. Everything has to interact by the application components to virtual network services.

to the components, virtual networks such as the Nuage Networks Virtualized Services Platform (VSP) have been developed to use a connection and organizations such the pieces to connect the virtualized applications and virtualized network components together.

SDN virtual network solutions such as Nuage Networks VSP automate IT across an entire data center infrastructure cloud while maintaining control, visibility and freedom choice. Interoperability in an SDN landscape has now technologies such services include chaining automatically integrate security and application delivery services in the virtual networks. Integration with these devices also means take advantage of the value-added features in each party solution and work well with open source cloud management systems such as OpenStack automation to provide end-to-end and centralized management.

With experience of installations at leading companies and cloud service provider customers, Nuage Networks reference architectures built on OpenStack and Nuage Networks Virtualized Services Platform (VSP) is based. The Nuage Networks Partner Ecosystem makes this architecture as a pre-designed and publicly accessible environment that allows in as little as two weeks self-certification of the elements of the architecture.

Nuage Networks expanded its Nuage Networks Partner Program with the introduction of self-service certification initiative. With a focus on Layer 4-7 application delivery and security, the initiative provides an easy, quick way to enterprise customers, to ensure that micro-segmentation security policies, components and services that they choose will provide and operate automatically in an environment Nuage networks SDN.

one of the most important network services, the application delivery controller that provides for applications, performance, availability and security. Citrix NetScaler is a leader ADC and we want to ensure that it can be automatically inserted into networks that are built on SDN and cloud infrastructure. Citrix NetScaler is the first application delivery controller (ADC) partner solutions from Nuage Networks are certified.

When organizations implement this new application and network architectures companies need to know that different components work together and they also need the best way to know that their network design. By validating that their solutions work alongside those of partners, Nuage Networks provides peace organizations like moving their business applications to the cloud.

By pre-qualify our solution with the Nuage Networks Virtualized Services Platform, we accelerate speed for enterprises and cloud service providers to the market and the risk, cost and complexity of implementation, integration and maintenance of advanced network functions to support applications to reduce.

Nuage Networks is a member of the Red Hat certifies Connect for Technology Partner Program and its products with the Red Hat Enterprise Linux OpenStack platform. Citrix has the same for NetScaler done that allows both Nuage VSP and NetScaler VPX running on RedHat OpenStack.

The Citrix NetScaler Application Delivery Controller platform powers the world some of the largest enterprises and cloud infrastructure systems available with the best components today. The certification with Nuage Networks Virtualized Services Platform in conjunction with OpenStack, will allow customers to quickly build their own cloud infrastructure, and they are operated on a large scale.

For more information
to demonstrate our cooperation on November 6, 2015 Citrix Systems and Nuage has a demo on Friday SDxCentral. See this link for the recording, painless Layer 4-7 network services Insert & Achieve Automation with Citrix & Nuage Demo Friday.

See this page for information on the Nuage Partner Program for Application Delivery.

this link for the Citrix and Red Hat Announcement See working with Citrix, Red Hat on New Product Integrations for building OpenStack Clouds.

Virtualized Services Platform (VSP) "Nuage Networks received Citrix Ready® certified.

Press Release, Nuage Networks Expands Partner Program with certification initiative launch.

Introducing Storefront 3.1 Tech Preview -

I am thrilled to introduce you to the storefront 3.1 Tech Preview, , the here available for download (Citrix Login required) .

The main features of this Tech Preview included a new administrative console and a new management PowerShell SDK. These are storefront management much easier.

In the past, we would get a lot of feedback that the existing Storefront management console is not sufficient for many scenarios, so it is essential for administrators must resolve to run PowerShell commands or edit web.config. Also, it might not be configured with different authentication settings for various businesses such is a major obstacle for many organizations.

We have in the last year working hard all address these concerns. The new administration console and manage PowerShell SDK are the result of the hard work of the team. We believe that with the new administration console, most administrators do not PowerShell commands or editing configuration files must be run.

Please raise any questions and / or provide us with your feedback by using our discussion forum.

Store Centric Conceptual Model

When you open the new administration console, you will find that all configuration settings now organized around businesses. found

settings in the Authentication node and Receiver for Web node in earlier versions of Storefront are even available now as manage authentication methods action and manage receiver for Web sites action within the memory node in the lower right pane. These tasks are now save specific. That is, configured in this task settings are related to the selected memory.

is the settings in NetScaler gateways node and in Beacons node in earlier versions of storefront you manage now are configurable via the NetScaler gateways action and beacons manage action in the upper right pane that are against valid cross shops.

Why do we have these changes?

First Storefront 3.1 different authentication settings for various businesses supported that performs multiple authentication services to a storefront deployment. There is a 1-to-many mapping between the authentication service and stores. There is also a 1-to-many mapping between the memory and Receiver for Web sites.

Without the UI architecture change, several authentication services in the UI implementation would make it more difficult to understand the associations between different services. In addition, our usability studies have suggested that the organization of the user interface to business fit better with the administrator conceptual model as administrators often think about different stores for different purposes or for different organizations and treat up authentication, Web access as properties of a memory.

memory Dedicated authentication settings

As mentioned above, the Administration Console before this release only supports a single authentication service for a Storefront deployment. This means that all the shops in the provision have to share the same authentication settings.

In the new administration console you are given a choice to use a shared or dedicated authentication service when you create a business. By default, a new authentication service for a new cache is created. If you will be the memory you want to create authentication settings to share with another business, you can check the box Use a Shared Authentication Service , and then select the disk (s) you want to configure authentication with from the drop-sharing menu , This setting is not available when you create the first shop.

is created after a storage, you can specify whether the authentication settings to share with other stores or not. Select the memory you want to change, and select the Managing Authentication Methods action. Then select the Extended menu in the pop-up dialog, followed by the selection of Common Authentication Service Settings from the drop-down menu. Another dialog popped for you to make the change.

delegating authentication to XenApp / XenDesktop Farms / sites

delegating authentication XenApp / XenDesktop farms / sites was in storefront 3.0 introduced. However, it was only configurable via Power. Now you can configure this feature using the administrative console. To do this, select the store you want to change, and select the Managing Authentication Methods action. In the pop-up dialog box, select the is associated with a user name and password settings drop-down menu, and then select password verification configure .

are

Select Delivery Controller drop-down menu and a dialog will indicate for you pop up on XenApp / XenDesktop broker used, to authenticate users.

policy for password expiration warning

You can now configure policies for password expiration warning that the administration console. Select the memory you want to change, and select the Managing Authentication Methods action. In the pop-up dialog box, select the Settings drop-down menu associated with username and password and then select manage password options .

A dialog is popped for whether to configure to allow users to change their password. If you allow users to change their password at any time, you can also configure the policy for password expiration warning.

highly available multi-site Configuration Store

[1945001mehrereXenApp/XenDesktopzuaggregierenFarmen/StellenfürLoad-BalancingFailoverundDisaster-Recovery-Benutzerzuordnung] highly available multi-site storage configuration is set up a very powerful feature storefront. This used to be about editing the web.config only configurable. We have now introduced UI support to configure most of the common applications. Users farm mapping and single aggregation group

To multi-site aggregation in the administration console, select the store you want to configure, and select the device Delivery Management Controller action. If you configure more than one farms / sites, the button in the user mapping and multi-site aggregation configuration section is enabled Configure, as shown below.

select Configure button, a new dialog popped for you to choose if you want to set the user mapping or resource aggregations.

If you select card users controller They are provided with dialogues available to specify user groups and Delivery Controller. When the user from the same domain hosting server the storefront, you can select user groups from the Active Directory. Otherwise, you must specify SIDs manually.

If you Aggregate Resources , you will be provided with a dialog available to decide, so what / sites holdings you want to aggregate group resource with the same name and path a symbol of the user.

Optimal Gateway Routing

Optimal Gateway Routing allows you to route HDX connections to different XenApp / XenDesktop farms / sites on different NetScaler gateway. UI support this feature for the configuration is added to the new Administration Console. To configure an optimal routing gateway, select the store you want to configure, and then select the Configure Store Settings Action in the right pane. In the pop-up dialog, select Optimal Routing HDX as shown below.

to the Gateway Select want to use and click Delivery Controller manage . Another dialog is for you Pop-up to select the farms / sites you would like traffic on the selected gateway to route HDX.

Store Advanced Settings

Advanced settings related to a business together and available grouped in the Advanced Settings of Configure Store Settings screen.

You can configure have found that there is a Advanced Settings shown section on the Edit Delivery Controller dialog below.

The Settings button a new dialogue brings for you Farm / configure site-specific advanced settings.

for Web Site Standard Receiver

Storefront 3.1 supports a receiver for setting website as Default Web Site for Your Storefront deployment, so users must enter only the base URL, eg https://sf.acme.com to the browser to access the specified recipient for website. This can be done in the store creation time on the following screen.

You can also set or save the default Web site to change creation. Simply select the Default site set IIS Action in the upper right pane. They will be displayed with a dialog to configure this feature.

Additional Receiver for Web configuration

Many additional settings related to web receiver now configurable to the administration console. Select the memory you want to configure, and then select the manage Receiver for Web Sites action. Select the website that you want to change, and click the Configure key. A pop-up dialog box is presented for you to change configuration for the site, as shown below.

Select Session Settings to configure different timeout values.

Select to change Workspace control session reconnection, separation and shutdown behavior.

Other settings are available from Advanced Settings section.

In addition expands the Deploy Citrix Receiver section, so upload Receiver installation packages to Storefront server, if you want your user receivers from the Receiver for Web Site to download.

Administration PowerShell SDK

Storefront 3.1, a new management PowerShell SDK provides. The documentation for this SDK can be found here for download. You can together with objects, you not only do the same tasks as the administrative console with the console. Cmdlets concentrated in the new SDK on administrative tasks and to storefront providing wide configration, Stores, authentication and Receiver for Web.

grouped New cmdlets with STF ahead. Example:


# Install the required components Storefront
Add-STFDeployment https://storefront.mycompany.com -Confirm: $ false


# an authentication service with a store Add IIS virtual path in the context of
$ authentication = Add-STFAuthenticationService "/ Citrix / AuthenticationStore"


# Add a business that uses the new authentication service configured the supplied XenDesktop server
$ store = Add-STFStoreService -VirtualPath "/ Citrix / Store" -AuthenticationService $ authentication -FarmName "XenDesktopFarm ''
-FarmType XenDesktop - server publishing "XDEUA", "XDEUB"


# Add a receiver for Web site so that users can access published in the store, the applications and desktops
$ recipient = Add -STFWebReceiverService -VirtualPath "/ Citrix / StoreWeb" -StoreService $ store

The SDK also high-level scripts that enable to script and automate storefront installations. You can adjust the high-level examples to your specific requirements.

Existing PowerShell cmdlets, supported with the prefix DS even for business continuity. However, they are outdated and will eventually be removed in the future.