From a4da066fcc375e71d7ade416765358ef2301f283 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Tue, 31 Jan 2017 09:46:35 -0800 Subject: [PATCH 01/76] Adding content --- windows/manage/TOC.md | 3 +- windows/manage/appv-about-appv.md | 23 ++++------ ...release-notes-for-appv-for-windows-1703.md | 37 +++++++++++++++ ...appv-release-notes-for-appv-for-windows.md | 43 +++++++----------- windows/manage/images/button.png | Bin 0 -> 9267 bytes 5 files changed, 63 insertions(+), 43 deletions(-) create mode 100644 windows/manage/appv-release-notes-for-appv-for-windows-1703.md create mode 100644 windows/manage/images/button.png diff --git a/windows/manage/TOC.md b/windows/manage/TOC.md index d68415cde7..49893c6821 100644 --- a/windows/manage/TOC.md +++ b/windows/manage/TOC.md @@ -72,7 +72,8 @@ ## [Application Virtualization (App-V) for Windows](appv-for-windows.md) ### [Getting Started with App-V](appv-getting-started.md) #### [What's new in App-V](appv-about-appv.md) -##### [Release Notes for App-V](appv-release-notes-for-appv-for-windows.md) +##### [Release Notes for App-V for Windows 10, version 1607](appv-release-notes-for-appv-for-windows.md) +##### [Release Notes for App-V for Windows 10, version 1703](appv-release-notes-for-appv-for-windows-1703.md) #### [Evaluating App-V](appv-evaluating-appv.md) #### [High Level Architecture for App-V](appv-high-level-architecture.md) ### [Planning for App-V](appv-planning-for-appv.md) diff --git a/windows/manage/appv-about-appv.md b/windows/manage/appv-about-appv.md index ef43aeed3d..56ab6132fc 100644 --- a/windows/manage/appv-about-appv.md +++ b/windows/manage/appv-about-appv.md @@ -1,7 +1,7 @@ --- title: What's new in App-V for Windows 10 (Windows 10) description: Information about what's new in App-V for Windows 10. -author: MaggiePucciEvans +author: eross-msft ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library @@ -12,15 +12,13 @@ ms.prod: w10 # What's new in App-V **Applies to** -- Windows 10, version 1607 +- Windows 10, version 1607 and later Microsoft Application Virtualization (App-V) enables organizations to deliver Win32 applications to users as virtual applications. Virtual applications are installed on centrally managed servers and delivered to users as a service – in real time and on as as-needed basis. Users launch virtual applications from familiar access points and interact with them as if they were installed locally. Application Virtualization (App-V) for Windows 10, version 1607, includes these new features and capabilities compared to App-V 5.1. See [App-V release notes](appv-release-notes-for-appv-for-windows.md) for more information about the App-V for Windows 10, version 1607 release. - ## App-V is now a feature in Windows 10 - With Windows 10, version 1607 and later releases, Application Virtualization (App-V) is included with [Windows 10 for Enterprise and Windows 10 for Education](https://www.microsoft.com/en-us/WindowsForBusiness/windows-product-home) and is no longer part of the Microsoft Desktop Optimization Pack. For information about earlier versions of App-V, see [MDOP Information Experience](https://technet.microsoft.com/itpro/mdop/index). @@ -29,26 +27,21 @@ The changes in App-V for Windows 10, version 1607 impact already existing implem - 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. -- 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). 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). 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. ->**Note**
If you're already using App-V 5.x, you don't need to re-deploy the App-V server components as they haven't changed since App-V 5.0 was released. + >[!NOTE] + >If you're already using App-V 5.x, you don't need to re-deploy the App-V server components as they haven't changed since App-V 5.0 was released. 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](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](appv-migrating-to-appv-from-a-previous-version.md). ->**Important** -You can upgrade your existing App-V installation to Windows 10, version 1607 from App-V versions 5.0 SP2 and higher only. If you are using a previous version of App-V, you’ll need to upgrade from that version to App-V 5.0 SP2 before you upgrade to Windows 10, version 1607. - +>[!IMPORTANT] +>You can upgrade your existing App-V installation to Windows 10, version 1607 from App-V versions 5.0 SP2 and higher only. If you are using a previous version of App-V, you’ll need to upgrade from that version to App-V 5.0 SP2 before you upgrade to Windows 10, version 1607.   ## Support for System Center - App-V supports System Center 2016 and System Center 2012 R2 Configuration Manager SP1. See [Planning for App-V Integration with Configuration Manager](https://technet.microsoft.com/library/jj822982.aspx) for information about integrating your App-V environment with Configuration Manager. - ## Have a suggestion for App-V? - Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). ## Related topics - - -[Release Notes for App-V](appv-release-notes-for-appv-for-windows.md) +- [Release Notes for App-V](appv-release-notes-for-appv-for-windows.md) diff --git a/windows/manage/appv-release-notes-for-appv-for-windows-1703.md b/windows/manage/appv-release-notes-for-appv-for-windows-1703.md new file mode 100644 index 0000000000..5201bc07ec --- /dev/null +++ b/windows/manage/appv-release-notes-for-appv-for-windows-1703.md @@ -0,0 +1,37 @@ +--- +title: Release Notes for App-V for Windows 10, version 1703 (Windows 10) +description: A list of known issues and workarounds for App-V running on Windows 10, version 1703. +author: eross-msft +ms.pagetype: mdop, appcompat, virtualization +ms.mktglfcycl: deploy +ms.sitesec: library +ms.prod: w10 +--- + + +# Release Notes for App-V for Windows 10, version 1703 + +**Applies to** +- Windows 10, version 1703 + +The following are known issues and workarounds for Application Virtualization (App-V) running on Windows 10, version 1703. + +Deletion of files and registry values is persisted during package updates +Custom shortcuts and FTA(?) are also saved after package updates +Fixed Connection Group issue that affected App-V Server +Reduced the number of App-V Sequencer environment checks. Narrowed down the list of required programs that should be disabled or turned off for a clean sequencing experience. Antivirus and other program warnings now are suppressed during the sequencer environment check. + +Additional info (not clear on whether we need this or where it would go in the existing structure, it’s from the last TAP release document) + +## Related resources list +For information that can help with troubleshooting App-V for Windows 10, see: +- [Application Virtualization (App-V): List of Microsoft Support Knowledge Base Articles](http://social.technet.microsoft.com/wiki/contents/articles/14272.app-v-v5-x-list-of-microsoft-support-knowledge-base-articles.aspx) +- [The Official Microsoft App-V Team Blog](https://blogs.technet.microsoft.com/appv/) +- [Technical Reference for App-V](https://technet.microsoft.com/itpro/windows/manage/appv-technical-reference) +- [App-V TechNet Forum](https://social.technet.microsoft.com/forums/en-us/home?forum=mdopappv) + +## Have a suggestion for App-V? +Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). + +## Related topics +- [What's new in App-V for Windows 10](appv-about-appv.md) diff --git a/windows/manage/appv-release-notes-for-appv-for-windows.md b/windows/manage/appv-release-notes-for-appv-for-windows.md index 0982031249..df98569910 100644 --- a/windows/manage/appv-release-notes-for-appv-for-windows.md +++ b/windows/manage/appv-release-notes-for-appv-for-windows.md @@ -1,23 +1,21 @@ --- -title: Release Notes for App-V (Windows 10) -description: Release Notes for App-V -author: MaggiePucciEvans +title: Release Notes for App-V for Windows 10, version 1607 (Windows 10) +description: A list of known issues and workarounds for App-V running on Windows 10, version 1607. +author: eross-msft ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 --- - # Release Notes for App-V for Windows 10, version 1607 **Applies to** - Windows 10, version 1607 -The following are known issues in Application Virtualization (App-V) for Windows 10, version 1607. +The following are known issues and workarounds for Application Virtualization (App-V) running on Windows 10, version 1607. ## Windows Installer packages (.msi files) generated by the App-V sequencer (version 5.1 and earlier) fail to install on computers with the in-box App-V client - MSI packages that were generated using an App-V sequencer from previous versions of App-V (App-V versions 5.1 and earlier) include a check to validate that the App-V client is installed on client devices before allowing the MSI package to install. Now that the App-V client is installed automatically when you upgrade user devices to Windows 10, version 1607, the pre-requisite check fails and causes the MSI to fail. **Workaround**: @@ -45,13 +43,11 @@ MSI packages that were generated using an App-V sequencer from previous versions where the path is to the new directory (**C:\MyMsiTools\ for this example**). ## Error occurs during publishing refresh between App-V 5.0 SP3 Management Server and App-V Client on Windows 10 - An error is generated during publishing refresh when synchronizing packages from the App-V 5.0 SP3 management server to an App-V client on Windows 10. This error occurs because the App-V 5.0 SP3 server does not understand the Windows 10 operating system that is specified in the publishing URL. The issue is fixed for App-V publishing server, but is not backported to versions of App-V 5.0 SP3 or earlier. **Workaround**: Upgrade the App-V 5.0 Management server to the App-V Management server for Windows 10 Clients. ## Custom configurations do not get applied for packages that will be published globally if they are set using the App-V Server - If you assign a package to an AD group that contains machine accounts and apply a custom configuration to that group using the App-V Server, the custom configuration will not be applied to those machines. The App-V Client will publish packages assigned to a machine account globally. However, it stores custom configuration files per user in each user’s profile. Globally published packages will not have access to this custom configuration. **Workaround**: Do one of the following: @@ -95,7 +91,6 @@ On the Packages page of the Management Console, if you click **Add or Upgrade** 3. Paste the path into the **Add Package** dialog box input field ## Upgrading App-V Management Server to 5.1 sometimes fails with the message “A database error occurred” - If you install the App-V 5.0 SP1 Management Server, and then try to upgrade to App-V Server when multiple connection groups are configured and enabled, the following error is displayed: “A database error occurred. Reason: 'Invalid column name 'PackageOptional'. Invalid column name 'VersionOptional'.” **Workaround**: Run this command on your SQL database: @@ -105,14 +100,11 @@ If you install the App-V 5.0 SP1 Management Server, and then try to upgrade to A where “AppVManagement” is the name of the database. ## Users cannot open a package in a user-published connection group if you add or remove an optional package - In environments that are running the RDS Client or that have multiple concurrent users per computer, logged-in users cannot open applications in packages that are in a user-published connection group if an optional package is added to or removed from the connection group. **Workaround**: Have users log out and then log back in. ## Error message is erroneously displayed when the connection group is published only to the user - - When you run Repair-AppvClientConnectionGroup, the following error is displayed, even when the connection group is published only to the user: “Internal App-V Integration error: Package not integrated for the user. Please ensure that the package is added to the machine and published to the user.” **Workaround**: Do one of the following: @@ -132,40 +124,37 @@ When you run Repair-AppvClientConnectionGroup, the following error is displayed, 3. If the package is currently published, run **Repair-AppvClientPackage** on that package. ## Icons not displayed properly in Sequencer - Icons in the Shortcuts and File Type Associations tab are not displayed correctly when modifying a package in the App-V Sequencer. This problem occurs when the size of the icons are not 16x16 or 32x32. **Workaround**: Only use icons that are 16x16 or 32x32. ## InsertVersionInfo.sql script no longer required for the Management Database - - The InsertVersionInfo.sql script is not required for versions of the App-V management database later than App-V 5.0 SP3. The Permissions.sql script should be updated according to **Step 2** in [KB article 3031340](https://support.microsoft.com/kb/3031340). -**Important**   -**Step 1** is not required for versions of App-V later than App-V 5.0 SP3. - +>[!IMPORTANT]  +>**Step 1** of the KB article listed above isn't required for versions of App-V later than App-V 5.0 SP3. ## Microsoft Visual Studio 2012 not supported +App-V doesn't support Visual Studio 2012. - -App-V does not support Visual Studio 2012. - -**Workaround**: None +**Workaround**: Use a newer version of Microsoft Visual Studio. ## Application filename restrictions for App-V Sequencer - - The App-V Sequencer cannot sequence applications with filenames matching "CO_<x>" where x is any numeral. Error 0x8007139F will be generated. **Workaround**: Use a different filename -## Have a suggestion for App-V? +## Related resources list +For information that can help with troubleshooting App-V for Windows 10, see: +- [Application Virtualization (App-V): List of Microsoft Support Knowledge Base Articles](http://social.technet.microsoft.com/wiki/contents/articles/14272.app-v-v5-x-list-of-microsoft-support-knowledge-base-articles.aspx) +- [The Official Microsoft App-V Team Blog](https://blogs.technet.microsoft.com/appv/) +- [Technical Reference for App-V](https://technet.microsoft.com/itpro/windows/manage/appv-technical-reference) +- [App-V TechNet Forum](https://social.technet.microsoft.com/forums/en-us/home?forum=mdopappv) +## Have a suggestion for App-V? Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). -## Related topics +![https://github.com/Microsoft/windows-itpro-docs/blob/master/CONTRIBUTING.md](images/button.png) -[What's new in App-V for Windows 10](appv-about-appv.md) diff --git a/windows/manage/images/button.png b/windows/manage/images/button.png new file mode 100644 index 0000000000000000000000000000000000000000..1ba7590f76664f4e40ca0745ed2633465069ddf6 GIT binary patch literal 9267 zcmV-3B+T21P)Px#1ZP1_K>z@;j|==^1poj532;bRa{vGi!vFvd!vV){sAK>D02y>eSaefwW^{L9 za%BK;VQFr3E^cLXAT%y8E-^DS16z6k03)MGL_t(|UVWPhbX8@x=WlW^1Xm}nhTQm; zNnF}%^;*5auGS1Ut+?QegJ)YsSl$HE)qBZ@Px zE6yw$nF&#NTjq76L^D%3l3T&JZj?qcef{WwaJtBt6Z6nTKgNSj2;ChyxZr;bzHa2; z!e0y?{)@o{zYy(&=0^=F9H{{@qIk&g+l(&ON2i%A3VE&{9T3ShccGmbI#6<(G)Vbv z`Y0tZ8yyH5&-EcQcbyqRLl%SRe0W?w18xG)pmQ)CMyIbUju-yoKm8={)mLAQJpTCO z*H4)neeCtrC%#CnJ(f~;ET#HL%9CHF)Ew1d=BfXaQq`@=rJtof@nvdxS8DB15lx?_ zRvk&L>P~&?&#CptHCfS>`t+YuYmSI!JolCE)*Vf4JTCr9=wqo3$5QK#q%Qqb^9{$v z-1M2Q%Rf)8W&ZQjYObH9Rvk`V#!R=YFfZEl)E^55dJy+pe1r`p&{*UOjjEcXsVlw+ zXiUQsT#uyIn|1Uz91T2_#m}TradnAi2DGETeG`B2 zY<%_Ec=MU~nv?O(XW}bQ$5)?;uRoi$>2%h!C$pN*WNrE`YyIi0)u*#ooy>aiT-KU1 z8qc1{dg*M|YNMM^$2XrE^2|4b*PI^Qe0uPjQ-hy7F{JtQkmfT()|?r#`s9$6Cx*1> z<7Ml=yKMED%Ql_4Y>jA%zi=jN<;g7Q=Ckn)-^N#+jITQvUvoOX{@eH(Tsj+XITc@P z1YT`CBZph?@Kk)`x%jhRXRX19Q(2qO$v5cclUXl7eQB$nOg@pb^Yhv-xqG}8@{uzU|V0oAA5A& z)mO0ne8HQ&(D_^X@^|&-@9xdt+L!-EU;aBi`8&_&`~2HIy6)`bR>5061+9JgJNoil zd-MO;lMk(1z4?24^0xG8KD@i~ThHfh>&t8H%iGhF_uBb9 zn3)H_*1qAp`+o9=|Cdp^C34&Rl!CFvcTNa#pE4&pttB#h>wwY^{$az3yf^-K-8(%+ zt$js1`ige-7QJiq&c4E3K;I)jwlmP!tCT1)(C0FXl1w?#|#$Ce(swDH*G>%PryK9#-UWcKQl*&Dyh zZa$H{{$%#rZ?jvz&0h0W_S#d~FswP7{rrjS7H+|CI{W#P+0T8Iz2W=pW<*Zv`uz9V ztG|(wHD|Kdoy%_K?#b+yvl{D9=B)iDckQ{{mb1B=Pvy3Jle^*j+%>0iH=oRHIhDKN zui4LiEsLx10fpaWZ#h-{frgE~n*m&c+itYfk2D_&#U# z$(+q6a^yT-;lqiXb!V=4@vm2`Ieo?26IX0Hcg5!KuUK>PinXV%c=7uyHhi1Cfe=nf z+sYFPXU$0oVi$|6zRBKXN;aIzS$isH)4810U+1hpm9zfa+_h(Oo4?9kdphU&zh*a| z$=-xu5)P}r%HH@_gAQ*`rPp;t?*Dz{H|rvIl%y2hRXjF<`_#Fr_gSscB_G6=9~)5m z$-ugfw3^Pe6`!V6x2M&1rZpT%Tk%<1bw^rNd)m@tY0Hj@u53$t`d@U*=b!!}t-4cE z4CtzkwAzley2EKteI7709Zh@Ua}f-*H69&U)jqJQW8f2?53K7NSkp1Ex^v)DUkt42 zgq8@(Q36rlo%YPX$Q(4Lmmg27Y!{7tjYnh!`l&Bu3qfu@^JU;kZ5M)rsyi-eIDARN zkxQQV{E|AOmmb%s@4BR>T`r*nLltdl&wZIz*Cj#3QG%but`NRJ$)MVfK@CR+t@w0M zO~;_B_Cd=&9klHDAWUG9cySUQZaociC-b`Xjqv#cDfa)$OsWHeG8vbql)waIC65 zR@W7)Y>PDJUTup;!YJ+hSw#B9UvO z^Sfi^2c?i1?!xJ``-3)=Ad4GJ;wm%T!eOktAl4<~GvJk_DQsSf64=Yh)i#Z+_5<2x@6p^&J*r4 zw?s?-1X$ocp#JcH`mOV|H~XT~G?m;iX3hR2-6$n)YA@8VwAzA);Fr0&GhWG&aPcQRPtw z*KXrK9Jq}G?u@J)k$%Sk8ddmU*BH2$yqEIOtC9QGslOMEORjftU(3E4UA#ZG+#Gc* zFrWZXXG(F@W9I7SamCFW;-0X6+=G~nQx(@59Whb3OWe>zp>7=x9HnsXpx*PM3vk+F zZj%YDTFA$F(aUfH@ z8}9S1-cjgbRD*&kfuH4tMaBiVTS|x%f2aUC4{hS8l@FFS$Ed-KGNk!J+|7p|_I_24 zyRW$);O;4L_rge3e=wU}!+oD{pRrbbrtkvXt-sH1jV^vahFe-+R^zV7Z97JQ#no+l zeen_7ir*Yf^qJyT2?Eoyqk@$#S-C~^K4QN0_f=6bCH^KvRo6*x<^_5X0{Jlb|hLDNZMasbZ*#Z3^LnMlKw!yetY!F;8XB-{i*;5 zt`uCd0|5?UpFu70;zO`Zj|lfA`%)f$-Rk`!+}T%ydVh}%!CIu135pQ*PA5y?ZY7q; zvnM8T^_YV`(;6TSr}frY+3V4w3DFS?VsjT*Gz+tXI zz301?*vxrmg4_o#i8_FzP#{nN;wzaPQUba8w!BcDW&jskRHz0=xEr3R>jEyf)*z|XBH;64-FDS(vn>}C3i=I>61u=K`*E?=2 z_uWCg&-BJ+jRJA_@!500z+tY*_1?JJQn*@>VG&i0w%hvx{b{q|K+e2kkPYjdmHh)8 zf_evc&XJG2p?V*)FeM+{6VFZRGwal67VqOEn}oY55^YM|7=t`x-fwv%LCm(V2DooY z*me<}BSGh))|vcQ^juKyoM(835O&~hfw4t%MF|^&k_YZqZrE)~!rf!0%G4Z$dw(71 zZ=%*j0(UQ+TCaD*eZk}667KA)VZG~gzbeRwaIkzMsGw}!z)XcX?yB*m4H-1Ry=-5~ zL$61suMzIUlX2I1hCZ`3TC$I0f6!-S+l0-wW+-zACb7*>t+Ah&d1&<+9sc@p$8}eN zl*-D_?|BhzgX~n+vIJJx&DeYWJVS2{`%HAI#rfo?rX;D}kyX9p&xQLcKG5;Cm(ng0 z=l8?0n&*5c4-|UZ1Xh=B1%1ZqeZ;B&N(+b6RBXQI!*Af01oRtILRPrYaRG($p#&7#!;#AgmDE{tfQZg zvJ&E;10nmWfkslny<)%4Gt-(??*(^^89QO)#*K!%&XMcvxoKZ)nWanRY>E(ea1(hB z3|rVNe|I9NcdIPN-Je%A@AXc2;q&S&i{FnW7Juw9J4KAz67H+SoOF()x(S1XcFfc z%f0SeyOR&X!FL5)XL8;K5aAvKR*2VfuXO+q_0D-_(L1X5X=}XR$Bdhpz@6t++gF$D z56+Q7+)5Z+w69u$ySvbG+TgY#RZ6&qg8hBQb58!1HuhDkcYAIMOET&2s)c&dk@VaY zY>5~Bjoumri~}AgK2&$arcMkP`u{kmcErYBsD!6E5J7_-ZFMCI#FNjg?5@Fw@Ndj^ zSzKymO#YPYO~=!CaK+T5}m>~ov5tlaWRJP{Czzhr?0yOpRh2`L) z#KjTexrBMdvBj;R^2}9eaPUUWaw-2fb;)}v4_UqIJd=z&=l5yrBeU37_s7tVJ+upP z6LzZt*S10TTej^j1hgk9AqbBuJpm$0=%;qz)zY!;0c~yq+5y6fm_0Uid@ohCa;nm| z3XD2ra6+Smt1JdpuUq&4GYn(}{dmZXGR;GPy{mC(kj0i4f%^vA3OhA1gSZ3_N@2o7 zj~W^Vb~0`;gDg3~qN_p>9Izrmg=6*pmg@bt8-#n_=%ha5^*(32a7P!1Zb#gGT5iSS zG2<~blU{mgSFzX;i1=+^6@$Br>v(_?$H)~@nB0ZHEtCKUGqB+fq9jS?8hgnNZJh8Uhg6ymn~ znT&(dW9~tdFjvCCx9pSDCGV=icCCK@~t~5mEnGvAIFWO>o)Rb47giTiL3S?ZVckA!L`Q3q&58fF} zmXF+0GE9kF^*zRzea7nmbMnFX^@7C$@oHsKbRs#AVR(K%;9Jt=$T_42D0l)L}j!_v$k!3HywSln_i1Rd8a+ zY1i+mWsq+^G8r(~qC^SECOVAwSl6TX;kM3jhL41%tot5=72jiwv&>Q`KRbmx=Xbpq zTNk-=amsb$F5Fkaoqg56_b59MID{gsDrWDkxM+Gk=Q!svd*OJ@eo#rQ?jR)Zt>G(d z1~H=tg^XZJ2n&b1iYkm8K!e#^UHxGXD(XfSaiWeuLBDyF+i0qt59`I3qhWQDZvW1yze3C;V=Ua zB96Xi8dbu?l_Yi-6LcJ$nR6t#FS2u_eosKXkH7Hz4(jK{{L?`a;bB3JS1-GDzm@{}l_EPw!aid}fx8DIEW#^l-2nk@ zN|=P1k7$M_atWFb_@k?#%s#|j21Zc}cIXjd&ItFAxhi~RKh0EKjDwYqn^yRagT>Aw z@U(H2py6)sBU3Bv`zAUHxQ|H2ojx;TZRD{nc78vit;y5q!lK<>-&bvY;X0F4w7U+Q ziZtoK>w;Xpd|+b`7#bKj=K+h^WAh?KFf195)7gTaV*xAK2?Q;dutB318t0XJYZ2Ui z@-y?q670TtwF*0{S&xfbh}cbVtbUB_Zd@)>vGQ0i#kAecRgAwlK`w>eHojdEC~rt z?t(=Svz3g)B()YZ?SdI-#G(6Rw$+9>Aj&AQg@qQxX?u*rL7y!=^jQ19ATlk45j zk^XxE;w%r}1LL&(vyc?CZE>D$xl7E(fNf|A`uk7wAiM^zy5@8SFPM`5Mz@CVq5RL@ z%%G~FJ2vXtVD5rHeYu+SK3#tTsJbJzY}dta_D8I;mzVj`N4?&KNbpX73jY7_9nttG zD1&=Y?_oIRkCN>P^X&?PD^;RNt9?FV#iIsy$Dye^R(VkM4(>nf?>9`f=O#bDqXK&f zlR8;7+&zt+cC=#;T4fU2>&M-IlZYP=!dL1^xGU`X;Ek^RO^WIVM*cPmTCT@NhPYp~ zAV!TZKNiA0DLOfP1vYxCxz`<=mH1NBoKJiy>VKoQD3I#*Slzbhm3fh?CPr&JgLlGm zOlvOuj`!|p@GctMFT??$z3+MKg5Gck7A;n8S=B3c7c|f)po# z@%Qhm@Y%9%U#t@p;q<>o_3wDYK9h(Y9`zhs+ztgZTp3`^l_S}Y;h=i=KBM1p==YIh z#wKvrdoi9@x9E2qXfLz#dl;>9;NW79JOjNO#vaVf@X@QA=LNTopp~s~xvH}G^DUq?siadI+;PXDC94NuT2|57I|HvQNrNcD%mvF1(1J)@TXAXX~pg+BA zpr{iSfN6aLc%*`GW^iByi1t2n z!1h)9edO(nQVR8Zu@LtubE5Pae=kP81DQXkBw|Jdc_vQB2pgF6WVkDSRi2I6R~&mw zf4v_Le$z6?WE&5M-{Q}Y@sVNyYpXb64Q=(V90a+S3HzRNV$hWR>x=5P*y9WJQD4px zv#oKM!QH>4zRIfp`qi;&fBSDg)(Do`kNqXS&@5Q`X+W|mHwra(;8wO=77GpDe5>%dp zYk$3W1-Q>P4Xo=#y&FuLN#Gv#cdK_xs;&3foc)ml@N%q%!xUUvI8~UII9h@|Z3_s52+p6{#Ng61IZf)r30xZA$! zeWvKH(RU`-`;2vw`8#!=jt9_IuwuqJuDWaAvI}=_ zFTSr@y(8X_dsy#3iaUS)Ej|JGwmf2GY)S(6V9kYJ*m4Z@A`Qtv2EfGbh16>9dYk7B#e0k8*~7;a9_=j&N6NE z_Y3w_#TMdjC?s%C{xhtDuTr(InhzGOc2{HR{~NPik@NUn5gy4oq7alf3XYN&|3)(s z`40>A<0^l#apx|j&{tbxN9Bq*@lt&K`>M5mhXsqatLwEIG&R9Fvh+Rs{reC5JAH=P zxjVvhB+pHjZGRMGk7eHz=+?h5fH$}zBJ40+S%7|)fXBO@1X(UrhwaJGYKXpW%w0iX z?sAJ2=20=fEI3Do`>I!*m#V#HLEL4D&|_vsbogFOd#rha2v?_JV|cAFAdq54A%x5b zI&dhVjGPu*XZV`a9F{pNLD+E2-Np)P!2v;Hx3md&og=N@f4t8)?p}QoGj~y~zznHM za}gUDb9Z6$ThMlTkx$r8xE|2qQCIO3vjtBMAf(?WRV<+(r+aG@>Ny@{5VM(P1{%94 z;p&2}nY-L_X68|@K>S^WbzUj4BJjJ2NJ*Hs<;VLyL5YAfCsFPSVS}H$L`0If>q=k_ zlsFE?tkv)5$bJ34OD(!9>HkrBpP6gt$fY#Iwt-8Jq*WbCTiTsgaWJi>J*~Dat)VNe z@}Ne2M_OG+TIC^)Wk=F#+QcckJFWac@KJ&X^natO+R~bwJ|wB8u7GarN~>*`6wFPB zrM6#C7K8KquMdiivAjF24CU=<^_^*ToibG2CMB3)5^@S>0^ycMhumxEl&V^bXoZ;N30IVqeWF_^S=v3Ys%>DCT~WfQ>l|3yA)Pp* z*pG@+IJost30P@81i@CE?EbeX6~GU-Ch$zUz|mkJB3uWt8sAsQgn# z#RnM;2LrnLLk(yqYd+FU)rT47A7s>itZVg0871#$)E~$w+h_CpGnz~g8qV5}0wsL( z8AK}nlu@={BG5Iaqz>`@sQP!e{RG@&_n2B{FejdmBvQIRqY_U(!kP4{kJ2kYOfTD? z-f%Fz>cjMk57U?IPj6~Vhq?X}SB1CfjR(_9_opw}myVUj1MDmU0Cn-UM#kRkUq#Gc4wBpCGq-wnTz&H2_GxpVJ2SowxrO8pi41o-qR$8m`~8Cg60a% zs151zw=@>*4y@x6gfnv&`tjZIx_$AIJ;5ym7w*fQnEL*{Ov(Ax7ayS?`M+heQxUX zbtwyWX3Tv({>bLc2cFNI{YvJ8n=&8Xl=;vLnR8yz%tM7Z;sFV zeSGFC@yA{X=to|T&-$I1@%f=m@j0&ydEohh)0^%01WEON!?gLSQ<~GJK7Hw3i!**% zmN9No1_al;OEbnT6g|EqV^Zm*;}&a7D!cUV@=M2+i2haOr4!38y$iYoI^(Vqal-$P z?I z1mlE85CZ0Lgn*zaK~P>9Ch`_P4ICUsj|={?JP2H%xfMP#Z(xou0iyI@Rz!>EMuv|a zbJrx{K6mciYwvzA>$lB0Qrzdi!E)_9jxyIDS+-Xg@zgeC;y(x!*(cdhS z!}vL+KIgY9WO^E&G-!Tuo#?3zcGu>iVP?SWY<`{5lyh&b?jnNPd!U)G%l++&+$jyY zlN)lUFAeB>>vHc~t}&%P7Z2}$Qn#4rc<7CzG=4TFAeg!J_Mta9Jz6|BzzoA^eY|nhu$zmA{rvW! zw~QWkQ!(S}pWlARU$##Lc4+yxNpN554KOpWgD{-hTV-{|`=f V?!+3XuG0Vj002ovPDHLkV1ipwlxF|{ literal 0 HcmV?d00001 From 402c816120bca0e6abd271f1fa009a8925dce611 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Tue, 31 Jan 2017 12:26:42 -0800 Subject: [PATCH 02/76] Adding content --- windows/manage/TOC.md | 3 +- .../appv-automatic-sequence-a-new-app.md | 50 ++++++++ ...appv-release-notes-for-appv-for-windows.md | 2 +- .../manage/appv-sequence-a-new-application.md | 109 ++++++++---------- 4 files changed, 103 insertions(+), 61 deletions(-) create mode 100644 windows/manage/appv-automatic-sequence-a-new-app.md diff --git a/windows/manage/TOC.md b/windows/manage/TOC.md index 49893c6821..0144c9280b 100644 --- a/windows/manage/TOC.md +++ b/windows/manage/TOC.md @@ -110,7 +110,8 @@ #### [Deploying Microsoft Office 2010 by Using App-V](appv-deploying-microsoft-office-2010-wth-appv.md) ### [Operations for App-V](appv-operations.md) #### [Creating and Managing App-V Virtualized Applications](appv-creating-and-managing-virtualized-applications.md) -##### [How to Sequence a New Application with App-V](appv-sequence-a-new-application.md) +##### [Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) +##### [Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-automatic-sequence-a-new-app.md) ##### [How to Modify an Existing Virtual Application Package](appv-modify-an-existing-virtual-application-package.md) ##### [How to Create and Use a Project Template](appv-create-and-use-a-project-template.md) ##### [How to Create a Package Accelerator](appv-create-a-package-accelerator.md) diff --git a/windows/manage/appv-automatic-sequence-a-new-app.md b/windows/manage/appv-automatic-sequence-a-new-app.md new file mode 100644 index 0000000000..e61f400e79 --- /dev/null +++ b/windows/manage/appv-automatic-sequence-a-new-app.md @@ -0,0 +1,50 @@ +--- +title: Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10) +description: How to automatically sequence a new app using the App-V Sequencer +author: eross-msft +ms.pagetype: mdop, appcompat, virtualization +ms.mktglfcycl: deploy +ms.sitesec: library +ms.prod: w10 +--- + + +# Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) + +**Applies to** +- Windows 10, version 1703 + +>[NOTE] +>In Windows 10, version 1703, the App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md). + +With the previous versions of the App-V Sequencer, you've had to manually sequence your app packages. This was time-consuming and required extensive interaction, causing many companies to deploy brand-new packages rather than update an existing one. Windows 10, version 1703 has introduced an updated App-V Sequencer that can automatically sequence your app packages, improving your overall experience by streamlining the provisioning of the prerequisite environment, automating app installation, and expediting the package updating setup. + +Using the automatic sequence to package your apps provides: + +- Automatic virtual machine (VM) provisioning of the sequencing environment. + +- Batch-sequencing of packages. This means that multiple apps can be sequenced at the same time, in a single group. + +- Batch-updating of packages. This means that multiple apps can be updated at the same time, in a single group. + +## Provision your VM +You have 2 options for provisioning an VM for auto-sequencing: +- Provision a new VM by using a Virtual Hard Disk (VHD) + + -OR- + +- Provision an existing VM + +### Provision a new VM for auto-sequencing by using a VHD file +The tasks of setting up user account, enabling auto-login, enabling remote PowerShell scripting, installing the App-V Sequencer, etc., will be covered by this OS provisioning stage. This stage is premised on a base OS being available in the form of VHD image + +### Provision an existing VM for auto-sequencing + + + +## Have a suggestion for App-V? +Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). + +## Related topics +- [Install the App-V Sequencer](appv-install-the-sequencer.md) +- [Operations for App-V](appv-operations.md) diff --git a/windows/manage/appv-release-notes-for-appv-for-windows.md b/windows/manage/appv-release-notes-for-appv-for-windows.md index df98569910..290e4b19b9 100644 --- a/windows/manage/appv-release-notes-for-appv-for-windows.md +++ b/windows/manage/appv-release-notes-for-appv-for-windows.md @@ -156,5 +156,5 @@ For information that can help with troubleshooting App-V for Windows 10, see: ## Have a suggestion for App-V? Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). -![https://github.com/Microsoft/windows-itpro-docs/blob/master/CONTRIBUTING.md](images/button.png) +Help us to improve diff --git a/windows/manage/appv-sequence-a-new-application.md b/windows/manage/appv-sequence-a-new-application.md index 24b1fb9ba1..7479636bf9 100644 --- a/windows/manage/appv-sequence-a-new-application.md +++ b/windows/manage/appv-sequence-a-new-application.md @@ -1,7 +1,7 @@ --- -title: How to Sequence a New Application with App-V (Windows 10) -description: How to Sequence a New Application with App-V -author: MaggiePucciEvans +title: Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10) +description: How to manually sequence a new app using the App-V Sequencer +author: eross-msft ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library @@ -9,10 +9,10 @@ ms.prod: w10 --- -# How to Sequence a New Application with App-V +# Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) **Applies to** -- Windows 10, version 1607 +- Windows 10, version 1607 and later In Windows 10, version 1607, the App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md). @@ -36,8 +36,8 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD - If short paths have been disabled for the virtualized package’s target volume, you must also sequence the package to a volume that was created and still has short-paths disabled. It cannot be the system volume. -> [!NOTE] -> The App-V Sequencer cannot sequence applications with filenames matching "CO_<_x_>" where x is any numeral. Error 0x8007139F will be generated. +>[!NOTE] +>The App-V Sequencer cannot sequence applications with filenames matching "CO_<_x_>" where x is any numeral. Error 0x8007139F will be generated. **To sequence a new standard application** @@ -47,15 +47,15 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD 3. On the **Prepare Computer** page, review the issues that could cause the package creation to fail or could cause the package to contain unnecessary data. You should resolve all potential issues before you continue. After making any corrections, click **Refresh** to display the updated information. After you have resolved all potential issues, click **Next**. - > [!IMPORTANT] - > If you are required to disable virus scanning software, you should first scan the computer that runs the sequencer in order to ensure that no unwanted or malicious files could be added to the package. + >[!IMPORTANT] + >If you are required to disable virus scanning software, you should first scan the computer that runs the sequencer in order to ensure that no unwanted or malicious files could be added to the package. 4. On the **Type of Application** page, click the **Standard Application (default)** check box, and then click **Next**. 5. On the **Select Installer** page, click **Browse** and specify the installation file for the application. - > [!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. + >[!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 click **Next**. @@ -65,8 +65,8 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD 7. On the **Installation** page, when the sequencer and application installer are ready you can proceed to install the application so that the sequencer can monitor the installation process. - > [!IMPORTANT] - > You should always install applications to a secure location and make sure no other users are logged on to the computer running the sequencer during monitoring. + >[!IMPORTANT] + >You should always install applications to a secure location and make sure no other users are logged on to the computer running the sequencer during monitoring. Use the application's installation process to perform the installation. If additional installation files must be run as part of the installation, click **Run** to locate and run the additional installation files. When you are finished with the installation, select **I am finished installing**. Click **Next**. @@ -74,8 +74,8 @@ 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 click **Run All**. To run specific programs, select the program or programs, and then click **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] - > 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. + >[!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. Click **Next**. @@ -91,23 +91,21 @@ 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 click **Next**. - > [!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, and then depending on how the background loading is configured, will load the rest of the application. - -   + >[!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, and then depending on how the background loading is configured, 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. Click **Next**. - > [!IMPORTANT] - > Make sure that the operating systems you specify here are supported by the application you are sequencing. + >[!IMPORTANT] + >Make sure that the operating systems you specify here are supported by the application you are sequencing. 14. The **Create Package** page is displayed. To modify the package without saving it, select **Continue to modify package without saving using the package editor**. This option opens the package in the sequencer console so that you can modify the package before it is saved. Click **Next**. To save the package immediately, select **Save the package now** (default). Add optional **Comments** to be associated with the package. Comments are useful for identifying the program version and other information about the package. - > [!IMPORTANT] - > The system does not support non-printable characters in **Comments** and **Descriptions**. + >[!IMPORTANT] + >The system does not support non-printable characters in **Comments** and **Descriptions**. The default **Save Location** is also displayed on this page. To change the default location, click **Browse** and specify the new location. Click **Create**. @@ -115,14 +113,13 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD The package is now available in the sequencer. - > [!IMPORTANT] - > After you have successfully created a virtual application package, you cannot run the virtual application package on the computer that is running the sequencer. - + >[!IMPORTANT] + >After you have successfully created a virtual application package, you cannot run the virtual application package on the computer that is running the sequencer.   **To sequence an add-on or plug-in application** -> [!NOTE] +>[!NOTE] >Before performing the following procedure, install the parent application locally on the computer that is running the sequencer. Or if you have the parent application virtualized, you can follow the steps in the add-on or plug-in workflow to unpack the parent application on the computer. >For example, if you are sequencing a plug-in for Microsoft Excel, install Microsoft Excel locally on the computer that is running the sequencer. Also install the parent application in the same directory where the application is installed on target computers. If the plug-in or add-on is going to be used with an existing virtual application package, install the application on the same virtual application drive that was used when you created the parent virtual application package. @@ -133,9 +130,8 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD 3. On the **Prepare Computer** page, review the issues that might cause the package creation to fail or could cause the package to contain unnecessary data. You should resolve all potential issues before you continue. After making any corrections, click **Refresh** to display the updated information. After you have resolved all potential issues, click **Next**. - > [!IMPORTANT] - > If you are required to disable virus scanning software, you should first scan the computer that runs the sequencer in order to ensure that no unwanted or malicious files could be added to the package. - + >[!IMPORTANT] + >If you are required to disable virus scanning software, you should first scan the computer that runs the sequencer in order to ensure that no unwanted or malicious files could be added to the package. 4. On the **Type of Application** page, select **Add-on or Plug-in**, and then click **Next**. @@ -143,17 +139,17 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD 6. On the **Install Primary** page, ensure that the primary application is installed on the computer that runs the sequencer. Alternatively, you can expand an existing package that has been saved locally on the computer that runs the sequencer. To do this, click **Expand Package**, and then select the package. After you have expanded or installed the parent program, select **I have installed the primary parent program**. - Click **Next**. +7. Click **Next**. -7. On the **Package Name** page, type a name that will be associated with the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name will be displayed in the App-V Management Console. +8. On the **Package Name** page, type a name that will be associated with the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name will be displayed in the App-V Management Console. - Click **Next**. +9. Click **Next**. -8. On the **Installation** page, when the sequencer and application installer are ready you can proceed to install the plug-in or add-in application so the sequencer can monitor the installation process. Use the application's installation process to perform the installation. If additional installation files must be run as part of the installation, click **Run** and locate and run the additional installation files. When you are finished with the installation, select **I am finished installing**, and then click **Next**. +10. On the **Installation** page, when the sequencer and application installer are ready you can proceed to install the plug-in or add-in application so the sequencer can monitor the installation process. Use the application's installation process to perform the installation. If additional installation files must be run as part of the installation, click **Run** and locate and run the additional installation files. When you are finished with the installation, select **I am finished installing**, and then click **Next**. -9. On the **Installation Report** page, you can review information about the virtual application package that you just sequenced. For a more detailed explanation about the information displayed in **Additional Information**, double-click the event. After you have reviewed the information, click **Next**. +11. On the **Installation Report** page, you can review information about the virtual application package that you just sequenced. For a more detailed explanation about the information displayed in **Additional Information**, double-click the event. After you have reviewed the information, click **Next**. -10. The **Customize** page is displayed. If you are finished installing and configuring the virtual application, select **Stop now** and skip to step 12 of this procedure. To perform either of the following customizations, select **Customize**. +12. The **Customize** page is displayed. If you are finished installing and configuring the virtual application, select **Stop now** and skip to step 12 of this procedure. To perform either of the following customizations, select **Customize**. - Optimize how the package will run across a slow or unreliable network. @@ -161,12 +157,10 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD Click **Next**. -11. 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 the applications to run. After all applications have run, close each of the applications. 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. Click **Next**. +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 the applications to run. After all applications have run, close each of the applications. 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. Click **Next**. - > [!NOTE]    - > If necessary, you can stop an application from loading during this step. In the **Application Launch** dialog box, click **Stop** and select one of the check boxes: **Stop all applications** or **Stop this application only**. - -   + >[!NOTE]    + >If necessary, you can stop an application from loading during this step. In the **Application Launch** dialog box, click **Stop** and select one of the check boxes: **Stop all applications** or **Stop this application only**. 12. 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. Click **Next**. @@ -174,8 +168,8 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD To save the package immediately, select **Save the package now**. Optionally, add a **Description** that will be associated with the package. Descriptions are useful for identifying the version and other information about the package. - > [!IMPORTANT]    - > The system does not support non-printable characters in Comments and Descriptions. + >[!IMPORTANT]    + >The system does not support non-printable characters in Comments and Descriptions. The default **Save Location** is also displayed on this page. To change the default location, click **Browse** and specify the new location. Click **Create**. @@ -187,9 +181,8 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD 3. On the **Prepare Computer** page, review the issues that could cause the package creation to fail or could cause the package to contain unnecessary data. You should resolve all potential issues before you continue. After making any corrections, click **Refresh** to display the updated information. After you have resolved all potential issues, click **Next**. - > [!IMPORTANT] - > If you are required to disable virus scanning software, you should first scan the computer that runs the App-V Sequencer in order to ensure that no unwanted or malicious files can be added to the package. - + >[!IMPORTANT] + >If you are required to disable virus scanning software, you should first scan the computer that runs the App-V Sequencer in order to ensure that no unwanted or malicious files can be added to the package. 4. On the **Type of Application** page, select **Middleware**, and then click **Next**. @@ -197,37 +190,35 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD 6. On the **Package Name** page, type a name that will be associated with the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name is displayed in the App-V Management Console. - Click **Next**. +7. Click **Next**. -7. On the **Installation** page, when the sequencer and middleware application installer are ready you can proceed to install the application so that the sequencer can monitor the installation process. Use the application's installation process to perform the installation. If additional installation files must be run as part of the installation, click **Run**, to locate and run the additional installation files. When you are finished with the installation, select the **I am finished installing** check box, and then click **Next**. +8. On the **Installation** page, when the sequencer and middleware application installer are ready you can proceed to install the application so that the sequencer can monitor the installation process. Use the application's installation process to perform the installation. If additional installation files must be run as part of the installation, click **Run**, to locate and run the additional installation files. When you are finished with the installation, select the **I am finished installing** check box, and then click **Next**. -8. On the **Installation** page, wait while the sequencer configures the virtual application package. +9. On the **Installation** page, wait while the sequencer configures the virtual application package. -9. On the **Installation Report** page, you can review information about the virtual application package that you have just sequenced. In **Additional Information**, double-click an event to obtain more detailed information. To proceed, click **Next**. +10. On the **Installation Report** page, you can review information about the virtual application package that you have just sequenced. In **Additional Information**, double-click an event to obtain more detailed information. To proceed, click **Next**. -10. On the **Target OS** page, specify the operating systems that can run this package. To enable 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 select the operating systems that can run this package. Click **Next**. +11. On the **Target OS** page, specify the operating systems that can run this package. To enable 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 select the operating systems that can run this package. Click **Next**. -11. On the **Create Package** page is displayed. To modify the package without saving it, select **Continue to modify package without saving using the package editor**. This option opens the package in the sequencer console so that you can modify the package before it is saved. Click **Next**. +12. On the **Create Package** page is displayed. To modify the package without saving it, select **Continue to modify package without saving using the package editor**. This option opens the package in the sequencer console so that you can modify the package before it is saved. Click **Next**. To save the package immediately, select **Save the package now**. Optionally, add a **Description** to be associated with the package. Descriptions are useful for identifying the program version and other information about the package. - > [!IMPORTANT]    - > The system does not support non-printable characters in Comments and Descriptions. + >[!IMPORTANT]    + >The system does not support non-printable characters in Comments and Descriptions. The default **Save Location** is also displayed on this page. To change the default location, click **Browse** and specify the new location. Click **Create**. -12. The **Completion** page is displayed. Review the information in the **Virtual Application Package Report** pane as needed, then click **Close**. This information is also available in the **Report.xml** file that is located in the directory specified in step 11 of this procedure. +13. The **Completion** page is displayed. Review the information in the **Virtual Application Package Report** pane as needed, then click **Close**. This information is also available in the **Report.xml** file that is located in the directory specified in step 11 of this procedure. The package is now available in the sequencer. To edit the package properties, click **Edit \[Package Name\]**. - > [!IMPORTANT]    - > After you have successfully created a virtual application package, you cannot run the virtual application package on the computer that is running the sequencer. + >[!IMPORTANT]    + >After you have successfully created a virtual application package, you cannot run the virtual application package on the computer that is running the sequencer. ## Have a suggestion for App-V? - Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). ## Related topics - - [Install the App-V Sequencer](appv-install-the-sequencer.md) - [Operations for App-V](appv-operations.md) From dc493e888adf82b96c2cb9a1020f6e98a43b03db Mon Sep 17 00:00:00 2001 From: LizRoss Date: Tue, 31 Jan 2017 15:06:35 -0800 Subject: [PATCH 03/76] Adding text --- .../appv-automatic-sequence-a-new-app.md | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/windows/manage/appv-automatic-sequence-a-new-app.md b/windows/manage/appv-automatic-sequence-a-new-app.md index e61f400e79..b8eaef66e8 100644 --- a/windows/manage/appv-automatic-sequence-a-new-app.md +++ b/windows/manage/appv-automatic-sequence-a-new-app.md @@ -36,7 +36,24 @@ You have 2 options for provisioning an VM for auto-sequencing: - Provision an existing VM ### Provision a new VM for auto-sequencing by using a VHD file -The tasks of setting up user account, enabling auto-login, enabling remote PowerShell scripting, installing the App-V Sequencer, etc., will be covered by this OS provisioning stage. This stage is premised on a base OS being available in the form of VHD image +Provisioning your new VM includes setting up a user account, turning on remote PowerShell scripting, and installing the App-V Sequencer. + +>[!IMPORTANT] +>For this process to work, you must have a base operating system available as a VHD image file. If you need a tool to create your VHD file, you can use the [Convert-WindowsImage.ps1](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) command-line tool. This tool is now a Function, so it must first be loaded and then called by its name, without the extension. Code examples and more info about the tool are included on the download site.

Additionally, when you run this tool to create your file, you must explicitly specify the parameter 'VHDPartitionStyle' as 'MBR'. The default partition value, 'GPT' will cause a boot failure in your VHD file. + +**On the Host device** +1. Install Windows 10, version 1703 and the matching ADK version, making sure that you've selected to install the **Microsoft Application Virtualization (App-V) Auto Sequencer** component. + +2. Make sure that Hyper-V is turned on. For more info about turning on and using Hyper-V, see [Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server) + +3. Open PowerShell as an admin and run the **New-AppVSequencerVM** cmdlet, using the required parameters: + + ``` + New-AppVSequencerVM -VMName -ADKPath -VHDPath [-VMSwitch ] [-VMMemory ] [-CPUCount ] [-SessionSetupTimeout ] [UseADKWebInstaller] + ``` + Where the VHD file and matching ADK tools are located on the Host device and referenced in the 'ADKPath' and the 'VHDPath' parameters. + +A new Hyper-V VM file is created out of the provisioned VHD, creating a "clean" checkpoint, from where all of the sequencing and updating will start. ### Provision an existing VM for auto-sequencing From 47bcbae6e0c82af303767a94d59312ab5873224f Mon Sep 17 00:00:00 2001 From: LizRoss Date: Tue, 31 Jan 2017 15:09:49 -0800 Subject: [PATCH 04/76] Adding content --- windows/manage/appv-automatic-sequence-a-new-app.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/manage/appv-automatic-sequence-a-new-app.md b/windows/manage/appv-automatic-sequence-a-new-app.md index b8eaef66e8..e609d0dfb1 100644 --- a/windows/manage/appv-automatic-sequence-a-new-app.md +++ b/windows/manage/appv-automatic-sequence-a-new-app.md @@ -41,8 +41,8 @@ Provisioning your new VM includes setting up a user account, turning on remote P >[!IMPORTANT] >For this process to work, you must have a base operating system available as a VHD image file. If you need a tool to create your VHD file, you can use the [Convert-WindowsImage.ps1](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) command-line tool. This tool is now a Function, so it must first be loaded and then called by its name, without the extension. Code examples and more info about the tool are included on the download site.

Additionally, when you run this tool to create your file, you must explicitly specify the parameter 'VHDPartitionStyle' as 'MBR'. The default partition value, 'GPT' will cause a boot failure in your VHD file. -**On the Host device** -1. Install Windows 10, version 1703 and the matching ADK version, making sure that you've selected to install the **Microsoft Application Virtualization (App-V) Auto Sequencer** component. +**To provision your VM using a VHD file** +1. On the Host device, install Windows 10, version 1703 and the matching ADK version, making sure that you've selected to install the **Microsoft Application Virtualization (App-V) Auto Sequencer** component. 2. Make sure that Hyper-V is turned on. For more info about turning on and using Hyper-V, see [Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server) From b4e018ae78c102c22a65544855b57e7978343a65 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 1 Feb 2017 09:07:09 -0800 Subject: [PATCH 05/76] Adding text --- .../appv-automatic-sequence-a-new-app.md | 42 ++++++++++++------- ...istory-for-manage-and-update-windows-10.md | 6 +++ 2 files changed, 34 insertions(+), 14 deletions(-) diff --git a/windows/manage/appv-automatic-sequence-a-new-app.md b/windows/manage/appv-automatic-sequence-a-new-app.md index e609d0dfb1..87f0b66e6e 100644 --- a/windows/manage/appv-automatic-sequence-a-new-app.md +++ b/windows/manage/appv-automatic-sequence-a-new-app.md @@ -17,7 +17,7 @@ ms.prod: w10 >[NOTE] >In Windows 10, version 1703, the App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md). -With the previous versions of the App-V Sequencer, you've had to manually sequence your app packages. This was time-consuming and required extensive interaction, causing many companies to deploy brand-new packages rather than update an existing one. Windows 10, version 1703 has introduced an updated App-V Sequencer that can automatically sequence your app packages, improving your overall experience by streamlining the provisioning of the prerequisite environment, automating app installation, and expediting the package updating setup. +Previous versions of the App-V Sequencer have required you to manually sequence your app packages. This was time-consuming and required extensive interaction, causing many companies to deploy brand-new packages rather than update an existing one. Windows 10, version 1703 introduces an updated App-V Sequencer that automatically sequences your app packages, improving your overall experience by streamlining the provisioning of the prerequisite environment, automating app installation, and expediting the package updating setup. Using the automatic sequence to package your apps provides: @@ -27,31 +27,45 @@ Using the automatic sequence to package your apps provides: - Batch-updating of packages. This means that multiple apps can be updated at the same time, in a single group. -## Provision your VM You have 2 options for provisioning an VM for auto-sequencing: -- Provision a new VM by using a Virtual Hard Disk (VHD) +- Using a Virtual Hard Disk (VHD) -OR- -- Provision an existing VM +- Updating an existing VM -### Provision a new VM for auto-sequencing by using a VHD file -Provisioning your new VM includes setting up a user account, turning on remote PowerShell scripting, and installing the App-V Sequencer. +## Provision a new VM by using a VHD file +Provisioning your new VM includes creating a VHD file, setting up a user account, turning on remote PowerShell scripting, and installing the App-V Sequencer. ->[!IMPORTANT] ->For this process to work, you must have a base operating system available as a VHD image file. If you need a tool to create your VHD file, you can use the [Convert-WindowsImage.ps1](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) command-line tool. This tool is now a Function, so it must first be loaded and then called by its name, without the extension. Code examples and more info about the tool are included on the download site.

Additionally, when you run this tool to create your file, you must explicitly specify the parameter 'VHDPartitionStyle' as 'MBR'. The default partition value, 'GPT' will cause a boot failure in your VHD file. +### Create a VHD file +For this process to work, you must have a base operating system available as a VHD image file, we recommend using the [Convert-WindowsImage.ps1](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) command-line tool. -**To provision your VM using a VHD file** +**To create a VHD file by using the Convert-WindowsImage command-line tool** +1. Open PowerShell as an admin and run the Convert-WindowsImage tool, using the following commands: + + ```ps1 + Convert-WindowsImage -SourcePath "" -VHDFormat "VHD" -VHDPartitionStyle "MBR" + ``` + Where `SourcePath` is the full file path to your ISO image, `VHDFormat` is *VHD*, and `VHDPartitionStyle` is *MBR*. + + >[!IMPORTANT] + >You must specify the `VHDPartitionStyle` as **MBR**. Using the default value, **GPT**, will cause a boot failure in your VHD image. + +### Provision your VM using your VHD file +After you have a VHD file, you must provision your VM for auto-sequencing. + +**To provision your VM using your VHD file** 1. On the Host device, install Windows 10, version 1703 and the matching ADK version, making sure that you've selected to install the **Microsoft Application Virtualization (App-V) Auto Sequencer** component. -2. Make sure that Hyper-V is turned on. For more info about turning on and using Hyper-V, see [Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server) +2. Make sure that Hyper-V is turned on. For more info about turning on and using Hyper-V, see [Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server). -3. Open PowerShell as an admin and run the **New-AppVSequencerVM** cmdlet, using the required parameters: +3. Open PowerShell as an admin and run the **New-AppVSequencerVM** cmdlet, using the following parameters: + ```ps1 + New-AppVSequencerVM -VMName "" -ADKPath "" -VHDPath "" -VMMemory -VMSwitch "" ``` - New-AppVSequencerVM -VMName -ADKPath -VHDPath [-VMSwitch ] [-VMMemory ] [-CPUCount ] [-SessionSetupTimeout ] [UseADKWebInstaller] - ``` - Where the VHD file and matching ADK tools are located on the Host device and referenced in the 'ADKPath' and the 'VHDPath' parameters. + + Where you create a unique name for your VM, ensure that the VHD file and matching ADK tools are located on the Host device and referenced in the 'ADKPath' and the 'VHDPath' parameters, determine the amount of memory to be allocated for use by your VM, and provide the name of your network switch. A new Hyper-V VM file is created out of the provisioned VHD, creating a "clean" checkpoint, from where all of the sequencing and updating will start. diff --git a/windows/manage/change-history-for-manage-and-update-windows-10.md b/windows/manage/change-history-for-manage-and-update-windows-10.md index a794ec798f..01ba55717c 100644 --- a/windows/manage/change-history-for-manage-and-update-windows-10.md +++ b/windows/manage/change-history-for-manage-and-update-windows-10.md @@ -14,6 +14,12 @@ This topic lists new and updated topics in the [Manage and update Windows 10](in >If you're looking for **update history** for Windows 10, see [Windows 10 and Windows Server 2016 update history](https://support.microsoft.com/help/12387/windows-10-update-history). +## February 2017 +| New or changed topic | Description | +| --- | --- | +|[Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-automatic-sequence-a-new-app.md) |New | + + ## January 2017 | New or changed topic | Description | From b624b4c8ec4d8f64b54d79abb2c4e61bd05ea376 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 1 Feb 2017 09:54:23 -0800 Subject: [PATCH 06/76] Adding content --- .../appv-automatic-sequence-a-new-app.md | 51 +++++++++++++++++-- 1 file changed, 48 insertions(+), 3 deletions(-) diff --git a/windows/manage/appv-automatic-sequence-a-new-app.md b/windows/manage/appv-automatic-sequence-a-new-app.md index 87f0b66e6e..598f2543b8 100644 --- a/windows/manage/appv-automatic-sequence-a-new-app.md +++ b/windows/manage/appv-automatic-sequence-a-new-app.md @@ -69,13 +69,58 @@ After you have a VHD file, you must provision your VM for auto-sequencing. A new Hyper-V VM file is created out of the provisioned VHD, creating a "clean" checkpoint, from where all of the sequencing and updating will start. -### Provision an existing VM for auto-sequencing - +## Provision an existing VM for auto-sequencing +If your apps require custom prerequesites, such as Microsoft SQL Server, we recommend that you preinstall the prerequisites on your VM and then use that VM for auto-sequencing. Using these steps will establish a connection to your existing VM, install the Microsoft Application Virtualization (App-V) Auto Sequencer from the ADK tools, and provision your VM for auto-sequencing. + +**To connect to your existing VM** +- Open PowerShell as an admin and run the following commands on your existing VM: + + - **Set the network category of your connection profile on the VM to `Private`:** + + `Get-netconnectionprofile | set-netconnectionprofile -NetworkCategory Private` + + - **Set the Windows Firewall rules for the display groups, `Remote Desktop` and `Windows Remote Management`:** + + `Enable-NetFirewallRule -DisplayGroup “Remote Desktop”` and `Enable-NetFirewallRule -DisplayGroup “Windows Remote Management”` + + - **Set the VM to receive remote commands without a confirmation prompt:** + + `Enable-PSRemoting –Force` + + These commands turn on [PowerShell Remoting](https://msdn.microsoft.com/powershell/reference/5.1/Microsoft.PowerShell.Core/about/about_Remote) and turn on the necessary Windows Firewall rules so you can connect to your VM. + +**To provision an existing VM** +1. On the Host device, install Windows 10, version 1703 and the matching ADK version, making sure that you've selected to install the **Microsoft Application Virtualization (App-V) Auto Sequencer** component. + +2. Open PowerShell as an admin and run the **New-AppVSequencerVM** cmdlet, using the following parameters: + + ```ps1 + New-AppVSequencerVM -VMName "" -VMComputerName "" -ADKPath "" + ``` + + Where `VMName` is the name of the VM granted during its creation and shown in the Hyper-V Manager tool, and the `VMComputerName` is the name of the VM, assigned after its creation and shown on the **Computer name** field of the **System Properties** screen. + +A new Hyper-V VM file is created from the existing VM, creating a "clean" checkpoint, from where all of the sequencing and updating will start. + +## Reviewing the provisioning log files +The 2 types of provisioning log files, located at `“%temp%\AutoSequencer\Logs”`, are: + +- **New-AppVSequencerVM-.txt**: Includes info about the provisioning activities, such as "Waiting for VM session", "Copying installer for Sequencer", and so on. + +- **New-AppVSequencerVM-report-.txt**: Includes info about the connections made to the VM, showing whether there were any failures. ## Have a suggestion for App-V? Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). ## Related topics +- [Convert-WindowsImage.ps1](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) + +- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit) + - [Install the App-V Sequencer](appv-install-the-sequencer.md) -- [Operations for App-V](appv-operations.md) + +- [Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server) + +- [Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) + From df584a2dff747274606cfc9f26e9c6fc16271dbe Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 1 Feb 2017 09:57:42 -0800 Subject: [PATCH 07/76] Adding content --- windows/manage/appv-automatic-sequence-a-new-app.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/manage/appv-automatic-sequence-a-new-app.md b/windows/manage/appv-automatic-sequence-a-new-app.md index 598f2543b8..42f30b61b2 100644 --- a/windows/manage/appv-automatic-sequence-a-new-app.md +++ b/windows/manage/appv-automatic-sequence-a-new-app.md @@ -110,9 +110,6 @@ The 2 types of provisioning log files, located at `“%temp%\AutoSequencer\Logs - **New-AppVSequencerVM-report-.txt**: Includes info about the connections made to the VM, showing whether there were any failures. -## Have a suggestion for App-V? -Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). - ## Related topics - [Convert-WindowsImage.ps1](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) @@ -124,3 +121,6 @@ Add or vote on suggestions on the [Application Virtualization feedback site](htt - [Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) +## Have a suggestion for App-V? +Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). + From 569db58c18a423554c3c9b1a863c83fecb3323c4 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 1 Feb 2017 09:58:36 -0800 Subject: [PATCH 08/76] Adding content --- windows/manage/appv-automatic-sequence-a-new-app.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/manage/appv-automatic-sequence-a-new-app.md b/windows/manage/appv-automatic-sequence-a-new-app.md index 42f30b61b2..64c91091ba 100644 --- a/windows/manage/appv-automatic-sequence-a-new-app.md +++ b/windows/manage/appv-automatic-sequence-a-new-app.md @@ -111,13 +111,13 @@ The 2 types of provisioning log files, located at `“%temp%\AutoSequencer\Logs - **New-AppVSequencerVM-report-.txt**: Includes info about the connections made to the VM, showing whether there were any failures. ## Related topics -- [Convert-WindowsImage.ps1](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) +- [Download the Convert-WindowsImage tool](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) - [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit) - [Install the App-V Sequencer](appv-install-the-sequencer.md) -- [Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server) +- [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server) - [Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) From 64bd26c16780712ed631c85bca607acd4d58591a Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 1 Feb 2017 10:07:52 -0800 Subject: [PATCH 09/76] Adding content --- .../appv-automatic-sequence-a-new-app.md | 29 ++++++++++++------- 1 file changed, 18 insertions(+), 11 deletions(-) diff --git a/windows/manage/appv-automatic-sequence-a-new-app.md b/windows/manage/appv-automatic-sequence-a-new-app.md index 64c91091ba..f9ae92a682 100644 --- a/windows/manage/appv-automatic-sequence-a-new-app.md +++ b/windows/manage/appv-automatic-sequence-a-new-app.md @@ -14,7 +14,7 @@ ms.prod: w10 **Applies to** - Windows 10, version 1703 ->[NOTE] +>[!NOTE] >In Windows 10, version 1703, the App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md). Previous versions of the App-V Sequencer have required you to manually sequence your app packages. This was time-consuming and required extensive interaction, causing many companies to deploy brand-new packages rather than update an existing one. Windows 10, version 1703 introduces an updated App-V Sequencer that automatically sequences your app packages, improving your overall experience by streamlining the provisioning of the prerequisite environment, automating app installation, and expediting the package updating setup. @@ -46,10 +46,10 @@ For this process to work, you must have a base operating system available as a V ```ps1 Convert-WindowsImage -SourcePath "" -VHDFormat "VHD" -VHDPartitionStyle "MBR" ``` - Where `SourcePath` is the full file path to your ISO image, `VHDFormat` is *VHD*, and `VHDPartitionStyle` is *MBR*. + Where _SourcePath_ is the full file path to your ISO image, _VHDFormat_ is *VHD*, and _VHDPartitionStyle_ is *MBR*. >[!IMPORTANT] - >You must specify the `VHDPartitionStyle` as **MBR**. Using the default value, **GPT**, will cause a boot failure in your VHD image. + >You must specify the _VHDPartitionStyle_ as **MBR**. Using the default value, **GPT**, will cause a boot failure in your VHD image. ### Provision your VM using your VHD file After you have a VHD file, you must provision your VM for auto-sequencing. @@ -65,7 +65,7 @@ After you have a VHD file, you must provision your VM for auto-sequencing. New-AppVSequencerVM -VMName "" -ADKPath "" -VHDPath "" -VMMemory -VMSwitch "" ``` - Where you create a unique name for your VM, ensure that the VHD file and matching ADK tools are located on the Host device and referenced in the 'ADKPath' and the 'VHDPath' parameters, determine the amount of memory to be allocated for use by your VM, and provide the name of your network switch. + Where you create a unique name for your VM, ensure that the VHD file and matching ADK tools are located on the Host device and referenced in the _ADKPath_ and the _VHDPath_ parameters, determine the amount of memory to be allocated for use by your VM, and provide the name of your network switch. A new Hyper-V VM file is created out of the provisioned VHD, creating a "clean" checkpoint, from where all of the sequencing and updating will start. @@ -76,17 +76,24 @@ If your apps require custom prerequesites, such as Microsoft SQL Server, we reco **To connect to your existing VM** - Open PowerShell as an admin and run the following commands on your existing VM: - - **Set the network category of your connection profile on the VM to `Private`:** + - **Set the network category of your connection profile on the VM to _Private_:** - `Get-netconnectionprofile | set-netconnectionprofile -NetworkCategory Private` + ```ps1 + Get-netconnectionprofile | set-netconnectionprofile -NetworkCategory Private + ``` - - **Set the Windows Firewall rules for the display groups, `Remote Desktop` and `Windows Remote Management`:** + - **Set the Windows Firewall rules for the display groups, _Remote Desktop_ and _Windows Remote Management_:** - `Enable-NetFirewallRule -DisplayGroup “Remote Desktop”` and `Enable-NetFirewallRule -DisplayGroup “Windows Remote Management”` + ```ps1 + Enable-NetFirewallRule -DisplayGroup “Remote Desktop” + Enable-NetFirewallRule -DisplayGroup “Windows Remote Management” + ``` - **Set the VM to receive remote commands without a confirmation prompt:** - `Enable-PSRemoting –Force` + ```ps1 + Enable-PSRemoting –Force + ``` These commands turn on [PowerShell Remoting](https://msdn.microsoft.com/powershell/reference/5.1/Microsoft.PowerShell.Core/about/about_Remote) and turn on the necessary Windows Firewall rules so you can connect to your VM. @@ -99,12 +106,12 @@ If your apps require custom prerequesites, such as Microsoft SQL Server, we reco New-AppVSequencerVM -VMName "" -VMComputerName "" -ADKPath "" ``` - Where `VMName` is the name of the VM granted during its creation and shown in the Hyper-V Manager tool, and the `VMComputerName` is the name of the VM, assigned after its creation and shown on the **Computer name** field of the **System Properties** screen. + Where _VMName_ is the name of the VM granted during its creation and shown in the Hyper-V Manager tool, and the _VMComputerName_ is the name of the VM, assigned after its creation and shown on the **Computer name** field of the **System Properties** screen. A new Hyper-V VM file is created from the existing VM, creating a "clean" checkpoint, from where all of the sequencing and updating will start. ## Reviewing the provisioning log files -The 2 types of provisioning log files, located at `“%temp%\AutoSequencer\Logs”`, are: +The 2 types of provisioning log files, located at “%temp%\AutoSequencer\Logs”, are: - **New-AppVSequencerVM-.txt**: Includes info about the provisioning activities, such as "Waiting for VM session", "Copying installer for Sequencer", and so on. From dd8eb5e7d4389556f5f0693fd6045c34dbbb02d6 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 1 Feb 2017 10:09:55 -0800 Subject: [PATCH 10/76] Adding content --- windows/manage/appv-automatic-sequence-a-new-app.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/manage/appv-automatic-sequence-a-new-app.md b/windows/manage/appv-automatic-sequence-a-new-app.md index f9ae92a682..d2de75ed89 100644 --- a/windows/manage/appv-automatic-sequence-a-new-app.md +++ b/windows/manage/appv-automatic-sequence-a-new-app.md @@ -110,7 +110,7 @@ If your apps require custom prerequesites, such as Microsoft SQL Server, we reco A new Hyper-V VM file is created from the existing VM, creating a "clean" checkpoint, from where all of the sequencing and updating will start. -## Reviewing the provisioning log files +## Review the provisioning log files The 2 types of provisioning log files, located at “%temp%\AutoSequencer\Logs”, are: - **New-AppVSequencerVM-.txt**: Includes info about the provisioning activities, such as "Waiting for VM session", "Copying installer for Sequencer", and so on. From dd1afdfb3cd878430690c29bd060e5a9af460d2f Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 1 Feb 2017 10:25:55 -0800 Subject: [PATCH 11/76] Adding content --- .../appv-automatic-sequence-a-new-app.md | 24 ++++++++++--------- 1 file changed, 13 insertions(+), 11 deletions(-) diff --git a/windows/manage/appv-automatic-sequence-a-new-app.md b/windows/manage/appv-automatic-sequence-a-new-app.md index d2de75ed89..8ae98f8d0c 100644 --- a/windows/manage/appv-automatic-sequence-a-new-app.md +++ b/windows/manage/appv-automatic-sequence-a-new-app.md @@ -19,14 +19,15 @@ ms.prod: w10 Previous versions of the App-V Sequencer have required you to manually sequence your app packages. This was time-consuming and required extensive interaction, causing many companies to deploy brand-new packages rather than update an existing one. Windows 10, version 1703 introduces an updated App-V Sequencer that automatically sequences your app packages, improving your overall experience by streamlining the provisioning of the prerequisite environment, automating app installation, and expediting the package updating setup. -Using the automatic sequence to package your apps provides: +Using the automatic sequencer to package your apps provides: -- Automatic virtual machine (VM) provisioning of the sequencing environment. +- Automatic virtual machine (VM) provisioning of the sequencing environment. The process for this is covered in this topic. -- Batch-sequencing of packages. This means that multiple apps can be sequenced at the same time, in a single group. +- Batch-sequencing of packages. This means that multiple apps can be sequenced at the same time, in a single group. For info about this, see ... -- Batch-updating of packages. This means that multiple apps can be updated at the same time, in a single group. +- Batch-updating of packages. This means that multiple apps can be updated at the same time, in a single group. For info about this, see ... +## Automatic VM provisioning of the sequencing environment You have 2 options for provisioning an VM for auto-sequencing: - Using a Virtual Hard Disk (VHD) @@ -34,10 +35,10 @@ You have 2 options for provisioning an VM for auto-sequencing: - Updating an existing VM -## Provision a new VM by using a VHD file +### Provision a new VM by using a VHD file Provisioning your new VM includes creating a VHD file, setting up a user account, turning on remote PowerShell scripting, and installing the App-V Sequencer. -### Create a VHD file +#### Create a VHD file For this process to work, you must have a base operating system available as a VHD image file, we recommend using the [Convert-WindowsImage.ps1](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) command-line tool. **To create a VHD file by using the Convert-WindowsImage command-line tool** @@ -51,7 +52,7 @@ For this process to work, you must have a base operating system available as a V >[!IMPORTANT] >You must specify the _VHDPartitionStyle_ as **MBR**. Using the default value, **GPT**, will cause a boot failure in your VHD image. -### Provision your VM using your VHD file +#### Provision your VM using your VHD file After you have a VHD file, you must provision your VM for auto-sequencing. **To provision your VM using your VHD file** @@ -70,7 +71,7 @@ After you have a VHD file, you must provision your VM for auto-sequencing. A new Hyper-V VM file is created out of the provisioned VHD, creating a "clean" checkpoint, from where all of the sequencing and updating will start. -## Provision an existing VM for auto-sequencing +### Provision an existing VM for auto-sequencing If your apps require custom prerequesites, such as Microsoft SQL Server, we recommend that you preinstall the prerequisites on your VM and then use that VM for auto-sequencing. Using these steps will establish a connection to your existing VM, install the Microsoft Application Virtualization (App-V) Auto Sequencer from the ADK tools, and provision your VM for auto-sequencing. **To connect to your existing VM** @@ -110,14 +111,14 @@ If your apps require custom prerequesites, such as Microsoft SQL Server, we reco A new Hyper-V VM file is created from the existing VM, creating a "clean" checkpoint, from where all of the sequencing and updating will start. -## Review the provisioning log files +### Review the provisioning log files The 2 types of provisioning log files, located at “%temp%\AutoSequencer\Logs”, are: - **New-AppVSequencerVM-.txt**: Includes info about the provisioning activities, such as "Waiting for VM session", "Copying installer for Sequencer", and so on. - **New-AppVSequencerVM-report-.txt**: Includes info about the connections made to the VM, showing whether there were any failures. -## Related topics +### Related topics - [Download the Convert-WindowsImage tool](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) - [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit) @@ -128,6 +129,7 @@ The 2 types of provisioning log files, located at “%temp%\AutoSequencer\Logs - [Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) -## Have a suggestion for App-V? +**Have a suggestion for App-V?** + Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). From b6228b9326d0ef0a02397e6c0ce969ac39c7d759 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 1 Feb 2017 10:29:26 -0800 Subject: [PATCH 12/76] Adding content --- windows/manage/appv-automatic-sequence-a-new-app.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/windows/manage/appv-automatic-sequence-a-new-app.md b/windows/manage/appv-automatic-sequence-a-new-app.md index 8ae98f8d0c..10fa90119e 100644 --- a/windows/manage/appv-automatic-sequence-a-new-app.md +++ b/windows/manage/appv-automatic-sequence-a-new-app.md @@ -14,9 +14,6 @@ ms.prod: w10 **Applies to** - Windows 10, version 1703 ->[!NOTE] ->In Windows 10, version 1703, the App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md). - Previous versions of the App-V Sequencer have required you to manually sequence your app packages. This was time-consuming and required extensive interaction, causing many companies to deploy brand-new packages rather than update an existing one. Windows 10, version 1703 introduces an updated App-V Sequencer that automatically sequences your app packages, improving your overall experience by streamlining the provisioning of the prerequisite environment, automating app installation, and expediting the package updating setup. Using the automatic sequencer to package your apps provides: @@ -58,6 +55,9 @@ After you have a VHD file, you must provision your VM for auto-sequencing. **To provision your VM using your VHD file** 1. On the Host device, install Windows 10, version 1703 and the matching ADK version, making sure that you've selected to install the **Microsoft Application Virtualization (App-V) Auto Sequencer** component. + >[!NOTE] + >The App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md). + 2. Make sure that Hyper-V is turned on. For more info about turning on and using Hyper-V, see [Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server). 3. Open PowerShell as an admin and run the **New-AppVSequencerVM** cmdlet, using the following parameters: @@ -101,6 +101,9 @@ If your apps require custom prerequesites, such as Microsoft SQL Server, we reco **To provision an existing VM** 1. On the Host device, install Windows 10, version 1703 and the matching ADK version, making sure that you've selected to install the **Microsoft Application Virtualization (App-V) Auto Sequencer** component. + >[!NOTE] + >The App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md). + 2. Open PowerShell as an admin and run the **New-AppVSequencerVM** cmdlet, using the following parameters: ```ps1 @@ -123,7 +126,7 @@ The 2 types of provisioning log files, located at “%temp%\AutoSequencer\Logs - [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit) -- [Install the App-V Sequencer](appv-install-the-sequencer.md) +- [How to install the App-V Sequencer](appv-install-the-sequencer.md) - [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server) From 40129c9d1f58b0f5ba5e2f2f949b62a4ed6a29cd Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 1 Feb 2017 10:38:38 -0800 Subject: [PATCH 13/76] Adding content --- windows/manage/TOC.md | 2 + windows/manage/appv-auto-batch-sequencing.md | 138 ++++++++++++++++++ windows/manage/appv-auto-batch-updating.md | 138 ++++++++++++++++++ .../appv-automatic-sequence-a-new-app.md | 4 +- windows/manage/appv-template-improvements.md | 138 ++++++++++++++++++ ...istory-for-manage-and-update-windows-10.md | 6 +- 6 files changed, 421 insertions(+), 5 deletions(-) create mode 100644 windows/manage/appv-auto-batch-sequencing.md create mode 100644 windows/manage/appv-auto-batch-updating.md create mode 100644 windows/manage/appv-template-improvements.md diff --git a/windows/manage/TOC.md b/windows/manage/TOC.md index 0144c9280b..853e71ae8d 100644 --- a/windows/manage/TOC.md +++ b/windows/manage/TOC.md @@ -112,6 +112,8 @@ #### [Creating and Managing App-V Virtualized Applications](appv-creating-and-managing-virtualized-applications.md) ##### [Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) ##### [Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-automatic-sequence-a-new-app.md) +###### [Automatically sequence multiple apps at the same time](appv-auto-batch-sequencing.md) +###### [Automatically update multiple apps at the same time](appv-auto-batch-updating.md) ##### [How to Modify an Existing Virtual Application Package](appv-modify-an-existing-virtual-application-package.md) ##### [How to Create and Use a Project Template](appv-create-and-use-a-project-template.md) ##### [How to Create a Package Accelerator](appv-create-a-package-accelerator.md) diff --git a/windows/manage/appv-auto-batch-sequencing.md b/windows/manage/appv-auto-batch-sequencing.md new file mode 100644 index 0000000000..10fa90119e --- /dev/null +++ b/windows/manage/appv-auto-batch-sequencing.md @@ -0,0 +1,138 @@ +--- +title: Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10) +description: How to automatically sequence a new app using the App-V Sequencer +author: eross-msft +ms.pagetype: mdop, appcompat, virtualization +ms.mktglfcycl: deploy +ms.sitesec: library +ms.prod: w10 +--- + + +# Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) + +**Applies to** +- Windows 10, version 1703 + +Previous versions of the App-V Sequencer have required you to manually sequence your app packages. This was time-consuming and required extensive interaction, causing many companies to deploy brand-new packages rather than update an existing one. Windows 10, version 1703 introduces an updated App-V Sequencer that automatically sequences your app packages, improving your overall experience by streamlining the provisioning of the prerequisite environment, automating app installation, and expediting the package updating setup. + +Using the automatic sequencer to package your apps provides: + +- Automatic virtual machine (VM) provisioning of the sequencing environment. The process for this is covered in this topic. + +- Batch-sequencing of packages. This means that multiple apps can be sequenced at the same time, in a single group. For info about this, see ... + +- Batch-updating of packages. This means that multiple apps can be updated at the same time, in a single group. For info about this, see ... + +## Automatic VM provisioning of the sequencing environment +You have 2 options for provisioning an VM for auto-sequencing: +- Using a Virtual Hard Disk (VHD) + + -OR- + +- Updating an existing VM + +### Provision a new VM by using a VHD file +Provisioning your new VM includes creating a VHD file, setting up a user account, turning on remote PowerShell scripting, and installing the App-V Sequencer. + +#### Create a VHD file +For this process to work, you must have a base operating system available as a VHD image file, we recommend using the [Convert-WindowsImage.ps1](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) command-line tool. + +**To create a VHD file by using the Convert-WindowsImage command-line tool** +1. Open PowerShell as an admin and run the Convert-WindowsImage tool, using the following commands: + + ```ps1 + Convert-WindowsImage -SourcePath "" -VHDFormat "VHD" -VHDPartitionStyle "MBR" + ``` + Where _SourcePath_ is the full file path to your ISO image, _VHDFormat_ is *VHD*, and _VHDPartitionStyle_ is *MBR*. + + >[!IMPORTANT] + >You must specify the _VHDPartitionStyle_ as **MBR**. Using the default value, **GPT**, will cause a boot failure in your VHD image. + +#### Provision your VM using your VHD file +After you have a VHD file, you must provision your VM for auto-sequencing. + +**To provision your VM using your VHD file** +1. On the Host device, install Windows 10, version 1703 and the matching ADK version, making sure that you've selected to install the **Microsoft Application Virtualization (App-V) Auto Sequencer** component. + + >[!NOTE] + >The App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md). + +2. Make sure that Hyper-V is turned on. For more info about turning on and using Hyper-V, see [Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server). + +3. Open PowerShell as an admin and run the **New-AppVSequencerVM** cmdlet, using the following parameters: + + ```ps1 + New-AppVSequencerVM -VMName "" -ADKPath "" -VHDPath "" -VMMemory -VMSwitch "" + ``` + + Where you create a unique name for your VM, ensure that the VHD file and matching ADK tools are located on the Host device and referenced in the _ADKPath_ and the _VHDPath_ parameters, determine the amount of memory to be allocated for use by your VM, and provide the name of your network switch. + +A new Hyper-V VM file is created out of the provisioned VHD, creating a "clean" checkpoint, from where all of the sequencing and updating will start. + + +### Provision an existing VM for auto-sequencing +If your apps require custom prerequesites, such as Microsoft SQL Server, we recommend that you preinstall the prerequisites on your VM and then use that VM for auto-sequencing. Using these steps will establish a connection to your existing VM, install the Microsoft Application Virtualization (App-V) Auto Sequencer from the ADK tools, and provision your VM for auto-sequencing. + +**To connect to your existing VM** +- Open PowerShell as an admin and run the following commands on your existing VM: + + - **Set the network category of your connection profile on the VM to _Private_:** + + ```ps1 + Get-netconnectionprofile | set-netconnectionprofile -NetworkCategory Private + ``` + + - **Set the Windows Firewall rules for the display groups, _Remote Desktop_ and _Windows Remote Management_:** + + ```ps1 + Enable-NetFirewallRule -DisplayGroup “Remote Desktop” + Enable-NetFirewallRule -DisplayGroup “Windows Remote Management” + ``` + + - **Set the VM to receive remote commands without a confirmation prompt:** + + ```ps1 + Enable-PSRemoting –Force + ``` + + These commands turn on [PowerShell Remoting](https://msdn.microsoft.com/powershell/reference/5.1/Microsoft.PowerShell.Core/about/about_Remote) and turn on the necessary Windows Firewall rules so you can connect to your VM. + +**To provision an existing VM** +1. On the Host device, install Windows 10, version 1703 and the matching ADK version, making sure that you've selected to install the **Microsoft Application Virtualization (App-V) Auto Sequencer** component. + + >[!NOTE] + >The App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md). + +2. Open PowerShell as an admin and run the **New-AppVSequencerVM** cmdlet, using the following parameters: + + ```ps1 + New-AppVSequencerVM -VMName "" -VMComputerName "" -ADKPath "" + ``` + + Where _VMName_ is the name of the VM granted during its creation and shown in the Hyper-V Manager tool, and the _VMComputerName_ is the name of the VM, assigned after its creation and shown on the **Computer name** field of the **System Properties** screen. + +A new Hyper-V VM file is created from the existing VM, creating a "clean" checkpoint, from where all of the sequencing and updating will start. + +### Review the provisioning log files +The 2 types of provisioning log files, located at “%temp%\AutoSequencer\Logs”, are: + +- **New-AppVSequencerVM-.txt**: Includes info about the provisioning activities, such as "Waiting for VM session", "Copying installer for Sequencer", and so on. + +- **New-AppVSequencerVM-report-.txt**: Includes info about the connections made to the VM, showing whether there were any failures. + +### Related topics +- [Download the Convert-WindowsImage tool](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) + +- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit) + +- [How to install the App-V Sequencer](appv-install-the-sequencer.md) + +- [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server) + +- [Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) + +**Have a suggestion for App-V?** + +Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). + diff --git a/windows/manage/appv-auto-batch-updating.md b/windows/manage/appv-auto-batch-updating.md new file mode 100644 index 0000000000..10fa90119e --- /dev/null +++ b/windows/manage/appv-auto-batch-updating.md @@ -0,0 +1,138 @@ +--- +title: Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10) +description: How to automatically sequence a new app using the App-V Sequencer +author: eross-msft +ms.pagetype: mdop, appcompat, virtualization +ms.mktglfcycl: deploy +ms.sitesec: library +ms.prod: w10 +--- + + +# Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) + +**Applies to** +- Windows 10, version 1703 + +Previous versions of the App-V Sequencer have required you to manually sequence your app packages. This was time-consuming and required extensive interaction, causing many companies to deploy brand-new packages rather than update an existing one. Windows 10, version 1703 introduces an updated App-V Sequencer that automatically sequences your app packages, improving your overall experience by streamlining the provisioning of the prerequisite environment, automating app installation, and expediting the package updating setup. + +Using the automatic sequencer to package your apps provides: + +- Automatic virtual machine (VM) provisioning of the sequencing environment. The process for this is covered in this topic. + +- Batch-sequencing of packages. This means that multiple apps can be sequenced at the same time, in a single group. For info about this, see ... + +- Batch-updating of packages. This means that multiple apps can be updated at the same time, in a single group. For info about this, see ... + +## Automatic VM provisioning of the sequencing environment +You have 2 options for provisioning an VM for auto-sequencing: +- Using a Virtual Hard Disk (VHD) + + -OR- + +- Updating an existing VM + +### Provision a new VM by using a VHD file +Provisioning your new VM includes creating a VHD file, setting up a user account, turning on remote PowerShell scripting, and installing the App-V Sequencer. + +#### Create a VHD file +For this process to work, you must have a base operating system available as a VHD image file, we recommend using the [Convert-WindowsImage.ps1](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) command-line tool. + +**To create a VHD file by using the Convert-WindowsImage command-line tool** +1. Open PowerShell as an admin and run the Convert-WindowsImage tool, using the following commands: + + ```ps1 + Convert-WindowsImage -SourcePath "" -VHDFormat "VHD" -VHDPartitionStyle "MBR" + ``` + Where _SourcePath_ is the full file path to your ISO image, _VHDFormat_ is *VHD*, and _VHDPartitionStyle_ is *MBR*. + + >[!IMPORTANT] + >You must specify the _VHDPartitionStyle_ as **MBR**. Using the default value, **GPT**, will cause a boot failure in your VHD image. + +#### Provision your VM using your VHD file +After you have a VHD file, you must provision your VM for auto-sequencing. + +**To provision your VM using your VHD file** +1. On the Host device, install Windows 10, version 1703 and the matching ADK version, making sure that you've selected to install the **Microsoft Application Virtualization (App-V) Auto Sequencer** component. + + >[!NOTE] + >The App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md). + +2. Make sure that Hyper-V is turned on. For more info about turning on and using Hyper-V, see [Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server). + +3. Open PowerShell as an admin and run the **New-AppVSequencerVM** cmdlet, using the following parameters: + + ```ps1 + New-AppVSequencerVM -VMName "" -ADKPath "" -VHDPath "" -VMMemory -VMSwitch "" + ``` + + Where you create a unique name for your VM, ensure that the VHD file and matching ADK tools are located on the Host device and referenced in the _ADKPath_ and the _VHDPath_ parameters, determine the amount of memory to be allocated for use by your VM, and provide the name of your network switch. + +A new Hyper-V VM file is created out of the provisioned VHD, creating a "clean" checkpoint, from where all of the sequencing and updating will start. + + +### Provision an existing VM for auto-sequencing +If your apps require custom prerequesites, such as Microsoft SQL Server, we recommend that you preinstall the prerequisites on your VM and then use that VM for auto-sequencing. Using these steps will establish a connection to your existing VM, install the Microsoft Application Virtualization (App-V) Auto Sequencer from the ADK tools, and provision your VM for auto-sequencing. + +**To connect to your existing VM** +- Open PowerShell as an admin and run the following commands on your existing VM: + + - **Set the network category of your connection profile on the VM to _Private_:** + + ```ps1 + Get-netconnectionprofile | set-netconnectionprofile -NetworkCategory Private + ``` + + - **Set the Windows Firewall rules for the display groups, _Remote Desktop_ and _Windows Remote Management_:** + + ```ps1 + Enable-NetFirewallRule -DisplayGroup “Remote Desktop” + Enable-NetFirewallRule -DisplayGroup “Windows Remote Management” + ``` + + - **Set the VM to receive remote commands without a confirmation prompt:** + + ```ps1 + Enable-PSRemoting –Force + ``` + + These commands turn on [PowerShell Remoting](https://msdn.microsoft.com/powershell/reference/5.1/Microsoft.PowerShell.Core/about/about_Remote) and turn on the necessary Windows Firewall rules so you can connect to your VM. + +**To provision an existing VM** +1. On the Host device, install Windows 10, version 1703 and the matching ADK version, making sure that you've selected to install the **Microsoft Application Virtualization (App-V) Auto Sequencer** component. + + >[!NOTE] + >The App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md). + +2. Open PowerShell as an admin and run the **New-AppVSequencerVM** cmdlet, using the following parameters: + + ```ps1 + New-AppVSequencerVM -VMName "" -VMComputerName "" -ADKPath "" + ``` + + Where _VMName_ is the name of the VM granted during its creation and shown in the Hyper-V Manager tool, and the _VMComputerName_ is the name of the VM, assigned after its creation and shown on the **Computer name** field of the **System Properties** screen. + +A new Hyper-V VM file is created from the existing VM, creating a "clean" checkpoint, from where all of the sequencing and updating will start. + +### Review the provisioning log files +The 2 types of provisioning log files, located at “%temp%\AutoSequencer\Logs”, are: + +- **New-AppVSequencerVM-.txt**: Includes info about the provisioning activities, such as "Waiting for VM session", "Copying installer for Sequencer", and so on. + +- **New-AppVSequencerVM-report-.txt**: Includes info about the connections made to the VM, showing whether there were any failures. + +### Related topics +- [Download the Convert-WindowsImage tool](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) + +- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit) + +- [How to install the App-V Sequencer](appv-install-the-sequencer.md) + +- [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server) + +- [Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) + +**Have a suggestion for App-V?** + +Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). + diff --git a/windows/manage/appv-automatic-sequence-a-new-app.md b/windows/manage/appv-automatic-sequence-a-new-app.md index 10fa90119e..923f535b49 100644 --- a/windows/manage/appv-automatic-sequence-a-new-app.md +++ b/windows/manage/appv-automatic-sequence-a-new-app.md @@ -20,9 +20,9 @@ Using the automatic sequencer to package your apps provides: - Automatic virtual machine (VM) provisioning of the sequencing environment. The process for this is covered in this topic. -- Batch-sequencing of packages. This means that multiple apps can be sequenced at the same time, in a single group. For info about this, see ... +- Batch-sequencing of packages. This means that multiple apps can be sequenced at the same time, in a single group. For info about this, see [Automatically sequence multiple apps at the same time](appv-auto-batch-sequencing.md) -- Batch-updating of packages. This means that multiple apps can be updated at the same time, in a single group. For info about this, see ... +- Batch-updating of packages. This means that multiple apps can be updated at the same time, in a single group. For info about this, see [Automatically update multiple apps at the same time](appv-auto-batch-updating.md) ## Automatic VM provisioning of the sequencing environment You have 2 options for provisioning an VM for auto-sequencing: diff --git a/windows/manage/appv-template-improvements.md b/windows/manage/appv-template-improvements.md new file mode 100644 index 0000000000..10fa90119e --- /dev/null +++ b/windows/manage/appv-template-improvements.md @@ -0,0 +1,138 @@ +--- +title: Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10) +description: How to automatically sequence a new app using the App-V Sequencer +author: eross-msft +ms.pagetype: mdop, appcompat, virtualization +ms.mktglfcycl: deploy +ms.sitesec: library +ms.prod: w10 +--- + + +# Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) + +**Applies to** +- Windows 10, version 1703 + +Previous versions of the App-V Sequencer have required you to manually sequence your app packages. This was time-consuming and required extensive interaction, causing many companies to deploy brand-new packages rather than update an existing one. Windows 10, version 1703 introduces an updated App-V Sequencer that automatically sequences your app packages, improving your overall experience by streamlining the provisioning of the prerequisite environment, automating app installation, and expediting the package updating setup. + +Using the automatic sequencer to package your apps provides: + +- Automatic virtual machine (VM) provisioning of the sequencing environment. The process for this is covered in this topic. + +- Batch-sequencing of packages. This means that multiple apps can be sequenced at the same time, in a single group. For info about this, see ... + +- Batch-updating of packages. This means that multiple apps can be updated at the same time, in a single group. For info about this, see ... + +## Automatic VM provisioning of the sequencing environment +You have 2 options for provisioning an VM for auto-sequencing: +- Using a Virtual Hard Disk (VHD) + + -OR- + +- Updating an existing VM + +### Provision a new VM by using a VHD file +Provisioning your new VM includes creating a VHD file, setting up a user account, turning on remote PowerShell scripting, and installing the App-V Sequencer. + +#### Create a VHD file +For this process to work, you must have a base operating system available as a VHD image file, we recommend using the [Convert-WindowsImage.ps1](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) command-line tool. + +**To create a VHD file by using the Convert-WindowsImage command-line tool** +1. Open PowerShell as an admin and run the Convert-WindowsImage tool, using the following commands: + + ```ps1 + Convert-WindowsImage -SourcePath "" -VHDFormat "VHD" -VHDPartitionStyle "MBR" + ``` + Where _SourcePath_ is the full file path to your ISO image, _VHDFormat_ is *VHD*, and _VHDPartitionStyle_ is *MBR*. + + >[!IMPORTANT] + >You must specify the _VHDPartitionStyle_ as **MBR**. Using the default value, **GPT**, will cause a boot failure in your VHD image. + +#### Provision your VM using your VHD file +After you have a VHD file, you must provision your VM for auto-sequencing. + +**To provision your VM using your VHD file** +1. On the Host device, install Windows 10, version 1703 and the matching ADK version, making sure that you've selected to install the **Microsoft Application Virtualization (App-V) Auto Sequencer** component. + + >[!NOTE] + >The App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md). + +2. Make sure that Hyper-V is turned on. For more info about turning on and using Hyper-V, see [Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server). + +3. Open PowerShell as an admin and run the **New-AppVSequencerVM** cmdlet, using the following parameters: + + ```ps1 + New-AppVSequencerVM -VMName "" -ADKPath "" -VHDPath "" -VMMemory -VMSwitch "" + ``` + + Where you create a unique name for your VM, ensure that the VHD file and matching ADK tools are located on the Host device and referenced in the _ADKPath_ and the _VHDPath_ parameters, determine the amount of memory to be allocated for use by your VM, and provide the name of your network switch. + +A new Hyper-V VM file is created out of the provisioned VHD, creating a "clean" checkpoint, from where all of the sequencing and updating will start. + + +### Provision an existing VM for auto-sequencing +If your apps require custom prerequesites, such as Microsoft SQL Server, we recommend that you preinstall the prerequisites on your VM and then use that VM for auto-sequencing. Using these steps will establish a connection to your existing VM, install the Microsoft Application Virtualization (App-V) Auto Sequencer from the ADK tools, and provision your VM for auto-sequencing. + +**To connect to your existing VM** +- Open PowerShell as an admin and run the following commands on your existing VM: + + - **Set the network category of your connection profile on the VM to _Private_:** + + ```ps1 + Get-netconnectionprofile | set-netconnectionprofile -NetworkCategory Private + ``` + + - **Set the Windows Firewall rules for the display groups, _Remote Desktop_ and _Windows Remote Management_:** + + ```ps1 + Enable-NetFirewallRule -DisplayGroup “Remote Desktop” + Enable-NetFirewallRule -DisplayGroup “Windows Remote Management” + ``` + + - **Set the VM to receive remote commands without a confirmation prompt:** + + ```ps1 + Enable-PSRemoting –Force + ``` + + These commands turn on [PowerShell Remoting](https://msdn.microsoft.com/powershell/reference/5.1/Microsoft.PowerShell.Core/about/about_Remote) and turn on the necessary Windows Firewall rules so you can connect to your VM. + +**To provision an existing VM** +1. On the Host device, install Windows 10, version 1703 and the matching ADK version, making sure that you've selected to install the **Microsoft Application Virtualization (App-V) Auto Sequencer** component. + + >[!NOTE] + >The App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md). + +2. Open PowerShell as an admin and run the **New-AppVSequencerVM** cmdlet, using the following parameters: + + ```ps1 + New-AppVSequencerVM -VMName "" -VMComputerName "" -ADKPath "" + ``` + + Where _VMName_ is the name of the VM granted during its creation and shown in the Hyper-V Manager tool, and the _VMComputerName_ is the name of the VM, assigned after its creation and shown on the **Computer name** field of the **System Properties** screen. + +A new Hyper-V VM file is created from the existing VM, creating a "clean" checkpoint, from where all of the sequencing and updating will start. + +### Review the provisioning log files +The 2 types of provisioning log files, located at “%temp%\AutoSequencer\Logs”, are: + +- **New-AppVSequencerVM-.txt**: Includes info about the provisioning activities, such as "Waiting for VM session", "Copying installer for Sequencer", and so on. + +- **New-AppVSequencerVM-report-.txt**: Includes info about the connections made to the VM, showing whether there were any failures. + +### Related topics +- [Download the Convert-WindowsImage tool](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) + +- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit) + +- [How to install the App-V Sequencer](appv-install-the-sequencer.md) + +- [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server) + +- [Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) + +**Have a suggestion for App-V?** + +Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). + diff --git a/windows/manage/change-history-for-manage-and-update-windows-10.md b/windows/manage/change-history-for-manage-and-update-windows-10.md index 01ba55717c..63da032a1f 100644 --- a/windows/manage/change-history-for-manage-and-update-windows-10.md +++ b/windows/manage/change-history-for-manage-and-update-windows-10.md @@ -18,7 +18,9 @@ This topic lists new and updated topics in the [Manage and update Windows 10](in | New or changed topic | Description | | --- | --- | |[Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-automatic-sequence-a-new-app.md) |New | - +|[Automatically sequence multiple apps at the same time](appv-auto-batch-sequencing.md) |New | +|[Automatically update multiple apps at the same time](appv-auto-batch-updating.md) |New | +|[](appv-template-improvements.md) |New | ## January 2017 @@ -30,8 +32,6 @@ This topic lists new and updated topics in the [Manage and update Windows 10](in | [Quick guide to Windows as a service](waas-quick-start.md) | Added video that explains how Windows as a service works. | | [Manage device restarts after updates](waas-restart.md) | Added Registry keys for controlling restarts. | - - ## December 2016 | New or changed topic | Description | From 102339df2d70fd3133dd83401ba11d7470cc3c9f Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 1 Feb 2017 10:51:10 -0800 Subject: [PATCH 14/76] Adding content --- windows/manage/appv-automatic-sequence-a-new-app.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/windows/manage/appv-automatic-sequence-a-new-app.md b/windows/manage/appv-automatic-sequence-a-new-app.md index 923f535b49..40ed2c4e0e 100644 --- a/windows/manage/appv-automatic-sequence-a-new-app.md +++ b/windows/manage/appv-automatic-sequence-a-new-app.md @@ -20,9 +20,9 @@ Using the automatic sequencer to package your apps provides: - Automatic virtual machine (VM) provisioning of the sequencing environment. The process for this is covered in this topic. -- Batch-sequencing of packages. This means that multiple apps can be sequenced at the same time, in a single group. For info about this, see [Automatically sequence multiple apps at the same time](appv-auto-batch-sequencing.md) +- Batch-sequencing of packages. This means that multiple apps can be sequenced at the same time, in a single group. For info about this, see [Automatically sequence multiple apps at the same time](appv-auto-batch-sequencing.md). -- Batch-updating of packages. This means that multiple apps can be updated at the same time, in a single group. For info about this, see [Automatically update multiple apps at the same time](appv-auto-batch-updating.md) +- Batch-updating of packages. This means that multiple apps can be updated at the same time, in a single group. For info about this, see [Automatically update multiple apps at the same time](appv-auto-batch-updating.md). ## Automatic VM provisioning of the sequencing environment You have 2 options for provisioning an VM for auto-sequencing: @@ -121,6 +121,7 @@ The 2 types of provisioning log files, located at “%temp%\AutoSequencer\Logs - **New-AppVSequencerVM-report-.txt**: Includes info about the connections made to the VM, showing whether there were any failures. + ### Related topics - [Download the Convert-WindowsImage tool](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) @@ -132,7 +133,7 @@ The 2 types of provisioning log files, located at “%temp%\AutoSequencer\Logs - [Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) -**Have a suggestion for App-V?** +**Have a suggestion for App-V?**

Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). From defc104cc18fbec92851ffeef7cf9d12cc4c372b Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 1 Feb 2017 12:54:08 -0800 Subject: [PATCH 15/76] Adding content --- windows/manage/TOC.md | 2 +- windows/manage/appv-auto-batch-sequencing.md | 30 ++++++------------- ...app.md => appv-auto-sequence-a-new-app.md} | 7 ++--- ...istory-for-manage-and-update-windows-10.md | 6 ++-- 4 files changed, 16 insertions(+), 29 deletions(-) rename windows/manage/{appv-automatic-sequence-a-new-app.md => appv-auto-sequence-a-new-app.md} (96%) diff --git a/windows/manage/TOC.md b/windows/manage/TOC.md index 853e71ae8d..92487184f3 100644 --- a/windows/manage/TOC.md +++ b/windows/manage/TOC.md @@ -111,7 +111,7 @@ ### [Operations for App-V](appv-operations.md) #### [Creating and Managing App-V Virtualized Applications](appv-creating-and-managing-virtualized-applications.md) ##### [Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) -##### [Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-automatic-sequence-a-new-app.md) +##### [Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-sequence-a-new-app.md) ###### [Automatically sequence multiple apps at the same time](appv-auto-batch-sequencing.md) ###### [Automatically update multiple apps at the same time](appv-auto-batch-updating.md) ##### [How to Modify an Existing Virtual Application Package](appv-modify-an-existing-virtual-application-package.md) diff --git a/windows/manage/appv-auto-batch-sequencing.md b/windows/manage/appv-auto-batch-sequencing.md index 10fa90119e..de052ec26f 100644 --- a/windows/manage/appv-auto-batch-sequencing.md +++ b/windows/manage/appv-auto-batch-sequencing.md @@ -1,6 +1,6 @@ --- -title: Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10) -description: How to automatically sequence a new app using the App-V Sequencer +title: Automatically sequence multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10) +description: How to automatically sequence multiple apps at the same time using the Microsoft Application Virtualization Sequencer. author: eross-msft ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -9,28 +9,18 @@ ms.prod: w10 --- -# Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) +# Automatically sequence multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer) **Applies to** - Windows 10, version 1703 -Previous versions of the App-V Sequencer have required you to manually sequence your app packages. This was time-consuming and required extensive interaction, causing many companies to deploy brand-new packages rather than update an existing one. Windows 10, version 1703 introduces an updated App-V Sequencer that automatically sequences your app packages, improving your overall experience by streamlining the provisioning of the prerequisite environment, automating app installation, and expediting the package updating setup. - -Using the automatic sequencer to package your apps provides: - -- Automatic virtual machine (VM) provisioning of the sequencing environment. The process for this is covered in this topic. - -- Batch-sequencing of packages. This means that multiple apps can be sequenced at the same time, in a single group. For info about this, see ... - -- Batch-updating of packages. This means that multiple apps can be updated at the same time, in a single group. For info about this, see ... - -## Automatic VM provisioning of the sequencing environment -You have 2 options for provisioning an VM for auto-sequencing: -- Using a Virtual Hard Disk (VHD) +Sequencing multiple apps at the same time +There are 2 approaches to sequencing multiple apps at the same time: +- Using a cmdlet in PowerShell -OR- -- Updating an existing VM +- Using the UI provided by the App-V Sequencer ### Provision a new VM by using a VHD file Provisioning your new VM includes creating a VHD file, setting up a user account, turning on remote PowerShell scripting, and installing the App-V Sequencer. @@ -132,7 +122,5 @@ The 2 types of provisioning log files, located at “%temp%\AutoSequencer\Logs - [Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) -**Have a suggestion for App-V?** - -Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). - +**Have a suggestion for App-V?**

+Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). \ No newline at end of file diff --git a/windows/manage/appv-automatic-sequence-a-new-app.md b/windows/manage/appv-auto-sequence-a-new-app.md similarity index 96% rename from windows/manage/appv-automatic-sequence-a-new-app.md rename to windows/manage/appv-auto-sequence-a-new-app.md index 40ed2c4e0e..820a341c6b 100644 --- a/windows/manage/appv-automatic-sequence-a-new-app.md +++ b/windows/manage/appv-auto-sequence-a-new-app.md @@ -20,9 +20,9 @@ Using the automatic sequencer to package your apps provides: - Automatic virtual machine (VM) provisioning of the sequencing environment. The process for this is covered in this topic. -- Batch-sequencing of packages. This means that multiple apps can be sequenced at the same time, in a single group. For info about this, see [Automatically sequence multiple apps at the same time](appv-auto-batch-sequencing.md). +- Batch-sequencing of packages. This means that multiple apps can be sequenced at the same time, in a single group. For info about this, see [Automatically sequence multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md). -- Batch-updating of packages. This means that multiple apps can be updated at the same time, in a single group. For info about this, see [Automatically update multiple apps at the same time](appv-auto-batch-updating.md). +- Batch-updating of packages. This means that multiple apps can be updated at the same time, in a single group. For info about this, see [Automatically update multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md). ## Automatic VM provisioning of the sequencing environment You have 2 options for provisioning an VM for auto-sequencing: @@ -135,5 +135,4 @@ The 2 types of provisioning log files, located at “%temp%\AutoSequencer\Logs **Have a suggestion for App-V?**

-Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). - +Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). \ No newline at end of file diff --git a/windows/manage/change-history-for-manage-and-update-windows-10.md b/windows/manage/change-history-for-manage-and-update-windows-10.md index 63da032a1f..2cd08ffa41 100644 --- a/windows/manage/change-history-for-manage-and-update-windows-10.md +++ b/windows/manage/change-history-for-manage-and-update-windows-10.md @@ -17,9 +17,9 @@ This topic lists new and updated topics in the [Manage and update Windows 10](in ## February 2017 | New or changed topic | Description | | --- | --- | -|[Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-automatic-sequence-a-new-app.md) |New | -|[Automatically sequence multiple apps at the same time](appv-auto-batch-sequencing.md) |New | -|[Automatically update multiple apps at the same time](appv-auto-batch-updating.md) |New | +|[Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-sequence-a-new-app.md) |New | +|[Automatically sequence multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) |New | +|[Automatically update multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) |New | |[](appv-template-improvements.md) |New | ## January 2017 From fa4dd07071c9b0147272f665490b27bb63f21e6b Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 1 Feb 2017 14:58:08 -0800 Subject: [PATCH 16/76] Adding content --- windows/manage/appv-auto-batch-sequencing.md | 194 ++++++++++-------- .../manage/appv-auto-sequence-a-new-app.md | 2 +- 2 files changed, 112 insertions(+), 84 deletions(-) diff --git a/windows/manage/appv-auto-batch-sequencing.md b/windows/manage/appv-auto-batch-sequencing.md index de052ec26f..052ab1e0fa 100644 --- a/windows/manage/appv-auto-batch-sequencing.md +++ b/windows/manage/appv-auto-batch-sequencing.md @@ -1,6 +1,6 @@ --- title: Automatically sequence multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10) -description: How to automatically sequence multiple apps at the same time using the Microsoft Application Virtualization Sequencer. +description: How to automatically sequence multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer). author: eross-msft ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -14,113 +14,141 @@ ms.prod: w10 **Applies to** - Windows 10, version 1703 -Sequencing multiple apps at the same time +Sequencing apps requires you to install and start the Microsoft Application Virtualization Sequencer (App-V Sequencer), install the necessary apps, and to collect any changes made to the operating system during the installation and building of the App-V package. + There are 2 approaches to sequencing multiple apps at the same time: + - Using a cmdlet in PowerShell -OR- -- Using the UI provided by the App-V Sequencer +- Using the user-interface provided by the App-V Sequencer -### Provision a new VM by using a VHD file -Provisioning your new VM includes creating a VHD file, setting up a user account, turning on remote PowerShell scripting, and installing the App-V Sequencer. +### Sequence multiple apps by using a PowerShell cmdlet +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 sequencing cmdlet to start the VM at a "clean" checkpoint, to copy the installer from the Host device to the VM by using the `copy-item` command, and then starting the App-V Sequencer and your specified app installations. -#### Create a VHD file -For this process to work, you must have a base operating system available as a VHD image file, we recommend using the [Convert-WindowsImage.ps1](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) command-line tool. +**To create your ConfigFile for use by the PowerShell cmdlet** +1. Determine the apps that need to be included in your App-V sequencing package, and then open a text editor, such as Notepad. -**To create a VHD file by using the Convert-WindowsImage command-line tool** -1. Open PowerShell as an admin and run the Convert-WindowsImage tool, using the following commands: +2. Add the following XML info for each app: + + - **<Name>.** The name of the app you're adding to the package. + + - **<InstallerFolder>.** The file path to the folder with the app installer. + + - **<Installer>.** The file name for the app executable. This will typically be an .exe or .msi file. + + - **<InstallerOptions>.** The command-line options required for the app installation. This only applies to cmdlet sequencing, it doesn't apply if you use the App-V Sequencer interface. [Liz] What are the options here? + + - **<TimeoutInMinutes>.** The maximum time interval 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. [Liz] Is this optional? + + - **<Cmdlet>.** 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 UI. You can use both the cmdlet and the UI together in the same ConfigFile, for different apps. + + - **<Enabled>.** Allows the app to be sequenced by either the cmdlet or the App-V Sequencer interface. [Liz] Guessing. This wasn't called out in the text. + + **Example:** + + ```XML + + + + Notepad + C:\Windows + notepad.exe + /S + 20 + True + True + + + Word 2016 + C:\Program Files (x86)\Microsoft Office\root\Office16 + winword.exe + /S + 20 + True + True + + + + ``` +3. Save your completed file, using the name **ConfigFile**. + + +### 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. + +**To 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 XML info for each app: + + - **<Name>.** The name of the app you're adding to the package. + + - **<InstallerFolder>.** The file path to the folder with the app installer. + + - **<Installer>.** The file name for the app executable. This will typically be an .exe or .msi file. + + - **<TimeoutInMinutes>.** The maximum time interval 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. [Liz] Is this optional? + + - **<Cmdlet>.** 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 UI. You can use both the cmdlet and the UI together in the same ConfigFile, for different apps. + + - **<Enabled>.** Allows the app to be sequenced by either the cmdlet or the App-V Sequencer UI. [Liz] Guessing. This wasn't called out in the text. + + **Example:** + + ```XML + + + + Notepad + C:\Windows + notepad.exe + 20 + False + True + + + Word 2016 + C:\Program Files (x86)\Microsoft Office\root\Office16 + winword.exe + 20 + False + True + + + + ``` +**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: ```ps1 - Convert-WindowsImage -SourcePath "" -VHDFormat "VHD" -VHDPartitionStyle "MBR" + New-BatchAppVSequencerPackages –ConfigFile –VMName -OutputPath ``` - Where _SourcePath_ is the full file path to your ISO image, _VHDFormat_ is *VHD*, and _VHDPartitionStyle_ is *MBR*. - - >[!IMPORTANT] - >You must specify the _VHDPartitionStyle_ as **MBR**. Using the default value, **GPT**, will cause a boot failure in your VHD image. + Where _VMName_ is the name of the virtual machine (VM) where you'll run the batch sequencing and _OutputPath_ is the full file path to where the sequenced packages should be copied. -#### Provision your VM using your VHD file -After you have a VHD file, you must provision your VM for auto-sequencing. + The cmdlet creates a "clean" checkpoint on the VM, the first app installer listed in the ConfigFile is copied from the Host computer to the VM, and then a new session of the VM opens and the App-V Sequencer is started so you can start the sequencing process. After completing all of the app sequencing and package creation for the first app on the VM, you'll be prompted in the PowerShell window to provide the full file path to the output folder on the Host computer, where the final package is copied. The cmdlet then goes to the second app on your list, reverting the VM back to a "clean" checkpoint and then running through all of the steps again, until the final package is copied to your output folder. This continues until all of the apps included in your list are done. After the last app, the VM is reverted back to a "clean" checkpoint and turned off. [Liz] Didn't they put the output location into the command in step 1? Why do they need to put it there AND in the prompt? -**To provision your VM using your VHD file** -1. On the Host device, install Windows 10, version 1703 and the matching ADK version, making sure that you've selected to install the **Microsoft Application Virtualization (App-V) Auto Sequencer** component. +### Review the log files +There are 3 types of log files that occur when you sequence multiple apps at the same time: - >[!NOTE] - >The App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md). +- **“%temp%\AutoSequencer\Logs” – ‘New-BatchAppVSequencerPackages-

Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). \ No newline at end of file diff --git a/windows/manage/appv-auto-sequence-a-new-app.md b/windows/manage/appv-auto-sequence-a-new-app.md index 820a341c6b..f9a419d461 100644 --- a/windows/manage/appv-auto-sequence-a-new-app.md +++ b/windows/manage/appv-auto-sequence-a-new-app.md @@ -1,6 +1,6 @@ --- title: Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10) -description: How to automatically sequence a new app using the App-V Sequencer +description: How to automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer). author: eross-msft ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy From 7616e6bbd73d784a24cddf4e741f55cc8f869262 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 1 Feb 2017 15:01:13 -0800 Subject: [PATCH 17/76] Adding content --- windows/manage/appv-auto-batch-sequencing.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/windows/manage/appv-auto-batch-sequencing.md b/windows/manage/appv-auto-batch-sequencing.md index 052ab1e0fa..0ed14629fd 100644 --- a/windows/manage/appv-auto-batch-sequencing.md +++ b/windows/manage/appv-auto-batch-sequencing.md @@ -74,6 +74,9 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFile ``` 3. Save your completed file, using the name **ConfigFile**. +**To start the App-V Sequencer interface and app installation process** +[Liz] Text here + ### 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. From 13dbedf182fbce082f1efe190ee5dabdf8d9fe03 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Thu, 2 Feb 2017 09:09:14 -0800 Subject: [PATCH 18/76] Adding content --- windows/manage/appv-auto-batch-sequencing.md | 32 +++++++++++-------- .../manage/appv-auto-sequence-a-new-app.md | 6 ++-- 2 files changed, 21 insertions(+), 17 deletions(-) diff --git a/windows/manage/appv-auto-batch-sequencing.md b/windows/manage/appv-auto-batch-sequencing.md index 0ed14629fd..ade2dfc301 100644 --- a/windows/manage/appv-auto-batch-sequencing.md +++ b/windows/manage/appv-auto-batch-sequencing.md @@ -8,7 +8,6 @@ ms.sitesec: library ms.prod: w10 --- - # Automatically sequence multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer) **Applies to** @@ -38,13 +37,13 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFile - **<Installer>.** The file name for the app executable. This will typically be an .exe or .msi file. - - **<InstallerOptions>.** The command-line options required for the app installation. This only applies to cmdlet sequencing, it doesn't apply if you use the App-V Sequencer interface. [Liz] What are the options here? + - **<InstallerOptions>.** The command-line options required for the app installation. This only applies to cmdlet sequencing, it doesn't apply if you use the App-V Sequencer interface. - - **<TimeoutInMinutes>.** The maximum time interval 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. [Liz] Is this optional? + - **<TimeoutInMinutes>.** The maximum time interval 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. - - **<Cmdlet>.** 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 UI. You can use both the cmdlet and the UI together in the same ConfigFile, for different apps. + - **<Cmdlet>.** 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. - - **<Enabled>.** Allows the app to be sequenced by either the cmdlet or the App-V Sequencer interface. [Liz] Guessing. This wasn't called out in the text. + - **<Enabled>.** Allows the app to be sequenced by either the cmdlet or the App-V Sequencer interface. **Example:** @@ -75,9 +74,15 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFile 3. Save your completed file, using the name **ConfigFile**. **To start the App-V Sequencer interface and app installation process** -[Liz] Text here +- Open PowerShell as an admin on the Host computer and run the following commands to start the batch sequencing: + ```ps1 + New-BatchAppVSequencerPackages –ConfigFile –VMName -OutputPath + ``` + Where _VMName_ is the name of the virtual machine (VM) where you'll run the batch sequencing and _OutputPath_ is the full file path to where the sequenced packages should be copied. + The cmdlet creates a "clean" checkpoint on the VM, the first app installer listed in the ConfigFile is copied from the Host computer to the VM, and then a new session of the VM opens (through VMConnect) and sequencing of the app begins from the command-line. After completing all of the app 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. @@ -92,11 +97,11 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFIle - **<Installer>.** The file name for the app executable. This will typically be an .exe or .msi file. - - **<TimeoutInMinutes>.** The maximum time interval 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. [Liz] Is this optional? + - **<TimeoutInMinutes>.** The maximum time interval 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. - - **<Cmdlet>.** 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 UI. You can use both the cmdlet and the UI together in the same ConfigFile, for different apps. + - **<Cmdlet>.** 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. - - **<Enabled>.** Allows the app to be sequenced by either the cmdlet or the App-V Sequencer UI. [Liz] Guessing. This wasn't called out in the text. + - **<Enabled>.** Allows the app to be sequenced by either the cmdlet or the App-V Sequencer interface. **Example:** @@ -130,17 +135,16 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFIle ``` Where _VMName_ is the name of the virtual machine (VM) where you'll run the batch sequencing and _OutputPath_ is the full file path to where the sequenced packages should be copied. - The cmdlet creates a "clean" checkpoint on the VM, the first app installer listed in the ConfigFile is copied from the Host computer to the VM, and then a new session of the VM opens and the App-V Sequencer is started so you can start the sequencing process. After completing all of the app sequencing and package creation for the first app on the VM, you'll be prompted in the PowerShell window to provide the full file path to the output folder on the Host computer, where the final package is copied. The cmdlet then goes to the second app on your list, reverting the VM back to a "clean" checkpoint and then running through all of the steps again, until the final package is copied to your output folder. This continues until all of the apps included in your list are done. After the last app, the VM is reverted back to a "clean" checkpoint and turned off. [Liz] Didn't they put the output location into the command in step 1? Why do they need to put it there AND in the prompt? + The cmdlet creates a "clean" checkpoint on the VM, the first app installer listed in the ConfigFile is copied from the Host computer to the VM, and then a new session of the VM opens and the App-V Sequencer is started so you can start the sequencing process. After completing all of the app sequencing and package creation for the first app on the VM, you'll be prompted in the PowerShell window to provide the full file path to the output folder on the Host computer, where the final package is copied. 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: -- **“%temp%\AutoSequencer\Logs” – ‘New-BatchAppVSequencerPackages-

+Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). \ No newline at end of file From d8ef3816817096b028dd11d530acc3291becf7be Mon Sep 17 00:00:00 2001 From: LizRoss Date: Thu, 2 Feb 2017 09:47:41 -0800 Subject: [PATCH 21/76] Fixing formatting --- windows/manage/appv-auto-batch-sequencing.md | 3 +++ windows/manage/appv-auto-batch-updating.md | 2 ++ 2 files changed, 5 insertions(+) diff --git a/windows/manage/appv-auto-batch-sequencing.md b/windows/manage/appv-auto-batch-sequencing.md index fc5aedce2e..4b61892358 100644 --- a/windows/manage/appv-auto-batch-sequencing.md +++ b/windows/manage/appv-auto-batch-sequencing.md @@ -73,6 +73,7 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFile ``` 3. Save your completed file, using the name **ConfigFile**. + **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: @@ -127,6 +128,8 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFIle ``` + + **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: diff --git a/windows/manage/appv-auto-batch-updating.md b/windows/manage/appv-auto-batch-updating.md index 597648b8cd..500841cc92 100644 --- a/windows/manage/appv-auto-batch-updating.md +++ b/windows/manage/appv-auto-batch-updating.md @@ -77,6 +77,7 @@ Updating multipe apps at the same time requires that you create a **ConfigFile** ``` 3. Save your completed file, using the name **ConfigFile**. + **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 updating: @@ -135,6 +136,7 @@ Updating multipe apps at the same time requires that you create a **ConfigFile** ``` + **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 updating: From 91eb655c4fd9e8311867f0f1be3bc1b965a25bec Mon Sep 17 00:00:00 2001 From: LizRoss Date: Thu, 2 Feb 2017 13:34:07 -0800 Subject: [PATCH 22/76] Adding content --- .../appv-create-and-use-a-project-template.md | 24 +-- windows/manage/appv-template-improvements.md | 138 ------------------ ...istory-for-manage-and-update-windows-10.md | 1 - 3 files changed, 13 insertions(+), 150 deletions(-) delete mode 100644 windows/manage/appv-template-improvements.md diff --git a/windows/manage/appv-create-and-use-a-project-template.md b/windows/manage/appv-create-and-use-a-project-template.md index c6a0be63bb..c41b4723f2 100644 --- a/windows/manage/appv-create-and-use-a-project-template.md +++ b/windows/manage/appv-create-and-use-a-project-template.md @@ -1,28 +1,30 @@ --- -title: How to Create and Use a Project Template (Windows 10) -description: How to Create and Use a Project Template -author: MaggiePucciEvans +title: Create and apply an App-V project template to a sequenced App-V package (Windows 10) +description: Steps for how to create and apply an App-V project template (.appvt) to a sequenced App-V package. +author: eross-msft ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 --- - -# How to Create and Use a Project Template +# Create and apply an App-V project template to a sequenced App-V package **Applies to** -- Windows 10, version 1607 +- Windows 10, version 1703 -You can use an App-V project template to save commonly applied settings associated with an existing virtual application package. These settings can then be applied when you create new virtual application packages in your environment. Using a project template can streamline the process of creating virtual application packages. +Starting with Windows 10, version 1703, you can save an App-V project template (.appvt) file as part of a sequenced App-V package, so it's automatically loaded every time the package opens for editing or updates. Your template can include general option settings, file exclusion list settings, and target operating system settings. -> **Note**  You can, and often should apply an App-V project template during a package upgrade. For example, if you sequenced an application with a custom exclusion list, it is recommended that an associated template is created and saved for later use while upgrading the sequenced application. +>[!NOTE] +>App-V project templates differ from App-V Package Accelerators because App-V Package Accelerators are application-specific, while App-V project templates can be applied to multiple applications. For more info about Package Accelerators, see the [How to create a Package Accelerator](appv-create-a-package-accelerator) topic. -App-V project templates differ from App-V Application Accelerators because App-V Application Accelerators are application-specific, and App-V project templates can be applied to multiple applications. -Use the following procedures to create and apply a new template. -**To create a project template** + + + +## Create a project template + 1. To start the App-V sequencer, on the computer that is running the sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**. diff --git a/windows/manage/appv-template-improvements.md b/windows/manage/appv-template-improvements.md deleted file mode 100644 index 10fa90119e..0000000000 --- a/windows/manage/appv-template-improvements.md +++ /dev/null @@ -1,138 +0,0 @@ ---- -title: Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10) -description: How to automatically sequence a new app using the App-V Sequencer -author: eross-msft -ms.pagetype: mdop, appcompat, virtualization -ms.mktglfcycl: deploy -ms.sitesec: library -ms.prod: w10 ---- - - -# Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) - -**Applies to** -- Windows 10, version 1703 - -Previous versions of the App-V Sequencer have required you to manually sequence your app packages. This was time-consuming and required extensive interaction, causing many companies to deploy brand-new packages rather than update an existing one. Windows 10, version 1703 introduces an updated App-V Sequencer that automatically sequences your app packages, improving your overall experience by streamlining the provisioning of the prerequisite environment, automating app installation, and expediting the package updating setup. - -Using the automatic sequencer to package your apps provides: - -- Automatic virtual machine (VM) provisioning of the sequencing environment. The process for this is covered in this topic. - -- Batch-sequencing of packages. This means that multiple apps can be sequenced at the same time, in a single group. For info about this, see ... - -- Batch-updating of packages. This means that multiple apps can be updated at the same time, in a single group. For info about this, see ... - -## Automatic VM provisioning of the sequencing environment -You have 2 options for provisioning an VM for auto-sequencing: -- Using a Virtual Hard Disk (VHD) - - -OR- - -- Updating an existing VM - -### Provision a new VM by using a VHD file -Provisioning your new VM includes creating a VHD file, setting up a user account, turning on remote PowerShell scripting, and installing the App-V Sequencer. - -#### Create a VHD file -For this process to work, you must have a base operating system available as a VHD image file, we recommend using the [Convert-WindowsImage.ps1](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) command-line tool. - -**To create a VHD file by using the Convert-WindowsImage command-line tool** -1. Open PowerShell as an admin and run the Convert-WindowsImage tool, using the following commands: - - ```ps1 - Convert-WindowsImage -SourcePath "" -VHDFormat "VHD" -VHDPartitionStyle "MBR" - ``` - Where _SourcePath_ is the full file path to your ISO image, _VHDFormat_ is *VHD*, and _VHDPartitionStyle_ is *MBR*. - - >[!IMPORTANT] - >You must specify the _VHDPartitionStyle_ as **MBR**. Using the default value, **GPT**, will cause a boot failure in your VHD image. - -#### Provision your VM using your VHD file -After you have a VHD file, you must provision your VM for auto-sequencing. - -**To provision your VM using your VHD file** -1. On the Host device, install Windows 10, version 1703 and the matching ADK version, making sure that you've selected to install the **Microsoft Application Virtualization (App-V) Auto Sequencer** component. - - >[!NOTE] - >The App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md). - -2. Make sure that Hyper-V is turned on. For more info about turning on and using Hyper-V, see [Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server). - -3. Open PowerShell as an admin and run the **New-AppVSequencerVM** cmdlet, using the following parameters: - - ```ps1 - New-AppVSequencerVM -VMName "" -ADKPath "" -VHDPath "" -VMMemory -VMSwitch "" - ``` - - Where you create a unique name for your VM, ensure that the VHD file and matching ADK tools are located on the Host device and referenced in the _ADKPath_ and the _VHDPath_ parameters, determine the amount of memory to be allocated for use by your VM, and provide the name of your network switch. - -A new Hyper-V VM file is created out of the provisioned VHD, creating a "clean" checkpoint, from where all of the sequencing and updating will start. - - -### Provision an existing VM for auto-sequencing -If your apps require custom prerequesites, such as Microsoft SQL Server, we recommend that you preinstall the prerequisites on your VM and then use that VM for auto-sequencing. Using these steps will establish a connection to your existing VM, install the Microsoft Application Virtualization (App-V) Auto Sequencer from the ADK tools, and provision your VM for auto-sequencing. - -**To connect to your existing VM** -- Open PowerShell as an admin and run the following commands on your existing VM: - - - **Set the network category of your connection profile on the VM to _Private_:** - - ```ps1 - Get-netconnectionprofile | set-netconnectionprofile -NetworkCategory Private - ``` - - - **Set the Windows Firewall rules for the display groups, _Remote Desktop_ and _Windows Remote Management_:** - - ```ps1 - Enable-NetFirewallRule -DisplayGroup “Remote Desktop” - Enable-NetFirewallRule -DisplayGroup “Windows Remote Management” - ``` - - - **Set the VM to receive remote commands without a confirmation prompt:** - - ```ps1 - Enable-PSRemoting –Force - ``` - - These commands turn on [PowerShell Remoting](https://msdn.microsoft.com/powershell/reference/5.1/Microsoft.PowerShell.Core/about/about_Remote) and turn on the necessary Windows Firewall rules so you can connect to your VM. - -**To provision an existing VM** -1. On the Host device, install Windows 10, version 1703 and the matching ADK version, making sure that you've selected to install the **Microsoft Application Virtualization (App-V) Auto Sequencer** component. - - >[!NOTE] - >The App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md). - -2. Open PowerShell as an admin and run the **New-AppVSequencerVM** cmdlet, using the following parameters: - - ```ps1 - New-AppVSequencerVM -VMName "" -VMComputerName "" -ADKPath "" - ``` - - Where _VMName_ is the name of the VM granted during its creation and shown in the Hyper-V Manager tool, and the _VMComputerName_ is the name of the VM, assigned after its creation and shown on the **Computer name** field of the **System Properties** screen. - -A new Hyper-V VM file is created from the existing VM, creating a "clean" checkpoint, from where all of the sequencing and updating will start. - -### Review the provisioning log files -The 2 types of provisioning log files, located at “%temp%\AutoSequencer\Logs”, are: - -- **New-AppVSequencerVM-.txt**: Includes info about the provisioning activities, such as "Waiting for VM session", "Copying installer for Sequencer", and so on. - -- **New-AppVSequencerVM-report-.txt**: Includes info about the connections made to the VM, showing whether there were any failures. - -### Related topics -- [Download the Convert-WindowsImage tool](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) - -- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit) - -- [How to install the App-V Sequencer](appv-install-the-sequencer.md) - -- [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server) - -- [Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) - -**Have a suggestion for App-V?** - -Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). - diff --git a/windows/manage/change-history-for-manage-and-update-windows-10.md b/windows/manage/change-history-for-manage-and-update-windows-10.md index cace61015e..eba1115bb3 100644 --- a/windows/manage/change-history-for-manage-and-update-windows-10.md +++ b/windows/manage/change-history-for-manage-and-update-windows-10.md @@ -21,7 +21,6 @@ This topic lists new and updated topics in the [Manage and update Windows 10](in |[Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-sequence-a-new-app.md) |New | |[Automatically sequence multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) |New | |[Automatically update multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) |New | -|[](appv-template-improvements.md) |New | ## January 2017 From 5d712f4b38d5aa02e766f0346fcaf6819ae49ab8 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Thu, 2 Feb 2017 14:24:21 -0800 Subject: [PATCH 23/76] Updating based on feedback --- windows/manage/appv-auto-batch-sequencing.md | 16 ++++++++-------- windows/manage/appv-auto-batch-updating.md | 12 ++++++------ 2 files changed, 14 insertions(+), 14 deletions(-) diff --git a/windows/manage/appv-auto-batch-sequencing.md b/windows/manage/appv-auto-batch-sequencing.md index 4b61892358..98d6dc29ce 100644 --- a/windows/manage/appv-auto-batch-sequencing.md +++ b/windows/manage/appv-auto-batch-sequencing.md @@ -29,7 +29,7 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFile **To create your ConfigFile for use by the PowerShell cmdlet** 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 XML info for each app: +2. Add the following required XML info for each app: - **<Name>.** The name of the app you're adding to the package. @@ -37,13 +37,13 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFile - **<Installer>.** The file name for the app executable. This will typically be an .exe or .msi file. - - **<InstallerOptions>.** The command-line options required for the app installation. + - **<InstallerOptions>.** The command-line options required for the app installation. - - **<TimeoutInMinutes>.** The maximum time interval 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. + - **<TimeoutInMinutes>.** The maximum time interval 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. - **<Cmdlet>.** Determines whether the sequencer uses the cmdlet or the App-V Sequencer interface. **True** tells the sequencer to use 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. - - **<Enabled>.** Allows the app to be sequenced by either the cmdlet or the App-V Sequencer interface. + - **<Enabled>.** Indicates whether the app is included in the batch process. You can include as many apps as you want in the batch file, but optionally enable only a few of them. **Example:** @@ -90,7 +90,7 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFIle **To 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 XML info for each app: +2. Add the following required XML info for each app: - **<Name>.** The name of the app you're adding to the package. @@ -98,11 +98,11 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFIle - **<Installer>.** The file name for the app executable. This will typically be an .exe or .msi file. - - **<TimeoutInMinutes>.** The maximum time interval 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. + - **<TimeoutInMinutes>.** The maximum time interval 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. - **<Cmdlet>.** 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. - - **<Enabled>.** Allows the app to be sequenced by either the cmdlet or the App-V Sequencer interface. + - **<Enabled>.** Indicates whether the app is included in the batch process. You can include as many apps as you want in the batch file, but optionally enable only a few of them. **Example:** @@ -138,7 +138,7 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFIle ``` Where _VMName_ is the name of the virtual machine (VM) where you'll run the batch sequencing and _OutputPath_ is the full file path to where the sequenced packages should be copied. - The cmdlet creates a "clean" checkpoint on the VM, the first app installer listed in the ConfigFile is copied from the Host computer to the VM, and then a new session of the VM opens and the App-V Sequencer is started so you can start the sequencing process. After completing all of the app sequencing and package creation for the first app on the VM, you'll be prompted in the PowerShell window to provide the full file path to the output folder on the Host computer, where the final package is copied. 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. + The cmdlet creates a "clean" checkpoint on the VM, the first app installer listed in the ConfigFile is copied from the Host computer to the VM, and then a new session of the VM opens and the App-V Sequencer is started so you can start the sequencing process. After completing all of the app sequencing and package creation for the first app on the VM, you'll be prompted in the PowerShell window to provide the full file path to the output folder on the Host computer, where the final package is copied. 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: diff --git a/windows/manage/appv-auto-batch-updating.md b/windows/manage/appv-auto-batch-updating.md index 500841cc92..eb414c9535 100644 --- a/windows/manage/appv-auto-batch-updating.md +++ b/windows/manage/appv-auto-batch-updating.md @@ -37,15 +37,15 @@ Updating multipe apps at the same time requires that you create a **ConfigFile** - **<Installer>.** The file name for the app executable. This will typically be an .exe or .msi file. - - **<InstallerOptions>.** The command-line options required for the app installation. + - **<InstallerOptions>.** The command-line options required for the app installation. - **<Package>.** The file path to the location of your App-V packages. These packages were created when you sequenced your apps. - - **<TimeoutInMinutes>.** The maximum time interval that the cmdlet should wait for updating to complete. You can enter a different value for each app, based on the size and complexity of the app itself. + - **<TimeoutInMinutes>.** The maximum time interval that the cmdlet should wait for updating to complete. You can enter a different value for each app, based on the size and complexity of the app itself. - **<Cmdlet>.** Determines whether the sequencer uses the cmdlet or the App-V Sequencer interface. **True** tells the sequencer to use cmdlet-based updating, 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. - - **<Enabled>.** Allows the app to be updated by either the cmdlet or the App-V Sequencer interface. + - **<Enabled>.** AIndicates whether the app is included in the batch process. You can include as many apps as you want in the batch file, but optionally enable only a few of them. **Example:** @@ -104,11 +104,11 @@ Updating multipe apps at the same time requires that you create a **ConfigFile** - **<Package>.** The file path to the location of your App-V packages. These packages were created when you sequenced your apps. - - **<TimeoutInMinutes>.** The maximum time interval that the cmdlet should wait for updating to complete. You can enter a different value for each app, based on the size and complexity of the app itself. + - **<TimeoutInMinutes>.** The maximum time interval that the cmdlet should wait for updating to complete. You can enter a different value for each app, based on the size and complexity of the app itself. - **<Cmdlet>.** Determines whether the sequencer uses the cmdlet or the App-V Sequencer interface. **True** tells the sequencer to usea cmdlet-based updating, 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. - - **<Enabled>.** Allows the app to be updated by either the cmdlet or the App-V Sequencer interface. + - **<Enabled>.** Indicates whether the app is included in the batch process. You can include as many apps as you want in the batch file, but optionally enable only a few of them. **Example:** @@ -145,7 +145,7 @@ Updating multipe apps at the same time requires that you create a **ConfigFile** ``` Where _VMName_ is the name of the virtual machine (VM) where you'll run the batch updating and _OutputPath_ is the full file path to where the updated packages should be copied. - The cmdlet creates a "clean" checkpoint on the VM, the first app installer listed in the ConfigFile is copied from the Host computer to the VM, and then a new session of the VM opens and the App-V Sequencer is started so you can start the updating process. After completing all of the app updating and package creation for the first app on the VM, you'll be prompted in the PowerShell window to provide the full file path to the output folder on the Host computer, where the final package is copied. 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. + The cmdlet creates a "clean" checkpoint on the VM, the first app installer listed in the ConfigFile is copied from the Host computer to the VM, and then a new session of the VM opens and the App-V Sequencer is started so you can start the updating process. After completing all of the app updating and package creation for the first app on the VM, you'll be prompted in the PowerShell window to provide the full file path to the output folder on the Host computer, where the final package is copied. 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: From 039380f94cd9063c97ae60cee93557d968dff612 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Thu, 2 Feb 2017 14:33:04 -0800 Subject: [PATCH 24/76] Fixed broken link --- windows/manage/appv-create-and-use-a-project-template.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/manage/appv-create-and-use-a-project-template.md b/windows/manage/appv-create-and-use-a-project-template.md index c41b4723f2..c24bf3c6ba 100644 --- a/windows/manage/appv-create-and-use-a-project-template.md +++ b/windows/manage/appv-create-and-use-a-project-template.md @@ -16,7 +16,7 @@ ms.prod: w10 Starting with Windows 10, version 1703, you can save an App-V project template (.appvt) file as part of a sequenced App-V package, so it's automatically loaded every time the package opens for editing or updates. Your template can include general option settings, file exclusion list settings, and target operating system settings. >[!NOTE] ->App-V project templates differ from App-V Package Accelerators because App-V Package Accelerators are application-specific, while App-V project templates can be applied to multiple applications. For more info about Package Accelerators, see the [How to create a Package Accelerator](appv-create-a-package-accelerator) topic. +>App-V project templates differ from App-V Package Accelerators because App-V Package Accelerators are application-specific, while App-V project templates can be applied to multiple applications. For more info about Package Accelerators, see the [How to create a Package Accelerator](appv-create-a-package-accelerator.md) topic. From 2b936175eb1ac2717e4625d7080a33e6b559d604 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Fri, 3 Feb 2017 13:53:28 -0800 Subject: [PATCH 25/76] Editing based on tech review --- windows/manage/appv-auto-batch-sequencing.md | 44 +++++++------- windows/manage/appv-auto-batch-updating.md | 62 ++++++++++---------- 2 files changed, 53 insertions(+), 53 deletions(-) diff --git a/windows/manage/appv-auto-batch-sequencing.md b/windows/manage/appv-auto-batch-sequencing.md index 98d6dc29ce..9210cdf5ec 100644 --- a/windows/manage/appv-auto-batch-sequencing.md +++ b/windows/manage/appv-auto-batch-sequencing.md @@ -13,7 +13,7 @@ ms.prod: w10 **Applies to** - Windows 10, version 1703 -Sequencing apps requires you to install and start the Microsoft Application Virtualization Sequencer (App-V Sequencer), install the necessary apps, and to collect any changes made to the operating system during the installation and building of the App-V package. +Sequencing apps requires you to install and start the Microsoft Application Virtualization Sequencer (App-V Sequencer), and to install the necessary apps to collect any changes made to the operating system during the installation and building of the App-V package. There are 2 approaches to sequencing multiple apps at the same time: @@ -24,7 +24,7 @@ There are 2 approaches to sequencing multiple apps at the same time: - Using the user-interface provided by the App-V Sequencer ### Sequence multiple apps by using a PowerShell cmdlet -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 sequencing cmdlet to start the VM at a "clean" checkpoint, to copy the installer from the Host device to the VM by using the `copy-item` command, and then starting the App-V Sequencer and your specified app installations. +Sequencing multiple apps at the same time requires that you create a **ConfigFile** with info related to each round of sequencing. This file is then used by the cmdlet to start the VM at a "clean" checkpoint, to copy the installer from the Host device to the VM, and then to start the App-V Sequencer to monitor your specified app installations. **To create your ConfigFile for use by the PowerShell cmdlet** 1. Determine the apps that need to be included in your App-V sequencing package, and then open a text editor, such as Notepad. @@ -39,11 +39,11 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFile - **<InstallerOptions>.** The command-line options required for the app installation. - - **<TimeoutInMinutes>.** The maximum time interval 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. + - **<TimeoutInMinutes>.** 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. - **<Cmdlet>.** Determines whether the sequencer uses the cmdlet or the App-V Sequencer interface. **True** tells the sequencer to use 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. - - **<Enabled>.** Indicates whether the app is included in the batch process. You can include as many apps as you want in the batch file, but optionally enable only a few of them. + - **<Enabled>.** 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:** @@ -51,18 +51,18 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFile - Notepad - C:\Windows - notepad.exe + Skype + Need to get + Need to get /S 20 True True - Word 2016 - C:\Program Files (x86)\Microsoft Office\root\Office16 - winword.exe + Power BI + Need to get + Need to get /S 20 True @@ -80,9 +80,9 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFile ```ps1 New-BatchAppVSequencerPackages –ConfigFile –VMName -OutputPath ``` - Where _VMName_ is the name of the virtual machine (VM) where you'll run the batch sequencing and _OutputPath_ is the full file path to where the sequenced packages should be copied. + Where _VMName_ is the name of the virtual machine (VM) with the App-V Sequencer installed, where you'll run the batch sequencing, and _OutputPath_ is the full path to where the sequenced packages should be copied. - The cmdlet creates a "clean" checkpoint on the VM, the first app installer listed in the ConfigFile is copied from the Host computer to the VM, and then a new session of the VM opens (through VMConnect) and sequencing of the app begins from the command-line. After completing all of the app 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. + 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. @@ -98,11 +98,11 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFIle - **<Installer>.** The file name for the app executable. This will typically be an .exe or .msi file. - - **<TimeoutInMinutes>.** The maximum time interval 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. + - **<TimeoutInMinutes>.** 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. - **<Cmdlet>.** 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. - - **<Enabled>.** Indicates whether the app is included in the batch process. You can include as many apps as you want in the batch file, but optionally enable only a few of them. + - **<Enabled>.** 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:** @@ -110,17 +110,17 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFIle - Notepad - C:\Windows - notepad.exe + Skype + Need to get + Need to get 20 False True - Word 2016 - C:\Program Files (x86)\Microsoft Office\root\Office16 - winword.exe + Power BI + Need to get + Need to get 20 False True @@ -136,9 +136,9 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFIle ```ps1 New-BatchAppVSequencerPackages –ConfigFile –VMName -OutputPath ``` - Where _VMName_ is the name of the virtual machine (VM) where you'll run the batch sequencing and _OutputPath_ is the full file path to where the sequenced packages should be copied. + Where _VMName_ is the name of the virtual machine (VM) with the App-V Sequencer installed, where you'll run the batch sequencing, and _OutputPath_ is the full path to where the sequenced packages should be copied. - The cmdlet creates a "clean" checkpoint on the VM, the first app installer listed in the ConfigFile is copied from the Host computer to the VM, and then a new session of the VM opens and the App-V Sequencer is started so you can start the sequencing process. After completing all of the app sequencing and package creation for the first app on the VM, you'll be prompted in the PowerShell window to provide the full file path to the output folder on the Host computer, where the final package is copied. 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. + 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: diff --git a/windows/manage/appv-auto-batch-updating.md b/windows/manage/appv-auto-batch-updating.md index eb414c9535..82eb64a999 100644 --- a/windows/manage/appv-auto-batch-updating.md +++ b/windows/manage/appv-auto-batch-updating.md @@ -24,7 +24,7 @@ There are 2 approaches to updating multiple apps at the same time: - Using the user-interface provided by the App-V Sequencer ### Update multiple apps by using a PowerShell cmdlet -Updating multipe apps at the same time requires that you create a **ConfigFile** to collect all of the info related to each round of updating. This file is then used by the App-V Sequencer cmdlet to start the VM at a "clean" checkpoint, to copy the installer from the Host device to the VM by using the `copy-item` command, and then starting the App-V Sequencer and your specified app installations. +Updating multiple apps at the same time requires that you create a **ConfigFile** with info related to each round of updating. This file is then used by the cmdlet to start the VM at a "clean" checkpoint, to copy the installer from the Host device to the VM, and then to start the App-V Sequencer to monitor your specified app installations. **To create your ConfigFile for use by the PowerShell cmdlet** 1. Determine the apps that need to be included in your app package, and then open a text editor, such as Notepad. @@ -41,40 +41,40 @@ Updating multipe apps at the same time requires that you create a **ConfigFile** - **<Package>.** The file path to the location of your App-V packages. These packages were created when you sequenced your apps. - - **<TimeoutInMinutes>.** The maximum time interval that the cmdlet should wait for updating to complete. You can enter a different value for each app, based on the size and complexity of the app itself. + - **<TimeoutInMinutes>.** The maximum amount of time, in minutes, that the cmdlet should wait for updating to complete. You can enter a different value for each app, based on the size and complexity of the app itself. - **<Cmdlet>.** Determines whether the sequencer uses the cmdlet or the App-V Sequencer interface. **True** tells the sequencer to use cmdlet-based updating, 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. - - **<Enabled>.** AIndicates whether the app is included in the batch process. You can include as many apps as you want in the batch file, but optionally enable only a few of them. + - **<Enabled>.** 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 - Notepad_Update - C:\Windows - notepad.exe - /S - C:\App-V_Packages\Microsoft_Apps\notepad.appv + Skype_Update + Need to get + Need to get + /S + C:\App-V_Packages\Microsoft_Apps\skype_update.appv 20 True True - Word 2016 - C:\Program Files (x86)\Microsoft Office\root\Office16 - winword.exe + Power BI + Need to get + Need to get /S - C:\App-V_Packages\Microsoft_Apps\winword.appv + C:\App-V_Packages\Microsoft_Apps\power_bi_update.appv 20 True True - ``` + ``` + 3. Save your completed file, using the name **ConfigFile**. @@ -84,9 +84,9 @@ Updating multipe apps at the same time requires that you create a **ConfigFile** ```ps1 New-BatchAppVSequencerPackages –ConfigFile –VMName -OutputPath ``` - Where _VMName_ is the name of the virtual machine (VM) where you'll run the batch updating and _OutputPath_ is the full file path to where the updated packages should be copied. + Where _VMName_ is the name of the virtual machine (VM) with the App-V Sequencer installed, where you'll run the batch updating, and _OutputPath_ is the full path to where the updated packages should be copied. - The cmdlet creates a "clean" checkpoint on the VM, the first app installer listed in the ConfigFile is copied from the Host computer to the VM, and then a new session of the VM opens (through VMConnect) and updating of the app begins from the command-line. After completing all of the updating 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. + 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 updating of the app begins from the command-line. After completing updating 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. ### Update multiple apps by using the App-V Sequencer interface Updating multipe apps at the same time requires that you create a **ConfigFile** to collect all of the info related to each round of updating. This file is then used by the App-V Sequencer interface after creating a "clean" checkpoint on your VM. @@ -104,11 +104,11 @@ Updating multipe apps at the same time requires that you create a **ConfigFile** - **<Package>.** The file path to the location of your App-V packages. These packages were created when you sequenced your apps. - - **<TimeoutInMinutes>.** The maximum time interval that the cmdlet should wait for updating to complete. You can enter a different value for each app, based on the size and complexity of the app itself. + - **<TimeoutInMinutes>.** The maximum amount of time, in minutes, the cmdlet should wait for updating to complete. You can enter a different value for each app, based on the size and complexity of the app itself. - **<Cmdlet>.** Determines whether the sequencer uses the cmdlet or the App-V Sequencer interface. **True** tells the sequencer to usea cmdlet-based updating, 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. - - **<Enabled>.** Indicates whether the app is included in the batch process. You can include as many apps as you want in the batch file, but optionally enable only a few of them. + - **<Enabled>.** 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:** @@ -116,21 +116,21 @@ Updating multipe apps at the same time requires that you create a **ConfigFile** - Notepad_Update - C:\Windows - notepad.exe - C:\App-V_Packages\Microsoft_Apps\notepad.appv + Skype_Update + Need to get + Need to get + C:\App-V_Packages\Microsoft_Apps\skype_update.appv 20 - True + False True - Word 2016 - C:\Program Files (x86)\Microsoft Office\root\Office16 - winword.exe - C:\App-V_Packages\Microsoft_Apps\winword.appv + Power BI + Need to get + Need to get + C:\App-V_Packages\Microsoft_Apps\power_bi_update.appv 20 - True + False True @@ -143,11 +143,11 @@ Updating multipe apps at the same time requires that you create a **ConfigFile** ```ps1 New-BatchAppVSequencerPackages –ConfigFile –VMName -OutputPath ``` - Where _VMName_ is the name of the virtual machine (VM) where you'll run the batch updating and _OutputPath_ is the full file path to where the updated packages should be copied. + Where _VMName_ is the name of the virtual machine (VM) with the App-V Sequencer installed, where you'll run the batch updating, and _OutputPath_ is the full path to where the updated packages should be copied. - The cmdlet creates a "clean" checkpoint on the VM, the first app installer listed in the ConfigFile is copied from the Host computer to the VM, and then a new session of the VM opens and the App-V Sequencer is started so you can start the updating process. After completing all of the app updating and package creation for the first app on the VM, you'll be prompted in the PowerShell window to provide the full file path to the output folder on the Host computer, where the final package is copied. 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. + 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 updating of the app begins from the command-line. After completing updating 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 +### Review the log files There are 3 types of log files that occur when you sequence multiple apps at the same time: - **New-BatchAppVSequencerPackages-

+Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). \ No newline at end of file diff --git a/windows/manage/change-history-for-manage-and-update-windows-10.md b/windows/manage/change-history-for-manage-and-update-windows-10.md index eba1115bb3..9c6db63732 100644 --- a/windows/manage/change-history-for-manage-and-update-windows-10.md +++ b/windows/manage/change-history-for-manage-and-update-windows-10.md @@ -21,6 +21,7 @@ This topic lists new and updated topics in the [Manage and update Windows 10](in |[Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-sequence-a-new-app.md) |New | |[Automatically sequence multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) |New | |[Automatically update multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) |New | +|[Automatically clean-up unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md) ## January 2017 From 0e069ef892526107bceda79493a7d0bb61903886 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Tue, 7 Feb 2017 12:39:24 -0800 Subject: [PATCH 33/76] Adding clean-up topic --- windows/manage/TOC.md | 1 + 1 file changed, 1 insertion(+) diff --git a/windows/manage/TOC.md b/windows/manage/TOC.md index 92487184f3..ce6f92f788 100644 --- a/windows/manage/TOC.md +++ b/windows/manage/TOC.md @@ -144,6 +144,7 @@ ##### [How to deploy App-V Packages Using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md) ##### [How to Enable Only Administrators to Publish Packages by Using an ESD](appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md) #### [Using the App-V Client Management Console](appv-using-the-client-management-console.md) +##### [Automatically clean-up unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md) #### [Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md) ##### [How to Convert a Package Created in a Previous Version of App-V](appv-convert-a-package-created-in-a-previous-version-of-appv.md) #### [Maintaining App-V](appv-maintaining-appv.md) From ecded17dc023ce317150058ea9a572b279544de1 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Tue, 7 Feb 2017 13:36:53 -0800 Subject: [PATCH 34/76] Adding content --- .../appv-auto-clean-unpublished-packages.md | 48 +++++++++++++++++-- .../manage/appv-auto-sequence-a-new-app.md | 3 ++ ...istory-for-manage-and-update-windows-10.md | 2 +- 3 files changed, 49 insertions(+), 4 deletions(-) diff --git a/windows/manage/appv-auto-clean-unpublished-packages.md b/windows/manage/appv-auto-clean-unpublished-packages.md index 044ee60e31..92fa4efcd9 100644 --- a/windows/manage/appv-auto-clean-unpublished-packages.md +++ b/windows/manage/appv-auto-clean-unpublished-packages.md @@ -1,5 +1,5 @@ --- -title: Automatically clean-up unpublished packages on the App-V client (Windows 10) +title: Automatically cleanup unpublished packages on the App-V client (Windows 10) description: How to automatically clean-up any unpublished packages on your App-V client devices. author: eross-msft ms.pagetype: mdop, appcompat, virtualization @@ -9,15 +9,57 @@ ms.prod: w10 --- -# Automatically clean-up unpublished packages on the App-V client +# Automatically cleanup unpublished packages on the App-V client **Applies to** - Windows 10, version 1703 -## Clean-up by using PowerShell commands +Previous versions of App-V have required you to manually remove your unpublished packages from your client devices, to free up additional storage space. Windows 10, version 1703 introduces the ability to use PowerShell or Group Policy settings to automatically cleanup your unpublished packages after a device restart. + +## Cleanup by using PowerShell commands +Using PowerShell, you can turn on the **AutoCleanupEnabled** setting to automatically cleanup your unpublished App-V packages from your App-V client devices. + +**To turn on the AutoCleanupEnabled option** +1. Open PowerShell as an admin and run the following command to turn on the automatic package cleanup functionality: + + ```ps1 + Set-AppvClientConfiguration -AutoCleanupEnabled 1 + ``` + The command runs and you should see the following info on the PowerShell screen: + + + + + + + + + + + + + + + + +
NameValueSetbyGroupPolicy
AutoCleanupEnabled1False
+ +2. Run the following command to make sure the packages were successfully cleaned up. + + ```ps1 + Get-AppvClientConfiguration + ``` + You should see the **AutoCleanupEnabled** option turned on (shows a value of "1") in the configuration list. ## Clean-up by using Group Policy settings +Using Group Policy, you can turn on the **Enable automatic cleanup of unused appv packages** setting to automatically cleanup your unpublished App-V packages from your App-V client devices. +**To turn on the Enable automatic cleanup of unused appv packages setting** +1. Open your Group Policy editor and double-click the Administrative Templates\System\App-V\PackageManagement\Enable automatic cleanup of unused appv packages setting. + +2.Click **Enabled**, and then click **OK**. + + The setting is turned on and will cleanup any unpublished App-V packages on the App-V Client after restarting. ### Related topics - [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit) diff --git a/windows/manage/appv-auto-sequence-a-new-app.md b/windows/manage/appv-auto-sequence-a-new-app.md index 5bc2efe524..0bfc73261f 100644 --- a/windows/manage/appv-auto-sequence-a-new-app.md +++ b/windows/manage/appv-auto-sequence-a-new-app.md @@ -32,6 +32,9 @@ You have 2 options for provisioning an VM for auto-sequencing: - Updating an existing VM + >[!NOTE] + >We have reduced the number of environmental checks performed by the App-V Sequencer, narrowing down the list of apps that need to be disabled or turned off for a clean sequencing experience. We've also suppressed antivirus and other similar app warnings. + ### Provision a new VM by using a VHD file Provisioning your new VM includes creating a VHD file, setting up a user account, turning on remote PowerShell scripting, and installing the App-V Sequencer. diff --git a/windows/manage/change-history-for-manage-and-update-windows-10.md b/windows/manage/change-history-for-manage-and-update-windows-10.md index 9c6db63732..e206f0a086 100644 --- a/windows/manage/change-history-for-manage-and-update-windows-10.md +++ b/windows/manage/change-history-for-manage-and-update-windows-10.md @@ -21,7 +21,7 @@ This topic lists new and updated topics in the [Manage and update Windows 10](in |[Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-sequence-a-new-app.md) |New | |[Automatically sequence multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) |New | |[Automatically update multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) |New | -|[Automatically clean-up unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md) +|[Automatically clean-up unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md) |New | ## January 2017 From 1900fd67b62af098fd389df8d94cfd2fd1bf965c Mon Sep 17 00:00:00 2001 From: LizRoss Date: Tue, 7 Feb 2017 13:42:39 -0800 Subject: [PATCH 35/76] Adding content --- windows/manage/appv-auto-clean-unpublished-packages.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/windows/manage/appv-auto-clean-unpublished-packages.md b/windows/manage/appv-auto-clean-unpublished-packages.md index 92fa4efcd9..bf540c31f7 100644 --- a/windows/manage/appv-auto-clean-unpublished-packages.md +++ b/windows/manage/appv-auto-clean-unpublished-packages.md @@ -57,12 +57,17 @@ Using Group Policy, you can turn on the **Enable automatic cleanup of unused app **To turn on the Enable automatic cleanup of unused appv packages setting** 1. Open your Group Policy editor and double-click the Administrative Templates\System\App-V\PackageManagement\Enable automatic cleanup of unused appv packages setting. -2.Click **Enabled**, and then click **OK**. +2. Click **Enabled**, and then click **OK**. The setting is turned on and will cleanup any unpublished App-V packages on the App-V Client after restarting. ### Related topics - [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit) +- [Download the Microsoft Application Virtualization 5.0 Client UI Application](https://www.microsoft.com/en-us/download/details.aspx?id=41186) + +- [Using the App-V Client Management Console](appv-using-the-client-management-console.md) + + **Have a suggestion for App-V?**

Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). \ No newline at end of file From d14b88d61101c720e7068b5ee0e9d646a9c1ec1e Mon Sep 17 00:00:00 2001 From: LizRoss Date: Tue, 7 Feb 2017 14:52:00 -0800 Subject: [PATCH 36/76] Adding content --- windows/manage/appv-auto-batch-sequencing.md | 2 +- .../appv-create-and-use-a-project-template.md | 44 ++++++++++--------- 2 files changed, 25 insertions(+), 21 deletions(-) diff --git a/windows/manage/appv-auto-batch-sequencing.md b/windows/manage/appv-auto-batch-sequencing.md index bede5e7435..0b95054cf3 100644 --- a/windows/manage/appv-auto-batch-sequencing.md +++ b/windows/manage/appv-auto-batch-sequencing.md @@ -158,7 +158,7 @@ There are 3 types of log files that occur when you sequence multiple apps at the - [Automatically sequence a single app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-sequence-a-new-app.md) -- [Manually sequence a single app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) [Liz] Do we want to continue to point to the manual steps? Is there a reason to do one over the other? +- [Manually sequence a single app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) **Have a suggestion for App-V?**

Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). \ No newline at end of file diff --git a/windows/manage/appv-create-and-use-a-project-template.md b/windows/manage/appv-create-and-use-a-project-template.md index c24bf3c6ba..b165db3a88 100644 --- a/windows/manage/appv-create-and-use-a-project-template.md +++ b/windows/manage/appv-create-and-use-a-project-template.md @@ -18,40 +18,44 @@ Starting with Windows 10, version 1703, you can save an App-V project template ( >[!NOTE] >App-V project templates differ from App-V Package Accelerators because App-V Package Accelerators are application-specific, while App-V project templates can be applied to multiple applications. For more info about Package Accelerators, see the [How to create a Package Accelerator](appv-create-a-package-accelerator.md) topic. - - - - - ## Create a project template +You must first create and save a project template, including a virtual app package with settings to be used by the template. +1. On the device running the App-V Sequencer, click **Start**, click **All Programs**, click **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**. -1. To start the App-V sequencer, on the computer that is running the sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**. + >[!NOTE] + >If the virtual app package is currently open in the App-V Sequencer console, skip to Step 3 of this procedure. - > **Note**  If the virtual application package is currently open in the App-V Sequencer console, skip to step 3 of this procedure. +2. On the **File** menu, click **Open**, click **Edit Package**, browse for the virtual app package that includes the settings you want to save with the App-V project template, and then click **Edit**. -2. To open the existing virtual application package that contains the settings you want to save with the App-V project template, click **File** / **Open**, and then click **Edit Package**. On the **Select Package** page, click **Browse** and locate the virtual application package that you want to open. Click **Edit**. +-- What happens in between here? You've said you want to edit your package and then you want to save your template file. This feels like there's something missing. What are you editing? -- -3. In the App-V Sequencer console, to save the template file, click **File** / **Save As Template**. After you have reviewed the settings that will be saved with the new template, click **OK**. Specify a name that will be associated with the new App-V project template. Click Save. +3. On the **File** menu, click **Save As Template**, review the settings associated with the new template, click **OK**, name your new template, and then click **Save**. The new App-V project template is saved in the folder you specified. -**To apply a project template** +## Apply a project template +After creating the template, you can apply it to all of your new virtual app packages, automatically including all of the settings. -> **Important**  Creating a virtual application package using a project template in conjunction with a Package Accelerator is not supported. +>[!IMPORTANT] +>Virtual app packages don't support using both a project template and a Package Accelerator together. -1. To start the App-V sequencer, on the computer that is running the sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**. +1. On the device running the App-V Sequencer, click **Start**, click **All Programs**, click **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**. -2. To create or upgrade a new virtual application package by using an App-V project template, click **File** / **New From Template**. +2. On the **File** menu, click **New From Template**, browse to your newly created project template, and then click **Open**. -3. To select the project template that you want to use, browse to the directory where the project template is saved, select the project template, and then click **Open**. +3. Create your new virtual app package. The settings saved with your template are automatically applied. - Create the new virtual application package. The settings saved with the specified template will be applied to the new virtual application package that you are creating. +### Related topics +- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit) -## Have a suggestion for App-V? +- [How to install the App-V Sequencer](appv-install-the-sequencer.md) +- [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server) + +- [Automatically sequence a single app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-sequence-a-new-app.md) + +- [Manually sequence a single app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) [Liz] Do we want to continue to point to the manual steps? Is there a reason to do one over the other? + +**Have a suggestion for App-V?**

Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). - -## Related topics - -[Operations for App-V](appv-operations.md) From 65fba7cbd0b254a09b8f077cafb96665b3d9938d Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 8 Feb 2017 10:03:36 -0800 Subject: [PATCH 37/76] Adding content --- windows/manage/appv-auto-batch-sequencing.md | 9 ++++++++- windows/manage/appv-auto-batch-updating.md | 12 ++++++++++++ windows/manage/appv-auto-sequence-a-new-app.md | 6 ++++++ 3 files changed, 26 insertions(+), 1 deletion(-) diff --git a/windows/manage/appv-auto-batch-sequencing.md b/windows/manage/appv-auto-batch-sequencing.md index 0b95054cf3..a45578c76b 100644 --- a/windows/manage/appv-auto-batch-sequencing.md +++ b/windows/manage/appv-auto-batch-sequencing.md @@ -23,6 +23,9 @@ There are 2 approaches to sequencing multiple apps at the same time: - Using the user-interface provided by the App-V Sequencer +>[!NOTE] +If you're trying to update multiple apps at the same time, see the [Automatically update multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) topic. + ### Sequence multiple apps by using a PowerShell cmdlet Sequencing multiple apps at the same time requires that you create a **ConfigFile** with info related to each round of sequencing. This file is then used by the cmdlet to start the VM at a "clean" checkpoint, to copy the installer from the Host device to the VM, and then to start the App-V Sequencer to monitor your specified app installations. @@ -156,9 +159,13 @@ There are 3 types of log files that occur when you sequence multiple apps at the - [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server) -- [Automatically sequence a single app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-sequence-a-new-app.md) +- [Automatic VM provisioning of the sequencing environment](appv-auto-sequence-a-new-app.md) - [Manually sequence a single app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) +- [Automatically update multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) + +- [Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md) + **Have a suggestion for App-V?**

Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). \ No newline at end of file diff --git a/windows/manage/appv-auto-batch-updating.md b/windows/manage/appv-auto-batch-updating.md index 4dfb8879aa..37180d0140 100644 --- a/windows/manage/appv-auto-batch-updating.md +++ b/windows/manage/appv-auto-batch-updating.md @@ -23,9 +23,13 @@ There are 2 approaches to updating multiple apps at the same time: - Using the user-interface provided by the App-V Sequencer +>[!NOTE] +If you're trying to sequence multiple apps at the same time, see the [Automatically sequence multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) topic. + ### Update multiple apps by using a PowerShell cmdlet Updating multiple apps at the same time requires that you create a **ConfigFile** with info related to each round of updating. This file is then used by the cmdlet to start the VM at a "clean" checkpoint, to copy the installer from the Host device to the VM, and then to start the App-V Sequencer to monitor your specified app installations. + **To create your ConfigFile for use by the PowerShell cmdlet** 1. Determine the apps that need to be included in your app package, and then open a text editor, such as Notepad. @@ -165,6 +169,14 @@ There are 3 types of log files that occur when you sequence multiple apps at the - [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server) +- [Automatic VM provisioning of the sequencing environment](appv-auto-sequence-a-new-app.md) + +- [Manually sequence a single app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) + +- [Automatically sequence multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) + +- [Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md) + **Have a suggestion for App-V?**

Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). \ No newline at end of file diff --git a/windows/manage/appv-auto-sequence-a-new-app.md b/windows/manage/appv-auto-sequence-a-new-app.md index 0bfc73261f..b5a448f343 100644 --- a/windows/manage/appv-auto-sequence-a-new-app.md +++ b/windows/manage/appv-auto-sequence-a-new-app.md @@ -136,6 +136,12 @@ The 2 types of provisioning log files, located at %temp%\AutoSequencer\Logs, are - [Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) +- [Automatically sequence multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) + +- [Automatically update multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) + +- [Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md) + **Have a suggestion for App-V?**

Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). \ No newline at end of file From 09eec572225134c739cc8fec38ab3d4e80b2c0b8 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 8 Feb 2017 11:17:57 -0800 Subject: [PATCH 38/76] Adding content from tech review --- .../manage/appv-auto-sequence-a-new-app.md | 37 +++++++------------ 1 file changed, 14 insertions(+), 23 deletions(-) diff --git a/windows/manage/appv-auto-sequence-a-new-app.md b/windows/manage/appv-auto-sequence-a-new-app.md index b5a448f343..3c95e5f6d0 100644 --- a/windows/manage/appv-auto-sequence-a-new-app.md +++ b/windows/manage/appv-auto-sequence-a-new-app.md @@ -14,15 +14,15 @@ ms.prod: w10 **Applies to** - Windows 10, version 1703 -Previous versions of the App-V Sequencer have required you to manually sequence your app packages. This was time-consuming and required extensive interaction, causing many companies to deploy brand-new packages rather than update an existing one. Windows 10, version 1703 introduces an updated App-V Sequencer that automatically sequences your app packages, improving your overall experience by streamlining the provisioning of the prerequisite environment, automating app installation, and expediting the package updating setup. +Previous versions of the App-V Sequencer have required you to manually sequence and update your app packages. This was time-consuming and required extensive interaction, causing many companies to deploy brand-new packages rather than update an existing one. Windows 10, version 1703 introduces the App-V Auto-Sequencer, which automatically sequences your app packages, improving your overall experience by streamlining the provisioning of the prerequisite environment, automating app installation, and expediting the package updating setup. Using the automatic sequencer to package your apps provides: - Automatic virtual machine (VM) provisioning of the sequencing environment. The process for this is covered in this topic. -- Batch-sequencing of packages. This means that multiple apps can be sequenced at the same time, in a single group. For info about this, see [Automatically sequence multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md). +- Batch-sequencing of packages. This means that multiple apps can be sequenced at the same time, in a single group. For info about this, see [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md). -- Batch-updating of packages. This means that multiple apps can be updated at the same time, in a single group. For info about this, see [Automatically update multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md). +- Batch-updating of packages. This means that multiple apps can be updated at the same time, in a single group. For info about this, see [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md). ## Automatic VM provisioning of the sequencing environment You have 2 options for provisioning an VM for auto-sequencing: @@ -56,10 +56,7 @@ For this process to work, you must have a base operating system available as a V After you have a VHD file, you must provision your VM for auto-sequencing. **To provision your VM using your VHD file** -1. On the Host device, install Windows 10, version 1703 and the matching ADK version, making sure that you've selected to install the **Microsoft Application Virtualization (App-V) Auto Sequencer** component. - - >[!NOTE] - >The App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md). +1. On the Host device, install Windows 10, version 1703 and the **Microsoft Application Virtualization (App-V) Auto Sequencer** component from the matching version of the Windows Assessment and Deployment Kit (ADK). For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md). 2. Make sure that Hyper-V is turned on. For more info about turning on and using Hyper-V, see [Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server). @@ -69,13 +66,11 @@ After you have a VHD file, you must provision your VM for auto-sequencing. New-AppVSequencerVM -VMName "" -ADKPath "" -VHDPath "" -VMMemory -VMSwitch "" ``` - Where you create a unique name for your VM, ensure that the VHD file and matching ADK tools are located on the Host device and referenced in the _ADKPath_ and the _VHDPath_ parameters, determine the amount of memory to be allocated for use by your VM, and provide the name of your network switch. - -A new Hyper-V VM file is created out of the provisioned VHD, creating a "clean" checkpoint, from where all of the sequencing and updating will start. +This command creates a new Hyper-V VM file using the provided VHD file and also creates a "clean" checkpoint, from where all sequencing and updating will start. ### Provision an existing VM for auto-sequencing -If your apps require custom prerequesites, such as Microsoft SQL Server, we recommend that you preinstall the prerequisites on your VM and then use that VM for auto-sequencing. Using these steps will establish a connection to your existing VM, install the Microsoft Application Virtualization (App-V) Auto Sequencer from the ADK tools, and provision your VM for auto-sequencing. +If your apps require custom prerequisites, such as Microsoft SQL Server, we recommend that you preinstall the prerequisites on your VM and then use that VM for auto-sequencing. Using these steps will establish a connection to your existing VM. **To connect to your existing VM** - Open PowerShell as an admin and run the following commands on your existing VM: @@ -86,7 +81,7 @@ If your apps require custom prerequesites, such as Microsoft SQL Server, we reco Get-netconnectionprofile | set-netconnectionprofile -NetworkCategory Private ``` - - **Set the Windows Firewall rules for the display groups, _Remote Desktop_ and _Windows Remote Management_:** + - **Enable firewall rules for _Remote Desktop_ and _Windows Remote Management_:** ```ps1 Enable-NetFirewallRule -DisplayGroup “Remote Desktop” @@ -99,30 +94,26 @@ If your apps require custom prerequesites, such as Microsoft SQL Server, we reco Enable-PSRemoting –Force ``` - These commands turn on [PowerShell Remoting](https://msdn.microsoft.com/powershell/reference/5.1/Microsoft.PowerShell.Core/about/about_Remote) and turn on the necessary Windows Firewall rules so you can connect to your VM. - **To provision an existing VM** -1. On the Host device, install Windows 10, version 1703 and the matching ADK version, making sure that you've selected to install the **Microsoft Application Virtualization (App-V) Auto Sequencer** component. +1. On the Host device, install Windows 10, version 1703 and the **Microsoft Application Virtualization (App-V) Auto Sequencer** component from the matching version of the Windows Assessment and Deployment Kit (ADK). For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md). - >[!NOTE] - >The App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md). - -2. Open PowerShell as an admin and run the **New-AppVSequencerVM** cmdlet, using the following parameters: +2. Open PowerShell as an admin and run the **Connect-AppvSequencerVM** cmdlet, using the following parameters: ```ps1 - New-AppVSequencerVM -VMName "" -VMComputerName "" -ADKPath "" + Connect-AppvSequencerVM -VMName "" -ADKPath "" ``` Where _VMName_ is the name of the VM granted during its creation and shown in the Hyper-V Manager tool, and the _VMComputerName_ is the name of the VM, assigned after its creation and shown on the **Computer name** field of the **System Properties** screen. -A new Hyper-V VM file is created from the existing VM, creating a "clean" checkpoint, from where all of the sequencing and updating will start. +This command creates a new Hyper-V VM file using the provided VHD file and also creates a "clean" checkpoint, from where all sequencing and updating will start. + ### Review the provisioning log files The 2 types of provisioning log files, located at %temp%\AutoSequencer\Logs, are: -- **New-AppVSequencerVM-.txt**. Includes info about the provisioning activities, such as "Waiting for VM session", "Copying installer for Sequencer", and so on. +- **New-AppVSequencerVM-<*time_stamp*>.txt**. Includes info about the provisioning activities, such as "Waiting for VM session", "Copying installer for Sequencer", and so on. -- **New-AppVSequencerVM-report-.txt**. Includes info about the connections made to the VM, showing whether there were any failures. +- **Connect-AppvSequencerVM-report-<*time_stamp*>.txt**. Includes info about the connections made to the VM, showing whether there were any failures. ### Related topics From 869306763245e7a81775f3007b90b2aae6500266 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 8 Feb 2017 11:41:40 -0800 Subject: [PATCH 39/76] Adding content --- windows/manage/TOC.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/manage/TOC.md b/windows/manage/TOC.md index ce6f92f788..e6a9eeb85d 100644 --- a/windows/manage/TOC.md +++ b/windows/manage/TOC.md @@ -112,8 +112,8 @@ #### [Creating and Managing App-V Virtualized Applications](appv-creating-and-managing-virtualized-applications.md) ##### [Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) ##### [Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-sequence-a-new-app.md) -###### [Automatically sequence multiple apps at the same time](appv-auto-batch-sequencing.md) -###### [Automatically update multiple apps at the same time](appv-auto-batch-updating.md) +##### [Automatically sequence multiple apps at the same time](appv-auto-batch-sequencing.md) +##### [Automatically update multiple apps at the same time](appv-auto-batch-updating.md) ##### [How to Modify an Existing Virtual Application Package](appv-modify-an-existing-virtual-application-package.md) ##### [How to Create and Use a Project Template](appv-create-and-use-a-project-template.md) ##### [How to Create a Package Accelerator](appv-create-a-package-accelerator.md) From 0210ae630976532a3c8577c6f7795ce6cf2ae35f Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 8 Feb 2017 11:48:03 -0800 Subject: [PATCH 40/76] Adding content --- windows/manage/appv-auto-batch-sequencing.md | 4 ++-- windows/manage/appv-auto-batch-updating.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/manage/appv-auto-batch-sequencing.md b/windows/manage/appv-auto-batch-sequencing.md index a45578c76b..3365ee769a 100644 --- a/windows/manage/appv-auto-batch-sequencing.md +++ b/windows/manage/appv-auto-batch-sequencing.md @@ -146,9 +146,9 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFIle ### Review the log files There are 3 types of log files that occur when you sequence multiple apps at the same time: -- **New-BatchAppVSequencerPackages-

+Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). \ No newline at end of file diff --git a/windows/manage/appv-auto-sequence-a-new-app.md b/windows/manage/appv-auto-sequence-a-new-app.md index 3c95e5f6d0..ccf5008ce5 100644 --- a/windows/manage/appv-auto-sequence-a-new-app.md +++ b/windows/manage/appv-auto-sequence-a-new-app.md @@ -1,6 +1,6 @@ --- -title: Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10) -description: How to automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer). +title: Automatically sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10) +description: How to automatically sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer) PowerShell cmdlet or the user interface. author: eross-msft ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -9,7 +9,7 @@ ms.prod: w10 --- -# Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) +# Automatically sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer) **Applies to** - Windows 10, version 1703 @@ -24,6 +24,8 @@ Using the automatic sequencer to package your apps provides: - Batch-updating of packages. This means that multiple apps can be updated at the same time, in a single group. For info about this, see [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md). +- Automatic template creation. The App-V package template is automatically created when using the automatic App-V Sequencer cmdlet or interface. + ## Automatic VM provisioning of the sequencing environment You have 2 options for provisioning an VM for auto-sequencing: - Using a Virtual Hard Disk (VHD) @@ -47,7 +49,7 @@ For this process to work, you must have a base operating system available as a V ```ps1 Convert-WindowsImage -SourcePath "" -VHDFormat "VHD" -VHDPartitionStyle "MBR" ``` - Where _SourcePath_ is the full path to your ISO image, _VHDFormat_ is *VHD*, and _VHDPartitionStyle_ is *MBR*. + Where _SourcePath_ is the full path to your ISO image, _VHDFormat_ is always *VHD*, and _VHDPartitionStyle_ is always *MBR*. >[!IMPORTANT] >You must specify the _VHDPartitionStyle_ as **MBR**. Using the default value, **GPT**, will cause a boot failure in your VHD image. @@ -125,11 +127,11 @@ The 2 types of provisioning log files, located at %temp%\AutoSequencer\Logs, are - [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server) -- [Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) +- [Manually sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) -- [Automatically sequence multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) +- [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) -- [Automatically update multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) +- [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) - [Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md) diff --git a/windows/manage/appv-release-notes-for-appv-for-windows-1703.md b/windows/manage/appv-release-notes-for-appv-for-windows-1703.md index dc1959c81b..80bca70545 100644 --- a/windows/manage/appv-release-notes-for-appv-for-windows-1703.md +++ b/windows/manage/appv-release-notes-for-appv-for-windows-1703.md @@ -16,9 +16,11 @@ ms.prod: w10 The following are known issues and workarounds for Application Virtualization (App-V) running on Windows 10, version 1703. -|Problem |How you see it |Workaround | -|--------|---------------|-----------| -| +|Problem |Workaround | +|--------|-----------| +|Unable to manually create a system-owned folder needed for the `set-AppVClientConfiguration` PowerShell cmdlet when using the _PackageInstallationRoot_, _IntegrationRootUser_, or _IntegrationRootGlobal_ parameters. |Don't create this file manually, instead let the Add-AppVClientPackage cmdlet auto-generate it. | +|Failure to update an App-V package from App-V 5.0 or App-V 5.1 to the latest version. |Make sure you have the complete App-V package or the MSI file from the original app. | +|Unable to modify the locale for auto-sequencing. |Open the C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\AutoSequencer\Unattend_Sequencer_User_Setup_Template.xml file diff --git a/windows/manage/change-history-for-manage-and-update-windows-10.md b/windows/manage/change-history-for-manage-and-update-windows-10.md index 75be1d1767..eaf7844d8c 100644 --- a/windows/manage/change-history-for-manage-and-update-windows-10.md +++ b/windows/manage/change-history-for-manage-and-update-windows-10.md @@ -20,10 +20,10 @@ This topic lists new and updated topics in the [Manage and update Windows 10](in |[Assign devices to servicing branches for Windows 10 updates](waas-servicing-branches-windows-10-updates.md) | Added Group Policy setting that blocks user access to Windows Update. | |[What's new in App-V for Windows 10, version 1703 and earlier](appv-about-appv.md)|Updated to include new features in App-V for Windows 10, version 1703. | |[Release Notes for App-V for Windows 10, version 1703](appv-release-notes-for-appv-for-windows-1703.md)|New | -|[Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-sequence-a-new-app.md) |New | -|[Automatically sequence multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) |New | -|[Automatically update multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) |New | -|[Automatically clean-up unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md) |New | +|[Automatically sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md) |New | +|[Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) |New | +|[Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) |New | +|[Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md) |New | ## January 2017 From fdfd9b274e5c193d78b46ad14854f22e8697d985 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Thu, 9 Feb 2017 11:55:10 -0800 Subject: [PATCH 47/76] Adding content --- windows/manage/appv-auto-provision-a-vm.md | 140 ------------------ ...release-notes-for-appv-for-windows-1703.md | 15 +- 2 files changed, 2 insertions(+), 153 deletions(-) delete mode 100644 windows/manage/appv-auto-provision-a-vm.md diff --git a/windows/manage/appv-auto-provision-a-vm.md b/windows/manage/appv-auto-provision-a-vm.md deleted file mode 100644 index 914b475a9f..0000000000 --- a/windows/manage/appv-auto-provision-a-vm.md +++ /dev/null @@ -1,140 +0,0 @@ ---- -title: Automatically sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10) -description: How to automatically sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer) PowerShell cmdlet or the user interface. -author: eross-msft -ms.pagetype: mdop, appcompat, virtualization -ms.mktglfcycl: deploy -ms.sitesec: library -ms.prod: w10 ---- - - -# Automatically provision a virtual machine (VM) using Microsoft Application Virtualization Sequencer (App-V Sequencer) - -**Applies to** -- Windows 10, version 1703 - -Previous versions of the App-V Sequencer have required you to manually sequence and update your app packages. This was time-consuming and required extensive interaction, causing many companies to deploy brand-new packages rather than update an existing one. Windows 10, version 1703 introduces the App-V Auto-Sequencer, which automatically sequences your app packages, improving your overall experience by streamlining the provisioning of the prerequisite environment, automating app installation, and expediting the package updating setup. - -Using the automatic sequencer to package your apps provides: - -- Automatic virtual machine (VM) provisioning of the sequencing environment. The process for this is covered in this topic. - -- Batch-sequencing of packages. This means that multiple apps can be sequenced at the same time, in a single group. For info about this, see [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md). - -- Batch-updating of packages. This means that multiple apps can be updated at the same time, in a single group. For info about this, see [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md). - -- Automatic template creation. The App-V package template is automatically created when using the automatic App-V Sequencer cmdlet or interface. - -## Automatic VM provisioning of the sequencing environment -You have 2 options for provisioning an VM for auto-sequencing: -- Using a Virtual Hard Disk (VHD) - - -OR- - -- Updating an existing VM - - >[!NOTE] - >We have reduced the number of environmental checks performed by the App-V Sequencer, narrowing down the list of apps that need to be disabled or turned off for a clean sequencing experience. We've also suppressed antivirus and other similar app warnings. - -### Provision a new VM by using a VHD file -Provisioning your new VM includes creating a VHD file, setting up a user account, turning on remote PowerShell scripting, and installing the App-V Sequencer. - -#### Create a VHD file -For this process to work, you must have a base operating system available as a VHD image file, we recommend using the [Convert-WindowsImage.ps1](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) command-line tool. - -**To create a VHD file by using the Convert-WindowsImage command-line tool** -1. Open PowerShell as an admin and run the Convert-WindowsImage tool, using the following commands: - - ```ps1 - Convert-WindowsImage -SourcePath "" -VHDFormat "VHD" -VHDPartitionStyle "MBR" - ``` - Where _SourcePath_ is the full path to your ISO image, _VHDFormat_ is always *VHD*, and _VHDPartitionStyle_ is always *MBR*. - - >[!IMPORTANT] - >You must specify the _VHDPartitionStyle_ as **MBR**. Using the default value, **GPT**, will cause a boot failure in your VHD image. - -#### Provision your VM using your VHD file -After you have a VHD file, you must provision your VM for auto-sequencing. - -**To provision your VM using your VHD file** -1. On the Host device, install Windows 10, version 1703 and the **Microsoft Application Virtualization (App-V) Auto Sequencer** component from the matching version of the Windows Assessment and Deployment Kit (ADK). For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md). - -2. Make sure that Hyper-V is turned on. For more info about turning on and using Hyper-V, see [Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server). - -3. Open PowerShell as an admin and run the **New-AppVSequencerVM** cmdlet, using the following parameters: - - ```ps1 - New-AppVSequencerVM -VMName "" -ADKPath "" -VHDPath "" -VMMemory -VMSwitch "" - ``` - -This command creates a new Hyper-V VM file using the provided VHD file and also creates a "clean" checkpoint, from where all sequencing and updating will start. - - -### Provision an existing VM for auto-sequencing -If your apps require custom prerequisites, such as Microsoft SQL Server, we recommend that you preinstall the prerequisites on your VM and then use that VM for auto-sequencing. Using these steps will establish a connection to your existing VM. - -**To connect to your existing VM** -- Open PowerShell as an admin and run the following commands on your existing VM: - - - **Set the network category of your connection profile on the VM to _Private_:** - - ```ps1 - Get-netconnectionprofile | set-netconnectionprofile -NetworkCategory Private - ``` - - - **Enable firewall rules for _Remote Desktop_ and _Windows Remote Management_:** - - ```ps1 - Enable-NetFirewallRule -DisplayGroup “Remote Desktop” - Enable-NetFirewallRule -DisplayGroup “Windows Remote Management” - ``` - - - **Set the VM to receive remote commands without a confirmation prompt:** - - ```ps1 - Enable-PSRemoting –Force - ``` - -**To provision an existing VM** -1. On the Host device, install Windows 10, version 1703 and the **Microsoft Application Virtualization (App-V) Auto Sequencer** component from the matching version of the Windows Assessment and Deployment Kit (ADK). For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md). - -2. Open PowerShell as an admin and run the **Connect-AppvSequencerVM** cmdlet, using the following parameters: - - ```ps1 - Connect-AppvSequencerVM -VMName "" -ADKPath "" - ``` - - Where _VMName_ is the name of the VM granted during its creation and shown in the Hyper-V Manager tool, and the _VMComputerName_ is the name of the VM, assigned after its creation and shown on the **Computer name** field of the **System Properties** screen. - -This command creates a new Hyper-V VM file using the provided VHD file and also creates a "clean" checkpoint, from where all sequencing and updating will start. - - -### Review the provisioning log files -The 2 types of provisioning log files, located at %temp%\AutoSequencer\Logs, are: - -- **New-AppVSequencerVM-<*time_stamp*>.txt**. Includes info about the provisioning activities, such as "Waiting for VM session", "Copying installer for Sequencer", and so on. - -- **Connect-AppvSequencerVM-report-<*time_stamp*>.txt**. Includes info about the connections made to the VM, showing whether there were any failures. - - -### Related topics -- [Download the Convert-WindowsImage tool](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) - -- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit) - -- [How to install the App-V Sequencer](appv-install-the-sequencer.md) - -- [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server) - -- [Manually sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) - -- [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) - -- [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) - -- [Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md) - - -**Have a suggestion for App-V?**

-Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). \ No newline at end of file diff --git a/windows/manage/appv-release-notes-for-appv-for-windows-1703.md b/windows/manage/appv-release-notes-for-appv-for-windows-1703.md index 80bca70545..c7ba2dd63f 100644 --- a/windows/manage/appv-release-notes-for-appv-for-windows-1703.md +++ b/windows/manage/appv-release-notes-for-appv-for-windows-1703.md @@ -20,7 +20,8 @@ The following are known issues and workarounds for Application Virtualization (A |--------|-----------| |Unable to manually create a system-owned folder needed for the `set-AppVClientConfiguration` PowerShell cmdlet when using the _PackageInstallationRoot_, _IntegrationRootUser_, or _IntegrationRootGlobal_ parameters. |Don't create this file manually, instead let the Add-AppVClientPackage cmdlet auto-generate it. | |Failure to update an App-V package from App-V 5.0 or App-V 5.1 to the latest version. |Make sure you have the complete App-V package or the MSI file from the original app. | -|Unable to modify the locale for auto-sequencing. |Open the C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\AutoSequencer\Unattend_Sequencer_User_Setup_Template.xml file +|Unable to modify the locale for auto-sequencing. |Open the `C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\AutoSequencer\Unattend_Sequencer_User_Setup_Template.xml` file and include the language code for your locale. | +|Filetype and protocol handlers aren's registering properly with the Google Chrome browser, causing you to not see App-V packages as an option for default apps from the **Settings > Apps> Default Apps** area |[Liz] What is workaround? Using Microsoft Edge? This one is kind of tricky since we usually don't include 3rd party issues in release notes. Do we know of this happening with any other program besides Chrome? | @@ -28,18 +29,6 @@ The following are known issues and workarounds for Application Virtualization (A - - - - - -Deletion of files and registry values is persisted during package updates -Custom shortcuts and FTA(?) are also saved after package updates -Fixed Connection Group issue that affected App-V Server - - -Additional info (not clear on whether we need this or where it would go in the existing structure, it’s from the last TAP release document) - ## Related resources list For information that can help with troubleshooting App-V for Windows 10, see: - [Application Virtualization (App-V): List of Microsoft Support Knowledge Base Articles](http://social.technet.microsoft.com/wiki/contents/articles/14272.app-v-v5-x-list-of-microsoft-support-knowledge-base-articles.aspx) From fa2d1834204442a4d9ffd94448647b130ebadb46 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Thu, 9 Feb 2017 12:00:59 -0800 Subject: [PATCH 48/76] Fixing broken links --- windows/manage/TOC.md | 2 +- .../manage/change-history-for-manage-and-update-windows-10.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/manage/TOC.md b/windows/manage/TOC.md index 53063ef193..dace7dc5c2 100644 --- a/windows/manage/TOC.md +++ b/windows/manage/TOC.md @@ -110,7 +110,7 @@ #### [Deploying Microsoft Office 2010 by Using App-V](appv-deploying-microsoft-office-2010-wth-appv.md) ### [Operations for App-V](appv-operations.md) #### [Creating and Managing App-V Virtualized Applications](appv-creating-and-managing-virtualized-applications.md) -##### [Automatically sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md) +##### [Automatically sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-sequence-a-new-app.md) ##### [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) ##### [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) ##### [Manually sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) diff --git a/windows/manage/change-history-for-manage-and-update-windows-10.md b/windows/manage/change-history-for-manage-and-update-windows-10.md index 7d30310114..baf6308bd2 100644 --- a/windows/manage/change-history-for-manage-and-update-windows-10.md +++ b/windows/manage/change-history-for-manage-and-update-windows-10.md @@ -21,7 +21,7 @@ This topic lists new and updated topics in the [Manage and update Windows 10](in | [Distribute offline apps](distribute-offline-apps.md) | General updates to topic. Added links to supporting content for System Center Configuration Manager and Microsoft Intune. | |[What's new in App-V for Windows 10, version 1703 and earlier](appv-about-appv.md)|Updated to include new features in App-V for Windows 10, version 1703. | |[Release Notes for App-V for Windows 10, version 1703](appv-release-notes-for-appv-for-windows-1703.md)|New | -|[Automatically sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md) |New | +|[Automatically sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-sequence-a-new-app.md) |New | |[Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) |New | |[Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) |New | |[Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md) |New | From 989be0592d0149e2e629eb2138c0d47a642fa86d Mon Sep 17 00:00:00 2001 From: LizRoss Date: Tue, 14 Feb 2017 09:37:00 -0800 Subject: [PATCH 49/76] Fixed typo --- windows/manage/appv-release-notes-for-appv-for-windows-1703.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/manage/appv-release-notes-for-appv-for-windows-1703.md b/windows/manage/appv-release-notes-for-appv-for-windows-1703.md index c7ba2dd63f..37f95b6416 100644 --- a/windows/manage/appv-release-notes-for-appv-for-windows-1703.md +++ b/windows/manage/appv-release-notes-for-appv-for-windows-1703.md @@ -21,7 +21,7 @@ The following are known issues and workarounds for Application Virtualization (A |Unable to manually create a system-owned folder needed for the `set-AppVClientConfiguration` PowerShell cmdlet when using the _PackageInstallationRoot_, _IntegrationRootUser_, or _IntegrationRootGlobal_ parameters. |Don't create this file manually, instead let the Add-AppVClientPackage cmdlet auto-generate it. | |Failure to update an App-V package from App-V 5.0 or App-V 5.1 to the latest version. |Make sure you have the complete App-V package or the MSI file from the original app. | |Unable to modify the locale for auto-sequencing. |Open the `C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\AutoSequencer\Unattend_Sequencer_User_Setup_Template.xml` file and include the language code for your locale. | -|Filetype and protocol handlers aren's registering properly with the Google Chrome browser, causing you to not see App-V packages as an option for default apps from the **Settings > Apps> Default Apps** area |[Liz] What is workaround? Using Microsoft Edge? This one is kind of tricky since we usually don't include 3rd party issues in release notes. Do we know of this happening with any other program besides Chrome? | +|Filetype and protocol handlers aren't registering properly with the Google Chrome browser, causing you to not see App-V packages as an option for default apps from the **Settings > Apps> Default Apps** area |[Liz] What is workaround? Using Microsoft Edge? This one is kind of tricky since we usually don't include 3rd party issues in release notes. Do we know of this happening with any other program besides Chrome? | From db9164fee6e78832573a4d752e990b96310df639 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Tue, 14 Feb 2017 11:48:18 -0800 Subject: [PATCH 50/76] Adding workaround for issue --- ...release-notes-for-appv-for-windows-1703.md | 94 +++++++++++++++++-- 1 file changed, 84 insertions(+), 10 deletions(-) diff --git a/windows/manage/appv-release-notes-for-appv-for-windows-1703.md b/windows/manage/appv-release-notes-for-appv-for-windows-1703.md index 37f95b6416..eeb42371c9 100644 --- a/windows/manage/appv-release-notes-for-appv-for-windows-1703.md +++ b/windows/manage/appv-release-notes-for-appv-for-windows-1703.md @@ -16,17 +16,91 @@ ms.prod: w10 The following are known issues and workarounds for Application Virtualization (App-V) running on Windows 10, version 1703. -|Problem |Workaround | -|--------|-----------| -|Unable to manually create a system-owned folder needed for the `set-AppVClientConfiguration` PowerShell cmdlet when using the _PackageInstallationRoot_, _IntegrationRootUser_, or _IntegrationRootGlobal_ parameters. |Don't create this file manually, instead let the Add-AppVClientPackage cmdlet auto-generate it. | -|Failure to update an App-V package from App-V 5.0 or App-V 5.1 to the latest version. |Make sure you have the complete App-V package or the MSI file from the original app. | -|Unable to modify the locale for auto-sequencing. |Open the `C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\AutoSequencer\Unattend_Sequencer_User_Setup_Template.xml` file and include the language code for your locale. | -|Filetype and protocol handlers aren't registering properly with the Google Chrome browser, causing you to not see App-V packages as an option for default apps from the **Settings > Apps> Default Apps** area |[Liz] What is workaround? Using Microsoft Edge? This one is kind of tricky since we usually don't include 3rd party issues in release notes. Do we know of this happening with any other program besides Chrome? | - - - - + + + + + + + + + + + + + + + + + + + + + + + +
ProblemWorkaround
Unable to manually create a system-owned folder needed for the set-AppVClientConfiguration PowerShell cmdlet when using the PackageInstallationRoot, IntegrationRootUser, or IntegrationRootGlobal parameters.Don't create this file manually, instead let the Add-AppVClientPackage cmdlet auto-generate it.
Failure to update an App-V package from App-V 5.0 or App-V 5.1 to the latest version.Make sure you have the complete App-V package or the MSI file from the original app.
Unable to modify the locale for auto-sequencing.Open the C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\AutoSequencer\Unattend_Sequencer_User_Setup_Template.xml file and include the language code for your locale. For example, if you wanted Spanish (Spain), you'd use: es-ES.
Filetype and protocol handlers aren't registering properly with the Google Chrome browser, causing you to not see App-V packages as an option for default apps from the Settings > Apps> Default Apps area.The recommended workaround is to add the following code to the AppXManifest.xml file, underneath the <appv:Extensions> tag: + 

+                <appv:Extension Category="AppV.URLProtocol">
+                    <appv:URLProtocol>
+                        <appv:Name>ftp</appv:Name>
+                        <appv:ApplicationURLProtocol>
+                            <appv:DefaultIcon>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0</appv:DefaultIcon>
+                            <appv:ShellCommands>
+                                <appv:DefaultCommand>open</appv:DefaultCommand>
+                                <appv:ShellCommand>
+                                    <appv:ApplicationId>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe</appv:ApplicationId>
+                                    <appv:Name>open</appv:Name>
+                                    <appv:CommandLine>"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"</appv:CommandLine>
+                                    <appv:DdeExec>
+                                        <appv:DdeCommand />
+                                    </appv:DdeExec>
+                                </appv:ShellCommand>
+                            </appv:ShellCommands>
+                        </appv:ApplicationURLProtocol>
+                    </appv:URLProtocol>
+                </appv:Extension>
+                <appv:Extension Category="AppV.URLProtocol">
+                    <appv:URLProtocol>
+                        <appv:Name>http</appv:Name>
+                        <appv:ApplicationURLProtocol>
+                            <appv:DefaultIcon>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0</appv:DefaultIcon>
+                            <appv:ShellCommands>
+                                <appv:DefaultCommand>open</appv:DefaultCommand>
+                                <appv:ShellCommand>
+                                    <appv:ApplicationId>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe</appv:ApplicationId>
+                                    <appv:Name>open</appv:Name>
+                                    <appv:CommandLine>"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"</appv:CommandLine>
+                                    <appv:DdeExec>
+                                        <appv:DdeCommand />
+                                    </appv:DdeExec>
+                                </appv:ShellCommand>
+                            </appv:ShellCommands>
+                        </appv:ApplicationURLProtocol>
+                    </appv:URLProtocol>
+                </appv:Extension>
+                <appv:Extension Category="AppV.URLProtocol">
+                    <appv:URLProtocol>
+                        <appv:Name>https</appv:Name>
+                        <appv:ApplicationURLProtocol>
+                            <appv:DefaultIcon>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0</appv:DefaultIcon>
+                            <appv:ShellCommands>
+                                <appv:DefaultCommand>open</appv:DefaultCommand>
+                                <appv:ShellCommand>
+                                    <appv:ApplicationId>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe</appv:ApplicationId>
+                                    <appv:Name>open</appv:Name>
+                                    <appv:CommandLine>"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"</appv:CommandLine>
+                                    <appv:DdeExec>
+                                        <appv:DdeCommand />
+                                    </appv:DdeExec>
+                                </appv:ShellCommand>
+                            </appv:ShellCommands>
+                        </appv:ApplicationURLProtocol>
+                    </appv:URLProtocol>
+                    </appv:Extension>
+
+
## Related resources list From 2056ec61fe2b24057378c73d2c5be0d6f76312ac Mon Sep 17 00:00:00 2001 From: LizRoss Date: Tue, 14 Feb 2017 12:50:12 -0800 Subject: [PATCH 51/76] Fixing code style --- ...release-notes-for-appv-for-windows-1703.md | 119 +++++++++--------- 1 file changed, 59 insertions(+), 60 deletions(-) diff --git a/windows/manage/appv-release-notes-for-appv-for-windows-1703.md b/windows/manage/appv-release-notes-for-appv-for-windows-1703.md index eeb42371c9..1da797cb73 100644 --- a/windows/manage/appv-release-notes-for-appv-for-windows-1703.md +++ b/windows/manage/appv-release-notes-for-appv-for-windows-1703.md @@ -16,7 +16,6 @@ ms.prod: w10 The following are known issues and workarounds for Application Virtualization (App-V) running on Windows 10, version 1703. - @@ -38,65 +37,65 @@ The following are known issues and workarounds for Application Virtualization (A From 714cef859bb73b4c3a959b5d8cfc41c3c657aa51 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Tue, 14 Feb 2017 14:50:29 -0800 Subject: [PATCH 52/76] Editing from tech review --- windows/manage/appv-release-notes-for-appv-for-windows-1703.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/manage/appv-release-notes-for-appv-for-windows-1703.md b/windows/manage/appv-release-notes-for-appv-for-windows-1703.md index 1da797cb73..9e787d612c 100644 --- a/windows/manage/appv-release-notes-for-appv-for-windows-1703.md +++ b/windows/manage/appv-release-notes-for-appv-for-windows-1703.md @@ -27,7 +27,7 @@ The following are known issues and workarounds for Application Virtualization (A - + From bd118e043ed291356a5654889b43a05985c277c3 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 15 Feb 2017 09:56:13 -0800 Subject: [PATCH 53/76] Adding content --- windows/manage/TOC.md | 2 +- windows/manage/appv-about-appv.md | 2 +- windows/manage/appv-auto-batch-sequencing.md | 2 +- windows/manage/appv-auto-batch-updating.md | 2 +- ...new-app.md => appv-auto-provision-a-vm.md} | 31 ++++++------------- .../appv-create-and-use-a-project-template.md | 2 +- ...istory-for-manage-and-update-windows-10.md | 2 +- 7 files changed, 15 insertions(+), 28 deletions(-) rename windows/manage/{appv-auto-sequence-a-new-app.md => appv-auto-provision-a-vm.md} (72%) diff --git a/windows/manage/TOC.md b/windows/manage/TOC.md index 1adfb7d70a..a5969b77d0 100644 --- a/windows/manage/TOC.md +++ b/windows/manage/TOC.md @@ -113,7 +113,7 @@ #### [Deploying Microsoft Office 2010 by Using App-V](appv-deploying-microsoft-office-2010-wth-appv.md) ### [Operations for App-V](appv-operations.md) #### [Creating and Managing App-V Virtualized Applications](appv-creating-and-managing-virtualized-applications.md) -##### [Automatically sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-sequence-a-new-app.md) +##### [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md) ##### [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) ##### [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) ##### [Manually sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) diff --git a/windows/manage/appv-about-appv.md b/windows/manage/appv-about-appv.md index 24929e0f34..9fc61c9b7d 100644 --- a/windows/manage/appv-about-appv.md +++ b/windows/manage/appv-about-appv.md @@ -22,7 +22,7 @@ The following are new features in App-V for Windows 10, version 1703. Previous versions of the App-V Sequencer have required you to manually sequence and update your app packages. This was time-consuming and required extensive interaction, causing many companies to deploy brand-new packages rather than update an existing one. Windows 10, version 1703 introduces the App-V Auto-Sequencer, which automatically sequences your app packages, improving your overall experience by streamlining the provisioning of the prerequisite environment, automating app installation, and expediting the package updating setup. Using the automatic sequencer to package your apps provides: -- Automatic virtual machine (VM) provisioning of the sequencing environment. For info about this, see [Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-sequence-a-new-app.md) +- Automatic virtual machine (VM) provisioning of the sequencing environment. For info about this, see [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md). - Batch-sequencing of packages. This means that multiple apps can be sequenced at the same time, in a single group. For info about this, see [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md). diff --git a/windows/manage/appv-auto-batch-sequencing.md b/windows/manage/appv-auto-batch-sequencing.md index 75fe7d75e7..1e89fe8fb9 100644 --- a/windows/manage/appv-auto-batch-sequencing.md +++ b/windows/manage/appv-auto-batch-sequencing.md @@ -159,7 +159,7 @@ There are 3 types of log files that occur when you sequence multiple apps at the - [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server) -- [Automatic VM provisioning of the sequencing environment](appv-auto-sequence-a-new-app.md) +- [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md) - [Manually sequence a single app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) diff --git a/windows/manage/appv-auto-batch-updating.md b/windows/manage/appv-auto-batch-updating.md index a354113ab8..1be4eb3da8 100644 --- a/windows/manage/appv-auto-batch-updating.md +++ b/windows/manage/appv-auto-batch-updating.md @@ -169,7 +169,7 @@ There are 3 types of log files that occur when you sequence multiple apps at the - [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server) -- [Automatic VM provisioning of the sequencing environment](appv-auto-sequence-a-new-app.md) +- [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md) - [Manually sequence a single app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) diff --git a/windows/manage/appv-auto-sequence-a-new-app.md b/windows/manage/appv-auto-provision-a-vm.md similarity index 72% rename from windows/manage/appv-auto-sequence-a-new-app.md rename to windows/manage/appv-auto-provision-a-vm.md index ccf5008ce5..a148fc7743 100644 --- a/windows/manage/appv-auto-sequence-a-new-app.md +++ b/windows/manage/appv-auto-provision-a-vm.md @@ -1,6 +1,6 @@ --- -title: Automatically sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10) -description: How to automatically sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer) PowerShell cmdlet or the user interface. +title: Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10) +description: How to automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer) PowerShell cmdlet or the user interface. author: eross-msft ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -9,22 +9,12 @@ ms.prod: w10 --- -# Automatically sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer) +# Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer) **Applies to** - Windows 10, version 1703 -Previous versions of the App-V Sequencer have required you to manually sequence and update your app packages. This was time-consuming and required extensive interaction, causing many companies to deploy brand-new packages rather than update an existing one. Windows 10, version 1703 introduces the App-V Auto-Sequencer, which automatically sequences your app packages, improving your overall experience by streamlining the provisioning of the prerequisite environment, automating app installation, and expediting the package updating setup. - -Using the automatic sequencer to package your apps provides: - -- Automatic virtual machine (VM) provisioning of the sequencing environment. The process for this is covered in this topic. - -- Batch-sequencing of packages. This means that multiple apps can be sequenced at the same time, in a single group. For info about this, see [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md). - -- Batch-updating of packages. This means that multiple apps can be updated at the same time, in a single group. For info about this, see [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md). - -- Automatic template creation. The App-V package template is automatically created when using the automatic App-V Sequencer cmdlet or interface. +Previous versions of the App-V Sequencer have required you to manually create your sequencing environment. Windows 10, version 1703 introduces two new PowerShell cmdlets, New-AppVSequencerVM and Connect-AppvSequencerVM, which automatically create your sequencing environment for you, including provisioning your virtual machine. ## Automatic VM provisioning of the sequencing environment You have 2 options for provisioning an VM for auto-sequencing: @@ -118,6 +108,11 @@ The 2 types of provisioning log files, located at %temp%\AutoSequencer\Logs, are - **Connect-AppvSequencerVM-report-<*time_stamp*>.txt**. Includes info about the connections made to the VM, showing whether there were any failures. +### Next steps +After provisioning your sequencing environment, you must sequence your apps, either as a group or individually. For more info about sequencing your apps, see [Manually sequence a single new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md), [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md), and [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md). + +After you sequence your packages, you can automatically cleanup any unpublished packages on the App-V client. For more info, see [Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md). + ### Related topics - [Download the Convert-WindowsImage tool](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) @@ -127,14 +122,6 @@ The 2 types of provisioning log files, located at %temp%\AutoSequencer\Logs, are - [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server) -- [Manually sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) - -- [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) - -- [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) - -- [Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md) - **Have a suggestion for App-V?**

Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). \ No newline at end of file diff --git a/windows/manage/appv-create-and-use-a-project-template.md b/windows/manage/appv-create-and-use-a-project-template.md index 5762aa28d6..9ea8d246a9 100644 --- a/windows/manage/appv-create-and-use-a-project-template.md +++ b/windows/manage/appv-create-and-use-a-project-template.md @@ -51,7 +51,7 @@ After creating the template, you can apply it to all of your new virtual app pac - [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server) -- [Automatically sequence a single app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-sequence-a-new-app.md) +- [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md) - [Manually sequence a single app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) [Liz] Do we want to continue to point to the manual steps? Is there a reason to do one over the other? diff --git a/windows/manage/change-history-for-manage-and-update-windows-10.md b/windows/manage/change-history-for-manage-and-update-windows-10.md index f864a7330a..abe275d91f 100644 --- a/windows/manage/change-history-for-manage-and-update-windows-10.md +++ b/windows/manage/change-history-for-manage-and-update-windows-10.md @@ -25,7 +25,7 @@ This topic lists new and updated topics in the [Manage and update Windows 10](in | [Distribute offline apps](distribute-offline-apps.md) | General updates to topic. Added links to supporting content for System Center Configuration Manager and Microsoft Intune. | |[What's new in App-V for Windows 10, version 1703 and earlier](appv-about-appv.md)|Updated to include new features in App-V for Windows 10, version 1703. | |[Release Notes for App-V for Windows 10, version 1703](appv-release-notes-for-appv-for-windows-1703.md)|New | -|[Automatically sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-sequence-a-new-app.md) |New | +|[Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md) |New | |[Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) |New | |[Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) |New | |[Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md) |New | From fcb5447fbcb3b0665b3836fd1f1ce664c52dbdf3 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 15 Feb 2017 10:00:28 -0800 Subject: [PATCH 54/76] Adding content --- windows/manage/appv-auto-batch-sequencing.md | 2 +- windows/manage/appv-auto-batch-updating.md | 7 +++---- 2 files changed, 4 insertions(+), 5 deletions(-) diff --git a/windows/manage/appv-auto-batch-sequencing.md b/windows/manage/appv-auto-batch-sequencing.md index 1e89fe8fb9..28c83407cb 100644 --- a/windows/manage/appv-auto-batch-sequencing.md +++ b/windows/manage/appv-auto-batch-sequencing.md @@ -17,7 +17,7 @@ Sequencing apps requires you to install and start Microsoft Application Virtuali There are 2 approaches to sequencing multiple apps at the same time: -- Using a cmdlet in PowerShell +- Using the PowerShell cmdlet, New-BatchAppVSequencerPackages -OR- diff --git a/windows/manage/appv-auto-batch-updating.md b/windows/manage/appv-auto-batch-updating.md index 1be4eb3da8..12663c038b 100644 --- a/windows/manage/appv-auto-batch-updating.md +++ b/windows/manage/appv-auto-batch-updating.md @@ -13,23 +13,22 @@ ms.prod: w10 **Applies to** - Windows 10, version 1703 -Updating multiple apps at the same time follows the same process as [automatically sequencing multiple apps at the same time](appv-auto-batch-sequencing.md). However for updating, we pass the previously created app package files to the App-V Sequencer cmdlet for updating. +Updating multiple apps at the same time follows the same process as [automatically sequencing multiple apps at the same time](appv-auto-batch-sequencing.md). However for updating, you'll pass your previously created app package files to the App-V Sequencer cmdlet for updating. There are 2 approaches to updating multiple apps at the same time: -- Using a cmdlet in PowerShell +- Using the PowerShell cmdlet, New-BatchAppVSequencerPackages -OR- - Using the user-interface provided by the App-V Sequencer >[!NOTE] -If you're trying to sequence multiple apps at the same time, see the [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) topic. +>If you're trying to sequence multiple apps at the same time, see the [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) topic. ### Update multiple apps by using a PowerShell cmdlet Updating multiple apps at the same time requires that you create a **ConfigFile** with info related to each round of updating. This file is then used by the cmdlet to start the VM at a "clean" checkpoint, to copy the installer from the Host device to the VM, and then to start the App-V Sequencer to monitor your specified app installations. - **To create your ConfigFile for use by the PowerShell cmdlet** 1. Determine the apps that need to be included in your app package, and then open a text editor, such as Notepad. From 0d8601d9cc0ed20947672ef80efeb4cd76e7d25d Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 15 Feb 2017 10:25:16 -0800 Subject: [PATCH 55/76] Adding content --- windows/manage/appv-auto-batch-sequencing.md | 6 ++++-- windows/manage/appv-auto-batch-updating.md | 2 ++ 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/windows/manage/appv-auto-batch-sequencing.md b/windows/manage/appv-auto-batch-sequencing.md index 28c83407cb..8f0566a318 100644 --- a/windows/manage/appv-auto-batch-sequencing.md +++ b/windows/manage/appv-auto-batch-sequencing.md @@ -13,7 +13,7 @@ ms.prod: w10 **Applies to** - Windows 10, version 1703 -Sequencing apps requires you to install and start Microsoft Application Virtualization Sequencer (App-V Sequencer), and to install the necessary apps to collect any changes made to the operating system during the installation and building of the App-V package. +Sequencing multiple apps at the same time requires you to install and start Microsoft Application Virtualization Sequencer (App-V Sequencer), and to install the necessary apps to collect any changes made to the operating system during the installation and building of the App-V package. There are 2 approaches to sequencing multiple apps at the same time: @@ -23,8 +23,10 @@ There are 2 approaches to sequencing multiple apps at the same time: - Using the user-interface provided by the App-V Sequencer +Starting with Windows 10, version 1703, running the New-BatchAppVSequencerPackages cmdlet or the App-V Sequencer interface captures and stores all of your customizations as an App-V project template. If you later want to make changes to this package, your customizations are automatically loaded from this template file. + >[!NOTE] -If you're trying to update multiple apps at the same time, see the [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) topic. +>If you're trying to update multiple apps at the same time, see the [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) topic. ### Sequence multiple apps by using a PowerShell cmdlet Sequencing multiple apps at the same time requires that you create a **ConfigFile** with info related to each round of sequencing. This file is then used by the cmdlet to start the VM at a "clean" checkpoint, to copy the installer from the Host device to the VM, and then to start the App-V Sequencer to monitor your specified app installations. diff --git a/windows/manage/appv-auto-batch-updating.md b/windows/manage/appv-auto-batch-updating.md index 12663c038b..45221ed9ad 100644 --- a/windows/manage/appv-auto-batch-updating.md +++ b/windows/manage/appv-auto-batch-updating.md @@ -23,6 +23,8 @@ There are 2 approaches to updating multiple apps at the same time: - Using the user-interface provided by the App-V Sequencer +Starting with Windows 10, version 1703, running the New-BatchAppVSequencerPackages cmdlet or the App-V Sequencer interface captures and stores all of your customizations as an App-V project template. If you later want to make changes to this package, your customizations are automatically loaded from this template file. + >[!NOTE] >If you're trying to sequence multiple apps at the same time, see the [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) topic. From bb003a4e4cc1d15a8112e33bf8720dde5047d3f2 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 15 Feb 2017 10:33:51 -0800 Subject: [PATCH 56/76] Adding content --- windows/manage/appv-auto-batch-sequencing.md | 4 +++- windows/manage/appv-auto-batch-updating.md | 2 +- windows/manage/appv-sequence-a-package-with-powershell.md | 5 +++++ 3 files changed, 9 insertions(+), 2 deletions(-) diff --git a/windows/manage/appv-auto-batch-sequencing.md b/windows/manage/appv-auto-batch-sequencing.md index 8f0566a318..1d370065aa 100644 --- a/windows/manage/appv-auto-batch-sequencing.md +++ b/windows/manage/appv-auto-batch-sequencing.md @@ -23,7 +23,9 @@ There are 2 approaches to sequencing multiple apps at the same time: - Using the user-interface provided by the App-V Sequencer -Starting with Windows 10, version 1703, running the New-BatchAppVSequencerPackages cmdlet or the App-V Sequencer interface captures and stores all of your customizations as an App-V project template. If you later want to make changes to this package, your customizations are automatically loaded from this template file. +In Windows 10, version 1703, running the new-appvsequencerpackage cmdlet automatically captures and stores all of your customizations as an App-V project template. If you later want to make changes to this package, your customizations will be automatically loaded from this template file. + +In Windows 10, version 1703, running the New-BatchAppVSequencerPackages cmdlet or the App-V Sequencer interface automatically captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file. >[!NOTE] >If you're trying to update multiple apps at the same time, see the [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) topic. diff --git a/windows/manage/appv-auto-batch-updating.md b/windows/manage/appv-auto-batch-updating.md index 45221ed9ad..847f5807f9 100644 --- a/windows/manage/appv-auto-batch-updating.md +++ b/windows/manage/appv-auto-batch-updating.md @@ -23,7 +23,7 @@ There are 2 approaches to updating multiple apps at the same time: - Using the user-interface provided by the App-V Sequencer -Starting with Windows 10, version 1703, running the New-BatchAppVSequencerPackages cmdlet or the App-V Sequencer interface captures and stores all of your customizations as an App-V project template. If you later want to make changes to this package, your customizations are automatically loaded from this template file. +Starting with Windows 10, version 1703, running the New-BatchAppVSequencerPackages cmdlet or the App-V Sequencer interface captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file. >[!NOTE] >If you're trying to sequence multiple apps at the same time, see the [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) topic. diff --git a/windows/manage/appv-sequence-a-package-with-powershell.md b/windows/manage/appv-sequence-a-package-with-powershell.md index e1920755b9..1e11304931 100644 --- a/windows/manage/appv-sequence-a-package-with-powershell.md +++ b/windows/manage/appv-sequence-a-package-with-powershell.md @@ -59,6 +59,11 @@ The following list displays additional optional parameters that can be used with - FullLoad - specifies that the package must be fully downloaded to the computer running the App-V before it can be opened. +In Windows 10, version 1703, running the new-appvsequencerpackage or the update-appvsequencepackage cmdlets automatically captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file. + +>[!IMPORTANT] +>If you have an auto-saved template and you attempt to load another template through the _TemplateFilePath_ parameter, the customization value from the parameter will override the auto-saved template. + ## Have a suggestion for App-V? Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). From fb41caab948085554e2221771893d06a01aef72f Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 15 Feb 2017 10:45:06 -0800 Subject: [PATCH 57/76] Adding content --- windows/manage/appv-auto-batch-sequencing.md | 2 +- windows/manage/appv-auto-batch-updating.md | 2 +- windows/manage/appv-create-and-use-a-project-template.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/manage/appv-auto-batch-sequencing.md b/windows/manage/appv-auto-batch-sequencing.md index 1d370065aa..db30fd169b 100644 --- a/windows/manage/appv-auto-batch-sequencing.md +++ b/windows/manage/appv-auto-batch-sequencing.md @@ -44,7 +44,7 @@ Sequencing multiple apps at the same time requires that you create a **ConfigFil - **<Installer>.** The file name for the app executable. This will typically be an .exe or .msi file. - - **<InstallerOptions>.** The command-line options required for the app installation. + - **<InstallerOptions>.** The command-line options required for the app installation. - **<TimeoutInMinutes>.** 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. diff --git a/windows/manage/appv-auto-batch-updating.md b/windows/manage/appv-auto-batch-updating.md index 847f5807f9..9ddfe5c45e 100644 --- a/windows/manage/appv-auto-batch-updating.md +++ b/windows/manage/appv-auto-batch-updating.md @@ -42,7 +42,7 @@ Updating multiple apps at the same time requires that you create a **ConfigFile* - **<Installer>.** The file name for the app executable. This will typically be an .exe or .msi file. - - **<InstallerOptions>.** The command-line options required for the app installation. + - **<InstallerOptions>.** The command-line options required for the app installation. - **<Package>.** The file path to the location of your App-V packages. These packages were created when you sequenced your apps. diff --git a/windows/manage/appv-create-and-use-a-project-template.md b/windows/manage/appv-create-and-use-a-project-template.md index 9ea8d246a9..c430efef24 100644 --- a/windows/manage/appv-create-and-use-a-project-template.md +++ b/windows/manage/appv-create-and-use-a-project-template.md @@ -53,7 +53,7 @@ After creating the template, you can apply it to all of your new virtual app pac - [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md) -- [Manually sequence a single app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) [Liz] Do we want to continue to point to the manual steps? Is there a reason to do one over the other? +- [Manually sequence a single app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) **Have a suggestion for App-V?**

Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). From 357d6c4bf40d486bf8c6b1b855a5a50cba3ac3c8 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 15 Feb 2017 11:01:06 -0800 Subject: [PATCH 58/76] Adding content --- ...-creating-and-managing-virtualized-applications.md | 11 +++++++---- .../manage/appv-sequence-a-package-with-powershell.md | 8 ++++---- 2 files changed, 11 insertions(+), 8 deletions(-) diff --git a/windows/manage/appv-creating-and-managing-virtualized-applications.md b/windows/manage/appv-creating-and-managing-virtualized-applications.md index 861034a883..76135444e4 100644 --- a/windows/manage/appv-creating-and-managing-virtualized-applications.md +++ b/windows/manage/appv-creating-and-managing-virtualized-applications.md @@ -166,9 +166,7 @@ You can use the sequencer to modify an existing package. The computer on which y [How to Modify an Existing Virtual Application Package](appv-modify-an-existing-virtual-application-package.md) ## Creating a project template - - -A .appvt file is a project template that can be used to save commonly applied, customized settings. You can then more easily use these settings for future sequencings. +An pp-V project template (.appvt) file is a project template that can be used to save commonly applied, customized settings. You can then more easily use these settings for future sequencings. App-V project templates differ from App-V Application Accelerators because App-V Application Accelerators are application-specific, and App-V project templates can be applied to multiple applications. Additionally, you cannot use a project template when you use a Package Accelerator to create a virtual application package. The following general settings are saved with an App-V project template: @@ -180,10 +178,15 @@ A template can specify and store multiple settings as follows: - **Exclusion Items.** Contains the Exclusion pattern list. +In Windows 10, version 1703, running the new-appvsequencerpackage or the update-appvsequencepackage cmdlets automatically captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file. + +>[!IMPORTANT] +>If you have an auto-saved template and you attempt to load another template through the _TemplateFilePath_ parameter, the customization value from the parameter will override the auto-saved template. + [How to Create and Use a Project Template](appv-create-and-use-a-project-template.md) -## Creating a package accelerator +## Creating a package accelerator **Note**   Package accelerators created using a previous version of App-V must be recreated using App-V. diff --git a/windows/manage/appv-sequence-a-package-with-powershell.md b/windows/manage/appv-sequence-a-package-with-powershell.md index 1e11304931..1d3143b133 100644 --- a/windows/manage/appv-sequence-a-package-with-powershell.md +++ b/windows/manage/appv-sequence-a-package-with-powershell.md @@ -64,10 +64,10 @@ In Windows 10, version 1703, running the new-appvsequencerpackage or the update- >[!IMPORTANT] >If you have an auto-saved template and you attempt to load another template through the _TemplateFilePath_ parameter, the customization value from the parameter will override the auto-saved template. -## Have a suggestion for App-V? - -Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). - ## Related topics - [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md) + +## Have a suggestion for App-V? + +Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). \ No newline at end of file From 527634fee3c0cc73670f341f5ab3e60ab2de265c Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 15 Feb 2017 11:07:28 -0800 Subject: [PATCH 59/76] Adding content --- .../appv-creating-and-managing-virtualized-applications.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/windows/manage/appv-creating-and-managing-virtualized-applications.md b/windows/manage/appv-creating-and-managing-virtualized-applications.md index 76135444e4..448da026da 100644 --- a/windows/manage/appv-creating-and-managing-virtualized-applications.md +++ b/windows/manage/appv-creating-and-managing-virtualized-applications.md @@ -166,9 +166,7 @@ You can use the sequencer to modify an existing package. The computer on which y [How to Modify an Existing Virtual Application Package](appv-modify-an-existing-virtual-application-package.md) ## Creating a project template -An pp-V project template (.appvt) file is a project template that can be used to save commonly applied, customized settings. You can then more easily use these settings for future sequencings. - -App-V project templates differ from App-V Application Accelerators because App-V Application Accelerators are application-specific, and App-V project templates can be applied to multiple applications. Additionally, you cannot use a project template when you use a Package Accelerator to create a virtual application package. The following general settings are saved with an App-V project template: +An App-V project template (.appvt) file is a project template that can be used to save commonly applied, customized settings. You can then more easily use these settings for future sequencings. App-V project templates differ from App-V Application Accelerators because App-V Application Accelerators are application-specific, and App-V project templates can be applied to multiple applications. Additionally, you cannot use a project template when you use a Package Accelerator to create a virtual application package. The following general settings are saved with an App-V project template: A template can specify and store multiple settings as follows: From f52fba34f8ef33dd76e5c7c0832bc09fde5a6783 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 15 Feb 2017 11:18:29 -0800 Subject: [PATCH 60/76] Adding content --- .../appv-create-and-use-a-project-template.md | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/windows/manage/appv-create-and-use-a-project-template.md b/windows/manage/appv-create-and-use-a-project-template.md index c430efef24..1496e43518 100644 --- a/windows/manage/appv-create-and-use-a-project-template.md +++ b/windows/manage/appv-create-and-use-a-project-template.md @@ -11,16 +11,19 @@ ms.prod: w10 # Create and apply an App-V project template to a sequenced App-V package **Applies to** -- Windows 10, version 1703 +- Windows 10, version 1607 -Starting with Windows 10, version 1703, you can save an App-V project template (.appvt) file as part of a sequenced App-V package, so it's automatically loaded every time the package opens for editing or updates. Your template can include general option settings, file exclusion list settings, and target operating system settings. +You can use an App-V project template (.appvt) file to save commonly applied settings associated with an existing virtual application package. These settings can then be applied when you create new virtual application packages in your environment. Using a project template can streamline the process of creating virtual application packages. App-V project templates differ from App-V Package Accelerators because App-V Package Accelerators are application-specific, while App-V project templates can be applied to multiple applications. For more info about Package Accelerators, see the [How to create a Package Accelerator](appv-create-a-package-accelerator.md) topic. + +>[!IMPORTANT] +>In Windows 10, version 1703, running the new-appvsequencerpackage or the update-appvsequencepackage cmdlets automatically captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file. If you have an auto-saved template and you attempt to load another template through the _TemplateFilePath_ parameter, the customization value from the parameter will override the auto-saved template. ->[!NOTE] ->App-V project templates differ from App-V Package Accelerators because App-V Package Accelerators are application-specific, while App-V project templates can be applied to multiple applications. For more info about Package Accelerators, see the [How to create a Package Accelerator](appv-create-a-package-accelerator.md) topic. ## Create a project template You must first create and save a project template, including a virtual app package with settings to be used by the template. +**To create a project template** + 1. On the device running the App-V Sequencer, click **Start**, click **All Programs**, click **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**. >[!NOTE] @@ -51,9 +54,11 @@ After creating the template, you can apply it to all of your new virtual app pac - [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server) -- [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md) +- [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) -- [Manually sequence a single app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) +- [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) + +- [Manually sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) **Have a suggestion for App-V?**

Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). From 41163a2dc14f68b8fa4ded226efcc6e43b6150da Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 15 Feb 2017 13:52:16 -0800 Subject: [PATCH 61/76] Updating from tech review --- windows/manage/appv-auto-batch-sequencing.md | 12 ++++-------- windows/manage/appv-auto-batch-updating.md | 8 -------- 2 files changed, 4 insertions(+), 16 deletions(-) diff --git a/windows/manage/appv-auto-batch-sequencing.md b/windows/manage/appv-auto-batch-sequencing.md index db30fd169b..a62bc351da 100644 --- a/windows/manage/appv-auto-batch-sequencing.md +++ b/windows/manage/appv-auto-batch-sequencing.md @@ -15,17 +15,13 @@ ms.prod: w10 Sequencing multiple apps at the same time requires you to install and start Microsoft Application Virtualization Sequencer (App-V Sequencer), and to install the necessary apps to collect any changes made to the operating system during the installation and building of the App-V package. -There are 2 approaches to sequencing multiple apps at the same time: +In Windows 10, version 1703, running the App-V Sequencer automatically captures and stores your customizations as an App-V project template (.appvt) file. If you want to make changes to this package later, your customizations will be automatically loaded from this template file. This is applicable to all of the sequencing scenarios: -- Using the PowerShell cmdlet, New-BatchAppVSequencerPackages +- Using the New-BatchAppVSequencerPackages cmdlet - -OR- +- Using the App-V Sequencer interface -- Using the user-interface provided by the App-V Sequencer - -In Windows 10, version 1703, running the new-appvsequencerpackage cmdlet automatically captures and stores all of your customizations as an App-V project template. If you later want to make changes to this package, your customizations will be automatically loaded from this template file. - -In Windows 10, version 1703, running the New-BatchAppVSequencerPackages cmdlet or the App-V Sequencer interface automatically captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file. +- Using the new-AppVSequencerPackage cmdlet >[!NOTE] >If you're trying to update multiple apps at the same time, see the [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) topic. diff --git a/windows/manage/appv-auto-batch-updating.md b/windows/manage/appv-auto-batch-updating.md index 9ddfe5c45e..ccb21c347a 100644 --- a/windows/manage/appv-auto-batch-updating.md +++ b/windows/manage/appv-auto-batch-updating.md @@ -15,14 +15,6 @@ ms.prod: w10 Updating multiple apps at the same time follows the same process as [automatically sequencing multiple apps at the same time](appv-auto-batch-sequencing.md). However for updating, you'll pass your previously created app package files to the App-V Sequencer cmdlet for updating. -There are 2 approaches to updating multiple apps at the same time: - -- Using the PowerShell cmdlet, New-BatchAppVSequencerPackages - - -OR- - -- Using the user-interface provided by the App-V Sequencer - Starting with Windows 10, version 1703, running the New-BatchAppVSequencerPackages cmdlet or the App-V Sequencer interface captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file. >[!NOTE] From a314a9e37c07d353c2c94ecb68fd8c048d2a3783 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 15 Feb 2017 13:59:01 -0800 Subject: [PATCH 62/76] Fixing formatting --- windows/manage/appv-auto-batch-sequencing.md | 2 ++ windows/manage/appv-auto-batch-updating.md | 2 ++ 2 files changed, 4 insertions(+) diff --git a/windows/manage/appv-auto-batch-sequencing.md b/windows/manage/appv-auto-batch-sequencing.md index a62bc351da..2722febd18 100644 --- a/windows/manage/appv-auto-batch-sequencing.md +++ b/windows/manage/appv-auto-batch-sequencing.md @@ -30,6 +30,7 @@ In Windows 10, version 1703, running the App-V Sequencer automatically captures Sequencing multiple apps at the same time requires that you create a **ConfigFile** with info related to each round of sequencing. This file is then used by the cmdlet to start the VM at a "clean" checkpoint, to copy the installer from the Host device to the VM, and then to start the App-V Sequencer to monitor your specified app installations. **To create your ConfigFile for use by the PowerShell cmdlet** + 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: @@ -91,6 +92,7 @@ Sequencing multiple apps at the same time requires that you create a **ConfigFil 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. **To 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: diff --git a/windows/manage/appv-auto-batch-updating.md b/windows/manage/appv-auto-batch-updating.md index ccb21c347a..3c9a7531bc 100644 --- a/windows/manage/appv-auto-batch-updating.md +++ b/windows/manage/appv-auto-batch-updating.md @@ -24,6 +24,7 @@ Starting with Windows 10, version 1703, running the New-BatchAppVSequencerPackag Updating multiple apps at the same time requires that you create a **ConfigFile** with info related to each round of updating. This file is then used by the cmdlet to start the VM at a "clean" checkpoint, to copy the installer from the Host device to the VM, and then to start the App-V Sequencer to monitor your specified app installations. **To create your ConfigFile for use by the PowerShell cmdlet** + 1. Determine the apps that need to be included in your app package, and then open a text editor, such as Notepad. 2. Add the following XML info for each app: @@ -89,6 +90,7 @@ Updating multiple apps at the same time requires that you create a **ConfigFile* Updating multipe apps at the same time requires that you create a **ConfigFile** to collect all of the info related to each round of updating. This file is then used by the App-V Sequencer interface after creating a "clean" checkpoint on your VM. **To create your ConfigFile for use by the App-V Sequencer interface** + 1. Determine the apps that need to be updated and then open a text editor, such as Notepad. 2. Add the following XML info for each app: From 461a0582cbf6ffa894355cd9f8329c85c209edf8 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Thu, 16 Feb 2017 08:36:38 -0800 Subject: [PATCH 63/76] Updated based on tech review --- windows/manage/appv-auto-clean-unpublished-packages.md | 4 ++-- windows/manage/appv-auto-provision-a-vm.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/manage/appv-auto-clean-unpublished-packages.md b/windows/manage/appv-auto-clean-unpublished-packages.md index bf540c31f7..3a0eec3646 100644 --- a/windows/manage/appv-auto-clean-unpublished-packages.md +++ b/windows/manage/appv-auto-clean-unpublished-packages.md @@ -44,7 +44,7 @@ Using PowerShell, you can turn on the **AutoCleanupEnabled** setting to automati

Problem
Filetype and protocol handlers aren't registering properly with the Google Chrome browser, causing you to not see App-V packages as an option for default apps from the Settings > Apps> Default Apps area. The recommended workaround is to add the following code to the AppXManifest.xml file, underneath the <appv:Extensions> tag: - 

-                <appv:Extension Category="AppV.URLProtocol">
-                    <appv:URLProtocol>
-                        <appv:Name>ftp</appv:Name>
-                        <appv:ApplicationURLProtocol>
-                            <appv:DefaultIcon>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0</appv:DefaultIcon>
-                            <appv:ShellCommands>
-                                <appv:DefaultCommand>open</appv:DefaultCommand>
-                                <appv:ShellCommand>
-                                    <appv:ApplicationId>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe</appv:ApplicationId>
-                                    <appv:Name>open</appv:Name>
-                                    <appv:CommandLine>"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"</appv:CommandLine>
-                                    <appv:DdeExec>
-                                        <appv:DdeCommand />
-                                    </appv:DdeExec>
-                                </appv:ShellCommand>
-                            </appv:ShellCommands>
-                        </appv:ApplicationURLProtocol>
-                    </appv:URLProtocol>
-                </appv:Extension>
-                <appv:Extension Category="AppV.URLProtocol">
-                    <appv:URLProtocol>
-                        <appv:Name>http</appv:Name>
-                        <appv:ApplicationURLProtocol>
-                            <appv:DefaultIcon>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0</appv:DefaultIcon>
-                            <appv:ShellCommands>
-                                <appv:DefaultCommand>open</appv:DefaultCommand>
-                                <appv:ShellCommand>
-                                    <appv:ApplicationId>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe</appv:ApplicationId>
-                                    <appv:Name>open</appv:Name>
-                                    <appv:CommandLine>"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"</appv:CommandLine>
-                                    <appv:DdeExec>
-                                        <appv:DdeCommand />
-                                    </appv:DdeExec>
-                                </appv:ShellCommand>
-                            </appv:ShellCommands>
-                        </appv:ApplicationURLProtocol>
-                    </appv:URLProtocol>
-                </appv:Extension>
-                <appv:Extension Category="AppV.URLProtocol">
-                    <appv:URLProtocol>
-                        <appv:Name>https</appv:Name>
-                        <appv:ApplicationURLProtocol>
-                            <appv:DefaultIcon>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0</appv:DefaultIcon>
-                            <appv:ShellCommands>
-                                <appv:DefaultCommand>open</appv:DefaultCommand>
-                                <appv:ShellCommand>
-                                    <appv:ApplicationId>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe</appv:ApplicationId>
-                                    <appv:Name>open</appv:Name>
-                                    <appv:CommandLine>"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"</appv:CommandLine>
-                                    <appv:DdeExec>
-                                        <appv:DdeCommand />
-                                    </appv:DdeExec>
-                                </appv:ShellCommand>
-                            </appv:ShellCommands>
-                        </appv:ApplicationURLProtocol>
-                    </appv:URLProtocol>
-                    </appv:Extension>
-
+

+<appv:Extension Category="AppV.URLProtocol">
+	<appv:URLProtocol>
+		<appv:Name>ftp</appv:Name>
+		<appv:ApplicationURLProtocol>
+			<appv:DefaultIcon>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0</appv:DefaultIcon>
+			<appv:ShellCommands>
+				<appv:DefaultCommand>open</appv:DefaultCommand>
+				<appv:ShellCommand>
+					<appv:ApplicationId>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe</appv:ApplicationId>
+					<appv:Name>open</appv:Name>
+					<appv:CommandLine>"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"</appv:CommandLine>
+					<appv:DdeExec>
+						<appv:DdeCommand />
+					</appv:DdeExec>
+				</appv:ShellCommand>
+			</appv:ShellCommands>
+		</appv:ApplicationURLProtocol>
+	</appv:URLProtocol>
+</appv:Extension>
+<appv:Extension Category="AppV.URLProtocol">
+	<appv:URLProtocol>
+		<appv:Name>http</appv:Name>
+		<appv:ApplicationURLProtocol>
+			<appv:DefaultIcon>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0</appv:DefaultIcon>
+			<appv:ShellCommands>
+				<appv:DefaultCommand>open</appv:DefaultCommand>
+				<appv:ShellCommand>
+					<appv:ApplicationId>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe</appv:ApplicationId>
+					<appv:Name>open</appv:Name>
+					<appv:CommandLine>"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"</appv:CommandLine>
+					<appv:DdeExec>
+						<appv:DdeCommand />
+					</appv:DdeExec>
+				</appv:ShellCommand>
+			</appv:ShellCommands>
+		</appv:ApplicationURLProtocol>
+	</appv:URLProtocol>
+</appv:Extension>
+<appv:Extension Category="AppV.URLProtocol">
+	<appv:URLProtocol>
+		<appv:Name>https</appv:Name>
+		<appv:ApplicationURLProtocol>
+			<appv:DefaultIcon>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0</appv:DefaultIcon>
+			<appv:ShellCommands>
+				<appv:DefaultCommand>open</appv:DefaultCommand>
+				<appv:ShellCommand>
+					<appv:ApplicationId>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe</appv:ApplicationId>
+					<appv:Name>open</appv:Name>
+					<appv:CommandLine>"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"</appv:CommandLine>
+					<appv:DdeExec>
+						<appv:DdeCommand />
+					</appv:DdeExec>
+				</appv:ShellCommand>
+			</appv:ShellCommands>
+		</appv:ApplicationURLProtocol>
+	</appv:URLProtocol>
+</appv:Extension>
+
Don't create this file manually, instead let the Add-AppVClientPackage cmdlet auto-generate it.
Failure to update an App-V package from App-V 5.0 or App-V 5.1 to the latest version.Failure to update an App-V package from App-V 5.x to the latest in-box version, by using the PowerShell sequencing commands. Make sure you have the complete App-V package or the MSI file from the original app.
-2. Run the following command to make sure the packages were successfully cleaned up. +2. Run the following command to make sure the configuration is ready to automatically cleanup your packages. ```ps1 Get-AppvClientConfiguration @@ -59,7 +59,7 @@ Using Group Policy, you can turn on the **Enable automatic cleanup of unused app 2. Click **Enabled**, and then click **OK**. - The setting is turned on and will cleanup any unpublished App-V packages on the App-V Client after restarting. + After Group Policy updates, the setting is turned on and will cleanup any unpublished App-V packages on the App-V Client after restarting. ### Related topics - [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit) diff --git a/windows/manage/appv-auto-provision-a-vm.md b/windows/manage/appv-auto-provision-a-vm.md index a148fc7743..b4b1819a25 100644 --- a/windows/manage/appv-auto-provision-a-vm.md +++ b/windows/manage/appv-auto-provision-a-vm.md @@ -39,7 +39,7 @@ For this process to work, you must have a base operating system available as a V ```ps1 Convert-WindowsImage -SourcePath "" -VHDFormat "VHD" -VHDPartitionStyle "MBR" ``` - Where _SourcePath_ is the full path to your ISO image, _VHDFormat_ is always *VHD*, and _VHDPartitionStyle_ is always *MBR*. + Where *<path_to_iso_image>* is the full path to your ISO image. >[!IMPORTANT] >You must specify the _VHDPartitionStyle_ as **MBR**. Using the default value, **GPT**, will cause a boot failure in your VHD image. @@ -95,7 +95,7 @@ If your apps require custom prerequisites, such as Microsoft SQL Server, we reco Connect-AppvSequencerVM -VMName "" -ADKPath "" ``` - Where _VMName_ is the name of the VM granted during its creation and shown in the Hyper-V Manager tool, and the _VMComputerName_ is the name of the VM, assigned after its creation and shown on the **Computer name** field of the **System Properties** screen. + Where *<name_of_vm>* is the name of the VM granted during its creation and shown in the Hyper-V Manager tool. This command creates a new Hyper-V VM file using the provided VHD file and also creates a "clean" checkpoint, from where all sequencing and updating will start. From a04200a2c37a3777fe6993f120887848ac8cef99 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Thu, 16 Feb 2017 08:50:04 -0800 Subject: [PATCH 64/76] Fixed formatting --- windows/manage/appv-auto-clean-unpublished-packages.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/windows/manage/appv-auto-clean-unpublished-packages.md b/windows/manage/appv-auto-clean-unpublished-packages.md index 3a0eec3646..234222854e 100644 --- a/windows/manage/appv-auto-clean-unpublished-packages.md +++ b/windows/manage/appv-auto-clean-unpublished-packages.md @@ -20,11 +20,13 @@ Previous versions of App-V have required you to manually remove your unpublished Using PowerShell, you can turn on the **AutoCleanupEnabled** setting to automatically cleanup your unpublished App-V packages from your App-V client devices. **To turn on the AutoCleanupEnabled option** + 1. Open PowerShell as an admin and run the following command to turn on the automatic package cleanup functionality: ```ps1 Set-AppvClientConfiguration -AutoCleanupEnabled 1 ``` + The command runs and you should see the following info on the PowerShell screen: @@ -51,15 +53,16 @@ Using PowerShell, you can turn on the **AutoCleanupEnabled** setting to automati ``` You should see the **AutoCleanupEnabled** option turned on (shows a value of "1") in the configuration list. -## Clean-up by using Group Policy settings +## Cleanup by using Group Policy settings Using Group Policy, you can turn on the **Enable automatic cleanup of unused appv packages** setting to automatically cleanup your unpublished App-V packages from your App-V client devices. **To turn on the Enable automatic cleanup of unused appv packages setting** + 1. Open your Group Policy editor and double-click the Administrative Templates\System\App-V\PackageManagement\Enable automatic cleanup of unused appv packages setting. 2. Click **Enabled**, and then click **OK**. - After Group Policy updates, the setting is turned on and will cleanup any unpublished App-V packages on the App-V Client after restarting. + After your Group Policy updates, the setting is turned on and will cleanup any unpublished App-V packages on the App-V Client after restarting. ### Related topics - [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit) From 659d7ee979ab9cf3679ed4f743f590e608a14900 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 1 Mar 2017 13:28:45 -0800 Subject: [PATCH 65/76] Adding content --- windows/manage/appv-available-mdm-settings.md | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 windows/manage/appv-available-mdm-settings.md diff --git a/windows/manage/appv-available-mdm-settings.md b/windows/manage/appv-available-mdm-settings.md new file mode 100644 index 0000000000..f2f9ffb071 --- /dev/null +++ b/windows/manage/appv-available-mdm-settings.md @@ -0,0 +1,20 @@ +--- +title: Available Mobile Data Management (MDM) settings for App-V (Windows 10) +description: A list of the available MDM settings for App-V on Windows 10. +author: eross-msft +ms.pagetype: mdop, appcompat, virtualization +ms.mktglfcycl: deploy +ms.sitesec: library +ms.prod: w10 +--- + +# Available Mobile Data Management (MDM) settings for App-V + +**Applies to** +- Windows 10, version 1703 + +If you manage your policies using Intune, you'll want to use these MDM policy settings. You can see the full list of available policies, on the [Policy CSP]() page. + +|Policy name|Supported versions|Details| +|-------------|-------------------|-----------------|--------| +|AllowAddressBarDropdown|Windows 10, Windows Insider Program|
  • **URI full path.** ./Vendor/MSFT/Policy/Config/Browser/AllowAddressBarDropdown
  • **Data type.** Integer
  • **Allowed values:**
    • **0.** Not allowed. Address bar drop-down is disabled, which also disables the user-defined setting, "Show search and site suggestions as I type."
    • **1 (default).** Allowed. Address bar drop-down is enabled.
| \ No newline at end of file From f4e44dc3e475a02b15be8d6334a0efb1205a1397 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 1 Mar 2017 14:34:43 -0800 Subject: [PATCH 66/76] Adding content --- windows/manage/appv-available-mdm-settings.md | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/windows/manage/appv-available-mdm-settings.md b/windows/manage/appv-available-mdm-settings.md index f2f9ffb071..5119dadf19 100644 --- a/windows/manage/appv-available-mdm-settings.md +++ b/windows/manage/appv-available-mdm-settings.md @@ -17,4 +17,20 @@ If you manage your policies using Intune, you'll want to use these MDM policy se |Policy name|Supported versions|Details| |-------------|-------------------|-----------------|--------| -|AllowAddressBarDropdown|Windows 10, Windows Insider Program|
  • **URI full path.** ./Vendor/MSFT/Policy/Config/Browser/AllowAddressBarDropdown
  • **Data type.** Integer
  • **Allowed values:**
    • **0.** Not allowed. Address bar drop-down is disabled, which also disables the user-defined setting, "Show search and site suggestions as I type."
    • **1 (default).** Allowed. Address bar drop-down is enabled.
| \ No newline at end of file +|Name|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/Name
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|Version|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/Version
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|Publisher|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/PUblisher
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|InstallLocation|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/InstallLocation
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|InstallDate|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/InstallDate
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|Users|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/Users
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|AppVPackageID|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/AppVPackageID
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|AppVVersionID|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/AppVVersionID
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|AppVPackageUri|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/AppVPackageUri
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|LastError|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/LastError
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|LastErrorDescription|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/LastErrorDescription
  • **Data type.** String
  • **Allowed values:**
    • **0.** No errors returned during publish.
    • **1.** Unpublish groups failed during publish.
    • **2.** Publish no-group packages failed during publish.
    • **3.** Publish group packages failed during publish.
    • **4.** Unpublish packages failed during publish.
    • **5.** New policy write failed during publish.
    • **6.** Multiple non-fatal errors occurred during publish.
| +|SyncStatusDescription|Windows 10, Version 1703|
  • **URI full +path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/SyncStatusDescription
  • **Data type.** String
  • **Allowed values:**
    • **0.** App-V publishing is idle.
    • **1.** App-V connection groups publish in progress.
    • **2.** App-V packages (non-connection group) publish in progress.
    • **3.** App-V packages (connection group) publish in progress.
    • **4.** App-V packages unpublish in progress.
| + + + + From f6cfc78e7aabf6ba98f30bbcd0dfc047bfcfb5bc Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 1 Mar 2017 14:56:40 -0800 Subject: [PATCH 67/76] Adding content --- windows/manage/appv-available-mdm-settings.md | 34 +++++++++---------- 1 file changed, 16 insertions(+), 18 deletions(-) diff --git a/windows/manage/appv-available-mdm-settings.md b/windows/manage/appv-available-mdm-settings.md index 5119dadf19..2117c082b8 100644 --- a/windows/manage/appv-available-mdm-settings.md +++ b/windows/manage/appv-available-mdm-settings.md @@ -11,26 +11,24 @@ ms.prod: w10 # Available Mobile Data Management (MDM) settings for App-V **Applies to** -- Windows 10, version 1703 +- Windows 10, Version 1703 If you manage your policies using Intune, you'll want to use these MDM policy settings. You can see the full list of available policies, on the [Policy CSP]() page. |Policy name|Supported versions|Details| |-------------|-------------------|-----------------|--------| -|Name|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/Name
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|Version|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/Version
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|Publisher|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/PUblisher
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|InstallLocation|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/InstallLocation
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|InstallDate|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/InstallDate
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|Users|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/Users
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|AppVPackageID|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/AppVPackageID
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|AppVVersionID|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/AppVVersionID
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|AppVPackageUri|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/AppVPackageUri
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|LastError|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/LastError
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|LastErrorDescription|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/LastErrorDescription
  • **Data type.** String
  • **Allowed values:**
    • **0.** No errors returned during publish.
    • **1.** Unpublish groups failed during publish.
    • **2.** Publish no-group packages failed during publish.
    • **3.** Publish group packages failed during publish.
    • **4.** Unpublish packages failed during publish.
    • **5.** New policy write failed during publish.
    • **6.** Multiple non-fatal errors occurred during publish.
| -|SyncStatusDescription|Windows 10, Version 1703|
  • **URI full -path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/SyncStatusDescription
  • **Data type.** String
  • **Allowed values:**
    • **0.** App-V publishing is idle.
    • **1.** App-V connection groups publish in progress.
    • **2.** App-V packages (non-connection group) publish in progress.
    • **3.** App-V packages (connection group) publish in progress.
    • **4.** App-V packages unpublish in progress.
| - - - - +|Name|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/Name
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|Version|Windows 10, Version 1703 (is this right? Which versions of App-V?) (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/Version
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|Publisher|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/PUblisher
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|InstallLocation|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/InstallLocation
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|InstallDate|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/InstallDate
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|Users|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/Users
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|AppVPackageID|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/AppVPackageID
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|AppVVersionID|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/AppVVersionID
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|AppVPackageUri|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/AppVPackageUri
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|LastError|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/LastError
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|LastErrorDescription|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/LastErrorDescription
  • **Data type.** String
  • **Allowed values:**
    • **0.** No errors returned during publish.
    • **1.** Unpublish groups failed during publish.
    • **2.** Publish no-group packages failed during publish.
    • **3.** Publish group packages failed during publish.
    • **4.** Unpublish packages failed during publish.
    • **5.** New policy write failed during publish.
    • **6.** Multiple non-fatal errors occurred during publish.
| +|SyncStatusDescription|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/SyncStatusDescription
  • **Data type.** String
  • **Allowed values:**
    • **0.** App-V publishing is idle.
    • **1.** App-V connection groups publish in progress.
    • **2.** App-V packages (non-connection group) publish in progress.
    • **3.** App-V packages (connection group) publish in progress.
    • **4.** App-V packages unpublish in progress.
| +|SyncProgress|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/SyncProgress
  • **Data type.** String
  • **Allowed values:**
    • **0.** App-V Sync is idle.
    • **1.** App-V Sync is initializing.
    • **2.** App-V Sync is in progress.
    • **3.** App-V Sync is complete.
    • **4.** App-V Sync requires device reboot.
| +|PublishXML|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/Sync/PublishXML
  • **Data type.** Need info, not in DDF
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|Policy|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVDynamicPolicy/__/Policy
  • **Data type.** Need info, not in DDF
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| \ No newline at end of file From c66c35182d53dc30523660cd592dd3b567d6f1a5 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Thu, 2 Mar 2017 09:38:17 -0800 Subject: [PATCH 68/76] Fixing variables formatting --- windows/manage/appv-available-mdm-settings.md | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/windows/manage/appv-available-mdm-settings.md b/windows/manage/appv-available-mdm-settings.md index 2117c082b8..15e4e1b5df 100644 --- a/windows/manage/appv-available-mdm-settings.md +++ b/windows/manage/appv-available-mdm-settings.md @@ -17,18 +17,18 @@ If you manage your policies using Intune, you'll want to use these MDM policy se |Policy name|Supported versions|Details| |-------------|-------------------|-----------------|--------| -|Name|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/Name
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|Version|Windows 10, Version 1703 (is this right? Which versions of App-V?) (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/Version
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|Publisher|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/PUblisher
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|InstallLocation|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/InstallLocation
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|InstallDate|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/InstallDate
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|Users|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/Users
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|AppVPackageID|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/AppVPackageID
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|AppVVersionID|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/AppVVersionID
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|AppVPackageUri|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/**/**/**/AppVPackageUri
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|Name|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/Name
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|Version|Windows 10, Version 1703 (is this right? Which versions of App-V?) (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/Version
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|Publisher|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/PUblisher
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|InstallLocation|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/InstallLocation
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|InstallDate|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/InstallDate
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|Users|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/Users
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|AppVPackageID|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/AppVPackageID
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|AppVVersionID|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/AppVVersionID
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|AppVPackageUri|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/AppVPackageUri
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| |LastError|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/LastError
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| |LastErrorDescription|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/LastErrorDescription
  • **Data type.** String
  • **Allowed values:**
    • **0.** No errors returned during publish.
    • **1.** Unpublish groups failed during publish.
    • **2.** Publish no-group packages failed during publish.
    • **3.** Publish group packages failed during publish.
    • **4.** Unpublish packages failed during publish.
    • **5.** New policy write failed during publish.
    • **6.** Multiple non-fatal errors occurred during publish.
| |SyncStatusDescription|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/SyncStatusDescription
  • **Data type.** String
  • **Allowed values:**
    • **0.** App-V publishing is idle.
    • **1.** App-V connection groups publish in progress.
    • **2.** App-V packages (non-connection group) publish in progress.
    • **3.** App-V packages (connection group) publish in progress.
    • **4.** App-V packages unpublish in progress.
| |SyncProgress|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/SyncProgress
  • **Data type.** String
  • **Allowed values:**
    • **0.** App-V Sync is idle.
    • **1.** App-V Sync is initializing.
    • **2.** App-V Sync is in progress.
    • **3.** App-V Sync is complete.
    • **4.** App-V Sync requires device reboot.
| |PublishXML|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/Sync/PublishXML
  • **Data type.** Need info, not in DDF
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|Policy|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVDynamicPolicy/__/Policy
  • **Data type.** Need info, not in DDF
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| \ No newline at end of file +|Policy|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVDynamicPolicy/_configurationid_/Policy
  • **Data type.** Need info, not in DDF
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| \ No newline at end of file From 978b90b69de895c56b4664105b5ea85e8fbe4c94 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Thu, 2 Mar 2017 11:45:03 -0800 Subject: [PATCH 69/76] Updating content --- windows/manage/appv-available-mdm-settings.md | 30 +++++++++---------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/windows/manage/appv-available-mdm-settings.md b/windows/manage/appv-available-mdm-settings.md index 15e4e1b5df..4e6bd35820 100644 --- a/windows/manage/appv-available-mdm-settings.md +++ b/windows/manage/appv-available-mdm-settings.md @@ -17,18 +17,18 @@ If you manage your policies using Intune, you'll want to use these MDM policy se |Policy name|Supported versions|Details| |-------------|-------------------|-----------------|--------| -|Name|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/Name
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|Version|Windows 10, Version 1703 (is this right? Which versions of App-V?) (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/Version
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|Publisher|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/PUblisher
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|InstallLocation|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/InstallLocation
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|InstallDate|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/InstallDate
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|Users|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/Users
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|AppVPackageID|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/AppVPackageID
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|AppVVersionID|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/AppVVersionID
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|AppVPackageUri|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/AppVPackageUri
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|LastError|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/LastError
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|LastErrorDescription|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/LastErrorDescription
  • **Data type.** String
  • **Allowed values:**
    • **0.** No errors returned during publish.
    • **1.** Unpublish groups failed during publish.
    • **2.** Publish no-group packages failed during publish.
    • **3.** Publish group packages failed during publish.
    • **4.** Unpublish packages failed during publish.
    • **5.** New policy write failed during publish.
    • **6.** Multiple non-fatal errors occurred during publish.
| -|SyncStatusDescription|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/SyncStatusDescription
  • **Data type.** String
  • **Allowed values:**
    • **0.** App-V publishing is idle.
    • **1.** App-V connection groups publish in progress.
    • **2.** App-V packages (non-connection group) publish in progress.
    • **3.** App-V packages (connection group) publish in progress.
    • **4.** App-V packages unpublish in progress.
| -|SyncProgress|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/SyncProgress
  • **Data type.** String
  • **Allowed values:**
    • **0.** App-V Sync is idle.
    • **1.** App-V Sync is initializing.
    • **2.** App-V Sync is in progress.
    • **3.** App-V Sync is complete.
    • **4.** App-V Sync requires device reboot.
| -|PublishXML|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/Sync/PublishXML
  • **Data type.** Need info, not in DDF
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|Policy|Windows 10, Version 1703 (is this right? Which versions of App-V?)|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVDynamicPolicy/_configurationid_/Policy
  • **Data type.** Need info, not in DDF
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| \ No newline at end of file +|Name|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/Name
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|Version|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/Version
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|Publisher|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/PUblisher
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|InstallLocation|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/InstallLocation
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|InstallDate|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/InstallDate
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|Users|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/Users
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|AppVPackageID|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/AppVPackageID
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|AppVVersionID|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/AppVVersionID
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|AppVPackageUri|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/AppVPackageUri
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|LastError|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/LastError
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|LastErrorDescription|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/LastErrorDescription
  • **Data type.** String
  • **Allowed values:**
    • **0.** No errors returned during publish.
    • **1.** Unpublish groups failed during publish.
    • **2.** Publish no-group packages failed during publish.
    • **3.** Publish group packages failed during publish.
    • **4.** Unpublish packages failed during publish.
    • **5.** New policy write failed during publish.
    • **6.** Multiple non-fatal errors occurred during publish.
| +|SyncStatusDescription|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/SyncStatusDescription
  • **Data type.** String
  • **Allowed values:**
    • **0.** App-V publishing is idle.
    • **1.** App-V connection groups publish in progress.
    • **2.** App-V packages (non-connection group) publish in progress.
    • **3.** App-V packages (connection group) publish in progress.
    • **4.** App-V packages unpublish in progress.
| +|SyncProgress|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/SyncProgress
  • **Data type.** String
  • **Allowed values:**
    • **0.** App-V Sync is idle.
    • **1.** App-V Sync is initializing.
    • **2.** App-V Sync is in progress.
    • **3.** App-V Sync is complete.
    • **4.** App-V Sync requires device reboot.
| +|PublishXML|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/Sync/PublishXML
  • **Data type.** Need info, not in DDF
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| +|Policy|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVDynamicPolicy/_configurationid_/Policy
  • **Data type.** Need info, not in DDF
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| \ No newline at end of file From e615a4586d2f2c2a955986e93bb7a44ee4cc40cc Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 8 Mar 2017 12:51:58 -0800 Subject: [PATCH 70/76] Adding content --- windows/manage/appv-available-mdm-settings.md | 217 ++++++++++++++++-- 1 file changed, 199 insertions(+), 18 deletions(-) diff --git a/windows/manage/appv-available-mdm-settings.md b/windows/manage/appv-available-mdm-settings.md index 4e6bd35820..24911f1e84 100644 --- a/windows/manage/appv-available-mdm-settings.md +++ b/windows/manage/appv-available-mdm-settings.md @@ -13,22 +13,203 @@ ms.prod: w10 **Applies to** - Windows 10, Version 1703 -If you manage your policies using Intune, you'll want to use these MDM policy settings. You can see the full list of available policies, on the [Policy CSP]() page. +If you manage your policies using Microsoft Intune, you'll want to use these MDM policy settings. You can see the full list of available policies, on the [Policy CSP]() page. -|Policy name|Supported versions|Details| -|-------------|-------------------|-----------------|--------| -|Name|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/Name
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|Version|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/Version
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|Publisher|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/PUblisher
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|InstallLocation|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/InstallLocation
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|InstallDate|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/InstallDate
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|Users|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/Users
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|AppVPackageID|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/AppVPackageID
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|AppVVersionID|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/AppVVersionID
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|AppVPackageUri|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/*enterprise_id*/*package_family_name*/*package_full_name*/AppVPackageUri
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|LastError|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/LastError
  • **Data type.** String
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|LastErrorDescription|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/LastErrorDescription
  • **Data type.** String
  • **Allowed values:**
    • **0.** No errors returned during publish.
    • **1.** Unpublish groups failed during publish.
    • **2.** Publish no-group packages failed during publish.
    • **3.** Publish group packages failed during publish.
    • **4.** Unpublish packages failed during publish.
    • **5.** New policy write failed during publish.
    • **6.** Multiple non-fatal errors occurred during publish.
| -|SyncStatusDescription|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/SyncStatusDescription
  • **Data type.** String
  • **Allowed values:**
    • **0.** App-V publishing is idle.
    • **1.** App-V connection groups publish in progress.
    • **2.** App-V packages (non-connection group) publish in progress.
    • **3.** App-V packages (connection group) publish in progress.
    • **4.** App-V packages unpublish in progress.
| -|SyncProgress|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/SyncProgress
  • **Data type.** String
  • **Allowed values:**
    • **0.** App-V Sync is idle.
    • **1.** App-V Sync is initializing.
    • **2.** App-V Sync is in progress.
    • **3.** App-V Sync is complete.
    • **4.** App-V Sync requires device reboot.
| -|PublishXML|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/Sync/PublishXML
  • **Data type.** Need info, not in DDF
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| -|Policy|Windows 10, Version 1703|
  • **URI full path.** ./Vendor/MSFT/EnterpriseAppVManagement/AppVDynamicPolicy/_configurationid_/Policy
  • **Data type.** Need info, not in DDF
  • **Allowed values:**
    • **0.** Need info, not in DDF
    • **1 (default).** Need info, not in DDF.
| \ No newline at end of file +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Policy nameSupported versionsDetails
NameWindows 10, Version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/Name
    • +
  • Data type. String
    • +
  • Value. Read-only data, provided by your App-V packages.
    • +
+
VersionWindows 10, Version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/Version
    • +
  • Data type. String
    • +
  • Value. Read-only data, provided by your App-V packages.
    • +
+
PublisherWindows 10, Version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/Publisher
    • +
  • Data type. String
    • +
  • Value. Read-only data, provided by your App-V packages.
    • +
+
InstallLocationWindows 10, Version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/InstallLocation
    • +
  • Data type. String
    • +
  • Value. Read-only data, provided by your App-V packages.
    • +
+
InstallDateWindows 10, Version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/InstallDate
    • +
  • Data type. String
    • +
  • Value. Read-only data, provided by your App-V packages.
    • +
+
UsersWindows 10, Version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/Users
    • +
  • Data type. String
    • +
  • Value. Read-only data, provided by your App-V packages.
    • +
+
AppVPackageIDWindows 10, Version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/AppVPackageID
    • +
  • Data type. String
    • +
  • Value. Read-only data, provided by your App-V packages.
    • +
+
AppVVersionIDWindows 10, Version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/AppVVersionID
    • +
  • Data type. String
    • +
  • Value. Read-only data, provided by your App-V packages.
    • +
+
AppVPackageUriWindows 10, Version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/AppVPackageUri
    • +
  • Data type. String
    • +
  • Value. Read-only data, provided by your App-V packages.
    • +
+
LastErrorWindows 10, Version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/LastError
    • +
  • Data type. String
    • +
  • Value. Read-only data, provided by your App-V client.
    • +
+
LastErrorDescriptionWindows 10, Version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/LastErrorDescription
    • +
  • Data type. String
    • +
  • Values. +
      +
    • 0. No errors returned during publish.
      • +
    • 1. Unpublish groups failed during publish.
      • +
    • 2. Publish no-group packages failed during publish.
      • +
    • 3. Publish group packages failed during publish.
      • +
    • 4. Unpublish packages failed during publish.
      • +
    • 5. New policy write failed during publish.
      • +
    • 6. Multiple non-fatal errors occurred during publish.
      • +
    +
    • +
+
SyncStatusDescriptionWindows 10, Version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/SyncStatusDescription
    • +
  • Data type. String
    • +
  • Values. +
      +
    • 0. App-V publishing is idle.
      • +
    • 1. App-V connection groups publish in progress.
      • +
    • 2. App-V packages (non-connection group) publish in progress.
      • +
    • 3. App-V packages (connection group) publish in progress.
      • +
    • 4. App-V packages unpublish in progress.
      • +
    +
    • +
+
SyncProgressWindows 10, Version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/SyncProgress
    • +
  • Data type. String
    • +
  • Values. +
      +
    • 0. App-V Sync is idle.
      • +
    • 1. App-V Sync is initializing.
      • +
    • 2. App-V Sync is in progress.
      • +
    • 3. App-V Sync is complete.
      • +
    • 4. App-V Sync requires device reboot.
      • +
    +
    • +
+
PublishXMLWindows 10, Version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/Sync/PublishXML
    • +
  • Data type. String
    • +
  • Value. Custom value, entered by admin.
    • +
+
PolicyWindows 10, Version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVDynamicPolicy/configurationid/Policy
    • +
  • Data type. String
    • +
  • Value. Custom value, entered by admin.
    • +
+
\ No newline at end of file From 0a6b53bb721689882f4e04efcb8d3abd7c944b5e Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 8 Mar 2017 13:12:11 -0800 Subject: [PATCH 71/76] Adding content --- windows/manage/TOC.md | 2 +- windows/manage/appv-available-mdm-settings.md | 4 ---- ...-history-for-manage-and-update-windows-10.md | 17 +++++++++++------ 3 files changed, 12 insertions(+), 11 deletions(-) diff --git a/windows/manage/TOC.md b/windows/manage/TOC.md index 972e6695c8..af1d49ebfe 100644 --- a/windows/manage/TOC.md +++ b/windows/manage/TOC.md @@ -166,8 +166,8 @@ ##### [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) ### [Troubleshooting App-V](appv-troubleshooting.md) ### [Technical Reference for App-V](appv-technical-reference.md) +#### [Available Mobile Data Management (MDM) settings for App-V](appv-available-mdm-settings.md) #### [Performance Guidance for Application Virtualization](appv-performance-guidance.md) - #### [Application Publishing and Client Interaction](appv-application-publishing-and-client-interaction.md) #### [Viewing App-V Server Publishing Metadata](appv-viewing-appv-server-publishing-metadata.md) #### [Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications](appv-running-locally-installed-applications-inside-a-virtual-environment.md) diff --git a/windows/manage/appv-available-mdm-settings.md b/windows/manage/appv-available-mdm-settings.md index 24911f1e84..524752b09c 100644 --- a/windows/manage/appv-available-mdm-settings.md +++ b/windows/manage/appv-available-mdm-settings.md @@ -9,10 +9,6 @@ ms.prod: w10 --- # Available Mobile Data Management (MDM) settings for App-V - -**Applies to** -- Windows 10, Version 1703 - If you manage your policies using Microsoft Intune, you'll want to use these MDM policy settings. You can see the full list of available policies, on the [Policy CSP]() page. diff --git a/windows/manage/change-history-for-manage-and-update-windows-10.md b/windows/manage/change-history-for-manage-and-update-windows-10.md index 7533fabb94..4d3a63b309 100644 --- a/windows/manage/change-history-for-manage-and-update-windows-10.md +++ b/windows/manage/change-history-for-manage-and-update-windows-10.md @@ -14,6 +14,17 @@ This topic lists new and updated topics in the [Manage and update Windows 10](in >If you're looking for **update history** for Windows 10, see [Windows 10 and Windows Server 2016 update history](https://support.microsoft.com/help/12387/windows-10-update-history). +## March 2017 +| New or changed topic | Description | +| --- | --- | +|[What's new in App-V for Windows 10, version 1703 and earlier](appv-about-appv.md)|Updated to include new features in App-V for Windows 10, version 1703. | +|[Release Notes for App-V for Windows 10, version 1703](appv-release-notes-for-appv-for-windows-1703.md)|New | +|[Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md) |New | +|[Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) |New | +|[Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) |New | +|[Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md) |New | +|[Available Mobile Data Management (MDM) settings for App-V](appv-available-mdm-settings.md) |New | + ## February 2017 | New or changed topic | Description | | --- | --- | @@ -24,12 +35,6 @@ This topic lists new and updated topics in the [Manage and update Windows 10](in |[Assign devices to servicing branches for Windows 10 updates](waas-servicing-branches-windows-10-updates.md) | Added Group Policy setting that blocks user access to Windows Update. | |[Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md) |Added Express updates. | | [Distribute offline apps](distribute-offline-apps.md) | General updates to topic. Added links to supporting content for System Center Configuration Manager and Microsoft Intune. | -|[What's new in App-V for Windows 10, version 1703 and earlier](appv-about-appv.md)|Updated to include new features in App-V for Windows 10, version 1703. | -|[Release Notes for App-V for Windows 10, version 1703](appv-release-notes-for-appv-for-windows-1703.md)|New | -|[Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md) |New | -|[Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) |New | -|[Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) |New | -|[Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md) |New | ## January 2017 From cd09a00782a34fd2ab06e37088fa8e4b15dc3698 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 8 Mar 2017 13:14:58 -0800 Subject: [PATCH 72/76] Adding content --- windows/manage/appv-available-mdm-settings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/manage/appv-available-mdm-settings.md b/windows/manage/appv-available-mdm-settings.md index 524752b09c..1b523bc10a 100644 --- a/windows/manage/appv-available-mdm-settings.md +++ b/windows/manage/appv-available-mdm-settings.md @@ -9,7 +9,7 @@ ms.prod: w10 --- # Available Mobile Data Management (MDM) settings for App-V -If you manage your policies using Microsoft Intune, you'll want to use these MDM policy settings. You can see the full list of available policies, on the [Policy CSP]() page. +With Windows 10, Version 1703, you can configure, deploy, and manage your App-V apps by using these Mobile Data Management (MDM) settings. For the full list of available settings, see the [Policy CSP]() page.
From eed71fc52673d7021f633c07f1627213279d5895 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 15 Mar 2017 15:16:13 -0700 Subject: [PATCH 73/76] Updated topic --- windows/manage/appv-planning-for-using-appv-with-office.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/windows/manage/appv-planning-for-using-appv-with-office.md b/windows/manage/appv-planning-for-using-appv-with-office.md index bd79da1f4f..fd3f7a5bc1 100644 --- a/windows/manage/appv-planning-for-using-appv-with-office.md +++ b/windows/manage/appv-planning-for-using-appv-with-office.md @@ -32,9 +32,6 @@ You can use the App-V Sequencer to create plug-in packages for Language Packs, L Microsoft Visio and Microsoft Project do not provide support for the Thai Language Pack. ## Supported versions of Microsoft Office - - - The following table lists the versions of Microsoft Office that App-V supports, methods of Office package creation, supported licensing, and supported deployments.
From 166fb630986c7aba01b317cb429d056cefdc409c Mon Sep 17 00:00:00 2001 From: LizRoss Date: Thu, 16 Mar 2017 06:50:35 -0700 Subject: [PATCH 74/76] Updated CSP --- windows/manage/appv-available-mdm-settings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/manage/appv-available-mdm-settings.md b/windows/manage/appv-available-mdm-settings.md index 1b523bc10a..ad598a2a68 100644 --- a/windows/manage/appv-available-mdm-settings.md +++ b/windows/manage/appv-available-mdm-settings.md @@ -9,7 +9,7 @@ ms.prod: w10 --- # Available Mobile Data Management (MDM) settings for App-V -With Windows 10, Version 1703, you can configure, deploy, and manage your App-V apps by using these Mobile Data Management (MDM) settings. For the full list of available settings, see the [Policy CSP]() page. +With Windows 10, Version 1703, you can configure, deploy, and manage your App-V apps by using these Mobile Data Management (MDM) settings. For the full list of available settings, see the [EnterpriseAppVManagement CSP](https://msdn.microsoft.com/en-us/windows/hardware/commercialize/customize/mdm/enterpriseappvmanagement-csp) page.
From 30270764ac156ad96c62379134409b0ea8046740 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Thu, 16 Mar 2017 07:01:45 -0700 Subject: [PATCH 75/76] Updated content --- windows/manage/appv-available-mdm-settings.md | 32 +++++++++---------- 1 file changed, 16 insertions(+), 16 deletions(-) diff --git a/windows/manage/appv-available-mdm-settings.md b/windows/manage/appv-available-mdm-settings.md index ad598a2a68..dc5eb1a61a 100644 --- a/windows/manage/appv-available-mdm-settings.md +++ b/windows/manage/appv-available-mdm-settings.md @@ -9,7 +9,7 @@ ms.prod: w10 --- # Available Mobile Data Management (MDM) settings for App-V -With Windows 10, Version 1703, you can configure, deploy, and manage your App-V apps by using these Mobile Data Management (MDM) settings. For the full list of available settings, see the [EnterpriseAppVManagement CSP](https://msdn.microsoft.com/en-us/windows/hardware/commercialize/customize/mdm/enterpriseappvmanagement-csp) page. +With Windows 10, version 1703, you can configure, deploy, and manage your App-V apps by using these Mobile Data Management (MDM) settings. For the full list of available settings, see the [EnterpriseAppVManagement CSP](https://msdn.microsoft.com/en-us/windows/hardware/commercialize/customize/mdm/enterpriseappvmanagement-csp) page.
@@ -19,7 +19,7 @@ With Windows 10, Version 1703, you can configure, deploy, and manage your App-V - + - + - + - + - + - + - + - + - + - + - + - + - + - + - +
NameWindows 10, Version 1703Windows 10, version 1703
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/Name
    • @@ -30,7 +30,7 @@ With Windows 10, Version 1703, you can configure, deploy, and manage your App-V
VersionWindows 10, Version 1703Windows 10, version 1703
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/Version
    • @@ -41,7 +41,7 @@ With Windows 10, Version 1703, you can configure, deploy, and manage your App-V
PublisherWindows 10, Version 1703Windows 10, version 1703
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/Publisher
    • @@ -52,7 +52,7 @@ With Windows 10, Version 1703, you can configure, deploy, and manage your App-V
InstallLocationWindows 10, Version 1703Windows 10, version 1703
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/InstallLocation
    • @@ -63,7 +63,7 @@ With Windows 10, Version 1703, you can configure, deploy, and manage your App-V
InstallDateWindows 10, Version 1703Windows 10, version 1703
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/InstallDate
    • @@ -74,7 +74,7 @@ With Windows 10, Version 1703, you can configure, deploy, and manage your App-V
UsersWindows 10, Version 1703Windows 10, version 1703
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/Users
    • @@ -85,7 +85,7 @@ With Windows 10, Version 1703, you can configure, deploy, and manage your App-V
AppVPackageIDWindows 10, Version 1703Windows 10, version 1703
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/AppVPackageID
    • @@ -96,7 +96,7 @@ With Windows 10, Version 1703, you can configure, deploy, and manage your App-V
AppVVersionIDWindows 10, Version 1703Windows 10, version 1703
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/AppVVersionID
    • @@ -107,7 +107,7 @@ With Windows 10, Version 1703, you can configure, deploy, and manage your App-V
AppVPackageUriWindows 10, Version 1703Windows 10, version 1703
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/AppVPackageUri
    • @@ -118,7 +118,7 @@ With Windows 10, Version 1703, you can configure, deploy, and manage your App-V
LastErrorWindows 10, Version 1703Windows 10, version 1703
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/LastError
    • @@ -129,7 +129,7 @@ With Windows 10, Version 1703, you can configure, deploy, and manage your App-V
LastErrorDescriptionWindows 10, Version 1703Windows 10, version 1703
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/LastErrorDescription
    • @@ -150,7 +150,7 @@ With Windows 10, Version 1703, you can configure, deploy, and manage your App-V
SyncStatusDescriptionWindows 10, Version 1703Windows 10, version 1703
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/SyncStatusDescription
    • @@ -169,7 +169,7 @@ With Windows 10, Version 1703, you can configure, deploy, and manage your App-V
SyncProgressWindows 10, Version 1703Windows 10, version 1703
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/SyncProgress
    • @@ -188,7 +188,7 @@ With Windows 10, Version 1703, you can configure, deploy, and manage your App-V
PublishXMLWindows 10, Version 1703Windows 10, version 1703
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/Sync/PublishXML
    • @@ -199,7 +199,7 @@ With Windows 10, Version 1703, you can configure, deploy, and manage your App-V
PolicyWindows 10, Version 1703Windows 10, version 1703
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVDynamicPolicy/configurationid/Policy
    • From 17951bc28c9a8a66b3a02dc5e575f3b1fd2670ef Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 22 Mar 2017 07:20:01 -0700 Subject: [PATCH 76/76] Updating links --- .../appv-creating-and-managing-virtualized-applications.md | 4 +++- windows/manage/appv-for-windows.md | 4 ++++ 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/windows/manage/appv-creating-and-managing-virtualized-applications.md b/windows/manage/appv-creating-and-managing-virtualized-applications.md index 448da026da..b6aeefb413 100644 --- a/windows/manage/appv-creating-and-managing-virtualized-applications.md +++ b/windows/manage/appv-creating-and-managing-virtualized-applications.md @@ -68,7 +68,9 @@ The **Options** dialog box in the sequencer console contains the following tabs: App-V supports applications that include Microsoft Windows Services. If an application includes a Windows service, the Service will be included in the sequenced virtual package as long as it is installed while being monitored by the sequencer. If a virtual application creates a Windows service when it initially runs, then later, after installation, the application must be run while the sequencer is monitoring so that the Windows Service will be added to the package. Only Services that run under the Local System account are supported. Services that are configured for AutoStart or Delayed AutoStart are started before the first virtual application in a package runs inside the package’s Virtual Environment. Windows Services that are configured to be started on demand by an application are started when the virtual application inside the package starts the Service via API call. -[How to Sequence a New Application with App-V](appv-sequence-a-new-application.md) +- [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md) +- [How to Sequence a New Application with App-V](appv-sequence-a-new-application.md) +- [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) ## App-V shell extension support diff --git a/windows/manage/appv-for-windows.md b/windows/manage/appv-for-windows.md index 3938202a14..ed4d234781 100644 --- a/windows/manage/appv-for-windows.md +++ b/windows/manage/appv-for-windows.md @@ -42,10 +42,14 @@ The topics in this section provide information and step-by-step procedures to he [Operations for App-V](appv-operations.md) - [Creating and Managing App-V Virtualized Applications](appv-creating-and-managing-virtualized-applications.md) +- [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md) +- [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) +- [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) - [Administering App-V Virtual Applications by Using the Management Console](appv-administering-virtual-applications-with-the-management-console.md) - [Managing Connection Groups](appv-managing-connection-groups.md) - [Deploying App-V Packages by Using Electronic Software Distribution (ESD)](appv-deploying-packages-with-electronic-software-distribution-solutions.md) - [Using the App-V Client Management Console](appv-using-the-client-management-console.md) +- [Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md) - [Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md) - [Maintaining App-V](appv-maintaining-appv.md) - [Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md)