@sutra Sorry for the late reply! Can you provide the contents of d1.partitions, d1.minimum.partitions and d1.fixed_size_partitions? You find those files on your FOG server in /images/Alienware-i9-010618.

I haven’t added such a thing for one main reason. Multicast sessions are intended to be things you’re sitting in front of the systems for. I’ll see about adding a feature like this however as I can see the value in it, and didn’t think much about it 3.5 years ago when I created the session capability. If that tells you how long before, as far as I can recall, anybody asked for such a thing.

@john-l-clark If your image was from a machine that was in BIOS mode and the media to initially install was BIOS media as well, then the image is being deployed to the HDD/SSD with BIOS partitioning and not UEFI boot partitions. In this case the UEFI/BIOS would not consider it a UEFI bootable device (as it has no UEFI boot partition). Presuming your image is whole disk and not a single partition. I have seen posts around about converting images that are BIOS to UEFI, but didnt pay much attention to them. If the process of setting up that machine with a new image isnt too much of a burden, that may be your best bet. Fresh install OS with UEFI settings/media, setup what you need and capture. Hope this helps

Our master server and one storage node is on 1.4.4 the two newer storage nodes, both having the same problem as described, are on 1.5.2 We have had issues in the past upgrading hence the mixed versions. Thanks.

@sherder For me I had similar troubles with Windows 7. I came to 2 conclusions. sysprep + unattend is very finicky. If things are not perfect you get all kinds of odd behavior. The other was that many parts of it seem to not function as they should, the computer name being one of them. The CD key is another, many sites/articles say to use 00000… or XXXXX… repeated, but mine would fail unless I put a valid key in (ended up using the Windows generic install key that MS provides on their site, doesnt activate just gets install done). Are you making your unattend by hand or using a tool to generate it? @sherder said in Windows 10 Unattend file issues: It skips the setup but doesn’t implement the changes that I put in with sed Not clear on the above, could you elaborate what you mean here? When the syspreped image boots back up, are there some things that have been applied by unattend and some that have not, or does it appear to not have applied any changes specified?

@george1421 This is just a very bad guess since I can’t test this at all. net0.dhcp/43:hex = 6010B080FAAAA03C0A802C8C0A80368C0A8016600 net0.dhcp/60:string = PXEClient I’m more confident that net0.dhcp/60:string = PXEClient will work than the the option 43 one. net0.dhcp/43:hex = 6010B080FAAAA03C0A802C8C0A80368C0A8016600 net0.dhcp/60:string = PXEClient set altiris-server:ipv4 10.96.50.15 set net0/next-server ${altiris-server} cpuid --ext 29 && set arch x64 || set arch x86pc iseq ${platform} efi && set plat efi || set plat 0 chain -ar tftp://${altiris-server}/BStrap\\${arch}\\BStrap.${plat} boot || goto MENU

Thanks a lot guys ! Let(s go updating ! :)

I follow with my problem :( I think that the best option is ask this new feature :)

@ofh I am not exactly sure if that is the right spot to find what’s wrong but that was the first thing that came to my mind. Please check and let us know what you find.

Hola @Joe-Schmitt , Both. My gold image installs the client during the sysprep and, normally, the technician uses an image with the client installed. I have other question :) If I update the server version, is necessary reset the encryption data?

@Tom-Elliott So my interface completely locked up. I restarted the server and had no luck at all getting to my interface. I ended up having to remove PHP completely and then let the FOG installer re-install PHP. My interface is back up. I have not ran any tasks yet. I’m hoping it stays up long enough to get something done.

@george1421 That is good to know, I will then probably try to update the kernel every once in a while… I currently have Win 1709 and use Proxmox, let’s hope that there will be no problems ;)

It also appears you’re missing the actual FOG-API-TOKEN header. E.G. Try: curl -H 'fog-api-token: YourFOGAPITokenHere' -H 'Content-type: application/json' -u api:password 'http://fog.home/fog/task/active' -vvv

@bretfred https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

@Sebastian-Roth Yes it does return. I even see a ton of data being downloaded. I have cut off the data towards the end due to the length of the capture. 563 13.682607 10.86.96.177 10.85.195.199 TCP 74 50514 > 8080 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=1729539897 TSecr=0 WS=128 569 13.742557 10.85.195.199 10.86.96.177 TCP 78 8080 > 50514 [SYN, ACK] Seq=0 Ack=1 Win=65535 Len=0 MSS=1460 SACK_PERM=1 TSval=400875488 TSecr=1729539897 WS=64 570 13.742594 10.86.96.177 10.85.195.199 TCP 66 50514 > 8080 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=1729539912 TSecr=400875488 571 13.742693 10.86.96.177 10.85.195.199 HTTP 161 CONNECT fogproject.org:443 HTTP/1.1 575 13.801898 10.85.195.199 10.86.96.177 TCP 66 [TCP Window Update] 8080 > 50514 [ACK] Seq=1 Ack=1 Win=771008 Len=0 TSval=400875548 TSecr=1729539912 576 13.864407 10.85.195.199 10.86.96.177 HTTP 105 HTTP/1.1 200 Connection established 577 13.864424 10.86.96.177 10.85.195.199 TCP 66 50514 > 8080 [ACK] Seq=96 Ack=40 Win=29312 Len=0 TSval=1729539942 TSecr=400875608 579 13.87112 10.86.96.177 10.85.195.199 TLSv1.2 583 Client Hello 582 13.992592 10.85.195.199 10.86.96.177 TLSv1.2 1414 Server Hello 583 13.992609 10.85.195.199 10.86.96.177 TCP 166 8080 > 50514 [PSH, ACK] Seq=1388 Ack=613 Win=771008 Len=100 TSval=400875738 TSecr=1729539944 [TCP segment of a reassembled PDU] 584 13.992616 10.86.96.177 10.85.195.199 TCP 66 50514 > 8080 [ACK] Seq=613 Ack=1488 Win=32128 Len=0 TSval=1729539974 TSecr=400875738 585 13.992893 10.85.195.199 10.86.96.177 TCP 1414 8080 > 50514 [ACK] Seq=1488 Ack=613 Win=771008 Len=1348 TSval=400875738 TSecr=1729539944 [TCP segment of a reassembled PDU] 586 13.992908 10.85.195.199 10.86.96.177 TCP 166 8080 > 50514 [PSH, ACK] Seq=2836 Ack=613 Win=771008 Len=100 TSval=400875738 TSecr=1729539944 [TCP segment of a reassembled PDU] 587 13.992916 10.86.96.177 10.85.195.199 TCP 66 50514 > 8080 [ACK] Seq=613 Ack=2936 Win=35072 Len=0 TSval=1729539974 TSecr=400875738 588 13.992928 10.85.195.199 10.86.96.177 TLSv1.2 640 Certificate, Server Key Exchange, Server Hello Done 589 13.995298 10.86.96.177 10.85.195.199 TLSv1.2 192 Client Key Exchange, Change Cipher Spec, Encrypted Handshake Message 593 14.114585 10.85.195.199 10.86.96.177 TLSv1.2 117 Change Cipher Spec, Encrypted Handshake Message 594 14.114752 10.86.96.177 10.85.195.199 TLSv1.2 182 Application Data 598 14.237584 10.85.195.199 10.86.96.177 TCP 1414 8080 > 50514 [ACK] Seq=3561 Ack=855 Win=771008 Len=1348 TSval=400875988 TSecr=1729540005 [TCP segment of a reassembled PDU] 599 14.237599 10.85.195.199 10.86.96.177 TCP 166 8080 > 50514 [PSH, ACK] Seq=4909 Ack=855 Win=771008 Len=100 TSval=400875988 TSecr=1729540005 [TCP segment of a reassembled PDU] 600 14.237607 10.86.96.177 10.85.195.199 TCP 66 50514 > 8080 [ACK] Seq=855 Ack=5009 Win=40704 Len=0 TSval=1729540036 TSecr=400875988 ...... ..... .... ...

@tom-elliott Thank you, I will follow the step and let you know if I run into problems. Tom

What goes wrong with your storage node? What are you trying to accomplish? Deploy from different storage nodes in different locations? (read up on location plugin if you haven’t already)

OU Drop Down option is kind of confusing to setup, but it does work. Each OU is separated with a | The “default” OU is marked with a ; at the end. What this means is: OU1|OU2;|OU3|OU4 Will create a dropdown of: OU1 OU2 OU3 OU4 with OU2 being the default selected one. Hopefully this helps. Mind you all this is is a dropdown, you still have to make the choices and update the hosts/groups in question for this to apply.

Here is what my unattend.xml looks like. I have made some redactions and comments to help out. I made mine using Windows System Image Manager. This is one of many webpages I used to learn about building my unattend file (and lots of trial and error): https://www.tenforums.com/tutorials/3020-customize-windows-10-image-audit-mode-sysprep.html <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="specialize"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <ProductKey>Your key</ProductKey> <TimeZone>Your TimeZone</TimeZone> </component> <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <!--I had to add this as FOG wasn't expanding my OS partition all the way after OOBE ran--> <ExtendOSPartition> <Extend>true</Extend> </ExtendOSPartition> </component> </settings> <settings pass="oobeSystem"> <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <InputLocale>en-US</InputLocale> <SystemLocale>en-US</SystemLocale> <UILanguage>en-US</UILanguage> <UserLocale>en-US</UserLocale> </component> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <OOBE> <HideEULAPage>true</HideEULAPage> <HideLocalAccountScreen>true</HideLocalAccountScreen> <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen> <HideOnlineAccountScreens>true</HideOnlineAccountScreens> <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE> <ProtectYourPC>1</ProtectYourPC> </OOBE> <UserAccounts> <!--If you skip account creation in OOBE, you need to enable local Administrator account or create another admin account in unattend file --> <AdministratorPassword> <Value>Your AdministratorPassword==</Value> <PlainText>false</PlainText> </AdministratorPassword> </UserAccounts> <StartTiles> <PromoteOEMTiles>false</PromoteOEMTiles> </StartTiles> <AutoLogon> <Password> <Value>password again</Value> <PlainText>false</PlainText> </Password> <LogonCount>1</LogonCount> <Username>Administrator</Username> <Enabled>true</Enabled> </AutoLogon> <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <CommandLine>reg add &quot;HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon&quot; /v AutoLogonCount /t REG_DWORD /d 1 /f</CommandLine> <Description>Set AutoLogin count back to zero</Description> <Order>1</Order> <RequiresUserInput>false</RequiresUserInput> </SynchronousCommand> </FirstLogonCommands> </component> </settings> <settings pass="offlineServicing"> <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DriverPaths> <!--If you are using the postdownload script for driver injection, you will need this --> <PathAndCredentials wcm:action="add" wcm:keyValue="1"> <Path>C:\Windows\DRV</Path> </PathAndCredentials> </DriverPaths> </component> </settings> <!--don't think the offline image part is needed, but it's part of the one that get's made when I use Windows System Image Manager --> <cpi:offlineImage cpi:source="source" /> </unattend>

@sarge_212 Once you have the git repo locally then when fog 1.5.3 is released you can follow my initial instructions about git pull to download the updates.