mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-18 11:53:37 +00:00
Merge branch 'master' of https://github.com/Microsoft/win-cpub-itpro-docs into 8442312
This commit is contained in:
@ -410,10 +410,10 @@ You can use the following sample script to create a VBScript file to retrieve th
|
|||||||
' Usage
|
' Usage
|
||||||
' --------------------------------------------------------------------------------
|
' --------------------------------------------------------------------------------
|
||||||
Sub ShowUsage
|
Sub ShowUsage
|
||||||
Wscript.Echo "USAGE: GetBitLockerKeyPackageAD [Path To Saved Key Package] [Optional Computer Name]"
|
Wscript.Echo "USAGE: GetBitLockerKeyPackageADDS [Path To Save Key Package] [Optional Computer Name]"
|
||||||
Wscript.Echo "If no computer name is specified, the local computer is assumed."
|
Wscript.Echo "If no computer name is specified, the local computer is assumed."
|
||||||
Wscript.Echo
|
Wscript.Echo
|
||||||
Wscript.Echo "Example: GetBitLockerKeyPackageAD E:\bitlocker-ad-key-package mycomputer"
|
Wscript.Echo "Example: GetBitLockerKeyPackageADDS E:\bitlocker-ad-key-package mycomputer"
|
||||||
WScript.Quit
|
WScript.Quit
|
||||||
End Sub
|
End Sub
|
||||||
' --------------------------------------------------------------------------------
|
' --------------------------------------------------------------------------------
|
||||||
@ -541,13 +541,23 @@ Function BinaryToString(Binary)
|
|||||||
BinaryToString = S
|
BinaryToString = S
|
||||||
End Function
|
End Function
|
||||||
WScript.Quit
|
WScript.Quit
|
||||||
|
```
|
||||||
|
|
||||||
The following sample script exports a new key package from an unlocked, encrypted volume.
|
The following sample script exports a new key package from an unlocked, encrypted volume.
|
||||||
To run this script, start by saving the code into a VBS file (for example, GetBitLockerKeyPackage.vbs). Then, open an administrator command prompt and use “cscript” to run the saved file (for example, type "cscript GetBitLockerKeyPackage.vbs -?").
|
|
||||||
|
**To run the sample key package retrieval script**
|
||||||
|
|
||||||
|
1. Save the following sample script in a VBScript file. For example: GetBitLockerKeyPackage.vbs
|
||||||
|
2. Open an administrator command prompt, type a command similar to the following:
|
||||||
|
|
||||||
|
**cscript GetBitLockerKeyPackage.vbs -?**
|
||||||
|
|
||||||
|
``` syntax
|
||||||
' --------------------------------------------------------------------------------
|
' --------------------------------------------------------------------------------
|
||||||
' Usage
|
' Usage
|
||||||
' --------------------------------------------------------------------------------
|
' --------------------------------------------------------------------------------
|
||||||
Sub ShowUsage
|
Sub ShowUsage
|
||||||
Wscript.Echo "USAGE: GetBitLockerKeyPackage [VolumeLetter/DriveLetter:] [Path To Saved Key Package]"
|
Wscript.Echo "USAGE: GetBitLockerKeyPackage [VolumeLetter/DriveLetter:] [Path To Save Key Package]"
|
||||||
Wscript.Echo
|
Wscript.Echo
|
||||||
Wscript.Echo "Example: GetBitLockerKeyPackage C: E:\bitlocker-backup-key-package"
|
Wscript.Echo "Example: GetBitLockerKeyPackage C: E:\bitlocker-backup-key-package"
|
||||||
WScript.Quit
|
WScript.Quit
|
||||||
|
@ -28,7 +28,7 @@ Follow these steps to create the VPN policy you want to use with WIP.
|
|||||||
|
|
||||||
2. Go to **Windows**, click the **VPN Profile (Windows 10 Desktop and Mobile and later)**, click **Create and Deploy a Custom Policy**, and then click **Create Policy**.
|
2. Go to **Windows**, click the **VPN Profile (Windows 10 Desktop and Mobile and later)**, click **Create and Deploy a Custom Policy**, and then click **Create Policy**.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
3. Type *WIPModeID* into the **Name** box, along with an optional description for your policy into the **Description** box.
|
3. Type *WIPModeID* into the **Name** box, along with an optional description for your policy into the **Description** box.
|
||||||
|
|
||||||
@ -49,7 +49,7 @@ Follow these steps to create the VPN policy you want to use with WIP.
|
|||||||
5. In the **Authentication** area, choose the authentication method that matches your VPN infrastructure, either **Username and Password** or **Certificates**.<p>
|
5. In the **Authentication** area, choose the authentication method that matches your VPN infrastructure, either **Username and Password** or **Certificates**.<p>
|
||||||
It's your choice whether you check the box to **Remember the user credentials at each logon**.
|
It's your choice whether you check the box to **Remember the user credentials at each logon**.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
6. You can leave the rest of the default or blank settings, and then click **Save Policy**.
|
6. You can leave the rest of the default or blank settings, and then click **Save Policy**.
|
||||||
|
|
||||||
@ -77,7 +77,7 @@ The final step to making your VPN configuration work with WIP, is to link your t
|
|||||||
|
|
||||||
2. Go to **Windows**, click the **Custom Configuration (Windows 10 Desktop and Mobile and later)**, click **Create and Deploy a Custom Policy**, and then click **Create Policy**.
|
2. Go to **Windows**, click the **Custom Configuration (Windows 10 Desktop and Mobile and later)**, click **Create and Deploy a Custom Policy**, and then click **Create Policy**.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
3. Type a name (required) and an optional description for your policy into the **Name** and **Description** boxes.
|
3. Type a name (required) and an optional description for your policy into the **Name** and **Description** boxes.
|
||||||
|
|
||||||
|
@ -156,7 +156,7 @@ If you only want to remove some of the default pinned apps, you would use this m
|
|||||||
<CustomTaskbarLayoutCollection PinListPlacement="Replace">
|
<CustomTaskbarLayoutCollection PinListPlacement="Replace">
|
||||||
<defaultlayout:TaskbarLayout>
|
<defaultlayout:TaskbarLayout>
|
||||||
<taskbar:TaskbarPinList>
|
<taskbar:TaskbarPinList>
|
||||||
<taskbar:DesktopApp DesktopApplicationLinkPath=”%APPDATA%Microsoft\Windows\Start Menu\Programs\Accessories\Internet Explorer.lnk”/>
|
<taskbar:DesktopApp DesktopApplicationLinkPath="%APPDATA%\Microsoft\Windows\Start Menu\Programs\Accessories\Internet Explorer.lnk"/>
|
||||||
<taskbar:DesktopApp DesktopApplicationLinkPath="%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\Accessories\Paint.lnk" />
|
<taskbar:DesktopApp DesktopApplicationLinkPath="%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\Accessories\Paint.lnk" />
|
||||||
<taskbar:UWA AppUserModelID="Microsoft.Office.Word_8wekyb3d8bbwe!microsoft.word" />
|
<taskbar:UWA AppUserModelID="Microsoft.Office.Word_8wekyb3d8bbwe!microsoft.word" />
|
||||||
</taskbar:TaskbarPinList>
|
</taskbar:TaskbarPinList>
|
||||||
|
@ -25,7 +25,7 @@ With the new Windows Store for Business, organizations can make volume purchases
|
|||||||
|
|
||||||
Organizations of any size can benefit from using the Store for Business provides:
|
Organizations of any size can benefit from using the Store for Business provides:
|
||||||
|
|
||||||
- **Scales to fit the size of your business** - For smaller businesses, with Azure AD accounts and Windows 10 devices, you can quickly have an end-to-end process for acquiring and distributing content using the Store for Business. For larger businesses, all the capabilities of the Store for Businessare available to you, or you can integrate the Store for Businesswith management tools, for greater control over access to apps and app updates. You can use existing work or school accounts.
|
- **Scales to fit the size of your business** - For smaller businesses, with Azure AD accounts and Windows 10 devices, you can quickly have an end-to-end process for acquiring and distributing content using the Store for Business. For larger businesses, all the capabilities of the Store for Business are available to you, or you can integrate the Store for Business with management tools, for greater control over access to apps and app updates. You can use existing work or school accounts.
|
||||||
|
|
||||||
- **Bulk app acquisition** - Acquire apps in volume from the Store for Business.
|
- **Bulk app acquisition** - Acquire apps in volume from the Store for Business.
|
||||||
|
|
||||||
@ -145,11 +145,11 @@ Once signed in to the Store for Business, you can browse and search for all prod
|
|||||||
|
|
||||||
- Universal Windows Platform apps
|
- Universal Windows Platform apps
|
||||||
|
|
||||||
- Universal Windows apps, by device: Phone, Surface Hub, IOT devices , HoloLens
|
- Universal Windows apps, by device: Phone, Surface Hub, IOT devices, HoloLens
|
||||||
|
|
||||||
Apps purchased from the Store for Business only work on Windows 10 devices.
|
Apps purchased from the Store for Business only work on Windows 10 devices.
|
||||||
|
|
||||||
Line-of-business (LOB) apps are also supported via the Business store. You can invite IT developers or ISVs to be LOB publishers for your organization. This allows them to submit apps via the developer center that are only available to your organization. These apps can be distributed using the distribution methods discussed in this topic. For more information, see Working with Line-of-Business apps.
|
Line-of-business (LOB) apps are also supported via the Business store. You can invite IT developers or ISVs to be LOB publishers for your organization. This allows them to submit apps via the developer center that are only available to your organization. These apps can be distributed using the distribution methods discussed in this topic. For more information, see [Working with Line-of-Business apps](working-with-line-of-business-apps.md).
|
||||||
|
|
||||||
**App licensing model**
|
**App licensing model**
|
||||||
|
|
||||||
@ -265,7 +265,7 @@ Store for Business is currently available in these markets.
|
|||||||
## <a href="" id="isv-wsfb"></a>ISVs and the Store for Business
|
## <a href="" id="isv-wsfb"></a>ISVs and the Store for Business
|
||||||
|
|
||||||
|
|
||||||
Developers in your organization, or ISVs can create content specific to your organization. In the Store for Business, we call these app line-of-business (LOB) apps, and the devs that create them are LOB publishers. The process looks like this:
|
Developers in your organization, or ISVs can create content specific to your organization. In the Store for Business, we call these line-of-business (LOB) apps, and the devs that create them are LOB publishers. The process looks like this:
|
||||||
|
|
||||||
- Admin invites devs to be LOB publishers for your organization. These devs can be internal devs, or external ISVs.
|
- Admin invites devs to be LOB publishers for your organization. These devs can be internal devs, or external ISVs.
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user