I want to start off by saying that this is my very first time writing an article of any sort. Thanks to Rosen for letting me write as a guest on his awesome website. Anyhow, I hope you find the information below useful and practical as much as I have. Enjoy!
Several months ago, I quit Tech Support and started working as a Sys Admin for a storage company (still learning, there’s a looong way to go…). I knew about the power of SSH before, but on several occasions, I found out that creating SSH tunnels can be super useful and it gives you the freedom to quickly access devices from anywhere you want. In my particular situation, I have a Raspberry Pi 3 sitting at home, up and running all the time, which I use for pretty much anything that I want to experiment with, whenever I get the chance… That last part is key: I want to be able to access the little gadget whenever I feel like it, and not be restricted by my location or the computer I’m accessing it from.
After I set up proper port forwarding in my home router (check the web if you don’t know how to do that yet, it’s very useful), I had to SSH to my external IP address and the specific port, which would in turn forward that to port 22 on my Raspberry Pi, allowing me to type my password at the prompt. Pretty basic procedure but I wasn’t really happy with the fact that I have to specify and address, a port, and type a password. I wanted to create some sort of an alias which would include all that information. I wanted the process to be as automated as possible, and after quite some time digging around on the web, here are the possible solutions that I found:
Simple SSH with an SSH key
You can always use sshpass and use the -p flag to give the password in the command itself, but this is not very safe, as anybody with access can check the CLI history or the current SSH session process (ps aux | grep ssh) and see the password.
I had a student ask for some practical guidance on deploying software via SCCM application deployment model. So I decided to create one basic post about this topic.
Let’s start with brief overview. New model is using built in intelligence during deployment of software. Basically if software is provided by MSI file this is the easiest way to deploy, but we will speak about deploying EXE file. When MSI file is deployed almost every configuration is not needed. The picture is different when we speaking for EXE software. That’s why we will discus EXE software deployment because the process is not so clear.
Let’s start with application creation in SCCM.
Open Configuration Manager Console.
Click the Software Library workspace, expand Application Management, and then click Applications.
Right-click Applications, and then click Create Application.
In the Create Application Wizard, on the General page, ensure the Manual Specify the application information detect information about option is selected, and click Next.
Enter Application details.
On the Application Catalog page, click Next.
On the Deployment Types page, click Add to add a deployment type.
On the Create Deployment Type Wizard (note that the Create Application Wizard is still visible in the background) page, ensure the manually specify the deployment type information option is selected, click Next.
On General Information page, provide the application name, click Next.
On Content page, provide the following information: Network location of the program files (\\Sources\Software\WinSCP\v5.7.7\) and configure the installation (“winscp577setup.exe” /VERYSILENT), uninstallation parameters. (“C:\Program Files (x86)\WinSCP\unins000.exe” /VERYSILENT /NORESTART). Ensure the Run installation and uninstallation program as 32-bit process on 64-bit clients option is selected, click Next.
On Detection Method page, click Add Clause.
On Detection Rule page, ensure Registry is chosen from drop down menu Settings Type. Browse Local Machine registry hive for applications uninstall keys. Data Type is String. Ensure the This registry settings must satisfy the following rule to indicate the presence of the application option is selected and Operator: Equals, Value: 5.7.7 , click Ok.
On Detection Method page, click Next.
On User Experience page, click Next.
On Requirements page, click Next.
On Dependencies page, click Next.
On Summary page, click Next.
On Completion page, click Close.
On Summary page, click Next.
On Process page wait for process to finish and, click Close.
The Application has now been created and can be distributed and deployed with SCCM.