thanks for your great work
lebrun78
@lebrun78
Université de Rennes
Best posts made by lebrun78
-
RE: Kernel panic -not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
@george1421
I had Pxelinux.0 in my dhcp, the new code replace it now. -
RE: Set Host Product Key no logger works
Yes, restart computer > ok
If I restart the fogservice, it works too -
can't install fog client 0.11.19 "Unable to install CA certificate"
Hello
I upgraded my server from 1.5.7.60 to 1.5.8 yesterday.
I can’t install my fog client using msi file.
I get “Unable to install CA certificate”
Could you help me ?Arnaud
-
RE: Problem PXE boot since windows 10 1803
I use fog 1.4.4 on centos 6.8.
I use non-resizable image but the problem seem to be on boot chaining between ipxe and windows. -
RE: FOG Multicast Not starting anymore
mysql> use fog; Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Database changed mysql> ALTER TABLE groups ENGINE=InnoDB; ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'groups ENGINE=InnoDB' at line 1 mysql> ALTER TABLE `groups` ENGINE=InnoDB; Query OK, 69 rows affected (0.02 sec) Records: 69 Duplicates: 0 Warnings: 0
-
RE: Problem PXE boot since windows 10 1803
May be I am not clear.
All my compututer are boot first on pxe controlled by FOG.
But I have no problem with computer that are running Linux and Windows10 =< 1709.
But for computer that are running Windows 10 1803, available for 2 weeks, boot chainon between pxe and harddrive doesn’t work.
To start this machine I have to disable PXE.in bios or escape oduring PXE loading. -
RE: Problem PXE boot since windows 10 1803
This morning, I have the problem on several machines which have get 1803 update…
I have changed the dhcp configuration for this machine to point to my testing fog server. (1.5.2)
On this server, I have applied Quazz solution to set grub in place of sanboot and now my Dell machines on 1803 have started passing by PXE…Now I have to set it to my production fog server…
Thanks for your help
Latest posts made by lebrun78
-
RE: problem after deployment with release 1.5.10
Hello,
I’m working with CedricoR,
We don’t have probrem with windows host working with uefi.
On Ubuntu host, system crash booting refind after pxe. If we choose EXIT in FOG host conf, we have to choose manually booting from harddrive. Then Ubuntu works -
RE: FOG 1.5.10 officially released
Hello and thank you for your very useful job !
The installation instructions in https://news.fogproject.org/fog-1-5-10-officially-released/ link seams not good.
The link drives me to installer archiveArnaud
-
RE: powershell snapin no output, non error
@JJ-Fullmer
No log film created.
Task created as you proposed require administrator login to be executed. That is not the purpose of the snapin.
But I have no idea how to work around the problem@Tom-Elliott
Do you have any idea how to keep pxe boot with eufi Windows ?If I have to get up from my chair every time I have to deploy, that’s no big deal.
-
RE: powershell snapin no output, non error
@Tom-Elliott
Yes Tom, I agree,
That’s why JJ-Fullmer create a task executed as user administrator to modify the boot order.
I have a powershell problem, to how to create a task trigger at the creation of the task -
RE: powershell snapin no output, non error
@JJ-Fullmer
Thank you for your work, this script runs with snapin but does not do the expected job, the pxe is not ranked àat the good place :$adminUsr = "$($ENV:ComputerName)\Administrateur" $trigger = New-ScheduledTaskTrigger -AtLogOn -User $adminUsr; $settings = New-ScheduledTaskSettingsSet -WakeToRun -Priority 0; $principal = New-ScheduledTaskPrincipal -UserId $adminUsr -RunLevel Highest -LogonType Interactive; $sb = { $firmware = cmd /c "C:\windows\system32\bcdedit.exe" /enum firmware; $fullLine = (($firmware | Select-String "IPV4" -Context 1 ).context.precontext)[0]; $GUID = '{' + $FullLine.split('{')[1]; $result = cmd /c "C:\windows\system32\bcdedit.exe" /set "{fwbootmgr}" displayorder $GUID /addfirst; #make c:\temp if it doesn't exist if (!(Test-Path 'C:\temp')) { mkdir 'C:\temp'; } #log everything in a new C:\temp\firmware.log file New-Item -path C:\temp\firmware.log -itemType File -value "Firmware: $($firmware | out-string)`n`nFullLine: $fullLine`nGUID_ipV4: $GUID`nresult: $result`n" -force; } New-Item C:\netboot.ps1 -value $sb.tostring() -force; $action = New-ScheduledTaskAction -Execute "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" -Argument "-File C:\netboot.ps1" $task = New-ScheduledTask -Action $action -Description "update bcd" -Principal $principal -Trigger $trigger -Settings $settings; $taskName = "boot-to-IPV4"; Register-ScheduledTask -InputObject $task -TaskName $taskName; Start-ScheduledTask -TaskName $taskName; while ((Get-ScheduledTask $taskName).State -eq 'Running') { Start-Sleep -Seconds 1; } Unregister-ScheduledTask -TaskName $taskName -Confirm:$false -EA 0; move-Item 'C:\netboot.ps1' 'C:\netbootOLD.ps1' -force -ea 0;
-
RE: powershell snapin no output, non error
@JJ-Fullmer
I tried command line step by step with psexec, it works
I tried command line step by step with your modified script, it works
I tried snapin withSnapin Command read-only: C:\windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy bypass -NoProfile -File boot-uefi-pxe_win.ps1
and with boot-uefi-pxe_win.ps1
$bcdedit = "C:\windows\System32\bcdedit.exe" $firmware = & {start-process -filepath $bcdedit -args "/enum firmware" -Wait -RedirectStandardOutput output.txt ; get-content output.txt; remove-item output.txt} $fullLine = (($firmware | Select-String "IPV4" -Context 1 ).context.precontext)[0] $GUID = '{' + $FullLine.split('{')[1] $result = & {start-process $bcdedit -args "/set `"{fwbootmgr}`" displayorder $GUID /addfirst" -Wait -RedirectStandardOutput output.txt ; get-content output.txt; remove-item output.txt} # $firmware = $(bcdedit /enum firmware) # $fullLine = (($firmware | Select-String "IPV4" -Context 1 ).context.precontext)[0] # $GUID = '{' + $FullLine.split('{')[1] # $result = $(cmd /c bcdedit /set "{fwbootmgr}" displayorder $GUID /addfirst) $dateheure = (date).ToString() if (!(Test-Path 'C:\temp')) { mkdir 'C:\temp' } #log everything in a new C:\temp\firmware.txt file New-Item -path C:\temp\firmware.txt -itemType File -value "Firmware: $($firmware | out-string)`n`nFullLine: $fullLine`nGUID: $GUID`nresult: $result`ndate: $dateheure`n" -force
And the result is allways
Get-Content C:\temp\firmware.txt Firmware: FullLine: GUID: result: date: 03/04/2023 17:30:13
My OS is Windows 11
-
RE: powershell snapin no output, non error
@JJ-Fullmer
Running your script step by step works, I don’t understand why it doesn’t work by snapin.
Is it possible to test a script by the system account used by fog service? -
RE: powershell snapin no output, non error
@JJ-Fullmer
Thank you for your proposition
I now have the file with the title of each item, but the values are empty I modified by adding the date, just to have a trace$firmware = (bcdedit /enum firmware) $fullLine = (($firmware | Select-String "IPV4" -Context 1 ).context.precontext)[0] $GUID = '{'bcdedit /set "{fwbootmgr}" displayorder $GUID /addfirst) $datetime = (date).ToString() if (!(Test-Path 'C:\temp')) { mkdir 'C:\temp' } #log everything in a new C:\temp\firmware.txt file New-Item -path C:\temp\firmware.txt -itemType File -value "Firmware: $($firmware | out-string)`n`nFullLine: $fullLine`nGUID: $GUID`nresult: $result`ndate: $datetime`n" -force
I get
Firmware: FullLine: GUID: result: date: 03/04/2023 09:35:36
I tried adding cmd /c > it’s the same
-
RE: powershell snapin no output, non error
When I run the command
C:\> powershell.exe -ExecutionPolicy RemoteSigned -NoProfile -File boot-uefi.ps1
I get :
L'opération a réussi.
-
powershell snapin no output, non error
I try to run the script as snapin
# Create text file containing firmware settings bcdedit /enum firmware > c:\temp\firmware.txt # Find the line containing "IPV4", and read the line just before that $FullLine = (( Get-Content c:\temp\firmware.txt | Select-String "IPV4" -Context 1 ).context.precontext)[0] # Delete our temporary file #del firmware.txt # Split line into fields using the first left-curly as the delimiter, # and then grab the second field (and restore the first left-curly) $GUID = '{' + $FullLine.split('{')[1] # Set the boot order #bcdedit /set {fwbootmgr} displayorder $GUID {bootmgr} cmd /c bcdedit /set "{fwbootmgr}" displayorder $GUID /addfirst # SIG # Begin signature block # MIIECAYJKoZIhvcNAQcCoIID+TCCA/UCAQExCzAJBgUrDgMCGgUAMGkGCisGAQQB # gjcCAQSgWzBZMDQGCisGAQQBgjcCAR4wJgIDAQAABBAfzDtgWUsITrck0sYpfvNR
But I get no c:\temp\firmware.txt file
I think the script is not executedHere is the command line viewed on the fog console:
powershell.exe -ExecutionPolicy RemoteSigned -NoProfile -File boot-uefi.ps1I get this log
------------------------------------------------------------------------------ 31/03/2023 16:08:35 Client-Info Client Version: 0.11.19 31/03/2023 16:08:35 Client-Info Client OS: Windows 31/03/2023 16:08:35 Client-Info Server Version: 1.5.8 31/03/2023 16:08:35 Middleware::Response Success 31/03/2023 16:08:35 SnapinClient Running snapin boot-uefi-pxe-first 31/03/2023 16:08:35 Middleware::Communication Download: http://148.60.x.x//fog/service/snapins.file.php?mac=B8:85:84:AC:89:FA&taskid=5453 31/03/2023 16:08:36 SnapinClient C:\Program Files (x86)\FOG\tmp\boot-uefi.ps1 31/03/2023 16:08:36 Bus Emmiting message on channel: Notification 31/03/2023 16:08:36 SnapinClient Starting snapin 31/03/2023 16:08:40 SnapinClient Snapin finished 31/03/2023 16:08:40 SnapinClient Return Code: 0 31/03/2023 16:08:40 Bus Emmiting message on channel: Notification 31/03/2023 16:08:40 Middleware::Communication URL: https://fogus/fog/service/snapins.checkin.php?taskid=5453&exitcode=0&mac=B8:85:84:AC:89:FA&newServ
Any idea ?