Re: [msh] Some msh setup questions

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

"Krishna[MSFT]" <Krishna[MSFT]@discussions.microsoft.com> wrote in message
news:D4C6D98E-8157-42E4-9E4E-8DEB3203B56B@xxxxxxxxxxxxxxxx
> Krishna[MSFT]: When you install monad an Examples directory will be
> created
> in the install directory. A skeleton profile.msh is copied to this
> examples
> directory.
>
> When monad is installed, by default the ExecutionPolicy ( registry key
> HKLM\software\microsoft\msh\1\shellids\microsoft.management.automation.msh
> )
> is set to "Restricted". This means execution of scripts is disabled on the
> system by default. Profile.msh is a script. So if profile.msh is installed
> in
> "all users\documents\msh" then the user will see some annoying messages
> everytime msh.exe is invoked. This happens even if profile.msh is empty.
> To
> prevent these messages (warnings) at startup time we are not installing
> profile.msh in "all users\documents\msh" location.

Why not create a basic profile.msh file that is signed and trust it by
default (although it sounds like you guys decided not to trust MS signed
stuff by default). Then you could include instructions in the Profile.msh
file on how to either remove the signature (and update the registry) or how
to create your own cert and sign with that.

It just seems like something that most people are going to want to
customize. Having the file in place and ready to go seems a bit more "user
friendly" to me, not to mention more like other shells. It could be that
I've set up MSH on a number of machines now and having to setup the profile
over and over and it's a bit of a pain especially since the name isn't
exactly obvious. I still think the default MSH profile file should be
called just "profile.msh" and make other shell instances prefix with their
fully qualified type name.

--
Keith


.

Relevant Pages

  • Re: CSDK 2.90.UC3 on Solaris with IDS 10.00.FCx
    ... There are basic core shared libraries that are needed by both, with no versioning in the name, and the 32bit apps and the 64bit engine each need to see the correct libraries. ... You need to create a separate install directory for the 32bit CSDK from the one the 64bit engine is installed into. ... Then copy or link the sqlhosts file from the engine's etc subdit into the etc subdir under the CSDK install directory and use the CSDK install directory as INFORMIXDIR for running the 32bit application. ...
    (comp.databases.informix)
  • Re: Unable to install updates
    ... install directory. ... find branches.inf and uncheck the read only ... If you have a problem getting to Windows Update itself, ...
    (microsoft.public.windowsupdate)
  • Re: Curious questions regarding 64-bit apps on a W2K8 64-bit server
    ... accept your answer that "You can install anything anywhere (e.g., ... When I load 64-bit apps ... hand when I load a 32-bit application be default the install directory ... points to C:\Program Files (x86). ...
    (microsoft.public.windows.server.setup)
  • Re: win2000 install problem
    ... then copy the install directory from the CD to ... and was also able to boot from 2 different live Linux CDs ... functional Linux OS on the Toshiba laptop. ...
    (microsoft.public.win2000.general)