[FSLogix vs UPM 2209]

Microsoft definitely care about it, and we should see features increase in the not-too-distant future, however Microsoft vs Citrix on the profile management maturity, release cadence, feature development, bug fix front.... Citrix has always won that race.

 

Again, personally I like UPM and where it is going/how it has been going, but plenty of happy customers on FSLogix as well - I am on the fence, I don't think you can go wrong either way - whatever aligns with your project/supportability/longevity of your EUC roadmaps etc

[Is Vcloud Director is compatible with Citrix MCS and citrix Daas ?]

I don't believe so, but I also cannot speak for the roadmap - in my experience, the demand is very low, and use of vCloud directory does not mean that integration with VC isn't possible - so my guess is it's not likely on the list, but of again, that could be wrong

[FSLogix vs UPM 2209]

So there are a couple of things to consider 

 

I did a write up a while back delving into the two here:
https://jkindon.com/citrix-upm-and-fslogix-containers/

 

The trajectory of UPM is awesome, you can see how much focus there is with quarterly feature releases per below 

https://jkindon.com/the-evolution-of-citrix-profile-management/

 

OneDrive was the last frontier really 

 

I firmly believe that UPM is the superior solution in terms of functionality, support and focus, however, you won’t make a bad decision by sticking with FSLogix either

 

my discussions with customers was pretty much anything net new was UPM containers where I would have positioned FSLogix before, but also always delving into the need for containers at all, and for those that had fslogix, there was no reason to rip it out by any means 

[Is Vcloud Director is compatible with Citrix MCS and citrix Daas ?]

no, there is no integration with vCloud director. You will need delegated access directly to VC

[Access is denied to File Explorer Quick Access section on server 2019 (MCS)]

adding 2012 R2 lockdown GPO's to a 2019 build is a recipe for disaster - really need to start that from scratch and give it the respect it deserves - it's a very different platform

[Force Configuration Set]

go into the WEM console -> Select your configuration set -> Active Directory Objects -> Machines

 

Add your OU

[WEM Service without AD]

You can use wem for your scenario 

 

https://docs.citrix.com/en-us/workspace-environment-management/service/get-started/enroll-agent.html#introduction

[User can log into Storefront but is rejected by the Citrix server]

Are you using FAS in the environment? I’ve seen this with FAS but it’s not mentioned above 

[Power state unknown]

Unfortunately you will need to talk to Citrix support as they can see the cloud hosted delivery controller logs 

[Citrix DaaS MCS Azure VMs Premium SSD Storage with Performance level P50]

Does the new ARM template spec help here (I haven't tried)

https://docs.citrix.com/en-us/citrix-daas/install-configure/resource-location/azure-resource-manager.html#create-a-machine-catalog-using-an-azure-resource-manager-image

[how to set session numbers to a specific VDA in delivery group]

Create a Tag. Apply the Tag to the VDA

 

Create a policy with a load management config of max sessions = x

 

Filter the policy to the Tag

[Updating persistent VDI Desktops vs Shared Desktop in MCS.]

18 hours ago, Akiyo Hiroshi said:

In Pooled VDI desktops Update Machine option is not available in Citrix Studio;

 

Yes it most definitely is. I can't see your catalog, but maybe its not an MCS provisioned catalog?

 

This is core to Citrix capability and has been around for a long long time 

[How does PVS use less storage than MCS?]

with fast clone in the mix, i would think the ratio of storage consumption for mcs to pvs is impacted more so by the number of datastores you have MCS provisioning into

 

PVS is simple - there is a write-cache per VM and that's about it

 

MCS has the initial snapshot, a rollback instance, any "not yet updated instances" + any "not yet cleaned" stuff + (MCSIO cache if in use per VM) - that is then replicated across all datastores that MCS uses - so the different can be significant

[Updating persistent VDI Desktops vs Shared Desktop in MCS.]

pooled desktops are managed the same as pooled shared desktops - the same rules apply

 

if you are talking about persistent machines, then no, you need something else to manage those machines once they have been provisioned currently

[Unable to register VDA]

you cannot do that without hybrid rights for 2203, any public Cloud VDA will fail without that bolt on

[PVS or MCS for a 5000 single site VDI deployment?]

Nutanix HCI makes MCS shine - I would lean away from PVS on Nutanix for the most part and let MCS do it's thing

[Multiple Azure AD for citrix cloud?]

https://docs.citrix.com/en-us/citrix-secure-private-access/adaptive-authentication-service.html

[7.15 --> 7 2203 Export/Import Scripts???]

some here too

https://github.com/JamesKindon/Citrix/tree/master/Migration Scripts

[Dynamic Desktop and Application delivery with XenDesktop 1912LTSR based on the Client-IP.]

You could try playing with BrokerAccessPolicyRules - particularly the ExcludedClientIPFilter or IncludeClientIPFilter related settings

 

https://developer-docs.citrix.com/projects/delivery-controller-sdk/en/latest/Broker/Set-BrokerAccessPolicyRule/

[New Way To Perform Published Application Isolated Enviroments]

how about VM hosted apps? https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/technical-overview/delivery-methods.html#vm-hosted-apps

 

This might get you where you want to be?

[Put into maintance mode and deleting multiple machines from catalog via script with import server list txt file]

Probably best to reach out to a local consulting provider for some assistance

[Clone Server 2019 Remote Desktop License Server issue]

nice one - long live MCS provisioning ?

 

Have you seen this one? -You might need to follow this all the way through

https://docs.microsoft.com/en-us/troubleshoot/azure/virtual-machines/troubleshoot-rdp-no-license-server

 

[Gateway Callback fails after upgrade to Storefront 2203]

https://docs.citrix.com/en-us/storefront/current-release/whats-new/known-issues.html
 

ciphers….?

[Wemm Application and VUEMRSAV]

This is a confirmed bug - I hit it today as well, it doesn’t cause any functional problems 

[Migrate VDI to new VMware hypervisor]

On 3/12/2022 at 8:19 AM, Chris Retter said:

WARNING: Neither hypervisor connection nor machine ID can be specified for an unmanaged machine
Get-BrokerMachine : Object does not exist

I probably need to add way better error handling on this script - but straight off the bat it looks like you may not be targeting a power managed catalog as the destination - it has to have a hosting connection associated with it back to the same hypervisor as the MCS source