The tool is a fling, it's not an officially supported app by VMware. It's only supported by the team that built it. When downloading the app you accept the tech preview license and acknowledge that these are experimental apps and should not be expected to have successful results all the time.
Re: VMware OS Optimization Tool Updates
Re: VMware OS Optimization Tool Updates
Hello,
On this site where there are many VDI related interesting resources there is an article about VMware OS Optimizer Tool.
https://www.go-euc.com/the-true-power-of-vmware-osot-in-vdi/
the following is a comment from Hilko Lantinga that is a contributor to the project of VMware OS Optimizer Tool
"While the statement about support is correct I would like to clarify why the statement is there. It's not that we think the tool is incapable of running on production systems, as it is and multiple customers are using it as such, but as it's a free tool and developers are assigned when time allows it, the support isn't the same as on an official product nor do we accept any liability. This might change in the future as we are exploring ways of either integrating the technology or productizing the OS Optimizer Tool."
mchadwick19 probably third-party tools are also fine as written by you, but it would be more elegant if the VMware tools that are recommended in the documentation go hand in hand with the development of the Horizon. The hope is that as announced several times the tool will be put into production and official support.
Re: VMware OS Optimization Tool Updates
VMware Horizon View is a supported product by VMware and is used around the world. VDI has lots of great use cases and when VMWare promotes their product they mention these use cases and the advantages they bring. Much of the economic advantage is gained only if the VDI master image is optimized otherwise costs to run VDI are significantly higher. The article I linked to in my previous post is one put out by VMware showing this 30% improvement using OSOT. You would think that VMware would fully support an optimization product since it is in their best interest. The Citrix optimization product is regularly updated and fully supported.
In essence, VMware by not updating OSOT is telling customers with the newest version of Windows we do not have an optimization product, so either
- Look elsewhere for an optimization product
- Run without optimization and incur greater cost
At the moment I am between a rock and a hard place. We are running Win10 v1709 and OSOT works great for this version. v1709 is going end of life in January so we have to jump to a newer version. The logical jump is to v1903 but OSOT does not work.
Re: VMware OS Optimization Tool Updates
Hello,
I opened the ticket SR19023959808 asking for support for optimizing Windows Server 2019 in the Horizon environment this is the answer:
" The, VMware OS Optimization Tool is just a fling tool. It is a free to go tool which can be used for building base images. The operating systems supported by Horizon are not yet supported meaning there need not be a supporting document to that and we do not have one since it is not under the responsibility of the developers but in the interest of people."
"We do not have any document supporting the optimization of server 2019"
Do you know if is there any information about future tool updates? "Not as yet"
... what do you think?
Re: VMware Horizon Client Giving Black display after the upgrade on Ubuntu 18.04
Dear All,
Can someone provide solution or ask for additional logs. i am happy to provide. I am unable to use the ubuntu systems now.
I am swtiching to windows 10 to connect to my client VDI.
Re: connection server 7.7 session timed out so quick?
mchadwick19 thanks for answering.
however, i just solved it. it was due to time sync problem between servers, not the load-balance.
After Software Updates Via SCCM Some Persistent Desktops Go Agent Unreachable
We have a few hundred persistent full VMs in our Horizon View environment. These are updated via SCCM as they are full persistent VMs. Occasionally a few of them will get their updates, restart and then go agent unreachable. The only way to get them back is to remove them from the desktop pool and re-add them to the pool then shut them down and let Horizon View configure them and then start them up. Does anyone have any idea why this would happen? Horizon View 7.8
Re: After Software Updates Via SCCM Some Persistent Desktops Go Agent Unreachable
Hi,
Try to check which updates have been applied on the computers you lose reachability. It happens that some security updates make computers unreachable.
Alessandro Romeo
Re: After Software Updates Via SCCM Some Persistent Desktops Go Agent Unreachable
It's happened to a small number of random computers a few months in a row now. It isn't a particular update that is causing the issue.
Re: After Software Updates Via SCCM Some Persistent Desktops Go Agent Unreachable
So it looks like the Horizon View Agent is trying to request a Changekey with the server. Logs on the server show:
[DesktopTracker] CHANGEKEY message from agent/{some long guid} is discarded as it cannot be validated
[JMSMessageSecurity] Message could not be validated: Signature invalid for identity agent/{long guid}
[JMSMessageSecurity] Identity validation failed: UNKNOWN
This seems to be the same issue as is described in this article:
Presumably we could run a key reset to get the machine working again as well.
The question is why does running software updates on the machine and rebooting it cause this to happen occasionally.
WSDL link for Horizon View API
Does anybody know if such a thing exists and if so what it is please as I am needing to write PowerShell code to use its SOAP interface as I can't guarantee that PowerCLI (or the HV.Helper module) will be available for the code I'm writing.
I've tried various like https://viewserverFQDN/view-vlsi/sdk?wsdl but with zero success.
Thanks,
Guy
@guyrleech
Re: VMware OS Optimization Tool Updates
@HendersonD Not sure I agree with your statement... OSOT is just running scripts in the background to disable services, OS features & set registry values... All of which can be done with group policy too, either directly via a group policy template, via group policy preference items, or via computer startup/user login script.
Regarding it being a fling with no support... We get that, but if you supported application documentation says 'use the OSOT'... It really should be supported & updated accordingly... Otherwise just don't mention it at all in the documentation ♂️
Re: Horizon Help Desk Plugin for Horizon Agent
I'm also looking for the new command, can't find it.
Re: Horizon Help Desk Plugin for Horizon Agent
I probably should have updated this when I found out. The command is just
ADDLOCAL=All your other stuff you want installed, HelpDesk
Re: VMware OS Optimization Tool Updates
NoDowt,
You might be correct that Group Policy can do everything that OSOT can do but I would venture it would takes days worth of work to fashion group policies/scripts to reproduce what OSOT does. This would make my Group Policies a lot more complicated. A solid version of OSOT updated by VMware is certainly a better route to go.
Re: VMware OS Optimization Tool Updates
That is such bs for vmware to recommend to use vmware OS Optimization tool but with the caveat it's not supported.
Vmware sells Horizon View with the enterprise COST for the product and enterprise COST for upgrades AND support. In part the windows operating system is bloated and has many services, subsystems and user settings that can be turned off for "better performance for the user experience". But as part of the enterprise product you would think that optimization is fundamental part for the overall deployment BUT IT IS NOT included, but "hey, there's a fling that's slapped together by our engineeers on their spare time that you should use."
I mean seriously, how can a company get away with a product feature like that?
Well, with it being over a year that the fling hasn't been updated nor has it been "productized", it doesn't seem like vmware has no incentive to do either. We are all still using it right? And paying what we pay year in and year out.
Re: VMware Horizon Client Giving Black display after the upgrade on Ubuntu 18.04
No clue if this will help you, but I've been having similar issues all week with the Horizon Client on Debian 10. What finally seemed to do the trick for me was going into the settings and changing from PCoIP to VMware Blast.
VMWare TrueSSO unable to connect to certifcate server
Hi Al
I have a very strange issue in that the VMware Truesso enrolment service is unable to connect to the issuing CA service even though they are on the same server instance. I am trying to setup the enrolment service to talk to a Horizon cloud platform; however the enrolment service isn't able to talk to the certificate service even though it has specific permissions to do so in the CA server configuration. From digging through all the logs the only thing of any relevance that appears within: "C:\ProgramData\VMware\VDM\logs"
2019-08-18T02:38:47.859-07:00 TRACE (0A58-1AEC) <MessageFrameWorkDispatch> [wsnm_certenroll] EnrollmentServices::GenerateAndSignPKCS10CMC(): Enter - Generate And Sign PKCS10CMC
2019-08-18T02:38:47.875-07:00 TRACE (0A58-1AEC) <MessageFrameWorkDispatch> [wsnm_certenroll] EnrollmentServices::GenerateAndSignPKCS10CMC(): Exit
2019-08-18T02:38:47.875-07:00 TRACE (0A58-1AEC) <MessageFrameWorkDispatch> [wsnm_certenroll] CertSrvPool::SubmitToCaQueue(): Enter - Submit Queue
2019-08-18T02:38:47.875-07:00 DEBUG (0A58-1AEC) <MessageFrameWorkDispatch> [wsnm_certenroll] CertSrvPool::SubmitToCaQueue(): No Connected CA - wait for one to connect Id=1
2019-08-18T02:38:48.890-07:00 DEBUG (0A58-1AEC) <MessageFrameWorkDispatch> [wsnm_certenroll] CertSrvPool::SubmitToCaQueue(): No Connected CA - wait for one to connect Id=1
2019-08-18T02:38:49.906-07:00 DEBUG (0A58-1AEC) <MessageFrameWorkDispatch> [wsnm_certenroll] CertSrvPool::SubmitToCaQueue(): No Connected CA - wait for one to connect Id=1
2019-08-18T02:38:50.922-07:00 TRACE (0A58-1AEC) <MessageFrameWorkDispatch> [wsnm_certenroll] CertSrvPool::SubmitToCaQueue(): Completed request id=1 - FAILED - elapsed=3047ms
2019-08-18T02:38:50.922-07:00 TRACE (0A58-1AEC) <MessageFrameWorkDispatch> [wsnm_certenroll] CertSrvPool::SubmitToCaQueue(): Exit
2019-08-18T02:38:50.922-07:00 ERROR (0A58-1AEC) <MessageFrameWorkDispatch> [wsnm_certenroll] EnrollmentServices::SubmitRequest(): Failed to locate a connected CA - ErrorCode = 2147944650 (0x00000000800708CA)
2019-08-18T02:38:50.922-07:00 TRACE (0A58-1AEC) <MessageFrameWorkDispatch> [wsnm_certenroll] EnrollmentServices::SubmitRequest(): Exit
2019-08-18T02:38:50.922-07:00 TRACE (0A58-1AEC) <MessageFrameWorkDispatch> [wsnm_certenroll] EnrollmentConnection::SubmitRequest(): Exit
2019-08-18T02:38:50.922-07:00 ERROR (0A58-1AEC) <MessageFrameWorkDispatch> [wsnm_certenroll] CertEnrollService::CertEnrollOperation::SubmitRequestHandler(): Failed to locate a connected CA - ErrorCode = 2147944650 (0x00000000800708CA)
2019-08-18T02:38:50.922-07:00 TRACE (0A58-1AEC) <MessageFrameWorkDispatch> [wsnm_certenroll] CertEnrollService::CertEnrollOperation::SubmitRequestHandler(): Exit
Any ideas would be greatly appreciated as I need to stand this service up urgently; I have also been in contact with VMware support however they don't seem to understand why this isn't working either?
Re: VMware OS Optimization Tool Updates
Hi,
Just adding to the thread...
I attended a VDI event a couple months ago where Hilko was explaining the functionality of OSOT and what we can expected for the future of it.
He said that still this year a new version will be released, the idea is to integrate OSOT with UEM, and a new approach in how you can optimize a VM, you'll have the option to receive the best optimization settings based in few questions that the tool will ask for you.... maybe based on use cases, Worker, Developer... I don't know, he didn't mention.
I'm using it for 1803 and works pretty well, I didn't test it with 1903, because of the problems with snapshots + VMFS6 + 6.7u2.
Oh, and the OSOT itself doesn't do all the job, I've been using the VDILIKEAPRO template with some changes and different settings, and other manual tasks during the audit mode, sysprep, and customization.
Let's see, I agree with you guys, they should have a better support for it. I hope they'll do something about it.
Horizon Client Kiosk
I am attempting to deploy a group of Chromebooks that will automatically launch a Horizon desktop without needing the user to authenticate for a classroom scenario. I am managing the Chromebooks centrally via Google admin and I have successfully configured the Horizon Client to launch from Kiosk mode with a JSON file that provides connection server settings. My connection server has been configured to authenticate on MAC addresses and the automatic login functionality was successfully tested with a WYSE thin client.
I cannot replicate this with automatic connection with the Chromebook. The client will launch, and select the default connection server, but the client will not authenticate without entering a credential. I suspect that am missing a configuration setting in the JSON file that will trigger the client to authenticate via the machine's MAC. I've attempted several variations of the JSON file similar to the one below (sourced from https://chrome-experts.neverware.com/s/article/Deploying-Configuring-VMware-Horizon-View-in-Kiosk-mode-using-Google-Admi… ) with no success. Can anyone provide any insight?
{
"broker_list": {
"Value": {
"settings": {
"server-list": [{
"server": "172.16.12.76",
"default": true,
"description": "CloudReady Lab",
"domain": "Cloudsteady.lab"
}]
}
}
}
}