@Jaymes-Driver Reminds me of my time in the Army.

Particularly

NCO Creed
No one is more professional than I. I am a noncommissioned officer, a leader of Soldiers. As a noncommissioned officer, I realize that I am a member of a time honored corps, which is known as “The Backbone of the Army”. I am proud of the Corps of noncommissioned officers and will at all times conduct myself so as to bring credit upon the Corps, the military service and my country regardless of the situation in which I find myself. I will not use my grade or position to attain pleasure, profit, or personal safety.

Competence is my watchword. My two basic responsibilities will always be uppermost in my mind—accomplishment of my mission and the welfare of my Soldiers. I will strive to remain technically and tactically proficient. I am aware of my role as a noncommissioned officer. I will fulfill my responsibilities inherent in that role. All Soldiers are entitled to outstanding leadership; I will provide that leadership. I know my Soldiers and I will always place their needs above my own. I will communicate consistently with my Soldiers and never leave them uninformed. I will be fair and impartial when recommending both rewards and punishment.

Officers of my unit will have maximum time to accomplish their duties; they will not have to accomplish mine. I will earn their respect and confidence as well as that of my Soldiers. I will be loyal to those with whom I serve; seniors, peers, and subordinates alike. I will exercise initiative by taking appropriate action in the absence of orders. I will not compromise my integrity, nor my moral courage. I will not forget, nor will I allow my comrades to forget that we are professionals, noncommissioned officers, leaders!

I referenced this in my other post, but this fixed my issues as well. Thanks!
https://forums.fogproject.org/topic/6536/windows-10-after-upload-partition-erased/11

@KKTwenty101 I finally got this to work by updating the bios on my marvel/yukon nic machines.
PXE took off immediately afterwards. Just an option to try.

well as far as “stable” goes ive been using build 5370 for 3 months. Ive rolled out a couple of hundred windows 8.1 images - all of which are unattended from lan boot -> AD joined “ctrl-alt-del” screen (I use snappydriver via a script on OOBE boot).

I guess later trunk have other fixes but since that build worked for me (and works for me) I have no reason to update yet. I’d give trunk a test in your lab and decide for yourself; it is a world away from 1.2 - if only for the speed increase (not quite double the speed but I’d be surprised if you don’t notice it)

@Wayne-Workman
Hi Wayne, sorry been running around abit here lately for the mounting i am using nfs and in the exports:
/images *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure,fsid=1)
Hopefully helps others out.

@Tom-Elliott well done,
works like a charm.
Regards

@Wayne-Workman Thank you! I will try to convert the batch to an .exe file.

@Tom-Elliott Added here: https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#Maintain_Control_of_hosts_when_building_new_server

@EAHarvey Several programs have found no issues with the drive.

@Wayne-Workman Cannot do this right now as I only have 1 netbook in my Office but will give it ago when I can.

Anyone else have an idea why I get this error when trying to deploy an image? https://forums.fogproject.org/uploads/files/1452520756237-error.jpg

Thanks again.

@Wayne-Workman Thanks for that pointer, that will definitely help in getting started in this. I am learning how to do simple sql queries in PS and VBscript to try and accomplish this but none of them would work without this part.

@cbemerine https://forums.fogproject.org/topic/1341/requests-for-wiki-access-ask-here/107

Everything is working for me now! hooray for the new inits!

Future readers, please see: https://forums.fogproject.org/topic/6435/multicast-start-button-please

@Tom-Elliott said:

There is a time limit and the number of hosts to start.

I set ours to 5 minutes.
The setting is located here in FOG Trunk (pre FOG 1.3.0):
FOG Configuration -> FOG Settings -> Multicast Settings -> FOG_MULTICAST_MAXWAIT

0_1452188799247_upload-efe48a0b-9fdc-486f-a53f-9de0129aaf71

@Jbob It’s compatible with Windows 8.1

@hugothebas This article applies to 1.2.0 and below: https://wiki.fogproject.org/wiki/index.php?title=Advanced_Boot_Menu_Configuration_options

@Wayne-Workman It will replicate to the other nodes.

@Wayne-Workman Good catch! I had exactly this in mind when I said that we had issues with empty disks with fogpartinfo. The new method (using lsblk) should work on empty disks. Would be interesting if someone could test this as well. Easiest would be to boot an unused client into debug mode. Then use the dd command from KKTwenty101’s posting to “murder the partition table”. After that try deploying (using the init files I posted) to that client.

@Jbob said:

@mrayzies not a problem. To answer those questions:

Yes, the client installs your servers’ certificate and ours. The “FOG Project” CA (made by us) servers 2 purpose. SYSTEM level services need to be digitally signed otherwise windows will throw security errors (I have seen this issue when imaging a machine with an unsigned client). This can also be used to ensure no tampering was done with the client files That certificate is used to “verify” upgrades. Lets say we release v0.9.10, the client will download the msi from your server and check if it was signed by us. If the msi was somehow tampered, the digital signature would no longer be valid. Using HTTP over HTTPS has no security benefit to the client. Why? Because all traffic is already encrypted. Here’s a very basic overview of how the new client communicates Each client has a security token. This is used to prove to the server that the client is the actual host and not an impersonator. This token gets cycled constantly. When the client first makes contact, it encrypts its token and a proposed AES 256 key using RSA 4096 using your server’s public key. (This public key is verified against the pinned server CA certificate by checking the x509 chain and fingerprints). If the server accepts the security token and the new AES key, all traffic from that point on is AES 256 encrypted using that securely transmitted key.

The whole point of our security model is to allow for secure communication over insecure medians.
Even then, the client installation has an HTTPS option, but it serves no real security benefit.

This stuff and a little other stuff has been added here:
https://wiki.fogproject.org/wiki/index.php/FOG_Client#Security_design

Added here:
https://wiki.fogproject.org/wiki/index.php/Advanced_Boot_Menu_Configuration_options
and here:
https://wiki.fogproject.org/wiki/index.php/Include_any_ISO_in_the_FOG_Bootmenu