Hi,
The issue was the SSL/TLS configuration of the browser.
I suspect that the newer vCD uses TLS rather than SSL and therefore the original browser configuration had to be modified to include TLS.
Thanks for all that tried to help.
Henry
Hi,
The issue was the SSL/TLS configuration of the browser.
I suspect that the newer vCD uses TLS rather than SSL and therefore the original browser configuration had to be modified to include TLS.
Thanks for all that tried to help.
Henry
Same thing happening with me (Fusion 8.5 and Sierra 10.12.1) but I'm definitely not using Unity with any of my VMs. So far this has happened with several VMs including Windows XP & 10, Ubuntu Linux 16.04 (including Linux Live / Installation .iso image files) and Mac El Capitan.
I went back to El Capitan and installed 8.5, and during 10 days use (using several times a day) 8.5 never crashed once. Back to Sierra after the 10.12.1 update and it's randomly crashing again at VM startups.
After my other post, I figured Id start a new thread since it looks like most other issues are resolved.
My installation goes to 96% and fails with the common, "Failed to execute task. INNER" message.
This time I am able to reach Horizon, perform all/most? tasks in Horizon. However the deployment page on vSphere Web client shows failed.
Looking at the deployment Ansible logs, I see that it fails at:
TASK: [post-deployment | import image into glance] ****************************
2016-10-26 17:50:30,463 p=369 u=jarvis | failed: [10.25.212.100] => {"censored" : "results hidden due to no_log parameter", "changed": true, "rc": 1}
2016-10-26 17:50:30,463 p=369 u=jarvis | FATAL: all hosts have already failed -
I then go check glance-api.log:
Failed to establish a new connection : Errno -2 Name or Service not known
Thank you for any help
I'm running 8.5 on El Capitan and works fine, even with heavy loads.
aaaaaahhhhhh... SSO... yes that might be it, i do know that in certain locations we have issues with SSO and the windows credentials button doesnt work properly when trying to log in via the client.
this office might very well be one of those effected.. i havent checked this yet but i will do that when im back at work tomorrow.
the service account is in the vcenter admins group and it does work in the first 2 locations i did this so i would say yes it is part of the default authentication source... saying that i will double check this as well.
thanks for the tip!
also thanks for the cmdlet, i will look into it if the SSO thing is not the reason for this.
i will post back tomorrow
cheers!
Are you not able to add Test 3 to vCenter?
Create a scheduled task based on the event ID 4624 of the security log that runs the vbscript as "nt authority\system".
Similar post: https://communities.vmware.com/message/2272635
Message was edited by: EricNichols
It may be related to incomplete\missing registry keys that the credential provider should be creating. See how we addressed something similar with a login task Ctrl-Alt-Del "secure attention sequence" screen requires clicking on user tile.
On our active directory domain joined golden image with default credential providers, when a user resumes from screen saver or unlocks the screen, they are immediately presented with a field to type their password.
Once that computer has been turned into a linked clone, the VMWare agent installs a new credential provider and filter that presents an additional screen during the unlock sequence that requires a user to click on their user tile/icon. This step seems unnecessary.
Why is this additional tile screen needed? Will there be a future agent release that makes it optional? We want a transition for our users to be seamless and not require unnecessary tile clicking.
VMWare provider dll:
%ProgramFiles%\VMWare\Vmware View\Agent\bin\wscredf.dll 5.2.0.17180 build 987719
Registry Key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\Credential Providers(Filters)\
Provider GUID: BEBE672F-B0E3-4354-BB86-4EF127A55B6A wscredp
Filter GUID: 39FA3429-F61A-4975-9653-327BCE27C037 wscredf
Some interesting URL's I found during my research of credential providers:
Two detailed Microsoft resources
http://technet.microsoft.com/en-us/library/ff404303(v=ws.10)
Custom Login Experiences: Credential Providers in Windows Vista
Microsoft - Disabling a provider
Testing a Credential Provider - Active Directory Blog - Site Home - TechNet Blogs
Showing different user tiles for token and fingerprint based providers:
Writing your own credential provider with samples:
Update 1/6/14:
I found that after logging in from the View Client, if you set the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\SessionData\1\LastLoggedOnProvider = {6F45DC1E-5384-457A-BC13-2CD81B0D28ED} and copy the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\SessionData\1\LoggedOnSAMUser to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\SessionData\1\LoggedOnUsername, on subsequent unlocks and reconnects, that extra tile screen can be bypassed. Now if VMware could just reproduce that with some work by the agent!
End update
Why doesnt VMware incorporate these registry keys into their credential provider?
Got the purple screen on Dell R620 and gp exception 13 in world 32942 ( Recursive panic on same CPU (CPU 2, world 32942).
Note: PFA screenshot of the error
Hi All,
Here's the situation.
Base image has Office 2013 Pro Plus. Visio 2013 was created as an AppStack afterwards from a packager VM based on the base image (with Office installed).
Office works great, and the Visio appstack seems to work fine. We had a new requirement that the Windows Search service be enabled to facilitate searches in outlook. I noticed when the Visio appstack is attached to the VM, the "Indexing Options" button in Outlook was grayed out, and an additional section was added to "Upgrade windows search" as if it was not properly detected. Obviously, outlook search is not working properly.
If I remove the Visio appstack, everything goes back to working as expected.
Any ideas?
We had a similar issue. ESXi 5.5. Our revolved around boot times ( or at least it appears )
We have a SAN that takes about 10 mins to boot. The 3 ESXi Hosts ( Dell's ) take only 3-5 mins to boot
So if the power goes out and the outage exceeds our UPS capacity and thus the systems all shut down,
when the power does come back up, all 3 Hosts are up and running prior to the SAN becoming available
Anyway to affect the boot order of things (Dell servers after EMC SAN) in hopes that the SAN boots first
so it's available when ESXi 5.5 is going through its "first scan" during its boot process?
You can give Application Profiler to anyone that manages their applications. Create a share that has Access Base Enumeration, so the users only see there application profile drop-off folder.
They request you to place the AppProfile in UEM, this way you are just managing the UEM implementation and not the application profile settings.
Hello,
Not in the user interface, but you can do this manually if you really want it, note that this requires manually editing configuration files.
This means that it is important to make copies of those files before editing them so that you can restore them.
See:
and:
http://artykul8.com/2012/06/vmware-performance-enhancing/
hope this helps,
--
Wil
Try re-provisioning the Visio AppStack during your Office search changes or confirm if they are User or machine changes be made in the registry.
I have not run into this problem before.
Thanks a lot.
They'll be running test during failover. They're a little paranoid anytime someone mentions they're Protected Site storage will be overwritten with changed data (rightfully so). In an actual event this wouldn't be a consideration, but we're just testing (although a real test involving real data). The planned migration still uses actual real vm's with data they are paranoid of possible corruption on failback. Of course we could create fake vm's, but it defeats the purpose of testing actual real workloads.
Appreciate the feedback but even running a test with the vm's connected to the production networks defeats the purpose of not performing an actual failover followed by failback. Ultimately, it's that specific workflow using real data that is desired. I've communicated back to the business exactly what a failback will do, so there is no confusion. A decision is being made on how they want to proceed. It may just be more stringent backup procedures before the failover. Thanks very much for the feedback.
I have not seen that in any Win10 deployments yet. have you made sure you have installed the correct printer drivers on windows?
Is this local or network printing?
Do you use a printing solution, like ThinPrint?
Hi Laurent,
I just tried the updated JAR file and I can confirm that everything's working under Windows 10 Pro now.
Thank you!
Luna
This should be a known issue for 6.0 which is fixed in 6.0 u2 release: https://www.vmware.com/support/developer/vc-sdk/sso-sdk/vcenter_sso_sdk_2_0_releasenotes.html
You should be able to run the sample with --basic-connection, or using java 1.7.