Going from Exchange 2003 to Exchange 2007 was a switch, but with powershell and the ease of doing things in there has made the switch easier. Where I had to search for things in the GUI in 2003, with the powershell command, it is much quicker for me to find what I need.
kudos to powershell.
Discussion on:
View:
Show:
So, let me get this straight. The one major thing that business loves, the ease of administration for Windows through the GUI and the related ease of finding administrators who are just 'good with computers' or relatively low cost, is going away?
While I agree that this is a good thing for systems stability and stimulates the need for dedicated, or at least trained, IT staff, this could be a potentially bad move for MS. What's to stop people making the move to Linux on the back end if administration becomes equally as difficult a task?
While I agree that this is a good thing for systems stability and stimulates the need for dedicated, or at least trained, IT staff, this could be a potentially bad move for MS. What's to stop people making the move to Linux on the back end if administration becomes equally as difficult a task?
I'll have to admit that I fall more into the 'good with computers' category of admins than the nitty gritty script type. Not that I couldn't make the DOS command line sing back in the day. However when it comes to servers, both email and database, the GUI has enabled me to get them working and manage them will little effort. Is that the best? Probably not, but it has worked to this point. The lack of GUI is one of the things that has stymied me in the Linux front.
MS should be mindful that the GUI is what got them to this point. To totally forsake it now would be a major blunder. However from what I could pick up from the article they are keeping the GUI for simple or common admin tasks, but requiring more complex tasks to be from Powershell.
MS should be mindful that the GUI is what got them to this point. To totally forsake it now would be a major blunder. However from what I could pick up from the article they are keeping the GUI for simple or common admin tasks, but requiring more complex tasks to be from Powershell.
I agree that powershell should be mastered, but one thing I noticed about this blog (and many others) is that recommendations are given without links to training or resources.
Obviously, I'll find the proper resources to train myself. But this is not unlike me sending an email to my users saying "You MUST use Outlook merge to send out mass emails or we will be blacklisted," without telling them how to do it.
Obviously, I'll find the proper resources to train myself. But this is not unlike me sending an email to my users saying "You MUST use Outlook merge to send out mass emails or we will be blacklisted," without telling them how to do it.
Call it what you like - it's still a DOS shell. GUI it up all you want...it's still a DOS shell. Never went away no matter what they've been hyping to the masses...
I dutifully installed PS about eighteen months, two years ago, went to my local community college for a class, and seriously almost never use the thing. MS seems to think it's groovy that PS functions return objects, not text, but the arcane backbends you have to use to extract just the info you need -- *if* you can extract it -- are just too darn much trouble. Why can't MS have a *single*, *procedural*, *competent* scripting language that persists from OS to OS like Unix?
Ok I've been out of major IT stream for a bit but still have a finger or 2 in it. But this.... I really don't get. MS have flogged GUI over cmd for eons and its been great... Now PS is a must....? Has to be learned and mastered? WHY?!!! This is the same camp that's been railing and sqwacking at Linux and Unix for years...!!! This is BS. Glad I'm not in it anymore!!
Please excuse my ignorance, I'm just looking into PS for the first time.
My job involves developing apps that automate common business routines. My coding environment usually includes VB, VBA, or VB Script, and SQL Server. Can PowerShell be considered a substitue for VB Script and/or VBA in MS Office app dev?
My job involves developing apps that automate common business routines. My coding environment usually includes VB, VBA, or VB Script, and SQL Server. Can PowerShell be considered a substitue for VB Script and/or VBA in MS Office app dev?
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
