@Sebastian-Roth said in FOG client with dual boot image:
@tomhtil Thinking about this a bit more I can only suggest to copy
token.dat from Windows to Linux and back as a quick solution. I opened an issue on github for this so we won’t forget about it. I see it as a major change we’d need to make in the client and it’s not something we can do quickly.
@EduardoTSeoane said in FOG client with dual boot image:
On my last update the client break to malfunction on a lot of freezed computers that have the client installed on non default path, a little problem with the updaterhelper.
Can you give us some more details on this? I have to admit that I have not looked into the updatehelper code yet. Does it use default install path even if you had it installed in a different location?
Yes, I can… And Yes, I think so on my system.
We have a set of computers freezed, Because We don’t want to add another Freezer exception more, we install the fog client in D:\ Volume that we have unfreezed.
When i update my server from 1.4.2 (client 0.11.12) to 1.5.6 (client 0.11.16). We don’t prevent the computers to update the client, then the update uninstall the old client and try to install the new version, on next reboot the fog client was not there, my conclusion was that it was installed on freezed partition. The result all freezed computers with that client installation path goes down.
But I was thinking about that was a incident with my specific installation and custom configurations and system customizations, so I was thinking that it was not a FOGService problem, but I like to Advertise about take care with own customizations.
If you need more details…