Thank you sir for your response, it is working correctly…Just updated and was going through the motions checking functions.
Posts made by Hanz
-
RE: Power Manager is not working correctly with client...
-
RE: 1.4.0 rc1 not displaying logins for specified user when report ran.
@Tom-Elliott Just a question, hoping it was something I could possibly easily (add) to my own setup. Not a huge issue at all. Login history has been removed in RC-6, is it coming back ?
-
Power Manager is not working correctly with client...
Server
- FOG Version: Wed Apr 19, 2017 9:41 am
Running Version 1.4.0-RC-6
SVN Revision: 6069 - OS: Fedora 24
Client
- Service Version: 11.12
- OS: Windows 7
Description
Upon setting up power management settings on client and booting client, it will not show scheduled power management. I just updated to RC-6 from RC-1, where this was working.
Host Management
Edit: Sysprepx32------------------------------------------------------------------------------ --------------------------------PowerManagement------------------------------- ------------------------------------------------------------------------------ 4/19/2017 9:40 AM Client-Info Client Version: 0.11.12 4/19/2017 9:40 AM Client-Info Client OS: Windows 4/19/2017 9:40 AM Client-Info Server Version: 1.4.0-RC-6 4/19/2017 9:40 AM Middleware::Response Success 4/19/2017 9:40 AM PowerManagement Calculating tasks to unschedule 4/19/2017 9:40 AM PowerManagement Calculating tasks to schedule
- FOG Version: Wed Apr 19, 2017 9:41 am
-
RE: 1.4.0 rc1 not displaying logins for specified user when report ran.
@Tom-Elliott thank you sir… you got anything for the second part my man?
-
1.4.0 rc1 not displaying logins for specified user when report ran.
Kind of two fold here, but when running report on login history…the first page asks for either login name or hostname. When I enter a particular username, the next screen prompts with pre-filled dates (which I assume is the last known login for that user). If I just go with the default dates…the returned report shows all users that logged in on that date, or during range (if changed). It’s not actually carrying over the username to search against as well it seems.
The second part concerns the pushbullet notification when a user fails logon, I would like to know which hostname/ ip that user is attempting to login from…(if already registered, if not then maybe just the ip address)
-
Problem accessing pxe menu beyond login credentials
Server
- FOG Version: 1.3.1-RC-3
- OS: Fedora 24
Client
- Service Version: 11.7
- OS: Windows 7
Description
recently pulled RC-3, but during pxe boot I’m getting
http://X.X.X.Xservice/ipxe/boot.php…Error 0x3e11613b
odd looking without the “/” between ip and “service”
using undionly.kkpxechainloading failed
I can get to where I enter credentials, and then it errors after hitting “enter”
The actual “http://X.X.X.X/fog/service/ipxe/” returns the listing of directory from browser
-
Lost pxe boot: init errors
Server
- FOG Version: 1.3.1-RC1
- OS: Fedora 24
Client
- Service Version: 11.7
- OS: Windows 7
Description
PXE boot fails with errors. The following is from apache error logs:
[Tue Jan 03 09:42:02.244607 2017] [:error] [pid 5255] [client 10.72.2.42:29847] PHP Fatal error: Uncaught Error: Call to undefined method Location::isTFTP() in /var/www/html/fog/lib/plugins/location/hooks/changeitems.hook.php:175\nStack trace:\n#0 /var/www/html/fog/lib/fog/hookmanager.class.php(193): ChangeItems->bootItemSettings(Array)\n#1 /var/www/html/fog/lib/fog/bootmenu.class.php(314): HookManager->processEvent('BOOT_ITEM_NEW_S...', Array)\n#2 [internal function]: BootMenu->__construct(Object(Host))\n#3 /var/www/html/fog/lib/fog/fogbase.class.php(389): ReflectionClass->newInstance(Object(Host))\n#4 /var/www/html/fog/service/ipxe/boot.php(35): FOGBase::getClass('BootMenu', Object(Host))\n#5 {main}\n thrown in /var/www/html/fog/lib/plugins/location/hooks/changeitems.hook.php on line 175
-
RE: RC-25 boot error when pxe booting.
@Matthieu-Jacquart do you have this in your error logs ?
[Mon Nov 21 09:57:46.787970 2016] [:error] [pid 11741] [client 10.72.2.25:4168] PHP Fatal error: Uncaught Error: Call to a member function get() on null in /var/www/html/fog/lib/plugins/location/class/locationassociation.class.php:118\nStack trace:\n#0 /var/www/html/fog/lib/plugins/location/hooks/changeitems.hook.php(77): LocationAssociation->isTFTP()\n#1 /var/www/html/fog/lib/fog/hookmanager.class.php(185): ChangeItems->BootItemSettings(Array)\n#2 /var/www/html/fog/lib/fog/bootmenu.class.php(362): HookManager->processEvent('BOOT_ITEM_NEW_S...', Array)\n#3 [internal function]: BootMenu->__construct(Object(Host))\n#4 /var/www/html/fog/lib/fog/fogbase.class.php(389): ReflectionClass->newInstance(Object(Host))\n#5 /var/www/html/fog/service/ipxe/boot.php(36): FOGBase::getClass('BootMenu', Object(Host))\n#6 {main}\n thrown in /var/www/html/fog/lib/plugins/location/class/locationassociation.class.php on line 118
-
RE: RC-25 boot error when pxe booting.
@Matthieu-Jacquart upgraded from RC 23-25 myself…I can get an actual machine to image, just not VM
-
RC-25 boot error when pxe booting.
Server
- FOG Version: RC-25
- OS: Fedorea 24
Client
- Service Version: 11.5
- OS: win 7
Description
Getting pxe boot error only on vm below is the output from vm.
0_1479739629627_bootPHPError.docx -
RE: FOG Client stops reporting & working
@Wayne-Workman then, without updates, it seems like that would rule out the .NET framework updates…I will add that I only noticed this after changing from RC-23 to Tom’s working RC_24 candidate. After uninstall/reinstall the .json file was correct, then reboot wiped it. So far, after reverting to RC_23 doesn’t seem to exhibit this behavior after several reboots.
-
RE: FOG Client stops reporting & working
@Joe-Schmitt event viewer, I unfortunately lost that log after uninstall and reinstall of client…
reset token, and uninstall-reinstalled client 11/16/2016 8:44 AM Main Overriding exception handling 11/16/2016 8:44 AM Main Bootstrapping Zazzles 11/16/2016 8:44 AM Controller Initialize 11/16/2016 8:44 AM Zazzles Creating main thread 11/16/2016 8:44 AM Zazzles Service construction complete 11/16/2016 8:44 AM Controller Start 11/16/2016 8:44 AM Service Starting service 11/16/2016 8:44 AM Middleware::Configuration ERROR: Invalid parameters 11/16/2016 8:44 AM Service ERROR: ServerAddress not found! Exiting. 11/16/2016 8:52 AM Main Overriding exception handling 11/16/2016 8:52 AM Main Bootstrapping Zazzles 11/16/2016 8:52 AM Controller Initialize 11/16/2016 8:52 AM Zazzles Creating main thread 11/16/2016 8:52 AM Zazzles Service construction complete 11/16/2016 8:52 AM Controller Start 11/16/2016 8:52 AM Service Starting service 11/16/2016 8:52 AM Middleware::Configuration ERROR: Invalid parameters 11/16/2016 8:52 AM Service ERROR: ServerAddress not found! Exiting.
this isn’t it all unfortunately as I stated before, but I think most of the above is due to empty .json file.
all the “chinese/gibberish” was during the authentication portion when client first starts up…
-
RE: FOG Client stops reporting & working
@Wayne-Workman I also had this occur, oddly enough after running a snapin that forces the client to update via WSUS. I recently added .NET 4.6.1 to WSUS.
yup. here’s event viewer from that client The performance counter name string value in the registry is not formatted correctly. The malformed string is 뢭傞碻�鬋쏄军⍮휒㾲籍봯禵ᦂ瞣㛂⯦闚椂↛抋篾귩恫嗋⸑蓣톽�쾐⨨莐潋㌍胡빌폍伤밧縒�鬋웘趲ප᥀巽뼉랥躎衙┱禌㾬됯㏨궒外㈦慙ﭯ潘ﯦ랢ꤎ懨䄩賩ꗼ�唹훐⩦�ẏ⾟疽褎⌼凴䞛枢ﴙᚅ옝햌Ш↊ᱰ貼Ӗ醑᥆㔥㎦Ὢ苻☍▩臄ꮨ僭烻�釶⧐첨륗ꃕ⽷㢭�ᬓ욄䤘똎ꖷ뜕뷲훴洬勳꓅뛰ⵏ敺铨苌哅쇇寒楣ᗳ땦샄쿆ﳸᚅᄽ鱔�⬈잃䯧浯厃ݖ�麳䋺꺋릎揍쟏ކꞯ봮蒵慻ኋ풭聕慻ꛓ젭ฦ崘ᆶ㾾ّ腳㗢⧹籛䖩蹯ඝ䎈﨨旑䮋굯䗙阪ꍢ佦빏桟᧑禛捲굃쥏�쑚胬�좮圠ߺ쭷䳭瓕㐕꺯墽䣣씳鳎綸ø쿹淗팅嫵䛕髠텊떪㠷醛ୟꯊ핚隂➼㋳쏔晶럤ﷲ顝༷㛲ㇿ灳ᰲ䷯矂퉷₾�䎡똪胉ᜬ馿ꗶ㏏켗ꔙ柄⽱ꉬ蟊贘톙鷤留閸ꗯ䀡膒릹㣩㮃廹죘쓈⛛曬夐뙶빖摷帛룒䚄�됯㍍땫ᢦ戼㑦灰ﻻ�㻩䌲㔔뎤틕慻쪃鈐�㝚ิ뿮⯷浨リ齃鹸ྵ抃똭�ﹹ辗켟䛶渊㝛躴㙎匔ꋅ့畹⅟䅆汐攳섡증뿋蕖멥ꉘᏎ휻︇栿媼楔ꜣ転亥ി医�뽟﷼꼆鹣㣎ᶉꌾ轭끿뙲師߿꼔檑ꢖꪶ羚緓晴埻욽得⡇넃¶鲱鶤᯾ﱘ뤗鈋裂煉⒑貵뎸כּ뉗욻푍붆杍촛깺㛯揝뮳ꄠꍢ饋㛎䳅輧뭩롫㳄䪄☙c豤ᖳ澷督㉁る鞀멒곮綦묭驼浡⩐䘣᧣㿷묶䠗쩆ꎄл㻶ﻟ뉃ڻ耼萐葽쉅탺⻬顈譍钕Ć펰�员䰙⊰벹槚糈줣搗끘贵�㇒ꮃ壕║㫇럐瓥摮˷猉ત榢懺뷵쏝銻㗝舂㊤咧썛嶳붯�अ劵庛╘杼ꩥ�㒽죉褓瀍䏨脖죜볚⒉案랴´뉗槻ʏ䑈㮜㍯쩏齣ௌ᪒嫖ᵤ솭挖錝쯝嚡燀ꪌ뙼ྥ눷腻斤틠ᩆꊥ�껙⮇巙紼糭현䨙ᩰ涏⠒츞掕幪ᒻ찄晅Ῐ�₼ⷩ�봔揗䑦౫덇쟞쨘춣ힼ⛏룛�䤅◩ᑐ宺ꦝ긵睤�薨䭆딐ﰶ췘ք唀劯텆辑䳙㉘骓篙帯㦛菇䑧ላ鳂ʢ͉糨賐൨僔蔱㇢䴝쎄㝣ᘓ찤䯕漣枾拂泇갦᧱な驒懑磷嫬苕➄뤦浧뷚ẋ嚳蚵ꡥ塅₌鈝㾒⁞껡ᤦ䝅握贚夑䁱ᣏꖶ込短␗咎꫁䢖랣䱾뮿愆衰↛赣刬㬞幦沐躻㔨쌷챴禘붍곈樝⠍툚띏瘶␗棐�ⶑ淯↮䤗邷骪톕뛇ם飉簯찍끑蕋�遱ꉆᱭⓂþ们虈뛩䧏씂�襾焢ꆪꔔ썍괽寊氥瞭京�ਖ਼쟴྇茶�翯竽岽䡽ꢎ樳䓰砠શ뗳베宪㚷鹲懹戲�囹鞾㭚ଫꈍ쵓╏系跿塀㋐봏뎲揝�붨䅃�㙥ῼ. The first DWORD in the Data section contains the index value to the malformed string while the second and third DWORDs in the Data section contain the last valid index values.
I got a bunch of “chinese” in my client log when this occurred
also had another warning saying something about registry being open and in use as well
Hope it helps guys.
-
RE: Stand alone RC11 (not upgrade) does not install packages correctly
@Wayne-Workman @Wayne-Workman I didn’t do the wizard, but did run the following
dnf install https://rpms.remirepo.net/fedora/remi-release-24.rpm
after first failure of course…msg returned that it was already installed…then FOG installer failed again.
[0_1475182206245_fog_error_1.3.0-RC-11.log](Uploading 100%)
-
RE: Stand alone RC11 (not upgrade) does not install packages correctly
@Wayne-Workman this failed only as fresh/first install
-
Stand alone RC11 (not upgrade) does not install packages correctly
Server
- FOG Version: RC11
- OS: Fedora 24
Client
- Service Version: 11.5
- OS: Windows 7
Description
When installing newest and only install RC11 packages show as missing…I had to install r 5941 (RC4) and then upgrade
-
System Uptime
Server
- FOG Version: RC-11
- OS: Fedora 24
Client
- Service Version: 11.5
- OS: Windows 7 Pro
Description
System uptime on home page increases with refresh and not accurate at all.
-
RE: Particlone Fails to Start
@Wayne-Workman
"“make sure that both the server and node (via logviewer–>multicast show that multicast session is actually tasked…I’ve had to cancel both active multicast task and active tasks, along with restarting FOGMulticastManager on both server and node, after killing mysql (TASK=8). Restart multicast tasking and it should start right up. I’ve even done a travel node, and can swear to it working. The key is making sure the logviewer multicast from server and node, show same tasking”That’s all I got, not sure how to elaborate much more.
-
RE: Particlone Fails to Start
@Joe-Gill before you start the machines into pxe boot, make sure the task is showing on node will alleviate having to shut them all down each time. Set your Multicast timeout high enough to give you time…mine is set for 5 minutes.