We are going to look at Azure Bastion, which is a new resource that you can deploy in your virtual network. What you see here is an Azure Bastion resource deployed in my virtual network. My-Win-VM is one of my Windows virtual machine that I want to RDP to. Note that this virtual machine does not have a public IP address. Azure Bastion integrates natively with the Connect button in the Azure Portal. Since Azure Bastion is deployed in my virtual network, the platform automatically shows the Bastion experience in my Connect slider. Here I can enter the credentials for the virtual machine to be used in my RDP session. I enter my RDP session into my virtual machine directly in the Azure Portal. As you notice, the session is very responsive and fast so that I can be fully productive with a secure RDP session in my browser over SSL. This is all without the need of any public IP on my virtual machine.
so now let's go over to VMware Workstation and I'll show you how to access virtual machines using RDP the first thing we want to do inside view my workstation with a virtual machine that we want to access using RDP is of course to enable RDP in the Windows operating system to do that I've got this Windows Server I'm going to click on the console and then go full screen with control all enter then here inside server manager where it says remote desktop i'll click on disabled so that we can go into the system properties here and allow remote connections to this computer effectively enabling remote desktop I'll click on Windows Firewall here with advanced security because we'll either need to disable the firewall which of course isn't recommended or to open an exception or open a port and then to create an exception or open a port for RDP to open a port for RDP if we go up here to the inbound rules and then scroll down we'll find a remote desktop user mode down here I'll double click on that and then we'll just need to check the check box here to enable the rule I'll say ok and we can see now the Remote Desktop TCP in firewall exception is enabled you see yes right here under the enabled column so we just enabled RDP to come in through the firewall I'll say ok and then I'll say ok here on the system properties and we've been able to RDP to be allowed in to this virtual machine the next thing we need to find out is exactly how to connect to this virtual machine remotely so let's go down to the network connection I'll just right-click and open the network and sharing Center I'll double click on the Ethernet adapter go into details and here we see that this virtual machine has an IP address 10 dot 0 dot one dot 115 that it received via DHCP just from looking at IP configuration I could tell that this virtual machine is in bridge mode that means it's connected directly to the physical network interface on the host computer that's why it received an IP address that's on my local LAN will test the RDP connection first with the virtual machine in this bridge mode and then we'll go back and we'll change the virtual machine to NAT mode which is actually the default configure that to allow RDP in and then we'll retest so let's go ahead and close this out I'll get out of the virtual machine and then let's go and let's run remote desktop I'll type in the IP address 10.0 dot one dot 115 I have not tried this before so we'll just see if it works I'll go ahead and log in as myself I'll accept the certificate say yes and there we go we successfully connected to the virtual machine using RDP I can go in here and verify yes indeed it is 10.0 at 115 it's the same IP address it's the same operating system it's the same virtual machine that's running over in workstation so let's exit the RDP connection here and you can see back on the virtual machine's console it automatically logged out the console user you have to log back in here I'll login as David and we're back in so if we look at this virtual machines configuration we go down to settings and on the network adapter indeed it is in bridged mode so it's connected directly to the physical network so now let's change this to NAT mode this is going to really put the virtual machine behind a virtual NAT device in other words it's going to be on its own network it's going to get a different IP address still via DHCP but assigned by VMware Workstation typically if I want to connect to my virtual machines remotely I prefer the bridge mode just because it makes life simpler the virtual machine is on the same network as everything else and I don't have to worry about NAT so if your virtual machine is configured as that and you want to use RDP you can follow the instructions I'm about to show you or it may just be easier to configure it as a bridged virtual machine I'll say ok here and then to allow the RDP to come in we're going to have to configure net but first let's see what IP address this virtual machine receives notice how it got disconnected from the network because it's not on the same network anymore as the host computer it's behind in that device so I'm going to right click here and say open network and sharing I'll go back into the Ethernet device and notice now it has an IP address on the 192 168 Network and it is dot sixty five dot 130 I'm just going to have to write that down 192 168 dot 65.1 third so let's remember that because we're going to have to use that when we configure net so if we tried to connect to that 192 ones see 8 IP address from the host network which is the 10 network in my case it's not going to work there's no way for that traffic to route through the networking get to this virtual machine what we need to do instead is go to our virtual network editor which is here under edit virtual network editor and then we're going to have to go into the net Network which is VM net 8 then go down here to the NAT settings well first take a look at this here's the subnet this is where the IP address came from that was assigned to the virtual machine if we go into DHCP here we can see the range so we receive the very first IP address in the range what we want to do is to tell VMware Workstation which is on the host IP address or on the host network that when a connection comes in on a particular port and it's RDP it needs to go to this particular virtual machine that's over on the NAT network so I'll go into the NAT settings here and then what I'm going to do is to add and I'm going to set a port on the host now if I use 3389 that's going to prevent me from connecting to the host remotely using RDP of course 3389 is the TCP port that RDP uses in this case so let's configure 3390 so we're going to increment by 1 and here I need to enter the virtual machines IP address which is what we wrote down 192 168 that's 65.1 30 and then the virtual machine port which is going to be 33 89 so for description i'll put in net for RTP i'll say okay here we've got this configured I'll say ok and I'll say ok again ok now if we use our remote desktop client we're not going to connect to that 192 168 IP address we need to connect to the IP address of the host computer : 33 90 because that's going to then be translated with that into the 192 168 65.1 30 : 33 89 which is going to be the port for our DP on the guest operating system or this Windows Server 2012 that we're running as a virtual machine so here on the host operating system I'm going to right-click on the network go to network and sharing I'll go to the Ethernet adapter I'll go to details and a host IP address let's write this down is 10.0 dot one dot 110 and then we're going to connect to 33 90 so if we close that out then open up remote desktop will connect to 10 dot 0 dot one dot 110 : 33 90 that's going to be translated into the 192 168 IP and the port number 33 89 for RDP so let's give it a shot it's encouraging that we get a username and password prompt I have not tried this before my first time notice we're connected at the top to 10.0 dot one dot 110 but inside here if I go down to the virtual machine and I right click on network and sharing a Ethernet details look at the IP work connected to 192 168 65.1 30 even though up here it says we're connected to 10 dot 0 dot one dot 110 that's all thanks to net thanks to vmware workstation x' network address translator which is translating the 10 net to the 192 and the 3390 to the 3389 so that's how you connect to a virtual machine with RDP when it's on the VMware Workstation NAT network and that ends my demonstration on connecting a virtual machine via RDP you
hi guys today I'm going to show you how to convert any physical PC with a copy of Windows on it into a virtual copy of that system now this is called dis devii HD or p2v physical to virtual now it's a really simple process guys you just go over to their website so it's a sysinternals dis to be HD so disc 2 v HD top result you'll see it the less they're from TechNet go ahead follow the link download it from here version 2.0 1 it's quite an old piece of software once it's downloaded just run it extract the file so just extract somewhere you know it's gonna go to downloads done let's go ahead and open our downloads there it is and then within that we will then have the executable application so if we double click on this what its gonna do is it's going to launch the software that allows you to create a virtual image VHDX file or VHD file from your actual computer so the reason this would be important is if your machine is showing its age you don't really want to reinstall the operating system but you might lose the applications or some of the data or you might not be confident enough to kind of do it yourself this is a much simpler and easier way that allows you to create an image effectively a snapshot using the Microsoft writer Shadow Copy Service and then obviously you can import it into hyper-v or VMware parallels VirtualBox any virtualization software effectively so what I'm going to do is I'm going to show you this now so if we just drop down this box here you'll see the volumes that you can snapshot effectively now uncheck the actual volumes that store data and just backup windows which will be seen in the hidden volume partition for recovery system recovery and what we want to do before you do this just make sure that your writers are actually in a stable State okay so you right click on command prompt where as administrator we're gonna go to VSS admin and we do list writers okay so what this does is it checks the writers of the system as long as they're all stable you should be fine it'll create a snapshot fine and you'll be able to virtualize your operating systems this applies to any server any client computer anything you want to virtualize effectively from a physical machine so as you can see there you know no air no air no error let's scroll up to the top here no error all the way at the top you can see there's no errors there at all which is good so that means that the snapshot service will run correctly when we try and actually create a snapshot with disk to be HD so let's go ahead and click create what that's gonna do saver VHDX file which we can import into hyper-v to the desktop so let's go create what I'm gonna do is let that run through that I'll probably take half an hour to an hour depending on how large your volume is I'm gonna see on an SSD here so if we right click task manager performance and then go down to disc two you'll see that it's on an 850 Pro and this is a 500 Meg read and write drive so it should be able to do some pretty good speeds and and snapshot that volume pretty quickly for you on the desktop you'll see that it starts to create that VHDX file which we can then import into hyper-v afterwards so what I'll do is I'll place a link in the description box below for this product a disc the VHD software and just to clarify what this is doing right now is actually snapshotting and copying the volume of my actual physical computer here that I've got in in the office as you can see it's a Windows 10 computer and all the applications all of the data that's stored on this machine will then be copied to a VHDX file on the desktop and from there we can then obviously back it up or run it in a hype of the environment or a virtualized environment so the idea is you can keep the machine running without having to sacrifice the hardware you can actually upgrade the hardware to any computer you like so in this case an i7 16 gig of ram and SSD obviously that's an upgrade from potentially what could be I don't know Pentium 4 in some cases and 256 Meg of RAM so that you get the idea and that's why you can do this and why it's quite in business the disk export to VHD completed successfully so what we can do is now close this volume down and obviously you can see on the desktop here we have this Corsair volume now if we look at the size of this it'll show that it's 85 gig now what that means is that is everything contained within a file a compressed file that you can import into a virtualization software so it's a hyper vaca to a hypervisor effectively okay so now we've done all that we've got the VHDX file on the desktop let's go ahead and open hyper-v manager now this is the same principle on a server operating system as it is to Windows 10 Pro go ahead and create your new virtual machine and then just go through and cut what it wants I'm going to call it Windows 10 Pro P to be physical to virtual ok that's how it looks in theory that's what we're doing okay generation 1 next I'm gonna give it 4 9 6 gig of ram dynamic memories fine use the external switch next and then finally we're going to use an existing virtual hard disk now it's browse to on the desktop there it is corsair open that click finish and then the last thing we want to do is just right click settings and give it all 8 cores in this instance of the i7 processor ok so if we now go ahead and double click this to start this we're going to minimize the hubba theme manager down go ahead and click the start button you'll see it booting into itself in this instance but in any other environment this would be you physically creating a virtual machine out of a server that was maybe dying or dead on the hardwood that was running on but now is running you know perfectly so as you can see I'll log in to this own password and then on the desktop there we go exactly the same as the desktop in the background you can see that as the p2v folder all of my icons the software this is an exact replication of the machine in the background here ok so that's pretty much it guys you've gone ahead and created a virtual machine from a physical machine and that's p2v that is dis to VHD i hope you enjoyed it guys check the link in the description box below check my facebook page if you enjoyed the video as well and as always I'll see you next time some more IT tutorials see you later