sysprep and opsi
sysprep and opsi
Hi, I'm fairly new to Opsi. I am very impressed at how it is functioning for me so far. I have a question about a captured Sysprep image of a Windows 7 x64 build. Where should I place my .wim file on my Opsi-Depot server so I can apply it using Opsi. Is this possible. Thank you in advance.
- n.wenselowski
- Ex-uib-Team
- Beiträge: 3194
- Registriert: 04 Apr 2013, 12:15
Re: sysprep and opsi
Hi,
did you capture it using opsi tools?
Otherwise you probably want to replace the install.wim from the corresponding windows product. If you still want to roll out with that product you probably want to re-create the product with a new ID using opsi-package-manager.
-Niko
did you capture it using opsi tools?
Otherwise you probably want to replace the install.wim from the corresponding windows product. If you still want to roll out with that product you probably want to re-create the product with a new ID using opsi-package-manager.
-Niko
Code: Alles auswählen
import OPSI
Re: sysprep and opsi
Thank you for your response, sorry for the delay in my response.
No I did not capture with Opsi tools, Although I am going to try recreating with a new id with package manager as you suggested and see where that gets me. Thank you again.
Gary
No I did not capture with Opsi tools, Although I am going to try recreating with a new id with package manager as you suggested and see where that gets me. Thank you again.
Gary
- SisterOfMercy
- Beiträge: 1556
- Registriert: 22 Jun 2012, 19:18
Re: sysprep and opsi
You know you don't need a captured image, don't you? I was grateful to not have to put up with al that sysprep shite. 

Bitte schreiben Sie Deutsch, when I'm responding in the German-speaking part of the forum!
Re: sysprep and opsi
depends what you want to do.
i imply you want to use win7-x64
if you want this to be your one and only windows 7 base image, just replace the install.wim under with your own.
if you want this to be a seperate windows 7 image, run
it will ask for a new package name. f.e. win7-x64-[customname]
it will ask for a new version and package number - if you don't want to change those, also use -q it will just take the values in the control file and use those, an existing opsi-file will then be overwritten. as always, as always, if want to see what's happening, use -vvv - the more the merrier.
supply the required files to your new package on the depot
in case you also want to take over the already integrated drivers,
and again, last but not least, replace the install.wim under with your own.
this should be it.
i imply you want to use win7-x64
if you want this to be your one and only windows 7 base image, just replace the install.wim under
Code: Alles auswählen
[server-share]/opsi_depot_rw/win7-x64/installfiles
if you want this to be a seperate windows 7 image, run
Code: Alles auswählen
cd /home/opsiproducts
opsi-packagemanager -x /var/lib/opsi/repository/win7-x64_[currentversion/package].opsi --new-package-id
Code: Alles auswählen
cd win7-x64-[customname]
opsi-makeproductfile -h -m -z
Code: Alles auswählen
opsi-packagemanager -i win7-x64-[customname]_[version/package].opsi
Code: Alles auswählen
cd /var/lib/opsi/depot/win7-x64
cp ./custom ../win7-x64-[customname]/ -R
cp ./installfiles ../win7-x64-[customname]/ -R
cp ./winpe ../win7-x64-[customname]/ -R
Code: Alles auswählen
cp ./drivers ../win7-x64-[customname]/ -R
Code: Alles auswählen
[server-share]/opsi_depot_rw/win7-x64-[customname]/installfiles
this should be it.