What is PowerShell?

And should I deploy it to all my users, +/- 6K.

Is there any advantages?

Thanks.

S.

"S." <> wrote in message
news:...

To the question "What is PowerShell?"

Amazingly enough -- http://www.microsoft.com/powershell

> And should I deploy it to all my users, +/- 6K.

In general, you should *never* deploy anything unless you actually know what
it is, and why you're deploying it.

I'll presume that reviewing the provided link will also provide you your
answer to the second question.



--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

"Lawrence Garvin [MVP]" <> wrote in message
news:...
> "S." <> wrote in message
> news:...
>
> To the question "What is PowerShell?"
>
> Amazingly enough -- http://www.microsoft.com/powershell
>
>> And should I deploy it to all my users, +/- 6K.
>
> In general, you should *never* deploy anything unless you actually know
> what it is, and why you're deploying it.
>
> I'll presume that reviewing the provided link will also provide you your
> answer to the second question.
>
>
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> My Blog: http://onsitechsolutions.spaces.live.com
> Microsoft WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>

Yes, it is amazing... you found it on the Internet. So did I.

Let me rephrase; I am not an IT guy, I just own the network because I pay
for everything. So, our WSUS was recently put back in production and the IT
team apparently did not notice PowerShell being pushed to everybody.

Is there any advantages for me as a user to have PowerShell installed?
Also can it be removed thru the WSUS?

Thanks,

S.

"S." <> wrote in message
news:%...

>> To the question "What is PowerShell?"
>>
>> Amazingly enough -- http://www.microsoft.com/powershell
>>
>>> And should I deploy it to all my users, +/- 6K.
>>
>> In general, you should *never* deploy anything unless you actually know
>> what it is, and why you're deploying it.
>>
>> I'll presume that reviewing the provided link will also provide you your
>> answer to the second question.


> Yes, it is amazing... you found it on the Internet. So did I.

Okay, then let me put it this way, if you're not capable or interested in
reading the excellent descriptions posted on the Microsoft product page for
the product, then I don't have a hope of belief that you'd read anything *I*
wrote here, so I'm not particularly likely to invest the effort.

Furthermore, this is the *wrong* forum to be asking for general product
information. You asked if you should deploy the update, and I answered that
question, and the answer is still: You should not deploy an update until you
know what the product is, and I provided you a link to find the answer to
that question.


> Let me rephrase; I am not an IT guy, I just own the network because I pay
> for everything. So, our WSUS was recently put back in production and the
> IT team apparently did not notice PowerShell being pushed to everybody.

Installing PowerShell is not a bad thing; depending on the skill set of your
IT team it might be a Good Thing; it might even be an intentional thing! I
am intrigued with you second guessing the actions of your IT Team. If they
found it useful to deploy PowerShell to all systems (and, as I said, if
anybody on the team knows the product and can use it -- and they *should*),
then there's every reason in the world to deploy it to every system.

As for "not noticing"... *somebody* approved the update for all of your
systems. Presumably that "Somebody" had a reason for approving the package.


> Is there any advantages for me as a user to have PowerShell installed?

Not if you don't know what the product is or how to use it.


> Also can it be removed thru the WSUS?

Standard answer: Any product can be uninstalled from a client system via
WSUS if the product supports uninstallation. Typically this is limited to
products installed using the Windows Installer (MSI) technology. I believe
PowerShell uses MSI.


==========
Truly.. you should be asking these questions of your =IT TEAM=. If you want
to know why PowerShell was deployed -- ASK THEM! If you want to know *who*
approved it -- Tell the team leader to find out who approved it. If you want
an Executive Overview of the product -- ask your IT Team Leader. If you
don't like the answers you get, hire a new IT Team Leader. If you don't
trust your IT Team, or your IT Team Leader, then you might consider hiring a
paid consultant that you do trust.

Now, having had my say -- let me put this all in perspective. You posted
into a technical support forum (anonymously, to boot) where we (I) assume
the poster is an IT Pro / IT Administrator seeking technical assistance --
that is, after all, the purpose of this forum. You provided no background to
counter that presumption, and your questions were, in the context presented,
somewhat indicative of a rookie help desk op trying to get somebody else to
do their research for them.

While you're more than welcome to delegate research tasks to people who work
for you, and they're certainly expected to provide those answers, we (in
this forum) are *volunteers*, and our time here is limited, and personally I
like to maximize my effect in this forum, and as a result, I tend to point
people to existing resources quite frequently because retyping the same
answer over and over and over week after week gets hard on the fingertips
after a while.

Furthermore, this isn't a product training or marketing forum, so if you
post in here asking for basic information about "What is <some_product>?" I
can pretty much guarantee you you're going to get pointed to the Product
Information page at microsoft.com -- like I did. I'll be more than happy to
answer *technical questions* about Microsoft Windows Server Update Services
all day long, ad infinitum, and happily so -- but I'm not an executive
research assistant. :-)
==========

--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

"Lawrence Garvin [MVP]" <> wrote in message
news:%...
> "S." <> wrote in message
> news:%...
>
>>> To the question "What is PowerShell?"
>>>
>>> Amazingly enough -- http://www.microsoft.com/powershell
>>>
>>>> And should I deploy it to all my users, +/- 6K.
>>>
>>> In general, you should *never* deploy anything unless you actually know
>>> what it is, and why you're deploying it.
>>>
>>> I'll presume that reviewing the provided link will also provide you your
>>> answer to the second question.
>
>
>> Yes, it is amazing... you found it on the Internet. So did I.
>
> Okay, then let me put it this way, if you're not capable or interested in
> reading the excellent descriptions posted on the Microsoft product page
> for the product, then I don't have a hope of belief that you'd read
> anything *I* wrote here, so I'm not particularly likely to invest the
> effort.
>
> Furthermore, this is the *wrong* forum to be asking for general product
> information. You asked if you should deploy the update, and I answered
> that question, and the answer is still: You should not deploy an update
> until you know what the product is, and I provided you a link to find the
> answer to that question.
>
>
>> Let me rephrase; I am not an IT guy, I just own the network because I pay
>> for everything. So, our WSUS was recently put back in production and the
>> IT team apparently did not notice PowerShell being pushed to everybody.
>
> Installing PowerShell is not a bad thing; depending on the skill set of
> your IT team it might be a Good Thing; it might even be an intentional
> thing! I am intrigued with you second guessing the actions of your IT
> Team. If they found it useful to deploy PowerShell to all systems (and, as
> I said, if anybody on the team knows the product and can use it -- and
> they *should*), then there's every reason in the world to deploy it to
> every system.
>
> As for "not noticing"... *somebody* approved the update for all of your
> systems. Presumably that "Somebody" had a reason for approving the
> package.
>
>
>> Is there any advantages for me as a user to have PowerShell installed?
>
> Not if you don't know what the product is or how to use it.
>
>
>> Also can it be removed thru the WSUS?
>
> Standard answer: Any product can be uninstalled from a client system via
> WSUS if the product supports uninstallation. Typically this is limited to
> products installed using the Windows Installer (MSI) technology. I believe
> PowerShell uses MSI.
>
>
> ==========
> Truly.. you should be asking these questions of your =IT TEAM=. If you
> want to know why PowerShell was deployed -- ASK THEM! If you want to know
> *who* approved it -- Tell the team leader to find out who approved it. If
> you want an Executive Overview of the product -- ask your IT Team Leader.
> If you don't like the answers you get, hire a new IT Team Leader. If you
> don't trust your IT Team, or your IT Team Leader, then you might consider
> hiring a paid consultant that you do trust.
>
> Now, having had my say -- let me put this all in perspective. You posted
> into a technical support forum (anonymously, to boot) where we (I) assume
> the poster is an IT Pro / IT Administrator seeking technical assistance --
> that is, after all, the purpose of this forum. You provided no background
> to counter that presumption, and your questions were, in the context
> presented, somewhat indicative of a rookie help desk op trying to get
> somebody else to do their research for them.
>
> While you're more than welcome to delegate research tasks to people who
> work for you, and they're certainly expected to provide those answers, we
> (in this forum) are *volunteers*, and our time here is limited, and
> personally I like to maximize my effect in this forum, and as a result, I
> tend to point people to existing resources quite frequently because
> retyping the same answer over and over and over week after week gets hard
> on the fingertips after a while.
>
> Furthermore, this isn't a product training or marketing forum, so if you
> post in here asking for basic information about "What is <some_product>?"
> I can pretty much guarantee you you're going to get pointed to the Product
> Information page at microsoft.com -- like I did. I'll be more than happy
> to answer *technical questions* about Microsoft Windows Server Update
> Services all day long, ad infinitum, and happily so -- but I'm not an
> executive research assistant. :-)
> ==========
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> My Blog: http://onsitechsolutions.spaces.live.com
> Microsoft WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>

My god! Relax man! You are a touchy fellow mr. Garvin. I just asked a simple
question... if you don't want to answer then move on!

S.