These are commonly asked questions we hear and answers to those questions, including resources to help you.
This article refers to the MyCloudIT Gen 2 platform, which was launched in 2015. Look for MyCloudIT Gen 3 to be launched in early 2021.
I Created My First Deployment, What’s Next?
We talk to many customers who request a checklist of topics to review as they are getting started to ensure they are familiar with their new deployment AND are maximizing both cost and performance.
Click here to see the 1st deployment checklist
Why Won’t My Deployment Build in Azure?
There are several reasons why a new RDS deployment will not deploy in Azure. The typical reasons are that your subscription does not have access to the VM sizes requested or that you do not have enough virtual cores available to complete the build of a deployment. We see this issue mainly when we have customers that create a deployment using a trial Azure subscription. Currently, our automation can detect some of these limitations that may impact your build, but not all limitations.
Click here to see some ways to identify the root cause of the problem
How Do I Build Multi-Tenant App Delivery in the Cloud?
When you look at delivering your solution to multiple customers, does that mean you need a separate infrastructure for each customer? Maybe, but not always. You may be able to build a single infrastructure in the cloud, then provision portions of that infrastructure for each customer. The decision on single vs. multiple infrastructures is really based on the data security built into your application.
Click here to read more about single vs. multiple infrastructures
Do’s and Don’ts of Your MyCloudIT Deployment
Here are some Do’s and Don’ts as you move forward with your MyCloudIT deployment:
• Do install your applications within the RDS Session Hosts built for your deployment.
• Do leverage the extra storage space on the RDSMgmt server as shared storage for your users.
• Do remember that if you are using the scheduler to turn VMs on and off, you should update the scheduler after any VM additions.
• Do not change the security groups assigned to your RDS collections.
• Do not change the name of the deployment, RDS collections, or server names.
If you grant the Domain Users group, or other groups within your Active Directory access to the collection, all users within the new group will be charged for both the RDS and MyCloudIT licenses.**
** MyCloudIT Licenses are counted based on per user/per collection.
Click here to see the rest of the Do’s and Don’ts
Can MyCloudIT Deploy RDS Across Multiple Azure Regions?
The short answer is Yes, but it is a little more complicated than just clicking a button.
VDI vs. RDS, What’s the Difference?
Virtual Desktop Infrastructure (VDI) is built around the Windows Client Operating System, Windows 10. Remote Desktop Session Hosts (RDS) are built around the Windows Server Operating System. One of the significant differences between VDI and RDS comes down to reducing cost.
Click here to read more about the differences
What is Microsoft SPLA and How to Stay Compliant?
SPLA stands for Service Provider License Agreement and is Microsoft’s primary licensing mechanism for hosting providers. SPLA licensing is based on a monthly consumption model, as opposed to purchasing perpetual licenses that are purchased upfront. Microsoft licensing can be a “challenge” to get right, but we can help you with your licensing needs.
Click here to read more about SPLA and staying compliant
What could Unexpectedly Drive-Up My Azure Costs?
We try to help our customers understand how to manage costs within Azure, but there can always be surprises if we aren’t careful.
1. Leaving a deployment on when it isn’t needed.
2. Playing “What if” with a deployment and not cleaning up your scenarios after testing.
3. Users that consume more storage than anticipated.
4. Leaving unneeded VPN gateways running.
5. Not leveraging scheduling or auto-scaling.
6. Assigning users that do not need RDS access to the RDS collection.
Click here to read more about what could drive your Azure costs
How Do I Manually Patch or Update All the Servers?
Administrators need the ability to manage all the VMs within a deployment, and sometimes that requires administrators to move between VMs within their deployment. This can be a challenge because most of the VMs within a deployment do not have Public IP addresses, thus making it impossible to remote directly into these VMs from outside of your deployment. This is by design to reduce the security footprint of your RDS deployment in Azure.
Click here to see how you can “hop” from one VM to other VMs within your deployment
Should I Have One Big Session Host, Or Several Smaller Session Hosts?
In Azure, you pay for the resources you use when you use them. If a resource isn’t being used, it is more cost-effective to turn it off and back on when needed. A large session host is more expensive but supports more users. Smaller VMs can be started based on actual user demand then taken offline after hours as users log out. It is cheaper to use multiple smaller VMs that are only started as user load increases, then to run a single large VM 24×7 even when all of the resources are not needed.
Click here to see a cost comparison
Which Azure Region is Right for Me?
Azure has a global presence, so picking an Azure Region near your physical location is typically our suggestion, but there are other factors to take into consideration as you make your decision, such as redundancy.
Click here to see what factors to consider when selecting an Azure Region
If you have any questions, feel free to email us email@example.com.