K2000 v3.3; Source Media; Windows 7 slipstreaming Microsoft Updates
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.
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
Answers (21)
Please log in to answer
Posted by:
CordlezToaster
13 years ago
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.
Given the timeframe we had to work in i needed something quick. It's so far worked really well.
Posted by:
cblake
13 years ago
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:
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 /?
Posted by:
bowlesrice
13 years ago
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.
Thanks again - very helpful.
Posted by:
cserrins
13 years ago
bowlesrice,
Try using WSUSOffline, http://www.wsusoffline.net/ as a post installation task. Won't get all the updates but lots of them.
Try using WSUSOffline, http://www.wsusoffline.net/ as a post installation task. Won't get all the updates but lots of them.
Posted by:
dyehardfan
13 years ago
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.
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.
Posted by:
cjones34
13 years ago
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
Posted by:
dchristian
13 years ago
What i did was put the wsusoffiline files on petemp.
I would then copy them locally as a mid level task.
I would then copy them locally as a mid level task.
Posted by:
cjones34
13 years ago
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
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
Posted by:
dchristian
13 years ago
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).
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
Posted by:
cjones34
13 years ago
David,
Great thank you, I will try that. Sorry for being a little dense.
Caleb
Great thank you, I will try that. Sorry for being a little dense.
Caleb
Posted by:
cserrins
13 years ago
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.
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.
Posted by:
cjones34
13 years ago
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
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
Posted by:
dchristian
13 years ago
Can you try running the command manually?
Try mounting the petemp folder and running update.cmd from the command line.
Try mounting the petemp folder and running update.cmd from the command line.
Posted by:
cserrins
13 years ago
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.
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.
Posted by:
rmeyer
13 years ago
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)
Posted by:
cserrins
13 years ago
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.
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.
Posted by:
larryw
12 years ago
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
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
Posted by:
cblake
12 years ago
@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.
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.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.