Affected Version(s):
vRD 2010, Build 6.5.2800.0

1. Assigning of default credentials to connections does not work as expected
Symptoms:
The vRD Systemadministrator has assigned default credentials to connections for other users. When then a user logs in to vRD the default credentials do not apply as expected.
Cause:
visionapp confirms this to be a bug.
Resolution:
Has been fixed with vRD 2010 (6.5.2806.0)

2. Errors after updating from vRD 2008/2009 to vRD 2010
A) Backup does not work
Symptoms:
After updating from vRD 2008/2009 to 2010, the backup does not work and reports an error.
Cause:
visionapp confirms this to be a bug.
Resolution:
Has been fixed with vRD 2010 (6.5.2806.0)

B) Passwords have not been migrated correctly
Symptoms:
After updating from vRD 2008/2009 to 2010, password of private credentials have not been migrated correctly and thus are not working.
Cause:
visionapp confirms this to be a bug.
Workaround:
Re-entering the passwords of the private credentials.
Resolution:
Has been fixed with vRD 2010 (6.5.2806.0) for the person, who has migrated the database. Due to an enhancement of the database security, other persons still need to re-enter the passwords of their private credentials after migration.

D) Already existing user-defined roles are not be displayed correctly
Symptoms:
After updating from vRD 2008/2009 to 2010, the permissions settings for user-defined roles within permission administration are not shown correctly.
Cause:
visionapp confirms this to be a bug.
Resolution:
Has been fixed with vRD 2010 (6.5.2806.0)

3. Using local accounts to access a databse
Symptoms:
When trying to log in integrated with a local account to a database, a wrong string for this person will be delivered - necessary for granting access.
Cause:
visionapp confirms this to be a bug.
Resolution:
Has been fixed with vRD 2010 (6.5.2806.0)

4. Read Only access for external applications does not work as expected
Symptoms:
Even Read Only permission has been assigned for a user when using external applications, it is possible for him to adjust the min. and max. wait time.
Cause:
visionapp confirms this to be a bug.
Resolution:
Has been fixed with vRD 2010 (6.5.2806.0)

5. Activating a VNC connection returns an error
Symptoms:
When trying to connect to a remote system using VNC an error occurs.
Cause:
vRD tries to establish the connection using DMS encryption, even it has not been activated.
Resolution:
Has been fixed with vRD 2010 (6.5.2806.0).
Note: After updating to the new version (6.5.2806.0) check the VNC properties of already existing connections and if necessary deselect the option Use UltraVNC Encryption.

This post was last modified: 09-09-2009 12:41 PM by Thomas Hertwig.