Best posts made by JJ Fullmer

@Sebastian-Roth I saw it happen again this morning. In at least one case (I have scenarios where it’s happening that this doesn’t match up with) it seems to happen right after a snapin hash doesn’t match.
I attached the fog.log section where the host went through Authenticated -> start snapins ->Snapin hash mismatch -> Invalid host

How my hashes keep getting mismatches is a whole other question because I use the exact same file for every snapin. And said file hasn’t changed in 2 years.

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 8/25/2020 7:12:24 AM Client-Info Version: 0.12.0
 8/25/2020 7:12:24 AM Client-Info OS:      Windows
 8/25/2020 7:12:24 AM Middleware::Authentication Waiting for authentication timeout to pass
 8/25/2020 7:12:24 AM Middleware::Communication Download: http://fogserver/fog/management/other/ssl/srvpublic.crt
 8/25/2020 7:12:24 AM Data::RSA FOG Server CA cert found
 8/25/2020 7:12:24 AM Middleware::Authentication Cert OK
 8/25/2020 7:12:24 AM Middleware::Communication POST URL: http://fogserver/fog/management/index.php?sub=requestClientInfo&authorize&newService
 8/25/2020 7:12:24 AM Middleware::Response Success
 8/25/2020 7:12:24 AM Middleware::Authentication Authenticated


 8/25/2020 7:12:24 AM Middleware::Communication URL: http://fogserver/fog/management/index.php?sub=requestClientInfo&configure&newService&json
 8/25/2020 7:12:24 AM Middleware::Response Success
 8/25/2020 7:12:24 AM Middleware::Communication URL: http://fogserver/fog/management/index.php?sub=requestClientInfo&mac=9C:7B:EF:C3:90:84||00:00:00:00:00:00:00:E0&newService&json
 8/25/2020 7:12:25 AM Middleware::Response Success
 8/25/2020 7:12:25 AM Middleware::Communication URL: http://fogserver/fog/service/getversion.php?clientver&newService&json
 8/25/2020 7:12:25 AM Middleware::Communication URL: http://fogserver/fog/service/getversion.php?newService&json

 8/25/2020 7:12:25 AM Service Creating user agent cache
 8/25/2020 7:12:25 AM Middleware::Response Module is disabled globally on the FOG server
 8/25/2020 7:12:25 AM Middleware::Response Module is disabled globally on the FOG server
 8/25/2020 7:12:25 AM Middleware::Response Module is disabled globally on the FOG server
 8/25/2020 7:12:25 AM Service Initializing modules

------------------------------------------------------------------------------
---------------------------------ClientUpdater--------------------------------
------------------------------------------------------------------------------
 8/25/2020 7:12:25 AM Client-Info Client Version: 0.12.0
 8/25/2020 7:12:25 AM Client-Info Client OS:      Windows
 8/25/2020 7:12:25 AM Client-Info Server Version: 1.5.9-RC2
 8/25/2020 7:12:25 AM Middleware::Response Success
------------------------------------------------------------------------------


------------------------------------------------------------------------------
----------------------------------TaskReboot----------------------------------
------------------------------------------------------------------------------
 8/25/2020 7:12:25 AM Client-Info Client Version: 0.12.0
 8/25/2020 7:12:25 AM Client-Info Client OS:      Windows
 8/25/2020 7:12:25 AM Client-Info Server Version: 1.5.9-RC2
 8/25/2020 7:12:25 AM Middleware::Response Success
------------------------------------------------------------------------------


------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
 8/25/2020 7:12:25 AM Client-Info Client Version: 0.12.0
 8/25/2020 7:12:25 AM Client-Info Client OS:      Windows
 8/25/2020 7:12:25 AM Client-Info Server Version: 1.5.9-RC2
 8/25/2020 7:12:25 AM Middleware::Response Success
 8/25/2020 7:12:25 AM HostnameChanger Checking Hostname
 8/25/2020 7:12:25 AM HostnameChanger Hostname is correct
 8/25/2020 7:12:25 AM HostnameChanger Attempting to join domain
 8/25/2020 7:12:25 AM HostnameChanger Host already joined to target domain
------------------------------------------------------------------------------


------------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
 8/25/2020 7:12:25 AM Client-Info Client Version: 0.12.0
 8/25/2020 7:12:25 AM Client-Info Client OS:      Windows
 8/25/2020 7:12:25 AM Client-Info Server Version: 1.5.9-RC2
 8/25/2020 7:12:25 AM Middleware::Response Success
 8/25/2020 7:12:25 AM SnapinClient Running snapin DeviceForm - Desktop
 8/25/2020 7:12:25 AM Middleware::Communication Download: http://192.168.100.117//fog/service/snapins.file.php?mac=9C:7B:EF:C3:90:84||00:00:00:00:00:00:00:E0&taskid=5462
 8/25/2020 7:12:26 AM SnapinClient C:\Program Files (x86)\FOG\tmp\chocoPkgSnapin.ps1
 8/25/2020 7:12:26 AM Bus Emmiting message on channel: Notification
 8/25/2020 7:12:26 AM SnapinClient Starting snapin
 8/25/2020 7:13:00 AM SnapinClient Snapin finished
 8/25/2020 7:13:00 AM SnapinClient Return Code: 0
 8/25/2020 7:13:00 AM Bus Emmiting message on channel: Notification
 8/25/2020 7:13:00 AM Middleware::Communication URL: http://fogserver/fog/service/snapins.checkin.php?taskid=5462&exitcode=0&mac=9C:7B:EF:C3:90:84||00:00:00:00:00:00:00:E0&newService&json
 8/25/2020 7:13:00 AM SnapinClient Running snapin mitel-pm
 8/25/2020 7:13:00 AM Middleware::Communication Download: http://192.168.100.117//fog/service/snapins.file.php?mac=9C:7B:EF:C3:90:84||00:00:00:00:00:00:00:E0&taskid=5475
 8/25/2020 7:13:01 AM SnapinClient C:\Program Files (x86)\FOG\tmp\chocoPkgSnapin.ps1
 8/25/2020 7:13:01 AM Bus Emmiting message on channel: Notification
 8/25/2020 7:13:01 AM SnapinClient Starting snapin
 8/25/2020 7:14:35 AM SnapinClient Snapin finished
 8/25/2020 7:14:35 AM SnapinClient Return Code: 0
 8/25/2020 7:14:35 AM Bus Emmiting message on channel: Notification
 8/25/2020 7:14:35 AM Middleware::Communication URL: http://fogserver/fog/service/snapins.checkin.php?taskid=5475&exitcode=0&mac=9C:7B:EF:C3:90:84||00:00:00:00:00:00:00:E0&newService&json
 8/25/2020 7:14:35 AM SnapinClient Running snapin office2010-Std
 8/25/2020 7:14:35 AM Middleware::Communication Download: http://192.168.100.117//fog/service/snapins.file.php?mac=9C:7B:EF:C3:90:84||00:00:00:00:00:00:00:E0&taskid=5476
 8/25/2020 7:14:36 AM SnapinClient C:\Program Files (x86)\FOG\tmp\chocoPkgSnapin.ps1
 8/25/2020 7:14:36 AM Bus Emmiting message on channel: Notification
 8/25/2020 7:14:36 AM SnapinClient Starting snapin
 8/25/2020 7:22:15 AM SnapinClient Snapin finished
 8/25/2020 7:22:15 AM SnapinClient Return Code: 0
 8/25/2020 7:22:15 AM Bus Emmiting message on channel: Notification
 8/25/2020 7:22:15 AM Middleware::Communication URL: http://fogserver/fog/service/snapins.checkin.php?taskid=5476&exitcode=0&mac=9C:7B:EF:C3:90:84||00:00:00:00:00:00:00:E0&newService&json
 8/25/2020 7:22:15 AM SnapinClient Running snapin outlook2016
 8/25/2020 7:22:15 AM Middleware::Communication Download: http://192.168.100.117//fog/service/snapins.file.php?mac=9C:7B:EF:C3:90:84||00:00:00:00:00:00:00:E0&taskid=5477
 8/25/2020 7:22:16 AM SnapinClient C:\Program Files (x86)\FOG\tmp\chocoPkgSnapin.ps1
 8/25/2020 7:22:16 AM SnapinClient ERROR: Hash does not match
 8/25/2020 7:22:16 AM SnapinClient ERROR: --> Ideal: 817B881A4D07DCFF51F67A47D9595DDE59D010FE0C018BDF5B57C502CB83A14F3085AF48987B392E8BF38E2C6B29D094055BDFFB6BBCD5647697D64AA4BDD668
 8/25/2020 7:22:16 AM SnapinClient ERROR: --> Actual: 5271D1B9F35EA9FC2F1E3CE474C20641A15B37A02035E7E8210DFB513518CBC79FDFD25092A41491C2AB02AF8E0913C99819C6066B9883F398D90C5D045E4A1D
 8/25/2020 7:22:16 AM Middleware::Communication URL: http://fogserver/fog/service/snapins.checkin.php?taskid=5477&exitcode=-1&mac=9C:7B:EF:C3:90:84||00:00:00:00:00:00:00:E0&newService&json
------------------------------------------------------------------------------


------------------------------------------------------------------------------
--------------------------------PrinterManager--------------------------------
------------------------------------------------------------------------------
 8/25/2020 7:22:16 AM Client-Info Client Version: 0.12.0
 8/25/2020 7:22:16 AM Client-Info Client OS:      Windows
 8/25/2020 7:22:16 AM Client-Info Server Version: 1.5.9-RC2
 8/25/2020 7:22:16 AM Middleware::Response Module is disabled globally on the FOG server
------------------------------------------------------------------------------


------------------------------------------------------------------------------
--------------------------------PowerManagement-------------------------------
------------------------------------------------------------------------------
 8/25/2020 7:22:16 AM Client-Info Client Version: 0.12.0
 8/25/2020 7:22:16 AM Client-Info Client OS:      Windows
 8/25/2020 7:22:16 AM Client-Info Server Version: 1.5.9-RC2
 8/25/2020 7:22:16 AM Middleware::Response Success
 8/25/2020 7:22:16 AM PowerManagement Calculating tasks to unschedule
 8/25/2020 7:22:16 AM PowerManagement Calculating tasks to schedule
------------------------------------------------------------------------------


------------------------------------------------------------------------------
----------------------------------UserTracker---------------------------------
------------------------------------------------------------------------------
 8/25/2020 7:22:16 AM Client-Info Client Version: 0.12.0
 8/25/2020 7:22:16 AM Client-Info Client OS:      Windows
 8/25/2020 7:22:16 AM Client-Info Server Version: 1.5.9-RC2
 8/25/2020 7:22:16 AM Middleware::Response Success
 8/25/2020 7:22:16 AM Middleware::Communication URL: http://fogserver/fog/service/usertracking.report.php?action=login&user=SHP-WKS-6096\AdlAdmin&mac=9C:7B:EF:C3:90:84||00:00:00:00:00:00:00:E0&newService&json
------------------------------------------------------------------------------

 8/25/2020 7:22:16 AM Service Sleeping for 94 seconds
 8/25/2020 7:23:50 AM Middleware::Communication URL: http://fogserver/fog/management/index.php?sub=requestClientInfo&configure&newService&json
 8/25/2020 7:23:50 AM Middleware::Response Success
 8/25/2020 7:23:50 AM Middleware::Communication URL: http://fogserver/fog/management/index.php?sub=requestClientInfo&mac=9C:7B:EF:C3:90:84||00:00:00:00:00:00:00:E0&newService&json
 8/25/2020 7:23:50 AM Middleware::Response Invalid host
 8/25/2020 7:23:50 AM Middleware::Communication URL: http://fogserver/fog/service/getversion.php?clientver&newService&json
 8/25/2020 7:23:51 AM Middleware::Communication URL: http://fogserver/fog/service/getversion.php?newService&json

 8/25/2020 7:23:51 AM Service Creating user agent cache
 8/25/2020 7:23:51 AM Middleware::Response Module is disabled globally on the FOG server
 8/25/2020 7:23:51 AM Middleware::Response Module is disabled globally on the FOG server
 8/25/2020 7:23:51 AM Middleware::Response Module is disabled globally on the FOG server

@vbelous said:

i’m taking for a previous user

I’m not sure what you mean by that

And since you have 7 and 8 images, are you running into some sort of trouble with uploading a windows 10 image or are you just worried that there’s no option to say an image is windows 10 in the older versions of fog. Setting it to windows 7 or 8 doesn’t change anything in the imaging process that I am aware of, it’s more for inventory and organization of the database as I understand it. Granted Windows 10 is an option in the latest trunks, so it doesn’t really matter.

Have you tried uploading a windows 10 image to your working image configurations for 7 and 8 and run into trouble?
Just trying to help you better here.

@Sebastian-Roth Here ya go

I think that one possibility of the problem lies in the variable dump from fog.
It lists the partition as /dev/nvme0n11 but fdisk -l or gdisk -l lists it as /dev/nvme0n1p1

@Jonathan-Cool So I found my old post where I mentioned those exact commands you put in your original post
https://forums.fogproject.org/topic/6540/adding-custom-printer-configuration plus it has a bat script (which is a language I don’t even use anymore since I moved everything to powershell)

So it is the .dat file that you want but where it resides, I’m trying to find that info.

I was a bit long winded when I tried to help someone else with something related here https://forums.fogproject.org/topic/6615/printer-problems/5

I am sure I made some sort of documentation post somewhere though just gotta find it and then make sure it gets put somewhere more findable

Isn’t this functionality also available in the GreenFog settings?
I’ve looked at them but never tried playing with them.

@Sebastian-Roth @Tom-Elliott Is there a timeline on when you think this issue will be fixed?

Please and thank you

@Sebastian-Roth
Just gave this a test
I’m on fog 1.5.9.3
I’m using bzImage 5.6.18
I set a host to use the init you shared.

I had previously imaged this machine on the init that came with 1.5.9.3/1.5.9.2 and it imaged in 4 min 33 secs and when I watched the speed it was around 10-11 GB/min. But I wasn’t babysitting the speed, it probably slowed down a bit when I wasn’t looking based on the results below.

Same image on the new init didn’t appear to go much faster but did stay stable around 11-12 GB/min but it actually finished in 2 min 38 secs. So It almost cut the time in half.

So, I didn’t get to see the super fast 20+ GiB/min speed again, but it did finish in about half the time.

Edit

I also noticed it now shows speed in GB/min instead of GiB/min. Not that big a scale change, but something I noticed. I also deployed the image on the machine one more time, this time without being connected to a small desktop switch and got the exact same 2:38 deploy time.

Other Edit

I also noticed that I too don’t have any 2.89 partclone images to test. Mine are all 3.13 I’m pretty sure.

Also, this might still be a thing
https://wiki.fogproject.org/wiki/index.php/Auto_driver_Install

@Sebastian-Roth @Tom-Elliott
I updated to the latest trunk since I noticed one of the commits said that it had adjusted the way partition numbers were found. But sadly it still isn’t working. I will try making it a raw image to see if that works as a workaround like it did for the other person with this problem with the m.2 drive. The debug information lsblk and for variable dump all still have the same information.

Thanks,
-JJ

@Sebastian-Roth These weird suddenly pending asset issues are still happening. I’m about to start re-imaging all our computers. May provide more data to debug the problem, or maybe it’ll fix the problem, we’ll see.

@wayne-workman
Fun fact, you can add the old default windows photo viewer to LTSB or the normal windows 10.
You just need to enable it in the registry. This is the contents of the reg file to do that

 Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Applications\photoviewer.dll]

[HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell]

[HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\open]
"MuiVerb"="@photoviewer.dll,-3043"

[HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\open\command]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\
6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\
00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\
25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\
00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\
6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\
00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\
5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\
00,31,00,00,00

[HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\open\DropTarget]
"Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}"

[HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\print]

[HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\print\command]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\
6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\
00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\
25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\
00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\
6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\
00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\
5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\
00,31,00,00,00

[HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\print\DropTarget]
"Clsid"="{60fd46de-f830-4894-a628-6fa81bc0190d}"

Save all that as a .reg file to add the windows 7/8 style photo viewer to windows 10

Awesome! I’m giving it a try right now. And my apologies if I seemed impatient in my asking, I was just curious and getting all excited.
I currently only have one image and it is a resizable one, we’ll see what happens.

Thanks,
-JJ

Made a fogapi git issue, so that I hopefully don’t forget about this idea https://github.com/darksidemilk/FogApi/issues/4

So, despite the ridiculous amount of changes (some really dumb ones, google demystifying dual scan, and then read the windows 10 wsus group policy documentation to find some conflicting ones) I would still recommend the Current Branch for Business. We’ll actually they recently changed the naming to be Semi-annual Channel for CBB and Semi-Annual-Channel (Targeted) for Current Branch.

While I certainly was all about the LTSB at first, there are some issues with it I have discovered.

One of the bigger ones is the lack of support for “new silicone” I don’t have time to go find the articles at the moment, but I’ve read a few microsoft and third party posts on how LTSB won’t support the latest chipsets as they come out. So in other words, if you have a image setup with LTSB 2015, but you have a new computer with a cpu/chipset that came out in 2018 with some fancy new features, you won’t be able to install LTSB on that new computer, or at least you won’t be supposed to be able to.

Also, while I was rather hesitant to allow access to the windows store, as I started adding surface type touch screens to our environment I’ve come to find it more and more useful. Also, there are plenty of group policies to disable access to the windows store.

Also, reading about the new features and such as they come out, kept making me want the new features. A more flexible and customizable windows update experience, new powershell cmdlets, and all sorts of things to play with.

Personally the whole no support for new silicone thing is what converted me.
Plus, we want to have a regular imaging schedule and the now semi-annual release schedule gives us a schedule to deploy fresh images. Which we intend to do instead of deploying the new releases through wsus. Updating from one release to another tends to lose some customizations like lockscreen images and custom account pictures. Plus they tend to change some of the features surrounding those customizations, so updating the ol unattend file and setupcomplete type scripts on that regular basis to be able to take advantage of new features is prolly a good idea. Also, have you checked out windows imaging configuration designer to make provisioning packages? It’s pretty sweet.

So in short, due to recent changes to the windows as a service paradigm and choices in support rules for LTSB, unless you are using the same hardware for something for 10 years that needs to not have any risks of new features, and perhaps has some legacy software needs. Then LTSB is the way to go. If you are just looking to shirk away from pieces of windows 10 like the store and such, you should not go with LTSB and either embrace the changes, or create more restrictive group policies. Especially since you become so very stuck with any version of LTSB since you can only update to another iteration with a fresh install/image.

If you for some reason don’t have a AD to deploy group policies you can utilize provisioning packages and for policies not yet supported there you can learn to utilize the https://github.com/dlwyatt/PolicyFileEditor powershell module to deploy local group policies.

That’s my 2 (maybe it’s more like 200) cents on the matter.

@Sebastian-Roth I just tested with a resizable image to no avail. I got some error messages. It looks like some numbering didn’t quite work as expected. Mainly when it is searching for /dev/nvme0n1p instead of /dev/nvme0n1p1 and when it tries to find the image file named d1pp1.img instead of d1p1.img

My apologies that some of these pictures have duplicate information, this happened twice I was just ready with the camera the second time since it happened so fast.

I am currently uploading a non-resizable version of that image to test that idea. I should be able to post results on that test in like 10 minutes or so.

@chris-whiteley I just re-read your post and realized you want to deploy a single snapin task, not the all snapins task.

I’d have to test it but I believe what you want is

$json = (@{
  "taskTypeID"='13';
  "deploySnapins"='snapinName';
} | ConvertTo-Json);
New-FogObject -type objecttasktype -coreTaskObject host -jsonData $json -IDofObject $hostid;

When doing the all snapins taks the tasktypeid is 12 and you set the deploySnapins to ‘-1’. @Tom-Elliott can help with confirming the syntax of the json required for a single snapin. But if your using my powershell module, then the New-FogObject command will take care of creating the task.

If you look at the code for start-fogsnapins here https://github.com/darksidemilk/FogApi/blob/master/FogApi/Public/Start-FogSnapins.ps1 you’ll note that I also have some checks for existing snapin tasks on the host. You’d probably want to do something like that. I should probably make it so that little segment is its own function, like Test-SnapinTasks and should probably make a separate start-fogsnapin function for single snapin tasks. But hey you could always do a pull request if you want to give writing it a try. I don’t know when I’ll have time to do all that myself.

TL;DR
The quick answer is the ‘useAD’ property of a host in the api checks that box, but will not pull your default settings when done through the api. So you need to provide all domain join info.

@Jamaal Good day sir! Sorry for a delayed reply, haven’t been on here in a bit, had been trying to stay active during my quarantine but eventually my infant son won all my attention while I was home. But I am now back at work and am excited to see someone with a powershell api question =).

I took a look at that old post and @scottybullet and I should clearly be friends. Looks like he posted some powershell api stuff before I published my module publicly.

So as @Sebastian-Roth mentioned, check out the powershell module (check the links in my signature). If you use that as a dependency of your script you’ll have a good time. If this leads to some more functions needing to be added to the module to make it easier we can make the functions and get them added.

So let me see if I got this straight.

You have microsoft orchestrator (I’m not actually familiar with that product, but I think I get what it does from context)

1. You want other employees to put info about a new computer into that product in some way
2. That product sends that info to a powershell script
3. The script adds the computer to fog and queues it to start imaging with wake on lan as soon as you plug it in to the network.

Currently it isn’t auto joining the domain but you want it to.

Well sir I believe the answer may be pretty easy. I usually add fog hosts using the pxe boot menu
Firstly, something built in fog is setting default AD settings at http://fog-server/fog/management/index.php?node=about&sub=settings (select Active directory defaults). I pull that info when I register a host in the pxe boot menu and then edit it during a provisioning script to put things in the right OU. But I just realized that doesn’t matter because it doesn’t pull that information when you create from the API, but it’s still a feature that exists and there may be a way to leverage it in your situation but we’ll come back to that if we need to.

Ok so first let’s create a host

# you can also just do name, description, and macs and add the rest after with a set-fogobject command
$HostJson = @{
    "name"=  "testHost-1"
    "description"=  "a test"
    "macs" =  @("11:22:33:44:55:66")
    "imageID" = "29"
    "useAD" = 1 
    "ADDomain" = "yourDomain.com"
    "ADOU" =  "OU=OUname,OU=ParentOU,OU=GrandParrentOU,DC=yourDomain,DC=com"
    "ADUser" = "domainUsername"
    "ADPass" = "plainTextPassword"
    "enforce" = 1
}
#note that "useAD" = 1 checks the join domain after deploy box
#note that "enforce" = 1 checks the force rename and join even if user is logged in box
#note that the password is in plaintext via the api because you are already authenticated to get to this point, this is why I prefer to pull from the existing default so I don't pass the password in plaintext anywhere. 

#convert to ps object to a json string
$json = $hostJson | ConvertTo-Json
$newHost = New-FogObject -type object -coreObject host -jsonData $json

Sidenote: @Tom-Elliott or @Sebastian-Roth is it possible to pull the default domain settings include username/password from the fog settings via the api? So that to add domain join info through an api call doesn’t require a plaintext password, or maybe some other solution, like making it so the defaults are pulled if a host created with the api has that join after deploy/useAD box checked?

So that above code would add a new host with the domain information and stores the host info in a variable. You could then queue the image of the host with (I should really make a function for this)

$jsonObj = @{
    "taskTypeID" = 1
}
$jsonData = $jsonObj | ConvertTo-Json;
# create the image task on the newhost 
New-FogObject -type objecttasktype -coreTaskObject host -jsonData $jsonData -IDofObject $newHost.ID;

@Sebastian-Roth Similar problem with a non-resizable disk, it doesn’t seem to add a 1 at the end of /dev/nvme0n1p
I’m going to do a debug session and see if the lsblk is any different from before and such. Let me know if there’s any other information you need. I’m here to help

On a side note, I did take out the primary hard disk specification and ran a hardware inventory and it found the hard drive just fine on its own. It didn’t get a harddrive manufacturer, model, or s/n but it knows it exist now. Yay progress!

@sideone Are you getting different IP addresses in the snapin download url and the communication url? i.e. is the communication URL going to your master and the download going to a storage node? Maybe a storage node has something goofy in its storage node config?

The communication url is derived from the c:\program files (X86)\Fog\settings.json file where it uses the Https flag, server name, and webroot values to construct that base url i.e. http://10.xx.xx.xx/fog
I’m not sure if the download url is combo of the settings.json file with info from the server or if it’s just from the server or what. But your download url is missing the http/https and is also has an extra slash.

P.S. you don’t really need to hide the ip of the fog server. It’s an internal subnet only ip address, it doesn’t expose anything to say what ip you’re using. Do whatever makes you feel safe, just saying is all.

@Sebastian-Roth and @Jurgen-Goedbloed Could I also be added as a maintainer. I would love to help with this project.
Maybe we make some github issues for what documents need creating and or copy pasting and divide and conquer?