Here is the full inventory report of the virtual (esxi) windows 8.1:

Host ID : 1
Host name : win8.1-ent-x64
Host MAC : 00:0c:29:…
Host Desc : Created by FOG Reg on June 18
Image ID : 2015
Image Name : 4:50 pm
Image Desc : 2
OS Name : win10-test
Inventory ID :
Inventory Desc :
Primary User : 1
Other Tag 1 :
Other Tag 2 :
System Manufacturer :
System Product :
System Version : VMware
System Serial : Inc.
System Type : VMware Virtual Platform
BIOS Version : None
BIOS Vendor : VMware-56 4d 9f 5a db d9 cb f7-52 1b 88 3e 3a 45 d3 7e
BIOS Date : Type: Other
MB Manufacturer : 6.00
MB Name : Phoenix Technologies LTD
MB Version : 07/30/2013
MB Serial : Intel Corporation
MB Asset : 440BX Desktop Reference Platform
CPU Manufacturer : None
CPU Version : None
CPU Speed : Not Specified
CPU Max Speed : GenuineIntel 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000
Memory : Intel Xeon CPU E5606 @ 2.13GHz Unknown Processor Unknown Processor Unknown Processor Unknown Processor Unknown Processor Unknown Processor Unknown Processor Unknown Processor Unknown Processor Unknown Processor Unknown Processor Unknown Process
HD Model : Current Speed: 2133 MHz
HD Firmware : Max Speed: 30000 MHz
HD Serial : 3.86 GB
Chassis Manufacturer :
Chassis Version :
Chassis Serial :
Chassis Asset : No Enclosure

The OS is Win 10 with Creators Update.
I had successfully deployed registry-snapins on Win-10-Creators-Update.

I’m not sure, but I think the only change was the Version of FOG Server / Client.
I think the last time I did a registry-snapin was with or before 1.4.0-RC-5.

I have exactly the same problem.
I always did registry-update-snapins successfully with snapin-packs in this way:

file fix.bat (example)

pushd %~dp0
REG IMPORT AutoAdminLogonDisable.reg

file AutoAdminLogonDisable.reg (example)

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"AutoAdminLogon"="0"

The snapins are successfully sent to the client and run. But the registry doesn’t change…

Version of Fog Server: 1.4.0-RC-9.2
Version of Fog Client: 0.11.12

Here is the full inventory report of the virtual (esxi) windows 8.1:

Host ID : 1
Host name : win8.1-ent-x64
Host MAC : 00:0c:29:…
Host Desc : Created by FOG Reg on June 18
Image ID : 2015
Image Name : 4:50 pm
Image Desc : 2
OS Name : win10-test
Inventory ID :
Inventory Desc :
Primary User : 1
Other Tag 1 :
Other Tag 2 :
System Manufacturer :
System Product :
System Version : VMware
System Serial : Inc.
System Type : VMware Virtual Platform
BIOS Version : None
BIOS Vendor : VMware-56 4d 9f 5a db d9 cb f7-52 1b 88 3e 3a 45 d3 7e
BIOS Date : Type: Other
MB Manufacturer : 6.00
MB Name : Phoenix Technologies LTD
MB Version : 07/30/2013
MB Serial : Intel Corporation
MB Asset : 440BX Desktop Reference Platform
CPU Manufacturer : None
CPU Version : None
CPU Speed : Not Specified
CPU Max Speed : GenuineIntel 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000
Memory : Intel Xeon CPU E5606 @ 2.13GHz Unknown Processor Unknown Processor Unknown Processor Unknown Processor Unknown Processor Unknown Processor Unknown Processor Unknown Processor Unknown Processor Unknown Processor Unknown Processor Unknown Process
HD Model : Current Speed: 2133 MHz
HD Firmware : Max Speed: 30000 MHz
HD Serial : 3.86 GB
Chassis Manufacturer :
Chassis Version :
Chassis Serial :
Chassis Asset : No Enclosure

No, with image a meant the windows-image.

But: HAAA! I found it!
On the SVN 3553 I always just tried some of the very new kernels (Fog-Configuration > Kernel-Update).
When I select an older one (I took 3.0.1), then it works!

Is there a reason, why the newer kernels (like 4.0.4) don’t support the VM-Images?
Can I help by giving you a list of the virtual hardware the esxi applied to the machine?

Thank to all the great work!

@Tom Hey Tom, thanks for replying!
But why can i handle the same (!) vm-image with fog 1.2.0 and not with svn 3553?

@Jbob
Yes, its windows 8.1.
But i don’t think, that it has to do something with the version of windows.

I want to add, that i also tried different kernels…

With fog 1.20 on debian 7 i was able to clone a virtual (esxi) windows (working with virutal ide- and scsi-drive).
Whe I’m trying to do so with svn 3553 on debian 8, i’m getting the following error, when trying to register the virtual host (full host registration and inventory):

Other (real) computers I can register with svn 3553 on debian 8.

Hi Tom,
i updatet the database before.
After debian-restart, i checked status of

• /etc/init.d/FOGMulticastManager
• /etc/init.d/FOGScheduler
• /etc/init.d/FOGImageReplicator

They are alle running!

BUT: now i’m getting error when trying to perform full host registration and inventory:

With SVN 3540 on Debian 8.1 I still have the following installation-error:

Starting FOG Multicast Management Server...Failed!

Greeds and Thanks!

Is there any new idea about fog on debian 8?
I think there are a lot of people out there that would like to run latest fog on latest debian…

Greeds and thanks for all the great work!