-
Posts
776 -
Joined
-
Last visited
-
Days Won
39
Content Type
Forums
Articles
Labs
Videos
TechZone
Citrix Community Articles
Events
Profiles
Posts posted by Jeff Riechers
-
-
Any reason you are putting both under a single delivery group instead of creating 2 delivery groups? Then you could do user based targeting and lock them to a gpu/non-gpu session.
If the apps on the machine are the same, and you don't care which machine people get you can just deploy both Machine Catalogs to the 1 delivery group and have just a single Desktop defined. That will keep people to just a single machine. But when you add additional Desktop options in the list that is designed to give users multiple desktops in the same environment.
-
I host Linux Desktops on XenServer and VMWare in my datacenter. And am running CentOS, Ubuntu, and Devian. But you could host them really on any hypervisor, including cloud or on physical.
Hosting them on a supported hypervisor allows you to use MCS to create multiple read only copies of the Linux Desktop. But if you use a physical machine, or a Linux KVM hosting a linux instance you can still allow direct connections to that resource with either Citrix On-premise or Citrix Cloud.
Also if you use nfs mount points you can mount your home share to a network location for creating persistent user "profiles" on multiple machine even if they are non-persistent. I can provide more info on that if you would like.
-
What is the login before this? Are they doing SAML or AD username and password. Connecting via Storefront, or Gateway?
-
By default it should only allow a single connection. If they attempt to launch a second desktop it should just reconnect them to the previous session.
However if you define 2 desktops in the Delivery group then they will publish as separate items. Is there a particular reason to have 2 desktops defined in the delivery group?
-
So we can bascially setup an unlimited number of on-premise Active directory domains to Citrix Cloud. But it looks like you can only use a single Azure Active Directory.
Is there any way to add multiple Azure AD connections to Citrix Cloud for clients with multiple domains?
-
Because they are GPU added machines. When you use a GPU the hypervisor console is not accessible.
-
I was asked this by a client, and was wondering if anyone has real world numbers.
Looking to see how much bandwidth the cloud connector uses just for brokering user connections, director, etc. No ICA flow.
Citrix has tons of sizing guides for the hardware for Connectors, but nothing for bandwidth.
-
Can't console. Vcenter hosted machines.
-
LDAP will still work, you just can't do the verification tests. What I do is set it up, then attempt to login. If there are any failures you can use /tmp/aaad.debug to troubleshoot it.
And just to let everyone know, the new versions released today it is still broken. But at least they call it out in the known issues.
-
LDAP will still work, you just can't do the verification tests. What I do is set it up, then attempt to login. If there are any failures you can use /tmp/aaad.debug to troubleshoot it.
-
That hotfix was for the vcenter server, so it had no impact on the ADC networking.
ADC 12.1 works fine on a fully patched 7.0 updated esxi host.
-
I have a client that we are deploying new VDA builds on. Exactly the same hardware specs, only change is we are going with 2103 VDA instead of 1912 vda.
All applications work great, but any heavy graphic browser based apps run horribly. Noticeable lag on mouse movement.
We have no BCR enabled, and have GPU acceleration enabled on the web browsers.
Anyone else seen this, or have any info on optimizing the browser apps the same as desktop apps?
-
New 12.1 build addresses this.
-
It's a known issue with the Citrix Client. It doesn't capture those extra key commands to pass through. However there are some mac side modifications you can make to get that process back up and running. Check out this article for help.
https://gist.github.com/jdleslie/9a3566037e35437a3846c428f306318f
-
What does director show is happening during the black screen process?
What size are the profiles? If you have someone get a new profile does it address it?
-
If you go through the cloud.com site to the gateway service yes it works. You just have to enable the feature in your Workspace.
-
1
-
-
MAK activations periodically expire the activation token and then force a re-activation. This can quickly chew up your MAK licenses.
Better option is to get a KMS key so that all your activations are local and you don't run the risk of exhausting your seats when non-persistent machines restart.
-
This is an issue with the services it uses for files on demand. Similar to how it doesn't work on 2016, but does work in 2019.
Did you install with the "OneDriveSetup.exe /allusers" setting?
Also your agent needs to be above 1907 for it to be fully supported.
I would recommend rolling out a newer Windows with the latest App Layering Agent.
-
What MFA are you using?
-
Can confirm, this fixed it.
Is 12.1 going to get fixed as well though?
-
I just tested in my environment. Even though the LDAP is working, the test is failing. Looks like a bug. There is a similar one with the latest ADM with certificate verification.
-
I can second this. With how the storage is setup in Azure you will notice huge image updates, it's not just you.
With the possible ability to run PVS in Azure coming, you might be able to use that to address things, or just plan on increasing deployment times of images.
-
Is the application hanging, or is the session just not delivering data to the end user.
-
This happens because OneDrive looks for the location of the cache, and unless it is completely masked and appears only as local it won't activate.
FSLogix with it's file system driver can fully mask that correctly. So you probably are going to want to upgrade.
How is it not working? Is files on demand not an option? Does it not sync?
Windows 10 login screen appearing after launching XenDesktop
in XenDesktop 7.x
Posted
Is the machine accessible when it sits here? Since it does populate the credentials after waiting that leads me to some form of pre-logon service holding up the sson process.