Trunk version of Fog, old fog client. Will this work?
-
I’ve just rolled out a new trunk install of Fog. However, I had used standard 1.2.0 to image out 900+ machines earlier this year. As such, they have the old client.
Will the old client function with the trunk version of Fog? I know I’ll not get some of the new features, but a reimage for each machine is not feasible at this time. I plan to push the new client out, to make sure they all get it, but in the middle time, I don’t want to screw anything up.
TLDR:
Old fog client, new fog server, same IP, will it work until I can update the client on each machine? -
@Bob-Henderson Yep. Trunk maintains legacy client support.
-
As @jbob said, yes it’ll work.
Would I recommend it? Nope.
-
@Wayne-Workman said:
As @jbob said, yes it’ll work.
Would I recommend it? Nope.
Can you elaborate on why? My primary usage for the client at the moment is domain join after image and client rename, no snapins or anything. I’d just like to get this new version rolled out before our major summer imaging starts.
-
@Bob-Henderson said:
Can you elaborate on why?
Security concerns. Most people don’t recompile the old client to use a pass/salting other than the default, and don’t change the web side’s encryption from the default either. To make matters worse, most people use their domain’s administrator credentials too, instead of using a custom account with stripped down permissions that is only allowed to do domain joining.
That and - the developers are not developing the legacy client anymore. From my understanding, it doesn’t work on Windows 10. I imagine future updates to older versions of windows might break the legacy client as well.
There’s no reason not to update. The new client is more robust, comes in an MSI, has installation options, and a far superior encryption model.
Saying “Well… the legacy client works, I’ll just keep using it” - well that’s like saying a shovel works for digging a hole. Sure it works - but in FOG Terms, we’ve made a piece of heavy equipment available to you for free - and that equipment has an “easy” button as well.
-
Oh, I agree with all your points, and I fully plan on rolling out the new client with all new images.
My concern is for the imaged machines that are already out in the wild, with the old client installed. Since I’d be removing my 1.2.x install and replacing it with trunk, I wanted to make sure that the old client would still be able to ‘phone home’ as such and perform it’s duties with the newer server.
All of my new images have the new client included. This is more of a stop gap for the ones already out there. Wanted to make sure I don’t leave them in trouble until I get a chance to image them again, which will be over the summer.
-
@Bob-Henderson said:
I wanted to make sure that the old client would still be able to ‘phone home’ as such and perform it’s duties with the newer server.
They can.
Wanted to make sure I don’t leave them in trouble until I get a chance to image them again, which will be over the summer.
There are two major threads on updating from the old to the new. Successful deployments (including the one I did at my work) have only used Group Policy so far. You don’t need to wait until summer to update. But that’s up to you.
-
That’s also in the works. Again, it’s for the stop gap in between time. The clients are laptops that students roam with, and due to them being on wireless with cached logins, group policy takes longer than I’d like to roll out.
I’ll throw it into PDQ deploy though, that should handle it pretty fast. Thanks for your help and input!
