forum.opsi.org

Hello

What is the 100% proper way to update a Windows-image?
For example lets just say that Windows 7 x64 should be updated to contain Windows 7 x64 WITH SP1 (the would both be named "win7-x64" in OPSI).

Regards
Soren

I am talking about updating the installfiles.

Hi,

NT6 (Windows Vista and later) have no possibility for slipstreaming like Windows XP. Since NT6 the unattended Installation of Windows works internally with Images. You can manipulate this Images with dism. You have to search in the forum or in Internet, there are many ressources and tutorials. We have tried to integrate Service Pack 1 in the install.wim, but it have not worked.

You have three options:
1. You can download an install image from microsoft with integrated SP1 and change the install.wim in your installfiles in the depot-Share directly. (easiest way)
2. If you have our mshotfix subscription, there should be a opsi-Package for Install SP1 on Windows Systems with a localboot-Product.
3. You can try to build your own Service Pack 1 package for opsi.

NLite should be a option, but we have no experience with that.

If you use dism, you can extend your install.wim with some other stuff, like Hotfixes for Windows (Office Hotfixes is not possible). We use this to extend the WinPE with actual PE-Drivers. Have a look in opsi-getting-started manual.

Hope that is helpful for you.

bobzbobz hat geschrieben:Hello

What is the 100% proper way to update a Windows-image?
For example lets just say that Windows 7 x64 should be updated to contain Windows 7 x64 WITH SP1 (the would both be named "win7-x64" in OPSI).

Regards
Soren

Hi,

a nice Tool for downloading Windows Updates is this:
http://forums.mydigitallife.info/thread ... loader-5-2

after that you can integrate the updates with dism into your install.wim.
This is an tutorial how to use dism to integrate windows updates:
http://msdn.microsoft.com/en-us/library ... d.60).aspx

But I never tried to integrate a Service Pack, SP1 is already included in my install.wim

Hi again

I used "Windows Updates Downloader" and "RT 7 Lite" to create a new windows 7 install-image containing the newest updates and hotfixes.
Windows Updates Downloader
RT Se7en Lite

I then created a package called "win7-x64-slipstream" as a copy of the "win7-x64"-template: Side note: is this template up-to-date? I seem to be missing a few Product Properties after repackaging.

I then copied winpe, drivers and Unattended.xml from our current "win7-x64"-package to the newly created "win7-x64-slipstream".
Afterwards I installed a new client with the new image (+ mshotfixes) and it seemed to be faster.

Now I would like to update our "win7-x64"-package with the new win7-image, however I can see that the "win7-x64"-package has a version number of 4.0.3-8. How do i extract this current package for editing? or do i just copy/write the new installfiles directly to the "\\opsi\opsi_depot_rw"-share?

(I did unpack the template and repackaged the "win7-x64"-package, but am now missing the extra new product properties - is this a major problem?).

Regards,
Soren

bobzbobz hat geschrieben: I then created a package called "win7-x64-slipstream" as a copy of the "win7-x64"-template:

Code: Alles auswählen

opsi-package-manager --new-product-id win7-x64-slipstream -x /var/lib/opsi/repository/win7-x64_4.0.3-1.opsi

Side note: is this template up-to-date? I seem to be missing a few Product Properties after repackaging.

Uh, you should of course take the newest version that is available in your repository. But of course you can take the files of a newer win7-x64 package and put them in your modified package.
It's a bit of a mess on upgrading, but at least your modifications to the description don't get overwritten - or have I already said that?

bobzbobz hat geschrieben:Now I would like to update our "win7-x64"-package with the new win7-image, however I can see that the "win7-x64"-package has a version number of 4.0.3-8. How do i extract this current package for editing? or do i just copy/write the new installfiles directly to the "\\opsi\opsi_depot_rw"-share?

In my case it's \\opsi\opt_pcbin\install\win7-x64, and you do not need to edit that package in any way for normal functionality.
http://download.uib.de/opsi_stable/doc/ ... ckages-nt6
"Providing the Installation Files
Copy the complete installation DVD to
/opt/pcbin/install/win7/installfiles Adjust the file access rights by entering:
opsi-setup --set-rights /opt/pcbin/install/win7/installfiles"

But how have you gotten a win7-x64 package with that versionnumber? Is my opsi-product-updater broken?

The newest win7-x64-package/template in my repository is called win7-x64_4.0.3-2.opsi.

In my OPSI-configed the package-version of win7-x64 is/was "4.0.3-7".

I did unpack the template and edited the version-number to "8" and then repackaged as "win7-x64" - I probably shouldt have done it this way, as I am now missing a few Product Properties.
The next time I will just copy the installfiles directly to the "pcbin/install/win7-x64/installfiles".

Regards,
Soren