June 23, 2010 at 7:26 am
There is a manager in another IT department who thinks PowerShell should be removed from all 2008 servers, should not be installed on any servers, and that "we should know this." We're asking him for some evidence.
In the meantime, is this possibly a known condition that I have missed?
Mike Hinds Lead Database Administrator1st Source BankMCP, MCTS
June 23, 2010 at 7:42 am
People choose to be ignorant of the progress of tools, I guess, but removing PowerShell is akin to removing cmd.exe. It's now a part of the operating system, and server services, like Exchange (2007+), WILL NOT FUNCTION without PowerShell.
The IT manager in question needs to take a more objective look at the direction of the industry.
June 23, 2010 at 8:12 am
Whoa! No, don't do that. You'll be shooting yourself in the face (yes, face, not foot). I put out a small blog post[/url] on this, just today, that addresses this just a little bit. But I can go on and on about why you should have it and use it.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 27, 2010 at 6:41 pm
Considering that Powershell is Microsoft scripting platform of choice for administration going forward. I would not recommend it. Plus, as it has already been said, some products will not work right without it removed.
I honestly cannot understand where this person is coming from on this without a reference. I mean, it is already being installed by default on:
Windows Server 2008
Windows Server 2008 R2
Windows Vista
Windows 7
Exchange 2007
Exchange 2010
SQL Server 2008
SQL Server 2008 R2
And the list will continue to go on and on...
Joie Andrew
"Since 1982"
June 28, 2010 at 6:59 am
Not to mention that the out of the box security settings are pretty tight:
Script exec is prohibited by default
ps1 is not associated with the shell
must provide a path to a script
underlying security is not bypassed
With just this in place, not to mention internal firewalls, appropriate group rights, etc., what the heck is there to worry about?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 28, 2010 at 7:02 am
Thanks to all for the ammunition.
Mike Hinds Lead Database Administrator1st Source BankMCP, MCTS
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply