iForum – Notes on RES Powerfuse

  1. Challenges
    1. How do I ensure that users get their own personalised workspace
    2. How do I ensure that end user productivity impact is minimised during the migration
    3. How do I deal with some continued use of some local applications
    4. How do I ensure that my Virtual machines continue to be up to date
  2. This list of challenges seems to be very RES specific, perhaps that’s not surprising
  3. The workspace can be modified based on:
    1. Who you are
    2. Time of day
    3. Location
    4. Whether you have a token
  4. What is a workspace
    1. Personalisation, apps desktop, environment, portability, location sensing – with RES this is downloaded just in time
      1. Seems to require you to manually figure out what needs to be persistent between sessions.  if you have 4500 applications that’s a complex job.
    2. Security, Applications, files and folders, local disks, access to removable drives, IP connections
      1. seems to be very similar to group policy, but had the benefit of a common set of policies across operating systems.  Not sure whether it depends on the client device being domain joined, if not that would be an advantage as well
      2. more granular than GPO in some areas at least
      3. nice feature that allows a USB key to be used as a rule that can govern anything else, for example the ability to run a particular application can be linked to the presence or absence of a USB key
    3. Reliability, logon performance, session, cpu, memory, logoff
    4. Administration
      1. delegated admin, building blocks and templates, usage reporting, license metering, analysis and audit
    5. Integration
      1. Uses variety of databases
      2. Integrates with Active Directory
      3. Workspace integration between apps delivered locally and apps delivered by presentation server or xen desktop
      4. Runbook automation, using Wisdom – this seems to be a distributed systems management product – simillar to BMC Configuration manager or SCCM
        1. detects when snapshots are being used, when they are rolled back etc.  so that the cmdb maps to the actual configuration of the client, even if a snapshot rollback occurs, it will reapply lost changes.

Steve Richards

I'm retired from work as a business and IT strategist. now I'm travelling, hiking, cycling, swimming, reading, gardening, learning, writing this blog and generally enjoying good times with friends and family

Leave a Reply

Your email address will not be published. Required fields are marked *