DATASHEET

VMware Workspace ONE

Deploy and Consume -
Mobile
AT A GLANCE Service Overview
The VMware Workspace ONE Deploy and Consume – Mobile service provides remotely
The VMware Workspace ONE Deploy
delivered guided implementation and post go-live assistance. The service helps
and Consume – Mobile service
customers plan, design, implement, deploy, and operate VMware Workspace ONE® UEM
provides remotely delivered guided
for mobile device use cases. The service drives the value realization of the Workspace
implementation and post go-live
ONE suite, including Workspace ONE® UEM, Workspace ONE® Access™, Workspace ONE®
assistance, targeting comprehensive
Intelligence™, and Workspace ONE® Assist™.
value realization and platform
consumption.
Engagement Timeline
KEY BENEFITS
The service typically takes 20 weeks to fully deliver (excluding the time it takes for our
• Guided implementation of customer to procure hardware (where applicable) and meet pre-requisites) with the pre-
Workspace ONE for mobile use defined scope outlined in this data sheet. The VMware delivery methodology consists of
cases meetings, solutioning workshops, software installation and configuration sessions.
• Drive adoption and consumption
Initiate
through post-implementation
• Introduction meeting
assistance for both pilot and
production phases • Datasheet review
• Confirm scheduling
• Expert assistance through
planning, execution, and rollout Plan
• Project oversight through • Review scope, objectives, and key success criteria.
dedicated VMware project • Review technical architecture deployment options.
manager • Review user experiences for mobile device footprint
SKUS • Build, review, and deliver pre-requisites for customer completion.
Perpetual License SKU: • Download and set up any required software/tools.
VA-PS-DNC-MOB
Execute
Subscription License SKU: • Software installation of necessary components.
WD[X]-DNCMOB-1TCT0-[Y] • Technical integration with customer infrastructure.
• Configuration and validation of customer use case.
• Pilot and production rollout assistance.

Close
• Implementation monitoring and maintenance.
• Customer support transition.

1
VMware Workspace ONE Deploy and Consume: Mobile

The following depicts a typical project plan. Customer-specific project execution timelines
may vary:
Workspace ONE Deploy & Consume: Mobile - DURATION (WEEEKS)
Phases
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
Phase: Discovery & Assess
Phase: Pre-Requirements
Phase: Design & Plan
Phase: Kickoff
Phase: Execute Infrastructure
Phase: Execute Integrations
Phase: Execute Mobile Experience
Phase: Pilot & Adopt
Phase: Close & Transition to GSS

Key
Customer owned: Pre-Requisites
Joint Owned: Core Design & Build
Joint Owned: Mobile Workstream
Joint Owned: Close and Transition

Responsibilities
All VMware and customer responsibilities are listed in the Service Deliverables section.
The ownership is defined as follows:

1. Primary Owner = VMware: VMware is responsible for the delivery of the

component, with minimal assistance from the customer’s project team.
2. Joint: VMware and the customer’s project team are jointly responsible for the
delivery of the component.
3. Primary Owner = Customer: Customer is responsible for the delivery of the
component, with recommendations from VMware as needed.

About VMware Professional Services

VMware Professional Services transform IT possibilities into business outcomes. Our
comprehensive portfolio of services uncovers and exploits the unique opportunities
made possible by VMware technology. Drawing on our unparalleled product expertise
and customer experience, we collaborate with your team to address the technical,
people, process, and financial considerations for IT transformation to deliver results that
are positive, tangible, and material to IT and your business.

Service Scope
The service will include implementation of a Workspace ONE UEM and Workspace ONE
Access environments, with integration supported by components installed on-premises in
the customer’s data centers or through VMware hosted Workspace ONE SaaS
environments (where applicable).

The implementation scope includes:

1. Review of pre-requisites.
2. Implementation of one highly available Workspace ONE UEM on-premises
production environment, spanning up to two (2) datacenters, supporting up to
five thousand (5,000) devices in each datacenter.
3. Implementation of one highly available Workspace ONE Access on-premises
production environment, spanning up to two (2) data centers, supporting up to
five thousand (5,000) devices in each datacenter.
4. Implementation of VMware Unified Access Gateway™ servers (supporting
Content, VMware Tunnel™, Web, and Secure Email Gateway).
5. Configuration of Workspace ONE Intelligence (License permitting).
6. Configuration of Workspace ONE Assist (License permitting).

DATASHEET | 2
VMware Workspace ONE Deploy and Consume: Mobile

7. Integration of Workspace ONE Access with select 3rd party Identity Providers
(IDPs) Okta/Ping/ADFS.
8. Application integration into Workspace ONE Access.
9. Directory services integration.
10. Implementation of mobile device enrollment strategies.
11. Integration of productivity applications (Web / Content / VMware Tunnel).
12. Integration of E-mail: Up to two (2) clients (Gmail, iOS Native, Boxer, Outlook).
13. Implementation of E-mail authentication.

Service Assumptions
1. VMware will assist with the installation/configuration of one environment under
this datasheet. The environment type (SaaS or On-Premises) will be
implemented based on the license type purchased by the customer.
2. VMware will deliver this Service using global resources.
3. VMware will assist with up to three different device types/operating systems for
configuration and setup (iOS, Android, Chrome). Rugged Android, Rugged
Windows, Mobile/CE devices, and printers are out-of-scope.
4. VMware will integrate only one corporate e-mail infrastructure via one E-mail
Management integration (PowerShell, SEG v2, or SEG on UAG).
5. Alignment of all configurations and policy design with customer’s requirements
is the responsibility of the customer. VMware will provide recommendations and
guidance.
6. The procurement and installation of hardware for any on-premises is the
responsibility of the customer. VMware may provide recommendations.
7. Configuration of software other than VMware is the responsibility of the
customer, and aligned deliverables will be out-of-scope if third party software is
not available
8. Third-Party web applications: Any SAML 2.0 compliant web applications can be
integrated with Workspace ONE Access. The customer is required to work
independently with the service provider to provide VMware with all required
integration details or SAML meta-data. These include, but are not limited to the
following:
• Login Redirection
• Assertion Consumer Service URL
• Recipient Name
• Signing Certificates
• Audience
• Assertion Lifetime
• Attribute Mapping
• Application Parameters
9. Internally Developed Web Applications: Any SAML 2.0 compliant internal
application can be integrated with Workspace ONE Access. The customer is
required to provide VMware with all required integration details or SAML meta-
data. These include, but are not limited to the following:
• Login Redirection
• Assertion Consumer Service URL
• Signing Certificates
• Audience
• Assertion Lifetime
• Attribution Mapping

DATASHEET | 3
VMware Workspace ONE Deploy and Consume: Mobile

• Application Parameters
10. Native Application One Touch SSO Integration: Native applications supporting
SAML single-sign-on can be configured to accept Identity Provider initiated SSO
through VMware managed devices. The customer is required to work
independently with the service provider to provide VMware with all required
integration details, including attributes to be passed via VMware.
11. VMware cannot guarantee that individual third-party SAML endpoints will
integrate successfully with Workspace ONE Access given unforeseen customer
or service configurations or limitations.
12. Workspace ONE Access for App Catalog will be implemented with Workspace
ONE licensing.
13. Customer-specific customization for Workspace ONE Access is out-of-scope.
14. Certificate Authority integration can be included for the use of One Touch Single
Sign-On with Workspace ONE Access. Certificate usage for Wi-Fi, VPN, e-mail
authentication is out-of-scope.
15. Review of the systems and knowledge transfer will be provided throughout the
configuration; however, formal training is out-of-scope.
16. The implementation of derived credentials is out-of-scope.
17. Integration of Citrix XenApp/XenDesktop is out of scope
18. Horizon True SSO integration is out of scope
19. Cisco ISE integration is out of scope
20. Service user experience outcomes not identified or pre-requirements not ready
prior to Phase 3 (Execute) will be considered out-of-scope.
21. Services or products that have been deprecated or reached end of life are out-
of-scope.
22. Pre-requisites must be completed for all installation components before any
Phase 3 installation activities will be performed.
23. VMware and the customer will work closely together to ensure that project
scope and expected outcomes remain consistent, and issues are resolved in a
timely manner.
24. All work will be delivered remotely via screen-share. On-site travel is out-of-
scope.
25. All work, documentation and deliverables will be conducted during VMware
local business hours and will be provided in English.
26. Any feature not listed in Services Deliverables is out of scope
27. The staffing for this datasheet assumes all work will be completed part time,
within a maximum of 20 weeks after the initiation of Phase 3 (Execute).
28. The period of performance is limited to 12 months from the purchase date.
29. The scope of the services is deemed complete upon ONE of the following
criteria - whichever comes first:
a. Upon completion of all deliverables within scope of the engagement as
agreed upon in the Design Sign-off Form.
b. After 20 weeks from the date the project is moved to Phase 3
(Execute) as agreed upon in the Design Sign-off Form.
c. After 12 months from purchase date.
d. If the services were purchased using PSO credits the services expire
the same time the credits expire unless a credit extension is requested.
Work with your Account Executive to determine a plan for all remaining
credits on the account and request an extension.

DATASHEET | 4
VMware Workspace ONE Deploy and Consume: Mobile

Service Deliverables
The following is a list of all the potential deliverables that the customer may select. Items
will be listed on the project schedule as agreed to by customer and VMware during
Phase 1 (Initiate) and Phase 2 (Plan).

Phase 1 (Initiate)
ID Description Tool / Primary Comments
Deliverable Owner

1.1 Introduction Meeting Joint

1.2 Review Datasheet Customer Understand
service
assumptions
and scope
1.3 Register for My My Workspace Customer Required to
Workspace ONE ID ONE access
resources and
training

Phase 2 (Plan)
ID Description Tool / Primary Comments
Deliverable Owner

2.1 Plan Meeting Joint

2.2 Review scope/objectives Joint Scope

and success criteria for definition
customer’s deployment

2.3 Review recommended VMware VMware Hardware sizing

architecture deployment recommended and
options architecture architecture
guide
2.4 Review user experience VMware VMware Scope
and outline user Solution Design Definition
experience outcomes

2.5 Provide and review pre- Pre-Installation VMware Pre-requisites

requisites requirements clarified with
worksheet customer
network,
database,
server, and
security teams
2.6 Review best practices VMware

2.7 Download and setup any Customer

required software/tools

2.8 Summarize pre-work, Customer action VMware

next steps, and items
requirements for Phase
3 (Execute)

DATASHEET | 5
VMware Workspace ONE Deploy and Consume: Mobile

ID Description Tool / Primary Comments

Deliverable Owner

Customer requirements to proceed to Phase 3 (Execute)

2.9 Procure virtual and Customer Servers
physical servers accessible and
software pre-
requisites
completed
2.10 Stage required Open Customer If applicable
Virtual Appliance (OVA)
files
2.11 Configure Customer Networking
networking/firewall and
service accounts for
integration
2.12 Complete and return Installation pre- Customer
pre-installation requisites
requirements worksheet
2.13 Design approval and Documented Customer Confirm the
sign-off scope and project design,
design for baring change
customer control

Phase 3 (Execute)
ID Description Tool / Primary Owner Comments
Deliverable

Step 1: Installation
3.1.1 Validate Completion of Pre-installation Joint
pre-requisites requirements
worksheet
3.1.2 Installation of VMware VMware VMWare If required
UEM servers installation guide
3.1.3 Installation of VMware VMWare If required
Workspace ONE Access installation guide
servers
3.1.4 Installation of VMware VMware VMWare
connectors installation guide

3.1.5 Installation of Unified VMware VMWare For Per-App

Access Gateways installation guide VPN Content,
Web, SEG
3.1.6 Installation of Secure E- VMware VMware
mail Gateway v2 (SEG installation guide
v2) or SEG on UAG, or
configuration of
PowerShell
3.1.7 Integration with VMware VMware VMware On-Prem if
SaaS E-mail Notification installation guide required
Service v2 (ENS v2)

DATASHEET | 6
VMware Workspace ONE Deploy and Consume: Mobile

ID Description Tool / Primary Owner Comments

Deliverable

3.1.8 Installation of VMware VMware

Workspace ONE installation guide
Intelligence connectors
Step 2: Configuration and Integration of UEM

3.2.1 Configure Organizational Joint

Group structure

3.2.2 Register e-mail domain Joint

for auto discovery

3.2.3 Assistance configuring Joint

Directory Services
integration
3.2.4 Assist with creating two Joint Refer to
(2) user experiences that Appendix A
work for up to three (3) Choose (2)
mobile device operating
systems (iOS, Android,
Chrome)
3.2.5 Assist with creating up Joint
to three of each of the
following policies, one
for each device
Operating System (if
applicable):
• Enrollment Restriction
Policy (i.e., #of
devices, Ownership
Types, etc.)
• Compliance Policy (i.e.,
Comprised Status,
Encryption, Application
List, etc.,)
• E-mail Compliance
Policy (i.e.,
Unmanaged Devices,
Compromised Devices,
Encryption, etc.)
• Privacy Policy (i.e.,
Collect GPS Data,
Allow Full Wipe, etc.)
• Terms of Use (i.e.,
Platforms,
Geographies, etc.)
3.2.6 Configure Data Loss Joint
Prevention (DLP)
• Application
Containerization
Controls
• "Open in" Controls

DATASHEET | 7
VMware Workspace ONE Deploy and Consume: Mobile

ID Description Tool / Primary Owner Comments

Deliverable

• Email Attachment
Management
• Authentication
• Single Sign-on
• Integrated
Authentication
• Compromised
protection
• Network Access
Control
3.2.7. Configure application Joint
management policies
• Internal Application (5
per device OS)
• App Store integration
3.2.8 Assist with the Joint Customer
installation of up to three owns writing
client scripts from the and
Workspace ONE console supporting
scripts.
VMware will
help publish.
3.2.9 Assist with setup, Joint
association, and
installation of Volume
Purchase Program (VPP)
applications (sToken or
License-Based). This will
include:
• Upload of
sToken/redemption
codes
• Register for up to 3
deployment types with
VPP Terms of Use
• Register using app
catalog and automatic
• Install application on
same devices as
Auto/On-Demand
3.2.10 VMware Tunnel Joint
configuration

3.2.11 VMware Web Joint

configuration
3.2.12 Configuration of Joint
Content:
• Content Repository
integration

DATASHEET | 8
VMware Workspace ONE Deploy and Consume: Mobile

ID Description Tool / Primary Owner Comments

Deliverable

• Editing and Annotation

• Personal Content
• SCL Sync

Step 3: Configuration and Integration of Workspace ONE Access

3.3.1 Workspace ONE Access Joint Integration

configuration with
• Sync with Active customer’s
Directory users and endpoints for
groups single sign-on
• Configure the Unified
Application Catalog.
• Enable User AD
Password change
• Integration with
Workspace ONE UEM
3.3.2 Assist with SAML Joint
Integration of the
following:
• Workspace ONE UEM
Admin Authentication
• Workspace ONE UEM
User Authentication
• Up to three (3)
standard SAML
application
• Up to three (3) non-
modern authentication
applications (Cert /
Basic authentication)
• Up to three (3)
weblinks in the catalog
• Up to one (1) Horizon
Pod integrations
3.3.3 Configure the following Joint
authentication methods:
• Directory
• iOS Mobile SSO
• Android Mobile SSO
3.3.4 Setup Network Ranges Joint
for Authentication Policy

3.3.5 Setup of three Joint

Application-Specific
Authentication Policies

DATASHEET | 9
VMware Workspace ONE Deploy and Consume: Mobile

ID Description Tool / Primary Owner Comments

Deliverable

Step 4: Configuration of Workspace One Intelligence

3.4.1 Configure up to one Joint

Workspace ONE
Intelligence custom
report
3.4.2 Configure up to one Joint
Workspace ONE
Intelligence automation
(out of the box)
Step 5: Configuration of Hub Services Features

3.5.1 Knowledge Transfer to Joint

customer’s project team
about Hub Services
People Search
Home Tab
Notifications
3.5.2 Configure up to one Joint
Mobile Flow (out of the
box connectors)
Step 6: Pilot Readiness and Deployment

3.6.1 Define Enrollment / Joint

Registration Strategy for
new devices
3.6.2 Identify suitable pilot Customer
user group
3.6.3 User communication to Joint
pilot group
3.6.4 Up to two (2) weeks of Joint Refer to
pilot group support, Appendix B
targeting a friendly Pilot
of customer’s IT and
operations teams per
Appendix B
Step 7: Production Roll-out

3.7.1 Identify production user Customer

groups
3.7.2 User communication to Joint
Production group(s)

3.7.3 Up to four (4) weeks of Joint Refer to

go-live assistance for Appendix B
production group(s) per
Appendix B

DATASHEET | 10
VMware Workspace ONE Deploy and Consume: Mobile

Phase 4: Close
ID Description Tool / Primary Comments
Deliverable Owner

4.1 Implement Monitoring Customer

and Maintenance
4.2 Transition to support VMWare delivers Joint Open support
software related items owned by
services Global Support
completion Services
materials and
contact
information for
support
4.1 Implement Monitoring Customer
and Maintenance

Appendix A: User Experiences

A user experience is defined as the unique combination of device enrollment methods,
policies, and mobile applications. For example (these are just examples and will not limit a
customer’s ability to customize what works for your business during solution design
conversations:

• User Experience 1: Knowledge workers often leverage corporate owned

devices. These workers need access to email, internal websites and internal
content safely and securely on their device. Because these are corporate
owned devices, the business wants to implement tighter restrictions (like locking
down the camera), requiring complex passcodes to open the device, or among
other things, requiring passcodes into Workspace ONE productivity
applications. Customers often choose for this device posture to be the “de-
facto” device posture for users enrolling leveraging the device with Apple
Business Manager or take advantage of Android for Work, Work Managed
policies.
• User Experience 2: In addition to user experience 1, knowledge workers often
want to enroll their personally owned (BYO) mobile devices into Workspace
ONE. Similar to the above, they would like access to corporate email, internal
websites, and internal content. As these are personally owned devices,
administrators and HR teams want to provide the same tools but often decide
to offer a more employee friendly touch to privacy and restriction policies.
Customers often enable this workflow, with a “by approval only” approach.
When approved, a user’s device will be registered in the console, and an email
will be generated walking the user through the appropriate enrollment
procedures.
• User Experience 3: A line of business kiosk devices need to be outside each
conference room so staff can register and check into conference rooms. These
devices will require access to a single locked application, leaving staff no ability
to access settings or other applications. Administrators, if required, would be
able to log of out the locked application to access the core OS.
• User Experience 4: A line of business device allowing users, between shifts, to
check in the device they were leveraging, giving the next staff member the
opportunity to check out the device as themselves. Different users will require
different app access, and those settings should be taken into consideration
automatically by policies established in the console.

DATASHEET | 11
VMware Workspace ONE Deploy and Consume: Mobile

LEARN MORE Appendix B: Go-Live support

Visit vmware.com/services. During the go-live support phases, the primary professional services consultant is
available for the following activities:
FOR MORE INFORMATION
Contact a Professional Services expert • Assistance up to eight (8) hours per week
at • Answer questions from Customer’s Workspace ONE IT team that deployed the
vmware.com/company/contact.html. solution
• Assist the customer with resolving configuration issues and transitioning product
issues (not configuration related) to long term support for resolution or feature
requests.
• Assist with collection of pertinent logs and other relevant information required
to help resolve support tickets.
• Assist with raising tickets with VMWare’s technical support teams on behalf of
the Customer for non-configuration related issues.

Direct support of end-users or of staff outside of the customer’s designated Workspace

ONE team is out of scope.

TERMS AND CONDITIONS

This datasheet is for informational
purposes only. VMWARE MAKES NO
WARRANTIES, EXPRESS OR IMPLIED,
IN THIS DATASHEET. All VMware
service engagements are governed by
the VMware Professional Services
General Terms and Conditions. If you
are located in the United States, the
VMware contracting entity for the
service will be VMware, Inc. If you are
outside the United States, the VMware
contracting entity will be VMware
International Limited.
If you purchase this packaged service
outside of the ELA, the service must
be delivered and accepted within the
first 12 months of the purchase, or the
service will be forfeited. Pricing for this
service includes travel and other
expenses. For detailed pricing, contact
your local VMware representative.

VMware, Inc. 3401 Hillview Avenue Palo Alto CA 94304 USA Tel 877-486-9273 Fax 650-427-5001 www.vmware.com.
Copyright © 2021 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents
listed at vmware.com/go/patents. VMware is a registered trademark or trademark of VMware, Inc. and its subsidiaries in the United States and other jurisdictions. All other marks and names mentioned
herein may be trademarks of their respective companies. 8/21