diff --git a/hololens/app-deploy-intune.md b/hololens/app-deploy-intune.md index c8ccf715..13da568e 100644 --- a/hololens/app-deploy-intune.md +++ b/hololens/app-deploy-intune.md @@ -18,7 +18,7 @@ appliesto: # Intune & Company Portal -With Mobile Device Management (MDM), you can use your own custom apps through [Microsoft Endpoint Manager (Intune)](/intune/windows-holographic-for-business) to deploy it directly to your HoloLens devices. Microsoft Intune is a cloud-based service that focuses on mobile device management (MDM) and mobile application management (MAM). Intune is included in Microsoft's [Enterprise Mobility + Security (EMS) suite](https://www.microsoft.com/microsoft-365/enterprise-mobility-security), and enables users to be productive while keeping your organization data protected. To learn more about Intune, read [What is Intune](/mem/intune/fundamentals/what-is-intune). +With Mobile Device Management (MDM), you can use your own custom apps through [Microsoft Endpoint Manager (Intune)](/mem/intune/fundamentals/windows-holographic-for-business) to deploy it directly to your HoloLens devices. Microsoft Intune is a cloud-based service that focuses on mobile device management (MDM) and mobile application management (MAM). Intune is included in Microsoft's [Enterprise Mobility + Security (EMS) suite](https://www.microsoft.com/microsoft-365/enterprise-mobility-security), and enables users to be productive while keeping your organization data protected. To learn more about Intune, read [What is Intune](/mem/intune/fundamentals/what-is-intune). ## Setup diff --git a/hololens/hololens-certificates-network.md b/hololens/hololens-certificates-network.md index 4dd3a007..1d43f58e 100644 --- a/hololens/hololens-certificates-network.md +++ b/hololens/hololens-certificates-network.md @@ -36,7 +36,7 @@ To support the use of SCEP or PKCS certificates for authentication, Intune requi > [!NOTE] > When you use SCEP with a Microsoft CA, you must also configure the [Network Device Enrollment Service (NDES)](/mem/intune/protect/certificates-scep-configure#set-up-ndes) -For more information, see [Configure a certificate profile for your devices in Microsoft Intune.](/intune/certificates-configure) +For more information, see [Configure a certificate profile for your devices in Microsoft Intune.](/mem/intune/protect/certificates-configure) ## Deploy certificates and Wi-Fi/VPN profile @@ -45,14 +45,14 @@ For more information, see [Configure a certificate profile for your devices in M To deploy certificates and profiles, follow these steps: -1. Create a profile for each of the Root and Intermediate certificates (see [Create trusted certificate profiles](/intune/protect/certificates-configure#create-trusted-certificate-profiles).) Each of these profiles must have a description that includes an expiration date in DD/MM/YYYY format. **Certificate profiles without an expiration date will not be deployed.** +1. Create a profile for each of the Root and Intermediate certificates (see [Create trusted certificate profiles](/mem/intune/protect/certificates-configure#create-trusted-certificate-profiles).) Each of these profiles must have a description that includes an expiration date in DD/MM/YYYY format. **Certificate profiles without an expiration date will not be deployed.** -2. Create a profile for each SCEP or PKCS certificates (see [Create a SCEP certificate profile or Create a PKCS certificate profile](/intune/protect/certficates-pfx-configure#create-a-pkcs-certificate-profile)) Each of these profiles must have a description that includes an expiration date in DD/MM/YYYY format. **Certificate profiles without an expiration date will not be deployed.** +2. Create a profile for each SCEP or PKCS certificates (see [Create a SCEP certificate profile or Create a PKCS certificate profile](/mem/intune/protect/certficates-pfx-configure#create-a-pkcs-certificate-profile)) Each of these profiles must have a description that includes an expiration date in DD/MM/YYYY format. **Certificate profiles without an expiration date will not be deployed.** > [!NOTE] > As the HoloLens 2 is considered for many to be a shared device, multiple users per device, it is recommended to deploy Device certificates instead of User certificates for Wi-Fi authentication where possible -3. Create a profile for each corporate Wi-Fi network (see [Wi-Fi settings for Windows 10 and later devices](/intune/wi-fi-settings-windows)). +3. Create a profile for each corporate Wi-Fi network (see [Wi-Fi settings for Windows 10 and later devices](/mem/intune/configuration/wi-fi-settings-windows)). > [!NOTE] > It is recommended that the Wi-Fi profile be [assigned](/mem/intune/configuration/device-profile-assign) to Device groups rather than User groups where possible. @@ -60,7 +60,7 @@ To deploy certificates and profiles, follow these steps: > [!TIP] > You also can export a working Wi-Fi profile from a Windows 10 PC on your corporate network. This export creates an XML file with all the current settings. Then, import this file into Intune, and use it as the Wi-Fi profile for your HoloLens 2 devices. See [Export and import Wi-Fi settings for Windows devices.](/mem/intune/configuration/wi-fi-settings-import-windows-8-1) -4. Create a profile for each corporate VPN (see [Windows 10 and Windows Holographic device settings to add VPN connections using Intune](/intune/vpn-settings-windows-10)). +4. Create a profile for each corporate VPN (see [Windows 10 and Windows Holographic device settings to add VPN connections using Intune](/mem/intune/configuration/vpn-settings-windows-10)). ## Troubleshooting diff --git a/hololens/hololens-commercial-infrastructure.md b/hololens/hololens-commercial-infrastructure.md index 14606782..e19a9780 100644 --- a/hololens/hololens-commercial-infrastructure.md +++ b/hololens/hololens-commercial-infrastructure.md @@ -112,15 +112,15 @@ Ongoing device management will depend on your mobile device management infrastru 1. [CSPs (Configuration Service Providers)](/windows/client-management/mdm/configuration-service-provider-reference#csps-supported-in-hololens-devices) lets you create and deploy management settings for the devices on your network. See the [list of HoloLens CSPs](/windows/client-management/mdm/configuration-service-provider-reference#csps-supported-in-hololens-devices) for reference. -1. [Compliance policies](/intune/device-compliance-get-started) are rules and settings that devices must meet to be compliant in your corporate infrastructure. Use these policies with Conditional Access to block access to company resources for devices that are non-compliant. For example, you can create a policy that requires BitLocker be enabled. +1. [Compliance policies](/mem/intune/protect/device-compliance-get-started) are rules and settings that devices must meet to be compliant in your corporate infrastructure. Use these policies with Conditional Access to block access to company resources for devices that are non-compliant. For example, you can create a policy that requires BitLocker be enabled. -1. [Create Compliance Policy](/intune/protect/compliance-policy-create-windows). +1. [Create Compliance Policy](/mem/intune/protect/compliance-policy-create-windows). 1. Conditional Access allows/denies mobile devices and mobile applications from accessing company resources. Two documents you may find helpful are [Plan your CA Deployment](/azure/active-directory/conditional-access/plan-conditional-access) and [Best Practices](/azure/active-directory/conditional-access/best-practices). -1. [This article](/intune/fundamentals/windows-holographic-for-business) talks about Intune's management tools for HoloLens. +1. [This article](/mem/intune/fundamentals/windows-holographic-for-business) talks about Intune's management tools for HoloLens. -1. [Create a device profile](/intune/configuration/device-profile-create) +1. [Create a device profile](/mem/intune/configuration/device-profile-create) ### Manage updates @@ -128,7 +128,7 @@ Intune includes a feature called Update rings for Windows 10 devices, including For example, you can create a maintenance window to install updates, or choose to restart after updates are installed. You can also choose to pause updates indefinitely until you're ready to update. -Read more about [configuring update rings with Intune](/intune/windows-update-for-business-configure). +Read more about [configuring update rings with Intune](/mem/intune/protect/windows-update-for-business-configure). ### Application management @@ -142,7 +142,7 @@ Manage HoloLens applications through: Microsoft Store for Business and Education is a custom store for your corporate environment. It lets you use the Microsoft Store built into Windows 10 and HoloLens to find, acquire, distribute, and manage apps for your organization. It also lets you deploy apps that are specific to your commercial environment but not to the world. 1. Application deployment and management via Intune or another mobile device management solution - Most mobile device management solutions, including Intune, provide a way to deploy line of business applications directly to a set of enrolled devices. See this article for [Intune app install](/intune/apps-deploy). + Most mobile device management solutions, including Intune, provide a way to deploy line of business applications directly to a set of enrolled devices. See this article for [Intune app install](/mem/intune/apps/apps-deploy). 1. *not recommended* Device Portal Applications can also be installed on HoloLens directly using the Windows Device Portal. This isn't recommended since Developer Mode has to be enabled to use the device portal. @@ -151,29 +151,29 @@ Read more about [installing apps on HoloLens](hololens-install-apps.md). ### Certificates -You can distribute certificates through your MDM provider. If your company requires certificates, Intune supports PKCS, PFX, and SCEP. It's important to understand which certificate is right for your company. Please visit the [certificate configurations](/intune/protect/certificates-configure) documentation to determine which cert is best for you. If you plan to use certificates for HoloLens Authentication, PFX, or SCEP may be right for you. +You can distribute certificates through your MDM provider. If your company requires certificates, Intune supports PKCS, PFX, and SCEP. It's important to understand which certificate is right for your company. Please visit the [certificate configurations](/mem/intune/protect/certificates-configure) documentation to determine which cert is best for you. If you plan to use certificates for HoloLens Authentication, PFX, or SCEP may be right for you. -See the following steps for using [SCEP](/intune/protect/certificates-profile-scep). +See the following steps for using [SCEP](/mem/intune/protect/certificates-profile-scep). ### How to Upgrade to Holographic for Business Commercial Suite > [!NOTE] > Windows Holographic for Business (commercial suite) is only intended for HoloLens (1st gen) devices. The profile will not be applied to HoloLens 2 devices. -You can find directions for upgrading to the commercial suite in the [holographic upgrade](/intune/configuration/holographic-upgrade) documentation. +You can find directions for upgrading to the commercial suite in the [holographic upgrade](/mem/intune/configuration/holographic-upgrade) documentation. ### How to Configure Kiosk Mode Using Microsoft Intune -1. Sync Microsoft Store to Intune (See the following [instructions](/intune/apps/windows-store-for-business)). +1. Sync Microsoft Store to Intune (See the following [instructions](/mem/intune/apps/windows-store-for-business)). 1. Check your app settings 1. Log in to your Microsoft Store Business account 1. **Manage > Products and Services > Apps and Software > Select the app you want to sync > Private Store Availability > Select "Everyone" or "Specific Groups"** >[!NOTE] >If you don't see the app you want, you will have to "get" the app by searching the store for your app. **Click the "Search" bar in the upper right-hand corner > type in the name of the app > click on the app > select "Get"**. - 1. If you don't see your apps in **Intune > Client Apps > Apps** , you may have to [sync your apps](/intune/apps/windows-store-for-business#synchronize-apps) again. + 1. If you don't see your apps in **Intune > Client Apps > Apps** , you may have to [sync your apps](/mem/intune/apps/windows-store-for-business#synchronize-apps) again. -1. [Create a device profile for Kiosk mode](/intune/configuration/kiosk-settings#create-the-profile) +1. [Create a device profile for Kiosk mode](/mem/intune/configuration/kiosk-settings#create-the-profile) > [!NOTE] > You can configure different users to have different Kiosk Mode experiences by using "Microsoft Entra ID" as the "User logon type". However, this option is only available in Multi-App kiosk mode. Multi-App kiosk mode will work with only one app as well as multiple apps. @@ -188,4 +188,4 @@ Certificates can be deployed via you MDM (see "certificates" in the [MDM Section ### Additional Intune Quick Links -1. [Create Profiles:](/intune/configuration/device-profile-create) Profiles allow you to add and configure settings that will be pushed to the devices in your organization. +1. [Create Profiles:](/mem/intune/configuration/device-profile-create) Profiles allow you to add and configure settings that will be pushed to the devices in your organization. diff --git a/hololens/hololens-enroll-mdm.md b/hololens/hololens-enroll-mdm.md index 773fd002..31f1b30a 100644 --- a/hololens/hololens-enroll-mdm.md +++ b/hololens/hololens-enroll-mdm.md @@ -15,20 +15,20 @@ appliesto: # Enroll HoloLens in MDM -You can manage multiple Microsoft HoloLens devices simultaneously using solutions like [Microsoft Intune](/intune/windows-holographic-for-business). You'll be able to manage settings, select apps to install and set security configurations tailored to your organization's need. See [Manage devices running Windows Holographic with Microsoft Intune](/intune/windows-holographic-for-business), the [configuration service providers (CSPs) that are supported in Windows Holographic](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/configuration-service-provider-reference#hololens), and the [policies supported by Windows Holographic for Business](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#hololenspolicies). +You can manage multiple Microsoft HoloLens devices simultaneously using solutions like [Microsoft Intune](/mem/intune/fundamentals/windows-holographic-for-business). You'll be able to manage settings, select apps to install, and set security configurations tailored to your organization's need. See [Manage devices running Windows Holographic with Microsoft Intune](/mem/intune/fundamentals/windows-holographic-for-business), the [configuration service providers (CSPs) that are supported in Windows Holographic](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/configuration-service-provider-reference#hololens), and the [policies supported by Windows Holographic for Business](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#hololenspolicies). > [!NOTE] > Mobile device management (MDM), including the VPN, Bitlocker, and kiosk mode features, is only available when you [upgrade to Windows Holographic for Business](hololens1-upgrade-enterprise.md). ## Requirements - Your organization will need to have Mobile Device Management (MDM) set up in order to manage HoloLens devices. Your MDM provider can be Microsoft Intune or a 3rd party provider that uses Microsoft MDM APIs. + Your organization will need to have Mobile Device Management (MDM) set up in order to manage HoloLens devices. Your MDM provider can be Microsoft Intune or a third party provider that uses Microsoft MDM APIs. ## Enrollment per scenario Depending on what stage you are in your deployment we have the following recommendations: -- For multi-user shared devices being deployed in production it is suggested you use [Autopilot](hololens2-autopilot.md). +- For multi-user shared devices being deployed in production it's suggested you use [Autopilot](hololens2-autopilot.md). - For multi-user shared devices that are being initially part of a pilot program, [Microsoft Entra join during OOBE](hololens-enroll-mdm.md#auto-enrollment-in-mdm) should be sufficient. - For a proof of concept joining a device via the Settings menu may suit your needs if you don't need multiple users per device. diff --git a/hololens/hololens-gloves.md b/hololens/hololens-gloves.md index a8763ec6..581f1dd7 100644 --- a/hololens/hololens-gloves.md +++ b/hololens/hololens-gloves.md @@ -2,7 +2,7 @@ title: Using HoloLens 2 With Gloves description: Guidance on which types of gloves work best with hand tracking on HoloLens 2. ms.date: 5/13/2024 -ms.localizationpriority: +ms.localizationpriority: Low ms.service: hololens ms.topic: article audience: HoloLens diff --git a/hololens/hololens-identity.md b/hololens/hololens-identity.md index cfd4494b..2410101c 100644 --- a/hololens/hololens-identity.md +++ b/hololens/hololens-identity.md @@ -171,7 +171,7 @@ One way in which developing for HoloLens differs from developing for Desktop is Windows Hello for Business (which supports using a PIN to sign in) is supported for HoloLens (1st Gen). To allow Windows Hello for Business PIN sign-in on HoloLens (1st gen): 1. The HoloLens device must be [managed by MDM](hololens-enroll-mdm.md). -1. You must enable Windows Hello for Business for the device. ([See instructions for Microsoft Intune.](/intune/windows-hello)) +1. You must enable Windows Hello for Business for the device. ([See instructions for Microsoft Intune.](/mem/intune/protect/windows-hello)) 1. On the HoloLens device, the user can then use **Settings** > **Sign-in Options** > **Add PIN** to set up a PIN. > [!NOTE] diff --git a/hololens/hololens-offline.md b/hololens/hololens-offline.md index 7a6ec7dd..7e7bf3d7 100644 --- a/hololens/hololens-offline.md +++ b/hololens/hololens-offline.md @@ -159,8 +159,8 @@ In addition to the list above, to take full advantage of HoloLens functionality, - [Manage connection endpoints for Windows 10 Enterprise, version 1903](/windows/privacy/manage-windows-1903-endpoints) - [Manage connections from Windows 10 operating system components to Microsoft services](/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services) - [Manage connections from Windows 10 operating system components to Microsoft services using Microsoft Intune MDM Server](/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-mdm) -- [Intune network configuration requirements and bandwidth](/intune/fundamentals/network-bandwidth-use#network-communication-requirements) -- [Network endpoints for Microsoft Intune](/intune/fundamentals/intune-endpoints) +- [Intune network configuration requirements and bandwidth](/mem/intune/fundamentals/network-bandwidth-use#network-communication-requirements) +- [Network endpoints for Microsoft Intune](/mem/intune/fundamentals/intune-endpoints) - [Office 365 URLs and IP address ranges](/office365/enterprise/urls-and-ip-address-ranges) - [Prerequisites for Microsoft Entra Connect](/azure/active-directory/hybrid/how-to-connect-install-prerequisites) diff --git a/hololens/hololens-updates.md b/hololens/hololens-updates.md index 1c1781cc..5a924701 100644 --- a/hololens/hololens-updates.md +++ b/hololens/hololens-updates.md @@ -82,7 +82,7 @@ You can configure Windows Update for Business settings for HoloLens by using pol ### Managing Windows Update for Business by using Microsoft Intune -For a detailed discussion about how to use Intune to configure Windows Update for Business, see [Manage Windows 10 software updates in Intune](/intune/protect/windows-update-for-business-configure). For more information about the specific Intune functionality that HoloLens supports, see [Intune update management functions that HoloLens supports](#intune-update-management-functions-that-hololens-supports). +For a detailed discussion about how to use Intune to configure Windows Update for Business, see [Manage Windows 10 software updates in Intune](/mem/intune/protect/windows-update-for-business-configure). For more information about the specific Intune functionality that HoloLens supports, see [Intune update management functions that HoloLens supports](#intune-update-management-functions-that-hololens-supports). > [!IMPORTANT] > Intune provides two policy types for managing updates: *Windows 10 update ring* and *Windows 10 feature update*. The Windows 10 feature update policy type is in public preview at this time and is not supported for HoloLens. @@ -103,7 +103,7 @@ This section describes the policies that you can use to manage updates for eithe You can use the **Update/AllowAutoUpdate** policy to manage automatic update behavior, such as scanning, downloading, and installing updates. For more information about the available settings for this policy, see [Update/AllowAutoUpdate](/windows/client-management/mdm/policy-csp-update#update-allowautoupdate). > [!NOTE] -> In Microsoft Intune, you can use **Automatic Update Behavior** to change this policy. For more information, see [Manage Windows 10 software updates in Intune](/intune/windows-update-for-business-configure). +> In Microsoft Intune, you can use **Automatic Update Behavior** to change this policy. For more information, see [Manage Windows 10 software updates in Intune](/mem/intune/protect/windows-update-for-business-configure). #### Configure an update schedule diff --git a/hololens/hololens1-encryption.md b/hololens/hololens1-encryption.md index dff131ac..1aa7071d 100644 --- a/hololens/hololens1-encryption.md +++ b/hololens/hololens1-encryption.md @@ -24,7 +24,7 @@ On HoloLens (1st gen) you can enable BitLocker device encryption manually or usi You can use your Mobile Device Management (MDM) provider to apply a policy that requires device encryption. The policy to use is the [Security/RequireDeviceEncryption setting](/windows/client-management/mdm/policy-csp-security#security-requiredeviceencryption) in the Policy CSP. -[See instructions for enabling device encryption using Microsoft Intune.](/intune/compliance-policy-create-windows#windows-holographic-for-business) +[See instructions for enabling device encryption using Microsoft Intune.](/mem/intune/protect/compliance-policy-create-windows#windows-holographic-for-business) For other MDM tools, see your MDM provider's documentation for instructions. If your MDM provider requires custom URI for device encryption, use the following configuration: @@ -76,13 +76,13 @@ Provisioning packages are files created by the Windows Configuration Designer to ### Apply the provisioning package to HoloLens -1. Connect the device via USB to a PC and start the device, but do not continue past the **fit** page of the initial setup experience (the first page with the blue box). +1. Connect the device via USB to a PC and start the device, but don't continue past the **fit** page of the initial setup experience (the first page with the blue box). 1. Briefly press and release the **Volume Down** and **Power** buttons simultaneously. 1. HoloLens will show up as a device in File Explorer on the PC. 1. In File Explorer, drag and drop the provisioning package (.ppkg) onto the device storage. 1. Briefly press and release the **Volume Down** and **Power** buttons simultaneously again while on the **fit** page. 1. The device will ask you if you trust the package and would like to apply it. Confirm that you trust the package. -1. You will see whether the package was applied successfully or not. If it failed, you can fix your package and try again. If it succeeded, proceed with device setup. +1. You'll see whether the package was applied successfully or not. If it failed, you can fix your package and try again. If it succeeded, proceed with device setup. > [!NOTE] > If the device was purchased before August 2016, you will need to sign into the device with a Microsoft account, get the latest OS update, and then reset the OS in order to apply the provisioning package. diff --git a/hololens/hololens1-upgrade-enterprise.md b/hololens/hololens1-upgrade-enterprise.md index 49d13d66..771274bb 100644 --- a/hololens/hololens1-upgrade-enterprise.md +++ b/hololens/hololens1-upgrade-enterprise.md @@ -27,7 +27,7 @@ When you purchase the Commercial Suite, you receive a license that upgrades Wind The enterprise license can be applied by any MDM provider that supports the [WindowsLicensing configuration service provider (CSP)](https://msdn.microsoft.com/library/windows/hardware/dn904983.aspx). The latest version of the Microsoft MDM API will support WindowsLicensing CSP. -For step-by-step instructions for upgrading HoloLens by using Microsoft Intune, see [Upgrade devices running Windows Holographic to Windows Holographic for Business](/intune/holographic-upgrade). +For step-by-step instructions for upgrading HoloLens by using Microsoft Intune, see [Upgrade devices running Windows Holographic to Windows Holographic for Business](/mem/intune/configuration/holographic-upgrade). On other MDM providers, the specific steps for setting up and deploying the policy might vary. diff --git a/hololens/hololens2-corp-connected-configure.md b/hololens/hololens2-corp-connected-configure.md index 46f7ba67..0fe151dc 100644 --- a/hololens/hololens2-corp-connected-configure.md +++ b/hololens/hololens2-corp-connected-configure.md @@ -44,12 +44,12 @@ Corporate Wi-Fi connections will commonly require certificate-based authenticati To deploy certificates and profiles through Microsoft Endpoint Manager, follow these steps: -1. Create a profile for each of the Root and Intermediate certificates (see [Create trusted certificate profiles](/intune/protect/certificates-configure#create-trusted-certificate-profiles)). Each of these profiles must have a description that includes an expiration date in DD/MM/YYYY format. +1. Create a profile for each of the Root and Intermediate certificates (see [Create trusted certificate profiles](/mem/intune/protect/certificates-configure#create-trusted-certificate-profiles)). Each of these profiles must have a description that includes an expiration date in DD/MM/YYYY format. > [!CAUTION] > **Certificate profiles without an expiration date will not be deployed**. -2. Create a profile for each SCEP or PKCS certificates (see [Create a SCEP certificate profile or Create a PKCS certificate profile](/intune/protect/certficates-pfx-configure#create-a-pkcs-certificate-profile)) Each of these profiles must have a description that includes an expiration date in DD/MM/YYYY format. +2. Create a profile for each SCEP or PKCS certificates (see [Create a SCEP certificate profile or Create a PKCS certificate profile](/mem/intune/protect/certficates-pfx-configure#create-a-pkcs-certificate-profile)) Each of these profiles must have a description that includes an expiration date in DD/MM/YYYY format. > [!CAUTION] > **Certificate profiles without an expiration date will not be deployed.** @@ -57,7 +57,7 @@ To deploy certificates and profiles through Microsoft Endpoint Manager, follow t > [!Note] > As the HoloLens 2 is considered for many to be a shared device, i.e., multiple users per device, it is recommended to deploy Device certificates instead of User certificates for Wi-Fi authentication where possible. -3. Create a profile for your corporate Wi-Fi network (see [Wi-Fi settings for Windows 10 and later devices](/intune/wi-fi-settings-windows)). Within your Wi-Fi profile, you can select to use the proxy settings within your organization. +3. Create a profile for your corporate Wi-Fi network (see [Wi-Fi settings for Windows 10 and later devices](/mem/intune/configuration/wi-fi-settings-windows)). Within your Wi-Fi profile, you can select to use the proxy settings within your organization. Your options: - **None**: No proxy settings are configured. diff --git a/hololens/hololens2-enterprise-troubleshooting.md b/hololens/hololens2-enterprise-troubleshooting.md index 05078fc3..959f4494 100644 --- a/hololens/hololens2-enterprise-troubleshooting.md +++ b/hololens/hololens2-enterprise-troubleshooting.md @@ -139,7 +139,7 @@ Check out the original [blog](https://techcommunity.microsoft.com/t5/windows-it- ## Can't sign in to a previously set up HoloLens device -If your device was previously set up for someone else, either for a client or for a former employee, and you don't have their password to unlock the device, you can use Intune to remotely [wipe](/intune/remote-actions/devices-wipe) the device. The device then re-flashes itself. +If your device was previously set up for someone else, either for a client or for a former employee, and you don't have their password to unlock the device, you can use Intune to remotely [wipe](/mem/intune/remote-actions/devices-wipe) the device. The device then re-flashes itself. > [!IMPORTANT] > When you wipe the device, make sure to leave **Retain enrollment state and user account** unchecked. diff --git a/hololens/security-state-separation-isolation.md b/hololens/security-state-separation-isolation.md index 49c8a941..67f4e1bd 100644 --- a/hololens/security-state-separation-isolation.md +++ b/hololens/security-state-separation-isolation.md @@ -71,7 +71,7 @@ To achieve this balance, HoloLens 2 has a core operating system that is used for ## Code signing -Digitally signing code allows substantiation that executables and scripts haven't been modified since they were signed by a trusted source therefore providing authenticity and integrity. The authorities that HoloLens 2 trusts by default are Microsoft and Microsoft Store. IT administrators can add new certificates to the device through the [ClientCertificateInstall](/windows/client-management/mdm/clientcertificateinstall-csp) and [RootCATrustedCertificates](/windows/client-management/mdm/rootcacertificates-csp) CSPs. They can also use the [AllowAllTrustedApps policy](/windows/client-management/mdm/policy-csp-applicationmanagement#applicationmanagement-allowalltrustedapps) to trust other sideloaded or [Line-of-business apps](/intune/apps/lob-apps-windows). Certificates reside in the local machine certificate store that is stored in HKLM/Root if using “Device” or in HKCU if using “User”. +Digitally signing code allows substantiation that executables and scripts haven't been modified since they were signed by a trusted source therefore providing authenticity and integrity. The authorities that HoloLens 2 trusts by default are Microsoft and Microsoft Store. IT administrators can add new certificates to the device through the [ClientCertificateInstall](/windows/client-management/mdm/clientcertificateinstall-csp) and [RootCATrustedCertificates](/windows/client-management/mdm/rootcacertificates-csp) CSPs. They can also use the [AllowAllTrustedApps policy](/windows/client-management/mdm/policy-csp-applicationmanagement#applicationmanagement-allowalltrustedapps) to trust other sideloaded or [Line-of-business apps](/mem/intune/apps/lob-apps-windows). Certificates reside in the local machine certificate store that is stored in HKLM/Root if using “Device” or in HKCU if using “User”. ## Defender protections HoloLens 2 uses Microsoft services to give users an advanced level of security: