mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 05:17:22 +00:00
resolved suggestions and Acrolinx issues
This commit is contained in:
Siddarth Mandalika
parent
7c51a3cacd
commit
8d336e6f54
@ -39,11 +39,11 @@ Here's a step-by-step guide to adding an Azure Active Directory tenant, adding a
|
||||
|
||||
If you don't have a paid subscription to any Microsoft service, you can purchase an Azure AD premium subscription. Go to the Office 356 portal at https://portal.office.com/, and then sign in using the admin account that you created in Step 4 (for example, user1@contosoltd.onmicrosoftcom).
|
||||
|
||||
|
||||
|
||||
|
||||
6. Select **Install software**.
|
||||
|
||||
|
||||
|
||||
|
||||
7. In the Microsoft 365 admin center, select **Purchase Services** from the left navigation.
|
||||
|
||||
@ -69,27 +69,27 @@ If you have paid subscriptions to Office 365, Microsoft Dynamics CRM Online, Ent
|
||||
|
||||
1. Sign in to the Microsoft 365 admin center at <https://portal.office.com> using your organization's account.
|
||||
|
||||
|
||||
|
||||
|
||||
2. On the **Home** page, select on the Admin tools icon.
|
||||
|
||||
|
||||
|
||||
|
||||
3. On the **Admin center** page, hover your mouse over the Admin tools icon on the left and then click **Azure AD**. This will take you to the Azure Active Directory sign-up page and brings up your existing Office 365 organization account information.
|
||||
|
||||
|
||||
|
||||
|
||||
4. On the **Sign up** page, make sure to enter a valid phone number and then click **Sign up**.
|
||||
|
||||
|
||||
|
||||
|
||||
5. It may take a few minutes to process the request.
|
||||
|
||||
|
||||
|
||||
|
||||
6. You will see a welcome page when the process completes.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -78,19 +78,19 @@ The following table shows the Microsoft custom elements that this configuration
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td><p>parm-query</p></td>
|
||||
<td><p>Parm-query</p></td>
|
||||
<td><p>Yes</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td><p>noparm</p></td>
|
||||
<td><p>No parm</p></td>
|
||||
<td><p>Yes</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td><p>nocharacteristic</p></td>
|
||||
<td><p>No characteristic</p></td>
|
||||
<td><p>Yes</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td><p>characteristic-query</p></td>
|
||||
<td><p>Characteristic-query</p></td>
|
||||
<td><p>Yes</p>
|
||||
<p>Recursive query: Yes</p>
|
||||
<p>Top-level query: Yes</p></td>
|
||||
|
||||
@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Data structures for Microsoft Store for Business
|
||||
description: Learn about the various data structures for Microsoft Store for Business.
|
||||
MS-HAID:
|
||||
- 'p\_phdevicemgmt.business\_store\_data\_structures'
|
||||
- 'p\_phDeviceMgmt.data\_structures\_windows\_store\_for\_business'
|
||||
|
||||
@ -246,7 +246,10 @@ la--- 1/4/2021 2:45 PM 1
|
||||
la--- 1/4/2021 2:45 PM 2
|
||||
la--- 12/2/2020 6:27 PM 2701 results.xml
|
||||
```
|
||||
Each data gathering directive from the original `Collection` XML corresponds to a folder in the output. For example, if the first directive was <RegistryKey HRESULT="0">HKLM\Software\Policies</RegistryKey> then folder `1` will contain the corresponding `export.reg` file.
|
||||
Each data gathering directive from the original `Collection` XML corresponds to a folder in the output.
|
||||
For example, the first directive was:
|
||||
<RegistryKey HRESULT="0">HKLM\Software\Policies</RegistryKey>
|
||||
then folder `1` will contain the corresponding `export.reg` file.
|
||||
|
||||
The `results.xml` file is the authoritative map to the output. It includes a status code for each directive. The order of the directives in the file corresponds to the order of the output folders. Using `results.xml` the administrator can see what data was gathered, what failures may have occurred, and which folders contain which output. For example, the following `results.xml` content indicates that registry export of HKLM\Software\Policies was successful and the data can be found in folder `1`. It also indicates that `netsh.exe wlan show profiles` command failed.
|
||||
|
||||
|
||||
@ -107,15 +107,15 @@ Trigger the device to check for updates either manually or using Microsoft Endpo
|
||||
|
||||
1. Remotely trigger a scan of the test device by deploying a Trigger Scan configuration baseline.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Set the value of this OMA-URI by going to **Configuration Item**, and then selecting the newly created Trigger Scan settings from the previous step.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Ensure that the value that is specified for this URI is greater than the value on the device(s), and that the **Remediate noncompliant rules when supported** option is selected. For the first time, any value that is greater than 0 will work, but for subsequent configurations, ensure that you specify an incremented value.
|
||||
|
||||
|
||||
|
||||
|
||||
4. Create a configuration baseline for Trigger Scan and Deploy. We recommend that this configuration baseline be deployed after the Controlled Updates baseline has been applied to the device. (The corresponding files are deployed on the device through a device sync session.)
|
||||
5. Follow the prompts for downloading the updates, but do not install the updates on the device.
|
||||
@ -216,11 +216,11 @@ The deployment process has three parts:
|
||||
|
||||
1. Create a configuration item. In the **Browse Settings** window, select **Device File** as a filter, and then select **Select**.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Browse to the DUControlledUpdates.xml that was created from the test device, and then specify the file path and name on the device as `NonPersistent\DUControlledUpdates.xml`.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Select **Remediate noncompliant settings**, and then select **OK**.
|
||||
|
||||
@ -231,7 +231,7 @@ The deployment process has three parts:
|
||||
1. Create a configuration item and specify the file path and name on the device as `NonPersistent\DUCustomContentURIs.xml`
|
||||
2. Select **Remediate noncompliant settings**.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Select **OK**.
|
||||
|
||||
@ -242,11 +242,11 @@ The deployment process has three parts:
|
||||
1. Create a configuration baseline item and give it a name (such as ControlledUpdates).
|
||||
2. Add the DUControlledUpdates and DUCustomContentURIs configuration items, and then select **OK**.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Deploy the configuration baseline to the appropriate device or device collection.
|
||||
|
||||
|
||||
|
||||
|
||||
4. Select **OK**.
|
||||
|
||||
@ -472,14 +472,14 @@ Use this procedure for pre-GDR1 devices:
|
||||
2. In Microsoft Endpoint Configuration Manager, under **Assets and Compliance** > **Compliance Settings**, right-click **Configuration Items**.
|
||||
3. Select **Create Configuration Item**.
|
||||
|
||||
|
||||
|
||||
4. Enter a filename (such as GetDUReport), and then select **Mobile Device**.
|
||||
5. On the **Mobile Device Settings** page, select **Configure Additional Settings that are not in the default settings group**, and then select **Next**.
|
||||
|
||||
|
||||
|
||||
6. On the **Additional Settings** page, select **Add**.
|
||||
|
||||
|
||||
|
||||
7. On the **Browse Settings** page, select **Create Setting**.
|
||||
|
||||
|
||||
@ -490,39 +490,39 @@ Use this procedure for pre-GDR1 devices:
|
||||
10. On the **Browse Settings** page, select **Close**.
|
||||
11. On the **Create Configuration Item Wizard** page, select **All Windows Embedded 8.1 Handheld** as the supported platform, and then select **Next**.
|
||||
|
||||
|
||||
|
||||
12. Close the **Create Configuration Item Wizard** page.
|
||||
13. Right-click on the newly create configuration item, and then select the **Compliance Rules** tab.
|
||||
14. Select the new created mobile device setting (such as DUReport), and then select **Select**.
|
||||
15. Enter a dummy value (such as zzz) that is different from the one on the device.
|
||||
|
||||
|
||||
|
||||
16. Disable remediation by deselecting the **Remediate noncompliant rules when supported** option.
|
||||
17. Select **OK** to close the **Edit Rule** page.
|
||||
18. Create a new configuration baseline. Under **Assets and Compliance** > **Compliance Settings**, right-click **Configuration Baselines**.
|
||||
19. Select **Create Configuration Item**.
|
||||
|
||||
|
||||
|
||||
20. Enter a baseline name (such as RetrieveDUReport).
|
||||
21. Add the configuration item that you just created. Select **Add**, and then select the configuration item that you just created (such as DUReport).
|
||||
|
||||
|
||||
|
||||
22. Select **OK**, and then select **OK** again to complete the configuration baseline.
|
||||
23. Deploy the newly created configuration baseline to the appropriate device collection. Right-click on the configuration baseline that you created, and then select **Deploy**.
|
||||
|
||||
|
||||
|
||||
24. Select **Remediate noncompliant rules when supported**.
|
||||
25. Select the appropriate device collection and define the schedule.
|
||||
|
||||
|
||||
|
||||
26. To view the DUReport content, select the appropriate deployment for the configuration baseline that you created. Right-click on the deployment, and then select **View Status**.
|
||||
27. Select **Run Summarization**, and then select **Refresh**. The test device(s) should be listed on the **Non-Compliant** tab.
|
||||
28. Under **Asset Details**, right-click on the test device, and then select **Mode Details**.
|
||||
|
||||
|
||||
|
||||
29. On the **Non-compliant** tab, you can see the DUReport, but you cannot retrieve the content from here.
|
||||
|
||||
|
||||
|
||||
30. To retrieve the DUReport, open C:\\Program Files\\SMS\_CCM\\SMS\_DM.log.
|
||||
31. In the log file, search from the bottom for "./Vendor/MSFT/EnterpriseExt/DeviceUpdate/UpdatesResultXml" RuleExression="Equals zzz," where zzz is the dummy value. Just above this, copy the information for UpdateData and use this information to create the DUControlledUpdates.xml.
|
||||
|
||||
|
||||
@ -40,11 +40,11 @@ Joining your device to an Active Directory domain during the out-of-box-experien
|
||||
|
||||
1. On the **Who Owns this PC?** page, select **My work or school owns it**.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Next, select **Join a domain**.
|
||||
|
||||
|
||||
|
||||
|
||||
3. You'll see a prompt to set up a local account on the device. Enter your local account details, and then select **Next** to continue.
|
||||
|
||||
@ -56,19 +56,19 @@ To create a local account and connect the device:
|
||||
|
||||
1. Launch the Settings app.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Next, select **Accounts**.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Navigate to **Access work or school**.
|
||||
|
||||
|
||||
|
||||
|
||||
4. Select **Connect**.
|
||||
|
||||
|
||||
|
||||
|
||||
5. Under **Alternate actions**, select **Join this device to a local Active Directory domain**.
|
||||
|
||||
@ -101,11 +101,11 @@ To join a domain:
|
||||
|
||||
1. Select **My work or school owns it**, then select **Next.**
|
||||
|
||||
|
||||
|
||||
|
||||
2. Select **Join Azure AD**, and then select **Next.**
|
||||
|
||||
|
||||
|
||||
|
||||
3. Type in your Azure AD username. This is the email address you use to log into Microsoft Office 365 and similar services.
|
||||
|
||||
@ -121,23 +121,23 @@ To create a local account and connect the device:
|
||||
|
||||
1. Launch the Settings app.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Next, navigate to **Accounts**.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Navigate to **Access work or school**.
|
||||
|
||||
|
||||
|
||||
|
||||
4. Select **Connect**.
|
||||
|
||||
|
||||
|
||||
|
||||
5. Under **Alternate Actions**, selct **Join this device to Azure Active Directory**.
|
||||
|
||||
|
||||
|
||||
|
||||
6. Type in your Azure AD username. This is the email address you use to log into Office 365 and similar services.
|
||||
|
||||
@ -151,7 +151,7 @@ To create a local account and connect the device:
|
||||
|
||||
After you reach the end of the flow, your device should be connected to your organization’s Azure AD domain. You may now log out of your current account and sign in using your Azure AD username.
|
||||
|
||||
|
||||
|
||||
|
||||
### Help with connecting to an Azure AD domain
|
||||
|
||||
@ -183,19 +183,19 @@ To create a local account and connect the device:
|
||||
|
||||
1. Launch the Settings app, and then select **Accounts** >**Start** > **Settings** > **Accounts**.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Navigate to **Access work or school**.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Select **Connect**.
|
||||
|
||||
|
||||
|
||||
|
||||
4. Type in your Azure AD username. This is the email address you use to log into Office 365 and similar services.
|
||||
|
||||
|
||||
|
||||
|
||||
5. If the tenant is a cloud-only, password hash sync, or pass-through authentication tenant, this page changes to show the organization's custom branding, and can enter your password directly into the page. If the tenant is part of a federated domain, you are redirected to the organization's on-premises federation server, such as AD FS, for authentication.
|
||||
|
||||
@ -205,7 +205,7 @@ To create a local account and connect the device:
|
||||
|
||||
Starting in Windows 10, version 1709, you will see the status page that shows the progress of your device being set up.
|
||||
|
||||
|
||||
|
||||
|
||||
6. After you complete the flow, your Microsoft account will be connected to your work or school account.
|
||||
|
||||
@ -221,7 +221,7 @@ To create a local account and connect the device:
|
||||
|
||||
1. Launch the Settings app.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Next, navigate to **Accounts**.
|
||||
|
||||
@ -233,17 +233,17 @@ To create a local account and connect the device:
|
||||
|
||||
4. Select the **Enroll only in device management** link (available in servicing build 14393.82, KB3176934). For older builds, see [Connect your Windows 10-based device to work using a deep link](mdm-enrollment-of-windows-devices.md#connect-your-windows-10-based-device-to-work-using-a-deep-link).
|
||||
|
||||
|
||||
|
||||
|
||||
5. Type in your work email address.
|
||||
|
||||
|
||||
|
||||
|
||||
6. If the device finds an endpoint that only supports on-premises authentication, this page will change and ask you for your password. If the device finds an MDM endpoint that supports federated authentication, you’ll be presented with a new window that will ask you for additional authentication information.
|
||||
|
||||
Based on IT policy, you may also be prompted to provide a second factor of authentication at this point. Starting in Windows 10, version 1709, you will see the enrollment progress on screen.
|
||||
|
||||
|
||||
|
||||
|
||||
After you complete the flow, your device will be connected to your organization’s MDM.
|
||||
|
||||
@ -308,13 +308,13 @@ To connect your devices to MDM using deep links:
|
||||
|
||||
Type in your work email address.
|
||||
|
||||
|
||||
|
||||
|
||||
3. If the device finds an endpoint that only supports on-premises authentication, this page will change and ask you for your password. If the device finds an MDM endpoint that supports federated authentication, you’ll be presented with a new window that will ask you for additional authentication information. Based on IT policy, you may also be prompted to provide a second factor of authentication at this point.
|
||||
|
||||
After you complete the flow, your device will be connected to your organization's MDM.
|
||||
|
||||
|
||||
|
||||
|
||||
## Manage connections
|
||||
|
||||
|
||||
@ -23,11 +23,11 @@ If you have paid subscriptions to Office 365, Microsoft Dynamics CRM Online, Ent
|
||||
|
||||
1. Sign in to the Microsoft 365 admin center at <https://portal.office.com> using your organization's account.
|
||||
|
||||
|
||||
|
||||
|
||||
2. On the **Home** page, click on the Admin tools icon.
|
||||
|
||||
|
||||
|
||||
|
||||
3. On the **Admin center** page, under Admin Centers on the left, click **Azure Active Directory**. This will take you to the Azure Active Directory portal.
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user