Chrome detects the cert as valid for me. Most likely they’re using a shared SSL certificate, which means it should work on any domain that is structured *.fogproject.org

@mandrade I would advise trying a different USB NIC, it seems like this one isn’t working properly given that it cannot read the device descriptor properly.

Unless… is this being plugged into a USB3 port? If so, try a USB2 port.

@Abuelika Looking a lot better already, I can’t spot an error right now, just information about its boot process. Does it stop there when you try to image? Or does something else happen/show up?

@Erwan It sounds like what you need is two different storage groups, with each node in a different group.

If I understood Tom correctly, the trunk version of FOG can replicate images between different storage groups, allowing image captures in different locations to be replicated to the master node of the other group (which then replicates it to the nodes in its group).

It sounds like that’s what you need for your situation.

@Twilems http://www.linuxgfx.co.uk/karoshi/documentation/wiki/index.php?title=Creating_a_Windows_10_Mandatory_Profile might help.

Basically you need to alter the registry key permissions and ownerships of the default ntsuer.man

@Abuelika You might want to update the BIOS of the Z400 and see if that helps, latest BIOS dates from April this year and fixed a couple of issues with certain CPUs.

http://h20564.www2.hp.com/hpsc/swd/public/readIndex?sp4ts.oid=3718669&swLangOid=8&swEnvOid=4059

@Tom-Elliott TIL xcopy has internal error codes, that’s very useful.

@Scott-Adams

xcopy /e “\\x.x.x.x\WES_Apps\Technology\Beyond Question\Beyond Question” “C:\%programpath%\Beyond Question”

should be

xcopy /e "\\x.x.x.x\WES_Apps\Technology\Beyond Question\Beyond Question" "%programpath%\Beyond Question"

Since %programpath% will include the drive letter already as inherited from %programfiles(x86)%

Please test the batch file manually to confirm.

#Edited to add backticks so we can properly see the command.

@Erwan All of this points to the credentials under your student node being incorrect. Seeing as everything else works exactly as expected and the principle works with the default node, it’s the only option left, really.

Try entering it again manually and see if that resolves it.

I believe the error codes are general windows error codes (correct me if I’m wrong)

In which case it’s

ERROR_TOO_MANY_OPEN_FILES
4 (0x4)
The system cannot open the file.

https://msdn.microsoft.com/en-us/library/windows/desktop/ms681382(v=vs.85).aspx

Which of course isn’t particularly helpful on its own.

@Erwan You mentioned in your post that when you changed only the IP of the teacher node it worked. Does this mean you did not alter the interface?

@michaeloberg I’m guessing it ran out of IP addresses to hand out?

@Abuelika Which imagetype did you try?

You likely filled in the wrong credentials for the student storage node. (the fog ftp password at the working storage node by clicking on the reveal password thingy)

It is not the same as the webGUI login. (maybe you know this, but a lot of people get confused by the different credentials being used) It is automatically generated by FOG upon install.

Seeing as you have not modified the credentials of the working node, this seems like the most likely scenario, please check and confirm/deny this.

I am guessing you are on FOG 1.2, in regards to your question about the storage interface options. The image is of the newest version, which is continuously being updated. You can search the wiki for installing trunk if you’re interested in that (many people here use it in production environments).

Images are not replicated across different storage groups.

They’d have to be part of the same storage group to replicate them. FOG uses FTP to move the images as far as I know, so different subnets are no problem for replication.

Did you follow the wiki for the install?

My first guess would be SELinux still being enabled.

@mandrade In the mean time, if you have custom menu entries it might be worth trying to load for example an ISO and see if that gets any further.

I’ve had a few devices that wouldn’t get far with the downloading of files in PXE, not sure if (and how) I resolved that, though.

Just for clarity sake as well, which binary are you currently using?

Seeing as the NIC is Realtek, it might be worth testing with Realtek.kpxe if you aren’t already.

edit: Also, seeing as it’s a USB NIC, it might be worth checking out the USB settings in BIOS, particularily those related to XHCI handoff and see if that helps any.

@kickers56 Is it possible they altered something behind the screens concerning AD?

@kickers56 Sounds like permission issues to me. That’s generally what Access Denied leads to anyway.

I’m curious why it was looking for access when it already states the hostname to be correct already, though.

Resize doesn’t work for Apple partitions, it’s not a “validResizeOS”

You have to use one of the unresizable image types.

Perhaps an idea for the devs is to simply hide the resizable option for OS it won’t work for anyway?