Mission Control update and management

Mission Control update process:

First things first. Here's a few things to know:

Please back up MongoDB/Mission Control before doing anything.
Mission Control lives on HOK-184vs server machine.
On that machine, the actual app is located at C:\NodeProjects\MissionControl
You can access that machine by requesting permission from one of the IT managers. James Blackadar is a good place to start. You will need Admin rights so ask for that right out of the gate. Once you have access rights just use RemoteDesktop to log into the machine.
Current version of MongoDB installed on that server machine is 3.4.7. Please see below for instructions on how to update MongoDB if needed.
Current version of Node.js is 8.3.0. Please see below for instructions on how to update Node.js if needed.
For Mission Control to work we need to run MongoDB server in the background at all times. That can be done by setting up a service. Please see below for more details.
For Mission Control to work we need to launch it every time the server machine is rebooted. That is currently done with a Task Scheduler. Please see below for more information.

You can download MongoDB for Windows Server 2008+ x64 from this link: MongoDB Download Page
Once you have it downloaded, you can place it in a Public Parking folder and then access it from the server machine like this:
I would copy it over to the server machine desktop, and then launch the installer. If the version upgrade is minor, for example from 3.4.7 to 3.4.9 Mongo will not create a new directory. If the update was a major one ie. 3.4.7 to 3.6.0 then it's possible that Mongo will create a new directory in C:\Program Files\MongoDB\Server\3.6
If Mongo created a new directory on update, that destroyed the Mongo service that was running in the background since that was pointing at the 3.4 location. To fix that follow these steps:

Launch the Command Prompt with elevated permissions (as Administrator). Use this command to navigate to Mongo's old location: cd "C:\Program Files\MongoDB\Server\3.4\bin" hit Enter now type in mongod --remove hit enter That will remove the current running service of MongoDB.
Now we need to install a new service with the MongoDB 3.6. So in the same session of Command Prompt you can navigate to new location of MongoDB by typing in cd "C:\Program Files\MongoDB\Server\3.6\bin' and hitting Enter. Then we need to add a service so type in: mongod --config "D:\MongoDB\mongo.config" --install` Now, as you can see the second argument is a path to config file that we will be using for the service. It was saved at the location above. If you wish to change it, just navigate to that folder and override the file.
Now, just verify that a new MongoDB service is running and is pointing at the right version of Mongo. Open Start menu and type in Services.
You might want to uninstall MongoDB 3.4 at this point. It's still installed.

You can get the latest Node.js from here: Node.js Download Page
The rest of steps are the same as for MongoDB, with the exception that it will not create a new directory for new version of Node, so you don't have to worry about that.
One thing that you do have to worry about is restarting the Node.js Task that is created in Task Scheduler. Go to Task Scheduler, and just manually hit Run:

As mentioned above Mission Control lives on C:\NodeProjects\MissionControl. All you have to do is copy/replace current version of Mission Control files with the latest one in your local drive.
You can just paste this path: \\ny-fwr-l011\c$\Users\konrad.sobon\OneDrive - HOK\GoogleDrive\Work\MissionControl into an explorer; where first group is your laptop/desktop name and rest is path to where Mission Control is stored.
You will have to restart Node.js after doing that, so just again, go to Task Scheduler and restart it there by hitting Run.