<?xml version='1.0' encoding='UTF-8'?><rss xmlns:atom='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' version='2.0'><channel><atom:id>tag:blogger.com,1999:blog-15591336</atom:id><lastBuildDate>Thu, 11 Mar 2010 11:04:33 +0000</lastBuildDate><title>The Bit Bucket</title><description>A real world view inside the IT industry with articles covering all sorts of items. All feedback is welcome and comments, suggestions, etc can be posted here or direct to me by emailing me on blog@gdwnet.com</description><link>http://blog.gdwnet.com/</link><managingEditor>noreply@blogger.com (Gary Williams)</managingEditor><generator>Blogger</generator><openSearch:totalResults>159</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-15591336.post-2348971006548497097</guid><pubDate>Thu, 11 Mar 2010 11:04:00 +0000</pubDate><atom:updated>2010-03-11T11:04:33.479Z</atom:updated><title>This blog has moved</title><description>&lt;br /&gt;       This blog is now located at http://gdwnet.blogspot.com/.&lt;br /&gt;       You will be automatically redirected in 30 seconds, or you may click &lt;a href='http://gdwnet.blogspot.com/'&gt;here&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;       For feed subscribers, please update your feed subscriptions to&lt;br /&gt;       http://gdwnet.blogspot.com/feeds/posts/default.&lt;br /&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591336-2348971006548497097?l=blog.gdwnet.com' alt='' /&gt;&lt;/div&gt;</description><link>http://blog.gdwnet.com/2010/03/this-blog-has-moved.html</link><author>noreply@blogger.com (Gary Williams)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-15591336.post-4665713339347769962</guid><pubDate>Mon, 01 Feb 2010 13:01:00 +0000</pubDate><atom:updated>2010-02-05T12:12:06.246Z</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Administrivia</category><title>Catching up</title><description>I've been a bit remiss in not updating my blog for several months. A few combinations of a sudden urgent project, the wife having knee surgery and a flood at home all conspired to steal a lot of my time and then, of course, the inevitable run up to Christmas with all the fun and games of Christmas shopping in the snow.&lt;br /&gt;&lt;br /&gt;I have been thinking about what to do with the blog, should I continue it? should I change it or should I just close it? I'm not playing with enough new technology to bring anything wonderful and astounding to the site and my time is ever more limited but I'd like to keep the blog going with a few war stories and other things.&lt;br /&gt;&lt;br /&gt;Thoughts?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591336-4665713339347769962?l=blog.gdwnet.com' alt='' /&gt;&lt;/div&gt;</description><link>http://blog.gdwnet.com/2010/02/catching-up.html</link><author>noreply@blogger.com (Gary Williams)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>1</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-15591336.post-2882985826799970616</guid><pubDate>Mon, 28 Sep 2009 07:10:00 +0000</pubDate><atom:updated>2009-09-28T13:24:25.838+01:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>War Stories</category><title>Upcoming Week</title><description>I already know it's going to be one of "those" weeks, but then I guess it always is, there is always something that turns a nice quiet, productive week into a nightmare. This week hasn't even started properly yet and it already has the feel of problems.&lt;br /&gt;&lt;br /&gt;Put simply, this week is going to be all about shuffling data from one location to another, the sheer joys of being taken over and having to comply with another companies standards. It doesn't help that our permissions are a total disgrace. If you think of the standard rules of users into groups and assign the groups permissions.. well, we haven't done that. we don't even come close so permissions changes are proving to be a stumbling block.&lt;br /&gt;&lt;br /&gt;We also have a subsidiary company that has been bought out by another company. Data transfer to the new location is proving to be another interesting experience, I cannot, for the life of me, understand why people cannot get organised and actually work out before hand what it is they need and so this is leading to a lot of last minute requests... situation normal I suppose.&lt;br /&gt;&lt;br /&gt;Add this to the fact that Netapp have discovered another bug in their firmware this time and this bug is a good one. It seems that only on the 3070 cluster the bug will result in a reboot of the filer leading to a panic. Nice. I had this happen to one of the filers in Cambridge and now it seems that the only way to fix it is by being onsite with a laptop and a serial cable....&lt;br /&gt;&lt;br /&gt;More updates coming soon and I'm thinking of changing this blog into more of a war stories blog with the occasional bit of technical information rather than leaving it a few months between updates.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591336-2882985826799970616?l=blog.gdwnet.com' alt='' /&gt;&lt;/div&gt;</description><link>http://blog.gdwnet.com/2009/09/upcoming-week.html</link><author>noreply@blogger.com (Gary Williams)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-15591336.post-1054367885077449105</guid><pubDate>Tue, 07 Jul 2009 11:01:00 +0000</pubDate><atom:updated>2009-07-07T12:07:57.694+01:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Tools</category><title>TaskCoach</title><description>There are a lot of little tools out there which can &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_0"&gt;&lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_0"&gt;allegedly&lt;/span&gt;&lt;/span&gt; help you get more organised, better with time management, etc, etc. Personally I find most of the tools are more &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_1"&gt;&lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_1"&gt;awkward&lt;/span&gt;&lt;/span&gt; to use and so consume time that is better spent on actually do the stuff that needs doing.&lt;br /&gt;&lt;br /&gt;However, I did find &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_2"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_2"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_0"&gt;TaskCoach&lt;/span&gt;&lt;/span&gt;&lt;/span&gt; which is a simple enough .&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_3"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_3"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_1"&gt;exe&lt;/span&gt;&lt;/span&gt;&lt;/span&gt; file that I can around on &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_4"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_4"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_2"&gt;USB&lt;/span&gt;&lt;/span&gt;&lt;/span&gt; stick, any task that needs doing I stick into there. It's possible to organise by &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_5"&gt;category&lt;/span&gt; and to set deadlines on. It's short of a few features I would like, for example, no software seems to get the idea of chained-tasks, that is where one task has to be completed before another starts so as soon as you flag the first task as complete the second appears.&lt;br /&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_6"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_5"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_3"&gt;TaskCoach&lt;/span&gt;&lt;/span&gt;&lt;/span&gt; does have quite a powerful category system for organising items into different groupings and I'm using this to organise work tasks by week number. This is a very useful way of seeing what I've got on for the week and what can be &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_7"&gt;&lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_6"&gt;deferred&lt;/span&gt; &lt;/span&gt;to a later week.&lt;br /&gt;&lt;br /&gt;All in all it's a lovely little tool. Now, all I need is a checklist tool.....&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591336-1054367885077449105?l=blog.gdwnet.com' alt='' /&gt;&lt;/div&gt;</description><link>http://blog.gdwnet.com/2009/07/taskcoah.html</link><author>noreply@blogger.com (Gary Williams)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-15591336.post-6020806116267367971</guid><pubDate>Sun, 05 Jul 2009 20:28:00 +0000</pubDate><atom:updated>2009-07-05T21:43:28.206+01:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>War Stories</category><category domain='http://www.blogger.com/atom/ns#'>Processes</category><title>Why change control can be a Bad Idea</title><description>I'm sure that many people have had to endure the torture that is a change control process. In short, change control is a process whereby changes to a system have to be approved by a change control panel.&lt;br /&gt;Generally, the panel is a group of people who probably don't know about the system and/or don't much care about it so you have to be quite vocal in why and change might be needed.&lt;br /&gt;The actual ideal behind change control is to moderate changes to a system in such a way that should a system fail or have problems it should be possible to use the change control tool to work out what recent changes had been applied and undo those changes or research/test to see if those changes could be the root cause the issue. Sounds ideal doesn't it? In reality it never works that way.&lt;br /&gt;&lt;br /&gt;In the long run a change control tool can actually do more damage that it's designed to prevent. How come?&lt;br /&gt;&lt;br /&gt;Let's say that you have a website which has a fairly minor bug. Let's say that you know that the change control process will take two weeks to follow it's winding path and that you will need to invest about four hours to write and &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_0"&gt;represent&lt;/span&gt; what is, at best, a 20 minute change.&lt;br /&gt;&lt;br /&gt;What do you do?&lt;br /&gt;&lt;br /&gt;Do you spend the time and fix the bug or do you forget about it and press on with the several hundred other things that's on your list?&lt;br /&gt;&lt;br /&gt;Let's say you pick the second option (and I don't blame you if you do because I've done that) and several months later that small issue could explode to be a big issue.&lt;br /&gt;&lt;br /&gt;And that's why change control systems need to be as flexible as possible otherwise what &lt;span style="font-style: italic;"&gt;appear&lt;/span&gt; to be minor changes &lt;span style="font-weight: bold;"&gt;will&lt;/span&gt; be &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_1"&gt;quietly&lt;/span&gt; shelved and in the long run that can lead to a major incident.&lt;br /&gt;&lt;br /&gt;I'll provide some suitably altered real world examples in a future article.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591336-6020806116267367971?l=blog.gdwnet.com' alt='' /&gt;&lt;/div&gt;</description><link>http://blog.gdwnet.com/2009/07/why-change-control-can-be-bad-idea.html</link><author>noreply@blogger.com (Gary Williams)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-15591336.post-2773790939345249775</guid><pubDate>Sat, 04 Jul 2009 11:01:00 +0000</pubDate><atom:updated>2009-07-04T18:48:53.507+01:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Administrivia</category><title>Marriage!</title><description>It's certainly been a busy previous six months. Not only the company take over but I got married last week.&lt;br /&gt;&lt;br /&gt;The amount of work required for a wedding reminds me of one of those projects with an unmissible deadline except in this case the deadline really is unmissible!! Once a date is set, that's it. Full steam ahead until the big day and wow, what a day. For me, the big day was June 29th and it was too hot. Mind you, we had some lovely photos taken down by the river and then off for the honeymoon in Paris.&lt;br /&gt;&lt;br /&gt;Now that I'm back at home things feel like they are calming down but I'm sure the next major piece of work isn't far away.... why do I  have the feeling that my wife wants to have most of the rooms redecorated......!&lt;br /&gt;&lt;br /&gt;Anyway, here is to you Krys.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591336-2773790939345249775?l=blog.gdwnet.com' alt='' /&gt;&lt;/div&gt;</description><link>http://blog.gdwnet.com/2009/07/marriage.html</link><author>noreply@blogger.com (Gary Williams)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-15591336.post-6591785880668199227</guid><pubDate>Wed, 10 Jun 2009 11:01:00 +0000</pubDate><atom:updated>2009-06-11T14:09:50.285+01:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Projects</category><category domain='http://www.blogger.com/atom/ns#'>War Stories</category><category domain='http://www.blogger.com/atom/ns#'>commentary</category><title>Software is not a panacea - Part 2</title><description>In the previous article I raised the fictional scenario of a company wanting to automate a timesheet submission process. In this article I'd like to touch on some of the project processes that would be used by the majority of companies.&lt;br /&gt;&lt;br /&gt;Generally, most companies will start off with the sensible process of evaluating existing software packages, looking at what's out there and maybe even seeing what other companies use. After a period of time a sensible company will come to the conclusion that there is no one piece of software that fits their requirements and so &lt;span style="font-style: italic;"&gt;their requirements must change as well as some processes. &lt;/span&gt;This is a key point as every company likes to think that they are unique and so around that uniqueness certain process have appeared so when it comes to upgrade or computerise those processes they are reluctant to change them.&lt;br /&gt;&lt;br /&gt;However, back here in the real world most companies will do one of three things, they will&lt;br /&gt;&lt;ol&gt;&lt;li&gt;Abandon the idea&lt;/li&gt;&lt;li&gt;Buy the commercial package closet to their requirements and get it customised&lt;/li&gt;&lt;li&gt;Hire a developer to write a bespoke piece of software&lt;/li&gt;&lt;/ol&gt;Of the above three options the first is the best and safest but at this point many companies make another fundamental mistake. &lt;span style="font-style: italic;"&gt;They never document the issues found or the reason for the project to be abandoned. &lt;/span&gt;This means that often someone else will reopen the project 6 to 12 months later, reinvestigate options and then select  option 2 or 3.&lt;br /&gt;&lt;br /&gt;Option 2 is an interesting one, surely there can't be much wrong with making some customisations could there?&lt;br /&gt;Well, it depends. If the software is designed to allow those customisations then go ahead. However, may companies will want to alter certain business logic (e.g. maybe three people would have to approve a timesheet and the system, by design, only allows a maximum of two.&lt;br /&gt;Quite often a company will purchase development skills and get the codebase changed to support what they require. This causes a problem when upgrades are required or if a security hole is discovered as often the customised verison &lt;span style="font-style: italic;"&gt;will break when patches for the mainline system are applied&lt;/span&gt; if it's even possible to apply them at all.&lt;br /&gt;Now the company ends up in a situation where they like and want the features in the next version but are tied to an old version due to the customisations, often they will have to face the choice of staying with the customised version, migrating to the new version or paying out to get the customisations in the new version.&lt;br /&gt;&lt;br /&gt;Option 3 opens up all sorts of interesting possibilities for problems and complications to occur but I'll save that one for another blog&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style: italic;"&gt;&lt;span style="font-style: italic;"&gt;&lt;/span&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591336-6591785880668199227?l=blog.gdwnet.com' alt='' /&gt;&lt;/div&gt;</description><link>http://blog.gdwnet.com/2009/03/software-is-not-panacea-part-2.html</link><author>noreply@blogger.com (Gary Williams)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-15591336.post-6852966380288792117</guid><pubDate>Tue, 24 Mar 2009 12:01:00 +0000</pubDate><atom:updated>2009-03-24T16:50:04.505Z</atom:updated><title>Software is not a panacea - Part 1</title><description>There have been many times where I've come across situations where people have this mistaken belief that software will fix all their ills. Surely, anyone with a few years experience know that software is merely a tool designed to fix a problem the way the programmer/designer intended it to be fixed and not the way that &lt;span style="font-weight: bold;"&gt;you&lt;/span&gt; expect it to be fixed.&lt;br /&gt;&lt;br /&gt;There is often a huge disparity in the way a company wants a problem to be fixed compared to the way the software actually fixes it and this leaves the company with three options, namely:&lt;br /&gt;a. Change the processes to fit the software.&lt;br /&gt;or&lt;br /&gt;b. Change the software to fit the process.&lt;br /&gt;or&lt;br /&gt;c. Write their own software.&lt;br /&gt;&lt;br /&gt;Let's take the classical scenario of a time recording and billing application. Let's say that company X records time on paper sheets which then get passed to finance to generate the bills and send out to the clients. Let's say that the company bills on 15 minute intervals based on a client code.&lt;br /&gt;&lt;br /&gt;Obviously, the above scenario  is crying out for some sort of automation, the amount of time and money that can be saved with an online tool means it's worth investing in the hardware and IT departments time to get such a system installed.&lt;br /&gt;&lt;br /&gt;In the next article I'll take a closer look at the process many companies follow for such a project.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591336-6852966380288792117?l=blog.gdwnet.com' alt='' /&gt;&lt;/div&gt;</description><link>http://blog.gdwnet.com/2009/03/software-is-not-panacea-part-1.html</link><author>noreply@blogger.com (Gary Williams)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>1</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-15591336.post-1577804006552310026</guid><pubDate>Thu, 26 Feb 2009 12:01:00 +0000</pubDate><atom:updated>2009-02-26T12:01:00.700Z</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Idle Ramblings</category><category domain='http://www.blogger.com/atom/ns#'>commentary</category><title>Gameforge supports theft</title><description>Up until a few days ago I played ogame. This is a browser based online game where thousounds of people interact to steal and trade resources. It was the sort of game that you could spend 10-20 minutes on throughout the course of a day and provided a welcome respite from work.&lt;br /&gt;My finacee also played it for similar reasons. She played for almost a year and I did for 2 and a half years.&lt;br /&gt;&lt;br /&gt;That is, until the other day. Because I was helping out my financee (which is within the rules) and because she was on the same IP address (also within the rules) when the resources arrived (against the rules) we both got banned until 2036. Now, I'm not disputing the ban. We both violated one small part of the terms and conditions. The penalities for that are a permanent ban which seems a little draconian but that's how it is.&lt;br /&gt;&lt;br /&gt;So, Ban in place I decided to ask for my money back as I've got 8 months left to run on the account only to be told to go away.&lt;br /&gt;&lt;br /&gt;So, bewary of online games especially of places like gameforge who will happily take your money and then ban you for an infraction.&lt;br /&gt;&lt;br /&gt;This to me is theft - a bought for service is not being provided, they won't transfer the subscription to another account and they won't refund me.&lt;br /&gt;&lt;br /&gt;So, thanks to Gameforge I'll not be trusting any MMO ever again.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591336-1577804006552310026?l=blog.gdwnet.com' alt='' /&gt;&lt;/div&gt;</description><link>http://blog.gdwnet.com/2009/02/gameforge-supports-theft.html</link><author>noreply@blogger.com (Gary Williams)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-15591336.post-3871625216064361287</guid><pubDate>Sat, 14 Feb 2009 12:02:00 +0000</pubDate><atom:updated>2009-02-14T12:12:53.976Z</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Idle Ramblings</category><title>Company Takeover</title><description>The company where I work has just been taken over by a much larger organisation. I'm not going to say where I work for now as enough has been plastered over the technical press but I'll have a few things to say on the matter much later on.&lt;br /&gt;&lt;br /&gt;It's an interesting time for both good and bad reasons. Obviously the economic problems have hit both companies hard so the usual bans on travel and overtime have come into force. This presents a problem for us IT Department types who have been given a lot of work to do around the integration and are going to have to take time off in lieu for it. At the end of the year I think they will have many staff out as they will have leave that they will have to take. Hell, they will probably buy it off us!!&lt;br /&gt;&lt;br /&gt;The current plan is to re-ip all the devices as the company that has taken us over use the same IP range as we do and this is right on the back of recently relocating them all to new data centres do yet more out of hours work and then fixing things that break.&lt;br /&gt;&lt;br /&gt;The Chinese have a curse "&lt;a href="http://en.wikipedia.org/wiki/May_you_live_in_interesting_times"&gt;May you live in interesting times&lt;/a&gt;" and for the next few months those times sure will be interesting....&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591336-3871625216064361287?l=blog.gdwnet.com' alt='' /&gt;&lt;/div&gt;</description><link>http://blog.gdwnet.com/2009/02/company-takeover.html</link><author>noreply@blogger.com (Gary Williams)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-15591336.post-6139901323241633624</guid><pubDate>Thu, 15 Jan 2009 12:01:00 +0000</pubDate><atom:updated>2009-01-15T16:28:44.203Z</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Administrivia</category><title>Busy Project Time (2).........</title><description>So, It's January 2009 and not much has changed, it's still busy project time. Unsurprisingly the server migration which absolutely, totally HAD to be completed by the end of December 2008 wasn't. How the project manager expected 79 servers and a lot of filer data to be moved in less than three months was beyond me but as with so many projects here the project managers are under the thumb from higher ups to deliver so often the way they do this is to pass on only good news to the higher ups whilst pressurising the staff to do the job no matter the cost...&lt;br /&gt;&lt;br /&gt;Still, as the company is being taken over there is hope that this will change. Time will tell. With a little luck I'll be back blogging my normal nonsense very soon.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591336-6139901323241633624?l=blog.gdwnet.com' alt='' /&gt;&lt;/div&gt;</description><link>http://blog.gdwnet.com/2009/01/busy-project-time-2.html</link><author>noreply@blogger.com (Gary Williams)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-15591336.post-2180802542113020618</guid><pubDate>Fri, 17 Oct 2008 11:01:00 +0000</pubDate><atom:updated>2008-10-17T15:21:19.652+01:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Projects</category><category domain='http://www.blogger.com/atom/ns#'>Administrivia</category><title>Busy Project Time.........</title><description>Just when you think it's all going to be quiet and maybe it will be a good time to get those niggling little tasks out of the way and to be able to sit down and write some decent blog articles someone comes up with the idea of decommissioning a server room to save on power. So now I'm involved in a project that requires the relocation of about 4TB of data to another filer, including updating and moving the servers that use the filer data....&lt;br /&gt;&lt;br /&gt;Yes, it's going to be a busy few months.&lt;br /&gt;&lt;br /&gt;And a project manager just asked me if I needed any help installing IIS...... Sometimes I'd rather be doing anything else than working in IT.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591336-2180802542113020618?l=blog.gdwnet.com' alt='' /&gt;&lt;/div&gt;</description><link>http://blog.gdwnet.com/2008/10/busy-project-time.html</link><author>noreply@blogger.com (Gary Williams)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-15591336.post-831799597107199529</guid><pubDate>Mon, 15 Sep 2008 11:01:00 +0000</pubDate><atom:updated>2008-09-15T16:03:17.740+01:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Technical</category><category domain='http://www.blogger.com/atom/ns#'>Tips</category><title>Some DNS Tips</title><description>Several times in just the past week I've had to deal with &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_0"&gt;DNS&lt;/span&gt; entries that have made things a touch more painful than they should have been so I thought it might be time for me to jot down a few notes on how &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_1"&gt;DNS&lt;/span&gt; should be configured to save IS people's sanity!&lt;br /&gt;&lt;br /&gt;First up the &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_2"&gt;DNS&lt;/span&gt; servers themselves. You should always have a primary and secondary which generally, speaking are two different &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_3"&gt;DNS&lt;/span&gt; servers at your &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_4"&gt;ISP's&lt;/span&gt; location. If two are not available you should consider switching &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_5"&gt;ISP's&lt;/span&gt;. Personally, I use three. Two from my &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_6"&gt;ISP&lt;/span&gt; and one from &lt;a href="http://www.opendns.com/"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_7"&gt;OpenDNS&lt;/span&gt;.&lt;/a&gt; This way, should the &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_8"&gt;ISP&lt;/span&gt; change for any reason and/or should access be denied to the &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_9"&gt;ISP's&lt;/span&gt; &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_10"&gt;DNS&lt;/span&gt; servers I've got a third, totally separate service available to me.&lt;br /&gt;&lt;br /&gt;Next up, A records. These should always point to the &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_11"&gt;IP&lt;/span&gt; address of the server in question and they should always use the &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_12"&gt;hostname&lt;/span&gt; of the server. Sure, this can lead to some unfriendly names but it's really handy to know the proper &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_13"&gt;hostname&lt;/span&gt; of the server. If you want to use something 'pretty' then use &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_14"&gt;CNames&lt;/span&gt;. When you create the A record make sure the &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_15"&gt;PTR&lt;/span&gt; record is also created in the reverse look up zone. This way, when you are trying to work out what physical server a &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_16"&gt;CName&lt;/span&gt; is all you have to do is a reverse &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_17"&gt;lookup&lt;/span&gt; against the &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_18"&gt;IP&lt;/span&gt; address.&lt;br /&gt;&lt;br /&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_19"&gt;MX&lt;/span&gt; Records should also have two internal/DMZ based mail servers which they can deliver to and a third at the &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_20"&gt;ISP&lt;/span&gt; which can retry delivery to your internal servers at a later date.&lt;br /&gt;&lt;br /&gt;These are simple tips and they (or variants of them) can be found as best practice advice for standard &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_21"&gt;DNS&lt;/span&gt; configurations.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591336-831799597107199529?l=blog.gdwnet.com' alt='' /&gt;&lt;/div&gt;</description><link>http://blog.gdwnet.com/2008/09/some-dns-tips.html</link><author>noreply@blogger.com (Gary Williams)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-15591336.post-6083651987407629315</guid><pubDate>Mon, 08 Sep 2008 11:01:00 +0000</pubDate><atom:updated>2008-09-08T14:27:38.870+01:00</atom:updated><title>Understanding your environment</title><description>A practical demonstration of why understanding your environment is vital occurred a few evenings ago when some NetApp filer\domino work went wrong. A little bit of background first, domino data is stored on a NetApp filer which is shared using nfs. This is mounted by the domino server and it all (most of the time) works.&lt;br /&gt;&lt;br /&gt;For some reason this particular server running Domino (let's call him Bob) was showing high i/o stats, although the server itself was responding fine. The filer (Nutkins) wasn't reporting any problems but it was deemed that Nutkins had to be at fault. There are a lot of connections to Nutkins after all and in fairness the mount point is living in an aggregate that is unbalanced in terms of i/o profile so the decision was made to create a new aggregate decided for Bob. Simple enough to do. For those not filer aware an aggregate is a collection of physical disks. In giving Bob his own aggregate it dedicated 8 spindles to the Domino data. More than enough to remove any i/o bottleneck.&lt;br /&gt;&lt;br /&gt;Now, Nutkins itself has a very cool piece of technology called snapmirror. A snapmirror was duly setup and Nutkins began copying the data to its new home.&lt;br /&gt;&lt;br /&gt;So, the big evening arrives. The paperwork is signed (in blood, naturally). The changes authorised, the servers poised.......  A hush descends and the commands to stop Domino are typed into Bob......... and Domino promptly hangs.&lt;br /&gt;&lt;br /&gt;Red flag  1 - when a manager says "oh, it always does that. Just issue kill -9 and everything will be fine, well except that a few databses might be corrupt" it's probably time to start worrying. However, the final snapmirror is initiated and the last 140mb of changes are copied (in 22 seconds no less, not even enough time to get a cup of tea). The snapmirror is then quiesed and broken. This makes the destination for the snapmirror writable. Over to the unix admin and a few key clicks later the export is mounted and Bob was started.........&lt;br /&gt;Or not. Seems that a small fact was missed. Bob not only has data stored on Nutkins but also has a local directory for crash dump logs.&lt;br /&gt;&lt;br /&gt;Red-flag 2 - when Bob's admin doesn't know the configuration of Bob's setup it  is probably time to start panicking. Anyway, a tappety-tap of the keyboard and the directory is created. Oh, lets stop and start Bob hoping red flag 1 doesn't pop up. Mr. Unix issues the command and on the screen "server shutdown. Bob_stop not found". Ok, so did it shut down or not? Ps -ef | grep lotus and nope, nothing running. Red flag 1 avoided! So, start Bob and..... Nothing. Not happy. Hmmm. Time to fail back, something isn't understood\not working.. So Mr. Unix does his stuff and...... No Bob. Seems red flag 1 corrupted the data then the final snapmirror copied corrupt data. Also seems that the shutdown script has at least one bug in it which causes a loop to fail when the script is executed.&lt;br /&gt;&lt;br /&gt;Anyway, to cut a long story short we backed out and made the change a few days later. There are several lessons learnt here mostly revolving around documentation, standarisation and knowing your environment. I'll leave it as an excercise to the reader to work out the rest!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591336-6083651987407629315?l=blog.gdwnet.com' alt='' /&gt;&lt;/div&gt;</description><link>http://blog.gdwnet.com/2008/09/understand-your-environment.html</link><author>noreply@blogger.com (Gary Williams)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-15591336.post-577173206541642803</guid><pubDate>Thu, 21 Aug 2008 11:01:00 +0000</pubDate><atom:updated>2008-08-23T13:14:55.776+01:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Tools</category><category domain='http://www.blogger.com/atom/ns#'>Active Directory</category><title>AD Find</title><description>AD Find is the second of the two tools I managed to find in the same week. This little tool weighs in at just 700K for the download and about 2&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_0"&gt;mb&lt;/span&gt; for the actual file. This tool does exactly what it says, it finds things in Active Directory. The clever part about it is it's possible to say exactly what you want to get back and the format it should be in.&lt;br /&gt;As an example, a few weeks back I had the issue with &lt;a href="http://blog.gdwnet.com/2008/07/legacy-systems-and-very-handy-sql.html"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_1"&gt;Bindview&lt;/span&gt; not liking non-ASCII characters&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;Now, the version of &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_2"&gt;Bindview&lt;/span&gt; that's being used where I work is a very old NT4 only aware application which means it will update the &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_3"&gt;SAMAccountName&lt;/span&gt; attribute but not the display name.&lt;br /&gt;&lt;br /&gt;This isn't a problem as there is a &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_4"&gt;workflow&lt;/span&gt; from an HR application which deals with all of that, all &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_5"&gt;bindivew&lt;/span&gt; should be doing is delegated group permissions (and yes, I know it's much easier in &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_6"&gt;AD&lt;/span&gt; but &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_7"&gt;thats&lt;/span&gt; a war story for another time).&lt;br /&gt;&lt;br /&gt;Anyway, I was curious to know how many &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_8"&gt;SAMAccountNames&lt;/span&gt; didn't match up with display names so I used &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_9"&gt;ADFind&lt;/span&gt; to display the &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_10"&gt;CN&lt;/span&gt;, &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_11"&gt;Samaccountname&lt;/span&gt;, mail, &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_12"&gt;firstname&lt;/span&gt; and &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_13"&gt;lastname&lt;/span&gt; fields in a &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_14"&gt;CSV&lt;/span&gt; format which could then be processed by a filer in Excel. Much quicker than messing around with the native Active Directory tools.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591336-577173206541642803?l=blog.gdwnet.com' alt='' /&gt;&lt;/div&gt;</description><link>http://blog.gdwnet.com/2008/08/ad-find.html</link><author>noreply@blogger.com (Gary Williams)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-15591336.post-3553708430804750745</guid><pubDate>Thu, 21 Aug 2008 11:01:00 +0000</pubDate><atom:updated>2008-08-22T10:34:21.537+01:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Tools</category><category domain='http://www.blogger.com/atom/ns#'>Active Directory</category><title>AD Explorer from Sysinternals</title><description>Sometimes it's possible to stumble upon a tool and wonder just how you would have gotten a task accomplished without it. Last week I had the good fortune to stumble upon two such applications right at the time when I needed them most. I did consider buying a lottery ticket that evening!&lt;br /&gt;&lt;br /&gt;The first one is AD Explorer and it's from &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_0"&gt;sysinternals&lt;/span&gt; and it's exactly what it says, a explorer tool for Active Directory. It allows viewing, searching and editing of the AD in ways that are far &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_1"&gt;superior&lt;/span&gt; to Active Directory Users and Computers. I suspect the only thing that AD users and computers can do (or do better) that this tool cannot are password changes, &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_2"&gt;logon&lt;/span&gt; hour restrictions and limiting &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_3"&gt;logon&lt;/span&gt; &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_4"&gt;ID's&lt;/span&gt; to specific computers.&lt;br /&gt;&lt;br /&gt;One very nice feature this tool has is the ability to take a snapshot of an Active Directory and compare it to another snapshot. Doing this shows just how many changes occur in the AD in just a few days. It's also a great way to see how many differences &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_5"&gt;accumulate&lt;/span&gt; between your production and test active directory environments.&lt;br /&gt;&lt;br /&gt;Overall this is a fantastic tool and one I'll be using when the MS &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_6"&gt;technotes&lt;/span&gt; require delving into some obscure key via &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_8"&gt;ADSIEdit&lt;/span&gt;. I'll also be using it in place of tools like &lt;a href="http://www.ldapadministrator.com/"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_9"&gt;Softerras&lt;/span&gt; &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_10"&gt;LDAP&lt;/span&gt; browser&lt;/a&gt; unless I need to something &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_11"&gt;LDAP&lt;/span&gt; &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_12"&gt;specfic&lt;/span&gt;.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591336-3553708430804750745?l=blog.gdwnet.com' alt='' /&gt;&lt;/div&gt;</description><link>http://blog.gdwnet.com/2008/08/ad-explorer-from-sysinternals.html</link><author>noreply@blogger.com (Gary Williams)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-15591336.post-2516739840078936736</guid><pubDate>Fri, 01 Aug 2008 11:01:00 +0000</pubDate><atom:updated>2008-08-01T14:45:18.185+01:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Friday Rants</category><category domain='http://www.blogger.com/atom/ns#'>War Stories</category><title>Why Total Cost of Ownership is a fallacy</title><description>If I have one more potential supplier try and sell me something on the lie that it will "reduce TCO" I will not only scream but I will beat them to death with a CAT 5 cable.&lt;br /&gt;&lt;br /&gt;Total Cost of Ownership (TCO) is one of those almost unmeasurable  values that seems to have pride of place in the salespersons portfolio. How do they KNOW a new system (with it's associated equipment, licensing and training costs) will work out cheaper than the old one?&lt;br /&gt;The idea is that newer systems have better support so rather than training someone in an older system and maybe having to buy in more expensive skills more legacy systems it works out cheaper to upgrade or replace with the latest model.&lt;br /&gt;&lt;br /&gt;I don't disagree that for some systems which are truly legacy such the old DOS or OS/2 application may well work out cheaper in the long run but the one thing that will truly reduce TCO?&lt;br /&gt;&lt;br /&gt;&lt;li&gt;Understand your systems.&lt;/li&gt;&lt;br /&gt;&lt;li&gt;Take time to test and document the fixes.&lt;/li&gt;&lt;br /&gt;&lt;li&gt;Use your call logging system as a knowledge base.&lt;/li&gt;&lt;br /&gt;&lt;br /&gt;These three tips alone will truly reduce TCO.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591336-2516739840078936736?l=blog.gdwnet.com' alt='' /&gt;&lt;/div&gt;</description><link>http://blog.gdwnet.com/2008/08/why-total-cost-of-ownership-is-fallacy.html</link><author>noreply@blogger.com (Gary Williams)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-15591336.post-8663441858256023475</guid><pubDate>Tue, 15 Jul 2008 11:01:00 +0000</pubDate><atom:updated>2008-07-16T14:09:49.409+01:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Training</category><category domain='http://www.blogger.com/atom/ns#'>Administrivia</category><title>VMWare course</title><description>For much of this week I'm on a VMWare course for the second half of my VMWare training. This part of the course is titled Deploy, Secure and Analyse. The course itself is to prepare me for a server consolidation project that the company I work for is kicking off.&lt;br /&gt;The project invovles several VMWare clusters, a Hitachi SAN and blades. Lots of flashing lights and new technology to &lt;del&gt;break&lt;/del&gt; support.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591336-8663441858256023475?l=blog.gdwnet.com' alt='' /&gt;&lt;/div&gt;</description><link>http://blog.gdwnet.com/2008/07/vmware-course.html</link><author>noreply@blogger.com (Gary Williams)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-15591336.post-9126764948753814345</guid><pubDate>Sun, 13 Jul 2008 15:16:00 +0000</pubDate><atom:updated>2008-07-15T13:55:54.587+01:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>NT4</category><category domain='http://www.blogger.com/atom/ns#'>Tools</category><category domain='http://www.blogger.com/atom/ns#'>Tips</category><category domain='http://www.blogger.com/atom/ns#'>War Stories</category><category domain='http://www.blogger.com/atom/ns#'>Active Directory</category><title>Legacy Systems and a very handy SQL comparrison Tool</title><description>On Friday, I had the "pleasure" of having to get a legacy system up and running.&lt;br /&gt;This system was originally introduced to allow users in the business to manage group membership for projects they had ownership of. The idea was that it would cut down user calls to the service desk by about 10% and allow the project managers themselves to get a speedier turn around for new starters.&lt;br /&gt;Sounds fine in theory and in the world of NT4 it wasn't a problem. Move on to the world of Active Directory and things are a little different. The legacy system (&lt;a href="http://www.cstl.com/products/Symantec/Symantec-bindview/Symantec-bindview.asp"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_0"&gt;Bindview&lt;/span&gt;&lt;/a&gt; v4.6) has been &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_1"&gt;superceded&lt;/span&gt; about 5 times over but we can't just install the latest version. Trust me on this, the latest version is fine but there are many design decisions and compromises as well as several rejections for upgrading the system from a few years back that have all &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_2"&gt;combined&lt;/span&gt; to lead to the current problem.&lt;br /&gt;&lt;br /&gt;The actual problem was an interesting one. The system was complaining whenever anyone tried to edit a group. A restore of the back end &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_3"&gt;SQL&lt;/span&gt; database fixed the problem until the next domain sync &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_4"&gt;occurred&lt;/span&gt; when the database would corrupt itself again.&lt;br /&gt;&lt;br /&gt;Obviously, the sync was pulling something from the domain that it didn't like.&lt;br /&gt;For the first attempt at a fix I fired up &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_5"&gt;SQL&lt;/span&gt; Trace which records every single &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_6"&gt;SQL&lt;/span&gt; statement that goes to a selected database. The neat thing about Trace is that it's possible to point the trace results to a &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_7"&gt;SQL&lt;/span&gt; database itself and then filter it to get rid of stuff you know isn't going to help - such as &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_8"&gt;SQL&lt;/span&gt; agent tasks and so on.&lt;br /&gt;Trace left me with a multi-variable &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_9"&gt;SQL&lt;/span&gt; script spanning over 4,000 lines and quite difficult to read or even test so I decided that the next best thing was to restore the working database to new a database name and then find a tool to compare every object on the &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_10"&gt;bindview&lt;/span&gt; user table to see what was different between the restore and the one that &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_11"&gt;synced&lt;/span&gt; with the domain and &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_12"&gt;promptly&lt;/span&gt; broke.&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.adeptsql.com/"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_13"&gt;AdeptSQL&lt;/span&gt;&lt;/a&gt; was the third tool I tried and whilst it has a very simplistic point and click interface it's incredibly powerful for comparing two &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_14"&gt;SQL&lt;/span&gt; databases. Once the &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_15"&gt;comparison&lt;/span&gt; is done you get two side-by-side windows which represent the two databases. Changes are highlighted by colour - Red for deletions, Blue for new and black for no changes.&lt;br /&gt;This left me with a 2,000 list of changes, deletions and amendments in the database.&lt;br /&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_16"&gt;AdeptSQL&lt;/span&gt; also lets you filter things out and by using these features I eventually tracked the problem down to the description field of two user accounts.&lt;br /&gt;These accounts had &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_17"&gt;spurious&lt;/span&gt; characters in them which &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_18"&gt;Bindview&lt;/span&gt; being rather old and totally ASCII &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_19"&gt;prompt&lt;/span&gt; fell over on. Removing these and waiting for a &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_20"&gt;resync&lt;/span&gt; solved the problem.&lt;br /&gt;&lt;br /&gt;&lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_21"&gt;Whilst&lt;/span&gt; &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_22"&gt;AdeptSQL&lt;/span&gt; helped me solve that particular problem there is still the problem of this legacy system updating Active Directory whilst not being active directory aware which leads to some other fun and games with the display name versus the &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_23"&gt;SAMAccount&lt;/span&gt; name but more on that in a later article.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591336-9126764948753814345?l=blog.gdwnet.com' alt='' /&gt;&lt;/div&gt;</description><link>http://blog.gdwnet.com/2008/07/legacy-systems-and-very-handy-sql.html</link><author>noreply@blogger.com (Gary Williams)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-15591336.post-7638597066876578077</guid><pubDate>Mon, 30 Jun 2008 11:01:00 +0000</pubDate><atom:updated>2008-08-03T17:47:02.262+01:00</atom:updated><title>Build your own NAS</title><description>Things have really moved on in terms of storage. Not so long ago the largest hard drive you could buy for a home PC was a 200GB &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_0"&gt;IDE&lt;/span&gt;. Today, 1TB &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_1"&gt;SATA&lt;/span&gt; hard drives are available for less than £100 from my favourite hardware website &lt;a href="http://www.autdirect.co.uk/"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_2"&gt;AUT&lt;/span&gt; Direct&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;I'll admit that I couldn't resist for long and as I've got a tower PC with 6 &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_3"&gt;IDE&lt;/span&gt; hard disks in which are not doing anything at present it was just too much of a lure and I've ordered up 4 1TB disks.&lt;br /&gt;The plan is to replace four of the &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_4"&gt;IDE&lt;/span&gt; disks with these 1TB &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_5"&gt;SATA&lt;/span&gt; drives and I've bought the necessary &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_6"&gt;SATA&lt;/span&gt; drive bays to making swapping them out easier if needed.&lt;br /&gt;&lt;br /&gt;As the motherboard is quite old I also purchased two &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_7"&gt;SATA&lt;/span&gt; cards which will be able to handle the &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_8"&gt;SATA&lt;/span&gt; disks.&lt;br /&gt;&lt;br /&gt;The tower also has two &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_9"&gt;IDE&lt;/span&gt; disks on an &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_10"&gt;IDE&lt;/span&gt; expansion card. This was originally for the OS but I'm going to pull that&lt;br /&gt;and put one of the &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_11"&gt;SATA&lt;/span&gt; cards in it's place. The &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_12"&gt;IDE&lt;/span&gt; disks are small (either 10 or 20GB) which I'm going to bin and replace with two 250GB &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_13"&gt;IDE&lt;/span&gt; disks.&lt;br /&gt;&lt;br /&gt;In total the box will have about 4.5TB raw storage capability. I need to configure the 4 &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_14"&gt;SATA&lt;/span&gt; drives as RAID 5 in case of a failure. I also want to configure the two 250GB &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_15"&gt;IDE's&lt;/span&gt; as RAID1 for the same reason but testing in in &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_16"&gt;VMWare&lt;/span&gt; showed it wasn't quite that easy.&lt;br /&gt;&lt;br /&gt;The operating system of choice will be &lt;a href="http://www.openfiler.com/"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_17"&gt;OpenFiler&lt;/span&gt;. &lt;/a&gt;This OS supports all sorts of storage options including &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_18"&gt;CIFS&lt;/span&gt;, &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_19"&gt;NFS&lt;/span&gt; and &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_20"&gt;iSCSI&lt;/span&gt;. It's free and actually supports more than some hardware solutions such as the &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_21"&gt;Buaffalo&lt;/span&gt; &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_22"&gt;terrastation&lt;/span&gt; I recently bought!&lt;br /&gt;&lt;br /&gt;Even so, When finished and configured with the RAID arrays the box should be able to support an impressive 3.2 or so TB or usable storage.&lt;br /&gt;&lt;br /&gt;A fun little project......!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591336-7638597066876578077?l=blog.gdwnet.com' alt='' /&gt;&lt;/div&gt;</description><link>http://blog.gdwnet.com/2008/06/build-your-own-nas.html</link><author>noreply@blogger.com (Gary Williams)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-15591336.post-3465724144174179669</guid><pubDate>Sun, 29 Jun 2008 11:01:00 +0000</pubDate><atom:updated>2008-06-29T19:16:12.876+01:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Windows 2000</category><category domain='http://www.blogger.com/atom/ns#'>Technical</category><category domain='http://www.blogger.com/atom/ns#'>Tips</category><category domain='http://www.blogger.com/atom/ns#'>Troubleshooting</category><category domain='http://www.blogger.com/atom/ns#'>Knowledge</category><title>Issues upgrading Domain Schema to 2003</title><description>So I'm probably a little behind in upgrading my home networks domain schema to support Windows 2003 but better late than never!&lt;br /&gt;The process itself was smooth enough once I'd corrected some problems on the machine but the upgrade logs were not the most helpful troubleshooting aid I've come across.&lt;br /&gt;One particular error had me stumped for a few days:&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style: italic;"&gt;"Error code: 0x57 Error message: The parameter is incorrect.."&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;No indication of which parameter it was but as it &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_0"&gt;occurred&lt;/span&gt; when checking security descriptors and many blog articles refer to missing security &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_1"&gt;ACL's&lt;/span&gt; on &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_2"&gt;GPO's&lt;/span&gt; I had a look at those and sure enough, &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_3"&gt;Enterprise&lt;/span&gt; admins was missing some rights so I fixed those up and....... the same problem. At this point &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_4"&gt;I'd&lt;/span&gt; admit to a lot of head scratching. The event logs didn't shed much light until I realised that the security event logs were not accessible. Sure enough, somehow the &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_5"&gt;ACL's&lt;/span&gt; on the security event logs had lost all &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_6"&gt;their&lt;/span&gt; rights. Resetting these and then rebooting allowed the process to complete perfectly.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591336-3465724144174179669?l=blog.gdwnet.com' alt='' /&gt;&lt;/div&gt;</description><link>http://blog.gdwnet.com/2008/06/issues-upgrading-domain-schema-to-2003.html</link><author>noreply@blogger.com (Gary Williams)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-15591336.post-3123502685593211539</guid><pubDate>Fri, 20 Jun 2008 09:23:00 +0000</pubDate><atom:updated>2008-06-20T10:32:14.052+01:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>ITIL</category><category domain='http://www.blogger.com/atom/ns#'>Friday Rants</category><title>ITIL Overview Training</title><description>The company I'm currently working at have decided that ITIL is the way forward. Yes, after several years of different ideas, options, tests and other madness they want to adopt the official ITIL framework over a period of 6-7 months.&lt;br /&gt;&lt;br /&gt;Now, whilst I think that ITIL is a good idea and yes, I am something of a convert to the whole ITIL structure I think that the nature of the user/customer base here is simply one that won't tolerate the ITIL way of doing things because it will require &lt;span style="font-style: italic;"&gt;them&lt;/span&gt; to become more proactive and less reactive. I really do believe that many IT departments are products of the greater company in which they find themselves. Have a company that's reactive and unstructured then your IT department will be as well because it &lt;span style="font-style: italic;"&gt;fits in to the business model.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Still, the training was interesting if a little dry and I picked up a few things on Problem Management and Root Cause Analysis. Something I'm very interested in because of the way it deals with problems and provides permanent documented fixes. This is something I'll go into in more detail in a later blog.&lt;br /&gt;&lt;br /&gt;As for ITIL here, well.... I really do hope it works but I can see it being a somewhat half-hearted implementation unless the business are prepared to be a little more structured.&lt;br /&gt;&lt;br /&gt;The final thing I'll say on ITIL is that it's a nice framework with a focus on how IT should be run but it &lt;span style="font-style: italic;"&gt;doesn't&lt;/span&gt; address any sort of approach for bringing it into the business. I know that ITIL practitioners will say that this is because each business is different but it would be nice to read some success stories and find out just how they implemented ITIL and what order they implemented it.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591336-3123502685593211539?l=blog.gdwnet.com' alt='' /&gt;&lt;/div&gt;</description><link>http://blog.gdwnet.com/2008/06/itil-overview-training.html</link><author>noreply@blogger.com (Gary Williams)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-15591336.post-567093874696573691</guid><pubDate>Mon, 09 Jun 2008 11:01:00 +0000</pubDate><atom:updated>2008-06-09T12:01:01.448+01:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Administrivia</category><title>Posting update</title><description>Yes I know I've not posted for a bit. No excuses and I promise I will try to be good for here on in!&lt;br /&gt;&lt;br /&gt;Lot's of changes at work and enough material to fill the blog every day for a year but I do need to actually get on with writing some of it down!&lt;br /&gt;&lt;br /&gt;One article a week from here on in. Not a new years resolution but a start of summer resolution.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591336-567093874696573691?l=blog.gdwnet.com' alt='' /&gt;&lt;/div&gt;</description><link>http://blog.gdwnet.com/2008/06/posting-update.html</link><author>noreply@blogger.com (Gary Williams)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-15591336.post-4827474268106250987</guid><pubDate>Mon, 28 Apr 2008 11:01:00 +0000</pubDate><atom:updated>2008-04-28T17:37:43.720+01:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Security</category><category domain='http://www.blogger.com/atom/ns#'>Infosec</category><title>InfoSec 2008</title><description>Well, After some false starts involving problems with London Undergrounds District Line I made it to Olympia and to &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_0"&gt;Infosec&lt;/span&gt; 2008. The event itself is a good one for picking up the latest trends in security and seeing a few demo's of various products and as always there was some good stuff to see there.&lt;br /&gt;&lt;br /&gt;For example, &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_1"&gt;Sophos&lt;/span&gt; have come on in leaps and bounds and I was most impressed with their new AV console. It can also do NAP (where a machine is quarantined until it means a specific criteria for patches and AV).&lt;br /&gt;&lt;br /&gt;The &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_2"&gt;Sophos&lt;/span&gt; solution also has a web based applet which can be deployed to guest machines (i.e. visitors). The classic here was the sales guy who was demonstrating it was telling me just how clean the solution was "It &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_3"&gt;uninstall's&lt;/span&gt; without a trace so we don't change a THING on the users machine" he extolled. &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_4"&gt;Hmm&lt;/span&gt;. But if it doesn't met the policy then the remediation servers will be the only ones the user can see. This allows the user to update AV definitions and patches. Now, if we can't touch a visitors machine then what's the point? It's a nice technology but worthless for that reason.&lt;br /&gt;Guest machines should be in an isolated &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_5"&gt;vlan&lt;/span&gt; with only net access. They should not only be isolated from the production network &lt;span style="font-style: italic;"&gt;but from each other as well&lt;/span&gt;.&lt;br /&gt;&lt;br /&gt;The Microsoft seminar was superficial but I did learn a few things about their NAT offering in Windows Server 2008 and it does look useful. Certainly on the "to test" list.&lt;br /&gt;&lt;br /&gt;Overall, I came away from &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_6"&gt;Infosec&lt;/span&gt; slightly underwhelmed. There didn't seem to be any new technologies or ideas that made me feel "yes, I like this. This is a good way forward". The last time I had that feeling was with &lt;a href="http://www.splunk.com"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_7"&gt;Splunk&lt;/span&gt;&lt;/a&gt; and I still think that about the product. I do wonder if security is falling into something of a rut just waiting for the next big attack.......&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591336-4827474268106250987?l=blog.gdwnet.com' alt='' /&gt;&lt;/div&gt;</description><link>http://blog.gdwnet.com/2008/04/infosec-2008.html</link><author>noreply@blogger.com (Gary Williams)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-15591336.post-6760440967764770498</guid><pubDate>Mon, 14 Apr 2008 11:01:00 +0000</pubDate><atom:updated>2008-04-14T14:34:39.747+01:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Automation</category><category domain='http://www.blogger.com/atom/ns#'>Windows</category><title>nLite Automated builds</title><description>I'm a big fan of unattended builds and I've been using them for over five years now. The process of creating an unattended build can be somewhat hit and miss so using something like &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_0"&gt;VMWare&lt;/span&gt; to test the final build is often an essential.&lt;br /&gt;&lt;br /&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_1"&gt;nLite&lt;/span&gt; has been around for a while but the last time I used it I found that the resultant build could be flaky and often just not work.&lt;br /&gt;These issues seems to have been fixed with current version as it's remarkably easy to create a custom build and to add service packs, drivers and patches.&lt;br /&gt;&lt;br /&gt;Overall I'm very impressed with the tool and at price tag which is free I really cannot complain!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591336-6760440967764770498?l=blog.gdwnet.com' alt='' /&gt;&lt;/div&gt;</description><link>http://blog.gdwnet.com/2008/04/nlite-automated-builds.html</link><author>noreply@blogger.com (Gary Williams)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item></channel></rss>