Alexander Foken's questions

Environment:

• fresh Debian 10 Samba 4.9.5-Debian as AD-DC, using internal LDAP, internal DNS, RFC2307 enabled, libnss-winbind enabled and configured, libpam-winbind enabled and configured
• fresh Debian 10 Samba 4.9.5-Debian as Fileserver, joined to the AD-Domain, RFC2307 enabled, libnss-winbind enabled and configured, libpam-winbind enabled and configured
• Windows 7 and Windows 10 Clients
• Various Linux Servers will join the AD-Domain
• Microsoft RSAT Tools installed on Windows 7 for Management

AD-Users and AD-Groups simply work on Windows, both have NIS User/Group IDs assigned.

getent passwd on the fileserver shows all AD-users. getent group on the fileserver shows all AD-groups, but all AD-groups appear empty on Linux. Windows RSAT tools show group members as expected.

Output is somegroup:x:23456:.

Expected output is somegroup:x:23456:joe.user,tim.trouble,n.o.clue.

It seems I'm missing a little detail that needs to be configured.

I am trying to install Windows 7 on Proxmox Virtual Environment version 4.2-4/2660193c, running on Debian Jessie. I have followed the instructions on this site.

I uploaded a known-good Win7 ISO (that works fine with VirtualBox and real hardware) to Proxmox, and configured VM following the recommended best practices.

When the VM is started, Windows shows the gray text mode progress bar saying "Windows is loading files ...", then switches to "Starting Windows" and stays there for hours.

There is no visible action, no colored Windows logo, no animation, no disk I/O, no CPU load, no log output. No way to continue.

XP Home installed without any problems in a VM.

Host is Intel Core i5, VT enabled, 32 GByte RAM, 8 TByte SATA disks.

How do I get Win7 to continue its setup process on Proxmox 4.2?