<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Use a Central File to Simplify Your PowerShell Profile</title><link>http://blogs.technet.com/b/heyscriptingguy/archive/2012/05/23/use-a-central-file-to-simplify-your-powershell-profile.aspx</link><description>Microsoft Scripting Guy, Ed Wilson, shows how to use a central file to simplify configuring your Windows PowerShell profile.</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Use a Central File to Simplify Your PowerShell Profile</title><link>http://blogs.technet.com/b/heyscriptingguy/archive/2012/05/23/use-a-central-file-to-simplify-your-powershell-profile.aspx#3499731</link><pubDate>Wed, 23 May 2012 18:51:43 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3499731</guid><dc:creator>JV</dc:creator><description>&lt;p&gt;The profile in the MyDocuments folder is the one to use for most things. &amp;nbsp;If we redirect &amp;#39;MyDocuments&amp;#39; to &amp;nbsp;a network location in a GPO we can always have the same code available on any system. &amp;nbsp; This is an All-Hosts on steroids. &amp;nbsp;The profile can contain any or all modules in its modules folder. &amp;nbsp;Just think, Anywhere you log into the network you have all of your code.&lt;/p&gt;
&lt;p&gt;MyDocuments\WindowsPowerShell&lt;/p&gt;
&lt;p&gt;MyDocuments\WindowsPowerShell\Modules&lt;/p&gt;
&lt;p&gt;I have hundreds of scripts and modules in this location along with my per-user profile. &amp;nbsp;I also have this set up on every network I support. &amp;nbsp;We can also use BITS to keep things sync’d although I haven’t yet set this up.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3499731" width="1" height="1"&gt;</description></item><item><title>re: Use a Central File to Simplify Your PowerShell Profile</title><link>http://blogs.technet.com/b/heyscriptingguy/archive/2012/05/23/use-a-central-file-to-simplify-your-powershell-profile.aspx#3499589</link><pubDate>Wed, 23 May 2012 14:41:19 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3499589</guid><dc:creator>Ed Wilson</dc:creator><description>&lt;p&gt;@K_Schulte you are absolutely correct ... having one file for all users can become really complex. One thing you might consider in having multiple profiles is to have a basic one that ALL users do get for all hosts. Then Have additional commands for one group of users, and different file for the administrators. If you keep them like this,then the basic profile only goes to this group. The next group gets the basic profile, plus the other commands in the other file. The administrtors get all three files. &lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3499589" width="1" height="1"&gt;</description></item><item><title>re: Use a Central File to Simplify Your PowerShell Profile</title><link>http://blogs.technet.com/b/heyscriptingguy/archive/2012/05/23/use-a-central-file-to-simplify-your-powershell-profile.aspx#3499554</link><pubDate>Wed, 23 May 2012 11:34:05 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3499554</guid><dc:creator>K_Schulte</dc:creator><description>&lt;p&gt;Hi Ed,&lt;/p&gt;
&lt;p&gt;I really like the &amp;quot;have ONE file&amp;quot; for all users idea!&lt;/p&gt;
&lt;p&gt;But to be honest, I&amp;#39;m afraid that we won&amp;#39;t have ONE but maybe SOME profiles located somewhere in our network! But SOME is less the ALL :-)&lt;/p&gt;
&lt;p&gt;Having ONE profile and using script logic inside the script to distinguish between script types and user &amp;quot;groups&amp;quot; and ... whatsoever ... might be possible but will lead to rather complicated profiles ... especially if you are going to add functionality later on which should be available to group 1,2,4,8,16 ... but only for ISE hosts ... and not on Monday to Wednesday ... Well, than this script will be astonishingly difficult :-)(&lt;/p&gt;
&lt;p&gt;Klaus&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3499554" width="1" height="1"&gt;</description></item></channel></rss>