Reference:
https://social.technet.microsoft.com/Forums/windows/en-US/07cfcb73-796d-48aa-96a9-08280a1ef25a/ mapping-home-directory-with-username-variable?forum=w7itprogeneral

The net use command is a Windows command that can be used to create a batch script to map multiple shares.
The net use command can connect or disconnect a computer from a shared resource, such as a network drive or a printer, or display information about computer connections. The syntax of the net use command is:
net use [devicename | *] [\\computername\sharename[\u0003volume] [password | *]]
[/user:[domainname\]username] [/user:[dotted domain name\]username] [/user:[[username@dotted domain name] [/savecred] [/smartcard] [{/delete | /persistent:{yes | no}}] where:
devicename = the drive letter or printer port to assign to the shared resource computername = the name of the computer that provides access to the shared resource sharename = the name of the shared resource password = the password needed to access the shared resource /user = specifies a different username to make the connection /savecred = stores the provided credentials for future use /smartcard = uses a smart card for authentication /delete = cancels a network connection and removes the connection from the list of persistent connections /persistent = controls whether the connection is restored at logon To create a batch script to map multiple shares, you can use the net use command with different drive letters and share names, for example:
net use W: \\computer1\share1 net use X: \\computer2\share2 net use Y: \\computer3\share3 You can also add other options, such as passwords, usernames, or persistence, as needed. To save the batch script, you can use Notepad or any text editor and save the file with a .bat extension12.
References: 1 https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/net-use 2
https://www.watchingthenet.com/create-a-batch-file-to-map-drives-folders.html

FinanceApp software is running as a service named "FinanceApp Service". The service description says "Provides financial data and calculations for the FinanceApp software". The service status is "Stopped", which means that the service is not running and the software is not functional. The service startup type is "Manual", which means that the service needs to be started manually by the user or the administrator. The service log on as is "Local System", which means that the service runs under a predefined local account that has extensive privileges on the local computer.
To fix the issue with the FinanceApp software, you need to do two things:
First, you need to start the service, so that the software can run. To do this, you can right-click on the service name and select "Start" from the menu. Alternatively, you can select the service name and click on the "Start" button on the toolbar. You should see a message saying that the service has started successfully.
Second, you need to change the service startup type, so that the service can start automatically every time the server boots up. This way, you don't have to contact the help desk every time the issue occurs. To do this, you can right-click on the service name and select "Properties" from the menu. Alternatively, you can select the service name and click on the "Properties" button on the toolbar. You should see a window with several tabs and options. On the "General" tab, under "Startup type", you can select "Automatic" from the drop-down list. Then, click on "OK" to save your changes.
By doing these two steps, you should be able to use the FinanceApp software without any problems.
The MarketApp software is running as a service named "MarketApp Service". The service description says "Provides market data and analysis for the MarketApp software". The service status is "Running", which means that the service is running and the software is functional. However, as you reported, the software may crash sometimes, which can cause significant downtime. The service startup type is "Automatic", which means that the service starts automatically every time the server boots up. The service log on as is "TestAccount", which is a test account that was probably used for development or testing purposes.
To fix the issue with the MarketApp software, you need to do one thing:
You need to change the service log on as, so that the service runs under a proper account that has sufficient permissions and security settings for production use. To do this, you can right-click on the service name and select "Properties" from the menu. Alternatively, you can select the service name and click on the "Properties" button on the toolbar. You should see a window with several tabs and options. On the "Log On" tab, under "Log on as", you can select either "Local System account" or "This account". If you choose "Local System account", then the service will run under a predefined local account that has extensive privileges on the local computer. If you choose "This account", then you will need to enter a valid username and password for an account that has appropriate permissions and security settings for running the service. You may need to consult with your IT team or your software vendor to determine which option is best for your situation. Then, click on "OK" to save your changes.

Always load servers from the bottom up. This prevents servers from becoming top-heavy and tipping also we do not alternate the direction of the airflow because that would have already been setup on the room with airflow sensors.