I am curious what people are doing with slipstreaming updates to Windows 7 and uploading them to a K2000 series appliance. What is the easiest, secure way to slipstream the *.msu files to Windows 7, so that I can upload the source media with all the updates? XP was pretty straight forward, but there are many message board opinions on 7.

From what I've seen, there are many approaches: Freeware (vlite, nlite, rt7lite, wuInstall); Some people are updating 7 on a clean install, sysprep-ing, then using the *.wim file from this installation; Some people are mounting an *.wim image to a machine with a non-identical objectID and using the WAIK deployment tools command prompt to slipstream drivers, but I don't see anyone using this method for adding *.msu files.

I would appreciate any recommendations or suggestions on this topic.

Thanks.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I have just done this using rt7lite.
Given the timeframe we had to work in i needed something quick. It's so far worked really well.
Answered 01/19/2011 by: CordlezToaster
Purple Belt

Please log in to comment
0
I resigned myself to only slipstreaming the service packs years ago. Constantly updating the media was too much work, so I use K1000 or WSUS between service packs to keep things up to date. If I were inclined to return to the method you seek though I think I like rt7lite or vlite at surface value. Also note the MS releases update packs in ISO format. Possibly useful: http://support.microsoft.com/kb/913086. Not recommending or endorsing anything- that's just my first thought.

Also looks like MSU's natively support command line options. Seems the most flexible and efficient manner might be to upload them as application tasks to the K2 and run the apropriate command line. Full listing of options:
wusa.exe /?
Answered 01/19/2011 by: cblake
Red Belt

Please log in to comment
0
Thanks to both for the input. Rt7Lite does seem to be the software of choice for slipstreaming, but I think I might try the recommendation of simple command line installs through a post-installation task. They are easy to manage in this interface, but once that list gets really long, it becomes more tedious.

Thanks again - very helpful.
Answered 01/20/2011 by: bowlesrice
Orange Belt

Please log in to comment
0
bowlesrice,

Try using WSUSOffline, http://www.wsusoffline.net/ as a post installation task. Won't get all the updates but lots of them.
Answered 01/20/2011 by: cserrins
Red Belt

Please log in to comment
0
From what I have read any of the current methods of slipstreaming SP1 into Win7 will cause SP2 to not install down the road and possibly corrupt the machine when the SP install is attempted. I am interested in adding this as a post installation task as well, but since it requires a reboot it would have to be my last task in the post-installation.

edit: spoke before I researched....

/unattend /norestart will do the trick.

edit: odd behavior when I attempted to install it that way. It stops the scripted installation process similar to a reboot and it changed the visual style to look like Server08.
Answered 01/27/2011 by: dyehardfan
Second Degree Blue Belt

Please log in to comment
0
http://www.wsusoffline.net/

Corey,

Question for you, once you have the ISO created from the wsusoffline utility is there a way to run that as a post installation task on a scripted install?

Caleb
Answered 12/08/2011 by: cjones34
Senior Yellow Belt

Please log in to comment
0
What i did was put the wsusoffiline files on petemp.

I would then copy them locally as a mid level task.
Answered 12/08/2011 by: dchristian
Red Belt

Please log in to comment
0
David,

So which files would I use from wsusoffline? the iso file? also I am not familiar with a mid level task could you point me in the direction of getting more info on that?

Caleb
Answered 12/08/2011 by: cjones34
Senior Yellow Belt

Please log in to comment
0
Sorry last post was from memory...

What i did was place the whole wsusoffile folder in the petemp folder but you could technically use any share.

From there i ran the update so all my updates where stored in the client folder of wsus.

Here's my sample command (it was a bat script).

net start wuauserv
net use z: /delete
net use z: \\vm-kdeploy\petemp
z:\wsusoffline\client\update.cmd
Answered 12/08/2011 by: dchristian
Red Belt

Please log in to comment
0
David,

Great thank you, I will try that. Sorry for being a little dense.

Caleb
Answered 12/08/2011 by: cjones34
Senior Yellow Belt

Please log in to comment
0
No worries, let us know if it works out for you.
Answered 12/08/2011 by: dchristian
Red Belt

Please log in to comment
0
David,

Keep in mind, petemp will be locked down in 3.4. So you want want to change the commands to copy everything over from petemp to your computer while in kbe, and then run update.cmd as a post.
Answered 12/09/2011 by: cserrins
Red Belt

Please log in to comment
0
Good to know!!!!
Answered 12/09/2011 by: dchristian
Red Belt

Please log in to comment
0
David,

I ran the wsusoffline on a computer, uploaded the whole folder from that computer to the kbox petemp folder and then added the bat script that you gave me changing it to point to my kbox but it is not installing the updates, it only maps to the kbox petemp folder, it does not run the update.cmd during install. I am on the right path and just missing something or did I misunderstand what this was suppose to do?

Thanks,

Caleb
Answered 12/12/2011 by: cjones34
Senior Yellow Belt

Please log in to comment
0
Can you try running the command manually?

Try mounting the petemp folder and running update.cmd from the command line.
Answered 12/12/2011 by: dchristian
Red Belt

Please log in to comment
0
cjones,

Note that after dchristian maps petemp, he has files in a directory named wsusoffline and then another directory named client. Make sure that is where your update.cmd is located.
Answered 12/12/2011 by: cserrins
Red Belt

Please log in to comment
0
ORIGINAL: cserrins

David,

Keep in mind, petemp will be locked down in 3.4. So you want want to change the commands to copy everything over from petemp to your computer while in kbe, and then run update.cmd as a post.


I know it's off topic but why is it locked down ?
(I'm using it for stuff like storing PC name if they would like a specific name then it start with a prompt that store it on the petemp while it format the disk and copy windows files)
Answered 12/15/2011 by: rmeyer
Second Degree Blue Belt

Please log in to comment
0
People had security concerns.

Keep in mind that if you are in KBE (our boot environment) you have already authenticated to petemp and therefore no credentials are needed, only if you try to map from a workstation not in the boot environment.
Answered 12/15/2011 by: cserrins
Red Belt

Please log in to comment
0
ah ok good to hear ;)
Answered 12/20/2011 by: rmeyer
Second Degree Blue Belt

Please log in to comment
0
So, all of that is over my head.

How do I either:

A) update my source media so that Windows deploys already relatively updated
B) Have a post-installation task that installs some packaged Windows updates during the scripted install
Answered 01/20/2012 by: larryw
Senior Yellow Belt

Please log in to comment
0
@larryw:
A) http://www.sevenforums.com/tutorials/145343-slipstream-windows-7-sp1-into-installation-dvd-iso-file.html
B) There are many solutions to this listed above.

Slipstreaming the most current service pack is a fine start, but then pick one of the multiple recommendations we've discussed to fill the gap.
Answered 01/20/2012 by: cblake
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity