mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-18 16:27:22 +00:00
Merged PR 6495: 3/20 AM Publish
This commit is contained in:
Alma Jenks
commit
1afc1d3de0
@ -8,7 +8,7 @@ ms.sitesec: library
|
||||
ms.pagetype: store
|
||||
author: TrudyHa
|
||||
ms.localizationpriority: high
|
||||
ms.date: 10/17/2017
|
||||
ms.date: 3/19/2018
|
||||
---
|
||||
|
||||
# Distribute apps using your private store
|
||||
@ -47,6 +47,9 @@ Microsoft Store adds the app to **Apps & software**. Click **Manage**, **Apps &
|
||||
|
||||
The value under **Private store** for the app will change to pending. It will take approximately thirty-six hours before the app is available in the private store.
|
||||
|
||||
>[!Note]
|
||||
> If you are working with a new Line-of-Business (LOB) app, you have to wait for the app to be avilable in **Products & services** before adding it to your private store. For more information, see [Working with line of business apps](working-with-line-of-business-apps.md).
|
||||
|
||||
Employees can claim apps that admins added to the private store by doing the following.
|
||||
|
||||
**To claim an app from the private store**
|
||||
@ -57,6 +60,7 @@ Employees can claim apps that admins added to the private store by doing the fol
|
||||
|
||||
## Related topics
|
||||
- [Manage access to private store](manage-access-to-private-store.md)
|
||||
- [Manage private store settings](manage-private-store-settings.md)
|
||||
- [Configure access to Microsoft Store](/windows/configuration/stop-employees-from-using-microsoft-store)
|
||||
|
||||
|
||||
|
||||
BIN
store-for-business/images/lob-workflow.png
Normal file
BIN
store-for-business/images/lob-workflow.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 33 KiB |
@ -8,7 +8,7 @@ ms.sitesec: library
|
||||
ms.pagetype: store
|
||||
author: TrudyHa
|
||||
ms.localizationpriority: high
|
||||
ms.date: 10/17/2017
|
||||
ms.date: 3/19/2018
|
||||
---
|
||||
|
||||
# Working with line-of-business apps
|
||||
@ -38,8 +38,10 @@ You'll need to set up:
|
||||
- LOB publishers need to have an active developer account. To learn more about account options, see [Ready to sign up](https://go.microsoft.com/fwlink/p/?LinkId=623432).
|
||||
- LOB publishers need to have an app in Microsoft Store, or have an app ready to submit to the Store.
|
||||
|
||||
## <a href="" id="add-lob-publisher"></a>Add an LOB publisher (Admin)
|
||||
The process and timing look like this:
|
||||
|
||||
|
||||
## <a href="" id="add-lob-publisher"></a>Add an LOB publisher (Admin)
|
||||
Admins need to invite developer or ISVs to become an LOB publisher.
|
||||
|
||||
**To invite a developer to become an LOB publisher**
|
||||
@ -47,6 +49,7 @@ Admins need to invite developer or ISVs to become an LOB publisher.
|
||||
1. Sign in to [Microsoft Store for Business](https://businessstore.microsoft.com).
|
||||
2. Click **Manage**, click **Permissions**, and then choose **Line-of-business publishers**.
|
||||
3. On the Line-of business publishers page, click **Invite** to send an email invitation to a developer.
|
||||
|
||||
>[!Note]
|
||||
> This needs to be the email address listed in contact info for the developer account.
|
||||
|
||||
|
||||
@ -1658,11 +1658,16 @@ The DM agent for [push-button reset](https://msdn.microsoft.com/windows/hardware
|
||||
<li>Connectivity/AllowPhonePCLinking</li>
|
||||
<li>RestrictedGroups/ConfigureGroupMembership</li>
|
||||
</ul>
|
||||
<p>The following policy was updated in Windows 10, version 1803:</p>
|
||||
<p>The following existing policies were updated:</p>
|
||||
<ul>
|
||||
<li>TextInput/AllowIMENetworkAccess - when this policy is set to 1, suggestions from the Microsoft AI chatbot Rinna are enabled in the Japanese IME.</li>
|
||||
<li>InternetExplorer/AllowSiteToZoneAssignmentList - updated the description and added an example SyncML</li>
|
||||
<li>TextInput/AllowIMENetworkAccess - introduced new suggestion services in Japanese IME in addition to cloud suggestion.</li>
|
||||
</ul>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[Policy CSP - Bluetooth](policy-csp-bluetooth.md)</td>
|
||||
<td style="vertical-align:top"><p>Added new section [ServicesAllowedList usage guide](policy-csp-bluetooth.md#servicesallowedlist-usage-guide).</p>
|
||||
</td></tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
@ -282,7 +282,7 @@ If this policy is not set or it is deleted, the default local radio name is used
|
||||
<!--Description-->
|
||||
Set a list of allowable services and profiles. String hex formatted array of Bluetooth service UUIDs in canonical format, delimited by semicolons. For example, {782AFCFC-7CAA-436C-8BF0-78CD0FFBD4AF}.
|
||||
|
||||
The default value is an empty string.
|
||||
The default value is an empty string. For more information, see [ServicesAllowedList usage guide](#servicesallowedlist-usage-guide)
|
||||
|
||||
<!--/Description-->
|
||||
<!--/Policy-->
|
||||
@ -297,6 +297,95 @@ Footnote:
|
||||
|
||||
<!--/Policies-->
|
||||
|
||||
## ServicesAllowedList usage guide
|
||||
|
||||
When the Bluetooth/ServicesAllowedList policy is provisioned, it will only allow pairing and connections of Windows PCs and phones to explicitly define Bluetooth profiles and services. It is an allowed list, enabling admins to still allow custom Bluetooth profiles that are not defined by the Bluetooth Special Interests Group (SIG).
|
||||
|
||||
To define which profiles and services are allowed, enter the profile or service Universally Unique Identifiers (UUID) using semicolon delimiter. To get a profile UUID, refer to the [Service Discovery](https://www.bluetooth.com/specifications/assigned-numbers/service-discovery) page on the Bluetooth SIG website.
|
||||
|
||||
These UUIDs all use the same base UUID with the profile identifiers added to the beginning of the base UUID.
|
||||
|
||||
Here are some examples:
|
||||
|
||||
**Bluetooth Headsets for Voice (HFP)**
|
||||
|
||||
BASE_UUID = 0x00000000-0000-1000-8000-00805F9B34FB
|
||||
|
||||
|UUID name |Protocol specification |UUID |
|
||||
|---------|---------|---------|
|
||||
|HFP(Hands Free Profile) |Hands-Free Profile (HFP) * |0x111E |
|
||||
|
||||
Footnote: * Used as both Service Class Identifier and Profile Identifier.
|
||||
|
||||
Hands Free Profile UUID = base UUID + 0x111E to the beginning = 0000111E-0000-1000-8000-00805F9B34FB
|
||||
|
||||
**Allow Audio Headsets only (Voice)**
|
||||
|
||||
|Profile |Reasoning |UUID |
|
||||
|---------|---------|---------|
|
||||
|HFP (Hands Free Profile) |For voice enabled headsets |0x111E |
|
||||
|GAP (Generic Access Profile)* |Generic service used by Bluetooth |0x1800 |
|
||||
|DID (Device ID)* |Generic service used by Bluetooth |0x180A |
|
||||
|Scan Parameters* |Generic service used by Bluetooth |0x1813 |
|
||||
|
||||
Footnote: * *GAP, DID, and Scan Parameter are required, as these are underlying profiles and services used by all Bluetooth devices.
|
||||
|
||||
This means that if you only want Bluetooth headsets, the UUIDs are:
|
||||
|
||||
{0000111E-0000-1000-8000-00805F9B34FB};{00001800-0000-1000-8000-00805F9B34FB};{0000180A-0000-1000-8000-00805F9B34FB};{00001813-0000-1000-8000-00805F9B34FB}
|
||||
|
||||
**Allow Audio Headsets and Speakers (Voice & Music)**
|
||||
|
||||
|Profile |Reasoning |UUID |
|
||||
|---------|---------|---------|
|
||||
|HFP (Hands Free Profile) |For voice enabled headsets |0x111E |
|
||||
|A2DP Source (Advance Audio Distribution)|For streaming to Bluetooth speakers |0x110A |
|
||||
|GAP (Generic Access Profile) |Generic service used by Bluetooth |0x1800 |
|
||||
|Device ID (DID) |Generic service used by Bluetooth |0x180A |
|
||||
|Scan Parameters |Generic service used by Bluetooth |0x1813 |
|
||||
|
||||
{0000111E-0000-1000-8000-00805F9B34FB};{0000110A-0000-1000-8000-00805F9B34FB};{00001800-0000-1000-8000-00805F9B34FB};{0000180A-0000-1000-8000-00805F9B34FB};{00001813-0000-1000-8000-00805F9B34FB}
|
||||
|
||||
**Classic Keyboards and Mice**
|
||||
|
||||
|Profile |Reasoning |UUID |
|
||||
|---------|---------|---------|
|
||||
|HID (Human Interface Device) |For classic BR/EDR keyboards and mice |0x1124 |
|
||||
|GAP (Generic Access Profile) |Generic service used by Bluetooth |0x1800 |
|
||||
|DID (Device ID) |Generic service used by Bluetooth |0x180A |
|
||||
|Scan Parameters |Generic service used by Bluetooth |0x1813 |
|
||||
|
||||
{00001801-0000-1000-8000-00805F9B34FB};{00001812-0000-1000-8000-00805F9B34FB};{00001800-0000-1000-8000-00805F9B34FB};{0000180A-0000-1000-8000-00805F9B34FB};{00001813-0000-1000-8000-00805F9B34FB}
|
||||
|
||||
> [!Note]
|
||||
> For both Classic and LE use a super set of the two formula’s UUIDs
|
||||
|
||||
**LE Keyboards and Mice**
|
||||
|
||||
|Profile |Reasoning |UUID |
|
||||
|---------|---------|---------|
|
||||
|Generic Access Atribute |For the LE Protocol |0x1801 |
|
||||
|HID Over GATT * |For LE keyboards and mice |0x1812 |
|
||||
|GAP (Generic Access Profile) |Generic service used by Bluetooth |0x1800 |
|
||||
|DID (Device ID) |Generic service used by Bluetooth |0x180A |
|
||||
|Scan Parameters |Generic service used by Bluetooth |0x1813 |
|
||||
|
||||
Footnote: * The Surface pen uses the HID over GATT profile
|
||||
|
||||
{00001801-0000-1000-8000-00805F9B34FB};{00001812-0000-1000-8000-00805F9B34FB};{00001800-0000-1000-8000-00805F9B34FB};{0000180A-0000-1000-8000-00805F9B34FB};{00001813-0000-1000-8000-00805F9B34FB}
|
||||
|
||||
**Allow File Transfer**
|
||||
|
||||
|Profile |Reasoning |UUID |
|
||||
|---------|---------|---------|
|
||||
|OBEX Object Push (OPP) |For file transfer |0x1105 |
|
||||
|Object Exchange (OBEX) |Protocol for file transfer |0x0008 |
|
||||
|Generic Access Profile (GAP) |Generic service used by Bluetooth |0x1800 |
|
||||
|Device ID (DID) |Generic service used by Bluetooth |0x180A |
|
||||
|Scan Parameters |Generic service used by Bluetooth |0x1813 |
|
||||
|
||||
{00001105-0000-1000-8000-00805F9B34FB};{00000008-0000-1000-8000-00805F9B34FB};{0000111E-0000-1000-8000-00805F9B34FB};{00001800-0000-1000-8000-00805F9B34FB};{0000180A-0000-1000-8000-00805F9B34FB};{00001813-0000-1000-8000-00805F9B34FB}
|
||||
|
||||
<!--StartHoloLens-->
|
||||
## <a href="" id="hololenspolicies"></a>Bluetooth policies supported by Windows Holographic for Business
|
||||
|
||||
|
||||
@ -2129,6 +2129,11 @@ Value - A number indicating the zone with which this site should be associated f
|
||||
|
||||
If you disable or do not configure this policy, users may choose their own site-to-zone assignments.
|
||||
|
||||
> [!Note]
|
||||
> This policy is a list that contains the site and index value.
|
||||
|
||||
The list is a set of pairs of strings. Each string is seperated by F000. Each pair of string are stored as a registry name and value. The registry name is the site and the value is an index. The index has to be sequential. See an example below.
|
||||
|
||||
<!--/Description-->
|
||||
> [!TIP]
|
||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
||||
@ -2145,6 +2150,31 @@ ADMX Info:
|
||||
- GP ADMX file name: *inetres.admx*
|
||||
|
||||
<!--/ADMXBacked-->
|
||||
<!--Example-->
|
||||
```syntax
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
<CmdID>2</CmdID>
|
||||
<Item>
|
||||
<Meta>
|
||||
<Format>chr</Format>
|
||||
<Type>text/plain</Type>
|
||||
</Meta>
|
||||
<Target>
|
||||
<LocURI>./Device/Vendor/MSFT/Policy/Config/InternetExplorer/AllowSiteToZoneAssignmentList</LocURI>
|
||||
</Target>
|
||||
<Data><Enabled/><Data id="IZ_ZonemapPrompt" value="http://adfs.contoso.org1http://microsoft.com2"/></Data>
|
||||
</Item>
|
||||
</Replace>
|
||||
<Final/>
|
||||
</SyncBody>
|
||||
```
|
||||
|
||||
Value and index pairs in the SyncML example:
|
||||
- http://adfs.contoso.org 1
|
||||
- http://microsoft.com 2
|
||||
|
||||
<!--/Example-->
|
||||
<!--/Policy-->
|
||||
|
||||
<hr/>
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user