On 2015-12-14 11:43, Sergey Manucharian wrote:
> Excerpts from Peter Grehan's message from Sun 04-Oct-15 13:11:
>> As of r288524, bhyve has preliminary support to run Windows in headless 
>> mode using UEFI firmware.
>>
>> Since it's headless, the install process consists of modifying the 
>> Windows install ISO to include an 'unattend' XML script that automates 
>> the install, and also inserting the virtio network driver currently 
>> required by bhyve.
>>
>> This has been tested with 64-bit Windows Server 2k12r2 and 2k16 tp3, and 
>> Windows 10. The server versions are recommended since they have serial 
>> console support, whereas the desktop install is a black-screen experience.
>>
>> ISO repack instructions at:
>>      http://people.freebsd.org/~grehan/bhyve_uefi/windows_iso_repack.txt
>>
>> Install/run instructions at:
>>      http://people.freebsd.org/~grehan/bhyve_uefi/windows_install.txt
>>
>> Please give this a try and report back on how it goes.
>>
> 
> That's really cool! Thanks for the instructions!
> 
> I've installed Windows Server 2016 with no issues on a ZFS volume. Works
> fine. I can get the command prompt, set up IP address and so on.
> 
> However I cannot get Remote Desktop connection working. I tried to
> (re)enable it from the command line:
> 
>  C:\Windows\system32>reg add
>  "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server" /v 
> fDenyTSConnections /t REG_DWORD /d 0 /f
>  The operation completed successfully.
>                              
>  C:\Windows\system32>reg add
>  "hklm\system\currentControlSet\Control\Terminal Server" /v 
> "AllowTSConnections" /t REG_DWORD /d 1 /f                              
>  The operation completed successfully.                       
> 
>  C:\Windows\system32>net start Termservice                                    
>  The Remote Desktop Services service is starting.                             
>    
>  The Remote Desktop Services service was started successfully.
> 
>  C:\Windows\system32>ipconfig                                   
>  Windows IP Configuration
> 
>  Ethernet adapter Ethernet:                                                   
>    
>    
>    Connection-specific DNS Suffix  . :
>    Link-local IPv6 Address . . . . . : fe80::2cb4:3a4d:dff5:9f0c%3            
>   
>    IPv4 Address. . . . . . . . . . . : 192.168.4.5                            
>   
>    Subnet Mask . . . . . . . . . . . : 255.255.255.0                          
>   
>    Default Gateway . . . . . . . . . : 192.168.4.1
> 
> But rdesktop cannot connect:
> 
>  $ ping 192.168.4.5
>  PING 192.168.4.5 (192.168.4.5): 56 data bytes
>  64 bytes from 192.168.4.5: icmp_seq=0 ttl=128 time=0.314 ms
> 
>  $ rdesktop 192.168.4.5
>  ERROR: 192.168.4.5: unable to connect
> 
> Any ideas?
> 
> Thanks,
> Sergey
> 
> _______________________________________________
> freebsd-virtualization@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to 
> "freebsd-virtualization-unsubscr...@freebsd.org"
> 

You likely have to allow it through the windows firewall.

Last time I had to do this from a command prompt, i used netcmd or
something, I don't recall now, it was 7 or 8 years ago.

-- 
Allan Jude

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to