Problem installing Win7

[pav5088]

OK, I've discovered the logs tab, and I've already discovered why the Win7 product key is not being used. I guess for Windows 7 the extra licensing functionality must be used?

[3] [Jul 01 01:50:40] Failed to get license key from license management for host 'athlon64x2.strategicit.local', pool '', product 'win7', softwareid 'None': No license pool for product id 'win7' found (50_interface.conf|1763)

[pav5088]

The log (under the bootimage tab in opsi configuration editor) is much larger than the allowed limit. From the forum CMS :

Your message contains 474456 characters. The maximum number of allowed characters is 60000.

What should I be looking for? Should I email this to you?

[d.oertel]

Hi,

it should be possible to attach it as file - if not - mail it to info@uib.de

The use of the license management is not required.

regards

detlef oertel

[pav5088]

I noticed some name resolution problems in the logs. It's an interesting problem so I'll write about it here. It could effect people working in Microsoft server environments.

Symptoms : I could resolve a hostname, but not a hostname.domain.name eg. a ping would work for "host" but fail for "host.domain.name". When I used dnstracer, dig etc... they would show that my nameserver was working perfectly. Very strange!

The problem is related to using .local as a top level domain (ie. strategicit.local in my case). A .local TLD causes problems with the default settings Debian/Ubuntu/Suse use in nsswitch.conf . This is because nsswitch.conf uses mDNS/Avahi as part of name resolution. Because .local has a special meaning for Apples mDNS protocol different code paths get followed and name resolution fails.

# This shows my current nsswitch.conf hosts line with the default setting commented out because it fails with a .local TLD :
#hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
hosts: files dns

Because Microsoft recommends using .local as an internal TLD this could be a common problem.

Apparently there are other private TLDs reserved by RFC :

.test
.example
.invalid
.localhost

[pav5088]

I thought I would re-install opsi before trying to install Win7 again, and I had a problem purging opsiconfd :

Removing opsiconfd ...
Purging configuration files for opsiconfd ...

...The uninstall hangs here indefinately. Also while removing python-opsi :

dpkg: error processing python-opsi (--purge):
subprocess post-removal script returned error exit status 1

This is for 3.4 RC.

[pav5088]

OK, I tried uploading the bootimage log, but I can't see where it is.

Just in case I also uploaded this into a pastebin : http://pastebin.com/m7f06da7

[pav5088]

There is also an error message in the opsiconfd log. Note : I edited /etc/opsi/modules to include "license management = no" and I still get this error, and the mysql backend is not loaded in 21_mysql.conf .

opsiconfd log :

[4] [Jul 02 18:29:15] Client '192.168.1.139' did not send cookie (opsiconfd|261)
[4] [Jul 02 18:29:15] New session created (opsiconfd|951)
[4] [Jul 02 18:29:16] Authorization request from athlon64x2.strategicit.homelinux.net@192.168.1.139 (opsiconfd|354)
[4] [Jul 02 18:29:16] BackendManager created. (opsiconfd|391)
[3] [Jul 02 18:29:16] Failed to get license key from license management for host 'athlon64x2.strategicit.homelinux.net', pool '', product 'win7', softwareid 'None': Backend 'MySQL' not loaded! (50_interface.conf|1763)
[4] [Jul 02 18:29:21] Creating unix socket '/var/run/opsipxeconfd.socket' (OpsiPXEConfd.py|181)
[1] [Jul 02 18:29:28] Traceback (most recent call last):
File "/usr/lib/python2.5/threading.py", line 446, in run
self.__target(*self.__args, **self.__kwargs)
File "/usr/lib/python2.5/site-packages/twisted/python/threadpool.py", line 161, in _worker
context.call(ctx, function, *args, **kwargs)
File "/usr/lib/python2.5/site-packages/twisted/python/context.py", line 59, in callWithContext
return self.currentContext().callWithContext(ctx, func, *args, **kw)
File "/usr/lib/python2.5/site-packages/twisted/python/context.py", line 37, in callWithContext
return func(*args,**kw)
--- <exception caught here> ---
File "/usr/lib/python2.5/site-packages/twisted/internet/threads.py", line 24, in _putResultInDeferred
result = f(*args, **kwargs)
File "/usr/sbin/opsiconfd", line 528, in _realRpc
self.result['result'] = eval( "bm.%s(%s)" % (method, str(params)[1:-1]) )
File "<string>", line 1, in <module>

File "/etc/opsi/backendManager.d/50_interface.conf", line 1204, in setProductInstallationStatus
licensePoolId = self.getLicensePoolId(productId = productId)
File "/etc/opsi/backendManager.d/50_interface.conf", line 1728, in getLicensePoolId
return self._execMethod(self.licenseBackend, 'getLicensePoolId', productId, windowsSoftwareId)
File "/var/lib/python-support/python2.5/OPSI/Backend/BackendManager.py", line 496, in _execMethod
raise Exception("Backend '%s' not loaded!" % be)
exceptions.Exception: Backend 'MySQL' not loaded!
(opsiconfd|620)
[2] [Jul 02 18:29:28] Failed to process rpc: Backend 'MySQL' not loaded! (opsiconfd|624)
[4] [Jul 02 18:29:29] Creating unix socket '/var/run/opsipxeconfd.socket' (OpsiPXEConfd.py|181)
[4] [Jul 02 18:44:52] Client '192.168.1.139' did not send cookie (opsiconfd|261)
[4] [Jul 02 18:44:52] New session created (opsiconfd|951)
[4] [Jul 02 18:44:52] Authorization request from athlon64x2.strategicit.homelinux.net@192.168.1.139 (opsiconfd|354)
[4] [Jul 02 18:44:52] BackendManager created. (opsiconfd|391)
[4] [Jul 02 18:44:53] Creating unix socket '/var/run/opsipxeconfd.socket' (OpsiPXEConfd.py|181)

[d.oertel]

Hi,

according to : http://pastebin.com/m7f06da7
your Win7 productkey is loaded by the bootimage and should be correctly patched to the unattend.xml.

The other log you posted looks like you are going to use the mysql-backend.
- Is the mysql-server installed and the database initialized according to chapter
9.3.2. Initializing the MySQL-Backend
in http://download.uib.de/opsi3.3.1/doku/o ... 331-en.pdf
(The english opsi 3.4 manuals will be released soon.....)

regards

detlef oertel

[wolfbardo]

Just uploaded win7-x64_3.3.1-2.opsi cause you started the thread with Win7-x64.

Only difference between win7-x64_3.3.1-2.opsi and win7_3.3.1-2.opsi is the unattend.xml

regards

Bardo Wolf

[pav5088]

Thankyou very much... it now works, or at least gets further (my latest installation is still continuing). I'm curious as to what's different in the unattend.txt files. I never thought to look at how the Vista and Vista64 unattend.txt were different. Perhaps that would have given me a clue.