Use a Module to Simplify Your PowerShell Profile

re: Use a Module to Simplify Your PowerShell Profile

Ed Wilson — Sun, 27 May 2012 16:19:23 GMT

@JV yes, Scripter@Microsoft.com is down right now. I have been working with the help desk to get it back up, but it might take a bit of time. I will let you know. In the mean time, can you Direct Message me on Twitter, @ScriptingGuys or message me on Facebook?

re: Use a Module to Simplify Your PowerShell Profile

JV — Sat, 26 May 2012 04:42:29 GMT

@Ed - scripter@microsoft.com - invalid address.

<Scripter@Microsoft.Com>: host mail.messaging.microsoft.com[216.32.180.22]

said: 550 5.4.1 Scripter@Microsoft.Com: Recipient address rejected: Access

Denied (in reply to RCPT TO command)

re: Use a Module to Simplify Your PowerShell Profile

Ed Wilson — Fri, 25 May 2012 13:24:22 GMT

@JV this makes sense and would provide a very simple and powerful solution. I would love to hear more about it ... can you email me at Scripter@Microsoft.Com please?

re: Use a Module to Simplify Your PowerShell Profile

Ed Wilson — Fri, 25 May 2012 13:23:07 GMT

@K_Schulte Yes, modules are GREAT. I have even written a blog article called Don't Write Scripts, Write Modules. The nice thing is that if prople write modules and share them, perhaps on the Scripting Guys Script Repository, then others can easily use those modules. In this way, only ONE person needs to write a specific module, and thousands of others can share in the use of that modules. Modules are a great way to share code.

re: Use a Module to Simplify Your PowerShell Profile

JV — Thu, 24 May 2012 23:30:53 GMT

@Ed

On all of my sites I have both admin and standard user ‘My Documents’ redirected by a GPO to the same network folder. I can access all scripts and modules from both sessions and from Win7/08 elevated. I constantly create and modify scripts in the standard user environment then just click a link on the desktop that does ‘RunAs’ my admin account. I can then test the scripts as an admin when needed. I am finding that most things do not require elevation if we are querying remote systems as I can just use credentials. Once I launch PosH I enter my Admin password into a $cred and have it to use whenever needed. I only need to log in as an admin to run some code against the local machine.

The trick is to use a GPO to redirect you’re ‘My Documents’ for both accounts. They will then share the same network folder where PowerShell stores its profile.

re: Use a Module to Simplify Your PowerShell Profile

K_Schulte — Thu, 24 May 2012 20:41:44 GMT

Hi Ed,

this is probably a very good idea ...

But I have to admit that I never had to (or just avoided to) create a reasonably complex module on my own!

I'm using some modules ... for sure ...

But developing a module is something else than consuming a module.

So I'm really excited to see, what the weekend scripter will be blogging here!

Klaus.

re: Use a Module to Simplify Your PowerShell Profile

Ed Wilson — Thu, 24 May 2012 15:55:49 GMT

@JV My normal user account is called ed. It is the one I use to log onto my computers day in and day out. That account is not a memember of any admin group -- either on the local computer or in the domain. Therefore, when i need to elevate the Windows PowerShell console, to do admin work, I must right click and select RUN AS Administrator. When this happens, a credential dialog box appears prompting me for credentials. I then type in EdAdmin for my domain, and supply the password. This IS in fact, a completely different domain user, that has ADMIN rights on my local computer. If you do not see a different profile path being used, then it means you are running your computer as a user that has administrator rights ... and that is not a very good security practice. But thank you for clarifying this point ...

re: Use a Module to Simplify Your PowerShell Profile

JV — Thu, 24 May 2012 15:19:03 GMT

I have now checked numerous WS2008, Windows 7 and WS2008R2 systems with PowerShell V2. On all tests, when running elevated, the profile is always pointed correctly. The PowerShell setup is basic. No changes have been made. The GPO just sets the security and enables remoting. Nothing else has been done.

If you are not seeing this on your systems then there is a problem with your installation. This may be because you upgraded to V2 without first removing V1. (that is a guess)

re: Use a Module to Simplify Your PowerShell Profile

JV — Thu, 24 May 2012 15:10:00 GMT

On WIndows 7 with PowerSHell V3 the profile path does not change when elevated. It should not change in PosH V2 either. If it does then something may have altered the registry settings.