This site has moved

All new content is now located at

PowerShell 3 quick switch to PowerShell 2

PowerShell 3 improves on PowerShell 2 by adding almost 500 new cmdlets built-in.  One drawback unfortunately, is cmdlets or scripts written for version 2 do not always work as expected.

If you need to quickly switch to version 2 while you are in PowerShell 3 type the following.

PowerShell.exe -version 2

You will see the copyright info change to 2009 and if you type get-host it will display version 2.


To switch back to version 3 you can either  close and re-open PowerShell or simply type in your current session

PowerShell.exe -version 3


Powershell 3 combo installers

These combo installers will update PowerShell to Version 3 on either Windows 7 x86 or Windows 7 x64 / Server 2008 R2

The installer runs silently and installs both the dotNetFx40_Full_x86_x64.exe  and either the Windows6.1-KB2506143-x86.msu or Windows6.1-KB2506143-x64.msu files. When the script  completes a pop-up prompting for a reboot will be displayed.

1-28-2013 2-17-52 AM

  After re-booting and launching powershell type get-host to display the version number.

1-28-2013 2-25-39 AM

Modifying the Office 2010 ADMX Templates to allow more trusted locations

This guide will show how to edit your office2010.admn and office2010.adml files to add support for more trusted locations than the default 20 that the admx file currently allows. The below example will show how to add the 21st location. Just repeat the process for more locations. Bolded items need to be changed for each location. You will need to edit the office2010.admx and the office2010.adml file.

in the office2010.admx file search for location20
then insert the below on line 4517
<policy name=”L_TrustedLoc21” displayName=”$(string.L_TrustedLoc21)” explainText=”$(string.L_OfficeTrustedLocationsExplain)” presentation=”$(presentation.L_TrustedLoc21)” key=”software\policies\microsoft\office\14.0\common\security\trusted locations\all applications\location21“>
<parentCategory ref=”L_trustcenter241″ />
<supportedOn ref=”windows:SUPPORTED_WindowsVista” />
<text id=”L_pathcolon318” valueName=”path” expandable=”true” />
<text id=”L_datecolon319” valueName=”date” />
<text id=”L_descriptioncolon320” valueName=”description” />
<boolean id=”L_allowsubfolders321” valueName=”allowsubfolders”>
<decimal value=”1″ />
<decimal value=”0″ />

in the office2010.adml
search for <string id=”L_TrustedLoc20″>Trusted Location #20</string>
add after it  the below for 21
<string id=”L_TrustedLoc21“>Trusted Location #21</string>

search for  <presentation id=”L_TrustedLoc20”>
add at the end of it the below for 21

<presentation id=”L_TrustedLoc21“>
<textBox refId=”L_pathcolon318“>
<textBox refId=”L_datecolon319“>
<textBox refId=”L_descriptioncolon320“>
<checkBox refId=”L_allowsubfolders321“>Allow sub folders:</checkBox>

Once done making the edits copy the new office2010.admx to C:\windows\syvol\domain\policies\policy definitions and the new office2010.adml to the C:\windows\syvol\domain\policies\policy definitions\en-us

When you restart your Group Policy Management Editor you should see the new location

Once the GPO has been applied on a windows client in Office the trusted loactions will show the new 21st location

Customize The User Template on your Mac Leopard and Snow Leopard systems

If you’re like me then you probably strive to provide a consistent user  experience across multiple systems. This helps in facilitating training and minimizing troubleshooting time. I do this on macs by modifying the default account so each new user account created on a system has a standardized environment which is designed for my organizations needs.

At the heart of this practice is a default set of user data, carefully designed around the needs of the group and applied to each account when it’s first created. For Windows that data is typically stored in C:\Documents and Settings\Default User, while Unix systems have traditionally used /etc/skel. Mac OS X keeps its user template deep within the /System hierarchy, but while finding it can be difficult, customizing it to your needs is quite easy.

Start with a new account created specifically for this purpose. Choose the system preferences, dock items, browser bookmarks, server shortcuts, and application settings appropriate to your user base, leaving out anything you can instead control via Open Directory’s managed preferences. If you install individual applications or fonts on a per-user level, include those in ~/Applications and ~/Library/Fonts (where the tilde represents the user’s home directory).

Once you’ve finished, open Keychain Access from the /Applications/Utilities folder and delete the “login” keychain (both references and files when prompted)  so new users will get their own keychain file created for them. You’ll also want to delete the cache files stored in ~/Library/Caches, clear out the “Recent Items” from the Apple menu, and (if you’ve used the Terminal) discard the ~/.bash_history file.

Now log out of the template, and log in to an Admin account. From here, you’ll be clearing Apple’s existing user template and copying your new template user in its place. In Leopard, that work can’t be done using the sudo command, and instead must be performed as the root user, meaning you run the risk of doing serious damage if you don’t understand what you’re typing. If you’re at
peace with that, just open the Terminal, and very carefully type:
su –

After prompting you for a password, this will let you assume the role of root, the Unix “superuser”. This allows you to modify and delete any file on the machine.
rm -r /System/Library/User\ Template/English.lproj/*
This removes everything inside the English-speaking template folder. If you’re utilizing another language, you’ll need to change this to the appropriate template.
cp -R /Users/TEMPLATE/* /System/Library/User\ Template/English.lproj/
In the command above, replace TEMPLATE with the  actual name of the template account you’ve created. This copies your prepared user environment into the template location. After which you can:

Now, when you add a new user account, it’ll be created with your customizations already in place. You can then delete the original account from the install you built it on, but be sure to back up the home directory. The process can be repeated on multiple machines, deployed on your server, or incorporated into a system image, all using the same template.