You may start looking into Ansible, version 1.7 or greater comes with ability to control windows clients.
http://docs.ansible.com/ansible/intro_windows.html

And ansible is free (I think), but Ansible Tower costs.

@Tom-Elliott
OK.
Well, I think I figured it out. I may have missed updating the storage node info. The graphs/pie charts are back working now.

Setup capture and is working. Ugh. the one thing I didn’t double check after it all. Being that its the only storage node I didn’t think to check it again.

Thanks for all of y’alls time. sometimes it just needs more eyes and a better understanding of how this works. Y’all have a great day. I need a beverage.

thanks,
Jason

@alansopro There is indeed a new fog client, though the old one is there as a just in case but probably has its own set of issues. Besides, I HIGHLY encourage all people to use the new client. It’s much faster and less taxing on the FOG Server. While the old client wasn’t overly rough (after its initial load up) it still had it’s own issues to think/worry about.

@george1421 Ah this makes sense. My colleague notified me he uploaded an image and it didn’t seem to finish the task. That is when I noticed the disk was full. Got it.

Can you show us the logs verbatim then? You’re not seeing the exact same error if it’s not saying ‘ftp_login incorrect’

@george1421 It works ! Thanks for your support 🙂
edit : Yes I’m running dnsmasq.

Crosslinking related threads:
https://forums.fogproject.org/topic/8189/power-management-scheduled-shutdown-flakey

@fry_p Excellent job. What you posted is exactly what I would have had you do.

Just keep in mind that this is only likely to work with the exact sub-model, the one you said: Surface Pro 4 1724

For future readers, all that’s needed to make a vendor class for other sub models is a packet capture posted here on the forums, or analyzed by yourself. Simply look at the device’s DHCP Discover packet, inside option 60 you’ll find the vendor class identifier.

@Wayne-Workman using FOG 1.2.0, however after uploading the image a second time everything is now working correctly.

Cheers

@phishphan said in HP ZBOOK15U G3 - Host Registration Problem:

I ask because once I have my captured image I move it to another drive for archival.

You should automate that with a cron task and scp or rsync.

@Wayne-Workman Ok.

That what i did and then i re-ran the installer and it worked. Thank You!!

@Tom-Elliott said in Upload Task: Updating database... failed. FTP problems:

@zachu THe reason the path is specified (not allowing slashes) is because it can give access to other parts of the filesystem. This doesn’t mean it WILL happen, but from a security perspective what’s to ensure you don’t write a specific file or overwrite the root folder? I know there’s some other obfuscated methods of protection here, but let’s just imagine, you decide to put the image path be be as /images/../../../../bin/init or /images/../../../../usr/bin/init or some other binary name.
While technically it shouldn’t be possible, with the wrong setup it is a possibility. Now your fog server will likely work for a while. Then start having some funny issues.

I perfectly understand why it’s like this. I was more like toying with different ways to go around the problem I had. I’m ok with the way it works now.

The Wiki is perfectly accurate. You would, essentially, change the images location to go from /images to /images/newdisk. No where in the wiki article, from what I’ve skimmed through, would state that you are placing the image on the disk in the way you originally described. Changing the way move_upload is not quite that simple.

Oh right, I think I then read too far there between the lines. With the guide on the wiki article’s last lines, it’s meant to move all your images under the “newdisk”, not just one or part of them. I get it now 🙂

Changing the way move_upload is not quite that simple.

Yeah, I glanced just quickly at the codebase there and realized that it isn’t just a minor change, but I think it is doable still. All the needed actions are moving (renaming) and deleting files and folders, just as it is done now. Now it’s really simple and pretty when you can just move the whole directory instead of doing multiple actions to the files.

Would you accept a pull request of changing the move_upload process, if I find time to put it together? I’m not making any promises, but just thinking about it. I’ve never really contributed to an open source project but I might have the skills to put that one together. But if it fights the way you want it to work, then I wont bother 🙂

I really thank you for your time!

Btw, I settled for a process that I just move the image files to the dedicated HDD always after upload. It’ll do now, since it’s only temporary 🙂

For future readers:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_NFS

@Joe-Gill Well, I suppose the first thing to try is this group that failed - but by itself, without other multi-cast tasks running. See what happens.

Since this issue isn’t really related to FOG, I’ll mark it as solved.

OK reinstalled the FOG sever again (over itself) and everything seems to have ironed itself out. I had to basically install it twice. But everything seems golden. Back to Windows 10 on a Surface image. Thank you guys.

I also added it to the wiki.
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Hosts_think_they_are_not_registered_.2F_can.27t_register_.2F_other_weirdness

@spetzmax

We are requesting that all community members who have Surface Pros to please do a packet capture, to capture the DHCP conversation the client sends out at boot time via the ethernet dock, and upload the capture here. The intent is to gather more information about the Surface Pro, so fog can better support network booting it.

Thanks,
Wayne

@Scott-Adams

We are requesting that all community members who have Surface Pros to please do a packet capture, to capture the DHCP conversation the client sends out at boot time via the ethernet dock, and upload the capture here. The intent is to gather more information about the Surface Pro, so fog can better support network booting it.

Thanks,
Wayne

@dustindizzle11

We are requesting that all community members who have Surface Pros to please do a packet capture, to capture the DHCP conversation the client sends out at boot time via the ethernet dock, and upload the capture here. The intent is to gather more information about the Surface Pro, so fog can better support network booting it.

Thanks,
Wayne