# In the here-string that follows DO NOT USE any single quotes (') as this will mess up the here string. # DSC configuration script follows as a PowerShell "here string". But it sure was fun and I leave it to you to decide where on the POS-elegant spectrum it falls. I can’t decide, frankly, if it’s the worst POS code I’ve ever produced or the most elegant. So, to pass the FQDN to the DSC script when it is run on the target node, I used a DSC File resource whose only purpose is to write the incoming parm to disk so a Get-Content cmdlet in the Script resource can retrieve it. The DSC Script resource does not accept parameters in its GetScript specification.(Keep in mind, I wanted a single script, not one plus another file on disk.) To solve this, the actual DSC configuration is embedded in the running script as a here-string. That meant creating a file from the running script and storing it on disk. The most intricate part of the script is caused by the brain-dead AzureRM cmdlet Start-AzureRmAutomationDscCompilationJob.This is because the fully-qualified domain name of the RDG ( $FQDN) is passed from the running script to the DSC configuration by Azure DSC. Instead of passing a lot of parameters to the script, I’ve coded variables by topic in #region comments.Then you can close port 3389 in the Network Security Group and log in to the VM using its private address and the RDG as the gateway. You need to log in once on TCP 3389, retrieve the self-signed cert in c:\temp and add the self-signed certificate to the local client’s Trusted Root Certification Authorities. The Remote Desktop Gateway is all good-to-go.If you have any questions or comments about the script, please leave a comment below or contact me. So, sit back and watch it happen - it takes about 25 minutes to run. I’ve commented it extensively so you should be able to follow it. There’s so much going on that I will only list a few notes as bullets below. My “mother-of-all-Windows-jump-server scripts” is below. I wanted a script that would, from scratch and in one pass, create an Azure Vnet (and everything associated with it), launch a VM and then install and configure the RDG via PowerShell Desired State Configuration (DSC). You still had to create the VM and then login and run the script to install and configure Remote Desktop Gateway. I wanted a “pure” DevOps infrastructure-as-code approach, so I wrote one for Azure.īut even that script is incomplete. But it involves an administrator logging into the Remote Desktop Gateway (RDG) and configuring it via the UI. Certainly every time you add a new application and/or network container (either VPC or Vnet), you might need to add bastion hosts.Īn older post describing how to do it in AWS has become quite popular. It seems there’s a never-ending requirement to build jump boxes. It’s amazing to me how crucial this is in Windows environments. However, you could also miss out on multi-channel capabilities and not get optimal performance if you don't follow your motherboard's guidance.I’ve blogged a lot over the last few years on how to set up a Windows jump (or bastion) server in public clouds. Your computer should still work if you mix up the order. It all depends on your motherboard.ĭon't worry, though. That’s because motherboards may suggest installing RAM in a different order, such as Slot 2 > Slot 4 > Slot 1 > Slot 3. You must always consult your motherboard manual. This isn’t a hard and fast rule, however. Finally, a fourth stick would go into Slot 4. If you have a third stick, it would go into Slot 3, which will actually be between Slot 1 and Slot 2. A second stick should go into Slot 2, which isn't next to Slot 1. In the case of a motherboard with four RAM slots, it's probable you'll want to install your first RAM stick into the slot labeled 1. If you just have one stick, you don't have to fill Slot 2. In a motherboard with two RAM slots, you can simply put your first stick of RAM into Slot 1 and a second stick into Slot 2. In addition, which slots you go with will also depend on how many RAM sticks you have. You want to make sure you're putting the RAM into the correct slots, after all, so you can get the full performance out of them. Consult your motherboard's manualĪs easy as it is to pop RAM sticks into your motherboard, but when it comes to how to install RAM, you also shouldn’t be cavalier about slotting it just anywhere where there’s a spot available. Then, once you've got that sussed, follow the step by step instructions below on how to install RAM where we talk you through everything you need to know, from figuring out which slots to fill to actually inserting it in. Before you start, check out our guide to the best RAM to help you get off on the right foot.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |