Create UEFI ISO and prepare Surface go deployement.
-
@TheDiskDrive What does your storage node settings look like? Please post screenshots here.
-
Here the screenshot, i’m using the default storage node.
the only thing i have changed is the Image Path and FTP Path
-
@TheDiskDrive Username and Password shouldn’t be empty and definitely are not by default!
-
i’m using the default username and password, they are removed for the screenshot.
-
@TheDiskDrive Re-reading the whole topic I think I have missed an important part. Just can’t keep all the details of all the different posts in my head. So let’s go back a few steps.
Okay i think i have found why i can’t use the task “deploy” on a group of computer.
For some reason there no storage node being used.I am not sure why but seems like this is normal. I just tried a multicast deploy on my test system and this table column is empty for me as well. I am fairly sure this is not what is causing the issue for you. See what George posted earlier.
@george1421 said in Create UEFI ISO and prepare Surface go deployement.:
Originally this wasn’t possible. I think there was some kernel parameter changes that now make it possible. I have not tested this feature as of now.
The USB boot stuff is not a fully official part of FOG and therefore we might not have noticed that multicast is not working using that. @george1421 would you have the chance to give it a try and see if it fails for you as well. If so I will have a closer look and try to fix it.
-
@Sebastian-Roth said in Create UEFI ISO and prepare Surface go deployement.:
The USB boot stuff is not a fully official part of FOG and therefore we might not have noticed that multicast is not working using that. @george1421 would you have the chance to give it a try and see if it fails for you as well.
I think it should be possible since the session name is no longer needed. Getting the session name in grub menu wasn’t possible. That is why it didn’t work before. I can test when I’m back in the office. I’m currently on holiday so I don’t have any tools to test at the moment.
-
@Sebastian-Roth said in Create UEFI ISO and prepare Surface go deployement.:
@TheDiskDrive Re-reading the whole topic I think I have missed an important part. Just can’t keep all the details of all the different posts in my head. So let’s go back a few steps.
Okay i think i have found why i can’t use the task “deploy” on a group of computer.
For some reason there no storage node being used.I am not sure why but seems like this is normal. I just tried a multicast deploy on my test system and this table column is empty for me as well. I am fairly sure this is not what is causing the issue for you. See what George posted earlier.
Is not about multicast deploy but the “Deploy” task, here is my issue
I go to a group of computer then i click on basic task and select deploy task
here is a list of 10 computer from the group
When i launch the task and watching task progression ( in task management section) no working node is used but when i create deploy task to ONE computer ( the first computer named GEII) the defaultMember node is used
When i’ve installed fog on my debian server i’ve changed the path in the Storage node settings to use my 1 tb virtual disk and moved all the data from the default path to my 1tb drive (/data on /dev/sdb)
By the way i have deployed all my tablets, deployement took 5 minutes per machine. Now i want to understand where i’m wrong
-
@TheDiskDrive Thanks for the detailed pictures and explaination. I’ll try to replicate the issue. Won’t be this week but I won’t forget!
-
@TheDiskDrive I have looked into this again and I am still not sure I really get this. You said:
i’ve tried the deploy task to a 10 tablet group and this is not working i have this following error:
Invalid storage groupWhere/when exactly do you get this error message? Please take a picture of the error on screen and post here!
When i launch the task and watching task progression ( in task management section) no working node is used
As I said before, the empty column in the web UI is not causing the problem from my point of view. I have just done another test and it deploys perfectly fine on my test systems.
-
Just for the notes: I pushed a fix for populating the “Working with node” column properly. But still I don’t think this is causing @TheDiskDrive’s issue. Please post a picture of the error you see and we should be able to help.