Jump to content

Hans Straat

Members
  • Posts

    43
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Hans Straat's Achievements

  1. Hey GoShen, That is behavior as is. When we push a new image it always is secondary until all vm's are rebooted and get the updated image. Then it's the primary image. We push mostly secondary images and then on release evening we save time caus images can pushed during the day and reboot in the maintanance window.
  2. @virtualblog we run 2312 admx templates. Whe we upgraded from 2212 to 2312 we also refreshed all admx templates.
  3. At our environment npo start works just fine. we use horizon 2312.X (privat fix for connection server and appvolume managers) and client is 2406. can't figure out fast what profile we use not so much into the hardware more packaging etc clients use blast protocol we have this gpo enabled> VMware View Agent Configuration/VMware HTML5 Features/VMware WebRTC Redirection Features force client side WebRTC optimization.
  4. Did you confirm that FSLogix is not backing up the shortcuts. Also i would exclude them from onedrive and FSLogix cause you want to manage them purely from dem. Curious what the outcome is cause we are looking at onedrive and FSLogix.
  5. It was just a thought like the -what if 😉 parameter. We tested it in our acceptance environment and it works excellent. Next is deleting the greyed out production appstacks.
  6. @Robin Harmsen RadboutMC had a call with Microsoft about the 404 issue but support is urhmmm to cry for so to say (om te janken). Even with a severity 1 they didn't come with a solution. The 404 is not caused by Omnissa but a update from Microsoft. I don't get it why Microsoft isn't solving the issue. We delete the lflso key in the golden image and will remain doing so.
  7. We where thinking what happens if we reset all attachement_count to 0 ? we think attached appstacks will remain attached or will it create mahem? Anyone tested this? Just out of curiossity 🙂
  8. Update: After receiving the changed directory.rp file appstacks load again on group assignment for the affected users. Thanks Cliff and team for the hard work!
  9. The patch from Omnissa didn't work in our environment. We disabled the scheduled task Microsoft\windows\AppxDeploymendclient > UCPD velocity And as many answers we also implemented the registrytweak > HKLM:\SYSTEM\CurrentControlSet\Services\UCPD" -Name "Start" -Value 4 -Type DWord After implementing the above the adobe acrobatreader became main choise again. Also you can use the SetFTA.exe again to set other .xxx to programs. Why Microsoft thought it was wise to implement it don't know but it's a pain..
  10. Well your in the same business as I am in Leiden 🙂 lumc , thanks for confirming we can do it without stopping the managers Robin!
  11. We once had VMware engineers messing around in our database but that only deleted it in the GUI. Does this also delete the affected vmdk's etc? Also stopping all appvolume manager services in a 24/7 health environment isn't a workable solution 😞
  12. Does the app work from the sequencer you are building the appstack on? Sometimes you have to install some extra's on your seqencer to get it working we found out on our jobsite.
  13. Also mind that you remove the Scheduled Task for adobe update task 🙂 before sealing package or image.
  14. We already have a support ticket with Omnissa about this strange problem , this is a cry in the wild so to say. Situation ESB 2312. AD users around 150 Around 13 get the error message that appvolumes management server(s) cannot be contacted. If we run the ruby script provided by Omnissa support we get on the user the result back: Checking user 'USERNAME@DOMAIN.nl' in host 'dc01.DOMAIN.nl' at 2024-08-12 09:09:03 UTC-------------------------------- Searching started at 2024-08-12 09:09:03 UTC for 15 seconds Exception while searching user 'USERNAME@DOMAIN.nl' in host 'dc01.DOMAIN.nl': An existing connection was forcibly closed by the remote host. @ io_fillbuf - fd:7 If we change the guid USERNAME to USERNAME1 all works like a charm. Did anybody out there has a simulair issue and what was / is the solution besides recreating the users. We do net get errors on the domain controllers and the appvolume logfiles say the same as the above ruby error message. If someone has/had this issue then what was the sollution? Hopefully somebody can help me (us) out. Edit: We received a privat fix that will probably implemented in other versions and that is succesfull. regards, Hans
  15. We install the full suite and licenses are user based. We have the full monty with licenses so far. If that changes we simply create groups wether or not they have shortcuts.
×
×
  • Create New...