w2k3 session host: vWorkspace 7.5 configuration didn't get applied

Hi there,

we updated an existing vWorkspace v7.2.1 farm at a customer side to v7.5. The farm actually consists of 1 broker (w2k8 server), 1 Proxy-IT (w2k3 server), 3 session hosts running w2k8 r2 (in use for department 1 and 2) and 1 session host running w2k3 (in use for department 3).

Since the update to the current vWorkspace release we are having an issue at the w2k3 session host with the regular users. The vWorkspace configuration did not get applied to the users anymore. We double checked the whole AD security configuration as well as the NTFS security, but so far wasn't able to fix this. At first we thought that it could be solved by deleting the pnshell.ini within the user homes because we got only informed about missing drive mappings, but we found out that the pnshell.ini did not get re-created as soon as we delete it and that in front of it no change is written to this file. Anyway the pnshell.cmd as well as the pnshell.exe are getting executed for every user, but the pnshell.exe window do only show for a blink of an eye. We would guess that it closes down after the 1st or 2nd line.

Can there be an issue with the system DSN? We already created this new, but when we logon to the session host with a regular user and try to open the vWorkspace management console then the session host is asking for the configuration of the database connection.

Any hints?

Thanks,

Holger