Troubleshooting Shared HoloLens: Your Dynamics 365 Guides Solution

Table of Contents

Symptoms: Guide Discovery Challenges on Shared HoloLens Devices¶

Encountering difficulties in locating specific guides within Microsoft Dynamics 365 Guides while utilizing a shared HoloLens device can be a frustrating hurdle, particularly in environments where multiple users depend on the same device for operational tasks. Imagine a scenario where a team of technicians in a manufacturing plant relies on HoloLens devices for step-by-step instructions to assemble complex machinery. When a technician puts on a shared HoloLens and expects to immediately access the guide relevant to their current task, only to find it missing, significant delays and disruptions can occur. This inability to promptly access crucial guides can lead to decreased efficiency, workflow interruptions, and potential errors in task execution. The symptom manifests when the user navigates through the Dynamics 365 Guides application on the HoloLens, expecting to see a list of available guides, but the specific guide they require is conspicuously absent from the displayed options. This absence isn’t due to a technical malfunction of the HoloLens itself, but rather points towards an access control issue related to the shared account being used on the device.

Cause: Access Restrictions for Shared Accounts¶

The root cause of this issue typically lies in the access permissions configured for the shared account utilized on the HoloLens device. In Dynamics 365 Guides, access to individual guides is meticulously controlled through a role-based access system. This means that each user account, including shared accounts, must be explicitly granted permission to access specific guides or sets of guides. When a HoloLens is designated as a shared device, it often operates under a generic, shared user account to streamline device management and accessibility for multiple users. However, if this shared account has not been explicitly granted access to the guide in question, the guide will not be visible or accessible when a user logs in with that shared account on the HoloLens. This access control mechanism is in place to ensure data security, maintain guide integrity, and allow organizations to precisely manage which users can access sensitive or task-specific instructional content. Therefore, the “missing guide” symptom on a shared HoloLens device is almost invariably a direct consequence of insufficient access permissions assigned to the shared account within the Dynamics 365 Guides environment.

Resolution: Granting Access to Shared Accounts¶

To resolve the issue and ensure that guides are accessible on shared HoloLens devices, the primary step is to grant the necessary access permissions to the shared account. This process typically involves an administrator or guide author within the Dynamics 365 Guides environment. The administrator needs to identify the specific shared account being used on the HoloLens device that is experiencing the problem. Once the shared account is identified, the administrator must then navigate to the Dynamics 365 Guides authoring interface. Within the authoring interface, they will need to locate the specific guide that users are unable to find on the shared HoloLens. After selecting the relevant guide, the administrator should access the guide’s settings or permissions section. Here, they will find options to manage user access and assign roles. The crucial step is to add the identified shared account to the list of users with access to the guide. Depending on the desired level of access for the shared account, the administrator can assign roles such as “Operator” (for viewing and using the guide) or “Author” (for editing and modifying the guide, if applicable). After granting the appropriate access and saving the changes, the guide should become visible and accessible to users logging in with the shared account on the HoloLens device. It is advisable to test the resolution by logging into the shared HoloLens account and verifying that the guide is now correctly displayed in the Dynamics 365 Guides application.

Detailed Steps for Granting Access¶

To ensure clarity and facilitate the resolution process, here are more detailed steps for granting access to a shared account in Dynamics 365 Guides:

1. Identify the Shared Account: Determine the exact username or account name used for the shared HoloLens device. This is crucial to ensure you are granting access to the correct account.

2. Access Dynamics 365 Guides Authoring: Log in to the Dynamics 365 Guides authoring environment using an account with administrative or guide authoring privileges. This is typically done through a web browser on a computer.

3. Locate the Guide: Navigate through the guide list to find the specific guide that is not appearing on the shared HoloLens device. You can use search or filtering options to quickly locate the guide.

4. Access Guide Permissions: Open the selected guide and look for a section related to permissions, access control, or sharing. The exact terminology may vary slightly depending on the Dynamics 365 Guides version. This might be located in the guide settings, properties, or under a “Share” or “Permissions” tab.

5. Add Shared Account: Within the permissions section, you should find an option to add users or groups. Select this option and search for the shared account username you identified in step 1. Add the shared account to the list of users with access to the guide.

6. Assign Role: For the shared account, assign the appropriate role. For most shared device scenarios where users need to follow instructions, the “Operator” role is sufficient. This role allows users to view and use the guide to perform tasks. If the shared account needs to be able to modify the guide content, the “Author” role would be necessary, but this is less common for shared device scenarios focused on guide consumption.

7. Save Changes: After adding the shared account and assigning the role, ensure you save the changes to the guide permissions. This step is critical for the access changes to take effect.

8. Verify Access on HoloLens: Go to the shared HoloLens device and log in using the shared account. Open the Dynamics 365 Guides application and navigate to the guide list. Verify that the guide you granted access to is now visible and accessible.

9. Troubleshooting Access Issues: If the guide is still not visible after following these steps, double-check the following:

   • Account Name Accuracy: Ensure you added the correct shared account username to the guide permissions. Typos or incorrect account names will prevent access.
   • Synchronization Delay: In some cases, there might be a slight delay for permission changes to synchronize across the system. Wait a few minutes and try again.
   • Network Connectivity: Verify that the HoloLens device has a stable network connection. Network issues can sometimes interfere with access to Dynamics 365 Guides content.
   • Dynamics 365 Guides License: Ensure that the shared account has the necessary Dynamics 365 Guides licenses assigned to it. Licensing is a prerequisite for accessing and using Dynamics 365 Guides.

Best Practices for Shared HoloLens Device Management and Guide Access¶

To proactively prevent guide access issues on shared HoloLens devices and streamline user experience, consider implementing these best practices:

• Centralized Account Management: Utilize a centralized identity management system (like Azure Active Directory) to manage user accounts, including shared accounts for HoloLens devices. This simplifies account creation, permission management, and security.

• Group-Based Access Control: Instead of assigning guide access to individual shared accounts, consider creating user groups based on roles or departments. Assign guides to these groups, and then add shared accounts to the relevant groups. This approach simplifies access management, especially as the number of guides and shared devices grows. For example, create a “Manufacturing Technicians” group and grant access to guides relevant to manufacturing tasks. Then, add shared HoloLens accounts used by manufacturing technicians to this group.

• Regular Access Reviews: Periodically review the access permissions assigned to shared accounts and user groups. Ensure that access is still appropriate and remove access that is no longer needed. This helps maintain security and prevents unauthorized access to guides.

• Clear Naming Conventions: Use clear and consistent naming conventions for shared accounts and guides. This makes it easier to identify the correct accounts and guides when granting access. For example, use names like “SharedHoloLens-ProductionLine1” or “Guide-MachineAssembly-ModelXYZ”.

• User Training: Provide basic training to users on how to log in to shared HoloLens devices and access Dynamics 365 Guides. Include instructions on what to do if they encounter issues finding a guide, such as contacting an administrator.

• Dedicated Support Channel: Establish a clear channel for users to report issues with shared HoloLens devices or guide access. This could be a dedicated help desk email or a designated support person. Promptly address reported issues to minimize disruptions.

• Device and Account Inventory: Maintain an inventory of all shared HoloLens devices and the shared accounts associated with them. This inventory is valuable for tracking devices, managing accounts, and troubleshooting issues.

• Proactive Permissioning: When creating new guides, proactively consider which shared accounts or user groups will need access. Grant access during the guide creation process to avoid access issues when the guide is deployed to shared devices.

By implementing these best practices, organizations can significantly reduce the likelihood of guide access problems on shared HoloLens devices, ensuring a smoother and more efficient user experience with Dynamics 365 Guides. This will lead to better utilization of HoloLens devices and improved task execution in operational environments.

Do you have any other questions or experiences related to troubleshooting shared HoloLens devices and Dynamics 365 Guides? Share your thoughts and comments below!