I was reading PowerShell remoting in Windows Server 2008 R2<\/A>. The great thing about this article is that it documents how to use Group Policy to enable PSRemoting on lots of machines automatically. In the article there was the following heads up: <\/P>\n Warning:<\/B> <\/EM><\/P>\n The great thing about PowerShell is that it is a toolbox<\/STRONG>. <\/P>\n The great thing about toolboxes is that they have general purpose utilities that creative people can use their inspiration to do things that the tool designers didn\u2019t think of when they developed the tool. One of my favorite examples of this came from a problem with SELECT. SELECT is a utility which selects a set of properties from the incoming object. It creates a new object and adds those selected properties as NoteProperties on that new object. e.g.<\/P>\n PS> Get-Process *ss <\/STRONG><\/FONT><\/FONT><\/FONT><\/P>\n Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName Id Handles ProcessName TypeName: Selected.System.Diagnostics.Process <\/FONT><\/P>\n Name MemberType Definition PS> Get-Process *ss |Select ProcessName<\/STRONG> <\/FONT><\/P>\n ProcessName <\/EM><\/P>\n Sidenote: notice that the TYPE of the result is Selected.<\/STRONG>System.Diagnostics.Process. We did that in V2 to be consistent with our principle of always trying to help you keep track of where information came from. The idea is that if you are debugging a script and have an examine an object and see this typename, you have more information about where it came from to help debug your script.<\/EM><\/P>\n Anyway, that is great but notice what happens when you select a single property you get an object with a single property. Often you just want the values of the property not an object with a single property. The solution to that has been:<\/P>\n PS> <\/FONT>Get-Process *ss |foreach {$_.ProcessName} That works but I don\u2019t like it very much. We had lots of discussions about what to do about this. Some people wrote a function which did this operation and thought we should include it in the next version. Others felt like we ought to put a switch on Select which say something like \u2013VALUEONLY. It was Lee Holmes that pointed out that we already support this. I looked at him like he had a rat\u2019s tail hanging out of his mouth when he said that. He said that Select \u2013ExpandProperty did the trick. This switch was designed to work with objects that have properties which are collections. For instance: <\/P>\n PS> Get-Service WinMgmt |Select DependentServices<\/STRONG> <\/FONT><\/P>\n DependentServices PS> Get-Service WinMgmt |Select -ExpandProperty DependentServices<\/STRONG> <\/FONT><\/P>\n Status Name DisplayName <\/FONT><\/P>\n Pretty cool right? This tool was designed to work on properties which are collections. Lee Holmes wondered, \u201cWhat would it do on a property which wasn\u2019t a collection?\u201d.<\/P>\n PS> Get-Process *ss |Select -ExpandProperty ProcessName<\/STRONG> OH YEAH BABY! You asked for it you got it! Using the toolkit mindset, Lee was able to figure out that we already supported this function. (You might point out that this is longer than the foreach but it turns out to be a ton easier because of tab completion.)<\/P>\n So \u2013 what does this have to do with the remoting warning about not having access to any of the functions you defined in your profile file? Well, it turns out that the command Invoke-Command has a parameter \u2013FILEPATH which allows you to specify a file that you want to run on the remote machine. We added this feature to help people machine machines in DMZs<\/A> where it can be difficult to ensure that the script you want to run will be on that machine and it can be difficult for that machine to have access to a shared folder of scripts. We send the file across and execute it so there is deployment free script execution. (This is a super important feature that people haven\u2019t quite tuned into yet. I\u2019m going to write a blog in the future about how to use this capability to use PowerShell as a bootstrap management agent to do all of your management functions.) So the example of this is something like<\/P>\n PS> $DmzMachines = New-PSSession -ComputerName (cat DmzMachines.txt)<\/STRONG> PowerShell transfers and executes the Get-Inventory.ps1 script to all the machines. From there, you can connect the dots to putting the functions you want everywhere into a file called RemoteProfile and doing the following:<\/P>\n PS> Invoke-Command $DmzMachines -FilePath c:\\scripts\\RemoteProfile.ps1<\/STRONG><\/FONT><\/P>\n Enjoy! <\/P>\n Jeffrey Snover [MSFT] I was reading PowerShell remoting in Windows Server 2008 R2. The great thing about this article is that it documents how to use Group Policy to enable PSRemoting on lots of machines automatically. In the article there was the following heads up: Warning: Commands that are executed against a remote machine do not have access […]<\/p>\n","protected":false},"author":600,"featured_media":13641,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-3011","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-powershell"],"acf":[],"blog_post_summary":" I was reading PowerShell remoting in Windows Server 2008 R2. The great thing about this article is that it documents how to use Group Policy to enable PSRemoting on lots of machines automatically. In the article there was the following heads up: Warning: Commands that are executed against a remote machine do not have access […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/3011","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/users\/600"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/comments?post=3011"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/3011\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media\/13641"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media?parent=3011"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/categories?post=3011"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/tags?post=3011"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
Commands that are executed against a remote machine do not have access to information defined within your local profile. As such, commands that use a function or alias defined in your local profile will fail unless they are defined on the remote machine as well.<\/EM><\/FONT><\/P>\n
——- —— —– —– —– —— — ———–
917 14 3420 2364 52 9.97 424 csrss
771 27 3484 13428 189 108.02 512 csrss
1989 45 18272 17820 87 95.83 556 lsass
30 2 476 124 5 0.06 320 smss <\/FONT><\/P>\n
PS> Get-Process *ss |Select ID,Handles,ProcessName<\/STRONG> <\/FONT><\/P>\n
— ——- ———–
424 930 csrss
512 770 csrss
556 1984 lsass
320 30 smss <\/FONT><\/P>\n
PS> Get-Process *ss |Select ID,Handles,ProcessName |Get-Member<\/STRONG> <\/FONT><\/P>\n
—- ———- ———-
Equals Method bool Equals(System.Object obj)
GetHashCode Method int GetHashCode()
GetType Method type GetType()
ToString Method string ToString()
Handles NoteProperty System.Int32 Handles=925
Id NoteProperty System.Int32 Id=424
ProcessName NoteProperty System.String ProcessName=csrss
<\/FONT><\/P>\n
———–
csrss
csrss
lsass
smss<\/FONT><\/P>\n
<\/STRONG>csrss
csrss
lsass
smss<\/FONT><\/FONT><\/FONT><\/P>\n
—————–
{wscsvc, SharedAccess, iphlpsvc}
<\/FONT><\/P>\n
—— —- ———–
Running wscsvc Security Center
Stopped SharedAccess Internet Connection Sharing (ICS)
Running iphlpsvc IP Helper<\/FONT><\/P>\n
csrss
csrss
lsass
smss<\/FONT><\/P>\n
PS> Invoke-Command $DmzMachines -FilePath c:\\scripts\\Get-Inventory.ps1<\/STRONG>
<\/FONT>\u2026.<\/FONT><\/FONT><\/P>\n
Be aware that this mechanism has limitations. In a local profile, you can invoke other files on your system. Using this technique, those files aren\u2019t on the other system so that won\u2019t work \u2013 the files have to be self contained. That is why I called it RemoteProfile.ps1 . I keep it separate from my normal profile.<\/P>\n
Distinguished Engineer
Visit the Windows PowerShell Team blog at: http:\/\/blogs.msdn.com\/PowerShell<\/A>
Visit the Windows PowerShell ScriptCenter at: http:\/\/www.microsoft.com\/technet\/scriptcenter\/hubs\/msh.mspx<\/A><\/P><\/p>\n","protected":false},"excerpt":{"rendered":"