Bugs Fixed in v3.4-SP1

The following bugs have been fixed in the HyWorks v3.4-SP1 release:

#	Subject
28463	Local user import is failing when multiple teams are specified using semicolon. The bug is fixed now and administrators should use "#" to provide multiple team names.
28220	[Desktop Agent] Domain join operation fails when administrator has provided AD Path in customization tab with spaces. E.g., AD Path=OU=VMS, OU=HYWORKS-QA, DC=ACCOPS, DC=LOCAL. The bug is fixed in v3.4-SP1.
27964	[Desktop Agent] In a specific environment, HyPrep is failing with error "A constraint violation has occurred ", eventually the error is corrected to suggest that user is not having adequate privileges to unjoin machine from domain.
27955	Servers remain in 'Draining' state after changing the desktop creation type from 'Provision On Demand as Per Capacity Plan' to 'Provision now' and recomposing the pool. The bug is fixed now, HyWorks will be processing the servers as per configuration.
27576	Desktop session is getting logged out on user session disconnection, though it was configured to be logged-out after sometime for assignment type as floating on-connect. Fixed in this release.
27474	HyWorks does not record the session if it was first connected by user from HyWorks clients over the internet and then directly via Console or RDP. New enhancements are integrated to handle the directly accessed desktops.
27450	Upgrade from v3.3-GA to v3.4-GA fails with error "Object reference is not set to an instance of object". The issue is fixed in v3.4-SP1 setup and upgrade from previous versions should work fine.
27152	When the secret of configured Azure connector is expired, on pool edit a confusing error is shown as: The source desktop belongs to session provider which is inactive or in 'Not Reachable' state". Appropriate implementations are done to show Azure exceptions for simplicity and clarity.
27108	In some rare cases, deployed VMs were not getting joined to domain and computer name was not getting changed. The issue is fixed in v3.4-SP1.
26165	User assignment is not getting removed from reservation even on enabling VM retention option after logoff and Object reference is given in controller logs. Fixed and merged in current HyWorks v3.4-SP1 release.
25780	Controller installation fails with Azure SQL. HyWorks v3.4-SP1 can be installed with Azure SQL.
25479	In some cases, desktop agent status was shown as not responding with cause shown as certificate bind issue. The issue is found to be with the certificate binding process, now agent will check for any such issue on service restart and will try to rebind 10 times before declaring it as failed.
25049	Addition of session host server into HyWorks controller was failing with error "Object reference is not set to an instance of an object", when the controller was configured with Oracle as connector. Fixed in this release.
24288	Un-registration of desktop from domain controller fails with exception (0x8007200A): The specified directory service attribute or value does not exist. This is resolved in the current release.
23463	Controller uses VM-name instead of computer name to unregister from domain controller and thus fails if administrator has kept VM-name and computer name different.
22548	If user enters localhost as Database address while installing the controller, DB location is not getting resolved to hostname.
22370	HyWorks DVM Tools setup reinstalls built-in USB redirection driver, though latest one is already installed. This was not having any impact but fixed to handle the condition in v3.4-SP1.
18966	DVM Tools Lite should not get upgraded with DVM Tools Full from VMs page for managed session host servers. As it can change the machine type.
18289	Japanese Sync framework is not getting installed on Japanese Windows Server (Japanese Sync FW is not embedded in installer) Appropriate integrations to enable Japanese sync framework installation with HyWorks Controller is done in v3.4-SP1.
6101/13273/23491	In some case, HyWorks Controller Management Console becomes inaccessible after organization deletion. The issue was because of incomplete deletion of organization and its associated configurations. It is fixed in v3.4-SP1.