Jump to content

Recommended Posts

Posted

SP3 oddity.

 

I have a server that we use to build old workstations (non PXE), this had a copy of a basic XP SP2 CD on it. I've just applied SP3 for a play and the image increased in size by approx 180Mb. When i applied SP3 to the WDS server (again to a flat SP2 image) it only increased by 30Mb.

 

As both images were at a similar patch level i'm wondering why the images ended up so different in size. Could it be to do with the groveler service on the WDS?

 

Anyone got a scooby?

 

Cheers.

Posted (edited)

XP SP3 is broken on some of our HP AMD based desktop PCs. This is because HP ship these machines with the Intel 'intelppm' driver (I'm sure anyone who's built images remembers the stop code 0x0000007E error this results in) :)

 

Fix is to run the following command in safe mode:

sc config intelppm start=disabled

Then optionally shout at HP for doing a stupid on their base image.

Edited by Geoff
Posted

Hi

 

I have just install sp3 from the service pack and not from the widnows update site on a ghosted machine and it does not upgrade ie 7. Also when you run windows updates after the sp3 ie 7 does not appear on the updates list very strange.

 

After a bit of messing I have found you need to install ie 7 before sp3.

 

Richard

Posted

@ricki - XP SP3 installs an updated/patched version of IE6 from new. You have to install IE7 afterwards.

 

However if you had XP SP2 with IE7 already installed, XP SP3 will leave IE7 installed. The only change here is that you can no longer uninstall IE7.

Posted

Wow, I'm having a really wierd issue with XP SP3. Most machines went alright. But I just formatted a new machine here I'm building for a client on the side, installed windows, all new components. I connected to the internet, ran Windows Update and installed drivers as I usually do, however this is doing something I've never seen a fresh install of windows do on boot. EVERY TIME Windows boots up, it gives me a security warning of if I want to load each driver. EVERY TIME. Even if I uncheck "always ask before opening this file". Anyone else come across this yet? Just to see if it was a fluke, I reinstalled 3 times. I'm on my third try. Each time doing drivers, windows update, and office 2003 install in different order.

 

http://i198.photobucket.com/albums/aa188/link4scott/sc1.jpg

 

http://i198.photobucket.com/albums/aa188/link4scott/sc2.jpg

 

It's really really annoying. I swear I've seen something like it befor...

 

Oh...Oh wait...

Posted (edited)
I have just install sp3 from the service pack and not from the widnows update site on a ghosted machine and it does not upgrade ie 7. Also when you run windows updates after the sp3 ie 7 does not appear on the updates list very strange.

 

After a bit of messing I have found you need to install ie 7 before sp3.

 

I've not had this issue when i build an SP3 box it has a fully patched IE6 (SP3 doesn't include 7) and then it pulls IE7 off the WSUS server straight away.

 

 

@ Geoff: apparently if you download the full 500> ISO file you don't get the AMD problem it seems MS have missed a patch of some sort out of the 316 Mb version. It' still HP's fault for producing poor images for their desktops but MS have slipped up somewhere as well.

Edited by cookie_monster
Posted
Wow, I'm having a really wierd issue with XP SP3. Most machines went alright. But I just formatted a new machine here I'm building for a client on the side, installed windows, all new components. I connected to the internet, ran Windows Update and installed drivers as I usually do, however this is doing something I've never seen a fresh install of windows do on boot. EVERY TIME Windows boots up, it gives me a security warning of if I want to load each driver. EVERY TIME. Even if I uncheck "always ask before opening this file". Anyone else come across this yet? Just to see if it was a fluke, I reinstalled 3 times. I'm on my third try. Each time doing drivers, windows update, and office 2003 install in different order.

 

http://i198.photobucket.com/albums/aa188/link4scott/sc1.jpg

 

http://i198.photobucket.com/albums/aa188/link4scott/sc2.jpg

 

It's really really annoying. I swear I've seen something like it befor...

 

Oh...Oh wait...

 

Nothing to do with installing drivers - thats just a warning about opening an unknown .exe file. Unchecking "always ask before opening this file" wont make much of a difference if you are only opening it the once anyway.

 

I think its a feature of IE7 rather than sp3?

 

In Internet Explorer, click tools - Options

Under security settings, select "Intranet zone"

Click the "Sites" button, Uncheck the box that says "Automatically detect intranet network".

Checked the "Include all network paths (UNCs).

Click OK

  • Thanks 3
Posted

Those files are useless as well, one of them is the realtek sound bloatware driver, its not needed as XP has its own control panel for volume.

 

You can disable it by going to regedit and removing it from the run section of the registry. I do this on all new pcs to make them start up quicker.

Posted

Another slight annoyance.

 

With SP2 if i built a fresh box it downloaded all the patches (about 70) including IE7 and Office updates. Now with SP3 it builds then connects to the WSUS and downloads IE7 and that's it, it doesn't matter how long i leave it. Once IE7 has been added it reboots and then downloads all of the Office patches and installs them. This is a bit annoying as it can take to passes of scheduled installs to get upto date.

  • Thanks 1
Posted (edited)
Nothing to do with installing drivers - thats just a warning about opening an unknown .exe file. Unchecking "always ask before opening this file" wont make much of a difference if you are only opening it the once anyway.

 

I think its a feature of IE7 rather than sp3?

 

In Internet Explorer, click tools - Options

Under security settings, select "Intranet zone"

Click the "Sites" button, Uncheck the box that says "Automatically detect intranet network".

Checked the "Include all network paths (UNCs).

Click OK

 

Thanks for your reply! I tried that, and unfortunately the popups are still coming up on every boot. Any other suggestions? I also was suspicious it was IE's doing.

 

EDIT

 

Instead of just unchecking Include all network paths (UNC), I unchecked all 3. Still no difference.

Edited by link470
Posted

This might affect some people. (myself included).

 

Microsoft slams OEMs over XP SP3 install cock-up | Channel Register

 

“Microsoft is aware of a reboot issue experienced by some users who have attempted to install Windows XP SP3,” said a Microsoft spokesman. “While the root cause of this issue is complex, it results from OEMs improperly placing a Windows XP image created for an Intel-based computer onto machines with non-Intel chipsets. Microsoft issued guidance to OEMs advising them to only load Windows XP images onto like hardware in 2004.”

 

Indeed, the software giant also updated a knowledge base document (888372) on the same day it spat out the final XP service pack on 6 May.

 

It points out that the Intel processor driver (Intelppm.sys) may try to load on non-Intel-based PCs because of an errant registry key left over from the original Sysprep image that was intended for Intel machines only

Posted
It is lazy on HP's part in my opinion. Funny how no other big OEM has the same problem. In saying that though, you would expect Windows would use the correct file if it detects an AMD or Intel CPU. Maybe it's just too easy on Microsoft's part?
Posted (edited)
There must of been a slip up somewhere as the ISO version detects the issue so there must be something missing in the downloaded version that causes it to add the wrong components. Edited by cookie_monster
Posted

Out of interest, how are people planning on deploying this?

So far I've installed it in one suite and plan to leave it a while to bed in and make sure we have no major issues with it that didn't crop up in our earlier testing.

 

I'm thinking of manually installing it in the main suites (5 rooms) and then using our existing WSUS server to pick up all the other classrooms (One PC per room) and offices.

Having never done a full on SP over WSUS before, I'm somewhat wary of it as it's a pretty big update and their is many things that could cause the install to fail or go wrong (i.e people ignoring the "Do not switch off your PC" prompt or in the case of it installing in the background, a PC crashing or erroring for whatever reason) I've seen the results of a borked SP before and it's not pretty.

 

As for our laptop trolley's, I suppose they will have to be done by hand as if I recall, installing a service pack requires laptops to be plugged in rather than battery power, although I'd be extremely wary of doing it via battery and over wireless anyway.

 

It's been so long since the last Windows client SP so I'm a little rusty on this :p, when SP2 came out we only had 90/100 PC's mainly based around suites so it wasn't a real problem, now having nearly 500 all other the place, it gets a bit tricky....

Posted

currently putting it on all new machines as they arrive and any old ones that need rebuilt.

 

Sent it out via wsus to a test group of about 10 desktops and laptops.

 

Wont do the main computer suites until the summer, Ill just send it out via wsus and let them autoupdate.

 

Will probably do admin one at a time over the summer manually too. Theres only about 10 computers down there anyway.

Posted
I hadn't checked the service pack box so thats why mine hadn't come through! However think I might one manually on the oldest machine before I tick that box.
Posted
I've updated a WDS image and will be deploying it to new builds only for now, i'll think about deploying it down the road. As it's mainly a collection of hotfixes and no massive updates like IE6 for SP2 i'm not in a rush.
  • 4 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...