You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to build an omnissa thin client, and I noticed some bugs in thinstation-ng :
First, omnissa autostart doesn't work. The message (in logs) tells options fullscreen and allmonitors can't be used together.
I couldn't find any allmonitors option in conf files, and didn't find the way to disable it. Disabling fullscreen option in SESSION options makes the omnissa autostart to work, though (and in fullscreen mode !).
I tried a chmod -x on this file in chroot, before a new build, but error message still present. It seems the executable bit is added during build process.
The service can't launch (error message during client start).
Have a nice day
E.T.
The text was updated successfully, but these errors were encountered:
trezel,
on earlier versions I changed after the first build process in vmview/etc...
After the next build it was in the iso .
How large is your image with omnissa, I have 700MB, this does not start as ISO under iPXE.
Don gave same hints, I need to check this and your good described way to boot with iPXE.
But in general he imag is much larger, before I was under 500MB
Hi,
I'm trying to build an omnissa thin client, and I noticed some bugs in thinstation-ng :
First, omnissa autostart doesn't work. The message (in logs) tells options fullscreen and allmonitors can't be used together.
I couldn't find any allmonitors option in conf files, and didn't find the way to disable it. Disabling fullscreen option in SESSION options makes the omnissa autostart to work, though (and in fullscreen mode !).
Second, during building, I saw an error message :
I tried a chmod -x on this file in chroot, before a new build, but error message still present. It seems the executable bit is added during build process.
The service can't launch (error message during client start).
Have a nice day
E.T.
The text was updated successfully, but these errors were encountered: