- #Adobe creative cloud update command line software#
- #Adobe creative cloud update command line professional#
This isn't 1980 any more and using a custom installer/uninstaller is not not needed or even desirable. It's also an insult to the integrity of the programmers who work for them." Such an approach is not even remotely in agreement with recognised management principles and practice. If the management won't spend money to fix things that are broken and don't stand behind continually improving and enhancing every aspect of a product, they are not doing their job properly. If your boss won't let you fix it, keep asking them, every time you talk to them, "can we fix it yet?", get your colleagues to ask the same question, again and again and again until they agree.
#Adobe creative cloud update command line software#
It is also the duty of every programmer at these companies: you should have pride in your work and not tolerate bad software to persist and cause other people to suffer for it! Fix it! If they have neglected these important functions for a long time, it will cost that next yacht for the CEO to fix the problems, but it is their duty to fix these issues, because they created them. These companies are not acting professionally.
#Adobe creative cloud update command line professional#
With all the money they make, they can't afford to sort out the rat's nest of an architecture they created so that sysadmins can manage it without pain? Professional software companies create products that work properly, for everyone that has to interact with them. It also really lowers my opinion of the companies involved.
To read that Adobe and other companies still make products which behave so badly for sysadmins, is quite a surprise. I am a programmer by trade, although not on things which are sold and licensed. I don't get on reddit as much as I'd like to, but when I stumbled on this discussion, I just had to comment. Remove-Item -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Microsoft Todo. 11002 64Bit" -Force -ErrorAction Silentl圜ontinue | Out-Null Remove-ItemProperty -Path "HKLM:\SOFTWARE\myOrg" -Name "Microsoft ToDo. Remove-AppxPackage -Package Microsoft.Todos_1.0_圆4_8wekyb3d8bbwe -AllUsers $Folder = "$\WindowsApps\Microsoft.Todos_1.0_圆4_8wekyb3d8bbwe" #Script to Uninstall Microsoft_ToDo_.11002_64Bit Your strategy wouldn’t work at scale.Īnyways I would read up on the impact of each set execution policy in relation to a ps session otherwise I think we're done here. We have 60k + machines to manage across NA, LATAM, EMEA and APAC regions. The fact that you "dont need scripts" tells me you don't have real volume. ps1 file I have sitting around that an sccm task seq would action on the client side. Remember I have no choice due to GP's in place that prevent me from otherwise achieving greater things in PS. WMI is just the closest thing to PS that I can use to action certain tasks behind the scene. *facepalm* I never said WMIC replaces powershell.
0 kommentar(er)
