@butch2861 said in Windows 1809 Ent. Error after Upload to FOG:

@Sebastian-Roth After you run sysprep on a pc and upload the Image to the Fog Server the next thing that happens is the pc reboots and then the Fog Server loads the image just uploaded BACK to the pc you uploaded it from; almost like testing the uploaded image to the pc it came from as a test that it works.

Hi there 🙂

I was wondering, does the pc with the “golden” image restart and install correctly if you dont capture and deploy it?

Cause if it doesn’t that might mean that FOG is not involved in the problem at all - the error message I have had as well at some points, not sure what caused them then.

@Jim-Holcomb Yes, you’re on working-1.6 and I’ll be helping with that here shortly.

I find the service that wasn’t lauched. “service de la passerelle de la couche application”
Fog Service is ok and computer joined domain

Thanks

Here are dependency
fog service.PNG fog service2.PNG
3043296f-e3a2-439d-8198-92ad5cae185b-image.png
5e4a3899-aa40-4c67-a1c8-b4719653fd6e-image.png

@butch2861 As the Church Lady once said, “Well isn’t that special…”

Now that we know its a hardware class specific error. I wonder if this hardware is having a problem with the 64 bit kernel. We have seen some specialty hardware that has a 64bit CPU but externally its 32bit. I’m not saying this is specialty hardware, it could be similar in function.

I wonder what the results would be if you went into the host definition (You may have to manually register it if the kernel is panicing) set the kernel to bzImage_32 and the inits to init_32.xz This will force FOG to send the 32bit kernels to the client no matter what it reports to iPXE.

From your other screen shot I see 2011. Is the firmware the latest version available for this hardware. Lenovo has been known to have flaky early release firmware.

A reinstall helped correct the problem with the password.

@butch2861 said in Fresh install Ubuntu 16.04.1 Fog 1.3.4 Error:

The problem above is on the CLIENT end, not there server…server is okay from what I can tell

The server wasn’t OK at the time I posted what I did, it was out of space. This was not a fresh install of Ubuntu 16 /w fog if you were already out of space. The title of this thread should be changed.