Problem with updating old Client / SSL folder doesnt exist
- FOG Version: 1.3.3
- OS: Ubuntu 16.04
- Service Version: 0.1
- OS: Windows 7 PRO
we have made a fresh FOG Install.
We have an old FOG runnning (1.1.0) We exported all our Clients ( around 300 Clients) But i dont understand the procedure to Update the FOG Service.
i found this Article
i found out that it has something to do with ssl
i have to copy /opt/fog/snapins/ssl from the old Server to the new one
but here is the Problem, i found this folder on the new server, but the old server didnt have this folder :( what can i do to maintain control of existing hosts. old seever is running Ubuntu 10.04
@Wayne-Workman if there’s enough demand for such a snapin I can make it (It just requires some know-how concerning the design of the legacy and new client).
@Senior-Developers @Moderators @Developers @Testers
Concerning the Migrate FOG article, I purposely left out instructions concerning the removal of the old fog client and deployment of the new fog client, and I left out instructions concerning an IP address change/DNS name change where the old & new clients are concerned.
There are lots of ways to go about this, but I wanted to get the agreed upon way we recommend doing it.
At my old job, I used group policy and startup scripts and msiexec, but not everyone has Active Directory.
I also remember trying very hard to craft a snapin for the old client to remove itself and deploy the new client but I never got it to work.
It would be nice if we had a tool that stands on it’s own to perform the removal of the old client and the installation of the new one.
@nomercy81 I dont’ know what you mean “control”? The old client is functional (though I would still recommend updating).
Here’s some information on the new client:
In particular, I might suggest starting here so you can do a "network deployment"
You will need to figure out a means to remove the legacy client though, of which I don’t have any “best examples”.
ist there any chance to get the old clients easily updated to the new one? so that the new fog can control all updated clients?
@nomercy81 You may also be highly interested in this: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG
FOG 1.1.0 did not have the “new” client and these folders did not exist.
Chances are, when you updated, you didn’t update the FOG Client on your host machines. This ultimately means you will not lose control of your hosts.
You might lose the ability to join to the domain, temporarily, as the FOGCrypt password should be set in the now legacy labelled form field. (For both the default global and host ad fields).