The View connection server(s) acts as a broker for client connections. View Connection Servers authenticate users through Windows Active Directory and then assigns a user to the appropriate desktop. The main functions of a View Connection Server are as follows
- Authenticating users
- Entitling users to specific desktops and pools
- Assigning applications packaged with VMware ThinApp to specific desktops and pools
- Managing local and remote desktop sessions
- Establishing secure connections between users and desktops
- Enabling single sign-on
- Setting and applying policies
The configuration data is stored in a LDAP directory and is replicated amongst other connection servers.
I thought I would publish a series of articles which would provide an overview of Horizon View. This will consist of an overview of the following;
- Connection Servers
- The View Connection Process
- View Security Servers
- View Composer
- View Agent
- View Client
- vCentre’s Involvement in Horizon View
Keep your eyes open for the first article in the next day or so.
Time to check out all of the #VMworld 2015 social media channels to see what they offer
“Are You Ready” for an incredible VMworld 2015? Be sure you are connected with VMworld social media and community, for on-site and online offerings. Social media can often provide that ‘virtual handshake’ to start conversations with the global VMworld community. Take advantage of the following resources to expand those discussions or enhance face-to-face networking opportunities — before, during or after the conference.
How secure is the hybrid cloud?
The term hybrid cloud is used loosely, which is probably why so many companies say they’re planning to adopt it. If you’re planning a hybrid cloud strategy, the security questions you need to think about may not be the ones you’d expect.
VMware Validated Designs
In this video we explain what a VMware Validated Design is, some common components across all VMware Validated Designs, and how the VMware Validated Design process makes deploying a Software-Defined Datacenter a streamlined experience.
Achieving High-Performance 3D Graphics with Horizon 6
By Matt Coppinger, Director, End-User-Computing Technical Marketing and Enablement, VMware and Gary Sloane, Consulting Writer and Editor, VMware Are you considering virtualizing your 3D desktop workloads? Are you wondering if your 3D applications will perform on a virtual desktop? The new VMware Horizon 6 3D Engineering Workloads Reference Architecture looks at some of the more […] The post Achieving High-Performance 3D Graphics with Horizon 6 appeared first on VMware End-User Computing Blog .
So I came across this one today the vCenter server had previously been upgraded from 5.1 to 5.5 and the Syslog Collector had also been installed on that server. We noticed that the C Drive had started to fill up over a period of time and traced that back to the following file.
C:ProgramDataVMwareVMware Syslog Collectorlogsdebug.log which was now 15GB in size!
It turns out thanks to KB 2094175 that this is a known issue with no known resolution apart from to carry out the following tasks.
- log on to the vCenter server
- Stop the VMware Syslog Collector service. For more information, see Stopping, starting, or restarting VMware vCenter Server services (1003895)
- On the server running the VMware Syslog Collector service, navigate to C:ProgramDataVMwareVMware Syslog Collector and save a copy of vmconfig-syslog.xml.
- In a text editor, open vmconfig-syslog.xml and modify from:
<debug> <level>1</level> </debug>
<debug> <level>0</level> </debug>
- Start the VMware Syslog Collector service. For more information, see Stopping, starting, or restarting VMware vCenter Server services (1003895).
Having just completed a storage/ VMware migration from 4 x Dell Equallogics to a single Nimble CS300 (48TB 2.4TB Cache 1GB iSCSI) I just wanted to share with you my experience.
The firm runs a number of highly transactional Microsoft SQL servers which accepts data from the likes of Compare the Market and GoCompare. They have approximately 75 vm’s and also a small VDI environment running on the Nimble. Unsurprisingly the Nimble handles all this without breaking in to a sweat, but that’s to be expected right ?
So why do we get so much performance from a 3U box with 12 SATA disks and 4 SSD’s; quite simply CASL
CASL is a CPU-driven storage architecture, so write performance is no longer dependent on spindle speed or spindle count. What’s more, CASL dramatically increases the usable capacity of disk and flash through compression and its unique sequential data layout.
This document provides a great overview on CASL for those that want to know more.
So after the environment had bedded in I took a look at the Nimble interface to see what the steady state IOP and latency figures were for this environment, bearing in mind we have several highly transactional SQL servers, 75 vm’s and a small virtual desktop environment all running on this box, lets take a look below.
IOP figures for an average working day
- Random Read: 881 IOPS
- Sequential Read: 1931 IOPS
- Random Write: 580 IOPS
- Sequential Write: 180 IOPS
Latency figures for an average working day ( 1GB iSCSI Network)
- Read Latency 0.42msec
- Write Latency 0.19msec
Pretty impressive figures considering the blended workload, this is about the 11th Nimble I have installed and I am always impressed with the performance of these arrays.
Take a look at the new vSphere 6 Hardening Guide
This blog contains what I learned and shared with the public. All posts are my personal opinions and does not present any products or companies.
I came across this little beauty the other day and wanted to share the resolution with you, in my case it was the web service on the vCenter server had stopped.
Provisioning of a desktop pool fails, and you see one of the following error messages in the event database.
- Cannot log in to vCenter at address VC_Address
- The status of vCenter at address VC_Address is unknown
- The View Connection Server instance cannot connect to vCenter for one of the following reasons.
- The Web service on the vCenter Server has stopped.
- There are networking problems between the View Connection Server host and the vCenter Server.
- The port numbers and login details for vCenter or View Composer have changed.
- Verify that the Web service is running on the vCenter.
- Verify that there are no network problems between the View Connection Server host and the vCenter.
- In View Administrator, verify the port numbers and login details that are configured for vCenter and View Composer.