MVP Summit Next Week - Give Us Your Input

A bunch of the PowerShell MVPs will be heading off to the MVP summit next
week (Mar 12-15). Hopefully we will get a chance to give the PowerShell
team direct feedback on PowerShell. Obviously there's a *lot* to like about
PowerShell but being on a software product myself I know that developers are
usually more interested in hearing about things that could be better with
their product. With that in mind, could you spend a bit of time thinking
about the top three to five things about PowerShell that are either
impediments to your work flow, unpleasantries, rough edges, bugs or things
just plain piss you off and write those down here. As an MVP I would like
to be able to represent the community and I'll do my best to convey your
input in person. Of course, a lot of the PowerShell team members hang out
here so some of them will likely see it here first but hey, that's OK.

--
Keith

On Thu, 8 Mar 2007 18:40:03 -0700, "Keith Hill [MVP]"
<r_keith_hill@no.spam.thank.u.hotmail.com> wrote:

>A bunch of the PowerShell MVPs will be heading off to the MVP summit next
>week (Mar 12-15). Hopefully we will get a chance to give the PowerShell
>team direct feedback on PowerShell. Obviously there's a *lot* to like about
>PowerShell but being on a software product myself I know that developers are
>usually more interested in hearing about things that could be better with
>their product. With that in mind, could you spend a bit of time thinking
>about the top three to five things about PowerShell that are either
>impediments to your work flow, unpleasantries, rough edges, bugs or things
>just plain piss you off and write those down here. As an MVP I would like
>to be able to represent the community and I'll do my best to convey your
>input in person. Of course, a lot of the PowerShell team members hang out
>here so some of them will likely see it here first but hey, that's OK.

At the risk of going over old ground!

It really "just plain p y o" that a [datetime] cast does not respect
locale settings.

I've heard some really spurious justification for this from someone on
the PowerShell team - but it's just NOT right.

Other than that (and notwithstanding the excellent AD provider in
PSCX:-) I think it would be good to find out if the AD team are
progressing on their own implementation? Again, I've asked the
question but (perhaps revealingly) never received feedback...

Have a good trip!

Chris

For my twopence worth

1) Whats happening with AD support

2) Any chance of the WMI provider that was demo'd at IT Forum 2005 becoming
a reality

3) An SMO provider for SQL support

4) Remoting - so can run Powershell against remote systems

--
Richard Siddaway
Please note that all scripts are supplied "as is" and with no warranty
Blog: http://richardsiddaway.spaces.live.com/
PowerShell User Group: http://www.get-psuguk.org.uk


"Keith Hill [MVP]" wrote:

> A bunch of the PowerShell MVPs will be heading off to the MVP summit next
> week (Mar 12-15). Hopefully we will get a chance to give the PowerShell
> team direct feedback on PowerShell. Obviously there's a *lot* to like about
> PowerShell but being on a software product myself I know that developers are
> usually more interested in hearing about things that could be better with
> their product. With that in mind, could you spend a bit of time thinking
> about the top three to five things about PowerShell that are either
> impediments to your work flow, unpleasantries, rough edges, bugs or things
> just plain piss you off and write those down here. As an MVP I would like
> to be able to represent the community and I'll do my best to convey your
> input in person. Of course, a lot of the PowerShell team members hang out
> here so some of them will likely see it here first but hey, that's OK.
>
> --
> Keith
>
>
>

My First concerns is how do I use Powershell for remote management. Please keep WMI out of it, which also possible from VBScript.

For example Remote Management of Services
For example View event log of remote machines

There are several ways to can get logs on remote machine for example psloglist.exe but the parsing functionality which lies in PS in not comparable
If some model actually growing on this front ?

Recently I heard Powershell is associated with Longhorn and one of the top 10 reason to adopt powershell( let's not comment on it)

If it is really going to top10 reason, Please make sure you are able to do everything from LONGHORN CORE with CMDLETS, this include AD and Etc management.

Thanks,
Techstarts.wordpress.com




"RichS" <RichS@discussions.microsoft.com> wrote in message news:8A243C9C-A1C7-4590-A608-BA136D41CA8C@microsoft.com...
> For my twopence worth
>
> 1) Whats happening with AD support
>
> 2) Any chance of the WMI provider that was demo'd at IT Forum 2005 becoming
> a reality
>
> 3) An SMO provider for SQL support
>
> 4) Remoting - so can run Powershell against remote systems
>
> --
> Richard Siddaway
> Please note that all scripts are supplied "as is" and with no warranty
> Blog: http://richardsiddaway.spaces.live.com/
> PowerShell User Group: http://www.get-psuguk.org.uk
>
>
> "Keith Hill [MVP]" wrote:
>
>> A bunch of the PowerShell MVPs will be heading off to the MVP summit next
>> week (Mar 12-15). Hopefully we will get a chance to give the PowerShell
>> team direct feedback on PowerShell. Obviously there's a *lot* to like about
>> PowerShell but being on a software product myself I know that developers are
>> usually more interested in hearing about things that could be better with
>> their product. With that in mind, could you spend a bit of time thinking
>> about the top three to five things about PowerShell that are either
>> impediments to your work flow, unpleasantries, rough edges, bugs or things
>> just plain piss you off and write those down here. As an MVP I would like
>> to be able to represent the community and I'll do my best to convey your
>> input in person. Of course, a lot of the PowerShell team members hang out
>> here so some of them will likely see it here first but hey, that's OK.
>>
>> --
>> Keith
>>
>>
>>

[top posting]

Another related thread is going on here:
http://www.scriptinganswers.com/foru...ts.asp?TID=544

"Keith Hill [MVP]" <r_keith_hill@no.spam.thank.u.hotmail.com> wrote in
message news:uswwcveYHHA.596@TK2MSFTNGP06.phx.gbl...
>A bunch of the PowerShell MVPs will be heading off to the MVP summit next
>week (Mar 12-15). Hopefully we will get a chance to give the PowerShell
>team direct feedback on PowerShell. Obviously there's a *lot* to like
>about PowerShell but being on a software product myself I know that
>developers are usually more interested in hearing about things that could
>be better with their product. With that in mind, could you spend a bit of
>time thinking about the top three to five things about PowerShell that are
>either impediments to your work flow, unpleasantries, rough edges, bugs or
>things just plain piss you off and write those down here. As an MVP I
>would like to be able to represent the community and I'll do my best to
>convey your input in person. Of course, a lot of the PowerShell team
>members hang out here so some of them will likely see it here first but
>hey, that's OK.
>
> --
> Keith
>

Use .NET for remote management. I currently manage over 400 TS and 150 other Servers all from one server. I do use WMI for some, but for the two you give. .NET works great.

For example Remote Management of Services
[System.ServiceProcess.Servicecontroller]
# need to add this [System.Reflection.Assembly]::LoadWithPartialName($name)

For example View event log of remote machines
[System.Diagnostics.EventLog]

--
Brandon Shell
---------------
Stop by my blog some time
Blog: http://www.bsonposh.com/
PSH Scripts Project: www.codeplex.com/psobject
--------------------------------------

"Techstarts" <preetamzare@gmail.com> wrote in message news:O9gFKerYHHA.3268@TK2MSFTNGP04.phx.gbl...

My First concerns is how do I use Powershell for remote management. Please keep WMI out of it, which also possible from VBScript.

For example Remote Management of Services
For example View event log of remote machines

There are several ways to can get logs on remote machine for example psloglist.exe but the parsing functionality which lies in PS in not comparable
If some model actually growing on this front ?

Recently I heard Powershell is associated with Longhorn and one of the top 10 reason to adopt powershell( let's not comment on it)

If it is really going to top10 reason, Please make sure you are able to do everything from LONGHORN CORE with CMDLETS, this include AD and Etc management.

Thanks,
Techstarts.wordpress.com




"RichS" <RichS@discussions.microsoft.com> wrote in message news:8A243C9C-A1C7-4590-A608-BA136D41CA8C@microsoft.com...
> For my twopence worth
>
> 1) Whats happening with AD support
>
> 2) Any chance of the WMI provider that was demo'd at IT Forum 2005 becoming
> a reality
>
> 3) An SMO provider for SQL support
>
> 4) Remoting - so can run Powershell against remote systems
>
> --
> Richard Siddaway
> Please note that all scripts are supplied "as is" and with no warranty
> Blog: http://richardsiddaway.spaces.live.com/
> PowerShell User Group: http://www.get-psuguk.org.uk
>
>
> "Keith Hill [MVP]" wrote:
>
>> A bunch of the PowerShell MVPs will be heading off to the MVP summit next
>> week (Mar 12-15). Hopefully we will get a chance to give the PowerShell
>> team direct feedback on PowerShell. Obviously there's a *lot* to like about
>> PowerShell but being on a software product myself I know that developers are
>> usually more interested in hearing about things that could be better with
>> their product. With that in mind, could you spend a bit of time thinking
>> about the top three to five things about PowerShell that are either
>> impediments to your work flow, unpleasantries, rough edges, bugs or things
>> just plain piss you off and write those down here. As an MVP I would like
>> to be able to represent the community and I'll do my best to convey your
>> input in person. Of course, a lot of the PowerShell team members hang out
>> here so some of them will likely see it here first but hey, that's OK.
>>
>> --
>> Keith
>>
>>
>>

"Marco Shaw" <marcoDOTshaw_@_gmailDOTcom> wrote in message
news:uBFkvkrYHHA.4692@TK2MSFTNGP04.phx.gbl...
> [top posting]
>
> Another related thread is going on here:
> http://www.scriptinganswers.com/foru...ts.asp?TID=544

Thanks for the feedback all, whether you gave it here or elsewhere.

--
Keith

http://powergadgets.com/csPg/forums/thread/282.aspx
"We know it is a hack and we spoke to one of the PowerShell team members
about this, what we need is for them to allow apps hosting PowerShell to
have control over how processes are run. If they supported this, it would
just be a matter of setting some properties such as CreateNoWindow

If you (and others) could request this through the connect site, it will
increase the chance they would consider it for V2 :-)"

Perhaps I'm too late... ;-)

1. A public road map of PowerShell.
2. Some idea of what support we can expect from other Microsoft products
(like an official provider for SQL server/Access, etc.).

"Marco Shaw" <marcoDOTshaw_@_gmailDOTcom> wrote in message
news:uLdOl5JZHHA.1240@TK2MSFTNGP04.phx.gbl...
> http://powergadgets.com/csPg/forums/thread/282.aspx
> "We know it is a hack and we spoke to one of the PowerShell team members
> about this, what we need is for them to allow apps hosting PowerShell to
> have control over how processes are run. If they supported this, it would
> just be a matter of setting some properties such as CreateNoWindow
>
> If you (and others) could request this through the connect site, it will
> increase the chance they would consider it for V2 :-)"
>
> Perhaps I'm too late... ;-)

Nope, not too late. :-)

--
Keith