Windows Problems

• I

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

  10
  0
  Votes
  10
  Posts
  70
  Views

  S

  @ians said in Fog Client fails to join AD Domain with error 1326: I hadn’t even thought of the possibility that it could be the special characters in the password. I went ahead and created a new domain admin account and used only letters and it worked! Ohhh, do we actually have a special character issue?! Updating the settings on my groups also updated the settings on my hosts, yay! So this sounds like you were able to get things right and domain join on the client worked? Shall we mark this solved? About the group settings you want to use the forum search and ask it for “persistent groups”. My guess is that you are expecting something from FOG’s group capabilities that it doesn’t have.
• J

  SOLVED Windows 10 Anonymous Share Issue Printer Management
  • Joe Gill  

  4
  0
  Votes
  4
  Posts
  25
  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

  UNSOLVED Skipping partition restore (MBR Only)
  • kkptrck  

  10
  0
  Votes
  10
  Posts
  23
  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?
• B

  UNSOLVED Hostnamechanger fail while renaming client inside the domain
  • BSZAdmin  

  8
  0
  Votes
  8
  Posts
  77
  Views

  B

  @fry_p hey guys, it was not my intention to be impatient. i am thankful 4 the good work of the fog developers and volunteers. keep on :)) Greets
• 

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

  8
  0
  Votes
  8
  Posts
  64
  Views

  

  @Sebastian-Roth said in Windows 10 Image constantly trying to join domain after join.: @SKasai said in Windows 10 Image constantly trying to join domain after join.: Also should note that this is a Windows 10 Machine Joining a Samba 4 Domain (NT domain for Authentication) Well, that brings another variable into the equation. I do remember that Samba 4 and Windows 10 was a huge fight when Win 10. I will still try to replicate this and see if I can fix it in the next weeks. Sorry about that… But given I am in an Education (UC, in case), our groups were making use of most open source material (FOG Project included). In the Samba 3 domain with Windows 7, we never had an issue. I just happen to notice it and with another department with regards to Samba 4 and Windows 10.
• B

  UNSOLVED No configuration methods succeeded
  • blong10  

  2
  0
  Votes
  2
  Posts
  17
  Views

  

  Duplicate post to here: https://forums.fogproject.org/topic/13586/no-configuration-methods-succeeded I’m going to lock this thread. Please continue to use the other post for additional comments.
• B

  SOLVED Trying to get started
  • bogle  

  4
  0
  Votes
  4
  Posts
  43
  Views

  

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

  SOLVED PXE-E53: No boot filename recieved
  • weidongyan  

  12
  0
  Votes
  12
  Posts
  43
  Views

  W

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

  SOLVED PXE-T01: File Not Found Error
  • weidongyan  

  18
  0
  Votes
  18
  Posts
  42
  Views

  S

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

  SOLVED Response Invalid MAC address format Windows 7 Client
  • Daryl Lee  

  15
  0
  Votes
  15
  Posts
  648
  Views

  S

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

  SOLVED Windows 7 Machines on Network pickup Fog Server as DHCP Server
  • jramos76  

  5
  0
  Votes
  5
  Posts
  19
  Views

  J

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

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

  5
  0
  Votes
  5
  Posts
  43
  Views

  S

  @mm-Ekimia said in Capturing W10 on Sata , restoring on NVME = Fail to boot: the previous image ( W10 1809 like this one ) can be flashed to NVME and SATA without problems. To me this sounds like it’s not something FOG is doing wrong in general but only it cannot handle your new image. Please follow George’s hint on trying to deploy this image you have the blue screen issue with to a different SSD disk/computer just to see if there is a general problem with this image. As well please post the contents of the text files d1.partitions, d1.minimum.partitions and d1.fixed_size_partitions of that particular image you see the blue screen after deploy. You find those in /images/IMAGENAME/... on your FOG server. @george1421 said: @developers have you heard of a similar issue in the past? Not that I am aware of. We use sgdisk --load-backup ... to read the partition layout from a binary backup which doesn’t include the Linux specific disk device namings. As far as I see it the change from SSD to NVMe shouldn’t play a role here. Different naming convention doesn’t matter as far as I know.
• C

  SOLVED Issue joining domain & activating Windows after deployment
  • ckasdf  

  19
  0
  Votes
  19
  Posts
  314
  Views

  C

  Thanks for the insight! I copied one of my build images to a test-copy, then made two changes. I then ran sysprep /generalize /reboot /unattend and allowed the VM to sysprep and reboot to see what happens. I didn’t capture it to run it through FOG, but I imagine the results will be mirrored once I do. I noticed that your unattend file didn’t contain a reference to SetupComplete. Therefore, I edited unattend.xml to remove the <Component> block that contained <AutoLogon> and <LogonCommands> (within which was contained the reference to SetupComplete.cmd). I moved unattend.xml to the Panther directory at your suggestion. When I ran sysprep, I tested it without defining a file, and sure enough, it picked it up with no problem. After allowing sysprep to do its job, I logged in as the local admin (since I didn’t have FOG to join the domain for me), and no command windows popped up to try running SetupComplete as the local user. SetupComplete didn’t appear in the Startup tab of Task Manager. FOGService was set to Automatic and was Running. In other words, the things that weren’t supposed to be happening no longer were, and the things that were supposed to happen WERE! :)   By the way, slightly on the topic, I know the wiki suggests restarting the computer with a command in SetupComplete after enabling the FOG Client, but Microsoft’s documentation suggests this is a bad idea: Warning You cannot reboot the system and resume running SetupComplete.cmd. You should not reboot the system by adding a command such as shutdown -r. This will put the system in a bad state. My SetupComplete file contains two lines: sc config FOGService start= auto net start FOGService It seems to still restart if needed, so maybe the shutdown line can be removed?   Thanks to @fry_p, @george1421, and @Sebastian-Roth for your contributions in helping me figure out this strange issue!
• 

  UNSOLVED FYI Win10 1903 sysprep possible bug
  • fry_p  

  3
  0
  Votes
  3
  Posts
  534
  Views

  

  In addition to what @Shad0wguy posted, your golden image should be developed on an isolated network, or at least one that doesn’t have internet access for just that reason. You don’t want windows updates to help you “fix” your system while you are preparing for it. If you are doing this in audit mode, for sure disable the windows update service until just before sysprepping it. I myself use MDT to build the golden image so one of the task sequences is to update the windows updates from our WSUS server and not to use direct internet updates. That way the updates are applied and completed in a known state before MDT exits. We will typically sysprep and capture with FOG right after MDT finishes. But its great you are documenting the problem here and the potential solution. Because if you have the issue there are 100 other folks that will have it in the future. So thank you for helping them out too.
• S

  SOLVED After installation of Windows 10 pro PC gets caught in a loop and will not boot to HDD.
  • seahunter  

  15
  0
  Votes
  15
  Posts
  114
  Views

  

  @seahunter Well we can take the fall back approach and build a FOS usb boot drive to bypass iPXE altogether. I’m pretty sure that bzImage will work if we boot from a usb flash drive. Here are the instructions. Read all of my posts including the caveats in taking this approach: https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image Also look at the forum chat bubble in the upper right corner of the page for a few additional hits.
• D

  UNSOLVED Windows 10 temp file clean up - Error(5) shrinkPartition - Capture fail
  • duanekaeb  

  15
  0
  Votes
  15
  Posts
  81
  Views

  S

  @duanekaeb Thanks for the pictures. What I posted was the command parted -l - the parameter being a lower case l (like lion). But using the print command you still got us exactly the information I was hoping to see. Ok, so the partition layout is fine from my point of view. So now I am wondering if C: is simply almost full and that is causing the problem. Reviewing the pictures again I saw something that I have not noticed before: Needed relocations: ... (16179 MB) While I am not an expert on the ntfs3g-lib implementation I am really wondering if this is just “too much for it”. It tries to shrink the partition and for that to be able to do it would need to relocate/move roughly 16 GB of data. While it’s not nice that it fails to do so I can kind of understand it’s having a hard time to do so. I really wonder why defrag didn’t help you with this. Probably a bit different on the SSD, hmmmm. Not sure what else we can do for you.
• X

  UNSOLVED Install windows error after capturing image
  • xburnerx00  

  9
  0
  Votes
  9
  Posts
  57
  Views

  X

  Yes, I’ll try to get to those. I am under a time crunch right now so I can not get to that right away. I deployed the image that gave me the error after it was created, and it deployed successfully.
• 

  SOLVED FOG 1.5.6: Windows unattended.xml is intermittently failing to work
  • Cheetah2003  

  27
  0
  Votes
  27
  Posts
  251
  Views

  

  I’m back! New results! I prepared my same image again, just to be sure it’s ship-shape. I captured the image with ‘Multiple Partition Image - Single Disk (Not Resizable)’ setting on the image. 4 out of 4 deploys worked flawlessly. Think we can call this case closed. Resizing NTFS partitions is dubious with the linux based tools and is causing intermittent issues with UEFI systems. Why this doesn’t affect legacy deployments, you got me. Ask Microsoft? I’m going to just put a powershell script to have windows do my resize operations after setup completes. Thanks to all who helped me track this issue down to it’s cause. Back to work, for me! For developers looking to remedy this issue, I’d look into this error message (which I’m not getting anymore with that no-resize setting!!): The protective MBR's 0xEE partition is oversized! Auto-repairing. I’d bet money this has something to do with it breaking on UEFI systems.
• 

  UNSOLVED Cannot Install One Or More Boot Critical Drivers
  • Russell18  

  6
  0
  Votes
  6
  Posts
  37
  Views

  

  @Russell18 said in Cannot Install One Or More Boot Critical Drivers: Does this help in way? Truthfully, no. FOG doesn’t care about drivers at all, your issue is with WinSetup/OOBE. From a windows standpoint, how are you installing the drivers into your windows golden image? Are you deploying a universal image for all hardware or do you have hardware specific images? Are you sysprepping your image before you capture with FOG? If you have a single golden image did you install all drivers for all possible models you are deploying to? Have you done the Shift-F10 thing and look at the windows setup logs in c:\windows\panther directory to see what driver/issue its having troubles with? As you might see there are more questions than answers. But at this time the issue during deployment is after FOG’s job is done, your issue is within WinSetup/OOBE.
• C

  SOLVED Issue Imaging Windows 10 1903 with unattend file
  • cemmerthal  

  6
  0
  Votes
  6
  Posts
  245
  Views

  C

  Thank you for your help. Removing the client was the solution. I looked into and as before I didn’t need any of the functions it assisted with. Thank you for your help. The drive still doesn’t resize correctly, but I will wait for the release of 1.5.7. At the time thought the two may be related. Looked through the reported bugs and didn’t see one that specifically called out that issue, but I will keep looking. Thanks again for all of your help!! +Craig