Posts made by chunter2

@Sebastian-Roth I just tried disconnecting from the domain on a computer with a different image and the fog client reconnected correctly. Here’s the log.

------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
 10/09/2019 4:46 AM Client-Info Client Version: 0.11.16
 10/09/2019 4:46 AM Client-Info Client OS:      Windows
 10/09/2019 4:46 AM Client-Info Server Version: 1.5.6
 10/09/2019 4:46 AM Middleware::Response Success
 10/09/2019 4:46 AM HostnameChanger Checking Hostname
 10/09/2019 4:46 AM HostnameChanger Hostname is correct
 10/09/2019 4:46 AM HostnameChanger Attempting to join domain
 10/09/2019 4:46 AM HostnameChanger Success, code =  0
 10/09/2019 4:46 AM Power Creating shutdown command in 60 seconds
 10/09/2019 4:46 AM Bus Emmiting message on channel: Power
------------------------------------------------------------------------------

And then this.

------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
 10/09/2019 4:50 AM Client-Info Client Version: 0.11.16
 10/09/2019 4:50 AM Client-Info Client OS:      Windows
 10/09/2019 4:50 AM Client-Info Server Version: 1.5.6
 10/09/2019 4:50 AM Middleware::Response Success
 10/09/2019 4:50 AM HostnameChanger Checking Hostname
 10/09/2019 4:50 AM HostnameChanger Hostname is correct
 10/09/2019 4:50 AM HostnameChanger Attempting to join domain
 10/09/2019 4:51 AM HostnameChanger The machine is already joined to the domain, code =  2691
------------------------------------------------------------------------------

I really think it’s just something specific with this image but I can’t seem to figure out what’s different. It doesn’t make sense that I can join the domain manually either. I’m almost at the point of just re-installing Windows 7 from scratch to see if that cleans it up.

@Sebastian-Roth I just tried your suggestion. The net session command says There are no entries in the list. Starting the FOG service again produces the same error message as my first post. Strange how there’s no sessions. I figured there’s be something. If I manually join the domain and reboot I then get the following in the fog log.

 09/09/2019 7:36 PM HostnameChanger Checking Hostname
 09/09/2019 7:36 PM HostnameChanger Hostname is correct
 09/09/2019 7:36 PM HostnameChanger Attempting to join domain
 09/09/2019 7:36 PM HostnameChanger The machine is already joined to the domain, code =  2691

@Sebastian-Roth I’m still running an NT4 domain not an AD domain so I’m pretty sure I don’t have any GPO’s? I’m not sure where I’d look for any other tools or scripts on my server. Or are you thinking in the Windows 7 images itself? I’ve been putting off figuring out how to migrate a Samba NT4 domain to a Samba AD domain although I know I need to do that soon.

Thanks

@Sebastian-Roth I read through your reply a few times and I think the settings all makes sense now. The Host Registration one explains why I kept getting “new” MAC addresses for a couple machines even though I would remove them from the pending list. These machines had wifi modules that we don’t use. I also read through the link you posted to the other forum thread about the 1219 error. I’m wondering if I may have something similar in a way but I’m not exactly sure how to test. We have a logon.cmd script that runs to map a bunch of drives for the user logging in. Originally this wasn’t working because of linux file permissions on the logon.cmd file itself. I wonder if when “joining the domain” was working I hadn’t fixed that script yet. The strange thing is if I manually join the domain now and reboot it works fine. I checked and the fog service is set to delayed start like it suggested in that thread but that 1219 error still happens. Does the join happen without someone logging into the newly imaged host? I’m assuming it would? And would a logon.cmd script run on the join attempt? I figured it would only run on a user login.

Thanks

@Sebastian-Roth This may all just be confusion on my part. I’m learning this system that was already set up as I go. One thing I had to do was change the Domain Password from what looked like a guid to the actual password for the join to work from the fog client. I think this had to do with my 1.2.0 to 1.5.6 upgrade.
This was on the image that “worked”. This different image I just tried has the error message. Could you maybe explain the difference in the following settings in fog?

Under a hosts Active Directory section what’s “join domain after deploy”? Is that different than what the fog client tries to do?

What does “Name Change/AD Join Forced reboot?” in the Active Directory section do?

What’s the “Domain Password Legacy” for? Certain types of domains? We’re still running a Samba NT4 domain.

Under Service Settings for a host, what’s “Host Registration” do?

Under Service Settings what’s “Hostname Changer” do? I’m pretty sure this is the one that I’m getting the error message in the fog.log file from.

Thanks

I’ve just tried deploying a Windows 7 image to two computers and it doesn’t seem to want to join the domain. I’m getting the following error. I’ve deployed other Windows 7 images and they joined the domain properly. I’m guessing I’ve done something wrong with the image but I’m not sure what the error code means.

------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
 06/09/2019 7:17 PM Client-Info Client Version: 0.11.16
 06/09/2019 7:17 PM Client-Info Client OS:      Windows
 06/09/2019 7:17 PM Client-Info Server Version: 1.5.6
 06/09/2019 7:17 PM Middleware::Response Success
 06/09/2019 7:17 PM HostnameChanger Checking Hostname
 06/09/2019 7:17 PM HostnameChanger Hostname is correct
 06/09/2019 7:17 PM HostnameChanger Attempting to join domain
 06/09/2019 7:17 PM HostnameChanger Unknown Return Code:  1219
------------------------------------------------------------------------------

Thanks

@Sebastian-Roth I was on 1.2.0 and upgraded to 1.5.6. So removing the old entries manually should be fine then?

@Sebastian-Roth Just tried out the dll. I set a bad path on the first of two printers. I get the following first in the log which I think is good.

05/09/2019 7:45 PM PrinterManager Adding printers
05/09/2019 7:45 PM Printer Adding: Computer Lab x64
05/09/2019 7:45 PM PrinterManager Could not read printer INF file: bad path
05/09/2019 7:45 PM Printer Adding: Workroom Copier_64bit
05/09/2019 7:45 PM PrinterManager PrintUI return code = 0
05/09/2019 7:45 PM PrinterManager Restarting spooler

And then this the second and subsequent times through.

05/09/2019 7:47 PM PrinterManager Adding printers
05/09/2019 7:47 PM PrinterManager Computer Lab x64 has already been configured
05/09/2019 7:47 PM PrinterManager Workroom Copier_64bit already exists

So the second printer gets added now which is good but I don’t think it tries the first one again until you restart the service. I think I’m fine with that. I think my confusion was the “already been configured” message. I just assumed that was good.

I do understand this is an opensource project so no need to feel bad for not having the time. I can wait. I hope I’m coming across as a help and not demanding.

Thanks

Under inventory reports I’m noticing that if you choose a model name to search for it only lists hosts that are part of a group. This is without choosing a group. Does the inventory report only deal with groups? I’d like to see a list of all hosts of a specific model whether they’re in a group or not.

I also notice there are a bunch of models in the drop down list that have been removed from the system. I took a look at the database itself and the inventory table seems to have hosts still listed that have been removed. Is this table supposed to be updated when a host is removed?

Thanks

@Sebastian-Roth Can you try adding a printer with a bad path to the inf file? I think that’s my error. Maybe that log message just needs to have “but not installed” added on. I’m assuming you don’t want to keep trying to install over and over if the path is wrong. And that’s the reason for two lists?

@Sebastian-Roth Sure, I can test an updated DLL. Do you know why I was getting the message “has already been configured” instead of “already exists”? Or is that what I’d be testing with the updated DLL?

My guess is the database upgrade from 1.2.0 didn’t go as smoothly as I had thought. I probably should have checked some of the tables just to see. Setting the pConfig to “Local” in the database filled in “TCP/IP” in the Printer Type column when clicking on List all printers.

I just fixed my “second” printer issue. There was an & sign in the path to the inf file and the fog gui was showing & for some reason. I removed that from the gui and removed the & from the server path and the printer installed correctly. Strange how there was no error in the fog log but I’m guessing that’s not something you can query?

@Sebastian-Roth So I ended up changing the pConfig in the database and the printer installed. So I don’t have a screenshot that I can post. This host is supposed to have two printers but only one seems to install. I see this in the log.

9/3/2019 6:36 PM PrinterManager Adding printers
9/3/2019 6:36 PM PrinterManager Upstairs Printer_64-bit already exists
9/3/2019 6:36 PM PrinterManager Workroom Copier_64bit has already been configured

So the first one (Upstairs Printer_64-bit) installs correctly but the second one (Workroom Copier_64bit) doesn’t seem to be installed. Is there any meaning with the different log messages? “has already been configured”?

Thanks

@Sebastian-Roth I just took a look at the fog database itself and for the printers that seem to work their pConfig column is set to Local and their pDesc column is set to nothing. For the rest that don’t seem to work their pConfig is blank and their pDesc is set to NULL. The rest of the columns for all printers table seem fine. Is it safe to change those columns or are there more tables that could be affected?

Thanks

@Sebastian-Roth Here’s a full cycle from that host. I did just notice that when I click on the first printer that host has listed in fog I get a blank screen. If I click on the second printer I see all the details like printer type, printer name, ip address…

 9/2/2019 7:18 PM Middleware::Communication URL: http://xxx.xxx.xxx.xxx/fog/management/index.php?sub=requestClientInfo&configure&newService&json
 9/2/2019 7:18 PM Middleware::Response Success
 9/2/2019 7:18 PM Middleware::Communication URL: http://xxx.xxx.xxx.xxx/fog/management/index.php?sub=requestClientInfo&mac=xx:xx:xx:xx:xx:xx||00:00:00:00:00:00:00:E0&newService&json
 9/2/2019 7:18 PM Middleware::Response Success
 9/2/2019 7:18 PM Middleware::Communication URL: http://xxx.xxx.xxx.xxx/fog/service/getversion.php?clientver&newService&json
 9/2/2019 7:18 PM Middleware::Communication URL: http://xxx.xxx.xxx.xxx/fog/service/getversion.php?newService&json

 9/2/2019 7:18 PM Service Creating user agent cache
 9/2/2019 7:18 PM Middleware::Response Invalid time
 9/2/2019 7:18 PM Middleware::Response Success
 9/2/2019 7:18 PM Middleware::Response Module is disabled globally on the FOG server

------------------------------------------------------------------------------
---------------------------------ClientUpdater--------------------------------
------------------------------------------------------------------------------
 9/2/2019 7:18 PM Client-Info Client Version: 0.11.16
 9/2/2019 7:18 PM Client-Info Client OS:      Windows
 9/2/2019 7:18 PM Client-Info Server Version: 1.5.6
 9/2/2019 7:18 PM Middleware::Response Success
------------------------------------------------------------------------------


------------------------------------------------------------------------------
----------------------------------TaskReboot----------------------------------
------------------------------------------------------------------------------
 9/2/2019 7:18 PM Client-Info Client Version: 0.11.16
 9/2/2019 7:18 PM Client-Info Client OS:      Windows
 9/2/2019 7:18 PM Client-Info Server Version: 1.5.6
 9/2/2019 7:18 PM Middleware::Response Success
------------------------------------------------------------------------------


------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
 9/2/2019 7:18 PM Client-Info Client Version: 0.11.16
 9/2/2019 7:18 PM Client-Info Client OS:      Windows
 9/2/2019 7:18 PM Client-Info Server Version: 1.5.6
 9/2/2019 7:18 PM Middleware::Response Success
 9/2/2019 7:18 PM HostnameChanger Checking Hostname
 9/2/2019 7:18 PM HostnameChanger Hostname is correct
------------------------------------------------------------------------------


------------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
 9/2/2019 7:18 PM Client-Info Client Version: 0.11.16
 9/2/2019 7:18 PM Client-Info Client OS:      Windows
 9/2/2019 7:18 PM Client-Info Server Version: 1.5.6
 9/2/2019 7:18 PM Middleware::Response No snapins
------------------------------------------------------------------------------


------------------------------------------------------------------------------
--------------------------------PrinterManager--------------------------------
------------------------------------------------------------------------------
 9/2/2019 7:18 PM Client-Info Client Version: 0.11.16
 9/2/2019 7:18 PM Client-Info Client OS:      Windows
 9/2/2019 7:18 PM Client-Info Server Version: 1.5.6
 9/2/2019 7:18 PM Middleware::Response Success
 9/2/2019 7:18 PM PrinterManager ERROR: Data conversion using the DataContract FOG.Modules.DataContracts.PrinterManager failed
 9/2/2019 7:18 PM PrinterManager ERROR: Error converting value "" to type 'FOG.Modules.PrinterManager.Printer+PrinterType'. Path 'printers[0].type'.
------------------------------------------------------------------------------


------------------------------------------------------------------------------
--------------------------------PowerManagement-------------------------------
------------------------------------------------------------------------------
 9/2/2019 7:18 PM Client-Info Client Version: 0.11.16
 9/2/2019 7:18 PM Client-Info Client OS:      Windows
 9/2/2019 7:18 PM Client-Info Server Version: 1.5.6
 9/2/2019 7:18 PM Middleware::Response Success
 9/2/2019 7:18 PM PowerManagement Calculating tasks to unschedule
 9/2/2019 7:18 PM PowerManagement Calculating tasks to schedule
------------------------------------------------------------------------------


------------------------------------------------------------------------------
----------------------------------UserTracker---------------------------------
------------------------------------------------------------------------------
 9/2/2019 7:18 PM Client-Info Client Version: 0.11.16
 9/2/2019 7:18 PM Client-Info Client OS:      Windows
 9/2/2019 7:18 PM Client-Info Server Version: 1.5.6
 9/2/2019 7:18 PM Middleware::Response Success
------------------------------------------------------------------------------

 9/2/2019 7:18 PM Service Sleeping for 91 seconds

I’m getting the following errors in the PrinterManager service and my printers don’t install. I’ve got other printers assigned to different hosts that seem to work fine.

02/09/2019 4:12 PM PrinterManager ERROR: Data conversion using the DataContract FOG.Modules.DataContracts.PrinterManager failed
02/09/2019 4:12 PM PrinterManager ERROR: Error converting value “” to type ‘FOG.Modules.PrinterManager.Printer+PrinterType’. Path ‘printers[0].type’.

Any ideas on how to debug this? This is after a fog upgrade from 1.2.0 to 1.5.6.

Thanks

I didn’t see a forum here for generic questions not exactly related to fog so I figured I’d try here. We’ve got a Ubuntu 18.04 server running fog 1.5.6. It was upgraded from Ubuntu 10.04 and fog was upgraded from 1.2.0. It also runs our NT4 style Samba domain. We’re in the process of upgrading all our host machines from Windows 7 to Windows 10 and they have issues connecting to the NT4 domain. We’re looking to migrate from Samba NT4 to Samba AD. We can’t seem to find good instructions on migrating under Ubuntu 18.04. I’ve found instruction on Samba’s site but they’re not Ubuntu specific and I’ve found instructions on creating an AD on Ubuntu 16.04 but not migrating. Has anyone done this before? If this is too off-topic feel free to remove this post. Just figured I’d ask.

Thanks

@george1421 All my hosts seem to be working fine now.

Should I just remove the useless symlink?

Thanks for the help.

@george1421 Right now I’ve got all the web files in /var/www/html/fog. Inside that directory there’s a symlink called fog pointing to /var/www/html/fog (same thing). Not sure why. I’m on Ubuntu 18.04. How should it be set up so upgrades work properly?

I’ll have to test tonight to make sure the hosts are booting correctly and that the compatibility test works but I’m pretty sure they will now.

@george1421 Turns out the TFTP PXE KERNEL DIR variable was set to /var/www/fog/service/ipxe instead of /var/www/html/fog/service/ipxe/ which explains why the kernel wasn’t updating. Now it is. And I’ve got 4.19.64 now. I’m not sure why it was set wrong in the first place. And I agree, I don’t know why hosts were still booting. I’d get the fogproject splash page with a 3 second countdown on booting the first hard drive and then they would boot normally. A memory test seemed to work from the splash page but nothing else that I tried.