Windows Problems

• L

  Error 2691 add to domain ok
  • lebrun78

  8
  0
  Votes
  8
  Posts
  23
  Views

  S

  @lebrun78 said in Error 2691 add to domain ok:

  How could I create a small script in C to test this function ?

  Do you have MS Visual Studio? With that you should be able to come up with a simple C# console app.

  But maybe try PowerShell first. Not sure if that yields the same results really:

  PS > $o = [System.Net.Dns]::GetHostAddresses("domain.tld") PS > $o Address : 2014353xx AddressFamily : InterNetwork ScopeId : IsIPv6Multicast : False IsIPv6LinkLocal : False IsIPv6SiteLocal : False IsIPv6Teredo : False IsIPv4MappedToIPv6 : False IPAddressToString : 192.168.1.x
• L

  sysprep, add to domain, and fog client
  • lebrun78

  3
  0
  Votes
  3
  Posts
  45
  Views

  L

  @tom-elliott
  Merci

• F

  Fog Client not installing
  • FuriousGamer065

  7
  0
  Votes
  7
  Posts
  27
  Views

  F

  @sebastian-roth I looked in the registry and I deleted the left over fog files, I got it to work after a little tinkering.

• D

  Using OEM License Key During Imaging
  • dmoore

  5
  0
  Votes
  5
  Posts
  28
  Views

  

  @dmoore Finer points so you can be in legal rights:

  https://aidanfinn.com/?p=14534

  While the article is old, I believe it is still a relevant.

  https://www.reddit.com/r/msp/comments/eboxe1/windows_10_imaging_rights_per_msft/ (more recent documentation)

• D

  Driver Injection - Need help
  • dmoore

  3
  0
  Votes
  3
  Posts
  33
  Views

  

  This is from 2017 but its still relevent today. I should update just so it doesn’t confuse people thinking well its 3 years old it can’t still work.

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

  Driver injection happens in 2 parts. The first part is a feature of FOG called a post install script. These are bash (linux scripts) that gets called just after FOG deploys the image to the target computer and just before FOG reboots the computer at the end of imaging.

  Using these scripts we check the model number of the computer then copy over the right drivers to a common location on the target computer. That is where the FOG world stops.

  In the windows world we add a command to the windows standard batch file that gets run at the end of OOBE and before the first login pane appears. This file is called setupcomplete.cmd. In this file we are going to add a command that calls the windows pnputil.exe program and point it to the directory where FOG dropped the drivers.

  pnputil.exe /add-driver "C:\Drivers\*.inf" /subdirs /install

  That pnputil program will search all sub-directories in c:\drivers looking for inf files to install. That program will also replace any windows generic drivers with hardware specific drivers.

  I use a modified version of the script in the tutorial to support 15 models of Dells with one base image. Those post install scripts can also be used to update the unattend.xml file with (FOG) run time settings. I don’t use the fog client on my campus, but I use a post install script to supply the system name and target OU to the unattend.xml file and then let the target computer name itself and connect to AD in the proper OU.

• S

  No USB-driver for lates Lenovo Yoga 11E 6th Gen
  • snjlscmi

  8
  0
  Votes
  8
  Posts
  25
  Views

  

  @snjlscmi If you are willing it may add value for your IT partner to participate in this thread since the solution may require some technical questions and answers.

  Network pxe booting requires the cooperation of several technologies. As Sebastian mentioned having a picture of the error will help set the context of where its broken. If you get no iPXE menu then that means the iPXE boot loader is not being sent to the target computer. In this case undionly.kpxe (for a bios computer) or ipxe.efi (for a uefi computer) is not being sent to the target computer. This information is typically sent via the dhcp process.

• 

  First default domain admin login never ends when FOG (1.5.0) joins to domain (FOG Client 0.11.15)
  • x23piracy

  3
  0
  Votes
  3
  Posts
  22
  Views

  

  Hi,

  thanks for your suggestions, i made another try i gave the first login more time, after 10 minutes the first login attempt worked, i maybe was to impatient usually a login doesnt take such long, every login attempt after that first one is working normally.

  Hmpf, i will try recreate the image from scratch to see if this impact occours again.

  Best Regards X23

• A

  Smart Installer caching credentials causing AD lockouts - maybe?
  • altitudehack

  2
  0
  Votes
  2
  Posts
  9
  Views

  S

  @altitudehack said in Smart Installer caching credentials causing AD lockouts - maybe?:

  It’s especially weird because I wouldn’t have been able to actually run the installer as a non-admin …
  Sorry for pointing the finger at FOG but it’s the only non-commercial software installed on this particular laptop that I installed under my non-admin account.

  Those two sentences don’t make sense to me. One is saying fog-client was installed using the non-admin account and the other says no.

  The fog-client installs a service that should run as local system account and not using AD-accounts at all. Though the fog-client is trying to join the domain on every cycle it runs. If your non-admin account is used as AD-credentials (FOG web UI -> host settings -> Active Directory) and the password was changed at some point I can imagine this to happen as described. But the AD-account would have to have rights to join a computer to the domain - don’t think a non-admin account can do this.

• C

  Doubts About FOG Project Client Windows
  • cstutz

  2
  0
  Votes
  2
  Posts
  21
  Views

  

  MOD Note: Cross forum post here: https://forums.fogproject.org/topic/14843/doubts-about-fog-project-client-windows

• J

  Client does not want to update from 11.6 to 12.0
  • Jurgen Goedbloed

  2
  0
  Votes
  2
  Posts
  37
  Views

  S

  @Jurgen-Goedbloed I had a look through the code and I am fairly sure this is caused by the old code signing cert has lost validity on the 7th of September 2020. This cert is only used to ensure the binaries are certified by the FOG project team. We updated the code signing cert in January 2020 and released FOG 1.5.8 together with fog-client 0.11.19.

  Unfortunately I kind of lost sight of this “major” change that would affect auto-updating after 7th of September 2020 and never officially announced that people should update earlier for the auto-update to work.

  So from the version number we see in your log file I am sure you updated from FOG 1.5.7 to 1.5.9 - skipping the fog-client update that introduced the new code signing cert. This would have worked perfectly fine while the old code signing cert was still valid but fails now.

  You’ll need to update all your fog-client installations to 0.11.19 (auto-update to 0.12.0 will work from there) or 0.12.0 through some other kind of software deployment mechanism I am afraid.

  For now you should manually edit /var/www/html/fog/lib/fog/system.class.php and set FOG_CLIENT_VERSION back to 0.11.16 or clients will keep downloading the SmartInstaller.exe binary over and over again and put load on your FOG server for no reason. The code is smart enough to handle a situation where you have FOG_CLIENT_VERSION set to 0.11.16 version but the fog-client on some or all of your machines is on 0.12.0 already. So don’t worry about this.

• J

  UEFI Device Not booting
  • jgeorgic

  10
  0
  Votes
  10
  Posts
  44
  Views

  

  @jgeorgic first refind 0.11.4 was added many releases ago. So you should have the latest with 1.5.7 or later.

  Second, with a windows target OS and the target computer configured to boot from the hard drive first (and there is only one OS on the target drive), there is no way for the refind menu to appear. Its simply not possible unless the computer was configured for dual booting and you have a second OS on the target drive.

• G

  Images not deploying to computers
  • gadams

  22
  0
  Votes
  22
  Posts
  66
  Views

  G

  I had tried that originally when I started working with all of this. Either I wasn’t doing something correctly, or it’s not built that way, because I never could get it to enable the build-in administrator account. I still have the files if you want to take a look at them.

• M

  Unable to start on fog server
  • Maxime22

  5
  0
  Votes
  5
  Posts
  24
  Views

  

  @Maxime22 is your fog server at 192.168.1.200?

  If so, do you have a cheap / unmanaged / dumb network switch you can install between the building network switch and the PXE booting computer for a test? If this dumb switch solves the problem then we have a place to look.

• B

  Not able to use Legacy on BIOS :(
  • bwenig

  7
  0
  Votes
  7
  Posts
  41
  Views

  N

  @george1421 said in Not able to use Legacy on BIOS :

  ipxe.efi

  George, you are the best. You constantly help me out on these forms. If I could take you out for a working lunch I would.

  I switched it over to ipxe.efi and it worked.

• L

  Computer Name after imaging
  • loraxyguy

  3
  0
  Votes
  3
  Posts
  29
  Views

  L

  @george1421 Very nice, I will have to read into this. I will just need to comment out the AD domain joining and keep the host name change part only.

• K

  SOLVED Captured Image is about the size of the Hard Drive
  fog fog 1.3.3 • • KevFlwrs

  11
  0
  Votes
  11
  Posts
  270
  Views

  

  I realize this post is a bit old, but I wanted to thank everyone for their suggestions and give our experience to back up what has been said in this topic already. We experienced an image that should have been about 120gb, but was showing in FOG as the full 500GB hard drive. After referencing this thread, it fixed the issue. The steps we took are below in order:

  Verified that the PC didn’t have a second drive or second large partition it was capturing
  Verified that bitlocker encryption was OFF using the command prompt command “manage-bde -off C:”
  Ran Disk Cleanup (to get rid of old unused files)
  Ran Tools > Check to scan for hard drive errors (may require reboot to fix)
  Ran Tools > Tools > Optimize and defagment
  Capture Image again

  Once we did those steps, the newly captured image only takes up the actual amount used on the hard drive.

• B

  ipxe initialising devices
  • bluedark

  2
  0
  Votes
  2
  Posts
  16
  Views

  B

  i solved my problem using undionly.kpxe file from a debian 10.4

• S

  No network interfaces found when deploying Image
  • sysadmin

  15
  0
  Votes
  15
  Posts
  56
  Views

  

  @sysadmin How did you create this directory /opt/fog_stable Did you clone it from the git repository? Your error is not a very common one or one I’ve personally seen before.

• H

  Cannot perform New-PSDrive on SYSTEM account
  • hancocza

  1
  0
  Votes
  1
  Posts
  10
  Views

  No one has replied

• H

  New to fog, looking for a good step by step on creating an image
  • hcabrera

  2
  0
  Votes
  2
  Posts
  37
  Views

  

  Just to be clear (I can read your request 2 different ways), fog doesn’t care about the source image or how its setup. FOG only moves disk blocks from the source computer to storage on the FOG server and then from storage on the FOG server to the target computer. How you prepair the reference image before cloning and what happens to the target computer after FOG is done is up to the IT technician.

  But in general terms, for MS Windows you will want to setup the computer in audit mode to perfect how you want the target computers to appear, then sysprep the reference image and power it off (using a sysprep command line option). Then you pxe boot the reference image with FOG and capture the image. On the target computer side, you register the target computer with FOG. Then you assign an image to the target computer and create a deploy task. When the target computer is pxe booting FOG will image the computer then reboot it. On the first reboot the target computer will startup OOBE/Winsetup to complete the installation on the target computer, at this point of the first boot of the target computer FOG is no longer involved with the imaging process (said knowing that if the target computer is configured appropriately the FOG client will carry out an required post install commands).

  There is a wiki page that describes capturing your first image that you might want to look over: https://wiki.fogproject.org/wiki/index.php?title=Booting_into_FOG_and_Capturing_your_first_Image