When moving images into a different group from the one they were uploaded into, important attached metadata, such as file annotations and rendering settings, may be lost. This may especially affect moving data into a group with more restrictive permissions. See #10419 and #9610 for further details and to leave comments on your experience with this problem.
Depending on the group permissions, you may not be able to move projected images nor the original images that they were created from, into a different group (see #11532 for a work-around or to comment on your experience). Moving a dataset containing projected images may result in an error when trying to view the projected images, and the original image may be lost. See #10262 for further details.
The development server included with OMERO.web does not work under Windows XP. This server is included to allow you to easily evaluate and develop the OMERO.web component. As it should not be used in a production environment, while an inconvenience, this should not stop the deployment of a production version of OMERO.web. See OME forum topic.
On Windows servers not all binary files corresponding to a delete may be removed from the binary repository. See Binary data for more details.
Under certain circumstances building OmeroCpp can fail with “ld: symbol(s) not found”. You can find further details, a potential solution and make any comments on your experience with the problem on #3210.
The new security features prevent users from launching OMERO.insight via Java Web Start using the standard system security settings. The system wide setting needs to be changed in preferences, and this would have security implications. We are looking into code signing to resolve this issue.
Under older Ubuntu installations, the ‘import folder’ option in the desktop clients currently does not work.
Some files generated by an OMX system have a pixel type of float and a large dynamic range. While the files import into OMERO they are currently not viewable. This fix would require deep changes to several parts of the code and we have chosen not to make the changes yet. See #3256.
Enabling synchronization of LDAP on user login will result in LDAP being treated as the authority on both group membership and also the available groups. Any groups defined in OMERO and not in LDAP will result in users being removed from these groups. The groups will still exist in OMERO but user membership will be treated as being defined by LDAP alone.