Your first statement is to question if the OP is doing this as a school assignment or production? Is that relevant? Should we only help people who are running scripts in production environments? If they're testing in a test environment, do they not deserve help? Even if the question is for help with a school assignment, you don't have to answer.Ģ. I can't speak for whoever gave the thumbs down to your response, but I can see some potential reasons why your response might have been given a thumbs down.ġ. "per user" GPO to check and install the software on the machine (GPOs have the ability to check is application have been installed)Įlse why not see if that application have an "Enterprise" installer edition (like Chrome, that can be installed on the machines instead of per user) ? logon script to check and install the software from the local drive ? machine set up script to copy installers from a central file server to local drive (maybe c:\software) Then as an alternative to downloading the software, why not have Then the script only checks if the software is installed on the profile, what about version checking or version updates ? If your client have 10 users on 10 machines, then is this "per profile" installation going to run 100 times ? What if PS version changes and scripts stop running ? Are you going to future-proof it ? What do you mean "preciously were signing into a common local user" ? I know that this can be achieved via Intune, PDQ, and now, Action1, but our customer is not interested in adding in an extra suite to just manage one software install. We have an RMM but we can't trigger a more simple install script at login, which means we would just be spamming the machines every 15 minutes with a check script. In lieu of each employee installing the software whenever they jump to a new machine, we were hoping to just script it. Oddly, the software that they use needs to be installed on each user profile for them to use. We have a customer that is using AzureAD to sign into profiles where they were preciously were signing into a common local user. In the terminal, we can now issue this command to check the version of slack on your system.Īnd ta-da!, this is a working Slack-Desktop on Linux Mint.Powershell # Define the paths where Slack executable is expected to be installed $slackPath32 = "C:\Program Files (x86)\Slack\slack.exe" $slackPath64 = "C:\Program Files\Slack\slack.exe" $slackUserProfilePath = "$env:USERPROFILE\AppData\Local\slack\slack.exe" # URL to download the Slack installer $downloadUrl = "" # Temp location to save the downloaded installer $downloadLocation = "$env:TEMP\SlackSetup.exe" # Check if Slack is installed $slackInstalled = ( Test-Path $slackPath32 ) -or ( Test-Path $slackPath64 ) -or ( Test-Path $slackUserProfilePath ) if ( -not $slackInstalled ) deb package on linux mint with the command: This prompt converts the rpm file to a debian file which can now be installed on all Debian Based Operating Systems.įinally, we must install the. Replace the slack package with your file version in the above command. This is the command to convert the rpm file to a deb file using the Alien utility. This is the downloaded rpm package at home/./Downloads/Programs Alien is a computer conversion program that converts different linux software packages to. In this tutorial, I will use a work-around to convert the RPM version to a DEB version which is installable on Debian-based Operating Systems.Ĭonversion of an rpm package to a deb package requires a linux utility called Alien. Note: RPM version cannot be installed on Debian based Operating Systems like Ubuntu, Linux Mint. Visit the official website of slack and download the rpm version. Enter fullscreen mode Exit fullscreen mode
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |