Service Pack Integration

[zippy]

It's a no-brainer!

 

NeoWin AutoStreamer

 

For W2k SP3+, XP and W2K3.

 

Anyone know of an easier way?

 

[tarquel]

http://unattended.msfn.org/

 

 

...but it all depends how you are gonna use the source remember

 

Nath

[zippy]

Hmm... Gaah... my brain hurts. You're outta scope wid dat.

Got a better no-brainer?

[Dos_Box]

La, la, la...

 

http://flexbeta.net/slipstreamerxp/

 

La, la, la

 

This one is better (IMHO) than Autopatcher, and I've used both. Slipstream creates an ISO file too, which means you also get a bootable service packed CD. It only does Windows XP and Office though.

[zippy]

Het Dos_Box, you lost da plot or what?

AutoStreamer is AutoPatcher's 'Little Brother'.

It makes your ISO file.

It grooves with anything from w2k sp3+ onward.

It's a no-brainer.

WTF?

[ajbritton]

There's always NLite...

[Sirbendy]

I use Nlite...

[tarquel]

*spits* nlite hehe...

 

ive seen sooo many ppl on the msfn forum moan about how something in windows isnt working and its turned out that they've removed the service or something that is a component of whatever their problem was.

 

Then again, thats your general public for ya hehe...

 

I missed out xpcreate [ http://xpcreate.com ] and i can help out a load here with this as its the only one i've used for years - the guy is busy nowadays but the thing works great and can provide ya with a fully up-to-date slipstreamed [and unattended if thats ya poison hehe] CD of XP

 

...or 2k - although I havent tried the 2k one myself and it isnt so forgiving, but theres a guy on the forum that uses 2k primarily so he'd probably know hehe

 

Just my 2p as per usual

[ChrisH]

What would you say was the best one to use if you were planning to use the source for RIS? or are they all the same?

[tarquel]

I cant say for nlite - although with that one yu can remove components from the XP source cd, etc..but im not sure how good that is with a RIS source [not having used RIS either yet hehe] - but i do believe that xpcreate does a good job of safely slipstreaming the hotfixes and updates into a nice final ISO

 

I find it best to slipstream the SP manually, although xpcreate can do it too.

 

I use it for floorless installs of XP and its never caused a problem yet, so i cant see it not being any good for a RIS too

 

You can try at least hehe

 

Give me a shout on MSN if ya want a guide Some of my custom apps are handy for this too - Dotnet being one of them as it doesnt recognise the update properly if you use unedited methods...etc..

 

Cheers

Nath

[ChrisH]

I have been playing with this and now have a RIS source that has all updates from last month so when I go to windows update there are no critical patches I got all my information from the MSFN Forums .

I used a combination of

NLite: Which cut my installation source by half by stripping out extra languages and rubbish like that.

Ryan VM Integrator: To integrate all patches.

Bashrats Driver Packs: A good selection of all the drivers you will probably ever need. It doesnt use the usual OEMPnpDrivers method either.

 

You cant just use these tools on a ris image as certain stuff has to be compressed etc so look at these scripts

AutoRis

and

Risult

 

I had better luck with AutoRIS although I had to move some stuff manually as it only copied the i386 folder back and not the $oem$ and it also did not put another folder for the driver packs in the $oem$/$1 like it should have.

Risult seems like it should do everything well but I had trouble when I tried it, but will try again as I have learnt a few things since then.

 

I shall try and Wikify this at some point

[Michael]

I personally do it the official way when it comes to slipstreaming - not only Windows but Office too.

 

As for patching Windows 2000 or above, every administrator should have WSUS installed on their server. It's very efficient and it's one less worry on my mind being able to see what update(s) are applied to workstations irrelevant if it's switched on or not 8)

[ChrisH]

We have WSUS installed but as you know it takes more than one reboot to install all the patches and a while to detect without forcing sometimes. Using this method the computer is upto date as soon as windows setup has finished. Well upto date now but wont be in another month but at least the majority of patches will be done

[Michael]

I agree sometimes a reboot is required to install updates, but that's more to do with Windows 2000/XP's design rather than WSUS. Windows Vista is supposed to improve on this, so less reboots should be required when installing updates or of course application software.