More on WPAD

This content is 20 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 week I blogged about configuring WPAD for Internet Explorer clients. Since then I’ve come across some more information that might be useful:

Caught by the robot police (smile please – that’ll be 3 points and 60 quid)

This content is 20 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.

Speed camera signI’ve just received a a conditional offer of fixed penalty from Dorset Police after I was detected exceeding the 70mph speed limit on a dual-carriageway near Poole. Me being caught speeding will come as no surprise to those who knew me in my youth, but for a while now I’ve had a clean licence so I’m a little bit annoyed as it was dry, sunny, almost 7pm, I was just 13mph over the limit (on a wide, fast road) and the position of the Dorset Safety Camera Partnership mobile camera unit might have been considered by some to be parked dangerously.

To those who say “there is a sure way to avoid a speeding fine – don’t break the speed limit”, I say “fair comment”; but I find it difficult to believe that there are any drivers out there who do not occasionally stray over the limit and the issue of road safety is much bigger than just speed. I’d like to use this post to highlight my views on how technology could and should be used to improve road safety in the UK.

I don’t want to turn this into a rant but in my research I’ve found that much of the information on the ‘net breaks down into four major areas:

  • Local authority/police “safety partnerships”.
  • Petrolheads who want to be able to drive as fast as they like.
  • Environmental campaigners who want to see speed limits reduced and alternative transport promoted.
  • Technical information about various types of speed detection and/or detection-evasion devices.

My arguments are that technology (remember, this is a technology blog) in the form of “safety” cameras is being used instead of sensible policing; and that technology should be used to drive through road safety schemes that are much broader in scope than the official “Think!” or “Speed Kills – Kill Your Speed” campaigns.

Here’s some of the background information and opinion:

“The number of fixed penalty fines issued in England and Wales has risen seven-fold from around 260,000 in 2000-2001 to 1.8 million in 2003-2004. Speed cameras are reportedly currently netting more than £20m a year profits for the Treasury. Motorists caught by the cameras have three points added to their licence and pay a £60 fixed penalty.”

[UK National Speed Camera Database]

Meanwhile:

“In the 1980s around 15% of police resources went into traffic duties – now that has been cut to 5%… We need more police on traffic duty not less – both to combat road casualties and to encourage better driving standards.”

[Professor David Begg, Chair of the Commission for Integrated Traffic, writing in Police (the newspaper of the Police Federation), March 2004]

“We are told that the speed cameras cut accidents. They are not about safety; they are all about revenue. We are required to cut road deaths by 50 per cent by 2010. With traffic officer numbers down by 2,500 this year, we have more chance of having tea with the Pope than achieving that result.

The public has become alienated from the police. The public supported ‘traffic cops’ even if they were wary, because they could see the value of our work. Speed cameras have made the police the enemy of the motorist, even if we have nothing to do with them. They are seen as the police making money.”

[Un-named police officers writing in Police (the newspaper of the Police Federation), March 2004]

My personal views almost entirely mirror this article on the Association of British Drivers (ABD) website – to quote:

“Firstly, let me make it very plain. I am not against cameras being used as part of a structured, multi-faceted and well thought-out strategy to reduce accidents. What I am against is their proliferation on open roads… and the intention to replace the former methods of traffic behaviour-monitoring and accident reduction with these inanimate eyesores.”

I broke the law by driving at 83mph in a 70mph limit; I’m not trying to justify that. I’d just like to tread the fine line between being “yet another petrolhead” and ending the current obsession with numerical speed – stressing that there is more to road safety than speed limits and traffic calming measures.

Think!Unfortunately, the official campaigns do not recognise that speed (alone) doesn’t kill. Bad driving kills and whilst speed may be a contributory factor in many cases, so is hesitancy, and so is complacency. Too few motorists think of a driving licence as a responsibility, or a car as a 1.5-tonne lump of heavy machinery and targeting speeding is easy, whereas driver education isn’t. Most of us pass a UK Driving Standards Agency test at 17 years of age and many drivers never receive any further training. Last week I heard a radio phone-in on the BBC Radio 2 Jeremy Vine program discussing a “3 strikes and you’re out” caveat on those who find it difficult to reach the required standard to pass the driving test – what I didn’t hear anyone say (and what I’d rather see) is that perhaps pressure should be brought on the government to introduce compulsory re-assessment of driving standards (for example, every 10 years), or even a local voluntary scheme to increase standards. I certainly found my company-sponsored Royal Society for the Prevention of Accidents (RoSPA) defensive driving course an excellent eye opener (although almost 9 years ago now) and have even paid for additional motorcycle training.

This month is the RAC Foundation, Auto Express magazine, the Institute of Advanced Motorists (IAM) and BSM‘s National Motorway Month. Quoting from the RAC Foundation’s news release:

“In 2004, National Motorway Month covered the themes of tailgating, middle lane hogs, nervous drivers and driver fatigue. In 2005 the campaign will focus on:

  • Worst driving habits.
  • Causes of congestion.
  • Causes of accidents.
  • Standards of driving on motorways.

Key findings from the campaign last year were:

  • Over 40 per cent of motorists drive too close to the car in front on motorways.
  • One-third of lane capacity is being wasted at peak times due to poor lane discipline on the motorways.
  • More than 50 per cent of motorists habitually drive for more than two hours on long motorway journeys without taking a break.
  • More than one-third (ten million) drivers admit to regular feelings of anxiety when driving or considering driving on the motorways.”

Bad driving is not just a motorway problem. In my experience, driving across the country, at the start and end of the day schools often have parents’ cars illegally double-parked outside, seriously restricting visibility for children crossing the road (at one memorable location in Slough they were even parked with all four wheels on the pavement) whilst nobody checks the speed of nearby motorists (when even a perfectly legal 30mph may be an inappropriate speed). Meanwhile “safety camera vehicles” can be seen on a summer evening close to 70mph roads constructed only a few years ago (if these roads are dangerous at that time of the evening then they were poorly designed, or not wide enough!). It’s not just the public that drive badly either – most Police drivers today receive very little in the way of additional driver training and one of my friends often comments on the time I was forced to sound my horn to indicate my presence when cut up by a Police driver (non-emergency).

I live in a small market town, close to the county borders of Northamptonshire, Bedfordshire and Milton Keynes. Neighbouring Northamptonshire County Council has spent huge sums of money on road safety measures such as new refuges at junctions, but (along with many authorities) in 2004 it failed to grit major roads when winter weather was forecast – the result being rain freezing to ice followed by 4-5cm of snow the next day and traffic chaos.

One stretch of the A428 between Northampton and Bedford – one of Northamptonshire’s red routes – now has so many information and warning signs at some junctions that it could be considered difficult to take in all the information (even at well below the speed limit). Additionally, there is a SPECS system in place with no posted repeater speed limit signs (because the national speed limit is in place there is no legal need to display such signs), resulting in drivers slowing from a legal 60mph to as low as 30mph, but more typically 40-50mph); meanwhile last year the route was littered with signs encouraging drivers to slow down but which were so difficult to read with small lettering that they can actually cause accidents (e.g. “want to kill something – kill your speed”, “speeding fills hospital beds”, or signs detailing the number of casualties on the road in the last 3 years).

Sadly, many of the fatalities on this stretch of road occurred within days of some resurfacing work (and no warning signs of the new surface) a few years back – it is worrying to read that a type of surface for which safety has been called into question elsewhere in Europe is still routinely used in the UK.

At other locations there are the inconsistent signs and road markings that could cause confusion and accidents – for example last time I looked, the A43 between Northampton and M1 junction 15A had painted lane markings for the M1(N) which contradicted the overhead signs and a sign nearby which read “check your lane”!

Adding to this:

“Local roads are in their worst condition for 30 years, with consequences for traffic flow and safety.”

[UK Government Department for Transport]

So what’s the point of all this rambling? Basically, instead of the UK Government’s proposed national congestion charging scheme and the ever-rising use of “safety” cameras (coupled with reduced numbers of real police), I’d like to see technology used to good effect, increasing road safety through:

  • An increase in the use of variable speed limits on urban motorways, but only if the restrictions are cleared as soon as any danger has ended (e.g. fog has lifted, traffic levels have dropped), and possibly linked to higher limits on all motorways when visibility is good and traffic is light (analysis of European speed limits and accident rates shows no correlation between high speeds on motorways and increased levels of fatalities).
  • Engineering works to improve safety at dangerous junctions (e.g. grade-separated junctions replacing flat crossings on all trunk routes).
  • Assessment of information displayed on major road “matrix” signs every 15 minutes (so that out-of-date information is removed and up-to-date information is provided).
  • Removal of blatant revenue-raising “safety” cameras and redeployment to areas where they could have a real impact on saving lives.
  • A re-test for all drivers every 10 years, assessing their ability to cope with dangerous situations (e.g. using a simulator).

This application of technology to the problem should be supplemented with:

  • Reinstatement of real police, who understand what is bad driving and what isn’t, equipped with the necessary tools and training to carry out their job effectively.
  • Consistent application of speed limits across England and Wales with regular posting of repeater signs (even if the national speed limit is in place).
  • Consistent directional signing and road markings.
  • Removal of all distracting signage with small lettering.
  • Prompt and effective repairs to all roads where maintenance is required.

I’m conscious that I’ve linked many of the “petrolhead” articles in this post (as well as respectable organisations such as the RAC Foundation and the IAM); but in the interests of fairness and balance, I’d also like to highlight organisations with the opposite view:

  • The Slower Speed initiative is campaigning for a reduction in speed on our roads.
  • Transport 2000 campaign on a wide range of transport topics including lower speeds (interestingly they comment on the Association of British Drivers as “well known for hating speed cameras and, one assumes, anything that stops them going as fast as they like” – I have linked a couple of ABD articles in this post but can’t say I agree with everything on their website).
  • Brake – the road safety charity.

Finally, for a tongue in cheek look at driving standards in the UK today, I recommend that you check out Ian Everleigh’s New Highway Code.

The Microsoft view of connected systems

This content is 20 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 at a breakfast briefing on connected systems (Microsoft’s view of web services and BizTalk Server), delivered by David Gristwood (one of Microsoft UK’s Architect Evangelists). Even though I’m not a developer, I think I understood most of what David had to say (although many of my colleagues’ blogs will undoubtedly have more to offer in this subject area).

David explained how the need to connect applications has led to a shift towards service orientation as applications have longer lifetime and no longer consist of just a single executable program. Consequently there are requirements for application customisation and integration (generally loosely coupled) with the four tenets of a service oriented architecture (SOA) being:

  • Explicit boundaries.
  • Autonomous services (i.e. other services do not have to wait for your schedule).
  • Shared schema and contract (not class).
  • Compatibility based on policy (generally written in XML).

The Web Services Interoperability Organization‘s WS-* architecture is about providing a framework for web services with broad industry support (in the same way that the open system interconnection 7 layer network model has become the industry model for networking).

WS-I web services standards stackBasic web services operate well but are easy to make inoperable. As such WS-I is concerned with identifying the lowest common denominator – the basic profile (BP) or core set of specifications that provide the foundation for web services.

When developing web services, Visual Studio 2005 (codenamed Whidbey) will represent a huge step forward with the Microsoft .NET Framework v2.0 including numerous improvements in the web services protocol stack and ASMX (ASP.NET web services) representing an ongoing evolution towards the Windows communication foundation (formerly codenamed Indigo).

Although coding first and using web methods is still a good way to producing web services, there is a move to interface-based service contracts – first designing the interface using web service definition language (WSDL) and then adding contracts. The new application connection designer (ACD) (codenamed Whitehorse) is a visual tool to drag and drop connections which represent service contracts, allowing the generation of skeleton projects and the basic code required to implement/consume contracts.

In terms of standards and interoperability, this code is WS-I BP 1.1 compliant by default (and hence fits well into the WS-* architecture), whilst ASMX web services automatically support simple object access protocol (SOAP) 1.1 and 1.2.

Web services enhancements (WSE) is a fully supported download which sits on top of ASMX and extends the existing web services support within the Microsoft .NET Framework. WSE is a set of classes to implement on-the-wire standards and is actually an implementation of several WS-* specifications including WS-Addressing and WS-Security, to provide end-to-end message-level security (in a more sophisticated manner than SOAP over HTTP). The current version is WSE 2.0 SP3, and WSE 3.0 will be released with Visual Studio 2005 (due to a dependency on the Microsoft .NET Framework v2.0), with new features including:

  • Message transmission optimization mechanism (MTOM) for binary data transfer, replacing SOAP with attachments and WS-Attachments/direct Internet message encapsulation (DIME).
  • Enhancements to WS-Security/WS-Policy.

It should be noted that there are no guarantees that WSE 2.0 and 3.0 will be wire-level or object-model compatible, but there will be side-by-side support for the two versions. WSE 3.0 is likely to be wire-compatible with the Windows communication foundation (which will ultimately replace WSE around the end of 2006).

The Windows communication foundation itself is about productivity (writing less code), interoperability (binary, highly-optimised interoperability between computers, dropping to WS-I BP 1.1 if required) and service oriented development. Implemented as a set of classes, the Windows communication foundation takes messages, transforms them, maps them to a structure and pushes them to the receiving code.

To illustrate the productivity gains, using an example cited by Microsoft, an application implemented using Visual Studio .NET 2003 consisting of 56296 lines of code (20379 lines of security, 5988 lines for reliable messaging, 25507 lines for transactions, and 4442 lines for infrastructure) was reduced using WSE to 27321 lines of code (10 lines for security, 1804 lines for reliable messaging, and no change to the 25507 lines for transactions) and reduced further using the Windows communication foundation to just 3 lines of code (1 line for security, 1 line for reliable messaging and 1 line for the transactions)! This sounds extreme to me; but even an infrastructure architect like myself can appreciate that less code means easier management.

Evolution of Microsoft.NET FrameworkIn terms of a roadmap, the Windows communication foundation will supersede existing connected systems technologies (e.g. ASMX), but other technologies will continue to exist, supported by the Windows communication foundation (e.g. enterprise services, .NET remoting, COM, COM+ and MSMQ).

Another tool in Microsoft’s integration arsenal is the SQL Server 2005 Service Broker, which will provide a SQL-to-SQL binary data messaging protocol, allowing developers who are familiar with the database programming model to think about queues as databases and to take data from queues as as a kind of hanging query/result sets. Over time, this will be adapted to use the Windows communication foundation so that this will run on top of the Service Broker protocol before eventually allowing the Windows communication foundation to become the transport for WS-* interoperability.

Web services integrationOf course, Microsoft’s most significant integration product for connected systems is BizTalk Server. At 1.5 million lines of C# code, BizTalk Server 2004 is one of the largest Microsoft .NET products written to date (although SQL Server 2005 will exceed this at around 3 million lines). BizTalk Server allows the mesh of point-to-point web service (and other) connections to be replaced with a BizTalk Server “hub”.

Microsoft BizTalk Server
Another advantage of such a process is the ability to take business processes out of (potentially unstable) code and allow BizTalk’s orchestration model to handle the business processes.

BizTalk 2004 is the first Microsoft.NET incarnation of the product (the previous two versions were not .NET applications). Built on the ASP.NET application stack and including WS-I v1.0 support (and a v2.0 adapter), BizTalk Server 2004 is integrated with Visual Studio.NET 2003 and the Office System 2003 with additional features including business activity monitoring, human workflow services and a business rules engine. BizTalk Server 2006 is due to follow the SQL Server 2005 and Visual Server 2005 launch in November 2005 and (according to Microsoft) will offer simplified setup, migration and deployment, comprehensive management and operations, and business user empowerment. An adapter for the Windows communication framework is also expected later in 2006. Future versions of BizTalk Server will be built natively on the Windows communication foundation and will offer support for the next version of Windows Server (codenamed Longhorn) as well as the dynamic systems initiative (DSI).

Ultimately, the Windows communication foundation will become a transport layer for connected systems, with BizTalk Server providing orchestration. With continued support for WS-* standards, truly connected systems may well become a reality for many organisations.

Links

WS-I overview presentation

10 steps to help secure SQL Server 2000

This content is 20 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 just stumbled across this 10-step plan to help secure SQL Server 2000 and thought it might be useful to note…

New tools for managing and administering SQL Server 2005

This content is 20 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 haven’t looked at structured query language (SQL) since I was at Uni’, back in the early 1990s, and don’t intended to start now; but with a major new SQL Server release due from Microsoft in November, I’ve been building up my knowledge of the product from an infrastructure perspective. Yesterday evening, I was at a Microsoft TechNet UK event, where Matthew Stephen (one of Microsoft UK’s IT Pro Evangelists) presented the tools for managing and administrating SQL Server 2005 (codenamed Yukon) along with a few of the new features for administrators.

At the centre of SQL Server 2005 administration is the new SQL Management Studio, which replaces SQL Enterprise Manager and uses a Visual Studio project metaphor, featuring a much improved user interface showing registered servers, an object explorer (with a tree view of the databases – similar to Enterprise Manager) and a summary pane. New features include:

  • An integrated SQLCMD mode, allowing SQLCMD queries to be run from within SQL management Studio (as long as they are preceded with !!).
  • Online database restoration and fast recovery, with only the data currently being overwritten being unavailable.
  • Online indexing (so that queries can still be performed whilst indexes are rebuilding).
  • Integration with Visual Studio 2005 and the Microsoft .NET Framework v2.0, allowing the use of user-defined functions, data types and procedures, using any common language runtime (CLR)-compliant language.
  • A dedicated connection for administrative access (allowing an administrator to connect to a server and diagnose problems even if access is generally being prevented by, for example, blocking).

In common with all new Microsoft products, SQL Server 2005 will be delivered “secure by default”, meaning that some configuration changes may be required in order to administer some legacy services. Now, when connecting to a server using the SQL Management Studio, the default connection method is using TCP/IP, and Windows authentication is the preferred authentication model.

The SQL Server Web Data Administrator is available today for administering SQL Server databases where no management tools are available. It runs on either Microsoft Internet Information Services (IIS) or the lightweight Cassini portable web server and allows either Windows or SQL-based authentication to connect to a server for management purposes, import and export (queries, stored procedures, etc.) and a T-SQL query editor. Because it is lightweight, the Web Data Administrator is ideal for use over slow network links.

SQL Server 2005 Express Edition replaces the Microsoft SQL Server 2000 Desktop Engine (MSDE) – Microsoft’s free (but functionally limited) version of SQL Server 2000. SQL Server Express 2005 is still limited, but the constraints are different to MSDE, now allowing use of a single CPU (although it can make use of multiple logical CPUs – i.e. with a multi-core CPU), 1Gb of RAM and a 4Gb database size, with no limit on the number of concurrent sessions, making it ideal as a database to support a web site.

The SQL Server Express Manager can be used to administer SQL Server Express or MSDE databases and is based on the Microsoft.NET Framework v2.0. With a tree view of database objects and wizards for common tasks, SQL Express Manager can be used to administer either local or remote databases and includes a T-SQL query editor.

SQLCMD uses the OLEDB interface and replaces ISQL (DB-Library) and OSQL (ODBC) tools (although OSQL still exists and SQLCMD parameters are backwards compatible with OSQL). Offering batch functionality (including command line variables and nested scripts) and script chaining, SQLCMD is a powerful command line tool for SQL Server administration and queries.

SQLiMail is a replacement for the former MAPI32-based SQLMail. Including its own SMTP client, SQLiMail makes use of the new SQL Broker provided with SQL Server 2005 and because it is no longer MAPI-based, has no reliance on Outlook. Multiple profiles can be attached to an SMTP account along with multiple host databases. SQLiMail also supports clusters and 64-bit SQL Server installations.

One of the new features of SQL Management Studio is the creation of maintenance plans (each one made up of sub-plans). The maintenance plan designer has a similar appearance to SQL Server Integration Services (SSIS) (a subject on which Jamie Thomson frequently blogs) featuring a drag and drop visual design workspace which allows tasks to be joined to build up a complex workflow. It is also possible to view the resulting T-SQL statements.

SQL Profiler also has a host of new features, not least the ability to grant trace access to developers (without requiring SA access). Also featuring a new selection user interface, SQL Profiler includes a host of new events (so that pretty much every activity can be audited), assisting with the compliance issues faced by many organisations today. SQL Service Broker activity can also be traced and traced can be redirected to an XML file for programmatic analysis. Working in real-time, SQL Profiler includes templates to assist in profiling and results can be filtered (e.g. by SQL Server internal process identifier). One particularly impressive feature (which Mat didn’t show last night but which I’ve seen him demonstrate before) is that ability to overlay SQL Profiler data on top of a performance monitor graph, allowing analysis of the effect of a SQL operation on server performance.

Finally, the features for monitoring SQL Server 2005 are enhanced with a new log file viewer (allowing SQL logs to be viewed in combination with Windows event logs), activity monitor (e.g. allowing locks to be viewed in real-time, by process, etc.) and an updated SQL Server Agent which can be used to set alerts, now with multiple proxies (so different logins can be used for different services) and new agent user roles.

Microsoft and SAP alliance site

This content is 20 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 don’t know anything about enterprise resource planning (ERP) products, except that SAP are a big player in this space (and that Microsoft runs its business on SAP with a 1.7Tb SQL Server database – pretty much the only non-Microsoft product in use there). Last night, Mat Stephen mentioned the Microsoft/SAP Alliance website and, after having taken a look this morning, the technology section (including details of how to integrate SAP and Microsoft products) looks pretty useful to me.

Windows Vista only a replacement for XP – Windows Server is still codenamed Longhorn

This content is 20 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 days back, I commented on Microsoft’s announcement of Windows Vista (formerly codenamed Longhorn), speculating as to whether this new name included the next generation Windows server product. It seems not, at least according to the Microsoft Windows Vista Beta 1 fact sheet.

I’m one of the 10,000 beta testers for Windows Vista (not a particularly exclusive club I know…) as well as Longhorn Server and Internet Explorer 7 so I guess I’ll blog some more about Vista after I’ve used it for a while – in the meantime Paul Thurrott has a Vista FAQ on his SuperSite for Windows.

Finally, I’m starting to understand the possible uses for a camera phone…

This content is 20 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.

For a few years now, it’s been becoming increasingly difficult to buy a mobile phone handset which was both stylish and a good phone without also getting a whole load of distractions (games, camera, etc.). Now, I have a smartphone (a Nokia 6600), which is connected to my private number and my work phone (a Nokia 6310i), which is just really good at doing one thing – making and receiving telephone calls (although it does also have infra-red, Bluetooth and GPRS connectivity, all of which are useful).

Throughout all of this, I’ve been skeptical about the need for mobile messaging services (MMS) – the idea that anyone (other than teenagers, who either have too much pocket money, or are running up huge bills for their parents to pay) would want to send low quality photos to one another from their mobile phone. Recently though, I’ve begun to change my mind…

I have a couple of blogs – this (technology focused) one and another for my geographically dispersed friends and family to keep up to date on what is happening in the Wilson family. Moblog pictureFor the last year or so, not much has happened in the Wilson family that hasn’t been focused around my son, so when we were on holiday a few months back I had a bit of dilemma – I didn’t want to take my main camera to the beach, but I did want to grab some photos of him experiencing sand and surf for the first time. That’s when the camera in my mobile came in useful. At 640×480 (VGA), the images are never going to be great for printing, but they are just fine for display at 72dpi on a computer screen.

Now it seems that mobile blogging (moblogs) have become a bit of a phenomenon. According to a Nokia moblog backgrounder:

“Blogs are one of the fastest growing phenomenon on the Internet with over 6.5 million web logs available and thousands more coming online every day. Blogs are like diaries which allow people to publish their thoughts and opinions or simply act as a record of their lives. Blogs can be accessed by friends, family or anyone on the web. The sharing of photos is currently one of the most important drivers for creating weblogs… Moblogging takes this phenomenon to the next level, allowing people to use their mobile phones to instantly publish their life experiences on the web. You can post pictures, video and text from your camera phone directly to the web instantly and then share your memories with family and friends.”

It’s this phenomenon (along with “traditional” digital cameras and a PC) that’s driving the incredible growth of sites like Flickr, Moblog and Phlog.

But it’s not just ordinary (pseudo-)geeks like me that are getting on the moblog bandwagon (actually, I’m not quite there yet, but might be soon…) – Sony Ericsson and American Photo Magazine teamed up with photographer Robert Clark for his Image America project. Admittedly that was as much for Sony Ericsson to promote their latest camera phone but there’s also an interesting article from a BBC reporter on his experiences as he reported back from his US Road Trip family holiday via a moblog using Flickr and Blogger.

If only moblogging had existed when I was travelling around Australia a few years back…

Grabbing screenshots using the Microsoft virtual machine remote control client

This content is 20 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 just discovered this and think it’s really useful…

I’m in the process of documenting a client’s server configuration, using a virtual machine with a VPN connection to the client’s network and then a remote desktop protocol (RDP) connection to their servers. Because the VPN is within a virtual machine, I’m constrained by the limitations of the Microsoft virtual machine remote control (VMRC) client and thought I could only take full screen screenshots, using VMRC’s Remote Control | Special Keys | Send Print Screen menu commands. What I found (completely by accident) is that if I use the mouse to send the print screen command, the whole screen is captured; however, if I use the keyboard (Alt+R | right cursor | down cursor | carriage return) it acts like an Alt+PrtSc, and only the contents of the active window are copied to the clipboard.

I’m not sure if this is true for all clients (I haven’t tested further), but my setup was:

  • Windows Server 2003 SP1 host.
  • Virtual Server 2005 (v1.1.465.0 SE).
  • Windows XP SP2 guest (with virtual machine additions 13.206 installed), VPNed into the client’s network using the Cisco Systems VPN client (v4.6.02.0011) and then RDPed into a Windows 2000 SP4 server (RDP client v5.1.2600.2180).

Configuring web proxy auto discovery for Internet Explorer clients

This content is 20 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.

Over the last few weeks, I’ve been looking at using web proxy auto discovery (WPAD) to let a client’s PCs automatically discover the location of their Microsoft ISA Server 2000 web proxy servers through the Internet Explorer client. Note that WPAD is used by web proxy clients and firewall clients use winsock proxy auto detection (WSPAD).

Microsoft knowledge base article 296591 gives background information on WPAD (for WSPAD see Microsoft knowledge base article 260210) but basically, what is involved is:

  • A properly configured web proxy client (i.e one which has automatically detect settings checked in the Internet Explorer LAN connection settings) queries the DHCP server for option 252, which identifies an HTTP address for a file called wpad.dat which is ISA Server’s dynamically generated proxy auto configuration (PAC) file.
  • If a DHCP server does not respond with option 252, the web proxy client attempts to access http://wpad.domainsuffix:80/wpad.dat (or http://wpad.domainsuffix:80/wspad.dat for the firewall client). To locate this URL, the remote client queries its configured DNS servers for wpad.domainsuffix – obviously issues with incorrectly configured domain suffixes will prevent automatic discovery from working. Microsoft knowledge base article 307502 also indicates that the WPAD address is case sensitive.

It should be noted that WPAD is not supported for clients that connect to the LAN with any type of dial-up connection.

To set up WPAD, three steps are involved, as detailed in Microsoft knowledge base article 309814 (Windows 2000) and Microsoft knowledge base article 816320 (Windows Server 2003):

  • The web proxy servers must publish automatic discovery information (which might require the web proxy service to be restarted).
  • DHCP (and optionally, DNS) needs to be configured to send the WPAD URL to the web proxy client (as detailed in Microsoft knowledge base article 252898).
  • Finally, the clients need to be set to automatically detect settings.
  • We planned to roll out WPAD on a site-by-site basis, using DHCP (adding a DNS entry would affect all clients) and everything looked good using DHCP alone (no DNS installed) in my test environment; however the existing route used for production clients to access the Internet is direct via the firewall, and so the clients failed to use the DHCP-assigned WPAD information as the direct path was working (that’s the theory – it is difficult to diagnose the DHCP traffic to that level of certainty, other than using a network monitor and examining packets).

    One possibility for the failure is described in Microsoft knowledge base article 312864 but I could not replicate this behaviour in testing and as it is only linked from the Windows Server 2003 version of the knowledge base article describing configuration of firewall and web proxy client auto discovery, I am not convinced that the article applies to clients using Windows 2000 DHCP servers.

    The current plan is to use a group policy object, filtered by group membership, to manipulate client proxy settings and use http://proxyarray.domainname.suffix/wpad.dat as an automatic configuration script. This has the advantage that we can control who can access the Internet (take a user out of the group to remove their proxy access – once the direct path has been removed), but does not use WPAD at all.

    One comment which my client made was that the wpad.dat file which ISA Server uses looks complex compared to the .PAC files used by the parent company’s web proxy servers. We could have used a simple .PAC file, but the major advantage of wpad.dat is that it is updated dynamically to reflect changes in the proxy server configuration.