Jump to content

James Kindon

Moderators
  • Posts

    1,351
  • Joined

  • Last visited

  • Days Won

    66

Posts posted by James Kindon

  1. There is absolutely nothing wrong with using local profiles if you don't have a need for roaming them - just think about backing up critical data (if there is any) - but outside of that, users will love you for it experience wise....no point adding in complexity when it's not needed.

     

    You might want to look at the ServerVDI switches on your ServerOS if there is only going to be 1:1 relationships.

  2. Honestly, that far back, I would just create a new site with new everything, and then migrate configuration across, and cutover users -> There are so many factors in play with upgrades this far back, new -> Migrate is going to be smoother and allow you to de-risk everything

    • Like 1
  3. This is something Container technology can definitely help with from a roaming perspective. Citrix Profile Management has some selective controls for what goes where if capacity and performance is a consideration 

     

    Where possible, it's best to try and find the machine installers - a quick google shows 

     

    For postman: https://learning.postman.com/docs/administration/managing-enterprise-deployment/

    For Grasshopper - worth asking the question directly to the vendor

     

    Per User isn't great in non-persistent environments - I have dealt with customers that block it (AppMasking, or Application Whitelisting etc) to avoid it coming onboard.

  4. You can export storefront settings to a file and then import them to guarantee identical configurations. The process I would take there is 

     

    Build new Servers -> deploy identical version of StoreFront to that which is in prod -> Export/Import StoreFront configuration -> Upgrade new StoreFront to appropriate release

     

    The limitation with the export/import is that the versions MUST be identical https://docs.citrix.com/en-us/storefront/1912-ltsr/export-import-storefront-config.html

  5. For this scenario you would want to turn upm off entirely and optimise the default user profile -  it doesn’t sound like you need profile management at all 

     

    there are other factors that come into this around provisioning methods etc, but effectively it sounds like you want the following 

     

    user logs in -> default profile created -> policy controls all settings -> user logs off -> everything deleted -> repeat 

     

    This is all local profile style operations - if using UPM you would be looking at mandatory profiles (have a google) 

  6. Yeah this process is horrible and has been for a long time… amazingly it’s been somewhat optimised in multi session windows 10 but not enterprise… ridiculous really 

     

    There is a new feature in the latest release that I have haven’t tested which appears to be the start of trying to address this issue https://learn.microsoft.com/en-us/fslogix/whats-new

     

    That’s about all you can play with in a safe fashion 

×
×
  • Create New...