build 7bbbddf7 | content blog-content@c8490fa · 338 posts | profiles 20 · corpus 267 | 0 skipped | | format
apiVersion: soultec.ch/v1kind: Solutionmetadata: name: omnissa/workspace-one-uem locale: en labels: vendor: Omnissa Workspace ONE capability/modern-workplace: 2.11 capability/endpoint-security: 3.54 vendor/omnissa: 2.39 annotations: source: src/content/solutions/en/omnissa/workspace-one-uem.md route: /en/solutions/omnissa/workspace-one-uem/ schema: /nerd/schema/solutions.json markdown: /en/solutions/omnissa/workspace-one-uem.mdspec: title: Workspace ONE tags: [modern-workplace, endpoint-security] vendors: [omnissa] summary: >- Device management and access for laptops, phones and tablets. A device is managed because it reaches data, not because the company bought it. 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 Workspace ONE status: current practice: >- Draft, not yet reviewed. The technical half of a UEM project is rarely the problem. The hard half is what may be enforced on someone's personal phone, and no console answers that. We settle it with HR and data protection before the first policy exists. practiceReview: true sections: - heading:

What it is

body: | Workspace ONE manages endpoints across their whole life: enrolment, configuration, software, policy and wipe. Windows, macOS, iOS and Android run through one console. There is an access side to it as well. Whether a device may reach an application depends on the state of that device, not only on the password of the person holding it. - heading:

What it is for

body: | Estates where devices leave the building. A laptop in the field and a phone with company mail on it are the same problem: data on hardware that is not on the company network. For desk-bound machines already running under group policy, the benefit is smaller and the change is not. - heading:

What changed

body: | Workspace ONE has belonged to Omnissa since the end-user computing business was spun out of VMware. If your paperwork still says VMware, find out where you stand.status: corpus: 267 services: - {ref: services/modern-workplace, score: 0.81} - {ref: services/digital-workplace, score: 0.46} - {ref: services/security, score: 0.23} posts: - {ref: posts/soultec-ag-erreicht-hochsten-omnissa-partnerstatus, score: 0.51} - {ref: posts/ubersicht-omnissa-horizon-fur-citrix-kunden, score: 0.51} - {ref: posts/wie-du-citrix-hinter-dir-lasst-mit-omnissa-horizon-und-soultec-den-perfekten-umstieg-meistern, score: 0.51} - {ref: posts/how-to-horizon-verbindung-absichern-teil-2, score: 0.51} - {ref: posts/unrecognized-requests-xml-api, score: 0.51} - {ref: posts/nvidia-l40s-horizon-provisioning-error, score: 0.51} experts: - {ref: experts/valentina-cicmak, score: 0.40} - {ref: experts/mike-schmid, score: 0.36} neighbours: - {ref: solutions/omnissa, score: 0.86} - {ref: solutions/igel, score: 0.70} - {ref: solutions/omnissa/horizon/omnissa-app-volumes, score: 0.51}
{ "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": { "name": "omnissa/workspace-one-uem", "locale": "en", "labels": { "vendor": "Omnissa Workspace ONE", "capability/modern-workplace": "2.11", "capability/endpoint-security": "3.54", "vendor/omnissa": "2.39" }, "annotations": { "source": "src/content/solutions/en/omnissa/workspace-one-uem.md", "route": "/en/solutions/omnissa/workspace-one-uem/", "schema": "/nerd/schema/solutions.json", "markdown": "/en/solutions/omnissa/workspace-one-uem.md" } }, "spec": { "title": "Workspace ONE", "tags": [ "modern-workplace", "endpoint-security" ], "vendors": [ "omnissa" ], "summary": "Device management and access for laptops, phones and tablets. A device is managed because it reaches data, not because the company bought it.", "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 Workspace ONE", "status": "current", "practice": "Draft, not yet reviewed. The technical half of a UEM project is rarely the problem. The hard half is what may be enforced on someone's personal phone, and no console answers that. We settle it with HR and data protection before the first policy exists.\n", "practiceReview": true }, "sections": [ { "heading": "

What it is

",
"body": "Workspace ONE manages endpoints across their whole life: enrolment, configuration,\nsoftware, policy and wipe. Windows, macOS, iOS and Android run through one console.\n\nThere is an access side to it as well. Whether a device may reach an application depends\non the state of that device, not only on the password of the person holding it." }, { "heading": "

What it is for

",
"body": "Estates where devices leave the building. A laptop in the field and a phone with company\nmail on it are the same problem: data on hardware that is not on the company network.\n\nFor desk-bound machines already running under group policy, the benefit is smaller and the\nchange is not." }, { "heading": "

What changed

",
"body": "Workspace ONE has belonged to Omnissa since the end-user computing business was spun out\nof VMware. If your paperwork still says VMware, find out where you stand." } ], "status": { "corpus": 267, "services": [ { "ref": "services/modern-workplace", "score": "0.81" }, { "ref": "services/digital-workplace", "score": "0.46" }, { "ref": "services/security", "score": "0.23" } ], "posts": [ { "ref": "posts/soultec-ag-erreicht-hochsten-omnissa-partnerstatus", "score": "0.51" }, { "ref": "posts/ubersicht-omnissa-horizon-fur-citrix-kunden", "score": "0.51" }, { "ref": "posts/wie-du-citrix-hinter-dir-lasst-mit-omnissa-horizon-und-soultec-den-perfekten-umstieg-meistern", "score": "0.51" }, { "ref": "posts/how-to-horizon-verbindung-absichern-teil-2", "score": "0.51" }, { "ref": "posts/unrecognized-requests-xml-api", "score": "0.51" }, { "ref": "posts/nvidia-l40s-horizon-provisioning-error", "score": "0.51" } ], "experts": [ { "ref": "experts/valentina-cicmak", "score": "0.40" }, { "ref": "experts/mike-schmid", "score": "0.36" } ], "neighbours": [ { "ref": "solutions/omnissa", "score": "0.86" }, { "ref": "solutions/igel", "score": "0.70" }, { "ref": "solutions/omnissa/horizon/omnissa-app-volumes", "score": "0.51" } ] }}
apiVersion = "soultec.ch/v1"kind = "Solution"[metadata]name = "omnissa/workspace-one-uem"locale = "en"[metadata.labels]vendor = "Omnissa Workspace ONE""capability/modern-workplace" = "2.11""capability/endpoint-security" = "3.54""vendor/omnissa" = "2.39"[metadata.annotations]source = "src/content/solutions/en/omnissa/workspace-one-uem.md"route = "/en/solutions/omnissa/workspace-one-uem/"schema = "/nerd/schema/solutions.json"markdown = "/en/solutions/omnissa/workspace-one-uem.md"[spec]title = "Workspace ONE"tags = ["modern-workplace", "endpoint-security"]vendors = ["omnissa"]summary = "Device management and access for laptops, phones and tablets. A device is managed because it reaches data, not because the company bought it."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 Workspace ONE"status = "current"practice = '''Draft, not yet reviewed. The technical half of a UEM project is rarely the problem. The hard half is what may be enforced on someone's personal phone, and no console answers that. We settle it with HR and data protection before the first policy exists.'''practiceReview = true[[sections]]heading = "

What it is

"
body = '''Workspace ONE manages endpoints across their whole life: enrolment, configuration,software, policy and wipe. Windows, macOS, iOS and Android run through one console.There is an access side to it as well. Whether a device may reach an application dependson the state of that device, not only on the password of the person holding it.'''[[sections]]heading = "

What it is for

"
body = '''Estates where devices leave the building. A laptop in the field and a phone with companymail on it are the same problem: data on hardware that is not on the company network.For desk-bound machines already running under group policy, the benefit is smaller and thechange is not.'''[[sections]]heading = "

What changed

"
body = '''Workspace ONE has belonged to Omnissa since the end-user computing business was spun outof VMware. If your paperwork still says VMware, find out where you stand.'''[status]corpus = 267[[status.services]]ref = "services/modern-workplace"score = "0.81"[[status.services]]ref = "services/digital-workplace"score = "0.46"[[status.services]]ref = "services/security"score = "0.23"[[status.posts]]ref = "posts/soultec-ag-erreicht-hochsten-omnissa-partnerstatus"score = "0.51"[[status.posts]]ref = "posts/ubersicht-omnissa-horizon-fur-citrix-kunden"score = "0.51"[[status.posts]]ref = "posts/wie-du-citrix-hinter-dir-lasst-mit-omnissa-horizon-und-soultec-den-perfekten-umstieg-meistern"score = "0.51"[[status.posts]]ref = "posts/how-to-horizon-verbindung-absichern-teil-2"score = "0.51"[[status.posts]]ref = "posts/unrecognized-requests-xml-api"score = "0.51"[[status.posts]]ref = "posts/nvidia-l40s-horizon-provisioning-error"score = "0.51"[[status.experts]]ref = "experts/valentina-cicmak"score = "0.40"[[status.experts]]ref = "experts/mike-schmid"score = "0.36"[[status.neighbours]]ref = "solutions/omnissa"score = "0.86"[[status.neighbours]]ref = "solutions/igel"score = "0.70"[[status.neighbours]]ref = "solutions/omnissa/horizon/omnissa-app-volumes"score = "0.51"
<?xml version="1.0" encoding="UTF-8"?><manifest kind="Solution"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>omnissa/workspace-one-uem</name> <locale>en</locale> <labels> <vendor>Omnissa Workspace ONE</vendor> <entry key="capability/modern-workplace">2.11</entry> <entry key="capability/endpoint-security">3.54</entry> <entry key="vendor/omnissa">2.39</entry> </labels> <annotations> <source>src/content/solutions/en/omnissa/workspace-one-uem.md</source> <route>/en/solutions/omnissa/workspace-one-uem/</route> <schema>/nerd/schema/solutions.json</schema> <markdown>/en/solutions/omnissa/workspace-one-uem.md</markdown> </annotations> </metadata> <spec> <title>Workspace ONE</title> <tags> <item>modern-workplace</item> <item>endpoint-security</item> </tags> <vendors> <item>omnissa</item> </vendors> <summary>Device management and access for laptops, phones and tablets. A device is managed because it reaches data, not because the company bought it.</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 Workspace ONE</vendorName> <status>current</status> <practice>Draft, not yet reviewed. The technical half of a UEM project is rarely the problem. The hard half is what may be enforced on someone's personal phone, and no console answers that. We settle it with HR and data protection before the first policy exists. </practice> <practiceReview>true</practiceReview> </spec> <sections> <section> <heading>

What it is

</heading>
<body>Workspace ONE manages endpoints across their whole life: enrolment, configuration,software, policy and wipe. Windows, macOS, iOS and Android run through one console.There is an access side to it as well. Whether a device may reach an application dependson the state of that device, not only on the password of the person holding it. </body> </section> <section> <heading>

What it is for

</heading>
<body>Estates where devices leave the building. A laptop in the field and a phone with companymail on it are the same problem: data on hardware that is not on the company network.For desk-bound machines already running under group policy, the benefit is smaller and thechange is not. </body> </section> <section> <heading>

What changed

</heading>
<body>Workspace ONE has belonged to Omnissa since the end-user computing business was spun outof VMware. If your paperwork still says VMware, find out where you stand. </body> </section> </sections> <status> <corpus>267</corpus> <services> <item> <ref>services/modern-workplace</ref> <score>0.81</score> </item> <item> <ref>services/digital-workplace</ref> <score>0.46</score> </item> <item> <ref>services/security</ref> <score>0.23</score> </item> </services> <posts> <item> <ref>posts/soultec-ag-erreicht-hochsten-omnissa-partnerstatus</ref> <score>0.51</score> </item> <item> <ref>posts/ubersicht-omnissa-horizon-fur-citrix-kunden</ref> <score>0.51</score> </item> <item> <ref>posts/wie-du-citrix-hinter-dir-lasst-mit-omnissa-horizon-und-soultec-den-perfekten-umstieg-meistern</ref> <score>0.51</score> </item> <item> <ref>posts/how-to-horizon-verbindung-absichern-teil-2</ref> <score>0.51</score> </item> <item> <ref>posts/unrecognized-requests-xml-api</ref> <score>0.51</score> </item> <item> <ref>posts/nvidia-l40s-horizon-provisioning-error</ref> <score>0.51</score> </item> </posts> <experts> <item> <ref>experts/valentina-cicmak</ref> <score>0.40</score> </item> <item> <ref>experts/mike-schmid</ref> <score>0.36</score> </item> </experts> <neighbours> <item> <ref>solutions/omnissa</ref> <score>0.86</score> </item> <item> <ref>solutions/igel</ref> <score>0.70</score> </item> <item> <ref>solutions/omnissa/horizon/omnissa-app-volumes</ref> <score>0.51</score> </item> </neighbours> </status></manifest>
Solution · Omnissa

Workspace ONE

Omnissa Workspace ONE

The vendor calls it: Omnissa Workspace ONE

Device management and access for laptops, phones and tablets. A device is managed because it reaches data, not because the company bought it.

Omnissa Platinum Partner

Topics Modern Workplace 2.11 Endpoint Security 3.54
Vendors Omnissa 2.39
03Services
06Posts
02Capabilities
267Corpus

What it is

Workspace ONE manages endpoints across their whole life: enrolment, configuration, software, policy and wipe. Windows, macOS, iOS and Android run through one console.

There is an access side to it as well. Whether a device may reach an application depends on the state of that device, not only on the password of the person holding it.

What it is for

Estates where devices leave the building. A laptop in the field and a phone with company mail on it are the same problem: data on hardware that is not on the company network.

For desk-bound machines already running under group policy, the benefit is smaller and the change is not.

What changed

Workspace ONE has belonged to Omnissa since the end-user computing business was spun out of VMware. If your paperwork still says VMware, find out where you stand.

What we do with it

Draft, unreviewed

Draft, not yet reviewed. The technical half of a UEM project is rarely the problem. The hard half is what may be enforced on someone's personal phone, and no console answers that. We settle it with HR and data protection before the first policy exists.

This paragraph is a draft and nobody at soulTec has confirmed it yet. Everything above it describes the product and is checkable against the vendor.

Posts about it

soulTec reaches the highest Omnissa partner status

We have reached Platinum, the highest partner status in the newly introduced Omnissa partner programme.

Modern Workplace 2.11 Virtualization 1.37

An overview of Omnissa Horizon for Citrix customers

A guide for Citrix administrators who want to understand how Horizon is put together, and how its components map onto a Citrix environment.

Modern Workplace 2.11 Virtualization 1.37

Leaving Citrix behind, with Omnissa Horizon and soulTec

Wondering how to move off your existing Citrix environment without interrupting operations? More and more of our customers are looking at it because Citrix keeps getting more expensive.

Modern Workplace 2.11 Virtualization 1.37

Securing the Horizon connection – part 2

Part 1 covered how locked.properties secures the connection between Horizon Connection Servers and clients, mainly through balancedHost. There are cases where that causes trouble.

Modern Workplace 2.11 Virtualization 1.37

Unrecognized requests in the Horizon Console XML API log

The Horizon Console dashboard shows a warning about unrecognized requests on the XML API protocol connection. Usually these have no direct effect on user sessions.

Modern Workplace 2.11 Virtualization 1.37

NVIDIA L40s: Horizon cannot provision desktop pools with vGPU profiles

A customer recently bought several NVIDIA L40s cards to extend their Horizon environment. Provisioning failed for every desktop pool using an L40s vGPU profile.

Modern Workplace 2.11 Virtualization 1.37

Who works with it

Do you work with this? Take a look at our open roles.