robinstolpe's Posts

Sorry for the late replay but the forum dident notice me that you hade replay.   anyway. I can from the thinclient tunnel the smart card in to my VDI. it’s on the thinclient it are flag as insert... See more...
Sorry for the late replay but the forum dident notice me that you hade replay.   anyway. I can from the thinclient tunnel the smart card in to my VDI. it’s on the thinclient it are flag as inserted but I can’t read anything from it and I’m sure that’s why I can’t login to the horizon with it. When I try to use it to login / auth to my horizon connection (to the broker / uag) it just greyed out. if I login with my password then I can see the smart card and use it inside my horizon session.   where can I find the PKCS11 module to copy it in to the correct path on the thinclient according to your suggestion above?
So I have been looking and I can’t find the install file for Cisco jabber to install inside win10 instant clone goldenimage our clients are regular windows 10 machines with horizon client installed.... See more...
So I have been looking and I can’t find the install file for Cisco jabber to install inside win10 instant clone goldenimage our clients are regular windows 10 machines with horizon client installed. I can find the agent etc but I can’t find some install file to run it directly on the VDI.. maybe a stupid question, does anyone have a link?
Yes, but you need UAG and enrollment server https://www.carlstalhood.com/vmware-horizon-true-sso-uag-saml/    
Hi, I have five Dell Wyse ThinClient OptiPlex 3000 TC with ThinOS 2208. The smart card reader is supported so that's checked. I can map the smart card in to the VDI and use it inside but the issue... See more...
Hi, I have five Dell Wyse ThinClient OptiPlex 3000 TC with ThinOS 2208. The smart card reader is supported so that's checked. I can map the smart card in to the VDI and use it inside but the issue is that inside the ThinClient I can't see any information about the smart card. I can see that it's inserted but nothing more than that. I can't change PIN, see cert or similar. And the biggest issue of all, I can't use it to login to the broker/connection servers with it as the ThinClient can't read anything from it is my guess? But still it can be tunneld/mapped without any issues from the tinnclient in to the VDI so it's kind of strange. How do I solve this? I can't figure it out and Dell's documentation is not so good to be fair I have search for a solution for this a long time now.
Did you solve this? Got the same issue here now as one of my PODS did delete the user and then also from the AD but the other POD still has it in it's database and I can't remove it as vdmadmin can't... See more...
Did you solve this? Got the same issue here now as one of my PODS did delete the user and then also from the AD but the other POD still has it in it's database and I can't remove it as vdmadmin can't find the SID as the user are deleted.
Hi, After I have activated smart card support on my connection servers it has started to tell "The website xxx requires a client certification". If I click cancel then I can write my username and p... See more...
Hi, After I have activated smart card support on my connection servers it has started to tell "The website xxx requires a client certification". If I click cancel then I can write my username and password to login on the Horizon view admin console but still I don't want this pop-up for the admin console. I was following this guide: https://docs.vmware.com/en/VMware-Horizon/2206/horizon-console-administration/GUID-965A7946-605E-40A9-8808-32D27C318F70.html In the Horizon view console I have the following settings: Horizon Authentication Smart card authentication for users: Optional Disconnect user sessions on smart card removal: Yes Current User Authentication Accept logon as current user: Yes True-SSO integration: Optional Horizon Administrator Authentication Smart card authentication for administrators: Not allowed
I have a very irritating issue. Some old nodes are stil in the global Adam database but they are removed from Horizon. If I run repadmin.exe /showrepl localhost:389 DC=vdi,DC=vmware,DC=int everythin... See more...
I have a very irritating issue. Some old nodes are stil in the global Adam database but they are removed from Horizon. If I run repadmin.exe /showrepl localhost:389 DC=vdi,DC=vmware,DC=int everything looks fine. But if I run: repadmin.exe /showrepl localhost:22389 dc=vdiglobal,dc=vmware,dc=int I do get errors.     ource: Default-First-Site-Name\xxxx$VMwareVDMDSG ******* 64 CONSECUTIVE FAILURES since 2022-07-20 23:45:41 Last error: 1772 (0x6ec): The list of RPC servers available for the binding of auto handles has been exhausted. Naming Context: CN=Schema,CN=Configuration,CN={xxx-xx-xx-xx-xxx} Source: Default-First-Site-Name\xxx$VMwareVDMDSG ******* WARNING: KCC could not add this REPLICA LINK due to error.       I know this nodes and they are removed for about a year ago or similar and they are flooding my logs with errors as all of the other CS are trying to replicate to / from them. I did remove them in the proper way. They don't show up in Horizon View and vdmadmin -S -r -s don't work either. Inside ADSIEdit for localhost:22389 under OU=Groups,OU=Properties,OU=Pod and then when I look under each pod they are not there either it's just my existing nodes there. This is starting to drive me crazy!   Edit: Also tried to run query in the ADSI Edit (&(objectClass=pae-PodEndpoint)(cn=xxxx)) can't find anything   Edit 2: Sovled it and made a blog post about it: https://stolpe.io/deleted-node-is-still-in-global-ldap-adam-db-and-how-to-delete-it/
Hi, When I run "repadmin.exe /showrepl localhost:389 DC=vdi,DC=vmware,DC=int" on my connection servers not all shows up on each connection server, every connection server shows different results. No... See more...
Hi, When I run "repadmin.exe /showrepl localhost:389 DC=vdi,DC=vmware,DC=int" on my connection servers not all shows up on each connection server, every connection server shows different results. Non replays with an error.   Example what they show that they has as INBOUND NEIGHBORS: CS1: CS2 and CS4 CS2: CS1 and CS3 CS3: CS2 and CS4 CS4: CS3 and CS1   CS3 and CS4 are 1:1 with a UAG but CS 1 and CS2 are not as they are used inside the LAN but all of them shows up under servers in Horizon View Administration GUI I have checked and all of them show the same fSMORoleOwner that's the CS4   Is that correct or should I re-install some of the connection servers? Shouldn't all of them replicate with all the servers?
@anil_agarwal  Do you have KB how I can collect them? I do have in my agreement support from VMWare as we are a government company can I email you with the logs instead due to the fact that we are ... See more...
@anil_agarwal  Do you have KB how I can collect them? I do have in my agreement support from VMWare as we are a government company can I email you with the logs instead due to the fact that we are a government company? (I was posting here as other people maybe get the same issue also That's why I did post here instead of contacting vmware support directly
@anil_agarwal  I did it like this: 1. Updated App Volume Manager servers to 2111 2. Updated App Volume agent and DEM agent to the 2111 version on the GoldenImages 3. Pushed it out to my pools DE... See more...
@anil_agarwal  I did it like this: 1. Updated App Volume Manager servers to 2111 2. Updated App Volume agent and DEM agent to the 2111 version on the GoldenImages 3. Pushed it out to my pools DEM Self-Support just says "No Applications" then I did rollback to DEM agent 2106 and then I can see the application again in Self-Support. My Horizon View are running 2106 but I did update our Test environment yesterday to 2111 and it's the same issue there also. We do have our DEM profiles etc. on DFS share but as it works with 2106 when we rollback I can exclude that from the issue as it works with 2106
  @anil_agarwal  Hi, No, it works when I rollback to 2106 but when I upgrade to 2111 it stop working. When I'm on 2111 and opening for example the Self-Support DEM applikation in the pool I don't... See more...
  @anil_agarwal  Hi, No, it works when I rollback to 2106 but when I upgrade to 2111 it stop working. When I'm on 2111 and opening for example the Self-Support DEM applikation in the pool I don't see any applications etc. When I'm rolling back to 2106 I can see all of the application in self-support DEM application in the pool again. When I did test now it do seem to work with the sync, I did try to add a new bookmark to MS Edge Chromium and logoff and on again and it was still there and the log was telling that it was working. But the issue with self support are still there and that's a good feature for my users to use. So how can I provide with more information regarding the self-support application so we can get it to work?  
Hi, I was running 2106 of DEM and everything works fine with that so I did update to 2111 and then in self support they can't see there DEM config for apps and it don't load or save configuration ei... See more...
Hi, I was running 2106 of DEM and everything works fine with that so I did update to 2111 and then in self support they can't see there DEM config for apps and it don't load or save configuration either so DEM have stopped working with 2111. I did rollback to 2106 and everything work fine now again but I want to upgrade to 2111 anyone knowing what the issue can be?   Edit I have updated the GPO's to 2111 and it works with 2106 also - it do seem that I missing some kind of new or changed setting for 2111 that was not there for 2106?
Hi, I have three displays in vSphere for the golden image and I have 256MB of memory.   The issue are when someone connect with a Windows PC and have more then one display the Horizon Client are s... See more...
Hi, I have three displays in vSphere for the golden image and I have 256MB of memory.   The issue are when someone connect with a Windows PC and have more then one display the Horizon Client are showing the VDI as one big display dragged over all of the monitors. What I want is to have it as one single monitor on all of the monitor like when you Hooke up a PC with multiple monitors.
Hi, Now when most of my users are connecting to our pool or there persistent personal VDI:s they do get one monitor dragged over two displays how can I split it so it so they have two displays? Can'... See more...
Hi, Now when most of my users are connecting to our pool or there persistent personal VDI:s they do get one monitor dragged over two displays how can I split it so it so they have two displays? Can't figure this out it started with 2106 with 2103 it was two displays as default.
Updated to a better configuration that I did post earlier.   [IncludeRegistryTrees] HKCU\SOFTWARE\Microsoft\SQL Server Management Studio   [IncludeFiles] <LocalAppData>\Microsoft\SQL Server Man... See more...
Updated to a better configuration that I did post earlier.   [IncludeRegistryTrees] HKCU\SOFTWARE\Microsoft\SQL Server Management Studio   [IncludeFiles] <LocalAppData>\Microsoft\SQL Server Management Studio\18.0_IsoShell\1033\Ssms.CTM <LocalAppData>\Microsoft\SQL Server Management Studio\18.0_IsoShell\1033\Ssms.CTM.IconMapping <LocalAppData>\microsoft\sql server management studio\18.0_isoshell\settings\sql server management studio\NewSettings.vssettings <LocalAppData>\Microsoft\SQL Server Management Studio\18.0_IsoShell\Ssms.exe.config <AppData>\Microsoft\SQL Server Management Studio\18.0\UserSettings.xml
This did work, is it any GPO for this that I can push out for my clients?
I’ll create a support case tomorrow. The issue is with our cs that has smart cards requirement. you can’t access our environment if you have updated to 2106 on the CS you get http error 500. Same wit... See more...
I’ll create a support case tomorrow. The issue is with our cs that has smart cards requirement. you can’t access our environment if you have updated to 2106 on the CS you get http error 500. Same with client 2103 and 2106 this when we had updated the cs to 2106. And only for smart cards. this is only when your outside (internet/wan) when you go trough our LAN it do work. So I’m confused. But it only work with client 2103 and not 2106 and the cs 2106 so if I’m trying to access the cs that has 2103 it works fine with the 2103 client but not with 2106. I did also find a new strange thing. If your inside our environment and want to access horizon view admin you use to go to https://server1/admin but now you can go there but when you write your Creds it just say login failed. so then you need to go to https://server1.domain.com/admin then you can login.   this is strange and it’s an issue only with 2106 with 2103 the above did work.
You can do powershell script for this. It’s easy if your at the same domain or if he has his phone/email in the AD account.   use PowerCli then when machine is back you can either send email, sms o... See more...
You can do powershell script for this. It’s easy if your at the same domain or if he has his phone/email in the AD account.   use PowerCli then when machine is back you can either send email, sms or if your on the same domain you can do a pop up on his display.
What version of VMware tools are you running?  
Hole 2106 feels like a beta. I can’t even connect to my 2103 environment that uses smart card with the 2106 client. It don’t even work when I did try to update one connection server. if im using t... See more...
Hole 2106 feels like a beta. I can’t even connect to my 2103 environment that uses smart card with the 2106 client. It don’t even work when I did try to update one connection server. if im using the 2103 client it works flawless. I need some of the new features in 2106 so I’ll update the infrastructure but not the clients as it’s an issue with GUI and function for us in 2106