If you need to build an EdgeSight architecture for more than 6000 agents, you need to know you will have to split your database and EdgeSight server (web server) associated with it. This next architecture doesn't include Edgesight database broker you will need for XenDesktop VDI deployment. If some of you are looking forward a VDI deployment for EdgeSight just let me know, Twitter, Facebook, email, comment or phone, I can make it simple for you, and you won't need to read the 300 documentation pages ! This is a slightly different approach with file share and database broker... A typical data upload size for an EdgeSight for Endpoints agent is 80KB. EdgeSight for XenApp agent data uploads are typically larger due to the greater amount of data collected and can reach 300KB. These data upload sizes depend on a number of factors such as the agent properties and the usage profile of the system hosting the agent. From Edgesight Admin guide page 22. Of course it depend how your worker are configured and what data you need to collect. I'm still trying to figure our how to calculate the amount of data transferred from agents to the web server, this is a complex calculation and it take a lot of time for something Citrix should provide. So architecture for large environment is the same as the one you could watch in the previous blog - Citrix Edgesight architecture scenario – part 1/2 - except you need to split database and EdgeSight server. Only one Citrix license server and you can also keep one SQL Reporting Services for both Edgesight servers. This configuration means you need to configure agents with a different http address, for example, at one customer I had 4000 XenApp servers and 5000 Endpoint agents, so I choose to split Endpoint agents on one Edgesight server and all XenApp on the other. This is not very handy when you want to check from XenApp servers to the endpoint statistics, but this is the way it is for now.  By multiplying EdgeSight environment, complexity is getting stronger and find the good information is sometimes a matter of hours instead of minutes... What Citrix should consider for the future of Edgesight : Stop to check Citrix licenses on the Edgesight Servers, only agents is enough I think, then we would be able to load balance Edgesight Servers and SQL…

During my experimental EdgeSight setup, I have to face different error, mostly because everything was not ready or not well configure on my side but it can happen. I have install two Edgesight web server (Esx nlb) and two SQL Reporting Services server (Esx nlb too) with a database store on a SQL 2005 cluster. I didn't had the hand on the setup of the two nlb so things where a bit hard to understand since there is quiet a lot of issue and things to do to enable two VMWare ESX nlb communication. (I'm still working on it, any informations are welcome :) ) I will update this post everytime I will have an error, I hope it will help some of you. Error : Setup was unable to locate the requiered SQL Server Client Tools. The SQL Server Client Tools can usually be located on the SQL Server installation disk. You just have to install client components of SQL Server 2005 (or 2008) and RTM first :) You must have database and SQL Login creation rights on the server. This message means the credentials choose to create / access database needs to have sysadmin rights on the database server, I still hevn't understand why but still.   Error -2147217900: failed to execute SQL string, error detail: MODIFY FILE encountered operating system error 112(There is not enough space on the disk.) [...]   This error message happen when you don't have enough space where you choose to record SQL data. I think that would me near the same for log space.   The report server address used to communicate with Reporting Services is invalid This message will occure when your SQL Reporting is not reachable. I had this issue until my SQL Reporting Services ESX nlb works very fine. Error publishing reports: Server was unable to process request. ---> Timeout expired. This is a typical message when a timeout occure when you're uploding templates to the SQL Reporting Services.