mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
fixing markdig note warnings
This commit is contained in:
Liza Poggemeyer
parent
74f2d676a7
commit
a99b07b1c6
@ -51,7 +51,7 @@ The changes in App-V for Windows 10, version 1607 impact existing implementation
|
||||
* The App-V client is installed on user devices automatically with Windows 10, version 1607, and no longer has to be deployed separately. Performing an in-place upgrade to Windows 10, version 1607, on user devices automatically installs the App-V client.
|
||||
* In previous releases of App-V, the application sequencer was included in the Microsoft Desktop Optimization Pack. Although you’ll need to use the new application sequencer to create new virtualized applications, existing virtualized applications will continue to work. The App-V application sequencer is available from the [Windows 10 Assessment and Deployment Kit (ADK)](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit).
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>If you're already using App-V 5.x, you don't need to redeploy the App-V server components, as they haven't changed since App-V 5.0's release.
|
||||
|
||||
For more information about how to configure an existing App-V installation after upgrading user devices to Windows 10, see [Upgrading to App-V for Windows 10 from an existing installation](../app-v/appv-upgrading-to-app-v-for-windows-10-from-an-existing-installation.md) and [Migrating to App-V for Windows 10 from a previous version](../app-v/appv-migrating-to-appv-from-a-previous-version.md).
|
||||
|
||||
@ -411,14 +411,14 @@ The process then configures the client for package or connection group additions
|
||||
|
||||
5. Remove objects that are not published to the target (user or machine).
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>This will not perform a package deletion but rather remove integration points for the specific target (user or machine) and remove user catalog files (machine catalog files for globally published).
|
||||
|
||||
6. Invoke background load mounting based on client configuration.
|
||||
|
||||
7. Packages that already have publishing information for the machine or user are immediately restored.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>This condition occurs as a product of removal without unpublishing with background addition of the package.
|
||||
|
||||
This completes an App-V package add for the publishing refresh process. The next step is publishing the package to a specific target (machine or user).
|
||||
@ -447,7 +447,7 @@ During the Publishing Refresh operation, the specific publishing operation, **Pu
|
||||
|
||||
2. Store backup information in the user’s registry and roaming profile (Shortcut Backups).
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>This enables restore extension points if the package is unpublished.
|
||||
|
||||
3. Run scripts targeted for publishing timing.
|
||||
|
||||
@ -34,7 +34,7 @@ Use the following procedure to configure access to virtualized packages.
|
||||
|
||||
1. Using the format **mydomain** \\ **groupname**, enter the name or part of the name of an Active Directory group object, then select **Check**.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>Ensure that you provide an associated domain name for the group that you are searching for.
|
||||
|
||||
3. Grant access to the package by first selecting the desired group, then selecting **Grant Access**. The newly added group is displayed in the **AD entities with access** pane.
|
||||
|
||||
@ -93,7 +93,7 @@ You can use the connection group file to configure each connection group by usin
|
||||
|
||||
- Specify runtime priorities for connection groups. To edit priority by using the App-V Management Console, select the connection group and then select **Edit**.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>A package only requires priority if it's associated with more than one connection group.
|
||||
- Specify package precedence within the connection group.
|
||||
|
||||
|
||||
@ -54,7 +54,7 @@ The App-V package converter will save the App-V 4.6 installation root folder and
|
||||
|
||||
Additionally, the package converter optimizes performance of packages in App-V for Windows 10 by setting the package to stream fault the App-V package. This is more performant than the primary feature block and fully downloading the package. The flag **DownloadFullPackageOnFirstLaunch** allows you to convert the package and set the package to be fully downloaded by default.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>Before you specify the output directory, you must create the output directory.
|
||||
|
||||
### Advanced Conversion Tips
|
||||
|
||||
@ -30,7 +30,7 @@ You can create a dynamic user configuration file with the App-V Management Conso
|
||||
|
||||
4. Select **Advanced**, and then select **Export Configuration**. Enter a file name and select **Save**. Now you can edit the file to configure a package for a user.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>If you want to export a configuration while running on Windows Server, make sure to disable the IE Enhanced Security Configuration setting. If this setting is enabled and set to block downloads, you won't be able to download anything from the App-V Server.
|
||||
|
||||
|
||||
|
||||
@ -53,7 +53,7 @@ Use the following procedure to create a package accelerator.
|
||||
|
||||
6. On the **Gathering Information** page, review the files that you couldn't find in the location specified by the **Installation Files** page. If the files displayed are not required, select **Remove these files**, then select **Next**. If the files are required, select **Previous** and copy the required files to the directory specified on the **Installation Files** page.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>You must either remove the unrequired files or select **Previous** and locate the required files to advance to the next page of this wizard.
|
||||
|
||||
7. On the **Select Files** page, carefully review the detected files. Clear any file the package accelerator doesn't need to run successfully and select only the files that the application requires. When you're done, select **Next**.
|
||||
|
||||
@ -40,7 +40,7 @@ Use the following procedure to create a virtual application package with the App
|
||||
|
||||
Alternatively, if you have already copied the installation files to a directory on this computer, select **Make New Folder**, browse to the folder that contains the installation files, then select **Next**.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>You can specify the following types of supported installation files:
|
||||
> - Windows Installer files (**.msi**)
|
||||
> - Cabinet files (.cab)
|
||||
|
||||
@ -27,7 +27,7 @@ You must first create and save a project template, including a virtual app packa
|
||||
|
||||
1. On the device running the App-V Sequencer, select **Start**, select **All Programs**, select **Microsoft Application Virtualization**, and then select **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>If the virtual app package is currently open in the App-V Sequencer console, skip to Step 3 of this procedure.
|
||||
|
||||
2. On the **File** menu, select **Open**, select **Edit Package**, browse for the virtual app package that includes the settings you want to save with the App-V Project Template, and then select **Edit** to change any of the settings or info included in the file.
|
||||
|
||||
@ -31,7 +31,7 @@ You can use the App-V Sequencer to perform the following tasks:
|
||||
- Upgrade existing packages. You can expand an existing package onto the computer running the sequencer and then upgrade the application to create a newer version.
|
||||
- Edit configuration information associated with an existing package. For example, you can add a shortcut or modify a file type association.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>You must create shortcuts and save them to an available network location to allow roaming. If a shortcut is created and saved in a private location, the package must be published locally to the computer running the App-V client.
|
||||
|
||||
- Convert existing virtual packages.
|
||||
|
||||
@ -54,7 +54,7 @@ ms.topic: article
|
||||
| You are using a custom database name. | Select **Custom configuration** and type the database name.<br/>The database name must be unique, or the installation will fail.|
|
||||
8. On the **Configure** page, accept the default value, **Use this local computer**.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>If you're installing the Management server and Management database side-by-side, the appropriate options are selected by default and cannot be changed.
|
||||
9. On the initial **Create New Reporting Database** page, configure the **Microsoft SQL Server instance** and **Reporting Server database** by selecting the appropriate option below.
|
||||
|
||||
@ -64,7 +64,7 @@ ms.topic: article
|
||||
| You are using a custom database name. | Select **Custom configuration** and type the database name.<br/>The database name must be unique, or the installation will fail.|
|
||||
10. On the **Configure** page, accept the default value: **Use this local computer**.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>If you're installing the Management server and Management database side-by-side, the appropriate options are selected by default and cannot be changed.
|
||||
11. On the **Configure** (Management Server Configuration) page, specify the following:
|
||||
|
||||
|
||||
@ -110,7 +110,7 @@ The XML file included in the Office Deployment Tool specifies the product detail
|
||||
</Configuration>
|
||||
```
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>The configuration XML is a sample XML file. This file includes lines that are commented out. You can “uncomment” these lines to customize additional settings with the file.
|
||||
|
||||
The previous example of an XML configuration file specifies that Office 2013 ProPlus 32-bit edition, including Visio ProPlus, will be downloaded in English to the \\\\server\\Office 2013, which is the location where Office applications will be saved to. Note that the Product ID of the applications will not affect the final licensing of Office. Office 2013 App-V packages with various licensing can be created from the same applications by specifying licensing in a later stage. For more information, see [Customizable attributes and elements of the XML file](#customizable-attributes-and-elements-of-the-xml-file), later in this topic.
|
||||
@ -206,7 +206,7 @@ After you download the Office 2013 applications through the Office Deployment To
|
||||
|
||||
An example of when to use this parameter is if you create different packages for different users. For example, you can create a package with just Office 2013 for some users, and create another package with Office 2013 and Visio 2013 for another set of users.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>Even if you use unique package IDs, you can still deploy only one App-V package to a single device.
|
||||
2. Use the **/packager** command to convert the Office applications to an Office 2013 App-V package.
|
||||
|
||||
@ -231,7 +231,7 @@ After you download the Office 2013 applications through the Office Deployment To
|
||||
* **App-V Packages**, which contains an Office 2013 App-V package and two deployment configuration files.<br>
|
||||
* **WorkingDir**
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>To troubleshoot any issues, see the log files in the %temp% directory (default).
|
||||
3. Verify that the Office 2013 App-V package works correctly:
|
||||
|
||||
|
||||
@ -111,7 +111,7 @@ The XML file included in the Office Deployment Tool specifies the product detail
|
||||
</Configuration>
|
||||
```
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>The configuration XML is a sample XML file. The file includes lines that are commented out. You can “uncomment” these lines to customize additional settings with the file. To uncomment these lines, remove the ```<! - -``` from the beginning of the line, and the ```-- >``` from the end of the line.
|
||||
|
||||
The previous example of an XML configuration file specifies that Office 2016 ProPlus 32-bit edition, including Visio ProPlus, will be downloaded in English to the \\\\server\\Office2016 location where Office applications will be saved. Note that the Product ID of the applications will not affect Office's final licensing. You can create Office 2016 App-V packages with various licensing from the same applications by specifying licensing in a later stage. The following table summarizes the XML file's customizable attributes and elements:
|
||||
@ -190,7 +190,7 @@ After you download the Office 2016 applications through the Office Deployment To
|
||||
|
||||
An example of when to use this parameter is if you create different packages for different users. For example, you can create a package with just Office 2016 for some users, and create another package with Office 2016 and Visio 2016 for another set of users.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>Even if you use unique package IDs, you can still deploy only one App-V package to a single device.
|
||||
2. Use the /packager command to convert the Office applications to an Office 2016 App-V package.
|
||||
|
||||
@ -215,7 +215,7 @@ After you download the Office 2016 applications through the Office Deployment To
|
||||
* **App-V Packages**—contains an Office 2016 App-V package and two deployment configuration files.
|
||||
* **WorkingDir**
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>To troubleshoot any issues, see the log files in the %temp% directory (default).
|
||||
3. Verify that the Office 2016 App-V package works correctly:
|
||||
|
||||
@ -359,7 +359,7 @@ To upgrade an Office 2016 package, use the Office Deployment Tool. To upgrade a
|
||||
|
||||
1. Create a new Office 2016 package through the Office Deployment Tool that uses the most recent Office 2016 application software. The most recent Office 2016 bits can always be obtained through the download stage of creating an Office 2016 App-V Package. The newly created Office 2016 package will have the most recent updates and a new Version ID. All packages created using the Office Deployment Tool have the same lineage.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>Office App-V packages have two Version IDs:
|
||||
>* An Office 2016 App-V Package Version ID that is unique across all packages created using the Office Deployment Tool.
|
||||
>* A second App-V Package Version ID, formatted as X.X.X.X, in the AppX manifest that will only change if there is a new version of Office itself. For example, if a new Office 2016 release with upgrades is available, and a package is created through the Office Deployment Tool to incorporate these upgrades, the X.X.X.X version ID will change to reflect the new version of Office. The App-V server will use the X.X.X.X version ID to differentiate this package and recognize that it contains new upgrades to the previously published package, and as a result, publish it as an upgrade to the existing Office 2016 package.
|
||||
|
||||
@ -35,7 +35,7 @@ App-V offers the following five server components, each of which serves a specif
|
||||
|
||||
* **Management server.** Use the App-V management server and console to manage your App-V infrastructure. See [Administering App-V with the management console](appv-administering-virtual-applications-with-the-management-console.md) for more information about the management server.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>If you are using App-V with your electronic software distribution solution, you don’t need to use the management server and console. However, you may want to take advantage of the reporting and streaming capabilities in App-V.
|
||||
* **Management database.** Use the App-V management database to facilitate database pre-deployments for App-V management. For more information about the management database, see [How to deploy the App-V server](appv-deploy-the-appv-server.md).
|
||||
* **Publishing server.** Use the App-V publishing server to host and stream virtual applications. The publishing server supports the HTTP and HTTPS protocols and does not require a database connection. To learn how to configure the publishing server, see [How to install the App-V publishing server](appv-install-the-publishing-server-on-a-remote-computer.md).
|
||||
|
||||
@ -33,7 +33,7 @@ Use the following procedure to install the database server and management server
|
||||
* If you are using a custom database name, select **Custom configuration** and enter the database name.
|
||||
7. On the next **Create new management server database** page, select **Use a remote computer**, then enter the remote machine account using the following format: ```Domain\MachineAccount```.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>If you plan to deploy the management server on the same computer you must select **Use this local computer**. Specify the user name for the management server **Install Administrator** using the following format: ```Domain\AdministratorLoginName```. After that, select **Next**.
|
||||
8. To start the installation, select **Install**.
|
||||
|
||||
@ -49,7 +49,7 @@ Use the following procedure to install the database server and management server
|
||||
* If you're using a custom database name, select **Custom configuration** and enter the database name.
|
||||
7. On the next **Create new management server database** page, select **Use a remote computer**, and enter the remote machine account using the following format: ```Domain\MachineAccount```.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>If you plan to deploy the reporting server on the same computer you must select **Use this local computer**. Specify the user name for the reporting server **Install Administrator** using the following format: Domain\\AdministratorLoginName. After that, select **Next**.
|
||||
8. To start the installation, select **Install**.
|
||||
|
||||
@ -68,7 +68,7 @@ Use the following procedure to install the database server and management server
|
||||
* The App-V Reporting Database scripts and instructions readme are located in the following folder: **InstallationExtractionLocation** \\ **Database Scripts** \\ **Reporting Database**.
|
||||
4. For each database, copy the scripts to a share and modify them following the instructions in the readme file.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>For more information about modifying the required SIDs contained in the scripts see, [How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md).
|
||||
5. Run the scripts on the computer running Microsoft SQL Server.
|
||||
|
||||
|
||||
@ -25,7 +25,7 @@ To install the management server on a standalone computer and connect it to the
|
||||
5. On the **Installation Location** page, accept the default location, then select **Next**.
|
||||
6. On the **Configure Existing Management Database** page, select **Use a remote SQL Server**, then enter the computer running Microsoft SQL's machine name, such as ```SqlServerMachine```.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>If the Microsoft SQL Server is deployed on the same server, select **Use local SQL Server**. For the SQL Server Instance, select **Use the default instance**. If you are using a custom Microsoft SQL Server instance, you must select **Use a custom instance**, then enter the instance's name. Specify the **SQL Server Database name** that this management server will use, such as ```AppvManagement```.
|
||||
7. On the **Configure management server configuration** page, specify the following items:
|
||||
* The AD group or account that will connect to the management console for administrative purposes for example **MyDomain\\MyUser** or **MyDomain\\AdminGroup**. The account or AD group you specify will be enabled to manage the server through the management console. You can add additional users or groups using the management console after installation
|
||||
|
||||
@ -30,7 +30,7 @@ Use the following procedure to install the reporting server on a standalone comp
|
||||
5. On the **Installation location** page, accept the default location and select **Next**.
|
||||
6. On the **Configure existing reporting database** page, select **Use a remote SQL Server**, then enter the machine name of the computer running Microsoft SQL Server. For example, you can name your computer **SqlServerMachine**.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>If the Microsoft SQL Server is deployed on the same server, select **Use local SQL Server**. For the SQL Server instance, select **Use the default instance**. If you're using a custom Microsoft SQL Server instance, select **Use a custom instance**, then enter the name of your custom instance. Specify the **SQL Server Database name** that this reporting server will use; for example, you can name the server **AppvReporting**.
|
||||
7. On the **Configure reporting server configuration** page.
|
||||
|
||||
|
||||
@ -87,7 +87,7 @@ Use the following steps to modify the connection string to include ```failover p
|
||||
2. Navigate to **HKEY\_LOCAL\_MACHINE** \\ **Software** \\ **Microsoft** \\ **AppV** \\ **Server** \\ **ManagementService**.
|
||||
3. Modify the **MANAGEMENT\_SQL\_CONNECTION\_STRING** value with the ```failover partner = <server2>``` value.
|
||||
4. Restart management service using the IIS console.
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>Database Mirroring is on the list of [deprecated database engine features in SQL Server 2012](<https://msdn.microsoft.com/library/ms143729(v=sql.110).aspx>) due to the **AlwaysOn** feature available starting with Microsoft SQL Server 2012.
|
||||
|
||||
Click any of the following links for more information:
|
||||
|
||||
@ -32,7 +32,7 @@ The following list displays the end–to-end high-level workflow for reporting i
|
||||
2. Install the App-V reporting server and associated database. For more information about installing the reporting server see [How to install the Reporting Server on a standalone computer and connect it to the database](appv-install-the-reporting-server-on-a-standalone-computer.md). Configure the time when the computer running the App-V client should send data to the reporting server.
|
||||
3. If you are not using an electronic software distribution system such as Configuration Manager to view reports then you can define reports in SQL Server Reporting Service. Download predefined appvshort Reports from the Download Center at [Application Virtualization SSRS Reports](https://www.microsoft.com/en-us/download/details.aspx?id=42630).
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>If you are using the Configuration Manager integration with App-V, most reports are generated from Configuration Manager rather than from App-V.
|
||||
4. After importing the App-V Windows PowerShell module using **Import-Module AppvClient** as administrator, enable App-V client reporting. This sample Windows PowerShell command enables App-V reporting:
|
||||
|
||||
@ -46,7 +46,7 @@ The following list displays the end–to-end high-level workflow for reporting i
|
||||
5. After the reporting server receives the data from the App-V client it sends the data to the reporting database. When the database receives and processes the client data, a successful reply is sent to the reporting server, which then notifies the App-V client.
|
||||
6. When the App-V client receives the success notification, it empties the data cache to conserve space.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>By default, the cache is cleared after the server confirms receipt of data. You can manually configure the client to save the data cache.
|
||||
|
||||
If the App-V client device does not receive a success notification from the server, it retains data in the cache and tries to resend data at the next configured interval. Clients continue to collect data and add it to the cache.
|
||||
@ -91,7 +91,7 @@ Yes. Besides manually sending reporting using Windows PowerShell cmdlets (**Send
|
||||
For a complete list of client configuration settings, go to [About client configuration settings](appv-client-configuration-settings.md) and look for the following entries: **ReportingEnabled**, **ReportingServerURL**, **ReportingDataCacheLimit**, **ReportingDataBlockSize**, **ReportingStartTime**, **ReportingRandomDelay**, **ReportingInterval**.
|
||||
* Using Group Policy. If distributed using the domain controller, the settings are the same as previously listed.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>Group Policy settings override local settings configured using Windows PowerShell.
|
||||
|
||||
## App-V Client reporting
|
||||
|
||||
@ -56,7 +56,7 @@ No groups are created automatically during App-V setup. You should create the fo
|
||||
Consider the following additional information:
|
||||
|
||||
* Access to the package shares: If a share exists on the same computer as the management Server, the **Network** service requires read access to the share. In addition, each App-V client computer must have read access to the package share.
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>In previous versions of App-V, package share was referred to as content share.
|
||||
* Registering publishing servers with Management Server: A publishing server must be registered with the Management server. For example, it must be added to the database, so that the Publishing server machine accounts are able to call into the Management service API.
|
||||
|
||||
|
||||
@ -55,7 +55,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
5. On the **Select Installer** page, select **Browse** and specify the installation file for the application.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>If the specified application installer modifies security access to a file or directory, existing or new, the associated changes will not be captured into the package.
|
||||
|
||||
If the application does not have an associated installer file and you plan to run all installation steps manually, select the **Perform a Custom Installation** check box, and then select **Next**.
|
||||
@ -73,7 +73,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
9. On the **Configure Software** page, optionally run the programs contained in the package. This step allows you to complete any necessary license or configuration tasks before you deploy and run the package on target computers. To run all the programs at one time, select at least one program, and then select **Run All**. To run specific programs, select the program or programs, and then select **Run Selected**. Complete the required configuration tasks and then close the applications. You may need to wait several minutes for all programs to run.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>To run first-use tasks for any application that is not available in the list, open the application. The associated information will be captured during this step.
|
||||
|
||||
Select **Next**.
|
||||
@ -89,7 +89,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
12. On the **Streaming** page, run each program so that it can be optimized and run more efficiently on target computers. It can take several minutes for all the applications to run. After all applications have run, close each of the applications, and then select **Next**.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>If you do not open any applications during this step, the default streaming method is on-demand streaming delivery. This means applications will be downloaded bit by bit until it can be opened. After that, depending on how the background loading is configured, it will load the rest of the application.
|
||||
|
||||
13. On the **Target OS** page, specify the operating systems that can run this package. To allow all supported operating systems in your environment to run this package, select **Allow this package to run on any operating system**. To configure this package to run only on specific operating systems, select **Allow this package to run only on the following operating systems** and select the operating systems that can run this package. After that, select **Next**.
|
||||
@ -153,7 +153,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
13. On the **Streaming** page, run each program so that it can be optimized and run more efficiently on target computers. Streaming improves the experience when the virtual application package is run on target computers on high-latency networks. It can take several minutes for all applications to run. After all applications have run, close each application. You can also configure the package to be required to be fully downloaded before opening by selecting the **Force applications to be downloaded** check-box. Select **Next**.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>If necessary, you can stop an application from loading during this step. In the **Application Launch** dialog box, select **Stop** and select one of the check boxes: **Stop all applications** or **Stop this application only**.
|
||||
|
||||
14. On the **Target OS** page, specify the operating systems that can run this package. To allow all supported operating systems in your environment to run this package, select the **Allow this package to run on any operating system** check box. To configure this package to run only on specific operating systems, select the **Allow this package to run only on the following operating systems** check box, and then select the operating systems that can run this package. Select **Next**.
|
||||
|
||||
@ -842,7 +842,7 @@ The following diagram shows the BitLocker configuration service provider in tree
|
||||
</Replace>
|
||||
```
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>When you disable the warning prompt, the OS drive's recovery key will back up to the user's Azure Active Directory account. When you allow the warning prompt, the user who receives the prompt can select where to back up the OS drive's recovery key.
|
||||
>
|
||||
>The endpoint for a fixed data drive's backup is chosen in the following order:
|
||||
|
||||
@ -32,7 +32,7 @@ On the desktop, you can create an Active Directory account, such as "enrollment@
|
||||
|
||||
On the desktop and mobile devices, you can use an enrollment certificate or enrollment username and password, such as "enroll@contoso.com" and "enrollmentpassword." These credentials are used in the provisioning package, which you can use to enroll multiple devices to the MDM service. Once the devices are joined, many users can use them.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
> - Bulk-join is not supported in Azure Active Directory Join.
|
||||
> - Bulk enrollment does not work in Intune standalone environment.
|
||||
> - Bulk enrollment works in System Center Configuration Manager (SCCM) + Intune hybrid environment where the ppkg is generated from the SCCM console.
|
||||
|
||||
@ -128,7 +128,7 @@ Requirements:
|
||||
4. Filter using Security Groups.
|
||||
5. Enforce a GPO link.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
> Version 1903 (March 2019) is actually on the Insider program and doesn't yet contain a downloadable version of Templates (version 1903).
|
||||
|
||||
### Related topics
|
||||
|
||||
@ -29,7 +29,7 @@ Third-party MDM servers can manage Windows 10 by using the MDM protocol. The bu
|
||||
|
||||
With Windows 10, version 1809, Microsoft is also releasing a Microsoft MDM security baseline that functions like the Microsoft GP-based security baseline. You can easily integrate this baseline into any MDM to support IT pros’ operational needs, addressing security concerns for modern cloud-managed devices.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>Intune support for the MDM security baseline is coming soon.
|
||||
|
||||
The MDM security baseline includes policies that cover the following areas:
|
||||
|
||||
@ -1690,7 +1690,7 @@ The following list describes the prerequisites for a certificate to be used with
|
||||
|
||||
The following XML sample explains the properties for the EAP TLS XML including certificate filtering.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>For PEAP or TTLS Profiles the EAP TLS XML is embedded within some PEAP or TTLS specific elements.
|
||||
|
||||
|
||||
@ -1793,7 +1793,7 @@ The following XML sample explains the properties for the EAP TLS XML including c
|
||||
</EapHostConfig>
|
||||
```
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>The EAP TLS XSD is located at **%systemdrive%\\Windows\\schemas\\EAPMethods\\eaptlsconnectionpropertiesv3.xsd**
|
||||
|
||||
|
||||
@ -1818,7 +1818,7 @@ Alternatively you can use the following procedure to create an EAP Configuration
|
||||
7. Close the rasphone dialog box.
|
||||
8. Continue following the procedure in the [EAP configuration](eap-configuration.md) topic from Step 9 to get an EAP TLS profile with appropriate filtering.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>You can also set all the other applicable EAP Properties through this UI as well. A guide for what these properties mean can be found in the [Extensible Authentication Protocol (EAP) Settings for Network Access](https://technet.microsoft.com/library/hh945104.aspx) topic.
|
||||
|
||||
|
||||
|
||||
@ -30,7 +30,7 @@ For the list of enrollment scenarios not supported in Windows 10, see [Enrollme
|
||||
|
||||
The discovery web service provides the configuration information necessary for a user to enroll a device with a management service. The service is a restful web service over HTTPS (server authentication only).
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>The administrator of the discovery service must create a host with the address enterpriseenrollment.*domain\_name*.com.
|
||||
|
||||
The device’s automatic discovery flow uses the domain name of the email address that was submitted to the Workplace settings screen during sign in. The automatic discovery system constructs a URI that uses this hostname by appending the subdomain “enterpriseenrollment” to the domain of the email address, and by appending the path “/EnrollmentServer/Discovery.svc”. For example, if the email address is “sample@contoso.com”, the resulting URI for first Get request would be: http:<span></span>//enterpriseenrollment.contoso.com/EnrollmentServer/Discovery.svc
|
||||
@ -129,7 +129,7 @@ The discovery response is in the XML format and includes the following fields:
|
||||
- Authentication policy (AuthPolicy) – Indicates what type of authentication is required. For the MDM server, OnPremise is the supported value, which means that the user will be authenticated when calling the management service URL. This field is mandatory.
|
||||
- Federated is added as another supported value. This allows the server to leverage the Web Authentication Broker to perform customized user authentication, and term of usage acceptance.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>The HTTP server response must not be chunked; it must be sent as one message.
|
||||
|
||||
The following example shows a response received from the discovery web service for OnPremise authentication:
|
||||
@ -214,7 +214,7 @@ After the user is authenticated, the web service retrieves the certificate templ
|
||||
|
||||
MS-XCEP supports very flexible enrollment policies using various Complex Types and Attributes. We will first support the minimalKeyLength, the hashAlgorithmOIDReference policies, and the CryptoProviders. The hashAlgorithmOIDReference has related OID and OIDReferenceID and policySchema in the GetPolicesResponse. The policySchema refers to the certificate template version. Version 3 of MS-XCEP supports hashing algorithms.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>The HTTP server response must not be chunked; it must be sent as one message.
|
||||
|
||||
The following snippet shows the policy web service response.
|
||||
@ -306,7 +306,7 @@ The RequestSecurityToken will use a custom TokenType (http:<span></span>//schema
|
||||
|
||||
The RST may also specify a number of AdditionalContext items, such as DeviceType and Version. Based on these values, for example, the web service can return device-specific and version-specific DM configuration.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>The policy service and the enrollment service must be on the same server; that is, they must have the same host name.
|
||||
|
||||
The following example shows the enrollment web service request for OnPremise authentication.
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Walkthrough use Group Policy to configure Windows Update for Business (Windows 10)
|
||||
title: Walkthrough use Group Policy to configure Windows Update for Business - Windows 10
|
||||
description: Configure Windows Update for Business settings using Group Policy.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user