header1   header
header
header : : Login header
header
connector   connector
menuleft
Home
Forums
Scripts
User Groups
Resources
About
 menuright
submenu   submenu
left
IMPORTANT: PowerShellCommunity.org is moving! - Wednesday, August 15, 2012

PowerShellCommunity.org is moving!  This community software, and the hardware that it sits on, are no longer serving the purposes of this community.  As a result, we have decided to move this community to a new home at PowerShell.org.  PowerShell.org is already up and running with the new community software and in its new location, so please post any new questions that you have on the forums over there instead of posting them on this site.  We've already started getting some great questions from members of the community over there so please, come on over and join us!

While we are going through this transition, this site will remain up for the short term.  New posts may no longer be created on these forums, however replies to existing posts are allowed so that users who posted questions don't have to re-post the same question on the new site.

[UPDATE 28/02/2013] New user registration has been disabled and forums have now been switched to read-only, including for existing posts since all threads that were started should now be completed. If you have a question about content on this site or about PowerShell in general, head over to PowerShell.org and ask it there where there are people actively using the site and answering questions.

If you have any questions, please let us know on the PowerShell.org site.

Thank you,

Kirk "Poshoholic" Munro

 
Forums > Using PowerShell > General PowerShell
powershell profile & modules
Last Post 03 Apr 2012 07:00 AM by jakes. 5 Replies.
Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
jakesUser is Offline
New Member
New Member
Posts:15
Avatar

--
02 Mar 2012 06:45 PM
    Hi,
    I want to create a profile with custom colors, fonts, etc, and then also have it automatically load modules, such as quests, and others.  I would like to be able to have this profile "roam" with me to servers so it's available when I remote desktop into other systems, is this possible?
    Marco ShawUser is Offline
    Veteran Member
    Veteran Member
    Posts:1684
    Avatar

    --
    03 Mar 2012 10:15 AM
    If you can't install this software elsewhere, then you may be able to use a trick like making sure to mount your local drives in remote RDP sessions, then you would still have to have a profile on the remote server that is able to use those mounted drives to load various things.

    The Quest cmdlets are not a module so that might complicate things a bit as the code might not be "self-contained" and require libraries.

    If may be techically easier to simply not use RDP and use PowerShell remoting instead.
    jakesUser is Offline
    New Member
    New Member
    Posts:15
    Avatar

    --
    03 Mar 2012 05:54 PM
    Hi,
    I can do powershell remoting, but don't I still have to have the cmdlets available on the remote server?
    Marco ShawUser is Offline
    Veteran Member
    Veteran Member
    Posts:1684
    Avatar

    --
    04 Mar 2012 08:49 AM
    Yes, you are correct that remoting needs to have the cmdlets on the remote end. I replied too quickly without giving it enough thought. It does bring up an interesting test I may try some day: remote to an endpoint, and then remote back again from there to the initial point.
    0ptikGhostUser is Offline
    Basic Member
    Basic Member
    Posts:369
    Avatar

    --
    07 Mar 2012 03:39 PM
    This applies to both Remote Desktop and PowerShell Remoting: PowerShell can only find commands it knows about which is controlled mostly by $env:PATH and $env:PSModulePath. Commands must be local to be executable. You can always add remote file locations (shares) to your paths so that powershell can find functions ($env:PATH) and modules ($env:PSModulePath). Your ExecutionPolicy will need to set appropriately to allow these. Cmdlets that are available through snapins MUST installed locally on each server where you want to use them. You'll need a local $profile that can set up your local environment correctly based on your remote file locations (shares).
    jakesUser is Offline
    New Member
    New Member
    Posts:15
    Avatar

    --
    03 Apr 2012 07:00 AM
    Thanks, so how can I use remote powershell and have a profile that will "roam" or be the same on any remote server I connect to using powershell? Also the account I use to connect to remote systems is different than my local system login account.
    You are not authorized to post a reply.

    Forums > Using PowerShell > General PowerShell
    Active Forums 4.3
    		right
    footer   footer
    footer Many thanks to our original sponsors: Quest Software • SAPIEN Technologies • Compellent • Microsoft footer
    footer   footer