![]() Get a second opinion from another "MSP" or engage a trusted VAR you already have a relationship with on the current state of the environment. It needs it's own dedicated infrastructure to be successful.īut hey, don't take my word for it. ![]() The biggest part of a successful VDI is understanding that it should not run on your existing virtualization infrastructure. Server maintenance needs to be performed regularly in order to ensure that your server will continue to run with minimal problems, while a lot of maintenance tasks are automated within the Windows operating system now there are still things that need to be checked and monitored regularly to ensure that. ![]() Each host will be running Windows Server 2019 Datacenter guest VMs for employees to access through something like Spice or No Machine (i.e. You must be licensed properly or when audited you will have a hefty bill to pay later that is retroactive and includes penalties. These host will be running a 3rd party (undecided) solution and NOT Hyper-V. VDI licensing is used with virtual workstations, RDS CALs are used with multi-session terminal servers. After validation, it gets scaled up and more users are added. You may have the best software going, but if your infrastructure to support it isn't up to the task, you won't enjoy a good experience.Ī proper VDI solution should be scalable and a VDI project, once it has reached the implementation stage, should only take 1-2 months to get to validation. ![]() Non-persistent VDI is preferred and is NOT run multi-session. The correct one should be chosen if you intend to go this route. Multi-session capable OS's have widely different use cases. Okay, I think I see the issue(s) here but it'll be high level because you have too much to fix that this forum is not the place for it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |