Support for SP2 XP to end 13 Jul 2010

[speckytecky]

Firms consider options as Windows XP support deadline nears - V3.co.uk - formerly vnunet.com An interesting article highlighting support for XP SP2 OS machines is to end shortly. From what I have seen visiting some schools it's possible that many are are vulnerable as the bought in support they have paid for has not applied SP3 - yet!

[Michael]

The interesting aspect is what company would leave this kind of decision to the last few days until XP SP2 is retired? XP SP3 operates exactly the same as XP SP2, with the exception of a few drivers I've not been forced to upgrade any application.

[sandeep2504]

we're still using SP2 here.

 

plan is to upgrade over the summer our cc3 network.

 

our vanilla network upgrade is still up in the air.

 

down to various reasons; workload and lack of planning mainly.

 

I've made points to my network manager; not much further I can do.

[elsiegee40]

Likewise, the SP3 upgrade happens during the summer... for various reasons

[Hightower]

Due to SP3 just recently being released for CC3 we are still SP2 here. We were going to do it last half-term holidays but the shared tech said he had encountered problems on his primary networks so we put it on hold until Summer. On the to do list for summer.

 

It's good having a shared tech who tests things on his smaller networks before we make the changes to our bigger network.

[BatchFile]

Anything that hasn't been reinmaged recently will be done over the summer too, I've got the GPO ready to do it on startup - could set it loose next week - but a few people may moan if it takes their pc half an hour to boot

[PiqueABoo]

Due to SP3 just recently being released for CC3 we are still SP2 here.

 

 

Well it was released late Feb/early March IIRC, but I don't think "we" really had the measure of it in terms of emerging glitches and gotchas on CC3 until after Easter..

[Gatt]

I still have a few XP Machines here, but they are SP3, I would love to get rid of them but unfortunately we cannot...

This causes a hell of a nightmare as I need to create a seperate image for them...

[Jamo]

We are currently rolling out SP3 on our CC3 network here. I must say RM's way of packaging SP3 instead of the option of slipstreaming into the build area mystifies me, the increase in build time is astronomical on some of the slower machines.

[Michael]

@Jamo - I agree it's much better to start with a new image. Deploying a 300MB+ patch over a network just doesn't work well in practice. CC3 doesn't utilise Microsoft's intelligent 'BITS' technology which has been around since Windows 2000. Instead the 300MB patch will be pushed out as one huge file transfer in RM CC3. Not really that intelligent...

[Jamo]

Yeah its brilliant. Our slower machines (admittedly appauling machines 256 ram etc) are in the order of 3 hours for the upgrade lol

 

Its around 15 mins for the faster ones.

[speckytecky]

Crumbs - seeing many of the replies here I didn't realise that it wasn't standard practice to apply SP3 ASAP as after all it is applying many critical and necessary security patches.

 

SP3 has been out a fair old while now and I just assumed that every XP machine would be having it and the other critical updates that follow it.

[Jamo]

Crumbs - seeing many of the replies here I didn't realise that it wasn't standard practice to apply SP3 ASAP as after all it is applying many critical and necessary security patches.

 

SP3 has been out a fair old while now and I just assumed that every XP machine would be having it and the other critical updates that follow it.

 

Im guessing your network isn't RM? lol

[PiqueABoo]

Microsoft's intelligent 'BITS' technology

 

You either do:

 

1) High bandwidth + low quantity

2) Low/adaptive bandwidth + high quantity (e.g. BITS)

 

I've broken both by pushing the numbers. Copy as fast as you can (to a not too big subset of machines) and install at start-up does have some virtues. The trouble with BITS is what you do next i.e. when do you install? In the background can be a really bad idea in a few cases.

 

[i think it should have been both slipstreamed and available as a package in CC3]