Matt's essential software list

I've written in the past about the steps I take to perform a clean install and listed the software I use on a daily basis. Today I'll walk you through my software for 2011 - the applications that I find indispensible as a Web Developer for the Windows stack. Alas, I won't be going into as much detail as Scott Hanselman, more of a summary to look back on in a year or two and compare any changes.

Please note: these are listed in alphabetical order and for each application, assume I use the latest version (unless otherwise stated):

Found something in the list you hadn't heard of, or that you're already using? Let me know what you think and if you have anything additional to recommend.

comments Posted: Tuesday 1st March 2011, 05:51pm
Categories: Articles
Tags: software

Terminals

If you regularly connect to multiple servers, using RDP or a similar protocol (VNC etc.), then you probably have a good memory of all the various IPs/Hostnames of the servers. Either that, or you keep them in a document and regularly copy/paste to connect.

Personally, I have to connect to 9 of my own servers along with 40+ servers at work on a daily basis. For home, I kept 9 separate RDP connections saved to my Desktop, cluttering it up with their icons. This worked for a while, but was cumbersome and inefficient. At work, we keep a spreadsheet of IPs for each server and over a period of time you begin memorising each.

So I started looking for a better solution, one that would store each of my required server connections in an orderly fashion, allowing me to connect to multiple servers at once from within a single interface. I soon came across Terminals, a secure, multi tab terminal services/remote desktop client. It stores the configuration in ASP.NET's .config file, an XML style format which allows you to easily take your saved list of connections with you to another install.

Terminals

It's also very configurable with more options than the standard RDP client and also supports VNC, VMRC and many other protocols, allowing you to combine your server connection tools into one. And you can tag connections, allowing you to group them into logical categories - for me, per Active Directory domain/location.

If you meet the criteria, then give Terminals a go.

comments Posted: Sunday 11th April 2010, 05:51pm
Categories: Computers and Technology
Tags: software

Clean Install

Recently, I've been asked to perform a clean install on friend's laptop/desktop PCs. I reckon over the past few years I've installed an operating system over 100 times, of all different flavours. Off the top of my head, I've sat waiting for the following to complete:

Microsoft's Operating Systems are a firm favourite, apart from Millennium Edition - but I forgive them for that. Regardless of the Operating System in question, the process is pretty much the same for all:
  1. Copy all relevant files to another drive (network/external)
  2. Format the hard drive
  3. Pop-in the O/S CD/DVD and follow the instructions
  4. Restart
  5. Install the latest drivers (usually in a specific order)
  6. Restart
  7. Install updates
  8. Install software required
  9. Optimise
  10. Defrag
  11. Test
To elaborate, 1 should include all of the user(s) files which are located in C:\Documents and Settings or C:\Users by default on Microsoft Windows. I also grab any application specific files that would be needed, such as Save Games and configuration files. Then check for drivers that are lying around - Dell tend to put theirs in C:\Drivers or C:\DELL - so copy them to another drive too.

Step 2 is fairly straight forward and can be combined with 3 - as many Operating System installations allow you to format the drive(s) during the process. If you feel it's necessary, run a format utility on the drive to wipe them prior to installation - DBAN is good for this. The installation process can vary from 15 minutes or so, all the way up to a couple of hours. Microsoft seem to be doing better these days, as I've found the installation times with Vista and Windows 7 are far quicker than those of XP and older versions.

A restart is essential after installation. You may need to change the boot sequence within the BIOS on older hardware, to ensure it doesn't perform the whole process over again.

Once you're into your Operating System of choice, it's then a case of ascertaining which Drivers are needed. Usually, the more recent the Operating System, the less drivers you'll need to install - this is due to the vendors packaging many popular Drivers with the O/S.

You have 2 options whilst installing the Drivers - either restart in-between each install, or skip the restarts and wait until all are installed. The former is preferred, as it ensures each Driver is installed correctly and loaded prior to moving onto the next. It also allows you to resolve conflicts quicker if required.

Then you can move onto the updates. Linux/Mac fans would argue that they can get by without updates, but Microsoft users are veteran update installers. Choose wisely, opt for all critical and security updates, then trawl through the optional ones and ascertain whether or not you'd need them. I recommend Microsoft's Update website over the built-in Automatic Updates for pre-Vista O/S's, as it includes all Microsoft Updates, not just those specific to the O/S.

Step 8 is specific to your requirements, but if you've restored a PC to factory settings - now is the time to remove the excess crap that many Manufacturers install. Then add any additional software that you need. My current suite includes:

For my servers, it's usually just updates and then the software required for the Server's role.

Then move onto step 9, which for me involves running msconfig and removing startup programs not needed. Then look at all of the services and disable any unnecessary ones. Finally, tailor the settings to your needs, such as Folder Options within Control Panel and the Taskbar/Start Menu settings.

Finally, give the PC a Defrag. Afterall, it's just had a kicking in the hard drive department. Then it's a case of testing everything works as you'd expect and start using the machine.

Let me know if you do anything different and any interesting stories of your clean install encounters.

comments Posted: Thursday 24th September 2009, 05:51pm
Categories: Articles, Computers and Technology
Tags: microsoft, operating-system, software, windows