$SiteServers = Get-WmiObject -Namespace root\SMS\site_xxx -Class SMS_SiteSystemSummarizer | Select-Object SiteSystem, SiteCode, Roleĭue to the fact that many servers have more than one role, we put a list of unique server names into $UniqueServers. $ServerInfo = query WMI on the SCCM Site server and get back a list of all site servers with their site code and role, which we store in $SiteServers. $ServerInfo is an array and will be used to build a custom PSObject to help build the output file. $ServerList will be used to build a list of all site servers listed in SCCM. $OutputText will be used to hold the contents of the RDC Connection file that we will export at the end of the script. We start by initializing a few variables: Note: This script must be run on the Primary Site server. I’ll walk you through how it works, then at the bottom of this post, I’ll include the entire script in case you want to try it out! The script itself is rather simple, actually. The groupings key off the comments we included using PowerShell for each server. Here are some screenshots of what it will look like when finished: The resulting PowerShell script reads the site information on a Primary SCCM 2012 Site and automatically builds a RDC Man connection file, including smart groups that allow you to quickly view a list of servers by the role it is assigned. PowerShell to the rescueĪ philosopher somewhere once said, “It is when we dread doing something that we become most inventive.” He must have been a really smart guy, because I decided then and there that I wasn’t going to hand code my RDC Man connection files anymore! I was going to automate it! I’ll admit I wasn’t looking forward to setting RDC Man up. However, recently I have found myself again in a position where I need to add many connections from a new environment. Then I realized that the connection file is just a plain text file, so I started copying and pasting. I’ll admit the first few times I set up my connections I did it by hand.
I love this tool! It’s great … except for one thing: it’s a pain to set up the first time, especially when you have a lot of servers to add. I can configure servers to inherit settings from the group they are part of in RDC Man.It’s flexible! I can choose to view my RDP sessions inside of RDC Man (docked), or break them out across multiple monitors (un-docked).The desktop of each RDP session can be set to automatically resize to fit the RDC Man window.I can store credentials (with or without passwords) to make quick RDP connections.If you don’t already have it, you can download it from Microsoft at: Like many others, I use Microsoft’s Remote Desktop Connection Manager (RDC Man) daily to connect to the Servers I administer. Estimated Reading Time: 6 minutes An issue arises
0 kommentar(er)
