DaaS Onboarding Checklist

Configuration and Incident Data Collection

Customer Information
Customer Details, to be completed by Stellar.

Used for VM names, network hostnames, and internal references.

Primary point of contact for all technical matters.

DaaS Implementation
Specify information applicable to the entire DaaS implementation.

The VDI desktops will belong to a subnet. By default, Stellar will choose a subnet for VDI desktops based on the data collected in the Networking tab of the IaaS Order Form. However, if you wish to use a specific subnet, you may specify one.

Please ensure it is at least a /22 in size.


The URL users with which users will access VMware Horizon via the Horizon client or web browser. Usually, customers choose something like 'horizon.example.com'.

An SSL certificate is required, and may be a wildcard or standard certificate.

Infrastructure
DaaS requires an infrastructure that provides DNS, DHCP, File Shares, and several software applications for management.

- DNS: Usually a domain controller is used for DNS. If two are available, please specify both.

- DHCP: Usually a domain controller is used for DHCP. Best Practice is to have two deployed with failover load balancing.

- File Shares: Several shares for user data (folder redirection and profiles), policy configs, etc. are needed. Please list the server(s) desired for these shares.

Server FQDNIPUseStatusNotesActions
No infrastructure servers added yet. Click the button below to add your first server.
Desktops
Specify the quantity of Windows Desktops per profile and include any additional notes.
ProfilevCPUvRAMStorageQtyNotes / Requirements
Value12 GB75 GB
Professional24 GB75 GB
Premium48 GB75 GB
Performance816 GB75 GB
Software Applications
Add a new row for each software application that will be available on Orion Virtual Desktops.
App NameVersionShortcuts (D/T/S)LicensingAV Excl.
No software applications listed.
Drive Mappings
Add a new row for each drive mapping available on Orion Virtual Desktops. Note: Letters C, E, and Z are excluded.
Display NameLetterRemote PathConditions/Groups
No drive mappings defined.
Printer Mappings
Define shared network printers to be mapped for users. Only one printer per user should be marked as "Default".
Printer NameRemote PathDefaultConditions
No printer mappings defined.
DaaS Configuration Settings
Override or specify configuration details for common DaaS settings.
Default: 120 Minutes

Specify the amount of time, in minutes, that a logged in user may be idle before the system disconnects their session. This does not log them out of their Windows desktop, but rather disconnects their VDI session.

Default: Disabled

Enable or Disable USB Redirection. If enabled, USB devices attached to the VDI client will be virtually attached to the user's VDI desktop. This can be a security risk, enable with caution.

Default: Client-In

Select a Clipboard Sharing option. If set to Client-to-Desktop, items copied to the clipboard on the VDI client can be pasted on the VDI desktop. If set to Desktop-to-Client, items copied to the clipboard on the VDI desktop can be pasted on the VDI client. If set to Bidirectional, both Client-to-Desktop and Desktop-to-Client will be in effect. If set to Disabled, no clipboard sharing is allowed. This can be a security risk, enable with caution.

Default: Disabled

Select a Client Drive Redirection option. If set to Read/Write, the home folder of the VDI client will be attached to the user's VDI desktop as a network share with read/write permissions. If set to Read Only, the home folder of the VDI client will be attached to the user's VDI desktop as a network share with read-only permissions. If set to Disabled, no folders will be attached to the VDI desktop. This can be a security risk, enable with caution.

Default: 180 Minutes

Specify the amount of time, in minutes, that a logged in user may be idle before the system forcibly logs them out from their Windows VDI desktop.

Use this field to document exceptions or specific Security Group requirements related to the session policies above.

Submission Security
This form requires a secondary authorization key to verify the sender's identity and prevent unauthorized API submissions.

Submission will be rejected if this key is missing or invalid.