Windows Problems

• M

  UNSOLVED Windows 10 Deployment stuck
  • Mr.Pinguin777  

  16
  0
  Votes
  16
  Posts
  139
  Views

  S

  @Mr-Pinguin777 Did you ever get this solved? Any more help you need from us? See George’s questions.
• S

  SOLVED Windows PC Lock up in sleep mode
  • Scott Boucher  

  3
  0
  Votes
  3
  Posts
  36
  Views

  D

  @Scott-Boucher This issue is definitely not fog related. I have seen this on multiple occasions and usually comes down to a UEFI machine with a SSD. either try disabling sleep is the advanced power settings, try disabling hibernation, Disable fast boot in bios, or theres a “turn off hard disk after” setting that you may want to see if thats disabled. I have linked this issue to usually the computers bios misidentifying the SSD as a HDD making windows use the wrong things to sleep/hibernate. If you are using a HDD then try to see if there is a bios update for your machine and/or driver updates from the manufacturers website. Good Luck, this problem is proprietary to your type of device. Do some research in that and also look at disabling the settings. I have also learned that 5400 rpm 2.5" HDD are absolutely horrible. If that is what you have within those machines, try to put in a SSD for a test and see if you get the same results.
• G

  SOLVED WOL Firmware Linux Kernel Breaks - Power pulled or boot to windows fixes
  windows dell wol wakeonlan optiplex • • Gael  

  26
  0
  Votes
  26
  Posts
  81
  Views

  

  @Gael et al. I’m post a more descriptive post to summarize what the issue is. I don’t know how to fix (so I’ll start there.) TL;DR; Linux Kernel is putting a volatile Firmware on the NIC. This happens when FOS loads and the kernel begins associating the drivers. On restart, the firmware is still existing on the NIC from the Kernel. When Windows Boots, it re-flashes the volatile firmware so subsequent elements will work. Or a full power pull will do too (completely cold boot.) Basis: This particular issue, is due to Linux Kernel having a firmware defined for the NIC. This is volatile. This means when power is pulled, the firmware will no longer be present and normal actions will work properly. While the machine is in FOS, the linux kernel hands it a temporary Firmware File and this is what’s causing the strangeness with the NIC. Pulling the power cord causes the firmware to wipe. Similarly, if booting to Windows immediately after, and then powering off the machine, it should WOL. This is because Windows has a FW being applied when it loads, overwriting whatever the Linux Kernel pushed.
• E

  SOLVED ipxe initialising devices fog stuck
  • Emyle  

  14
  0
  Votes
  14
  Posts
  1416
  Views

  P

  @Wayne-Workman Worked for me
• S

  SOLVED How to shutdown the machine automatically when deployment is complete
  • samuel  

  2
  0
  Votes
  2
  Posts
  43
  Views

  S

  @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.
• B

  SOLVED Boot Option Issue (PXE booting)
  • Brendan Clemente  

  7
  0
  Votes
  7
  Posts
  65
  Views

  B

  @george1421 Looked into this and it is exactly what I am looking for. Thank you very much George.
• F

  SOLVED Windows 10 - Deployment can't boot
  • Fimlore  

  3
  0
  Votes
  3
  Posts
  74
  Views

  F

  @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.
• 

  Golden Image Deploy Problems
  • agray  

  8
  0
  Votes
  8
  Posts
  111
  Views

  D

  @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
• K

  SOLVED Activate Windows 10 via FOG agent
  • kralon  

  18
  0
  Votes
  18
  Posts
  191
  Views

  

  @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
• S

  UNSOLVED Win7 manual partimage
  • sokhanh21xn  

  3
  0
  Votes
  3
  Posts
  26
  Views

  S

  @sokhanh21xn Mind responding to my questions?
• J

  UNSOLVED FOG service quits running
  • Joe Gill  

  16
  0
  Votes
  16
  Posts
  98
  Views

  

  Try configuring the servicio with this: sc.exe config FOGService start=delayed-auto sc.exe failure FOGService actions= restart/60000/restart/60000/restart/ reset= 120. It work’s to save me from stopping Fogservice errors.
• 

  SOLVED Windows 10 Image constantly trying to join domain after join.
  • SKasai  

  12
  0
  Votes
  12
  Posts
  141
  Views

  S

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

  SOLVED Fog Client fails to join AD Domain with error 2202
  • amorim  

  7
  0
  Votes
  7
  Posts
  73
  Views

  A

  @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!
• 

  SOLVED Capturing W10 on Sata , restoring on NVME = Fail to boot
  • mm Ekimia  

  7
  0
  Votes
  7
  Posts
  95
  Views

  S

  @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.
• I

  SOLVED UEFI machine are always seen as BIOS machines causing boot issue
  • ITSLUIGICASALE  

  8
  0
  Votes
  8
  Posts
  73
  Views

  I

  @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.
• P

  SOLVED Windows 8.1 update does not work properly
  • Polar Bear  

  12
  0
  Votes
  12
  Posts
  147
  Views

  P

  @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
• I

  SOLVED Fog Client fails to join AD Domain with error 1326
  • ians  

  11
  0
  Votes
  11
  Posts
  140
  Views

  I

  @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!
• B

  SOLVED Hostnamechanger fail while renaming client inside the domain
  • BSZAdmin  

  10
  0
  Votes
  10
  Posts
  106
  Views

  S

  @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.
• J

  SOLVED Windows 10 Anonymous Share Issue Printer Management
  • Joe Gill  

  4
  0
  Votes
  4
  Posts
  34
  Views

  J

  @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
• K

  SOLVED Skipping partition restore (MBR Only)
  • kkptrck  

  10
  0
  Votes
  10
  Posts
  43
  Views

  S

  @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?