Technical Policies - Not Client Facing
Computer Naming Conventions
Computer Host Names The primary concerns are that: 1. New computers have a consistent but unique name 2. Rebuilt or upgraded computers (whether physical or virtual) or computers that have OS reinstalled are given the same name as the name as the ...
Tech Best Practices
Scripts Please remember that when you run a script, job, RMM component, etc. to install software, if there is a dashboard that the software reports to, you should always confirm that the device shows up in the dashboard. (e.g., AutoElevate, Webroot, ...
Policy on Driver and Software Updates
While working on a device, you may see updates that have not been installed. Remember that our RMM platform handles Windows updates and some Mac and third party updates. If an update hasn't occurred, there may be a good reason why. Don't do updates ...
Guidelines for Creating IT Glue Client-Facing Instructions
We use the "Documents" asset to create customer-facing instructions. Use the Document editor to create instructions. It includes various modules (text, graphic, steps) that make is easier to edit the document again later. Please do not create a ...
MSA Customer Issues that Require Immediate Action
RMM Workstation is unreachable or crashed Response might be reboot attempt through power management device. if one is attached. If customer does not have power management (most don't), the only immediate response possible may be walking the user ...
Special Procedures - On-Site Visits for Non-Managed Customers
Please do not perform work that was not assigned in the ticket. If the customer asks for other work to be performed, you must get approval from a senior staff member first. Before Work Begins 1. BACKUP SYSTEM IN PLACE? If the client does not have a ...
Documentation: Best Practices
Document Anything New or Changed When we set up anything that can be defined as “new” or “changed”, it must be documented. For example: a customer that wasn’t using Splashtop is now using it. That’s something new so we need to add a remote access ...
Internal Security Policies and Procedures
1. Wherever possible, employees must use 2FA. Where Duo is not applicable, employees must use stand-alone 2FA. 2. Employees must use complex passwords that are at least 8 characters long and contain uppercase, lowercase and at least one symbol. 3. ...
Remote Support Procedures (in progress)
Do not connect to a user's computer unless you are schedule or have permission to connect at that time. If you work on a customer's computer in the admin account, make sure to log out of the admin profile when you are done. If you leave the computer ...
Items Tech Must Bring Onsite
1. Laptop 2. Spare Ethernet cable at least 6' long (preferably more than one) 3. USB flash drive 4. External USB hard drive with min 500GB of free space.
Customer Logins Security Policy
Create separate logins for all customers, whether for NAS shares, email, AD, etc. Users should never share logins.
Technician On-Site Appointment Procedures
Please do not perform work that was not assigned in the ticket. If the customer asks for other work to be performed, you must get approval from a senior technician or office admin first. On-Site Visit Procedures Administrative items to bring to every ...
Customer Data Safety Policies: Customer Data, Operating Systems, Network Device Settings
Introduction Next to security, avoiding data loss is our most important priority. We do not remove anything - accounts, files, email folders, etc. - ever without a backup unless the customer provides written assurance that they no longer need the ...