<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Update on Nico Maas</title>
        <link>https://www.nico-maas.de/tags/update/</link>
        <description>Recent content in Update on Nico Maas</description>
        <generator>Hugo -- gohugo.io</generator>
        <language>en-us</language>
        <lastBuildDate>Wed, 02 Jan 2019 10:00:00 +0000</lastBuildDate><atom:link href="https://www.nico-maas.de/tags/update/index.xml" rel="self" type="application/rss+xml" /><item>
            <title>Windows 10 Update Error 0x80070001</title>
            <link>https://www.nico-maas.de/posts/2019-01-02-windows-10-update-error-0x80070001/</link>
            <pubDate>Wed, 02 Jan 2019 10:00:00 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2019-01-02-windows-10-update-error-0x80070001/</guid>
            <description>&lt;p&gt;I had two Windows 10 machines which had stopped pulling upgrades from Microsoft for quite long (1703, anyone?) and I could not get it back working.&lt;br&gt;&#xA;Windows Update just showed me the error 0x80070001 and did refuse to do anything.&lt;/p&gt;&#xA;&lt;p&gt;Tried:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Clearing Windows Update Cache&lt;/li&gt;&#xA;&lt;li&gt;WSUS Offline Patching (installed the updates, but the normal Windows Update did not start working after that&amp;hellip;)&lt;/li&gt;&#xA;&lt;li&gt;Windows Update Repair Tool from Microsoft&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Nothing did really work, until I stumbled upon a post by OksiQuatzel:&lt;br&gt;&#xA;Culprit was the installed ImDisk, a virtual Floppy Drive. With this installed and an A Drive mounted - this error arose.&lt;br&gt;&#xA;As soon as I unmounted the drive and removed the driver - everything started working again.&lt;br&gt;&#xA;Kind of nuts that something like this could occur.&lt;/p&gt;</description>
        </item><item>
            <title>[Dell] Using the Update CDs to get Dell Servers to latest firmware</title>
            <link>https://www.nico-maas.de/posts/2017-12-18-dell-using-the-update-cds-to-get-dell-servers-to-latest-firmware/</link>
            <pubDate>Mon, 18 Dec 2017 11:00:58 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2017-12-18-dell-using-the-update-cds-to-get-dell-servers-to-latest-firmware/</guid>
            <description>&lt;p&gt;Dell has an very comfortable way of getting new firmware to nearly all of its server components: The bootable media / ISO or Update CDs. You can find them on &lt;a class=&#34;link&#34; href=&#34;https://www.dell.com/support/article/us/en/04/sln296511/updating-dell-poweredge-servers-via-bootable-media---iso?lang=en&#34;  target=&#34;_blank&#34; rel=&#34;noopener&#34;&#xA;    &gt;this&lt;/a&gt; website and very useful. On a basic level, you pick your server, download the ISO, compare the MD5 checksum and burn the ISO onto a DVD. After that, you should get the Servicetag of your server and check for BIOS and iDRAC updates - these should be installed manually first. After that, boot from the DVD and let it install all the needed firmware. Basically, the DVD will cycle through all firmware of components ever installed in the series of your particular server and installs updates if needed. After another reboot, you&amp;rsquo;re done :).&lt;/p&gt;</description>
        </item><item>
            <title>[Docker] Keep Docker Container up-to-date with Watchtower</title>
            <link>https://www.nico-maas.de/posts/2016-05-12-docker-keep-docker-container-up-to-date-with-watchtower/</link>
            <pubDate>Thu, 12 May 2016 08:00:59 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2016-05-12-docker-keep-docker-container-up-to-date-with-watchtower/</guid>
            <description>&lt;p&gt;If you&amp;rsquo;re using Docker, you know you will need to update these containers from time to time by hand. Mostly with an docker pull repo/DockerContainerName and an docker-compose up -d. If you want to automate this, you can now use Watchtower: &lt;a class=&#34;link&#34; href=&#34;https://github.com/CenturyLinkLabs/watchtower&#34;  target=&#34;_blank&#34; rel=&#34;noopener&#34;&#xA;    &gt;https://github.com/CenturyLinkLabs/watchtower&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Using it, is very easy. Just run following command to let all your containers automatically update via watchtower:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;docker run -d \&#xD;&#xA;  --name watchtower \&#xD;&#xA;  -v /var/run/docker.sock:/var/run/docker.sock \&#xD;&#xA;  centurylink/watchtower&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;If you want choosen containers to be updated, include the names of the running containers as arguments, i.e.:&lt;/p&gt;</description>
        </item><item>
            <title>[Win] Update DeltaCopy</title>
            <link>https://www.nico-maas.de/posts/2013-09-08-win-update-deltacopy/</link>
            <pubDate>Sun, 08 Sep 2013 14:57:45 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2013-09-08-win-update-deltacopy/</guid>
            <description>&lt;p&gt;In terms of backups, I still love Rsync / DeltaCopy. Rsync is an awesome protocol, as it does only transmit data changes. So it is extremly useful if you are running on an slow dataconnection and try to backup big data chunks or files you are working on. It does save time as well.&lt;/p&gt;&#xA;&lt;p&gt;The problem: DeltaCopy (which was developed by Synametrics) is not supported anymore and has been replaced by their (non free) tool Syncrify. (And no, the free Personal Edition does not count as a useable alternative!). Problem with DeltaCopy would be the really old Version of the used rsync Part. But don&amp;rsquo;t worry, it is really easy to update that one (and that will resolve many problems including the ones experienced with special character filenames etc).&lt;/p&gt;</description>
        </item><item>
            <title>HTC Universal</title>
            <link>https://www.nico-maas.de/posts/2011-04-01-htc-universal/</link>
            <pubDate>Fri, 01 Apr 2011 09:00:53 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2011-04-01-htc-universal/</guid>
            <description>&lt;p&gt;I found a &amp;ldquo;bricked&amp;rdquo; HTC Universal without - everything.&lt;br&gt;&#xA;So I decided to piece it back together.&lt;br&gt;&#xA;First thing to find was an USB Cable to recharge the battery.&lt;br&gt;&#xA;Working is an normal Mini USB Cable, even tough the connector looks different.&lt;/p&gt;&#xA;&lt;p&gt;After that, I found out that the HTC was a brick.&lt;br&gt;&#xA;So to unbrick:&lt;/p&gt;&#xA;&lt;p&gt;get mtty1.42.exe, enter bootloader mode , (Power + Light Bulb + Reset)&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Stop Activesync USB connection&lt;/li&gt;&#xA;&lt;li&gt;Uni : Reboot Bootloader then Connect USB&lt;/li&gt;&#xA;&lt;li&gt;PC : Run mtty1.42.exe&lt;/li&gt;&#xA;&lt;li&gt;Choose USB in &amp;ldquo;Port&amp;rdquo; (Reconnect if can&amp;rsquo;t find/reconglize USB and try remove sim and sd card)&lt;/li&gt;&#xA;&lt;li&gt;type : task 28 55aa&lt;/li&gt;&#xA;&lt;li&gt;Press Enter&lt;/li&gt;&#xA;&lt;li&gt;Cause DOC reformatted, so there&amp;rsquo;s no rom in DOC ,try reflash any rom that you like .&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;For task 28 55aa in mtty success , will show the message (attachment )&lt;/p&gt;</description>
        </item></channel>
</rss>
