Posts made by The Dealman

@george1421 Yes it is usb-c. It’s one of these https://www.dell.com/en-us/work/shop/dell-docking-station-wd19-180w/apd/210-ariq/pc-accessories

@george1421 No spanning tree enable on this network. Here is the Hardware ID info

https://drive.google.com/file/d/1N-_V4eoJUOzo-CSwcoG_jS6aIb3jGcpN/view?usp=sharing

@george1421 I ran the dhcp net0 command and i saw a bunch of … then it said ok. So i did ran a ifstat again and it show the same result as the below screen shot. Should i see the assigned ip in the ifstat results?

https://drive.google.com/file/d/1-KLaPigNOP1cxXC1aO3oXLf7oAoooWfL/view?usp=sharing

@george1421 said in Dell 7000 series laptops pxe booting:

ifstat

Here is a screen shot of the ifstat results from the client computer

https://drive.google.com/file/d/1-KLaPigNOP1cxXC1aO3oXLf7oAoooWfL/view?usp=sharing

@george1421 Yes the FOG server is on the same subnet as the target computer. When i hit the S at the iPXE command prompt after the time out i did get to the command prompt. I pinged the ip of the FOG server and i get connection time out over and over again

@george1421 Yes that would have been the IP of the FOG server so it sort of worked but timed out.

@george1421 I tried the ipxe.efi file and that didn’t seem to work either. I have included the screen shot below

https://drive.google.com/file/d/1tHFGw6wMRJezyaBG0Th24HrOIbwZUMC0/view?usp=sharing

@george1421 Okay. I will give that a try today and report back the results.

@Sebastian-Roth I used the undionly.kpxe file. Should i be using the ipxe.efi? I never used that one.

ubuntu 16.04
FOG 1.5.8

It seems like the Dell 7000 series laptops are very difficult to get pxe booting to work with the docking stations. I have dell latitude 7220 and 7410’s that will not successfully go through the pxe boot process. I don’t even get an error message, we have tried

• Installing firmware version from DELL Support
• BIOS Settings General --> Advanced Boot Options --> Enable UEFI Network Stack
• System Configuration -> Thunderbolt Adapter Configuration --> Enable Thunderbolt Boot Support, Thunderbolt and Enable Thunderbolt (and PCIe behind TBT) Pre-boot Modules
• POST Behavior --> Fastboot --> Set to Thorough
• Secure Boot --> Disable (uncheck) Secure Boot Enable

and nothings seems to work. It’s almost like if the network interface isn’t built-in to the laptop it’s going to be a problem with the pxe boot process. Has anyone encounter this and if so what was the fix?

Here is a link to the video of what i see https://drive.google.com/file/d/1dLLI1hl24JkaxkyATjYQfWJeX3GroHRK/view?usp=sharing

@Fernando-Gietz Okay I got it working. You guys are awesome keep it up!

@Fernando-Gietz Okay i’ll give it a try and report back once i get to the office today.

@Sebastian-Roth I was able to locate this but it’s kinda hard to tell where you are when you drill down into the role and you want to modify rules. Once I jump into the rules I can’t tell if i’m looking at the rules for just the role I created or if it’s all the default rules for all the roles, it feels like it should be some sort of bread crumb trail on the UI to indicate where you are at the time. Also I deleted the printers from the access control rules main menu as a test and it still shows up at the top menu bar, we are suppose to delete the access control rules we don’t want to show up right?

I hadn’t tried to do this sort of architecture before, I took the easy road and built a normal server at each site and manually replicated the image. Anyway I found the setting, thanks Tom.

I’ve setup a normal server using FOG 1.5.5 at our main office and storage nodes running FOG 1.5.5 at each of the remote sites that are few miles apart and I have an image replicating to the storage nodes. I’ve noticed that when imaging at the main office for example, it seems like the image may have been coming from one of the storage nodes instead of from the normal server that is located at the main office. I believe i saw this in tasks management under the working with node column, is there anything that can be done to make it so that client machines only image from the local server at the physical location?

@Sebastian-Roth I’m using 1.5.5 of FOG on all servers.

@Sebastian-Roth Nope. I didn’t know one existed, where is this located?

It would be great if we had some sort of RBAC functionality built into fog, it doesn’t need to be anything complex. My use case is that I have central office IT staff that will have full access to fog, but I have computer technicians at schools that I only want to be able to image computers and not to have access to the web interface. Can this be done?

@george1421 Yeah it looks like by adding this to the xml file cscript /B C:\windows\system32_slmgr.vbs /ato resolved it on my machines. Thanks for the help.

@george1421 Can post a sanitized version of your unattended.xml file? I’m not sure what i should have in it to tell the workstation to find the kms server