lkowalski's Posts

This message is related to the prerequisite of mapping some specific mandatory user attributes to AD attributes, using the Workspace ONE Access admin UI. The "sid" is one of those user attributes that needs to be mapped. In the user guide for next-gen, start at the bottom of this page: https://docs.vmware.com/en/VMware-Horizon-Cloud-Service---next-gen/services/hzncloud-nextgen.pdf#page=33 Read onwards from the heading Configure Workspace ONE Access User Attributes for Integration with Horizon Cloud at the bottom of that page, where it says "If you are using Workspace ONE Access as your identity provider for Horizon Cloud, use the Workspace ONE Access console to configure the mandatory user attributes. The purpose of this procedure is to add additional Workspace ONE Access attributes that are mandatory to successfully configure Workspace ONE Access as the identity provider for Horizon Cloud, and to map those required attributes to your Active Directory attributes. The userPrincipalName, objectGuid, sid, and netBios Workspace ONE Access attributes are mandatory and must be mapped to the appropriate Active Directory attributes as described in the following steps."

my subscriptions should still work as expected A role is set on a specific *scope*.  It is described in the Access Control section of that article you provided the link for: docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-overview#access-control "Role assignments - associate a definition with an identity (user or group) for a particular scope (subscription, resource group, or resource)." For the node, Contributor role is set on the scope of the specific *service principal* that you're going to use for that node. I don' t believe it has to be set at a larger scope than the specific service principal. So I'm not sure why the question is "the subscriptions working as expected". Are you asking whether you must apply the Contributor role scoped at some level other than the specific service principal for use with the node?

My current understanding is that the Node Deployment wizard validation step requires that Contributor role be used on the service principal. Meaning that if the service principal info entered into the wizard (info like the application ID and authentication key) do not match a service principal having the Contributor role, the wizard's validation step will not succeed to let you deploy the node. And that is why the doc topic "Create the Required Service Principal by Creating an Application Registration" in the Getting Started Guide states "...you must ... assign the Contributor role...".  ("must" = "the system requires it"). Hope that helps, Lee Anne

In the Connector UI, on the Packaged Apps - ThinApp page, did you select the check box to enable account-based access and provide a user account/password that has read access to the network share? If not, try that, and re-sync the packages using the Connector UI's Sync Now button. The HTTP download capability of the client depends on having account-based access enabled in the Connector UI, afaik.

I think that the Windows desktop client has a way to specify No Sync for the files if the Windows client is installed via the command line, and the command-line installer option ENABLE_DATA is set to zero (0). The command-line options for the Windows desktop client are documented here: Command-Line Installer Options for Horizon Workspace for Windows However, I believe there is nothing comparable for the Mac desktop client.

The steps to add a Web application are mostly covered in this Horizon Workspace 1.5 Administrator's Guide topic: http://pubs.vmware.com/horizon-workspace-15/topic/com.vmware.hs-administrator.doc_15/GUID-F2E0CD4C-3E18-4CC8-9CA7-C37B860FEBE9.html You posted that you read through the documents -- would you please share the specific questions that you have? It might help if you can share more details on what sort of Web application you are trying to add.

Hi Craig, Sometimes there are invisible characters that are invalid. These characters can be accidentally introduced in the names. A common situation is introducing the backspace character into a file name. The backspace character is CONTROL-H, Ctrl-H, ^H, or \010. Users accidentally introduce the Ctrl-H character into the file names when they use the backspace during a file naming operation and their terminal is incorrectly configured. This Troubleshooting topic in the Administrator's Guide describes the potential causes for this situation and how to diagnose it: http://pubs.vmware.com/horizon-workspace-15/topic/com.vmware.hs-administrator.doc_15/GUID-66F3A345-AE1C-461D-9B7E-749FEFA38D61.html

The Administrator's Guide has a list of each client app and what the users can do in each client. For the iOS client, it says: "iPad users can view their entitled virtual desktops using Horizon View Client for iOS." So are you trying the iOS app on an iPad or on an iPhone? For Android, are you using the "Horizon Workspace Client for Android" app or the VMware Switch app for VMware Ready Android phones? For the "Horizon Workspace Client for Android" app, the Administrator's Guide says that users can access files or Web applications, but not View desktops from that client app. To enable the Applications tab in the client app, you'd need a Web application entitled to that user. Have you set up any Web applications in the Catalog to entitle to users?

Is this a vCenter Server in which there was a previous deployment of the Horizon Workspace vApp? I found this topic about unused extensions in the Horizon Workspace documentation, and I've been wondering if it could be related to that symptom: Deleting Unused Extensions from vCenter