What's new
Old Chevelles

Welcome to OldChevelles.com, built by Auto Enthusiasts for Auto Enthusiasts. Cars are not our only interests so please feel free to post about any subject the community might enjoy or you just feel you need to air.

We respect free speech and constructive dialogue however we don't allow threatening talk against members, nudity, or pornography. Threads are monitored and trolls are not tolerated.

This site is completely free and there are no costs. Please enjoy and provide feedback.
  • We've enabled the website app for anyone who wants to use it on a mobile or desktop device.

  • We've changed the header logo to display our Member's Cars.

    If you'd like your car to show up there, go to the forum Site Bugs & Feature Requests and post your image in the "Member's Car Pictures for the Header Logo" and we'll add your car into the lineup.

Microsoft killing off 3 legacy services in Windows - one of which goes back to the MS-DOS days...

I have to question why the one was kept around for so long in the first place.

DOS has really been gone for a long time, Powershell is the current CLI. DOS is there as an emulation for basic commands. The services mentioned are old and rarely used BUT... there will be some legacy applications that will die if removed.
 
Had a company who wanted to hire me as a consultant to setup and test powershell scripts for windows servers and exchange. I went and met with them and they wanted to see a sample of some of what I've written and they were blown away and offered me the job on the spot and then tried to inform me I'd be teaching their IT staff how to write powershell scripts, and I declined. Then they offered to double the pay and I looked at them for a second and said no again. Got a call later in the day that they still wanted to hire for the second offer (double salary) and I didn't need to teach them, but they wanted me to sign a 1 year contract and work for them for 30 hours a week and I said nope. Then they cut the hours to 20 a week, then 15, then 10. I guess they wanted me but after I saw their setup and what they were doing, they were way below my aptitude and I didn't want to waste my time writing stupidly simple scripts a high schooler could do. I used to love doing the really complicated scripts that executed multiple tasks across the enterprise by selecting options.
 
Had a company who wanted to hire me as a consultant to setup and test powershell scripts for windows servers and exchange. I went and met with them and they wanted to see a sample of some of what I've written and they were blown away and offered me the job on the spot and then tried to inform me I'd be teaching their IT staff how to write powershell scripts, and I declined. Then they offered to double the pay and I looked at them for a second and said no again. Got a call later in the day that they still wanted to hire for the second offer (double salary) and I didn't need to teach them, but they wanted me to sign a 1 year contract and work for them for 30 hours a week and I said nope. Then they cut the hours to 20 a week, then 15, then 10. I guess they wanted me but after I saw their setup and what they were doing, they were way below my aptitude and I didn't want to waste my time writing stupidly simple scripts a high schooler could do. I used to love doing the really complicated scripts that executed multiple tasks across the enterprise by selecting options.
Scripting is a special skill.

If I find an example of a Powershell Script I need I can adapt it and make it work in my environment. At work, everything is locked down so tight it takes alot of work to get the rights needed to do a task.
 
Scripting is a special skill.

If I find an example of a Powershell Script I need I can adapt it and make it work in my environment. At work, everything is locked down so tight it takes alot of work to get the rights needed to do a task.

Heh, I wrote scripts that changed rights, ran the task, then change the rights back. Done it a number of times. Had one admin who thought he was the shit and had his system locked down, so when I ran the script he said wouldn't run, it sent him into a panic and his boss (the CIO) called me into his office and tried to hire me to take that guys position. I respectfully declined. I've always been the guy who liked to just be a contractor and went where the pay and the jobs were a challenge.
 
Heh, I wrote scripts that changed rights, ran the task, then change the rights back. Done it a number of times. Had one admin who thought he was the shit and had his system locked down, so when I ran the script he said wouldn't run, it sent him into a panic and his boss (the CIO) called me into his office and tried to hire me to take that guys position. I respectfully declined. I've always been the guy who liked to just be a contractor and went where the pay and the jobs were a challenge.
Powershell is awesome to create roles and services without manual intervention.
 
Top Bottom