forum.opsi.org

Strange after your command the package is downloaded but on install the same error

I use 64bit windows do i need to change the command?

Can you repeat the command but with more verbosity? Replace -v with -vvv and copy the output here.

Looks like its up to date. Here is the last output.

Testing if download/installation of package 'win10_4.1.0.0-16.opsi' is needed Product 'win10' is installed Available product version is '4.1.0.0-16', installed product version is '4.1.0.0-16' Unfulfilled condition: Version(product=u'4.1.0.0', package=u'16') > Version(product=u'4.1.0.0', package=u'16') win10_4.1.0.0-16.opsi - installation not required: installed version '4.1.0.0-16' of product 'win10' is up to date Testing if download/installation of package 'win10-x64_4.1.0.0-16.opsi' is needed Product 'win10-x64' is installed Available product version is '4.1.0.0-16', installed product version is '4.1.0.0-16' Unfulfilled condition: Version(product=u'4.1.0.0', package=u'16') > Version(product=u'4.1.0.0', package=u'16') win10-x64_4.1.0.0-16.opsi - installation not required: installed version '4.1.0.0-16' of product 'win10-x64' is up to date No new packages downloaded Calling backend_exit() on backend <BackendExtender()> Calling backend_exit() on backend <HostControlBackend(resolveHostAddress=True, maxConnections=50)> Calling backend_exit() on backend <DepotserverBackend()> Calling backend_exit() on backend <ExtendedConfigDataBackend(configDataBackend=<BackendDispatcher(dispatchConfigFile=u'/etc/opsi/backendManager/dispatch.conf', context=<BackendManager()>)>)> Calling backend_exit() on backend <BackendDispatcher(dispatchConfigFile=u'/etc/opsi/backendManager/dispatch.conf', context=<BackendManager()>)>

Hi
i reuploaded the current experimental win10 and win10-x64 packages to experimental

If you still have the error related to the unattend.xml, please check if the template and the used unattend.xml are the same. IOf not you need to remove the specific line from your modified unattend.xml

cheers
mathias

No we have an other error wright at the start

Name isWifi is not defined

Hi,

you need an updated opsi-linux-bootimage for this to work aswell.

the bootimage is now available in stable and should avoid these issues

Regards
Mathias

Hi indeed i yust updated my opsi boot image however i still have the first issue

windows could not apply unattend settings during pass [specialise]

Am i the only one with this problem?

Do you use a modified unattend.xml in your Installation? If so, then you have to adapt the changes we made to male your modified unattend.xml to work