Hi,
I think there is a little bug in fog webinterface / Hosts / Image History.
We are many technician.
In the hosts if i go to the menu “Image History” i see in the first column “Engineer” always my name (instead if not me who have deploy image on this host).
While if i go to the mysql database i see the good technician name.
Regards
@Sebastian-Roth
Ok thanks.
Waiting, workaround for us is to use SUN, MON, TUE, WED, THU, FRI, SAT instead of number for Shutdown and Reboot
Thanks for your quickly solution.
It’s resolve this.
It’s possible to push it to the next release ?
Hi,
We see a weird usage with Power Management (problem only with Shutdown and Reboot , not happen with Wake On Lan).
Number of “Day of Week” does not have the same use as cron.
For example :
40 11 * * 3
-In FOG : correspond to TUESDAY
-In CRON : correspond to WEDNESDAY
I think it’s a bug on FOG Client interpretation of cron ?
It is possible to restore for Shutdown and Reboot the same usage of “day of week” of cron like this ?
0 - Sun Sunday
1 - Mon Monday
2 - Tue Tuesday
3 - Wed Wednesday
4 - Thu Thursday
5 - Fri Friday
6 - Sat Saturday
7 - Sun Sunday
Regards
Hi,
Same problem here with Windows 10 and UEFI.
If you have Dell Computers see solution here with Powershell Script and tools Dell Command Configure :
https://www.dell.com/community/Enterprise-Client/Dell-Command-Configure-bootorder/td-p/5075223
thanks!
It’s more clear.
I always have 0.11.16 version, not need to upgrade 
Regards.
Hi,
I want confirmation about FOGClient to deploy on my computers.
I have FOG 1.5.5
I found 2 FOGService in :
/var/www/fog/client/FOGService.msi => version 0.11.16
/var/www/fog/client/FOGService.zip - “FOG Service Installer.msi” => version 3.0.29 but not work for silent install with options.
What is the “good” version ?
@sudburr
In my case in my postinstall script (fog) i copy only driver for concerned model, not all drivers of all model.
After this command in sysprep add driver who are copied in c:\drivers in the driver store.
For not doing this for all model i go to add “if” in my postinstall script to add this in my xml only for model 7060 and 7460
I have resolve this with add this in my xml unattend file :
Pass Specialize : Microsoft-Windows-Deployment
<RunSynchronousCommand wcm:action="add">
<Order>1</Order>
<Description>Injection Pilotes</Description>
<Path>pnputil /add-driver C:\drivers\*.inf /subdirs /install</Path>
</RunSynchronousCommand>
</RunSynchronous>
Thanks for your response.
SetupComplete is launch at the end of Sysprep steps.
Install drivers here not resolve problem where my computers not add to active directory like is set in sysprep.
I go to try same in sysprep :
<Order>1</Order>
<Description>Injection Pilotes</Description>
<Path>C:\temp\drivers\dpinst.exe" /path "C:\temp\drivers" /q /se</Path>
</RunSynchronousCommand>
</RunSynchronous>
Hi,
We encounter a problem with network chipset intel I219-LM during Sysprep step.
We have this problem only with Dell Optiplex 7060 and 7460 AIO.
Problem is that computer not add to Active Directory because have not network at this step (Sysprep).
We have test Dell drivers, Intel Drivers, WinPE drivers but not work.
What is strange is after Sysprep steps, when logon on Windows 10 network drivers are installed and network works.
We use UEFI.
We have also test to “legacy option ROMs” and “enable attempt legacy boot”.
Have you solution for this problem or ideas ?
See logs for this problem :
-setupapi.setup.log (log install drivers during sysprep):
PCI\VEN_8086&DEV_15BB&SUBSYS_085A1028&REV_10\3&11583659&0&FE -> Configured [null] and unstarted (ProblemCode = 28, ProblemStatus = 0xC0000490, ConfigFlags = 0x00000040).
Code 28 (CM_PROB_FAILED_INSTALL)
Indicates that the installation failed and there is no driver selected for this device, although the kernel did not report a problem (and there is no DNF_XXX match for this the problem). This problem can be the result of an on-board system device (ISA timer, ISA RTC, RAM Memory, and so forth) that does not yet have an INF file
-setupapi.dev.log (log install drivers windows, who works but after windows start normally):
{Install Device - PCI\VEN_8086&DEV_15BB&SUBSYS_085A1028&REV_10\3&11583659&0&FE} 11:38:41.294
dvi: Device Status: 0x01802400, Problem: 0x1c (0xc0000490)
dvi: Parent device: ACPI\PNP0A08\0
dvi: {Configure Device - PCI\VEN_8086&DEV_15BB&SUBSYS_085A1028&REV_10\3&11583659&0&FE} 11:38:41.309
dvi: Device Status: 0x01802400, Problem: 0x1c (0xc0000490)
dvi: Parent device: ACPI\PNP0A08\0
sto: {Configure Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\e1d65x64.inf_amd64_6828698491cd7eda\e1d65x64.inf}
sto: Source Filter = pci\ven_8086&dev_15bb&subsys_085a1028
inf: Class GUID = {4d36e972-e325-11ce-bfc1-08002be10318}
inf: Class Options = Configurable
inf: {Configure Driver: Intel(R) Ethernet Connection (7) I219-LM}
inf: Section Name = E15BB.10.0.1
inf: {Add Service: e1dexpress}
inf: Start Type = 3
inf: Service Type = 1
inf: Error Control = 1
inf: Image Path = \SystemRoot\System32\drivers\e1d65x64.sys
inf: Display Name = Intel(R) PRO/1000 PCI Express Network Connection Driver D
inf: Group = NDIS
inf: Created new service 'e1dexpress'.
inf: {Add Service: exit(0x00000000)}
inf: Hardware Id = PCI\VEN_8086&DEV_15BB&SUBSYS_085A1028
inf: {Configure Driver Configuration: E15BB.10.0.1}
inf: Service Name = e1dexpress
inf: Included INFs = pci.inf
inf: Config Flags = 0x00000000
inf: {Configure Driver Configuration: exit(0x00000000)}
inf: {Configure Driver: exit(0x00000000)}
flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\e1d65x64.inf_amd64_6828698491cd7eda\e1d65x64.sys' to 'C:\WINDOWS\System32\drivers\e1d65x64.sys'.
flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\e1d65x64.inf_amd64_6828698491cd7eda\e1d65x64.din' to 'C:\WINDOWS\System32\e1d65x64.din'.
dvi: Existing files modified, may need to restart related services.
sto: {Configure Driver Package: exit(0x00000bc3)}
dvi: Restart required for any devices using this driver.
dvi: Install Device: Configuring device (oem4.inf:pci\ven_8086&dev_15bb&subsys_085a1028,E15BB.10.0.1). 11:38:41.356
dvi: Install Device: Configuring device completed. 11:38:41.356
dvi: Device Status: 0x01802000, Problem: 0x0 (0x00000000)
dvi: {Restarting Devices} 11:38:41.356
dvi: Start: PCI\VEN_8086&DEV_15BB&SUBSYS_085A1028&REV_10\3&11583659&0&FE
! dvi: Device pending start: Device has problem: 0x38 (CM_PROB_NEED_CLASS_CONFIG), problem status: 0x00000000.
dvi: {Restarting Devices exit} 11:38:41.403
dvi: {Configure Device - exit(0x00000000)} 11:38:41.403
dvi: Device Status: 0x01802400, Problem: 0x38
dvi: {Install Device - exit(0x00000000)} 11:38:41.403
dvi: {Core Device Install - exit(0x00000000)} 11:38:41.403
dvi: Waiting for device post-install to complete. 11:38:41.403
dvi: Device post-install completed. 11:38:41.700
ump: {Plug and Play Service: Device Install exit(00000000)}
-setupact.log:
Info [DJOIN.EXE] Unattended Join: JoinDomain = [mydomain.local]
Info [DJOIN.EXE] Unattended Join: JoinWorkgroup = [NULL]
Info [DJOIN.EXE] Unattended Join: Domain = [mydomain.local]
Info [DJOIN.EXE] Unattended Join: Username = [toto]
Info [DJOIN.EXE] Unattended Join: Password = [secret not logged]
Info [DJOIN.EXE] Unattended Join: MachineObjectOU = [OU=xx,OU=xx,OU=xx,OU=xx,OU=xx,DC=mydomain,DC=local]
Info [DJOIN.EXE] Unattended Join: DebugJoin = [true]
Info [DJOIN.EXE] Unattended Join: DebugJoinOnlyOnThisError = [NULL]
Info [DJOIN.EXE] Unattended Join: TimeoutPeriodInMinutes = [NULL]
Info [DJOIN.EXE] Unattended Join: Enabled DC Locator ETW tracing. Log file: C:\WINDOWS\Panther\UnattendGC\UnattendedJoinDCLocator.etl
Info [DJOIN.EXE] Unattended Join: Checking that auto start services have started.
Info [DJOIN.EXE] Unattended Join: Calling DsGetDcName for mydomain.local...
Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 10 seconds...
...same error during 15 minutes
Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 10 seconds...
@Sebastian-Roth
ok I’ll try this as soon as I have a moment.
Don’t remember if i have use –force-https , but sure manually configured https in my virtualhost
@Sebastian-Roth ,
I do new test and same problem.
Tests are done on the same server.
Same problem with Firefox or Chromium with https://fog.mydomain.com (Hosts -> Basic Tasks -> Advanced / Wake-up -> Schedule Instant).
If i do same with http://fog.mydomain.com it’s works.
Don’t understand why, so i use http instead of https
@Florent
Hi,
Solution for Dell workstations : Dell Command Configure
Script : https://www.dell.com/community/Enterprise-Client/Dell-Command-Configure-bootorder/td-p/5075223
Hi,
Same problem here (on Dell computers).
I set PXE first order in BIOS (UEFI) but after deploy Windows 10 , Windows boot manager go ahead …
Very hassle because we used to clone our classroom on night when nobody is there.
Only solution what i found is to set Wake on lan option to boot on “LAN With PXE” . And shutdown computer and launch deploy task
Hi,
Is it possible to donate to the FOG Projects but not with Paypal or bank card ?
Because we are university and can’t pay with this means of payment (only by transfer RIB/BIC).
Resolve with this :
Web FOG Settings :
-FOG Client - Hostname Changer was enabled : Now DISABLED
-General Settings / Change Hostname early was enabled : Now DISABLED
After disable this two settings it’s ok …
Problem solved.
@george1421
Hi George,
I advanced on the problem and i am very confused…
I identify problem is just after post download scripts.
I say that because in my multiple tests if i shutdown computer just after sed, cancel fog tasks and boot on Windows 10 1803 the name is correct !
See screenshot of step where i ientify problem occurs :
In tests where windows computer name is correct i shutdown computer just before this screen.
As i saw rubric “Changing hostname” i search in my web FOG Settings :
-FOG Client - Hostname Changer was enabled : Now DISABLED
-General Settings / Change Hostname early was enabled : Now DISABLED
After disable this two settings it’s ok …
2 months to identify this !
Problem solved.
Very thanks for your helps and guidance to post download scripts.
I was convinced that it was coming from Windows/Sysprep.
Don’t know why that did not bother Windows 10 1709.
Thanks again
@george1421
Ok i hope problem comes from my postinstall scripts.
I will try this likes yours
Thanks for runway