71 replies to this topic

[GaMeR]

I used it to create the WHS X:\Files Edition. (And yes, I'm still working on it! - New version will be somewhere early next year!)

An example on how to do this with WHS disk Management:

[codebox]REG IMPORT "<path to your regfile>\WHSDiskManagement.reg"
msiexec /i "<path to your Add-Ins\WHSDiskManagement.msi" /quiet[/codebox]

I prefer to use D:\Shares\Software\Add-Ins\ when installing the add-ins. I simply copy the add-ins that are selected in the menu to that location first before installing.

A small example of my script:

[codebox]COPY "<path to Add-In>\\Install\\Add-Ins\\WHSDiskManagement.msi" "D:\\Shares\\Software\\Add-Ins" /Y'
REG IMPORT "<path to regfile>\\Install\\Add-Ins\\WHSDiskManagement.reg"
msiexec /i "D:\\Shares\\Software\\Add-Ins\\WHSDiskManagement.msi" /quiet[/codebox]

I have both the Add-In and regfile in the same directory for easy install. Basicly, this is it.

If you need some regfiles of add-ins then I'm happy to help you out. But it's more fun to do it yourself, use VirtualPC to install WHS and the add-ins you want to use, extract the regfiles and use them in your scripts.

[peter_h]

I used it to create the WHS X:\Files Edition. (And yes, I'm still working on it! - New version will be somewhere early next year!)

An example on how to do this with WHS disk Management:

REG IMPORT "<path to your regfile>\WHSDiskManagement.reg"msiexec /i "<path to your Add-Ins\WHSDiskManagement.msi" /quiet

I prefer to use D:\Shares\Software\Add-Ins\ when installing the add-ins. I simply copy the add-ins that are selected in the menu to that location first before installing.

A small example of my script:

COPY "<path to Add-In>\\Install\\Add-Ins\\WHSDiskManagement.msi" "D:\\Shares\\Software\\Add-Ins" /Y'REG IMPORT "<path to regfile>\\Install\\Add-Ins\\WHSDiskManagement.reg"msiexec /i "D:\\Shares\\Software\\Add-Ins\\WHSDiskManagement.msi" /quiet

I have both the Add-In and regfile in the same directory for easy install. Basicly, this is it.

If you need some regfiles of add-ins then I'm happy to help you out. But it's more fun to do it yourself, use VirtualPC to install WHS and the add-ins you want to use, extract the regfiles and use them in your scripts.

I see so you are actually running this after the OS has already been installed. That's a nice approach. By doing it this way, you can always keep it up to date and you don't need to build a new ISO when you need to update an addin or add a new one. Just dump it all on a thumb drive and install the script. Kind of like an all in one add-in.

I'll play with this if I get some time this weekend. I need to get virtual machines running first so I can tinker without breaking anything... again.

[GaMeR]

But the thing is, during installation, the shares are not set up. There isn't a choice. And a lot of the stuff we do for the x-files is during the install process, so it is easiest and the most reliable way for us to do it.

I've tried it a hundred times (I believe it's even more right now!), and no problems. It's like Drashna said, my installer works right after the normal installer. And I use some "special" runonce reg stuff when needed to be safe.

[Revenent]

Not sure if anybody realizes this, but if you don't have Vista, but can boot from the WHS DVD, you can partition the USB drive from inside the WHS Setup.

When you get to the point where it asks for additional storage drivers (in the UI portion), browse to the System32 directory and find "diskpart.exe". Right-click on it and click on Open.

That will give you a Vista diskpart where you can run all the commands to prep a USB drive.

That's what I had to do since I don't have any Vista machines at home.

[Richard Ainz]

Is there any way to slipstream PP2 onto an original PP1 dvd?

[Drashna Jaelre (WGS)]

Simple answer: no
Not so simple answer: the PP2 installer requires that the OOBE wizard to have already been run. You can't integrate the update like a normal update because the components get installed later and will overwrite the newer files.

[Jubal]

Kudos to you guys for this tutorial. I'd managed to follow this and get an Intel SS4200-EHW headless up and running inside a couple of hours from a usb stick. I needed the AHCI and SATA drivers in the boot.wim and all the drivers (chipset, sata, ahci, lan etc) in the slipstream. I was confused as to how to set the password having never seen that part of a WHS install before but it's a piece of cake if you let the WHS connector do its' job. Thanks again.

[welchwerks]

Hi, when you say add the dos file,to the folder in the beginning, what dos file?

Thank you

[Rychek]

Hi, when you say add the dos file,to the folder in the beginning, what dos file?

Thank you

I'm assuming you are refferring to the following from "Setting Things Up" with your question:

"2. Copy your DOS drivers folder into C:\WORK, and rename it to DOS."

All this means is take the driver you want to slipstream (the acutal driver files, not the .exe <you may have to extract them using WinRAR or 7zip>) and copy it to a folder named "DOS" in your C:\Work\ directory.

[welchwerks]

o.k. im getting warmer,
is this where i would put SP1, 2 and 3 also if this is true after extracing each of them, do i put them in folders inside the dos folder

[The Lynx Effect]

As far as I am aware, you can't slipstream the ServicePacks into the install, this is due to the way WHS is built and is not an operating system in it's own right.

Thanks

TLE

[Naveris]

I am following the instructions for Slipstream but did not get a Program Data folder in C:\WORK\WIM. I unmounted and remounted but achieved the same result. Is this an acceptable variation? If not, any idea what I may have done wrong?

Thanks

[BigBlack]

Hi
I assume the DOS files we are talking about are any additional drivers for hard drives that are not included in WHS. is that correct? Is it possible to include drivers for additional HD controllers like the RocketRaid 3520? I am currently using this to control additional hard drives on my system in JBOD mode not Raid.
I am about to rebuild my WHS as the system disk is failing. Will the slipstream allow me to include these drivers during the install?

Thanks
Jan

[Drashna Jaelre (WGS)]

The DOS drivers are the textmode drivers for Server 2003 or XP.

[BigBlack]

The DOS drivers are the textmode drivers for Server 2003 or XP.

Thanks Drashna. Sorry to sound stupid but what are textmode drivers?

Jan

[Drashna Jaelre (WGS)]

They are meant for the installation, not for installation inside of windows. IIRC