Good to know. Thank you!

Celebrate your vestigial umbilical cord!

Is it?

• rename
• reboot
• join the domain
• reboot

… or is it?

• rename
• join the domain
• reboot

Does it call a Windows native command or use some other method?

The legacy client required that netdom.exe exist in a path designated in the .ini , which then also required pulling netdom.exe from the waik.

Does it call a Windows native function or do it some other way?

Boy does this thread sound familiar

I have access to everything.

Routers and firewalls at every site. Multiple vlans at every site.

This is why a storage node solution won’t work for us. That’s a lot of hardware overhead especially with 80+ sites.

We do not want centralized management of the fog server/nodes. Physical boxes at high schools, and portable virtual boxes for smaller sites used by 8 + 5 field technicians to service their schools. Techs must have the ability to capture their own images as well. Many images are restricted to their sites.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
CentOS_7.2.1511 - Install Minimal Server +20161005

• This is a MINIMAL (CORE) installation intended solely for a FOG Server role
• The resulting image can be deployed to any virtual or physical hardware
• https://wiki.centos.org/FAQ/CentOS7

=-=-=-=-=-
For a Physical FOG Server

i.	Flash & Program System BIOS for ODD Boot
ii.	Install HDD #1 (120+ GiB & zeroed) on first controller port
iii.	Install ODD #1 on last controller port
iv.	Insert CentOS-7-x86_64-NetInstall-1511CD

=-=-=-=-=-
For a Hyper-V Virtual FOG Server

i.	Create a New Virtual Machine: <Name of Choice>, Generation 1, 512MB Dynamic Memory, Onboard Network, Create a virtual hard disk
ii.	Boot from CD
iii.	Maximum RAM 2048MB
iv.	1 Virtual Processor
v.	DVD Drive Image File: "CentOS-7-x86_64-NetInstall-1511.iso"
vi.	REMOVE: SCSI Controller
vii.	Automatic Start Action: Nothing

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
01> Install CentOS_7.2.1511

• Start Machine
• Install!

@ CentOS 7

• Install CentOS 7.2.1511

@ What language would you like to use during the installation process?

• English (Canada)
  = CONTINUE

@ Installation Summary

/ Network & Host Name

• Ethernet (eth0) = ON
• Host Name = “centos7”
  = DONE

/ Date & Time

• Americas + Toronto
• Network Time = ON + Configure + OK
  = DONE

/ Installation Source

• On the network = “http://mirror.centos.org/centos/7.2.1511/os/x86_64/”
  = DONE

/ Software Selection

• Minimal Install
  = DONE

/ Installation Destination

• I will configure partitioning
• Checkmark <Msft Virtual Disk>
  = DONE

@ Manual Partitioning

• New mount points will use the following partitioning scheme = Standard Partition

• Add Mount Points

/sda1
Mount Point: /boot
Desired Capacity: 500 MB
Device Type: Standard Partition
File System: xfs

/sda2
Mount Point: swap
Desired Capacity: 2 GiB
Device Type: Standard Partition
File System: swap

/sda3
Mount Point: /
Desired Capacity: 20 GiB
Device Type: Standard Partition
File System: ext4

@ Summary of Changes
= Accept Changes

@ Installation Summary
= Begin Installation

@ Configuration

/ Root Password

• “… root password …”
  = DONE

/ User Creation

• Full name = administrator
• Username = administrator
• Make this user administrator
• Password = “… administrator password …”
  = DONE

@ CentOS is now successfully installed …

• Reboot (.ISO is ejected)
• system restarts

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
02> Determine IPv4 Address

• Login via CONSOLE

ip addr
exit

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
03> Update OS & Recompile Kernel

• Login REMOTELY with Kitty ( http://kitty.9bis.net/ )
• Elevate Access Level

sudo su

• Disable access via SSH for root account

sed -i "s|#PermitRootLogin yes|PermitRootLogin no|g" /etc/ssh/sshd_config
systemctl restart sshd.service

• Direct next Kernel recompilation to include AHCI drivers & be HW generic

sed -i 's|#add_drivers+="|add_drivers+="ahci|g' /etc/dracut.conf
sed -i 's|#hostonly="yes|hostonly="no|g' /etc/dracut.conf

• Clean & Update the OS (includes Kernel recompilation)

yum clean all
yum makecache
yum update -y

• Clear history of typed commands

history -c

• Shutdown

shutdown now

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
04> End of Minimal CentOS_7.2.1511

• Add Legacy Network Adapter
• Set Legacy Network Adapter, Virtual Switch: Onboard
• Set BIOS Boot to Legacy Network Adapter

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
05> Export and Capture from here

• Export VM
• Capture via FOG (Linux, Single Disk - Resizable, Compression=3)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Continues at How I Create a Ready-to-Deploy FOG Server git1.3.0-RC-10_svn5955 on CentOS 7.x VM

While I build out a new csv solution, we’re now looking at the site firewalls to see if we can create a static entry on each there instead.

With a site like above, with 5 subnets, how many storage nodes would I need?

M2CW, I have just successfully installed “1.3.0-RC-4” on a CentOS 7.2.1511 Minimal Install that I compiled on 2016/07/15.

I then reverted that VM and updated the OS:

yum clean all
yum makecache
yum update -y

Pulled these updates:

libwbclient.x86_64 0:4.2.10-7.el7_2
samba-client-libs.x86_64 0:4.2.10-7.el7_2
samba-common.noarch 0:4.2.10-7.el7_2
samba-common-libs.x86_64 0:4.2.10-7.el7_2
samba-common-tools.x86_64 0:4.2.10-7.el7_2
samba-libs.x86_64 0:4.2.10-7.el7_2

“1.3.0-RC-4” still installed without issue.

That would work great if I had only a single subnet at each site, just create a Host (A) record named fog-server, with the IP address of the server into the forward lookup zone, but I don’t.

I have a minimum of 2 subnet/vlan/scopes at each site now and soon that will be 5 minimum per.

VlanA = SubnetA > Contains clientsA, FogA, fog-server Host (A) for FogA
VlanB = SubnetB > Contains clientsB
VlanC = SubnetC > Contains clientsC
VlanD = SubnetD > Contains clientsD
VlanE = SubnetE > Contains clientsE

A Host(A) record named fog-server for subnet A will not help clients in BCD or E.

Now I’m not a DNS magician, but I don’t see a DNS option for my scenario. So I’m still left sniffing through a csv of the DHCP Scope dump at first boot.

I think I just answered my own question on a test box.

The testbox is registered with fog1.

I changed the “Server”: setting in testbox’s settings.json from “fog1” to “fog2” .

I changed the name of the testbox in fog1, and nothing happened.

In the testbox fog.log it clearly states that it cannot authenticate with “fog2”

Fog1 and Fog2 have different certificates at this time.

According to @Wayne-Workman in my thread The tale of two client programs the server name is entirely irrelevant to the key data that is saved to the client, and the name is only used to direct the installer to where to fetch the key from.

Then why do I see the file settings.json with the name of the fog server I used for the installer?

If I:

• use the same certificate on all my Fog servers.
• install the new client onto an image by pointing the installer to serverA.
• then deploy that image onto machineB registered on serverB, will machineB want to talk to serverA or will it happily show on serverB instead and only?

In the legacy client, we script-edited the file config.ini to replace the value for ipaddress with the server IP of the site upon the client’s first bootup ; must I edit this .json file similarly?

@george1421 Domain work is a no-brainer. It’s the workgroup solution that I’m trying to simplify.

I wish my scope comparison was that simple. My current end-of-sysprep solution determines the correct server for the legacy client in our current 80+ subnets with two dozen servers. One subnet’s server just changed which broke the script for that site.

But pucker up. We’re planning out 500 new scopes …

My experience tells me that the more external steps involved the less likely it to succeed when it must be performed by Level 1 field techs. Even when it was Ghost Suite that was being used, the interface can be overwhelming to some for even that seemingly simple function.

I’m looking for an exceedingly simple or push-button solution.

@Joe-Schmitt What if the heartbeat responder was password protected ?

Also consider KMS VL Activator formerly known as the KMS Client Emulator.

There is no record of the machine in FOG. It has never seen FOG. Virgin …