App Volumes

apiVersion: soultec.ch/v1kind: Solutionmetadata: name: omnissa/horizon/omnissa-app-volumes locale: en labels: vendor: Omnissa App Volumes capability/modern-workplace: 1.84 capability/virtualization: 1.38 vendor/omnissa: 1.96 annotations: source: src/content/solutions/en/omnissa/horizon/omnissa-app-volumes.md route: /en/solutions/omnissa/horizon/omnissa-app-volumes/ schema: /nerd/schema/solutions.json markdown: /en/solutions/omnissa/horizon/omnissa-app-volumes.mdspec: title: App Volumes tags: [modern-workplace, virtualization] vendors: [omnissa] summary: >- Applications arrive as containers that attach at logon instead of being baked into the image. One master image instead of one per department. photoNeed: >- A Horizon or Workspace ONE session in use: a virtual desktop on a real screen, or a thin client on a real desk stub: false draft: false kind: product addon: false vendorName: Omnissa App Volumes status: current practice: >- Draft, not yet reviewed. The work in an App Volumes project is packaging, not installing. We budget for the applications that resist it, because every estate has four or five, and finding them in week eight is what makes the project late. practiceReview: true sections: - heading:

What it is

body: | App Volumes delivers applications as virtual containers rather than as installations. A package holds one application or several. It is assigned to a person or to a machine, and it is there the moment they sign in, without having been installed into the image. - heading:

How it works

body: | The App Volumes Manager is the console and the bookkeeping: it holds the packages and the writable volumes, it talks to vCenter for the virtual machines, and it keeps every assignment in a SQL database. At logon the packages assigned to that person are attached to their profile and the applications in them are immediately available. If the person has a writable volume, that attaches too, and it is where their own data and settings live. At logoff both detach and nothing of them remains on the machine. - heading:

What it is for

body: | Cutting the number of master images. An estate that installs every application into the image ends up with an image per department, and then maintains all of them on patch Tuesday. With App Volumes there is one image and a catalogue of packages, and updating an application means updating a package rather than rebuilding a desktop. The second use is licensing. An application that only forty people are licensed for is assigned to forty people, instead of sitting installed on nine hundred desktops and being counted there. - heading:

What to watch

body: | Not every application packages cleanly. Drivers, kernel-level components and anything that insists on writing to the same path at install time are the usual arguments. Find those before the design, not after the pilot: the ones that resist are also the ones the business cannot do without.status: corpus: 293 services: - {ref: services/digital-workplace, score: 0.49} - {ref: services/modern-workplace, score: 0.45} - {ref: services/platform, score: 0.34} posts: - {ref: posts/soultec-ag-erreicht-hochsten-omnissa-partnerstatus, score: 1.00} - {ref: posts/ubersicht-omnissa-horizon-fur-citrix-kunden, score: 1.00} - {ref: posts/wie-du-citrix-hinter-dir-lasst-mit-omnissa-horizon-und-soultec-den-perfekten-umstieg-meistern, score: 1.00} - {ref: posts/how-to-horizon-verbindung-absichern-teil-2, score: 1.00} - {ref: posts/unrecognized-requests-xml-api, score: 1.00} - {ref: posts/nvidia-l40s-horizon-provisioning-error, score: 1.00} experts: - {ref: experts/valentina-cicmak, score: 0.50} - {ref: experts/oliver-erismann, score: 0.46} - {ref: experts/mike-schmid, score: 0.41} neighbours: - {ref: solutions/omnissa/horizon/dynamic-environment-manager, score: 1.00} - {ref: solutions/omnissa/horizon, score: 1.00} - {ref: solutions/omnissa/horizon/horizon-8, score: 1.00}

{ "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": { "name": "omnissa/horizon/omnissa-app-volumes", "locale": "en", "labels": { "vendor": "Omnissa App Volumes", "capability/modern-workplace": "1.84", "capability/virtualization": "1.38", "vendor/omnissa": "1.96" }, "annotations": { "source": "src/content/solutions/en/omnissa/horizon/omnissa-app-volumes.md", "route": "/en/solutions/omnissa/horizon/omnissa-app-volumes/", "schema": "/nerd/schema/solutions.json", "markdown": "/en/solutions/omnissa/horizon/omnissa-app-volumes.md" } }, "spec": { "title": "App Volumes", "tags": [ "modern-workplace", "virtualization" ], "vendors": [ "omnissa" ], "summary": "Applications arrive as containers that attach at logon instead of being baked into the image. One master image instead of one per department.", "photoNeed": "A Horizon or Workspace ONE session in use: a virtual desktop on a real screen, or a thin client on a real desk", "stub": false, "draft": false, "kind": "product", "addon": false, "vendorName": "Omnissa App Volumes", "status": "current", "practice": "Draft, not yet reviewed. The work in an App Volumes project is packaging, not installing. We budget for the applications that resist it, because every estate has four or five, and finding them in week eight is what makes the project late.\n", "practiceReview": true }, "sections": [ { "heading": "

What it is

", "body": "App Volumes delivers applications as virtual containers rather than as installations. A\npackage holds one application or several. It is assigned to a person or to a machine, and\nit is there the moment they sign in, without having been installed into the image." }, { "heading": "

How it works

", "body": "The App Volumes Manager is the console and the bookkeeping: it holds the packages and the\nwritable volumes, it talks to vCenter for the virtual machines, and it keeps every\nassignment in a SQL database.\n\nAt logon the packages assigned to that person are attached to their profile and the\napplications in them are immediately available. If the person has a writable volume, that\nattaches too, and it is where their own data and settings live. At logoff both detach and\nnothing of them remains on the machine." }, { "heading": "

What it is for

", "body": "Cutting the number of master images. An estate that installs every application into the\nimage ends up with an image per department, and then maintains all of them on patch\nTuesday. With App Volumes there is one image and a catalogue of packages, and updating an\napplication means updating a package rather than rebuilding a desktop.\n\nThe second use is licensing. An application that only forty people are licensed for is\nassigned to forty people, instead of sitting installed on nine hundred desktops and being\ncounted there." }, { "heading": "

What to watch

", "body": "Not every application packages cleanly. Drivers, kernel-level components and anything that\ninsists on writing to the same path at install time are the usual arguments. Find those\nbefore the design, not after the pilot: the ones that resist are also the ones the business\ncannot do without." } ], "status": { "corpus": 293, "services": [ { "ref": "services/digital-workplace", "score": "0.49" }, { "ref": "services/modern-workplace", "score": "0.45" }, { "ref": "services/platform", "score": "0.34" } ], "posts": [ { "ref": "posts/soultec-ag-erreicht-hochsten-omnissa-partnerstatus", "score": "1.00" }, { "ref": "posts/ubersicht-omnissa-horizon-fur-citrix-kunden", "score": "1.00" }, { "ref": "posts/wie-du-citrix-hinter-dir-lasst-mit-omnissa-horizon-und-soultec-den-perfekten-umstieg-meistern", "score": "1.00" }, { "ref": "posts/how-to-horizon-verbindung-absichern-teil-2", "score": "1.00" }, { "ref": "posts/unrecognized-requests-xml-api", "score": "1.00" }, { "ref": "posts/nvidia-l40s-horizon-provisioning-error", "score": "1.00" } ], "experts": [ { "ref": "experts/valentina-cicmak", "score": "0.50" }, { "ref": "experts/oliver-erismann", "score": "0.46" }, { "ref": "experts/mike-schmid", "score": "0.41" } ], "neighbours": [ { "ref": "solutions/omnissa/horizon/dynamic-environment-manager", "score": "1.00" }, { "ref": "solutions/omnissa/horizon", "score": "1.00" }, { "ref": "solutions/omnissa/horizon/horizon-8", "score": "1.00" } ] }}

apiVersion = "soultec.ch/v1"kind = "Solution"[metadata]name = "omnissa/horizon/omnissa-app-volumes"locale = "en"[metadata.labels]vendor = "Omnissa App Volumes""capability/modern-workplace" = "1.84""capability/virtualization" = "1.38""vendor/omnissa" = "1.96"[metadata.annotations]source = "src/content/solutions/en/omnissa/horizon/omnissa-app-volumes.md"route = "/en/solutions/omnissa/horizon/omnissa-app-volumes/"schema = "/nerd/schema/solutions.json"markdown = "/en/solutions/omnissa/horizon/omnissa-app-volumes.md"[spec]title = "App Volumes"tags = ["modern-workplace", "virtualization"]vendors = ["omnissa"]summary = "Applications arrive as containers that attach at logon instead of being baked into the image. One master image instead of one per department."photoNeed = "A Horizon or Workspace ONE session in use: a virtual desktop on a real screen, or a thin client on a real desk"stub = falsedraft = falsekind = "product"addon = falsevendorName = "Omnissa App Volumes"status = "current"practice = '''Draft, not yet reviewed. The work in an App Volumes project is packaging, not installing. We budget for the applications that resist it, because every estate has four or five, and finding them in week eight is what makes the project late.'''practiceReview = true[[sections]]heading = "

What it is

"body = '''App Volumes delivers applications as virtual containers rather than as installations. Apackage holds one application or several. It is assigned to a person or to a machine, andit is there the moment they sign in, without having been installed into the image.'''[[sections]]heading = "

How it works

"body = '''The App Volumes Manager is the console and the bookkeeping: it holds the packages and thewritable volumes, it talks to vCenter for the virtual machines, and it keeps everyassignment in a SQL database.At logon the packages assigned to that person are attached to their profile and theapplications in them are immediately available. If the person has a writable volume, thatattaches too, and it is where their own data and settings live. At logoff both detach andnothing of them remains on the machine.'''[[sections]]heading = "

What it is for

"body = '''Cutting the number of master images. An estate that installs every application into theimage ends up with an image per department, and then maintains all of them on patchTuesday. With App Volumes there is one image and a catalogue of packages, and updating anapplication means updating a package rather than rebuilding a desktop.The second use is licensing. An application that only forty people are licensed for isassigned to forty people, instead of sitting installed on nine hundred desktops and beingcounted there.'''[[sections]]heading = "

What to watch

"body = '''Not every application packages cleanly. Drivers, kernel-level components and anything thatinsists on writing to the same path at install time are the usual arguments. Find thosebefore the design, not after the pilot: the ones that resist are also the ones the businesscannot do without.'''[status]corpus = 293[[status.services]]ref = "services/digital-workplace"score = "0.49"[[status.services]]ref = "services/modern-workplace"score = "0.45"[[status.services]]ref = "services/platform"score = "0.34"[[status.posts]]ref = "posts/soultec-ag-erreicht-hochsten-omnissa-partnerstatus"score = "1.00"[[status.posts]]ref = "posts/ubersicht-omnissa-horizon-fur-citrix-kunden"score = "1.00"[[status.posts]]ref = "posts/wie-du-citrix-hinter-dir-lasst-mit-omnissa-horizon-und-soultec-den-perfekten-umstieg-meistern"score = "1.00"[[status.posts]]ref = "posts/how-to-horizon-verbindung-absichern-teil-2"score = "1.00"[[status.posts]]ref = "posts/unrecognized-requests-xml-api"score = "1.00"[[status.posts]]ref = "posts/nvidia-l40s-horizon-provisioning-error"score = "1.00"[[status.experts]]ref = "experts/valentina-cicmak"score = "0.50"[[status.experts]]ref = "experts/oliver-erismann"score = "0.46"[[status.experts]]ref = "experts/mike-schmid"score = "0.41"[[status.neighbours]]ref = "solutions/omnissa/horizon/dynamic-environment-manager"score = "1.00"[[status.neighbours]]ref = "solutions/omnissa/horizon"score = "1.00"[[status.neighbours]]ref = "solutions/omnissa/horizon/horizon-8"score = "1.00"

<?xml version="1.0" encoding="UTF-8"?><manifest kind="Solution"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>omnissa/horizon/omnissa-app-volumes</name> <locale>en</locale> <labels> <vendor>Omnissa App Volumes</vendor> <entry key="capability/modern-workplace">1.84</entry> <entry key="capability/virtualization">1.38</entry> <entry key="vendor/omnissa">1.96</entry> </labels> <annotations> <source>src/content/solutions/en/omnissa/horizon/omnissa-app-volumes.md</source> <route>/en/solutions/omnissa/horizon/omnissa-app-volumes/</route> <schema>/nerd/schema/solutions.json</schema> <markdown>/en/solutions/omnissa/horizon/omnissa-app-volumes.md</markdown> </annotations> </metadata> <spec> <title>App Volumes</title> <tags> <item>modern-workplace</item> <item>virtualization</item> </tags> <vendors> <item>omnissa</item> </vendors> <summary>Applications arrive as containers that attach at logon instead of being baked into the image. One master image instead of one per department.</summary> <photoNeed>A Horizon or Workspace ONE session in use: a virtual desktop on a real screen, or a thin client on a real desk</photoNeed> <stub>false</stub> <draft>false</draft> <kind>product</kind> <addon>false</addon> <vendorName>Omnissa App Volumes</vendorName> <status>current</status> <practice>Draft, not yet reviewed. The work in an App Volumes project is packaging, not installing. We budget for the applications that resist it, because every estate has four or five, and finding them in week eight is what makes the project late. </practice> <practiceReview>true</practiceReview> </spec> <sections> <section> <heading>

What it is

</heading> <body>App Volumes delivers applications as virtual containers rather than as installations. Apackage holds one application or several. It is assigned to a person or to a machine, andit is there the moment they sign in, without having been installed into the image. </body> </section> <section> <heading>

How it works

</heading> <body>The App Volumes Manager is the console and the bookkeeping: it holds the packages and thewritable volumes, it talks to vCenter for the virtual machines, and it keeps everyassignment in a SQL database.At logon the packages assigned to that person are attached to their profile and theapplications in them are immediately available. If the person has a writable volume, thatattaches too, and it is where their own data and settings live. At logoff both detach andnothing of them remains on the machine. </body> </section> <section> <heading>

What it is for

</heading> <body>Cutting the number of master images. An estate that installs every application into theimage ends up with an image per department, and then maintains all of them on patchTuesday. With App Volumes there is one image and a catalogue of packages, and updating anapplication means updating a package rather than rebuilding a desktop.The second use is licensing. An application that only forty people are licensed for isassigned to forty people, instead of sitting installed on nine hundred desktops and beingcounted there. </body> </section> <section> <heading>

What to watch

</heading> <body>Not every application packages cleanly. Drivers, kernel-level components and anything thatinsists on writing to the same path at install time are the usual arguments. Find thosebefore the design, not after the pilot: the ones that resist are also the ones the businesscannot do without. </body> </section> </sections> <status> <corpus>293</corpus> <services> <item> <ref>services/digital-workplace</ref> <score>0.49</score> </item> <item> <ref>services/modern-workplace</ref> <score>0.45</score> </item> <item> <ref>services/platform</ref> <score>0.34</score> </item> </services> <posts> <item> <ref>posts/soultec-ag-erreicht-hochsten-omnissa-partnerstatus</ref> <score>1.00</score> </item> <item> <ref>posts/ubersicht-omnissa-horizon-fur-citrix-kunden</ref> <score>1.00</score> </item> <item> <ref>posts/wie-du-citrix-hinter-dir-lasst-mit-omnissa-horizon-und-soultec-den-perfekten-umstieg-meistern</ref> <score>1.00</score> </item> <item> <ref>posts/how-to-horizon-verbindung-absichern-teil-2</ref> <score>1.00</score> </item> <item> <ref>posts/unrecognized-requests-xml-api</ref> <score>1.00</score> </item> <item> <ref>posts/nvidia-l40s-horizon-provisioning-error</ref> <score>1.00</score> </item> </posts> <experts> <item> <ref>experts/valentina-cicmak</ref> <score>0.50</score> </item> <item> <ref>experts/oliver-erismann</ref> <score>0.46</score> </item> <item> <ref>experts/mike-schmid</ref> <score>0.41</score> </item> </experts> <neighbours> <item> <ref>solutions/omnissa/horizon/dynamic-environment-manager</ref> <score>1.00</score> </item> <item> <ref>solutions/omnissa/horizon</ref> <score>1.00</score> </item> <item> <ref>solutions/omnissa/horizon/horizon-8</ref> <score>1.00</score> </item> </neighbours> </status></manifest>

What it is

How it works

What it is for

What to watch

What it is

How it works

What it is for

What to watch

What it is

How it works

What it is for

What to watch

What it is

How it works

What it is for

What to watch

What it is

How it works

What it is for

What to watch

What we do with it

Posts about it

soulTec reaches the highest Omnissa partner status

An overview of Omnissa Horizon for Citrix customers

Leaving Citrix behind, with Omnissa Horizon and soulTec

Securing the Horizon connection – part 2

Unrecognized requests in the Horizon Console XML API log

NVIDIA L40s: Horizon cannot provision desktop pools with vGPU profiles

Who works with it

Valentina Cicmak

Oliver Erismann

Mike Schmid