mac parallels windows 10 rdp keyboard mapping issue

I don't recall having any of this sort of basic problems with Parallels. As a second Beta release, this is extremely disappointing that one has to stuff around with remote connection on a stock standard Macbook Pro. Not sure if I am missing something - wasn't Fusion being refered to in this forum as a 'consumer' product. My configuration is as follows: OSX 10.4.8 MacBookPro 2.33Ghz, 2GB, 160GB HD, 1Ghz network connection - stock standard configuration. I am presuming that I have to be logged into Windows before I can install the VMware Tools. However, when I disconnect from the remote connection, the VM is now sitting there waiting for me to login locally which I can't do as I still don't have any keyboard and mouse. The VM boots Windows, I get the activation screen, I can now connect to it from the remote Mac which allows me to cancel the Product Activation window and get into Windows remotely. I tried going back to the Windows (Bootcamp) and turned the auto login off and then recreated a new Bootcamp VM but now I get a very slightly different problem. ' which is obviously true as the remote computer was in the process of starting to log in when it put up the activation screen. either remote connection are not enabled or the computer is too busy to accpet new connection. Going to another Mac on the network and endeavouring to connect remotely gives me a 'Client could not connect. And yes, I have clicked inside the VM window. Booting up without the USB mouse makes no difference. At this stage neither the keyboard, trackpad nor standard USB mouse is functioning. When I boot the VM, Windows starts up, then proceeds to start the login process and then puts up the Windows Product Activation screen. I also enabled Remote Desktop connections and tested it from another Mac on the network using MS Remote Desktop Connection. I rebooted Windows and confirmed that Windows automaticaly logged in on first boot and also automatically logged back in whenever I logged off.

Prior to this conversion, I edited the Windows registry and set AutoAdminLogin and ForceAutoLogon to true. I used VMconverter to convert my Bootcamp partition. I have search this forum for a solution without success. I am trying to test Fusion with a converted Bootcamp VM and have tried for a couple of hours but I can't get Fusion past the no keyboard and mouse issue.

Mac parallels windows 10 rdp keyboard mapping issue