Showing posts with label GUI. Show all posts
Showing posts with label GUI. Show all posts

Wednesday, April 7, 2021

File Synchronization and Backup

 Having access to your files at any given time is a convenience some people today rely on so heavily, that as a person who often never really needs any particular files I find it humorous. Despite this, I have been rather obsessive about file access and backups in the past few years. This is so much so that I realized recently I have over 50 USB flash drives and 4 external hard drives accessible to the network. tow of the hard drives are specifically for TV and movies because I keep duplicates at the ready should an external fail on Kodi. One of them is an old Apple time machine that is ready to go, but I don't actually use it. Another is an old Seagate I have had for about 10 years or so now that keeps chugging along despite the slow speeds and for the small files I usually work with it works just as I need it. Taking it a step further, I have a RAID 1 setup on my main laptop with most of my documents duplicated onto a secondary laptop, and everything else was in Google Drive.


So here's the thing about all of this. Google Drive, like any other cloud service, can have terms changed, storage space altered, and on top of that, do you really want your files in "the cloud?" Truth be told you could easily just manually copy files onto each device you have and be relatively fine. So if you do have storage available, you should make use of it. So stop being lazy and back up your files yourself!


That being said, of course there are solutions that depending on the effort you put in, can be  Let me start out by saying that ANY local network solution can be an "anywhere" solution with tools like a VPN. I personally have OpenVPN setup at home because my Asus router has that option built in. You can create your own OpenVPN server fairly easily, but that's not the topic at hand for this.


For file synchronizing across multiple devices and types of devices, I was recently made aware of some rather cool software called Syncthing. The program name is rather unappealing, but the software is one of the coolest things I did not realize I needed in my life. What sets this apart from any solution I have seen before is that it is a "decentralized" file sync program. This means it uses a Peer-to-Peer model as opposed to the typical Server-Client model. If that doesn't make sense to you, view it like this. Normally you have a "centralized" server that handles all requests, files get uploaded to and downloaded from the server. In a peer-to-peer model, any device can serve files to any device asking and any device can ask any device that has the file for the file. This creates a huge advantage in file accessibility for a busy connection.


This means a few things to consider. The first is that you will need at least two devices to synchronize, not a hard thing to find now-a-days. The second is that rather than configuring a server, you must configure each device. As of writing this, I have four devices connected and the only limiting factor is a raspberry pi 4 connected to a very slow external. So here is some food for thought over any problems I have run into.


The first thing is be certain where you want the files stored and what you will sync. The reason being if you blanket a whole swath of folders, there is a chance some program specific or computer specific stuff will take up room on devices you do not need it to. I have separated all of my stuff to be synchronized out of the normal workflow and pieced it back together with shortcuts. I have also tried to break down the folders that get synced into separate items on the list for greater control and flexibility. The second thing to keep in mind is space on each device, what you need, and where. This is in addition to deciding a good folder structure.


With that in mind, there is a little catch on Linux. I have an external formatted in NTFS, which Linux is not exactly a fan of. I did this because the ntfs-3g stuff works better than ext drivers on Windows which love to lock up the file system and make everything unusable. If you have the same setup, the device should be mounted with the user you launch Syncthing under as the owner. If you launch it as root, there's probably nothing to worry about.


Head on over to the download page and install Syncthing on any and every device you want to be involved. For Windows, I suggest also installing the SyncTrayzor just for ease of access. To launch on Windows, you can use the SyncTrayzor in the start menu or you can launch it via command line with the syncthing command. To get to the console to set everything up you can either launch a web browser and go to http://127.0.0.1:8384/ or if you have SyncTrazor, there is an icon in your notification tray there is an icon that you can right click on and select "Open SyncTrayzor." We want to begin to lock things down a bit and make them better.


It will start out with asking you for statistical data, do as you want there. Then it will mention something about setting a username and password, let's do that. If you missed it on the box, just go to the "Actions" menu on the top right hand corner and select "Settings." Under the "GUI" tab at the top you can set a username, a password, and select a theme if you wish to change the color scheme. I also recommend you check the option to use HTTPS for the GUI because why wouldn't you encrypt when there's an option? Click save, then "X" out of the GUI and relaunch. If you are using the website, you need to change http://127.0.0.1:8384/ to https://127.0.0.1:8384/ if you checked the option. After that you should be all set where it has a default folder. Let's remove that. To remove a folder, you click on it and select "Edit" and then "Remove" on the edit page, bottom left corner this time. Now you can go through and add all the folders you want to sync, remember to organize them first. After you get all the folders set, you can start on the next device. Follow the same process. It does a good job at auto-discovery for when you add a device. When you add the device, the device you are trying to add will prompt for approval, nice little security measure.


When you have both devices set of any folder, if any, each is going to share (keep in mind if you want to merge a folder on both devices, sync one to the other and then move the files you want into that folder to make things easier). Just edit the folder on the device and use the "Sharing" tab up top and check any device you want to sync with.


Before you add more devices, I recommend you let everything sync and normalize before you add the next device. When you get a third setup, you will need to add it to  ALL devices you want to sync with, then on ALL the other devices elect to share with ALL devices expected to sync for the best stability and performance. You can keep a more-or-less centralized model, but I would take advantage of removing single point failures and have everything connect.


Now let's talk phone. Chances are the big thing is going to be syncing your photos to your computer. We can do that and ditch Google Photos or whatever other invasive "online photo album" software is the flavor of the day. It's generally more polite this way because chances are you will also help protect the privacy of friends and family that may make an appearance in your photos. Unless you're like me and the majority of your pictures are sleeping dogs, screw-ups at work, and memes.



That being said, just download the app for your phone. Add your folders in there, then we can add devices the cool way. Select the devices tab, hit the plus, then select that little QR code icon. Then on the device you need to add, on it's interface under "Actions" there is a "Show ID" option that gives you a QR code you can scan. As usual, it the device will want confirmation that you are trying to add it. Share your folders like normal.

So that's a quick overview of a fairly easy to use, decentralized, file sync program. So here are my thoughts.

The first is, it's really cool and I am quite happy with it. The interface is usable and it's just easy to setup and use. The only real critique I have is I really wish there was a built in function to move a folder. Instead I have to remove the folder in the control panel, move it on the system, then tell it to re-add the folder in the new location and wait for it to sync and a couple of times complain about "conflicting" files. Not a deal breaker for me, the advantages are just too good.

All that being said, I will continue in my search for secure and private alternatives for everyday conveniences and hope that you too will join me in taking the necessary steps to protect your data. Targeted marketing and advertisements on top of data breaches has hit levels it never should have all for the sake of what is convenient and I hope we can remedy it. If that's not your goal, then maybe you will at least find some cool software to check out.


Wednesday, September 2, 2020

Starting Out as a Computer Tech (part 2)

Previously I covered some basic tasks you may need for dealing with a domain and Active Directory. Now I would like to cover some more local tasks. Even if a computer is on a domain, there is some necessary local management that may be necessary. Common tasks while locally managing a computer may include adding/altering/editing local users, cleaning out files, installing/troubleshooting programs, managing printers, changing default applications, changing display settings, and so on. There are actually a lot of things you still need to do locally. Some of these things can be done remotely, but they alter the local computer, not the domain. As a result, we will consider this local administration.


In my current environment I work with, every year we inadvertently need to change local administrators for some higher privileged computers. By this, I mean we add the domain account to be recognized as a local administrator when they log in. This is not necessarily the best way to do things, but quick and dirty tends to be the go to for a lot of IT people on all levels. On Windows 10 you go to the settings cog on the start menu. The category we need to look in is Accounts. On the left-hand side, there will be "Other users." To add a domain account, you will click "Add a work or school user." For a domain user, we add the domain before a backslash (\), like this: example\some_user. You then select the level you want the user at, like Administrator. When a user is added, they will appear in a list below the option to add a user. When you click on the user, there is a "Change account type" and "Remove" option.


The same things can be done with Powershell. For this we need knowledge of four commands: Get-LocalGroup, Get-LocalGroupMember, Add-LocalGroupMember, and Remove-LocalGroupMember. We can list all the group names with Get-LocalGroup. After you have a list of the group names and decide which one you want, for example Administrators, you can check what users are in the group by doing something like Get-LocalGroupMember -Group Administrators. When we want to add a user to a group to make them an administrator, we run a command like Add-LocalGroupMember -Group Administrators -Member example\some_user. Much in the same way, we can remove users with Remove-LocalGroupMember -Group Administrators -Member example\some_user. As mentioned before, the big advantage of Powershell in a lot of cases is doing things remotely.


The Command Prompt also offers the same functionality as different commands, specifically through the net command. The quick translation would look like this:

Get-LocalGroup would be net localgroup

Get-LocalGroupMember -Group Administrators would be net localgroup administrators

Add-LocalGroupMember -Group Administrators -Member example\some_user would be net localgroup administrators /add example\some_user

Remove-LocalGroupMember -Group Administrators -Member example\some_user would be net localgroup administrators /delete example\some_user

 

 Cleaning out files is another common task you may need to do. The first general maintenance cleanup task will be using Disk Cleanup. You can get to it by searching in the start menu for Disk Cleanup or Windows+r and running cleanmgr.exe. Disk Cleanup is something you may want to use to keep free space clear from various temporary files and Windows updates. You may need to tell it to include system files after the first scan if Windows update files are not showing up. Just go and select anything on the list you do not think you need and let it clean up the space.


Sometimes stuff may glitch out and the hard drive will be out of space and no files seem to be found. The times I have run into this, it was temporary files that decided they were permanent. You may need to go to C:\Windows\Temp and manually delete those files. The same can be done with Powershell by doing Remove-Item -Path C:\Windows\Temp\* -Force -Recurse.


The last bit of cleanup of files I often need to do is for network profiles stuck locally. This requires two steps. The first is to delete the folder under C:\Users that needs to be removed. The second step requires deleting a registry key. To delete the registry key, the first thing you need to do is launch regedit through regedit.exe with either Windows+r or the start menu. Navigate the tree to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList to find where all the profiles are. When you click on the items in the ProfileList, there will be keys on the right-hand side. ProfileImagePath will be the value that points to the profile folder. Delete the item on the left-hand side with a ProfileImagePath that matches a user folder you deleted. Whenever you are done, be sure to restart the computer.


Installing and troubleshooting programs is fairly straight-forward. You may need to check when you right-click a program and select Run as administrator. You may also need to right-click, go to properties, select the compatibility tab and select a compatibility mode. Be sure if you do that, you go through the "Change settings for all users" button at the bottom.


Moving on to one of the most hated topics, printers. The nature of a printer containing mechanically moving parts, software/drivers, and in some cases networking makes them a very difficult animal to deal with. For now, let's talk about installing and setting default printers. The problem I run into with printers is their user specific nature. To be guaranteed a printer gets installed and setup correctly you should try to do it entirely while logged in as the user that needs it, add it, and set it to default. Some printers may need you to download a driver or run a CD, some may need you to add it via the network. I will not go into any more detail than that, I hate dealing with printers and wish you luck in doing as little as possible with them.


Changing default applications is a user specific task that will probably cause a brain aneurysm for most techs. What should be a simple task often confuses people and Microsoft seems to often make no effort to make this any easier. The easiest way to set a default application to run a file type, is to right click, select "Open with" and make sure when you pick the program the checkbox is selected with "Always use this app to open ____ files." Sometimes this is not an immediate option. For that we go to the Settings cog on the start menu. Go to the Apps category and select Default apps on the left. The first list is of the basics like what to open websites or emails with. Just click on the icon and pick the program you want. At the bottom, you have "Choose default apps by file type." This is the pain one. Click on it to see the massive list of files types. There is no easy way to jump to a specific point, so you scroll down to the file type you want to alter the program for and change it by clicking on the icon next to the file type. I have to frequently do this with PDFs because for some reason it breaks a lot and resets back to Edge from Adobe Reader DC.


Since I work in a school system, changing display settings is an every day thing. Computers are connected to projectors here and second monitors there and it always seems people want it set up differently. There are also "problems" people report because of it. So let's go over how to change things. The first, and easiest when at a computer, is to press Windows+p to bring up a quick display menu on the right-hand side of your screen. There are four options PC only, Duplicate, Extend, Second screen/projector only. Duplicate shows both displays the same, extend has two separate desktop spaces, and the other two should be self-explanatory. The catch is often that Duplicate almost always messes up the resolution and extend might have the wrong screen as the "primary" display, making for a difficult time logging in. To access more settings, you can go to the start menu cog wheel Settings, go to the System category and Display on the left-hand side. This will show you your displays and you can tell it to "Identify" with the button below to tell you which screen is which. After they are identified, you can then easily drag the screens around on the settings to align them how they are in real life, they do not have to be an even match, or can be on top of each other, all sorts of things. To make one of them a primary display, select the screen and at the bottom there is a check box for "Make this my main display." You can also adjust your resolution and change the same settings that you get when you press Windows+p. There are also ways to do things over a CLI, but I'll talk about those later.


So here's a scenario I get all the time. A work order will say "Computer not coming on" or "screen is black and I can't log in, but I can see the mouse." So what is the problem? The answer is it's connected to a projector that is off, the projector is marked as the main display, and it's extended. The quick solution is to turn on the projector, press Windows+p, and then select Duplicate. To a tech it may seem simple and obvious, but normal people do not think "display settings," they think "it doesn't work" and get stuck panicking most of the time.


This is just a brief overview of some basic points required for being IT. There is still a lot more to cover. I hope someone somewhere finds this helpful.

Tuesday, September 1, 2020

Starting Out as a Computer Tech (part 1)

 As I gain more experience at my job as an IT Specialist, more often people are coming to me for answers. So I figure why not write down some of this to see if maybe people new to the tech world or looking to get into it can have some answers.

 

Back when I first started as a tech, I was completely lost and no one was really willing to show or teach me anything. Everything before being a tech was just personal computer stuff, no servers or large systems to deal with. My biggest mistake was not looking into stuff for large enterprise solutions. Becoming familiar with these kinds of systems will give you an edge over most newcomers. There is also a good expectation that where your job starts and ends will blur due to more items being computerized and network capable. So to start, you should want to have an idea of what areas you will need at least some knowledge in.


The most common baseline for people I know is the Comptia A+. This gives a basic understanding of computer hardware, operating systems, and computer concepts. Most IT jobs will also want some basic understanding of networking. The most common starting point that I get with job interviews and the like is some understanding of Windows Servers and Active Directory. Other knowledge areas may also include VOIP (voice over IP), Linux, and scripting. Another common thing I find interviewers ask about is familiarity with whatever flavor of ticketing software they use. The ticketing software is always weird to me, it's usually just a website on their intranet and there are a lot of different ones. The one my work currently uses is called SysAid.


So let's start with some of the basics of an IT job. Active Directory is something I commonly hear a few short and simple questions on, but what you need to know can vary. The absolute basics you should know are how to join AD, move objects in AD, terms like DC, OU, CN, GP, LDAP, and Kerberos. You will also need to know what tools you can use to work with these. Let's start with defining terms and acronyms.


The Domain Controller is a server(s) that has AD DS (Active Directory Domain Services) installed on it. Some call this the DC, but DC can also mean Domain Component. The term OU will also be used a lot, this means Organizational Unit which is a group in AD that will often include your policies known as GP (Group Policies). The Common Name (CN) will be things like a device or username, or various built in things. Lightweight Directory Access Protocol (LDAP, pronounced el-dap) is part of the suite of software that makes up what is AD. The main reason to recognize the term LDAP is because you may come across something that needs an LDAP path. These are a pain, but there's a few tricks to using and navigating it all a little easier. The final term you should be familiar with is Kerberos. Kerberos is the authentication part of the AD software which uses what are referred to as tickets to authenticate.


Now keep that in the back of your head, it's time to discuss tools for working with AD. In most cases, you will probably be working on a desktop and not a server. To add a computer to AD from the computer itself we have a few different tools at our disposal. This can be done through the Control Panel or Powershell. To get to the menu we need for the Control Panel has a few different ways as well. You can click on the start menu and type out Control Panel, you can press Windows+R and type out Control Panel then run it, you can open up the file explorer, right click on This PC and select Properties which will jump you to the Control Panel item we need to get to. When in Control Panel, under Category view you click on System and Security, then System, or if you are in icon view there should be one at the start called System. Under Computer name, domain, and workgroup settings, you click on Change settings. On the window that pops up, there should be a button called Change... next to text about renaming the computer, click Change. From the window that pops up, you can type in a name, change the workgroup name, or select the radio button for domain and type in your domain name. After you do this, the computer will need to restart.


One thing to mention now is that some of the tools necessary for working with a domain are in the Windows Remote Server Administration Tools (RSAT). Depending on your Windows version (October 2018 and later), it may be available through Settings > Apps > Windows optional features. Just do a quick Google search to see specifically what you need.


For those that prefer a command line way of doing this, we can use Powershell commands. For this, we use the Add-Computer module. To get to an Administrative Powershell session, you can press Windows+x then a, or right click on the start menu and select Windows Powershell (Admin). From here you can run a command like so:

Add-Computer -Domain "example.domain.com" -Credential "example\your-name" -Restart


After joining a domain, it may be necessary to view any policies applied to that computer to make sure policies were applied. For this we need to look at the Active Directory Users and Computers. As usual there is a graphical (GUI) way of doing things and a command line (CLI) way of doing things. The CLI way of doing things is a bit more involved, so I am going to highlight the GUI way for now. In comes the Microsoft Management Console (MMC). The MMC uses MSC files for various interfaces to do a lot of administration on Windows, these are also called Snap-Ins. I may cover more on that later, but we will be using a few of these over the course of learning things. So for the MMC Snap-in we need to run dsa.msc with either Windows+r or a start menu search. It has a tree-style drop down menu and to move a computer from one group to another it's as simple as a drag and drop.


Once you have joined a domain or moved to a new group, settings are set through Group Policy (GP). These policies should theoretically update themselves to the computer, but when you movie it from one group to another sometimes updates may or may not work there way through. It may also be necessary to force policies through. There are a few ways to update these policies. The first is a bit more passive, restarting the computer. I have had many times where this simply does not get everything. Opening an Administrative Command Prompt or Powershell we can use the command gpupdate /force to update and optionally add the /boot option to restart or logout if it is necessary to apply certain policies. From a Powershell we have the alternative command Invoke-GPUpdate with flags -Force and -Boot. The advantage of using Powershell is we can also run the command remotely with the -Computer option, for example: Invoke-GPUpdate -Computer "example\test-computer" -Force -Boot. Personally, I try to use Powershell commands over CMD as much as possible because of the possibility to continue with remote administration and management.


If we need to view the applied policies to a computer we look at the Resultant Set of Policy (RSOP). For the RSOP MSC, we can either search for in the start menu or press Windows+r and run rsop.msc. This will open up a window that should allow you to browse through policies applied to whatever computer you are on or whatever user you are logged in with. The GUI should be easy enough to understand.


To rename a computer on the domain or remove it from the domain is as simple as being logged in as an administrator and going about the same way you joined it to the domain. Removing it from the domain just requires changing over to a workgroup.


Hopefully this guide will be helpful to people as a quick overview of some basic tech work in enterprise style environments. When I started out, I had nothing to go on, but my interview allowed me to use Google, which was nice. With any luck, I should have plenty more to add to this.

Sunday, January 7, 2018

Cabal install of wxHaskell CBool Error

So recently, I have been trying to dive back into programming with a little more oomph than a one-off project. I figured setting up a GUI along side would help keep me motivated. Now my current computer is an older Mac Book Pro because it is one of the few laptops in the house with a working battery. After diving around a large amount of fluff without any real substance, I decided going with wxHaskell would be the better choice. So I made sure wx was installed and did a cabal install wx, and wouldn't you know it that it failed.

src/haskell/Graphics/UI/WXCore/WxcTypes.hs:752:20: error:
    Ambiguous occurrence ‘CBool’
    It could refer to either ‘Foreign.C.CBool’,
                             imported from ‘Foreign.C’ at src/haskell/Graphics/UI/WXCore/WxcTypes.hs:126:1-16
                             (and originally defined in ‘Foreign.C.Types’)
                          or ‘Graphics.UI.WXCore.WxcTypes.CBool’,
                             defined at src/haskell/Graphics/UI/WXCore/WxcTypes.hs:750:1
    |
752 | toCBool :: Bool -> CBool
    |                    ^^^^^

src/haskell/Graphics/UI/WXCore/WxcTypes.hs:755:22: error:
    Ambiguous occurrence ‘CBool’
    It could refer to either ‘Foreign.C.CBool’,
                             imported from ‘Foreign.C’ at src/haskell/Graphics/UI/WXCore/WxcTypes.hs:126:1-16
                             (and originally defined in ‘Foreign.C.Types’)
                          or ‘Graphics.UI.WXCore.WxcTypes.CBool’,
                             defined at src/haskell/Graphics/UI/WXCore/WxcTypes.hs:750:1
    |
755 | withBoolResult :: IO CBool -> IO Bool
    |                      ^^^^^

src/haskell/Graphics/UI/WXCore/WxcTypes.hs:760:14: error:
    Ambiguous occurrence ‘CBool’
    It could refer to either ‘Foreign.C.CBool’,
                             imported from ‘Foreign.C’ at src/haskell/Graphics/UI/WXCore/WxcTypes.hs:126:1-16
                             (and originally defined in ‘Foreign.C.Types’)
                          or ‘Graphics.UI.WXCore.WxcTypes.CBool’,
                             defined at src/haskell/Graphics/UI/WXCore/WxcTypes.hs:750:1
    |
760 | fromCBool :: CBool -> Bool
    |              ^^^^^

src/haskell/Graphics/UI/WXCore/WxcTypes.hs:763:55: error:
    Ambiguous occurrence ‘CBool’
    It could refer to either ‘Foreign.C.CBool’,
                             imported from ‘Foreign.C’ at src/haskell/Graphics/UI/WXCore/WxcTypes.hs:126:1-16
                             (and originally defined in ‘Foreign.C.Types’)
                          or ‘Graphics.UI.WXCore.WxcTypes.CBool’,
                             defined at src/haskell/Graphics/UI/WXCore/WxcTypes.hs:750:1
    |
763 | foreign import ccall "intToBool" intToCBool :: Int -> CBool
    |                                                       ^^^^^

src/haskell/Graphics/UI/WXCore/WxcTypes.hs:764:48: error:
    Ambiguous occurrence ‘CBool’
    It could refer to either ‘Foreign.C.CBool’,
                             imported from ‘Foreign.C’ at src/haskell/Graphics/UI/WXCore/WxcTypes.hs:126:1-16
                             (and originally defined in ‘Foreign.C.Types’)
                          or ‘Graphics.UI.WXCore.WxcTypes.CBool’,
                             defined at src/haskell/Graphics/UI/WXCore/WxcTypes.hs:750:1
    |
764 | foreign import ccall "boolToInt" cboolToInt :: CBool -> Int
    |                                                ^^^^^
cabal: Leaving directory '/var/folders/8_/gbh6jvpj5dng4lmty_f9bjwh0000gn/T/cabal-tmp-50540/wxcore-0.92.3.0'
cabal: Error: some packages failed to install:
wx-0.92.3.0-GsmnFZQfuQrJCt8TV3hj5w depends on wx-0.92.3.0 which failed to
install.
wxcore-0.92.3.0-Cn2phmaLu563t5S6tEBzjw failed during the building phase. The
exception was:
ExitFailure 1

So with that big mess, it was time to hunt for what to do. With any luck this will be fixed soon because I generally have very little idea of what I'm doing. So the first step was to see if there was an alternative without manual intervention. Nope. So, I downloaded the package that was having the problem.

https://hackage.haskell.org/package/wxcore

Then we extract and open up src/haskell/Graphics/UI/WXCore/WxcTypes.hs and edit line 127 to

import Foreign.C hiding (CBool)

Save the file, open up a terminal. Navigate to the wxcore-0.92.3.0 folder and run

cabal install

After it hopefully succeeds, which it did for me, just simply

cabal install wx

I hope this helps anyone that needs and that the need doesn't last too long. I came across someone mentioning this fix on Stack overflow I think, but I can't find the link to it and don't plan to search too hard for it.


Thursday, July 6, 2017

ChocolateyGUI Invalid Path with OneGet

So recently while browsing around some stuff about about Windows 10, I found out about OneGet. This is a package manager manager in Powershell. I think this could be super useful. So one of the package managers I added was Chocolatey. I also wanted to install the GUI for I figure it may be easier to browse packages that way. Upon installation and execution, I got met with a huge error screen along the lines of:

System.IO.InvalidDataException: invalid Chocolatey Path. Check that chocolateyInstall is correct in the app.config

So on and so fourth. After reading through the git page on this error and taking some time to consider the confusion around "how did you install chocolatey?" I realized that specifically it's not actually installed when you just add it to OneGet. So here's the fix. After you add chocolatey, you need to INSTALL it. Just like this:

Install-Package chocolatey

After that, it should run without a hitch. Hope this helps someone out there. Package managers are great, aren't they?