Twingle is a windows implementation of Tingle. It tries to replicate the original concept of having an automated update system that tries to invoke at least some logic to things.

You have Windows Updates, right? They can be automatically run on a weekly basis, or they can be run to only download things, pending user confirmation of installation. With Twingle, you (should, ideally), be able to schedule updates for as often as you want, and get some feedback out of your server as the process occurs.

Some things twingle can do for you:

• Automated installation: just say what day/time of the week you want installs, and twingle does the rest!
• But you can still customize the installation
• Notify a robot for humanoid about pending installations
• Installs all, or only important updates
• Notifies any logged in users about pending installations
• Cleans up after itself, just like a toilet-trained puppy!

• Copy the set of twingle files to C:\twingle, or similar
• Run Install Twingle.bat to get the mini-installer
• or run twingle.ps1 -setup -full to get the whole shebang
• automatic installer can be got via twingle.ps1 -setup -auto -day=DAY -time=XXXX
• Set your install day and time (default, weekly), and notification time (3 days before installation)
• Twingle will do the rest!

On setup, Twingle will setup a weekly scheduled task, at your indicated date/time for notify day, to check for pending updates. If there are pending updates, it will queue them for installation, and send an email to somewhere to let you know things are pending. It will then schedule the one-off installation task.

On the install day, Twingle will set off the installation of whatever updates were marked as being installable. Pending your settings, it will then schedule a reboot of the server, and let anyone on the server know that the server is going to go bye-bye's shortly.

In all these items, there are nagios hooks to let some automated system know that something's happening (for you to customize).

This code is currently very much beta. It is a work in progress, and it's written in Powershell. Both these items should indicate that caution should be used when viewing this code.

Two areas of the code that require customisation from the installer are the email and nagios hooks. Just search for CUSTOMISE THIS YOURSELF! to have a squizz at what needs to be changed.

• 0.2.0 : "Stable SP1" release, nothing should actually break. A few bug fixes, but should be OK.
• 0.1.0 : "Stable" release, that actually does a lot of nice things.
• 0.0.1 : Inital commit to public repo. Stripped version of working code, still horrid and full of swearwords.