<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Msi on ETDWH.com</title><link>https://www.etdwh.com/tags/msi/</link><description>Recent content in Msi on ETDWH.com</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 18 Jun 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://www.etdwh.com/tags/msi/index.xml" rel="self" type="application/rss+xml"/><item><title>Microsoft Deployment Toolkit (MDT) for newbies - Part 5</title><link>https://www.etdwh.com/posts/mdt-part-5/</link><pubDate>Fri, 18 Jun 2021 00:00:00 +0000</pubDate><guid>https://www.etdwh.com/posts/mdt-part-5/</guid><description>&lt;p&gt;In our final part, we want to create the offline media to use to reimage our physical machines.&lt;/p&gt;</description></item><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>SETTING UP A VIRTUAL SCCM TESTLAB – PART 5</title><link>https://www.etdwh.com/posts/setting-up-a-virtual-sccm-testlab-part-5/</link><pubDate>Wed, 19 Oct 2016 00:00:00 +0000</pubDate><guid>https://www.etdwh.com/posts/setting-up-a-virtual-sccm-testlab-part-5/</guid><description>&lt;p&gt;In the last 4 parts, we looked at of setting up a SCCM test lab and have now deployed our first application.&lt;/p&gt;
&lt;p&gt;In this post, we will look at how the deployed application looks on the client side and install this new application.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;This post was delayed as I was looking into SCCM 2016 and investigating the upgrade paths&lt;/p&gt;
&lt;/blockquote&gt;</description></item><item><title>Visio Viewer 2016 Not Working On Windows 7</title><link>https://www.etdwh.com/posts/visio-viewer-2016-not-working-on-windows-7/</link><pubDate>Wed, 27 Jul 2016 00:00:00 +0000</pubDate><guid>https://www.etdwh.com/posts/visio-viewer-2016-not-working-on-windows-7/</guid><description>&lt;p&gt;Recently I have been troubleshooting an issue I had with &lt;a href="https://www.microsoft.com/en-us/download/details.aspx?id=51188"&gt;Visio Viewer 2016&lt;/a&gt; on Windows 7. The application appears to install just fine, all Visio drawing files appears with the correct icons and is now associated with Internet Explorer. But once you open the file, the plugin or viewer does not load in Internet Explorer.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Note&lt;/strong&gt; : This was tested on Windows 7, but it applies to Windows Server 2008 R2 as well. It is in fact where I first encountered the error&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><item><title>PowerShell App Deployment Toolkit</title><link>https://www.etdwh.com/posts/powershell-app-deployment-toolkit/</link><pubDate>Fri, 22 Apr 2016 00:00:00 +0000</pubDate><guid>https://www.etdwh.com/posts/powershell-app-deployment-toolkit/</guid><description>&lt;p&gt;&lt;a href="http://psappdeploytoolkit.com/"&gt;&lt;img src="images/AppDeployToolkitBanner2.png" alt="AppDeployToolkitBanner2"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;In my line of work, knowledge of how installations work is crucial. And with that knowledge, comes experience making terrible vendor installations work properly in an enterprise environment. For years, the standard solution, when troubleshooting and experimenting was going nowhere, was to repackage the troublesome app. Where experimenting lead somewhere, there might have been an eventual VB script written to cater for all the complexities involved to get everything working properly.&lt;/p&gt;
&lt;p&gt;Some of the common challenges were&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Show a nice interface to let users know something was happening, for silent installs&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install admin (system context) and user level files or registry keys, from the same script.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Return proper error codes back to the deployment system (commonly SCCM)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Link together several installations&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Switch between install types (interactive, passive or silent; pulled install, task sequence, server install, etc)&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;These were common problems, and in some cases, you had to make several installation scripts, to cater for different scenarios. Ok, if you had enough time, you could create a script that accepted certain parameters on launch, to do different things. But in the rush to meet SLAs, you would do the most urgent thing first, and then go back to revisit the app later, when a different scenario was needed.&lt;/p&gt;
&lt;p&gt;Which is why I was happy to find the &lt;a href="http://psappdeploytoolkit.com/"&gt;PowerShell App Deployment Toolkit&lt;/a&gt;, as a common deployment toolkit to help with the common packaging and deployment issues.&lt;/p&gt;</description></item></channel></rss>