Main Area and Open Discussion > General Software Discussion

Resources for learning Windows PowerShell

<< < (2/3) > >>

wraith808:
If what was said during that article is true, I'd recommend a different approach.  Though you'll need some basics in PS... I'd go for a deep dive with Chocolatey.  You can use it in Windows Powershell, but you can also use it in the standard command line.  In that manner, you can get experience with the package manager aspect, and focus on exactly what you want and is relevant in powershell when/if the package manager does come to fruition.

https://chocolatey.org/
https://github.com/chocolatey/chocolatey
http://www.pcworld.com/article/2459950/how-to-use-chocolatey-a-delicious-windows-package-manager.html
http://lifehacker.com/5942417/chocolatey-brings-lightning-quick-linux-style-package-management-to-windows
https://groups.google.com/forum/#!forum/chocolatey

As far as Powershell, I'd take a look at Powershell Succinctly by Syncfusion.

http://www.syncfusion.com/resources/techportal/ebooks/powershell

It's free, though they do want you to register.  All of the succinctly series books are well done, and this one is no exception.

40hz:
Chocolatey is pretty interesting. I'm working with a medium-sized client to see if it can be used to handle all PC software installations and updates company-wide using the private feed feature and a local repository for security/management purposes.

Right now it looks very promising in testing. And certainly less complex or expensive than going with MS Systems Center. :Thmbsup:

x16wda:
And certainly less complex or expensive than going with MS Systems Center.
-40hz (November 29, 2014, 01:09 PM)
--- End quote ---

I'd rather deploy software manually on 5.25" floppies after swimming through leech-infested piranha tanks than use System Center.

Well, almost.  :P

40hz:
And certainly less complex or expensive than going with MS Systems Center.
-40hz (November 29, 2014, 01:09 PM)
--- End quote ---

I'd rather deploy software manually on 5.25" floppies after swimming through leech-infested piranha tanks than use System Center.

Well, almost.  :P
-x16wda (November 29, 2014, 06:42 PM)
--- End quote ---

Hear ya.  ;D It is a lot to get your head around. And it always struck me as being fussier and more complex than it needed to be. But that could just be ignorance on my part. I've done little more than read a few books and play with it a bit. I wouldn't even pretend to be up on it's intricacies. I know enough to know I'd to sub it out if I ever got called on to implement or maintain it.

Fortunately, my work is primarily with clients that are far too small to justify implementing MSC. And those few that are big enough to benefit already have the expertise in-house to handle it. It's a full time job from what I've seen.

 8)

x16wda:
One of our larger clients has core CALs for their 1500 or so workstations, and since that includes the necessary pieces, they've mandated using SCCM/SCEP for A/V and patching. In 15 geographically dispersed (including international) locations. With a single SCCM server. And me, in my spare time, to manage it. Regardless of the fact that SCEP is crap. And that they have to use something else to handle the servers.   :wallbash: :wallbash: :wallbash: :wallbash:

It's just so ungodly ungainly to do ANYTHING with it. Rube Goldberg would be proud.

Navigation

[0] Message Index

[#] Next page

[*] Previous page