Reboot server? Did you do a schema upgrade? did it work? Did you export your schema first?
Posts made by Szeraax
-
RE: Fog 1.5.2 Host module settings don't save
-
RE: Does FOG have any in built services which allow a users password to meet a specific criteria?
Looks like users in fog (best guess).
-
RE: Powershell snapin and registry
@joe-schmitt Good point. 32bit client is having to escape the normal system. 64 bit client would use powershell.exe and get the correct one by default. Anything us plebs can do to help get a 64bit client out?
-
RE: Powershell snapin and registry
@aruhuno I think that the problem is that if we just always use that path, then all x86 installations would fail (I don’t believe that a 32bit machine has a sysnative folder). If we put in a check that will attempt to use the 64 bit powershell if its running on a 64 bit machine, I think that would be good. For now, I just plan to use that path instead of powershell.exe.
-
RE: Fog Multicast Sessions: What happens when a host in session is powered off and what happens when it is powered back on?
@tom-elliott I mean rolling as in:
If the multicast is 50% done and a new client connects, it will begin writing at the same block as the others. Once all others complete, the storage node sees that there are clients who aren’t done. Asks them what block ranges they still need, and then gives out those blocks. Thus, I could start a multicast and join any number of clients while it is going. Assuming that the last one joins before the first one finishes, the total data sent would be less than 2x the image. Additionally, the first client was not slowed down in any way by the new clients joining.
a la, a feature that I think Ghost had once upon a time.
-
RE: Fog Multicast Sessions: What happens when a host in session is powered off and what happens when it is powered back on?
have full controls
This would be cool. I don’t use multicast currently cause I’ve used it on a prod network midday before… But, being able to do stuff like “rolling multicast” where the sender will start over for clients that joined later and get them all to completion ASAP (maybe that’s a thing that udpsender already does and I’ve missed it). etc.
-
RE: Rate is at a slow crawl when trying to deploy/capture image
Just going to add in here that when I want to see how busy my HDD’s are during tasks, I use nmon. Can run as normal user and press d to view disk activity percentage. Very friendly to a newb. Press n to also view network stats and c to view CPU as well.
If I was you, i’d bring a computer over to the same physical switch that your FOG server takes the image on. See if it sustains a better speed or not to determine if network routing is to blame or not.
-
RE: Error 'Could not open inode 'XXXXXX" through the library'
@sebastian-roth I agree! Well done sir. Do you care to explain what was happening? Or is to too long that you don’t even want to sum up?
-
RE: Error 'Could not open inode 'XXXXXX" through the library'
@tom-elliott Image did capture correctly. Can you explain to us newbs what was A) wrong and B) the fix? Just out of casual curiousity, so not a big deal if you don’t want to type it out.
Right now, my guess is that the disk cleanup to remove old windows installations did something funky that may have moved certain stuff that fog didn’t expect to change and now it sometimes thought certain things were in bounds but actually aren’t and your fix gets the correct new location. But that’s TOTALLY baseless.
-
RE: Error 'Could not open inode 'XXXXXX" through the library'
@tom-elliott I decided to do your fix before checkdisk, defrag, or resize. Is now capturing an image!
-
RE: Error 'Could not open inode 'XXXXXX" through the library'
Also of note: upgrading to 1709 RESET our fast boot option and we had to disable it again.
-
RE: Error 'Could not open inode 'XXXXXX" through the library'
@tom-elliott @Sebastian-Roth Hahaha, we just ran into this as well. Can image 1703. Can image 1709. Can’t image once removed the windows.old via running Disk Cleanup as administrator and selecting the “Previous Windows installstion(s)” (about 28gb of data) option for removal. Do you need anything else to help diagnose this issue? Or just testers to report?
Will try chkdsk + defrag tomorrow. When it doesn’t work, I’ll try to apply your init and report.
-
RE: Clear snapin history? Automatically?
@cml Better mark this as solved. Loved it!
-
RE: Snapin Timeout (seconds) not updating
@wayne-workman I have tried it both ways. Only update timeout. Update timeout and the snapin file. I would guess that only when I update the snapin file does it give an error in the apache log.
-
RE: Snapin Timeout (seconds) not updating
@wayne-workman Interesting is a word that I could use to describe it
-
RE: Snapin Timeout (seconds) not updating
Yes, it seems!
[Tue Mar 20 13:59:17.465432 2018] [php7:warn] [pid 27636] [client IPADDRESS:50418] PHP Warning: ftp_rmdir(): Remove directory operation failed. in /var/www/html/fog/lib/fog/fogftp.class.php on line 823, referer: http://IPADDRESS/fog/management/index.php?node=snapin&sub=edit&id=1
-
Snapin Timeout (seconds) not updating
Using 1.5.0, when i’m editing a snapin, if I change the timeout from 0 to anything like 60,30,120, the text will stay in that field once I click Update, but when I refresh the page, the value is not changed.
-
RE: Clear snapin history? Automatically?
@tom-elliott Thanks for the thoughts. And especially thank you for cml for the code, and Wayne for ALWAYS being amazing on the forums.
I’m just happy that I solved my other problem on my own (the post about running 64bit powershell snapins so I can use modules and such). Gettin better all the time. Actually, Tom, it may be worth making a 64bit powershell snapin template. Guess that may have to be my own PR to put in.