@samuel You can set a kernel parameter in the iPXE menu options to make machines shut down on deploy (or other tasks). Go to the FOG web UI -> FOG Configuration -> FOG Settings -> General Settings and add shutdown=1 to the field FOG_KERNEL_ARGS.

@Sebastian-Roth hi, yes: they have the same settings, they are all from the same batch (production wise)

I believe the system partition is the issue. I tried imaging on legacy and uefi, issue doesn’t change.

Tried to wipe the disks first, also no change.

Will try the full copy tomorrow, thanks for your suggestion.

@agray You said you set the machine to legacy, and secure boot is off, but
1 did you enable CSM support?
2 did you change your boot order?
Please take a picture of your BIOS/UEFI settings so i can help as well.
Im interested in your boot page, CSM, boot order, and secure boot pages

@kralon @Sebastian-Roth

I force the windows 10 activation on Windows 10 Pro with a script like this Script. It’s Writed thinking in WindowsUpdate disabled.
It Works to me on all License Types, except LV’s that is not tested.

If (-NOT ([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] "Administrator")) { $arguments = "& '" + $myinvocation.mycommand.definition + "'" Start-Process powershell -Verb runAs -ArgumentList $arguments Break } # License $serviceName = "wuauserv" $hostinfoFile = "c:\nntt\hostinfo.txt" # this is the hostinfo file downloaded from the postdownload $COAProductKeyPattern = "(?<=hostproductkey=).*" $COAProductKey = Select-String -Path $hostinfoFile -Pattern $COAProductKeyPattern | ForEach-Object {$_.Matches.Value -Replace "'",""} $BIOSProductKey = (get-wmiObject -query 'select * from SoftwareLicensingService').OA3xOriginalProductKey.Trim() Set-Service -Name $serviceName -StartupType Manual Start-Sleep -s 5 Start-Service -InputObject $serviceName (Get-Service -InputObject $serviceName).WaitForStatus('Running') If ($BIOSProductKey) { Invoke-Expression -Command "changepk.exe /productkey $BIOSProductKey" } ElseIf ($COAProductKey) { Invoke-Expression -Command "changepk.exe /productkey $COAProductKey" } Invoke-Expression -Command "$env:SYSTEMROOT\System32\cscript.exe //B $env:SYSTEMROOT\system32\slmgr.vbs /ato" Start-Sleep -s 10 Stop-Service -InputObject $serviceName (Get-Service -InputObject $serviceName).WaitForStatus('Stopped') Start-Sleep -s 5 Set-Service -Name $serviceName -StartupType Disabled Start-Sleep -s 5 # End License

@sokhanh21xn Mind responding to my questions?

This topic is being discussed on github in detail: https://github.com/FOGProject/fog-client/issues/110

@Sebastian-Roth the domain alunos.sc.br is a sub-domain of sc.br. I will test it as you mentioned, only with user. Soon notice the return here, thanks for now!

@mm-Ekimia From what I read between the lines I can imagine this being a UEFI vs. legacy boot issue or something.

If you still need help with this I ask you to post the information I asked for. Marking as solved for now.

@Quazz I know that I can capture and deploy UEFI images in Legacy mode, but I have to go in front of the PC turn it on, go in setup page, set network boot, then deploy, then go again in setup page, set windows boot manager … and do it 300 times.
So at the moment I’ve made a Legacy installation image, and I leave all pc in network boot, so when I want to deploy I just select the group and fire a multicast deploy.
I’m working on YASHI for booting in legacy mode I’ve ask to their support.

@george1421

Thank you George,

I only can say ‘Busy Busy Busy’ as Twiki – I need to absorb the information.

When I mentioned ‘the installation continues as from local media (DVD)’ – I meant that as files was made available from network resource the process will continue in same way as if it was run from local media (I meant that process will not be different, except that files be accessed from network and not from local computer media).

Thank you again George
Polar Bear

@Sebastian-Roth I don’t want to say definitely that there is a character issue since it could have been a whole host of other things that changing the domain account and password fixed. I’ll try to give it a test when I get some more free time in the next week or so to see if that’s really the issue.

Thanks for all your help!

@BSZAdmin Possibly this issue has to do with the computer having been turned off for a fair amount of time before you get the request to move it to another department?? See here: https://www.prajwaldesai.com/workstation-trust-relationship/

The more I read about this the less I think this is caused be the fog-client. But we’ll see. Please try things as suggested and we’ll take it from there.

@Wayne-Workman
@george1421

I figured this one out… I was having problems with security. One of Windows 10’s recent updates (as in the last 3 months or so) was blocking connections to anonymous shares. It allowed them but they needed to be authenticated. For those of you who stumble across this post…

Add your FOG server to your domain and configure Kerberos. After you do this you will need to configure your driver share. I have included the way I did mine and it works. This configuration is for using an existing domain controller. In our case, we use Windows Server 2012 to do domain control.

Do the following:

yum install samba*
yum install krb5-libs krb5-workstation

Confuguration Kerberos /etc/krb5.conf

[logging]
default = FILE:/var/log/krb5libs.log
kdc = FILE:/var/log/krb5kdc.log
admin_server = FILE:/var/log/kadmind.log

[libdefaults]
default_realm = YOURDOMAIN
dns_lookup_realm = false
dns_lookup_kdc = false
ticket_lifetime = 24h
renew_lifetime = 7d
forwardable = true

[realms]
DOMAIN.TN = {
kdc = dns-name-your-domain-controller
}

[domain_realm]
netbiosnameyourdoamin = NETBIOSNAMEYOURDOMAIN
netbiosnameyourdomain = NETBIOSNAMETYOURDOMAIN
Configuration samba /etc/samba/smb.conf

[global]

workgroup = DOMAIN
password server = dns-name-your-domain-controller:88
realm = NETBIOSNAMETYOURDOMAIN
security = ads
idmap uid = 16777216-33554431
idmap gid = 16777216-33554431
template shell = /bin/bash
winbind use default domain = false
winbind offline logon = true

log file = /var/log/samba/log.%m
max log size = 50

passdb backend = tdbsam

load printers = yes
cups options = raw

[homes]
comment = Home Directories
browseable = no
writable = yes

[printerdrivers]
comment = All FOG Printers
path = /PATHTODRIVERS
browseable = no
guest ok = no
writable = yes

Add dns name in /etc/hosts

Install and configuration ntp server (It’s important for use Kerborose authorization)

yum install ntpd
edit /etc/ntp.conf
server ip-address-your-ntp-server prefer
Create ticket
kinit account-admin-for-active-directory@NETBIOSNAMETYOURDOMAIN
Add server in domain

net ads join -S dns-name-your-domain-controller -U account-admin-for-active-directory
Create keytab for Kerberos

net ads keytab create -U account-admin-for-active-directory
Edit file /etc/nsswitch.conf

passwd: files winbind
shadow: files winbind
group: files winbind

Restart samba and windind

Test
net ads info
wbinfo -t

@kkptrck said in Skipping partition restore (MBR Only):

/dev/sda1 : start= 64, size= 1076291, type=27

I have missed one important thing here when you first posted this. The start sector 64 is quite unusual (usually it’s 63 or some other sector but I have not seen 64 yet) and I can imagine this being the cause of your issue. Did you manually do the partitioning?

@bogle No model specific drivers are copied to the target computer during image push and then inserted into the windows environment using pnputil utility.

https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed

I probably should update it for 2019 / Win10 specifically, but everything is in there.

I do have MDT add in the WinPE10 standard drivers so the golden image has at least the core network and disk drivers, but most of the windows 10 built in drivers are good enough to get to at least the point where the pnputil program is used.

@george1421 I got some tricky ways to find if dnsmasq is using the configuration that we created. In the directory /etc/dnsmasq.d/, we created the configuration file, but if there is no other file called README, I think dnsmasq did not use the configuration file. But after I updated dnsmasq, there is a new file called README. And it works!!! I am not sure if my thoughts was right. But it got working in my case.

@george1421 Done, hope that’s more obvious now.

I added some more checks and a more appropriate error message so people will find out more easy in future versions of the fog-client.

@Sebastian-Roth Thanks for your help! That fixed the issue.