Reduce running costs for your RDS Deployment in Azure using Auto-Scaling

Published 09-08-2018 09:55 AM 5,365 Views
Community Manager

First published on CloudBlogs on Mar 23, 2017 by Enterprise Mobility + Security Team
This post is authored by Clark Nicholson, Principal Program Manager, Remote Desktop Services. Hello everyone. This is Clark Nicholson from the Remote Desktop Services team. I’m writing today to let you know we have recently published a new version of the Remote Desktop Session Host (RDSH) auto-scaling sample script that uses Azure Resource Management (ARM) PowerShell. Many of you have deployed Remote Desktop Services (RDS) in Azure VMs based on the RDS Technet documentation , the RDS ARM templates , or the RDS Azure Marketplace solution template . You may be wondering, “How do I reduce the cost of my RDS deployment in Azure?” It turns out that for many RDS deployments, the most significant cost is the RDSH server VMs, so a great way to reduce cost is to shut down and de-allocate your RDSH VMs during off hours and then start them back up again as usage increases. The sample script is intended to help you automate RDSH scaling. You can use the sample script as-is with simple configuration using the config.xml file, or you can customize the sample script itself. The PowerShell script, xml configuration file, and a deployment document are all included in a .zip file that can all be downloaded from TechNet Script Center. For more information, please see Remote Desktop Services , and Microsoft Azure Virtual Machines . Note: Questions and comments are welcome. However, please DO NOT post a request for troubleshooting by using the comment tool at the end of this post. Instead, post a new thread on the RDS & TS forum or make suggestions on the RDS User Voice forum . Thank you!

2 Comments
Regular Visitor

Script doesn't work on Server 2019.  From the log file:

 

[Error] Failed to retrieve RDS collections: Method invocation failed because [Microsoft.Management.Infrastructure.CimInstance] does not contain a method named 'GetInt32Property'.

 

Running on the single RDS CB as a domain admin.

Occasional Visitor

could you please provide an actuall link. The script is not available anymore

%3CLINGO-SUB%20id%3D%22lingo-sub-1316208%22%20slang%3D%22en-US%22%3ERe%3A%20Reduce%20running%20costs%20for%20your%20RDS%20Deployment%20in%20Azure%20using%20Auto-Scaling%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1316208%22%20slang%3D%22en-US%22%3E%3CP%3EScript%20doesn't%20work%20on%20Server%202019.%26nbsp%3B%20From%20the%20log%20file%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%5BError%5D%20Failed%20to%20retrieve%20RDS%20collections%3A%20Method%20invocation%20failed%20because%20%5BMicrosoft.Management.Infrastructure.CimInstance%5D%20does%20not%20contain%20a%20method%20named%20'GetInt32Property'.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERunning%20on%20the%20single%20RDS%20CB%20as%20a%20domain%20admin.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2278907%22%20slang%3D%22en-US%22%3ERe%3A%20Reduce%20running%20costs%20for%20your%20RDS%20Deployment%20in%20Azure%20using%20Auto-Scaling%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2278907%22%20slang%3D%22en-US%22%3E%3CP%3Ecould%20you%20please%20provide%20an%20actuall%20link.%20The%20script%20is%20not%20available%20anymore%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-250145%22%20slang%3D%22en-US%22%3EReduce%20running%20costs%20for%20your%20RDS%20Deployment%20in%20Azure%20using%20Auto-Scaling%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-250145%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3EFirst%20published%20on%20CloudBlogs%20on%20Mar%2023%2C%202017%20by%20Enterprise%20Mobility%20%2B%20Security%20Team%3C%2FSTRONG%3E%3CBR%20%2F%3E%20%3CEM%3E%20This%20post%20is%20authored%20by%20Clark%20Nicholson%2C%20Principal%20Program%20Manager%2C%20Remote%20Desktop%20Services.%20%3C%2FEM%3E%20Hello%20everyone.%20This%20is%20Clark%20Nicholson%20from%20the%20Remote%20Desktop%20Services%20team.%20I%E2%80%99m%20writing%20today%20to%20let%20you%20know%20we%20have%20recently%20published%20a%20new%20version%20of%20the%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Frdshscaling%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%20Remote%20Desktop%20Session%20Host%20(RDSH)%20auto-scaling%20sample%20script%20%3C%2FA%3E%20that%20uses%20Azure%20Resource%20Management%20(ARM)%20PowerShell.%20Many%20of%20you%20have%20deployed%20Remote%20Desktop%20Services%20(RDS)%20in%20Azure%20VMs%20based%20on%20the%20%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Frdsonazure%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%20RDS%20Technet%20documentation%20%3C%2FA%3E%20%2C%20the%20%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Frdautomation%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%20RDS%20ARM%20templates%20%3C%2FA%3E%20%2C%20or%20the%20RDS%20%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fwindows-server-docs%2Fcompute%2Fremote-desktop-services%2Frds-in-azure%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%20Azure%20Marketplace%20solution%20template%20%3C%2FA%3E%20.%20You%20may%20be%20wondering%2C%20%E2%80%9CHow%20do%20I%20reduce%20the%20cost%20of%20my%20RDS%20deployment%20in%20Azure%3F%E2%80%9D%20It%20turns%20out%20that%20for%20many%20RDS%20deployments%2C%20the%20most%20significant%20cost%20is%20the%20RDSH%20server%20VMs%2C%20so%20a%20great%20way%20to%20reduce%20cost%20is%20to%20shut%20down%20and%20de-allocate%20your%20RDSH%20VMs%20during%20off%20hours%20and%20then%20start%20them%20back%20up%20again%20as%20usage%20increases.%20The%20sample%20script%20is%20intended%20to%20help%20you%20automate%20RDSH%20scaling.%20You%20can%20use%20the%20sample%20script%20as-is%20with%20simple%20configuration%20using%20the%20config.xml%20file%2C%20or%20you%20can%20customize%20the%20sample%20script%20itself.%20The%20PowerShell%20script%2C%20xml%20configuration%20file%2C%20and%20a%20deployment%20document%20are%20all%20included%20in%20a%20.zip%20file%20that%20can%20all%20be%20%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Frdshscaling%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%20downloaded%20%3C%2FA%3E%20from%20TechNet%20Script%20Center.%20For%20more%20information%2C%20please%20see%20%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Frds%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%20Remote%20Desktop%20Services%20%3C%2FA%3E%20%2C%20and%20%3CA%20href%3D%22http%3A%2F%2Fwww.windowsazure.com%2Fen-us%2Fsolutions%2Finfrastructure%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%20Microsoft%20Azure%20Virtual%20Machines%20%3C%2FA%3E%20.%20%3CSTRONG%3ENote%3A%20%3C%2FSTRONG%3E%20Questions%20and%20comments%20are%20welcome.%20However%2C%20please%20DO%20NOT%20post%20a%20request%20for%20troubleshooting%20by%20using%20the%20comment%20tool%20at%20the%20end%20of%20this%20post.%20Instead%2C%20post%20a%20new%20thread%20on%20the%20%3CA%20href%3D%22http%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fen-US%2FwinserverTS%2Fthreads%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%20RDS%20%26amp%3B%20TS%20forum%20%3C%2FA%3E%20or%20make%20suggestions%20on%20the%20RDS%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fuservoice-rds%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%20User%20Voice%20forum%20%3C%2FA%3E%20.%20Thank%20you!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-250145%22%20slang%3D%22en-US%22%3E%3CP%3EFirst%20published%20on%20CloudBlogs%20on%20Mar%2023%2C%202017%20This%20post%20is%20authored%20by%20Clark%20Nicholson%2C%20Principal%20Program%20Manager%2C%20Remote%20Desktop%20Services.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-250145%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESecurity%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Version history
Last update:
‎May 11 2021 02:00 PM
Updated by: