Re: [psh] Upgrade blues
- From: "Lee Holmes [MSFT]" <lee.holmes@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 3 May 2006 18:12:20 -0700
"Thomas Lee" <tfl@xxxxxxxxx> wrote in message
news:Xr2BKeCXjLWEFA76@xxxxxxxxxxxxxxxxx
Then why is it so hard to get into? This stuff should be fixed in the
installer. I should be able to install this product, via unattended means
and have it work the way I want to.
This is something that we hope to allow as a command-line arguement in the
installer. However, we're just about to rewrite our setup (into 3 different
technologies, in fact,) so we didn't want to put feature work into the
current installer for this release. With that, I think that most of your
deployment and personalization concerns would be covered.
If I try to edit the $profile file (Notepad $profile) I get errors.
Try the following to create a file, along with its intermediate directories:
[C:\temp\monad]
PS:12 > new-item -type File "c:\new path\file.txt" -force
Directory: C:\new path
Mode LastWriteTime Length Name
Description
---- ------------- ------ ----
-----------
-a--- 5/3/2006 6:09 PM 0 file.txt
Suggestion: An alias for New-Item is ni
[C:\temp\monad]
PS:13 > dir 'C:\new path\file.txt'
Directory: C:\new path
Mode LastWriteTime Length Name
Description
---- ------------- ------ ----
-----------
-a--- 5/3/2006 6:09 PM 0 file.txt
A mapped drive is NOT the Internet! I do not want to have to type "r" each
time I run a script off of a network share. This is stupid security, not
helpful security. It should be fixed by Execution Policy.
This is a separate bug that we're looking into. This isn't the experience
that we want users to have. Could you please file a bug about this on MS
Connect along with your system information so that we can try to track it
down?
--
Lee Holmes [MSFT]
Windows PowerShell Development
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- Follow-Ups:
- Re: [psh] Upgrade blues
- From: Thomas Lee
- Re: [psh] Upgrade blues
- From: William Stacey [MVP]
- Re: [psh] Upgrade blues
- References:
- [psh] Upgrade blues
- From: Thomas Lee
- Re: [psh] Upgrade blues
- From: Lee Holmes [MSFT]
- Re: [psh] Upgrade blues
- From: Thomas Lee
- [psh] Upgrade blues
- Prev by Date: Re: Executing powershell on W2k Server
- Next by Date: Re: Invoking E12 cmdlets from C# code
- Previous by thread: Re: [psh] Upgrade blues
- Next by thread: Re: [psh] Upgrade blues
- Index(es):
Relevant Pages
|