Hi Jasmine,  Only just had time to revist the problem.  Thanks for the response. Spotted another "deliberate" mistake. I had a /HUBADDRESS=  I gues the installer was sitting there with a error message about invalid parameter.  Corrected this and it's installing just fine.  I'm not normally as bad as this - honest
I'll hold my hands to having made a hash of the VDI assessment agent install.  First mistake was not realising that dns name was supposed to include the hostname as well, the resultant knock on effect is that the agent is trying to talk to the DNS suffix as opposed to a host.  Second mistake was having the HUBADDRESS= on the command line when testing and then leaving it when deploying to about 30 mcahines via SCCM. Partly I forgot to add the parameter and partly I read that the client will use the host name to find the hub anyway - back to mistake number 1 - although I had corrected the DNS name field the agent exe still held the old one. (yes I did download it again).  So having a load machines with the client on but not reporting to the the hub I thought that I would re-install the client with the correct HUBADDRESS. Doing this manually results in an uinstall or repair option, which I found out after it was too late and the /s seems to do nothing when the client is already installed. Now I had a load of machines with a broken install.  OK I thought I'll uninstall the client, through SCCM again, with the /x switch but this time I neglected to add the /s switch thus there were the a load of machines with a hidden uninstall dialog box. What a numpty.......  Anyway I killed off all the install-VDIAssementAgent processes using taskkill thinking that would be it and I could specify the /x and /s switches next time. This seemed to porcess correctly and the folders were removed etc.  What happens now when I try and run the install through SCCM as SYSTEM impersonation it gets stuck with a spawned process called identity chewing up CPU.   If I install manually it goes on OK.  Any ideas how to move on from this stuck identity process. I have not had any machines reboot yet and that may fix it but it was intended to be silent so I don't want ask the users to reboot.  I know a lot has been self inflicted but......  Any help appreciated.
Agent install stuck with identity.exe process