Vista - homebrew powershell installer for vista

Okay, caveats first: I don't recommend that ANYONE uses this installer. I
don't know how this will affect any attempt to use the forthcoming
Powershell installer for Vista. I have not tested using this to uninstall
Powershell (even though that capability is in the Inno Setup script).

And finally, this installer may cause planets to fall out of their orbit.
You have been warned.

You are still reading so I guess you just can't bear to do without
Powershell on Vista any longer.... here is the technique I used to get
Powershell installed on Vista.

I used Windows 2003 as my initial OS to gather the powershell source files.
I ran the Powershell Installer (WindowsServer2003-KB926139-x86-ENU.exe) and
when I got the first install wizard prompt, I looked out in my C:\ folder
and noticed a new folder with a guid-like name (e.g. "{323411...}"). In that
folder, I found all of the source files necessary for a PowerShell install
including an update.inf file that I used for the groundwork on what needed
to be done for a semi-proper install. You can find all the ngen commands,
etc in that file. Copy all the files and folders you find there into a
folder on your target vista machine and then cancel out of the install.

Use Inno Setup and the ISS file attached to the message to generate an
executable installer. If anyone wants to host the compiled installer, let me
know and I'll provide a copy. I just don't have anywhere to host it right
now.

Copy the resultant psinstaller.exe into the folder you copied the powershell
source files to on your target machine. Run the installer. In my test, I
always explicitly ran the installer as Administrator. When done, test
running powershell from the desktop icon or from command window.

My testing consisted of running powershell.exe and issuing the following
commands:

gwmi -class win32_computersystem
gwmi -class win32_computersystem | fl *

both worked therefore I was happy

A brand new installation of Vista in a Virtual PC image was used in all
testing. Problems, suggestions, complaints welcome.

Gaurhoth

In message <OAKqZA6GHHA.4116@TK2MSFTNGP05.phx.gbl>, Gaurhoth
<gaurhoth@live.com> writes
>Okay, caveats first: I don't recommend that ANYONE uses this installer.

For obvious reasons, me too...

But having said that...

{snip}

>here is the technique I used to get Powershell installed on Vista.

{snip details}

Cool idea.

I did it in a simpler fashion:
http://tfl09.blogspot.com/2006/12/mo...-on-vista.html

Thomas
--
Thomas Lee
doctordns@gmail.com
MVP - Admin Frameworks and Security

Based on a suggestion in another thread, I've updated these instructions to
a far simpler method that involves using the actual Windows 2003 Powershell
installer. You can find them at
http://gaurhothw.spaces.live.com/blog/cns!52B0837064D0B275!106.entry along
with links to the Inno Setup script and compiled installer for those that
don't wish to mess with Inno Setup.


"Gaurhoth" <gaurhoth@live.com> wrote in message
news:OAKqZA6GHHA.4116@TK2MSFTNGP05.phx.gbl...
> Okay, caveats first: I don't recommend that ANYONE uses this installer. I
> don't know how this will affect any attempt to use the forthcoming
> Powershell installer for Vista. I have not tested using this to uninstall
> Powershell (even though that capability is in the Inno Setup script).
>
> And finally, this installer may cause planets to fall out of their orbit.
> You have been warned.
>
> You are still reading so I guess you just can't bear to do without
> Powershell on Vista any longer.... here is the technique I used to get
> Powershell installed on Vista.
>
> I used Windows 2003 as my initial OS to gather the powershell source
> files.
> I ran the Powershell Installer (WindowsServer2003-KB926139-x86-ENU.exe)
> and
> when I got the first install wizard prompt, I looked out in my C:\ folder
> and noticed a new folder with a guid-like name (e.g. "{323411...}"). In
> that
> folder, I found all of the source files necessary for a PowerShell install
> including an update.inf file that I used for the groundwork on what needed
> to be done for a semi-proper install. You can find all the ngen commands,
> etc in that file. Copy all the files and folders you find there into a
> folder on your target vista machine and then cancel out of the install.
>
> Use Inno Setup and the ISS file attached to the message to generate an
> executable installer. If anyone wants to host the compiled installer, let
> me
> know and I'll provide a copy. I just don't have anywhere to host it right
> now.
>
> Copy the resultant psinstaller.exe into the folder you copied the
> powershell
> source files to on your target machine. Run the installer. In my test, I
> always explicitly ran the installer as Administrator. When done, test
> running powershell from the desktop icon or from command window.
>
> My testing consisted of running powershell.exe and issuing the following
> commands:
>
> gwmi -class win32_computersystem
> gwmi -class win32_computersystem | fl *
>
> both worked therefore I was happy
>
> A brand new installation of Vista in a Virtual PC image was used in all
> testing. Problems, suggestions, complaints welcome.
>
> Gaurhoth
>

In message <e#hCD1lHHHA.4760@TK2MSFTNGP03.phx.gbl>, Gaurhoth
<gaurhoth@live.com> writes
>Based on a suggestion in another thread, I've updated these
>instructions to a far simpler method that involves using the actual
>Windows 2003 Powershell installer. You can find them at
>http://gaurhothw.spaces.live.com/blog/cns!52B0837064D0B275!106.entry
>along with links to the Inno Setup script and compiled installer for
>those that don't wish to mess with Inno Setup.

Thanks. I'll try these when I get back home on Friday.

What I find somewhat amusing is that each time a manufacturer (in this
case MS) tries to stop geeks from doing their thing, we find a way
around it. :-)

Thomas


--
Thomas Lee
doctordns@gmail.com
MVP - Admin Frameworks and Security