cbaptiste's Posts

I would suggest you do a parallel upgrade. Meaning deploy a completely new environment. I would suggest using a newer version oh Horizon View rather than 7.8. Maybe 7.10? Why would I suggest that... See more...
I would suggest you do a parallel upgrade. Meaning deploy a completely new environment. I would suggest using a newer version oh Horizon View rather than 7.8. Maybe 7.10? Why would I suggest that? Well, if you are going to put the effort to deploy this environment you might as well do some research on big and fixes, new features, as well as linked clones/instant clones feature parity. Instead of deploying Horizon View brokers using Win 2016, I would usuggest 2019. Why? End of life support. Why use older version of OS unless license is an issue. Newer version with an extended end of life support equal less worry about upgrading the OS any time soon. I would ditch linked clones and go with instant clones unless there is a feature in linked clones that is not available in instant clones. Once you ditch linked clones you no longer have to deal with composer servers. Now you have 2 less servers to manage. By doing a parallel deployment you can do your testing without impacting production. It would be clean. You will not be bringing any ADAM database issues along with the install. You can create your desktops, entitled the users to it and when you are ready to migrate them from the previous environment you simply change the F5 LB to point the VIP to the new member servers. With this plan, your scheduled downtime is only a few minutes. :smileyplain:
I deploy the script through GPO and moved forward with my deployment. Here's the latest reply from VMware on this topic. :smileylaugh::smileylaugh::smileylaugh: I wanted to follow up regard... See more...
I deploy the script through GPO and moved forward with my deployment. Here's the latest reply from VMware on this topic. :smileylaugh::smileylaugh::smileylaugh: I wanted to follow up regarding the Support Request we have open for High Color Accuracy settings not taking place when set via Group Policy / Registry. After looking this over with our development team the behavior you are seeing is by design. The agent by default is set to support 444 if the client requests it, while the client by default will not request 444 due to the expensive nature of using 444 over 420. Setting the GPO to true on the agent results in no change in default agent behavior. There is currently no client side GPO to force 444.         As next steps I would recommend opening a feature request with your TAM/SAM to get this on the road map so this setting can be applied as a Client GPO to all users if necessary.     In theory, they have a policy that does absolutely nothing. :smileyconfused:
Reach out to your DB guy and ask him to run the query for you straight from the DB or leverage LogInsight.
I agree 100% with that statement. I created a mandatory profile with Windows 7 about 3 years ago and never once needed to touch it again. I created many mandatory profiles with Windows 10 and eac... See more...
I agree 100% with that statement. I created a mandatory profile with Windows 7 about 3 years ago and never once needed to touch it again. I created many mandatory profiles with Windows 10 and each time something(s) did not work. Mostly start menu and appx applications issues. Truth of the matter is, I did not see the gain so I ditched it and went back to local profile. My login time which was the main concern is between 11 - 30 seconds with local profile. I am not really missing out on anything.
I can send you the steps I took next week when I get back. I am currently out of town.
Thanks you. I eventually figured it out last night. When I read your comment I was looking for "Color-Settings" in the prefs file as you suggested which does not exist. I ended up writing a lo... See more...
Thanks you. I eventually figured it out last night. When I read your comment I was looking for "Color-Settings" in the prefs file as you suggested which does not exist. I ended up writing a logon script to solve the problem until VMware fixes it. The script will override the blast settings for users with an existing prefs.txt file without overriding the remaining settings. If the file does not exist, it will create it with the blast settings already enabled. matthiasFF​ I hope that helps you proceed with your deployment --------------------------------------------------------------------------------------------------------- Was it helpful? Let us know by completing this short survey here.
I would so what bjartest​ suggested to add the printer drivers. Also I would use universal drivers to minimize the amount of drivers to upload on the golden image.
You are not required to use UEM with mandatory profile. Considering all the issues surround mandatory profile, I would always advise against it in windows 10. You can obtain great login time, if ... See more...
You are not required to use UEM with mandatory profile. Considering all the issues surround mandatory profile, I would always advise against it in windows 10. You can obtain great login time, if that is what you seek, without mandatory profile. I get 11s login time with local profile.
Do you mind sharing a sample of that prefs.txt file? We are currently in the same boat. But I do not see the color section in my configuration even when I check the box.
Upgrading what in the parent image exactly? if you are referring to DEM, then the answer is no.
A case was opened from our end about 2 - 3 years ago about this and still no movement. I believe as far as I understand it, the wording are hard coded. They will have to find a way to make it dyn... See more...
A case was opened from our end about 2 - 3 years ago about this and still no movement. I believe as far as I understand it, the wording are hard coded. They will have to find a way to make it dynamic so the administrators can type in it. I guess you may see that finally in version 8.0 when they begin to redesign from scratch and clean up all codes. Again there is no way for me to know for sure but talking to them enough I know it wasn't fix in neither in 6.x, and 7.x. 7.10 is already released. So may be in 8.0. Hopefully :smileylaugh:
Let me see if i can explain this and try to simplify it. I see where you are getting confused. You have 1 pool where users need access both internally and externally You want your LAN users ... See more...
Let me see if i can explain this and try to simplify it. I see where you are getting confused. You have 1 pool where users need access both internally and externally You want your LAN users to authenticate using password You want your remote users to use passcode To accomplish this you will need about 2 brokers, 2 security servers/UAGs and 2 load balancers with 2 VIPs 1 internal load balancer to route LAN users to your connection brokers 1 external load balancer in your DMZ to route your remote users to your security servers or preferably your access points (UAG which is an abbreviation for Unified Access Gateway) where you will configure 2FA If you use unified access gateways,  you will put your brokers VIP FQDN as the server to connect to as part of the configure and then you will configure the authentication method you wish to use. If you use security servers (I would advise against it but feel free to do as you please obviously), they will be install and configure along with your connection servers using the same database, same everything as one POD. You will then go to only your security servers and configure them for 2FA but not your brokers. So in the end, your brokers will prompt users for password but your security servers or your UAGs will requires dual factor authentication. You will need a load balancer to direct users from either the brokers or the security servers/UAGs. No matter which route the a user take they will land on the same pool as long as they are entitled to it.
Which OS are you deploying. This sounds like exactly like this old VMXnet 3 NIC issue with Windows 7
Great. Glad you got it working.
Can you validate in the UEM log that the background was imported but not skipped? Also try using it without any conditions and see if it works. Could be something with the condition.
What does the log says? Enable debugging and see why it is not successful.
Try \\server\share\%username% instead \\server\share\%Logonuser% and let me know the result.
LB can not tell if your broker is in disable state. It does health check monitoring. Up and down base on if the "GET /broker /xml is reachable. That remains true even when the broker is not activ... See more...
LB can not tell if your broker is in disable state. It does health check monitoring. Up and down base on if the "GET /broker /xml is reachable. That remains true even when the broker is not active but online.
You may want to look into your permissions with either the service account you are using to provisioned these computer objects or the OU in AD. Clearly something is not working on that end causin... See more...
You may want to look into your permissions with either the service account you are using to provisioned these computer objects or the OU in AD. Clearly something is not working on that end causing things not to work properly. I have never had a case where the computer failed to either be created or joined to active directory properly. Last time I had an issues with provisioning it was because the ctkEnabled parameter was not set.
I most certainly hope so. Great tool with great potentials but so many limitations