From 86728891bfaa4107d7d612218bba663a3d306cb3 Mon Sep 17 00:00:00 2001 From: Michael Niehaus Date: Fri, 13 Jul 2018 16:36:00 -0700 Subject: [PATCH 1/4] Update windows-autopilot-requirements-licensing.md Added M365 F1 subscriptions to the list --- .../windows-autopilot-requirements-licensing.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/windows/deployment/windows-autopilot/windows-autopilot-requirements-licensing.md b/windows/deployment/windows-autopilot/windows-autopilot-requirements-licensing.md index a3dd1c1755..ccf644bd1f 100644 --- a/windows/deployment/windows-autopilot/windows-autopilot-requirements-licensing.md +++ b/windows/deployment/windows-autopilot/windows-autopilot-requirements-licensing.md @@ -23,6 +23,8 @@ Windows Autopilot depends on specific capabilities available in Windows 10 and A - One of the following, to provide needed Azure Active Directory (automatic MDM enrollment and company branding features) and MDM functionality: - Microsoft 365 Business subscriptions + + - Microsoft 365 F1 subscriptions - Microsoft 365 Enterprise E3 or E5 subscriptions, which include all Windows 10, Office 365, and EM+S features (Azure AD and Intune) From e076cbcb157b40746b5693c887a99b0a36719070 Mon Sep 17 00:00:00 2001 From: Randolph West Date: Fri, 13 Jul 2018 17:43:25 -0600 Subject: [PATCH 2/4] Update windows-autopilot-requirements-licensing.md --- .../windows-autopilot-requirements-licensing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopilot/windows-autopilot-requirements-licensing.md b/windows/deployment/windows-autopilot/windows-autopilot-requirements-licensing.md index a3dd1c1755..0cd157a332 100644 --- a/windows/deployment/windows-autopilot/windows-autopilot-requirements-licensing.md +++ b/windows/deployment/windows-autopilot/windows-autopilot-requirements-licensing.md @@ -12,7 +12,7 @@ ms.author: coreyp ms.date: 06/01/2018 --- -# Windows Autopilot licesning requirements +# Windows Autopilot licensing requirements **Applies to: Windows 10** From 71c48ff5d231f5ddda732ca28c9c64c2a9304ffa Mon Sep 17 00:00:00 2001 From: Abhilash Mohanta <41289718+Abhilash3107@users.noreply.github.com> Date: Mon, 16 Jul 2018 16:22:39 +0530 Subject: [PATCH 3/4] Repetitive information Repetitive information from line 84-136, should be removed. --- .../app-v/appv-auto-batch-sequencing.md | 56 +------------------ 1 file changed, 1 insertion(+), 55 deletions(-) diff --git a/windows/application-management/app-v/appv-auto-batch-sequencing.md b/windows/application-management/app-v/appv-auto-batch-sequencing.md index 508ae9f351..9cca4f5fb8 100644 --- a/windows/application-management/app-v/appv-auto-batch-sequencing.md +++ b/windows/application-management/app-v/appv-auto-batch-sequencing.md @@ -81,60 +81,6 @@ Where `````` is the name of the virtual machine (VM) with the App-V The cmdlet creates a "clean" checkpoint on the VM. Next, the cmdlet copies the first app installer listed in the ConfigFile from the Host computer to the VM, and finally a new session of the VM opens (through VMConnect) and sequencing of the app begins from the command-line. After completing sequencing and package creation for the first app on the VM, the package is copied from the VM to the Host computer, specified in the *OutputPath* parameter. The cmdlet then goes to the second app on your list, reverting the VM back to a "clean" checkpoint and running through all of the steps again, until the second app package is copied to your output folder. This process continues until all apps included in your list are done. After the last app, the VM is reverted back to a "clean" checkpoint and turned off. -### Sequence multiple apps by using the App-V Sequencer interface - -Sequencing multipe apps at the same time requires that you create a **ConfigFIle** to collect all of the info related to each round of sequencing. This file is then used by the App-V Sequencer interface after creating a "clean" checkpoint on your VM. - -#### Create your ConfigFile for use by the App-V Sequencer interface - -1. Determine the apps that need to be included in your App-V sequencing package, and then open a text editor, such as Notepad. - -2. Add the following required XML info for each app: - - - ``````. The name of the app you're adding to the package. - - ``````. The file path to the folder with the app installer. - - ``````. The file name for the app executable. This will typically be an .exe or .msi file. - - ``````. The maximum amount of time, in minutes, that the cmdlet should wait for sequencing to complete. You can enter a different value for each app, based on the size and complexity of the app itself. - - ``````. Determines whether the sequencer uses the cmdlet or the App-V Sequencer interface. **True** tells the sequencer to usea cmdlet-based sequencing, while **False** tells the sequencer to use the App-V Sequencer interface. You can use both the cmdlet and the interface together in the same ConfigFile, for different apps. - - ``````. Indicates whether the app should be sequenced. **True** includes the app, while **False** ignores it. You can include as many apps as you want in the batch file, but optionally enable only a few of them. - - **Example:** - - ```XML - - - - Skype for Windows - D:\Install\New\SkypeforWindows - SkypeSetup.exe - 20 - False - True - - - Power BI - D:\Install\New\MicrosoftPowerBI - PBIDesktop.msi - 20 - False - True - - - - ``` - -#### How to start the App-V Sequencer interface and app installation process - -Open PowerShell as an admin on the Host computer and run the following commands to start the batch sequencing: - -```PowerShell -New-BatchAppVSequencerPackages –ConfigFile –VMName -OutputPath -``` - -Where `````` is the name of the virtual machine (VM) with the App-V Sequencer installed, where you'll run the batch sequencing, and `````` is the full path to where the sequenced packages should be copied. - -The cmdlet creates a "clean" checkpoint on the VM. Next, the cmdlet copies the first app installer listed in the ConfigFile from the Host computer to the VM, and finally a new session of the VM opens (through VMConnect) and sequencing of the app begins from the command-line. After completing sequencing and package creation for the first app on the VM, the package is copied from the VM to the Host computer, specified in the OutputPath parameter. The cmdlet then goes to the second app on your list, reverting the VM back to a "clean" checkpoint and running through all of the steps again, until the second app package is copied to your output folder. This process continues until all apps included in your list are done. After the last app, the VM is reverted back to a "clean" checkpoint and turned off. - ### Review the log files There are 3 types of log files that occur when you sequence multiple apps at the same time: @@ -155,4 +101,4 @@ There are 3 types of log files that occur when you sequence multiple apps at the ## Have a suggestion for App-V? -Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization). \ No newline at end of file +Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization). From 4d4fd301f6797a16064a6630080de90f4575f57c Mon Sep 17 00:00:00 2001 From: Jeanie Decker Date: Mon, 16 Jul 2018 14:48:44 +0000 Subject: [PATCH 4/4] Merged PR 9822: Add filename clarification (issue 1278) --- windows/configuration/wcd/wcd-start.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/windows/configuration/wcd/wcd-start.md b/windows/configuration/wcd/wcd-start.md index 186c30961e..904711ae31 100644 --- a/windows/configuration/wcd/wcd-start.md +++ b/windows/configuration/wcd/wcd-start.md @@ -27,7 +27,10 @@ Use Start settings to apply a customized Start screen to devices. ## StartLayout -Use StartLayout to select the LayoutModification.xml file that applies a customized Start screen to a device. +Use StartLayout to select the `LayoutModification.xml` file that applies a customized Start screen to a mobile device. + +>[!NOTE] +>The XML file that defines the Start layout for Windows 10 Mobile must be named `LayoutModification.xml`. For more information, see [Start layout XML for mobile editions of Windows 10 ](../mobile-devices/lockdown-xml.md)).