Topics created by John Sartoris

I don’t have the ignore mac on client/imaging
Setting built in to those functions, but you can take a peek at the code to see whrte you are setting the primary property there is also a property for ignoring mac on client. I’m on my phone at the moment so can’t go test and get for sure answers. But it’s either a part of thr maclist array of a host or a different property. Point is you can for sure set that. If you give me a bit more detail I will gladly try to give you further examples on how to do it with the powershell module

@John-Sartoris Sorry for the long delay. Took me a while to get other things done and find the time to look into this. I have not played with this myself and so I needed some time.

The topic linked mentions the Task State plugin (named taskstateedit). You need to enable/install it as a first step. Then define new task states that you want to have manually.

I have not been able to fully replicate the update of task states using the mentioned URL yet but I suppose we can figure this out if you are still keen to get this work. Let us know if defining the new states manually is something you consider to be usable in your case. I don’t think there is any other way. You can’t just call the URL as ...&stateid=This%20is%20my%20new%20state sort of thing.

I’ve updated to 1.5.9-RC1 after a bit of work, I think I’ve gotten everything working now.

I have my Public signed wildcard cert working.

I’ve got ipxe configured to Trust the godaddy root cert. This was important as our content filter was again blocking what I think to be the validation attempts. This time it was not showing up as OCSP, but simple “web-browsing”.

edited /tftpboot/default.ipxe to use hostname, and added parameter to change screen resolution. Some of our newest machines have 4k monitors that make the menu tiny.

And lastly, Replication services, Image and Snapin, both are working. It final magic seems that the Replication services use “Fog Configuration -> Fog Settings -> Web Server -> Web Host” and cross reference it to the StorageNode names. It then takes the IP address and Interface configuration from there to determine if the nic is “UP”. It seems DNS resolution is not done on the IP address field here. I had the names and not the actual IP addresses. After setting “Web Host” to the FQDN, and adjusting the StorageNode name to match, and setting the StorageNode IP to the ip, and finally restarting the replication services, things started to all work. Sorry, that one was wordy.

@Sebastian-Roth Thanks for your help. I’ll post new topics if I find anything 1.5.9-RC1 related.

@john-sartoris Hmm, seems they’ve switched back and forth between the two on several occassions, bah.

@Wayne-Workman I would love to 😃
However I would wait until I have finished my current project of using fog to upgrade all clients to windows 10 so that this method is more thoroughly tested first.
It’s tested, but not thorough and I will likely make some changes to my image prep script along the way. Then making it a wiki article will pretty much be copy paste from my documentation on the work project. Should be done by the end of next month, hopefully sooner, but I’m anticipating more troubles.

@george1421 @Wayne-Workman

Both nodes are back online now. I had a left over “-T” in /etc/default/nfs-kernel-server on the storage node from my attempts to disable NFSv4. What I was reading said NFSv3 doesn’t use TCP and is only UDP. Well, however fog connects it needs TCP with v3.

Here is where I ended, I don’t know if the RPCNFSCOUNT of 48 is needed to be increased from the default 8, but I read that this increases the threads for nfs workers.

/etc/default/nfs-kernel-server

# Number of servers to start up # To disable nfsv4 on the server, specify '--no-nfs-version 4' here RPCNFSDCOUNT='48 --no-nfs-version 4' # Runtime priority of server (see nice(1)) RPCNFSDPRIORITY=0 # Options for rpc.mountd. # If you have a port-based firewall, you might want to set up # a fixed port here using the --port option. For more information, # see rpc.mountd(8) or http://wiki.debian.org/SecuringNFS # To disable NFSv4 on the server, specify '--no-nfs-version 4' here RPCMOUNTDOPTS='--manage-gids --no-nfs-version 4' # Do you want to start the svcgssd daemon? It is only required for Kerberos # exports. Valid alternatives are "yes" and "no"; the default is "no". NEED_SVCGSSD="no" # Options for rpc.svcgssd. RPCSVCGSSDOPTS="" # Options for rpc.nfsd. RPCNFSDOPTS=""

/etc/idmapd.conf

[General] Verbosity = 0 Pipefs-Directory = /run/rpc_pipefs # set your own domain here, if id differs from FQDN minus hostname Domain = localdomain [Mapping] Nobody-User = nobody Nobody-Group = nogroup [Translation] Method = nsswitch

/etc/default/nfs-common

# If you do not set values for the NEED_ options, they will be attempted # autodetected; this should be sufficient for most people. Valid alternatives # for the NEED_ options are "yes" and "no". # Do you want to start the statd daemon? It is not needed for NFSv4. NEED_STATD= # Options for rpc.statd. # Should rpc.statd listen on a specific port? This is especially useful # when you have a port-based firewall. To use a fixed port, set this # this variable to a statd argument like: "--port 4000 --outgoing-port 4001". # For more information, see rpc.statd(8) or http://wiki.debian.org/SecuringNFS STATDOPTS= # Do you want to start the gssd daemon? It is required for Kerberos mounts. NEED_GSSD=

Download the latest fog_1.1.2.tar.gz file from sourceforge. This should be fixed in the new one.

Not one you downloaded two day’s ago right when we released, redownload as I’ve updated it.