General > General Technical Chat
Hell freezes over...
<< < (11/15) > >>
bd139:
Believe me no one wants powershell on Linux. 90% of the windows admins I know don't want it on windows because it's a fucking pile of shit through and through. They're literally trying to blur the lines between the platforms here to maintain relevance. It's a total impedance mismatch. It's really like hooking people on their first dose of crack cocaine and then hoping they will come back for more because they are now dependent on it.

Anyone who has used powershell for windows automation knows that it's a fucking dirty great big minefield of pain once you get over the "ooh this is cool" phase. It's basically a fucked up object oriented bastardisation of Perl mixed with .Net but underneath the pile is still WMI and COM. Ultimately it's a stack of shit 100 levels deep that if anything even goes slightly awry it's game over for 2 days.

Example: Literally I spent two fucking days of my life a couple of weeks back trying to get Import-PfxCertificate to run over a WinRM connection to set up a signing certificate on local account on a build farm. Turned out that there was a KB article which required a registry frig to fix, an AD setting that needed to be changed in LSP, an account setting that needed to be changed and then it didn't work with the originally provisioned account so a new one had to be set up which required a bounce through the company's helpdesk to cover secpol. When that didn't work and MSFT support went "we don't know how to fix it", we actually logged in by hand to 30 boxes and deployed the certificates manually.

That is your life with powershell. Automation with it is a waste of time.

Don't use it on Linux. You don't need it. How do you solve the above problem on Linux? Stick a file in /etc/pki. Ansible's copy task does the job instantly. Bob=uncle.

Fucks sake. Good job I'm paid by the hour to handle this shit.
Mr. Scram:

--- Quote from: bd139 on July 25, 2018, 08:40:25 am ---Believe me no one wants powershell on Linux. 90% of the windows admins I know don't want it on windows because it's a fucking pile of shit through and through. They're literally trying to blur the lines between the platforms here to maintain relevance. It's a total impedance mismatch. It's really like hooking people on their first dose of crack cocaine and then hoping they will come back for more because they are now dependent on it.

Anyone who has used powershell for windows automation knows that it's a fucking dirty great big minefield of pain once you get over the "ooh this is cool" phase. It's basically a fucked up object oriented bastardisation of Perl mixed with .Net but underneath the pile is still WMI and COM. Ultimately it's a stack of shit 100 levels deep that if anything even goes slightly awry it's game over for 2 days.

Example: Literally I spent two fucking days of my life a couple of weeks back trying to get Import-PfxCertificate to run over a WinRM connection to set up a signing certificate on local account on a build farm. Turned out that there was a KB article which required a registry frig to fix, an AD setting that needed to be changed in LSP, an account setting that needed to be changed and then it didn't work with the originally provisioned account so a new one had to be set up which required a bounce through the company's helpdesk to cover secpol. When that didn't work and MSFT support went "we don't know how to fix it", we actually logged in by hand to 30 boxes and deployed the certificates manually.

That is your life with powershell. Automation with it is a waste of time.

Don't use it on Linux. You don't need it. How do you solve the above problem on Linux? Stick a file in /etc/pki. Ansible's copy task does the job instantly. Bob=uncle.

Fucks sake. Good job I'm paid by the hour to handle this shit.

--- End quote ---
Powershell seems to be pretty well received in the admin world. It's a bit unfortunate Microsoft is pushing it at the cost of any and all GUIs, but it seems to work pretty well. It has to, of course.
bd139:
I really doesn't work well. You need to use some of the non windows tools to see how bad it is.

We've got 1-2 people managing 400+ machine fleets with ansible for example.

Powershell / windows DSC team, similarly sized deployments are at 8-10 people and most of them are bogged down in weird edge cases and problems.
Mr. Scram:

--- Quote from: bd139 on July 25, 2018, 10:11:50 am ---I really doesn't work well. You need to use some of the non windows tools to see how bad it is.

It is merely better than clickops.

--- End quote ---
Non Windows tools?
bd139:
Updated post above to clarify.

To note I'm the platform decision maker here and we're shifting away from the human-centric windows admin world as a whole. It is very difficult to reliably automate windows.
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod