I have a desire this morning to be objective in what I say to you, and I think, in my desire to be objective, I also have a concern that I might not be invited back again to speak to you. I have not been privileged to attend this great institution, which memorializes the name of Brigham Young, but my interest in and concern for this university and its students are very great; and if BYU is going to be worthy of its name, it has the responsibility to expand the horizons of all who attend this institution, for Brigham Young himself was a man of endless vision. There is currently a rerun of the movie called Lost Horizon. If I can, I should like to challenge those who attend this institution to broaden their vision, rather than to limit it, so that there might be no lost horizons for any of the graduates of this great university.
Having recently come into the body of your leaders, I have a persuasion that the Brethren have been called, not because of their great intellects, although many have such, or their vast experience, although most have such, or their great learning, and all are learned according to the standards of the world. Based on their treatment of me, I am persuaded that in a large measure they have been called because of the understanding of their hearts. In this area they are not wanting. The Lord has made it clear that he requires an understanding heart and a willing mind. It is to be hoped that at this great University, while cultural and intellectual pursuits take their proper place, the feelings of the heart will be included in the curriculum and therefore not become one of the lost horizons.
There is in the Church today a truly remarkable family. They are the children of Patriarch and Sister Alexander R. Curtis, who used to run a coal yard in Sugarhouse. To my knowledge, no family in the Church has produced so many bishops, stake presidents, mission presidents, and regional representatives of the Twelve. There are presently three sons serving as regional representatives of the Twelve. One of them, President A. Ray Curtis, when asked to what he attributed his success, answered that it was the coal shovel his father put in his hands when he was a boy.
Another lost horizon may be in physical soundness. More than a strengthening of muscles, there comes a strengthening of resolve, self-discipline, and carriage in participating in athletic endeavors. My brother Gus and I occasionally had to walk five miles from Granite High School to Cottonwood where we lived, after having participated in a scrimmage or training for a track meet. To many, including my own children, this seems not only foolish but downright stupid, and as I look back on it I have some misgivings myself. But there was a certain satisfaction in having persevered in an overwhelming physical challenge.
The last horizon, which hopefully is never lost in our lives, is that of service. I speak of service to your family and to others, service to your calling, service to your profession, service to your community and your country. Most of the expanding horizons of all of us involve service and dedication. I humbly challenge all to remember that mere attendance at Brigham Young University, or for that matter Harvard University or the University of Utah, is not a substitute for excellence or endeavor. There is an unquestioned mark of distinction in being part of the student body of this great institution, but equating mere admission at Brigham Young University with achievement is an improper equation.
I bear my testimony to the divinity of the work which caused this great institution to be founded and to flourish, and to the reality of Jesus of Nazareth, our divine Redeemer, who should be our constant companion in the classrooms and assemblies, and even when we walk on the paths of Brigham Young University. And because of his influence on this campus, I pray that all who pause at this great oasis may have truly expanded horizons in their lives, and that he whose life we seek to emulate will be our continuing model. I humbly pray in the name of the Lord Jesus Christ. Amen.
Cancellation of Campsites 7 days or more prior to the arrival date, will be refunded minus a $10 cancellation fee. Sites cancelled within 7 days of arrival will NOT receive any refund. Changing the date within 7 days of your arrival is not permitted. Cancellations due to weather, medical, early departures, etc. are not exempt from this policy.
Cancellation of Cabins 30 days or more prior to the arrival date, will be refunded minus a $25 cancellation fee. Cabins cancelled within 30 days of arrival will NOT receive any refund. Changing dates within 30 days of arrival is not permitted. Cancellations due to weather, medical, early departures, etc. are not exempt from this policy.
**You may use the self-service portal through Campspot to cancel reservations yourself at any time via your account/reservation link OR email a typed request to in...@thelosthorizons.com. Cancellations will NOT be accepted over the phone.**
The first Horizon Connection Server must be a Standard Server. Subsequent Horizon Connection Servers are Replicas. Once Horizon Connection Server is installed, there is no difference between Standard and Replica.
If you point your browser to the Horizon Connection Server (without /admin in the path), the Install VMware Horizon Client link redirects to the VMware.com site for downloading of Horizon Clients. You can change it so that the Horizon Clients can be downloaded directly from the Horizon Connection Server.
If you plan to build RDS Hosts, then install Remote Desktop Licensing somewhere. You can install it on your Horizon Connection Servers by following the procedure at -controller-2203-ltsr-and-licensing/#rdlicensing.
I am still getting a 404 error. This had been running fine for a very long time, and stopped suddenly. I have edited the portal-links-html-access.properties on both connection servers, and restarted the VMware Horizon View Web Component on both connection server.
Hi Carl,
i am looking for a solution so that the horizon client connection to our Vmware horizon environment can only be accessed from company owned laptops.
Do you have any advise how to achieve this?
Many thanks in advance.
Kind Regards
Gerard
We used to see that VDPCONNECT_GATEWAY_ERROR error. We theorized that our load balanced UAGs or more so the F5 front ending the UAGs may have inadvertently caused this. The idea was that the users initial connection was via UAG1. A subsequent connection the F5 may send this user to UAG2. The Session or secured tunnel would tear down since the route for the reconnect wanted to go through UAG1.
Also, if I connect to a virtual machine on sites with version 2303, I do not shut down and connect from a third site with version 2303, I am given this virtual machine. What could be the problem? Can you tell me where to look?
thank you for your response. just a follow up question. Did Vmware end up recommending to match all sites to same version ? In our case, we have currently have 2209 and when upgraded one of the POD to 2309, the above issue occurred. we are waiting to hear from VMware.
In our case, we quickly raised the minimum test infrastructure and provided test updates from 2303 to 2306 and from 2303 to 2309. The problem arose in both cases, until we updated the second POD and the connection appeared, then the third POD. When upgrading from 2306 to 2309 there was no problem.
Hi, we are running Horizon 7.13 (linked-clone) on Windows 2012 R2
There is a need to replace the OS to 2019 or 2022. Instead upgrading the existing (in-place upgrade) Windows and Horizon on the existing machine, we are planning to deploy a new one instead, then perform configuration and testing first (Instant Clone) then perform a cutover once test is done. Do you think this this is practical and doable?
Basicaly you need to change the AD user Horizon uses to join VD to the domain (as Vmware says here: ).
In order to do so, you need to manualy change the CN=xxxx parameter of the pool through ADSIedit.
But to know which CN=xxxx correspond of the new user, you must add a test pool with the new account to see it in ASDI edit.
I am planning to upgrade OS on my Connection servers (running version 2211) from Windows 2016 to 2019. What would be the correct procedure? Can I just do the in-place upgrade? I would appreciate your suggestions.
BTW, I have always followed your BLOG to implement my Connection servers to the environment and they are running solid from the day one. Thank you in advance.
I would add a Replica server, reconfigure the load balancer to send traffic to the new server instead of the old server, and then remove the old server. If any UAGs connect directly to the old server, then reconfigure the UAGs too.
Another option is for each UAG to send Blast traffic to itself, but this would require three public IPs for the load balancer plus each UAG appliance instead of just one public IP for the load balancer.
Need to migrate the standard connection server from a 2012 server MS OS to 2019 MS OS. Can I create a replica of the 2012 connection server or does the new 2019 need to be a standard deployment? We have another connection server that used the 2012 standard to replicate from as well. If I have to use standard for the 2019 OS buildout does that also mean i need to replicate the other connection server off the new 2019 standard?
We are currently using the built-in HA features for UAGS and a primary connection server and a replica connection server. No load balancer. Had the primary connection server go down and connections failed to the replica. Started digging into DNS and found we never add an entry for examplevdi.domain.com for the replica server.
So if a primary connection server goes down and there is no load balancer then manual intervention should happen by changing the DNS record to point to the replica? Or is there a better way to go about it?
b37509886e