roc1479

Disk2VHD will do what you're looking to do. It basically creates either a VHD or VHDX which will contain an entire image for you to use with your Hypervisor. You'd then copy the vhd or vhdx to your hypervisor, create a vm, give it appropriate ram, cpu etc and use the vhd or vhdx as the hard drive. Should boot right up. You may have to reconfigure network.

Yes to be able to print on their home printers you'd have to be sure printers are redirected on the RDS host. Just be aware that if your RDS host does not have a driver for their device, that may cause problems for you. Also, 1 thing I've learned about RDS, the less printers you have on it, the better.

Yes its a shame you couldn't get it to read the tapes. I don't like it myself when problems like this happens, but the reality is that they do from time to time. The VM route is the way to go, you should be fine.

In that case, I would setup the VM setup as a temp solution to server 01. You would have to promote it, seize the roles, make it a gc and setup any necessary services (dhcp, dnc). Make sure the VM is replicating and all is well with clients. Demote server 01 and remove it completely from the domain and also remove any active directory services from it. Remove any traces of server01 from AD, Sites and services etc.. From there, you can either rebuild server01 from scratch, which i would do, or promote it again and pretty do the above to reclaim roles and services.

Remote Procedure Call (RPC) should be running on both servers. Confirm that it's running on both, start it if its not. Does server01 have roles, is it a GC? What about server02?

Is RPC service running on both servers? System state recovery is not ideal for DCs, anyway to do a baremetal restore from a recent backup? Can the servers talk to each other?

You can disable inheritance and add authenticated users Remove everyone and make sure the administrators group is also addedThat should take care of it for you.

I've had problems running any variants of ESET on server 2008 R2. Completely removed and have been running Viper through Control Now about 4 years now with no issues. I've had the same type of issues described in your OP and since removing ESET, haven't had any issues.

Did you load remote resource on the RDP client? This should allow you to see all RemoteApps on the RDS server. If you double click any of the resources listed, you should get a popup for further configuration, which you should follow through to connect to the remoteapp

Yes I'd start with a dcdiag /v and post the results here.

Hi, If your clients are getting IP, DNS, Gate info correctly, and you have them going through a proxy, I would start troubleshooting the proxy.

How many RDS users will you have?

No but it does copy over security

Sounds like you may need to enable routing on the vlan interfaces

Why not just move them and re-share them? You can use robocopy to do this.