<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>App-V on ETDWH.com</title><link>https://www.etdwh.com/tags/app-v/</link><description>Recent content in App-V on ETDWH.com</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 19 Oct 2016 00:00:00 +0000</lastBuildDate><atom:link href="https://www.etdwh.com/tags/app-v/index.xml" rel="self" type="application/rss+xml"/><item><title>App-V And Windows 10 - Making Sense Of It All</title><link>https://www.etdwh.com/posts/app-v-and-windows-10-making-sense-of-it-all/</link><pubDate>Wed, 19 Oct 2016 00:00:00 +0000</pubDate><guid>https://www.etdwh.com/posts/app-v-and-windows-10-making-sense-of-it-all/</guid><description>&lt;p&gt;In the last SCCM Test Lab post, we looked at &lt;a href="https://www.etdwh.com/posts/setting-up-a-virtual-sccm-testlab-part-4/"&gt;part 4&lt;/a&gt;, where we had done the basic setup, and were looking to go further into part 5.&lt;/p&gt;
&lt;p&gt;Things have moved on since then. Microsoft has now officially released &lt;a href="https://www.microsoft.com/en-us/cloud-platform/windows-server"&gt;Windows Server 2016&lt;/a&gt; and SCCM 2016. Windows 10 1607 was also released, with some interesting aspects about App-V and UE-V.&lt;/p&gt;
&lt;p&gt;My focus for the last 2 months had been to plan for how we could in our organization have coexisting operating systems (Windows 7 and Windows 10) when the App-V solution was different for Windows 10 1607.&lt;/p&gt;
&lt;p&gt;In this post I&amp;rsquo;ll be sharing some of the things I have discovered, and how you can try to make sense of all the confusion which might be out there.&lt;/p&gt;</description></item><item><title>PowerShell App Deployment Toolkit - Deep Dive</title><link>https://www.etdwh.com/posts/powershell-app-deployment-toolkit-deep-dive/</link><pubDate>Fri, 08 Jul 2016 00:00:00 +0000</pubDate><guid>https://www.etdwh.com/posts/powershell-app-deployment-toolkit-deep-dive/</guid><description>&lt;p&gt;&lt;a href="images/AppDeployToolkitBanner2.png"&gt;&lt;img src="images/AppDeployToolkitBanner2.png" alt="AppDeployToolkitBanner2"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;When we last looked at the PowerShell App Deployment Toolkit, we looked at a simple example of installing Visual C++ Runtime, which does not show the power of using the toolkit. In this post, we want to look at a more complete example of using the toolkit to save time and effort creating deployment scripts.&lt;/p&gt;
&lt;h3 id="toolkit-configuration"&gt;Toolkit Configuration&lt;/h3&gt;
&lt;p&gt;But first, we want to look into some of the configuration options of the toolkit. The toolkit folder has a file called AppDeployToolkitConfig.xml. This contains all the default configurations which will be used for all deployments.&lt;/p&gt;</description></item><item><title>SETTING UP A VIRTUAL SCCM TESTLAB – PART 4</title><link>https://www.etdwh.com/posts/setting-up-a-virtual-sccm-testlab-part-4/</link><pubDate>Thu, 30 Jun 2016 00:00:00 +0000</pubDate><guid>https://www.etdwh.com/posts/setting-up-a-virtual-sccm-testlab-part-4/</guid><description>&lt;p&gt;This post picks up after &lt;a href="https://www.etdwh.com/posts/setting-up-a-virtual-sccm-testlab/"&gt;part 1&lt;/a&gt;, &lt;a href="https://www.etdwh.com/posts/setting-up-a-virtual-sccm-testlab-part-2/"&gt;part 2&lt;/a&gt; and &lt;a href="https://www.etdwh.com/posts/setting-up-a-virtual-sccm-testlab-part-3/"&gt;part 3&lt;/a&gt;. I suggest you read all 3 parts first to understand what is happening here in part 4.&lt;/p&gt;
&lt;p&gt;In this part 4, we will setup the SCCM discovery methods, boundaries, boundary groups, SCCM roles, and push the SCCM Client to our client machine.&lt;/p&gt;
&lt;p&gt;Lets get started&lt;/p&gt;</description></item></channel></rss>