Using a mobile phone to help out in a crisis – with ICE

This content is 19 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

I’ve received this from a couple of sources and it seems to be both genuine and a really good idea. Since last Thursday’s attacks in London, this campaign has gained a lot of momentum and many people will already have received e-mail about this but just in case you haven’t seen it, then I’m sending it to your feed reader!

In Case of Emergency - ICEThe East Anglian Ambulance NHS Trust have launched a national “In Case of Emergency” (ICE) campaign. The idea is that you store the word “ICE” in your mobile phone address book, along with the number of the person you would wish to be contacted in case of emergency.

In an emergency situation ambulance and hospital staff will then be able to quickly find out who your next of kin are and be able to contact them. It’s so simple that everyone can do it.

For more than one contact name, multiple ICEs can be defined (ICE1, ICE2, ICE3, etc.).

Quoting from the original ICE press release:

“A Cambridge-based paramedic has launched a national campaign with Vodafone to encourage people to store emergency contact details in their mobile phones.

Bob Brotchie, a clinical team leader for the East Anglian Ambulance NHS Trust, hatched the plan last year after struggling to get contact details from shocked or injured patients.

By entering the acronym ICE – for In Case of Emergency – into the mobile’s phone book, users can log the name and number of someone who should be contacted in an emergency.

The idea follows research carried out by Vodafone that shows more than 75 per cent of people carry no details of who they would like telephoned following a serious accident.

Bob, 41, who has been a paramedic for 13 years, said: ‘I was reflecting on some of the calls I’ve attended at the roadside where I had to look through the mobile phone contacts struggling for information on a shocked or injured person. It’s difficult to know who to call. Someone might have ‘mum’ in their phone book but that doesn’t mean they’d want them contacted in an emergency. Almost everyone carries a mobile phone now, and with ICE we’d know immediately who to contact and what number to ring. The person may even know of their medical history.'”

More information is available at the ICE – In Case of Emergency website.

Internet Explorer displays credentials in status bar when used as an FTP client

This content is 19 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

A couple of weeks back, one of my clients pointed out that when he opens files from an FTP site using Internet Explorer (IE) as an FTP client his user name and password is displayed in the status bar at the bottom of his browser window.

FTP credentials visible in IE status bar

I seem to have the same problem with various flavours of Windows (2000, XP and 2003), a variety of IE patch levels, and can repeat it against both Unix and Windows-based FTP servers. I’ve not been able to test with older browser versions but as IE6 is the current version, this is my main concern.

One would think that there would be loads of information out on the ‘net about this but I can’t find much at all (except some reference to the issue in an internetfixes.com tip), which seems to suggest IE6 SP1 fixed this strange behaviour. Indeed, I built a PC with Windows XP SP1 (slipstreamed) and the issue was not there; however it reappeared after I upgraded to Windows XP SP2. I know the password will always be passed over the wire in clear text, and that RFC 2396, which defines the generic syntax for URIs (specifically section 3.2.2) recommends against the use of the format “user:password” in the userinfo field of the URL, but that’s just the way that FTP has been implemented! All I want to do is to prevent IE from displaying it in the status bar. As for ISA Server capturing the details in the proxy server logs… well that’s a whole new can of worms.

The strange thing is that a colleague who is using the same Internet Explorer version as me (6.0.2900.2180.xpsp_sp2_gdr.050301.1519 at update version SP2) can not repeat the issue.

It doesn’t help that IE version numbers don’t seem to increment as patches are applied. There is an interesting discussion of the merits of the Microsoft IE version number approach vs. the Mozilla Firefox approach in the comments to the April IE Security Update is available post on the IEBlog, and for anyone searching for information on the various versions of IE, the version numbers and associated Windows operating system version are all listed in Microsoft knowledge base article 164539. What I can’t find is any information on the fixes which update the last portion of the version number (i.e. from 6.0.2900.2180.xpsp_sp2_rtm.040803-2158 to 6.0.2900.2180.xpsp_sp2_gdr.050301.1519), although Microsoft knowledge base article 824994 does describe the significance of release to manufacturing (RTM), general distribution release (GDR), service pack (SPX) and quick fix engineering (QFE) software update packages and there is an article about the package installer (formerly called update.exe) for Microsoft Windows operating systems and Windows components in the Microsoft Windows Server 2003 TechCenter, which describes the multiple-branch-aware structure used for Microsoft patches.

I’ve spent hours loading patches one by one onto a client to see if the issue is resolved as a side-effect of a posted hotfix but can’t seem to get anywhere on this. The only answers I hear are “use the insert product name here FTP client” (incidentally, my preference is FileZilla) or “use SFTP”. What I’d like to hear is “apply Microsoft update xxxxxx“.

Towards operational excellence on the Microsoft platform

This content is 19 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

I was sorting out my den/office this weekend and came across a Microsoft operational excellence resource CD. The concept seems quite good (although the content seemed a little out of date, even bearing in mind that it had sat in a pile of “stuff to look at when I have time” for 10 months); however, the operational excellence section of the Microsoft website is worth a look.

The mobile networks didn’t collapse

This content is 19 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Following yesterday’s atrocities in London, it was widely reported that the mobile phone networks collapsed under the strain of those caught up in the chaos trying to contact their friends, family, work colleagues and vice versa.

In a statement from Vodafone yesterday lunchtime:

“The news networks have been reporting that Vodafone have shut down the network to ordinary users in the London area because of the incidents reported this morning. This is NOT the case, although customers will be experiencing severe congestion in the London area. However, [The Metropolitan Police] have asked us to invoke [ACcess Over Load Control (ACOLC), which restricts the network to emergency services only] in one base station in the Kings cross area, and this should be switched on imminently.”

Anyone worried about relatives or friends they have not heard from is advised to contact a special police hotline on +44 (0)870 156 6344.

The wonderful thing about web standards

This content is 19 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Alex and I were having a rant discussion a few days back about web standards after I pointed out to him that Firefox and Safari not being able to supply login credentials within a URL meant they were not RFC-compliant in this respect (and he accused me of being sponsored by Microsoft)!

I know that there are many pieces of Microsoft software where the standards have been “extended” or “enhanced” and this week I heard that they are going to extend RSS when it is integrated into the next version of Windows (codenamed Longhorn); but we had both hoped that the Mozilla browsers would be better in this respect (in general, they are).

I like Firefox. In fact the only reason that I’ve gone back to Internet Explorer (IE) is that a huge number of websites (about 10% according to IT Week) only work properly with IE and some mis-identified Firefox as a very old Netscape browser. Now that IE’s market share has slipped to about 85% and Firefox is gaining momentum, all we need to do is to persuade web designers to code sites to work with all common browsers.

It would be so much easier for web designers, IT administrators, and IT architects alike if all browsers complied with standards. In another IT Week article, Bill Pechey highlights a UK government department of trade and industry (DTI) report that suggests standards promote healthy growth.

I’m hoping that Microsoft’s forthcoming IE 7 browser will be fully web standards compliant (and if it has to support Microsoft-proprietary extensions as well then that is fine as long as it can properly render standard pages). That remains to be seen but meanwhile it’s good news that Microsoft is collaborating with the Web Standards Project to promote open standards.

Get Firefox!

(and just to show that I’m not biased…Internet Explorer).

Readvertising failed packages with Microsoft SMS

This content is 19 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

A few weeks back, my colleague Barry Feist gave me a useful tip for when deploying software using Microsoft Systems Management Server (SMS). Barry doesn’t have his own blog, so here are the details.

Details of commands executed on the local machine by SMS are held at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Mobile Client\Software Distribution\Execution History\packageid. It is not uncommon for there to be a failure within a distribution, so to rerun a failed installation, delete the key and re-advertise the package. According to the how to re-advertise a package post on MyITForum, Microsoft knowledge base article 257271 gives an alternative solution but Barry’s solution seems simpler to me.

Tips and tricks for using Microsoft SharePoint Portal Server 2003

This content is 19 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Last year, I blogged about understanding, and developing with, SharePoint products and technologies and a few months back I attended a workshop on designing IT platform collaborative applications with Microsoft SharePoint 2003. I haven’t had time to digest and blog my notes from that course, but one of the things I came away with was Microsoft’s tips and tricks for using Microsoft SharePoint Portal Server 2003 white paper. Looks useful for anybody starting out in SharePoint administration.

Some more about sIDHistory

This content is 19 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

A few weeks back I was looking at migrating users between forests using ADMT when the source and target domain names are similar. It worked in my virtual environment but when we went to put it into practice there were some issues caused by different people’s perception of what the sIDHistory attribute will do.

sIDHistory will not avoid the need to enter the correct password to access resources in the original domain.

If there is a trust in place, then the trusting domain will trust users in the trusted domain.

If there is no longer a trust (or as in my client’s case, where there was no direct trust but a sequence of non-transitive external trusts) then sIDHistory will allow migrated users security credentials to be compared with the access control entries (ACEs) in the access control list (ACL) for a resource and if there is a match then they will be authorised; however they still need to be authenticated.

If the passwords are the same in the new and the old domains, then there will be no password prompt (as the hashes will match and the user will authenticate transparently); however if there are different passwords in use, then the correct password for the user’s old account in the resource domain will still need to be supplied.

Further reading

Unable to browse users in trusted domain (Microsoft knowledge base article 263956).
How to use Active Directory Migration Tool version 2 to migrate from Windows 2000 to Windows Server 2003 (Microsoft knowledge base article 326480).
How to Troubleshoot Inter-Forest sIDHistory Migration with ADMTv2 (Microsoft knowledge base article 322970).

Use drag and drop to quickly open files in Notepad

This content is 19 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

I use Windows Notepad a lot and, a few months back, I posted a tip for Send to… Notepad to help people open text files from a context-sensitive right click. Whilst watching me struggle to edit a load of text files with strange file extensions (as he taught me how to use PHP yesterday), Alex came up with another suggestion. It’s probably well known, but if you create a link to Notepad on the Windows quick launch bar (just drag and drop from the start menu), you can drag and drop files onto it and they will open in Notepad. Simple, but very, very useful!

Can you help to make poverty history?

This content is 19 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Yesterday’s Live 8 concerts were a fantastic spectacle. I know that many critics doubt the effect that the Live 8 campaign can have; and as this is a technology blog I will put aside the politics, but one thing the Live 8 event has done is to grab the attention of the media (I guess bloggers are a small part of that group) and the general public (I definitely fit there) and focus it on the G8 summit, something which most of us would normally ignore.

I watched a big chunk of the UK coverage on television (but didn’t stay up to 4am to see the end of the US concert) and for me the favourites had to be the original Pink Floyd (reunited after 24 years – as one banner said “pigs have flown: Pink Floyd reunited”), The Who? and Faithless (we saw a short clip from the concert in Berlin). The great thing about these events is that you also hear acts that you wouldn’t normally pay any attention to – I thought Joss Stone was great; caught the end of the Snow Patrol set; and was pleasantly surprised to enjoy what I saw of Craig David’s acoustic set in Paris. I missed the Madonna set (which was reported to be fantastic), and was underwhelmed by the much-hyped Paul McCartney and U2 version of Sergeant Pepper’s Lonely Hearts Club Band but the McCartney performance of All along the Watchtower was great – it would have been cool if he’d played that with U2 (as they have both recorded it)…

Take part in the Make Poverty History campaign by adding your name to the list.

Links

Live 8 Live
Make Poverty History
White Band