F1 going back in time, Lotus and Brabham in 2010

Lotus49

The FIA’s cost cutting budget cap for F1 has spawned many different views and arguments, but the changes are certainly bringing some interesting news for the 2010 season.

One of the great things is that a few of the great names names from F1 history are returning.  So far we have Brabham and Team Lotus both with entries for next year.

As a bit of a Lotus geek, the Team Lotus entry is particularly interesting, for me at least.  Essentially the Litespeed F3 team posted an entry for the 2010 F1 season and have secured the Team Lotus name for their efforts.  At first that might sound a bit strange but Nino Judge and Steve Kenchington, the team principle and director and engineering are both ex-Team Lotus so hopefully the name is safe in their hands.  What’s more they’ve based the team in Norfolk which is Lotus’s traditional home.  With Mike Gascoyne on board they’ve got the makings of a pretty good team there.

The Brabham entry is a little less straight forward with the entry from Franz Hilmer using the Brabham name possibly being contested by the family of Jack Brabham

Now if only Tyrrell would turn up we’d almost have a full set!

Energy Efficiency in Windows 7

As you might have guessed from some of my other posts, I’ve been doing a fair amount of work recently on Windows 7.  One thing I’ve been doing a bit of reading about is power management and if/how Win7 can influence our energy efficiency. 

Like may organisations we’re actively looking at ways to reduce the energy we consume, both in terms of within the work we deliver (i.e. designing buildings for our customers that consume less energy), and also the energy we consume as a company in our day to day operations – of which IT plays a part.

Having dig into it a little, Windows 7 has some interesting capabilities that should help us achieve our green computing objectives by reducing the power consumed by our desktop and laptop computers.  There’s some detailed info available from Microsoft directly so I won’t talk about it too much, but a few points are worth talking about.

A big part of a computers overall power consumption is the energy it uses when idle – not least because most computers spend a fair chunck of their lives in that state.  If you can’t turn them off or put them to sleep when idle, you should at least try to optimise tham a little.  Win7 helps by reducing the system resources that are used when idle, and reducing or postponing background tasks until the computer is being actively used.  It achieves this partly though increasing the number of background services that are only started when needed, cutting the amount of work Windows asks the computer to do.

In addition to managing core CPU, memory and disk usage, Win7 is also more intelligent about how it manages devices that are attached.  Displays, network adapters and Bluetooth radios can be scaled back to reduce power consumption, and in the case of displays Win7 natively supports ambient lighting sensors to optimise the brightness of the screen.

A big advantage for organisations managing a large number of computers is Win7’s improved support for management and diagnostics.  Group Policy can be used to set power policies, and a WMI provider allows for better scripting support through PowerShell.  This will allow a much more consistent application of power saving features across organisations.

Of course Win7, whilst an improvement, isn’t a sliver bullet that will solve all your problems.  There’s still a place for third party tools such as 1E’s NightWatchman. 

NightWatchman is actually a pretty good product.  Not only does it help you to shutdown computers overnight whilst gracefully closing applications etc, the backend components will also help you track benefits across your organisation.  It’s worth a look if you’re looking at cutting power consumption, whether for green or financial reasons.

Further info:
–  MS Win7 Power Management White Paper
MS Win7 Power Management Webcast (it’s level 200 so not too techie)
–  1E NightWatchman

Best Practice Active Directory Schema Updates

It’s been a while since I had much to do with the techie side of looking after an AD, but a few bits of work we have on at the moment have had me thinking about AD and Schema updates in particular. 

It was quite a coincidence then that Jane Lewis over at MS posted up some good info on MSIT’s process for evaluating and implementing extensions to MS’s own AD Schema.

Whilst I’ve pasted some of the process below, its well worth heading over to Janes blog as she has some really good info over there.

I’ve added a few bit and pieces to the the high level process she describes below:

  1. Validate the justification for the Update – it is after all a one time procedure affecting the entire Forest.
  2. Fully define the type of change (Update, Modification, Depreciation)
  3. If the proposed change is a customized update from a third party, make sure that they provide a valid set of .LDIF files to analyze and that they have complete documentation
  4. Check whether base schema already has attributes or objects in it.  They may be affected by a change.
  5. Evaluate the risk of making the change
  6. Make sure that a Schema update is this the only way to effect your change
  7. Make sure you have a complete explanation of the update written and approved
  8. Define the list of roles and responsibilities for the Schema Update and make sure everyone knows what they are needed to do
  9. Stage the implementation of any Schema Change, test any change out in a non-production forest and thoroughly test it before implementing in a production environment.

Jane also provides a link to some docs and webcasts at MS that might be useful if you’re thinking about schema changes to your AD.