Microsoft has issued a warning that the newest version of its software for managing customer relations will not work with the company’s next Windows update. Also, Microsoft will finalize the code for Windows XP Service Pack 2 (SP2) sometime today, release it via Microsoft Download Center and MSDN on the Web tomorrow, and then ship it to customers via Windows Update beginning August 25, though Automatic Update users will get it immediately on a staggered basis.
Patch pre-empts Problem in Windows Update
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
If the thing is finalized today and going onto MSDN tomorrow why wait till August 25? I am assuming that this is the final version so why wait?
Probably because they need to recode it for the automatic update so when the updater checks our computer it will know if it needs it or not. Just a guess. That or they are hiding something. Ooooooo.
I was wondering if I should go ahead and update my machines tomorrow (I am in charge of an IT dept) or if I should wait. I do not know the benefits of waiting, unless we are guinea pigs if we downlaod it tomorrow
I would install it on a testing machine to make sure it plays nice with everything your department has/uses. Only until you are SURE that it won’t fubar a production machine you should just play with the testing machine, and check that it hasn’t done anything funky.
If not, you are sure to have to fix the same problem 1000’s of times, as opposed to learning a workaround once. At least, that has been my experience.
I was wondering if I should go ahead and update my machines tomorrow (I am in charge of an IT dept) or if I should wait.
It’s comments like that, on websites like this, that really make a powerful argument for outsourcing and automation…
I for one am looking forward to Windows XP Service Pack 2, and have been testing every build I could get my hands on for months, in order to work out any problems before hand…
Important lesson that I’m surprised you’ve not learned mini-me, being in charge of an IT department.
Never ever be an early adoptor of release tech from anyone on live systems. Ever. For anyone. Ever. And in case you missed it. EVER.
Get some test machines setup, identify people whose PC usage is less critical in conjunction with their managers and guinea pig them live.
Don’t go throwing a big update across the board because if that goes wrong who do you think will get the blame? Microsoft? Think again.
I was wondering if I should go ahead and update my machines tomorrow (I am in charge of an IT dept) or if I should wait.
——–
How about doing some testing on a few machines first? That is what smart IT people do.
I have been using Service pack RC2 on my work laptop, I am a sys admin for a company. I loaded it on my home pc and figured what better way to test it live than on my work laptop a few weeks later? Well from what I can tell it will “break” some apps at work that are web based due to stricter security settings, and pop up blocker, no big deal, I contact the local software companies that mades the apps and they keep saying they won’t work on an update until the offical release comes out.
I ask how long? They tell me a few months, what a bunch of b.s. RC1 and RC2 have been out for a long time now and it would be nice to just SP2 new boxes going out vs rolling out tons of patches.
Anyhow if you have to administer an Active Directory network also I have ran into slight problems with my 2000 domain controllers GPO editors not being able to interpret a file that adds comments to the GPO field or something like that, I went to Technet and was told to download some update but I have not been able to find that update.
best experience with a Service pack is always to integrate it into the files on the Windows XP CD – instructions at various places, google Slipstream XP service pack
This way you get all the latest file versions, latest drivers from initial install and no ability for system restore to break it !
If you’re really smart use an unattend.txt file on a floppy to automate the installation so you dont waste disk space on Windows Messenger, MSN Explorer or games
I am not talking about production machines.
I do not wish to waste my time installing this on a test machine. I’ve had other IT people where I work do this with the betas (pain in the rear end with all the bugs and glitches). I do not wish to be an MS beta tester. I check out updates from th windows update site on my testing gear first.
my question was along the lines of “is this different from what we will be getting on august 25th?” – if it is, I dont want to bother testing it.
I am going to push out SP2 via Group Policy, for new boxes I just plan on ghosting one image and using that one for all the desktops that come in new, but I am assuming soon enough the new Dell systems we get coming in will already have it next month *fingers crossed*.
“my question was along the lines of “is this different from what we will be getting on august 25th?” – if it is, I dont want to bother testing it.”
1. No what you get on the 25th is the same as you will be able to get tomorrow (albeit in a different package) i.e. the same binaries etc will be installed.
I suspect it’s been delayed again. It must be about noon in the USA by now (7pm UK) but no sign of it yet.
(I’d give good odds it’ll be released within an hour of my typing this ‘cos fate’s just like that)