@Arjenbulkens I would still try the method @george1421 mentioned just in case (run the script manually and see if any prompts show up). I use snapins quite frequently and have to test using this almost every time. Something is hanging it up and the most common issue for me is whatever I’m trying to run prompting for user input. The snapin method already hides stuff, but it may still be “trying” to prompt the user invisibly.
@Hanz said in FOG 1.5.6 pushbullet Plugin not functioning:
@fry_p lightspeed…I eventually figured it out thank you though
I use lightspeed too! Relay and the rocket filters. Still getting the hang of them tbh. Glad you got it
@Hanz I had re-categorized “api.pushbullet.com” from a blocked category to an allowed one. It all really depends on which filter you use. I’d try whitelisting whatever permutation of all of the subdomains of pushbullet.com your filter uses. It may involve something like:
*.pushbullet.com
or if your filter is like mine, there is a checkbox for all subdomains.
If you still are having trouble, let us know what kind of filter you have.
@BSZAdmin said in Hostnamechanger fail while renaming client inside the domain:
Hey guys,
are there any suggestions meanwhile?
Thx
I myself do not have any suggestions, but we appreciate your patience through @Sebastian-Roth looking through the client stuff this weekend. I feel that you already know this, but as a volunteer developed platform, sometimes we have to wait a bit for the developers to find free time to look into issues. I’ve been in that boat myself before. If anyone does have anything to add, I’m sure they will chime in.
@SKasai From the fog.log excerpt you posted, this appears to be regular behavior. I checked a log on one of my clients, it matches exactly. Correct me if I am wrong everyone, but I think the client checks to see if it is joined regardless of if it is already joined. This is only speaking to the fog.log message. It appears to me that the FOG client is successfully “talking” to AD as well judging by the “already joined” message.
May I ask what other behavior this is exhibiting? Is it trying to reboot to change the hostname endlessly? If not, and the only symptom is the log message, I myself would not worry too much about it as my clients also do the same. Others, please correct me if I am wrong!
@bogle Ah ok. I don’t know how the cloning would affect the intricacies of a web server. Please feel free to start a new thread if you run into any troubles with the windows imaging later.
@mkeane There is an article on the Wiki where you must perform some steps to maintain control of your FOG client hosts when migrating servers located here: https://wiki.fogproject.org/wiki/index.php/FOG_Client#Maintain_Control_Of_Hosts_When_Building_New_Server
Please let us know if you have access to your old setup still and we can most likely help you.
If you do not, I will defer to the other experts here to see if it is possible to make this work.
@bogle Forgive me if I am wrong, but in a VMware setup, are you not able to use the built in clone/export feature to make an exact copy of that VM? I believe if that is true, that would be the easier method. You can then customize things like the IP and hostname on the copy after it is imported to the other host.I am thinking FOG may not even be necessary in this case for this exact use. I mainly use FOG for “base” images (base install of an OS tailored a little bit to the model or use-case) and customize afterward.
If I am indeed wrong, which i may very well be, it would help the other folks to help you if you provided more info. For instance, may I ask the FOG version you are on?
@SBrady I myself have been bitten by web filter issues before on my linux FOG box, so no worries there haha! If you need any additional help or if you run into any other issues, please feel free to open another thread.
@Mokerhamer I wanted to clear up my first reply. I’m sorry, I didn’t want to seem so negative and I didn’t fully understand what this encompassed. I apologize if I came off as a meanie. I now see you have really good ideas/plans (and the equipment to back it up). Thank you for supporting the community through awareness and testing. I wish you the best for your trials and await the results!
Though I like the enthusiasm, it may be my pessimistic nature talking, but I think there are too many variables to properly “benchmark” FOG. FOG’s claim to fame is how versatile it is, running on many different distros on very different hardware, going along very different network types and scales, etc. Even building a reference image can differ greatly. Unless you have the exact same type of disk (NVME, SATA SSD, Spinner) with the same exact version of the OS with the same procedure to set up said image, you will get the “dirty” results. So even if you have everything procedurally and hardware-wise replicated from test to test, you will only be bench marking that particular procedure and hardware. So if some other user with an entirely different setup was to look at your benchmarks without understanding this caveat and got different performance, he/she may think something is wrong. Just my two cents.
@Sebastian-Roth Haha no problem! Please let me know if I can do anything. No rush on my part, but without the coding know-how, testing is all I can do! I actually impressed myself by understanding some simple logic in the different php files that make up these plugins. Oh, and some of the API methods. But that’s it lmao
So here is where I’m at. I created a test Slack environment with the free version with a username of “@Paul Fry” and a channel called “#test-channel”. The FOG web gui seems to not be able to pull this info with the legacy token that slack generates. I tried the combinations of the token with my username by itself and the channel name by itself to no avail. I made sure to include the necessary character before each item. Both generate the following error:
This may be a red herring, but the slack api documentation is saying not to use the channels.list method that is used in the current plugin: https://api.slack.com/methods/channels.list
They say to use the newfangled conversations API that uses the method conversations.list instead. I am no coder so I can’t seem to figure out how to test this, but here is that API page: https://api.slack.com/methods/conversations.list
This doesn’t explain how it can’t pull a username from the site however. The users.list method is still supported. I believe the FOG plugin uses this, but somehow still can’t find my username.
As an addendum to all of this, slack seems to be REALLY REALLY wanting to move away from what they call the “legacy token” (what we are using for the plugin) and instead wanting to use their apps platform. I do not know the viability of using this platform, but it looks pretty simple. The info can be found here: https://api.slack.com/custom-integrations/legacy-tokens
I may have time to poke around for a bit this weekend still, but my lack of coding fluency is really showing as I try to decipher what the heck slack wants us to do now.
Pinging @Sebastian-Roth just in case he is curious. You can find the OAuth token (legacy token) on this page when you are logged in (about half way down the page after all the dreck about how you shouldn’t be using it lol) : https://api.slack.com/custom-integrations/legacy-tokens
Cross posting this as it was what I thought was a similar issue. Probably not the case here, but here it is anyhow.
https://forums.fogproject.org/topic/13486/fog-1-5-6-pushbullet-plugin-not-functioning
I could poke around with this plugin if need be. I don’t know much about slack but if it is free I’ll throw my hat in.
So, this is really dumb on my part… It was our web filter blocking the calls out to pushbullet. It now displays the email and name in the table and the GUI after I whitelisted it. I will double check that notifications are working tomorrow, but this is looking like a whoopsie on my part. Most likely solved.
I forgot to mention in my OP that I can post any logs that are needed or errors that may pop up. So far, no errors but it it is not functioning. I wish there was visibility into the pushbullet side of troubleshooting…
EDIT: Where might I find the code for the plugins? I can take a look but I am no expert. Not trying to rush this, just might be a fun challenge for me if I am able to figure it out.
EDIT 2: found it and peeking through now. So in the DB, this is what I find:
Token is there, but no email or name, just like the GUI displays.
Digging further.
@Sebastian-Roth said in FOG 1.5.6: Auto resize is unpredictable:
@fry_p On first read this doesn’t sound related to me but we’ll see. I know you are very busy right now but would you mind opening a new topic with this one as well and post more information there? Picture of the error would be great!
I figured a new topic may be in order. I will open one up if I have time the beginning of next week when I would be able to replicate. If I am able to get some time I will gather as much info as possible including error messages and pictures.
@Sebastian-Roth sorry it took so long, but I finally was able to create a separate thread in bug reports. https://forums.fogproject.org/topic/13486/fog-1-5-6-pushbullet-plugin-not-functioning
We are in the midst of reassembling classroom tech after the custodians did their cleaning so that is what caused the delay.
Just want to chime in to say good job everyone! I would have thrown my hat in for testing fixes if I wasn’t sweating my buns off in hot school buildings reassembling classroom technology. I have experienced a pattern of right after uploading an image, as the upload is complete and the machine attempts to come out of sysprep, I get an error. Now I am not sure it is related to this, but I heard someone else having the same issue. After re-deploying to the very same machine with the image that was just captured, everything works just fine. Regardless it looks like you guys already have a good idea of what is going on, so I’ll shut up now :D