Wir probieren seit ein par Tagen Empirum v14 aus und haben uns dabei an die Empirum_v14_Getting_Started_DE.pdf gehalten.
Leider sind wir auf ein par Probleme gestoßen:
1) Wir bekommen es bisher nicht hin das Spy Image bzw. EPE zum laufen zu bringen. Laut Anleitung müssen wir dafür ein PXE-BootImage erstellen und das zusammen mit einen SPY Template auf die Konfigurationsgruppe ziehen und aktivieren. Das ergebniss ist: der Rechner lädt EPE, startet aber neu nach der Meldung: "[getconfig] could not get any os.ini - aborting".
Wir haben dann auch gemäß Empirum_v14_Preinstallation_Environment_HowTo_DE ein debugging Image erstellt und sind die einlzenen Phasen durchgegangen, hier das log:
Code: Select all
[getconfig] could not get any os.ini - aborting
[getconfig] Copying latest OS.INI from
[getconfig] trying to get OS.INI for D6BE2400
[getconfig] trying to get OS.INI for BED6EA79
[getconfig] entering runlevel
[raidsetup] searching for softwareraids
[raidsetup] entering runlevel
[TimeOutThread] 25.03.2011 17:10.31 - Eis32 Time Out Thread: End!
[TimeOutThread] 25.03.2011 17:10.29 - Eis32 Time Out Thread: Start!
[logon] Connection to the Empirum-Server successfully established
[logon] mounting EMPINST$ and CONFIGURATOR$
[logon] entering runlevel
[buildpxecmd] the following options are passed to msgpxe: -m:0024BED6EA79 -h:matrix42.*.de
[buildpxecmd] creating PXE-Command
[buildpxecmd] the following options are passed to msgpxe: -m:0024BED6EA79 -h:matrix42.*.de
[buildpxecmd] creating PXE-Command
[sshd] ssh-daemon succsessfully set up
[sshd] starting ssh server
[sshd] generating ssh host keys finished
[sshd] generating ssh host keys
[sshd] entering runlevel
[networking] Get IP via gethostbyname and set as environment variable
[networking] You can connect to observe the Client's state by browsing to http://192.168.3.103
[networking] using it's HW-Address as 0024BED6EA79
[networking] primary interface is up and running
[networking] eth0 is selected as primary interface
[networking] Using DNS from bootimage configuration
[networking] client IP is 192.168.3.103
[networking] waiting for the interface to be configured
[networking] Linked interfaces: eth0
[networking] Carrier for eth0: Detected
[networking] eth0 is up
[networking] Checking for network device activations
[networking] Module: e1000e already loaded => skipping it!
[networking] Loading alternative module(s) for NICs into running kernel
[networking] entering runlevel
[epelog] Empty mount point. Logs are saved local as /tmp/
[mountusb] Could not mount any USB devices
[epelog] EPE will automatically continue with the detection in 10 seconds
[epelog] Optionally insert a USB device now. SPY and log will be copied
[modsetup] Storage Adapter: 0x00008086-0x0000282a-0xffffffff-0xffffffff
[modsetup] Network Adapter: 0x00008086-0x000010eb-0xffffffff-0xffffffff
[modsetup] installing Driver dm-mirror
[modsetup] installing Driver dm-zero
[modsetup] installing Driver dm-log
[modsetup] installing Driver dm-mod
[modsetup] installing Driver dm-round-robin
[modsetup] installing Driver raid456
[modsetup] installing Driver multipath
[modsetup] installing Driver dm-crypt
[modsetup] installing Driver dm-region-hash
[modsetup] installing Driver raid0
[modsetup] installing Driver raid1
[modsetup] installing Driver dm-multipath
[modsetup] installing Driver raid10
[modsetup] installing Driver dm-snapshot
[modsetup] installing Driver linear
[modsetup] installing Driver md-mod
[modsetup] loading raid and lvm
[modsetup] installing Driver kafs
[modsetup] installing Driver msdos
[modsetup] installing Driver jfs
[modsetup] installing Driver udf
[modsetup] installing Driver xfs
[modsetup] installing Driver cifs
[modsetup] installing Driver coda
[modsetup] installing Driver ntfs
[modsetup] installing Driver exportfs
[modsetup] installing Driver reiserfs
[modsetup] installing Driver isofs
[modsetup] installing Driver minix
[modsetup] installing Driver ncpfs
[modsetup] installing Driver smbfs
[modsetup] loading fs-support
[modsetup] loading inserting ide disk-driver
[modsetup] loading inserting scsi disk-driver
[modsetup] loading scsi low-level-drivers
[modsetup] installing SCSI-drivers
[modsetup] installing NIC-drivers
[modsetup] installing Installing IDE-drivers
[modsetup] installing Driver pcspkr
[modsetup] installing Driver sermouse
[modsetup] installing Driver input-polldev
[modsetup] installing Driver ff-memless
[modsetup] installing Driver newtonkbd
[modsetup] installing Driver sunkbd
[modsetup] installing Driver xtkbd
[modsetup] loading input device driver
[modsetup] loading edd support
[modsetup] removing usb_storage
[modsetup] preparing modules directory
[modsetup] entering runlevel
[seldest] runlevel is skipped due to debug mode
[getimage] runlevel is skipped due to debug mode
[getconfig] runlevel is skipped due to debug mode
[raidsetup] runlevel is skipped due to debug mode
[logon] runlevel is skipped due to debug mode
[buildpxecmd] runlevel is skipped due to debug mode
[network] runlevel is skipped due to debug mode
[modsetup] runlevel is skipped due to debug mode
[startx] browser executed successfully
[startx] Starting Browser
[startx] setting DISPLAY-variable
[httpd] httpd starting httpd
[httpd] setting environment-variable $DESKTOP_DEST
[httpd] htpassword successfully configured
[httpd] Configuring .htaccess
[startx] starting Tiny-X for framebuffer devices Xfbdev
[startx] entering runlevel
[lo] Loopback interface succsessfully set up
[lo] setting up loopback interface
[lo] entering runlevel
[boot] loading keymap DEU
[boot] loading usb modules
[boot] updating modules.conf
[boot] preparing modules
[boot] EPE-Debug-Mode enabled - all runlevels except of the terminal are skiped and might be executed by typing minit runlevelname on the command shell
[boot] CPU has 64Bit capability
[boot] checking if CPU has 64Bit capability
[boot] setting hostname
[boot] setting up modul-dependentcies
[syslog] starting syslogd
[syslog] starting klogd
[boot] network mode: dhcp
[boot] choosing network mode
[boot] making udev managing hotplug events
[boot] performing udev initial scan
[boot] mounting /sys
[boot] mounting /proc
[boot] msg_enter
[uncrypt] decryption completed successfully
[uncrypt] decrypting ...
[uncrypt] reading disk.ini
Ein weiteres Problem ist, dass in den PXE Logs gar nichts drin steht.
Das ganze passt zu den im
http://helpfiles.matrix42-web.de/v14_DE ... nt.htm#6.8 beschriebenen Problem, keiner der Lösungsansätze hat jedoch geholfen.
Geräte mit denen wir es bisher getestet haben waren: LenovoT400s, Vaio VPCZ1 und eine Hyper-V VM. DIe VM lädt beim Netzwerk boot nichtmal das EPE das selbe image als CD hingegen funktioniert.
2) Zwei von drei Testclients mit bereits installierten Windows lassen sich nach erfolgreichen Agent Push und Installation einiger Empirum Pakete nun gar nicht mehr über Empirum verwalten. Nach manueller Installation über den Kiosk wird dann aber der Status in der Management Konsolo korekt aktualisert.
Außer den Agent Push Logs werden keine Logs angezeig. Unabhängig davon, ob sie noch über die Konsole verwaltet werden können oder nicht.
Testclients sind bisher nur Hyper-V VMs: Windows 7 32bit, 64bit und ein 2008r2 64bit Server. Auf allen ist SP1 installiert.
Unsere Konfiguration: Empirum v14.0.2.3134, SQL 2008 r2 Express und PXE server sind alle auf einer 2008r2 64bit SP1 Hyper-V VM installiert. Das ganze läuft in einer AD Umgebung. Der Empirum Subdepot/Advanced Agent-Login Account ist ein Lokaler Administrator auf den Empirum Server.
Vielen Dank schonmal für eure Antworten.
Gruß Malte