You will need the previous step for this one. Start Reviewing Performance Data for Critical Systems & Servers May we humbly suggest using Lansweeper?ĥ. Because you cannot manage/optimize/secure what you do not know you have in the first place. Is it up to date and easily maintained? Or is it still managed manually in spreadsheets like it is in 1998? First, you need a reliable asset baseline before you can do anything. Now, before you do anything else, find out if the company has a complete IT inventory. Get a reliable IT Inventory as soon as possible Besides, in many cases, giving them some more time to use their brains will usually be enough to solve their problem. You will not actually have the time to follow up on the daily I-lost-my-password requests, but at least they will get the feeling like their ticket is "under review". Assign a due date for completion and make sure that the system sends you automated reminders. Categorize tickets according to priority and define who is responsible for each one. This is usually done using automated issue management software. Regardless, it is wise to set up an issue management system as soon as you start. When you are just starting out, you will probably have other things to worry about than logging requests and complaints. These measures are really the only thing that stands between you and a possible ransomware attack or an unexpected hardware failure. What is the backup rotation scheme? Do you need to take into account off-site storage? And when was the last disaster recovery plan performed? We advise you to do a DR test at least once a year for smaller businesses and every quarter for larger organizations of 150+ employees. Check if the backups are running as intended. Make Backups Before Making Changesīefore you make any changes, it is extremely important that you work on backups and a disaster recovery plan. Do not make the mistake of waiting too long in either case, because then you risk getting dragged into the daily run and you will lose your chance to make any meaningful changes at all. However, if you fill a senior position in charge of a team or if you are the sole sysadmin at your company, then you have the power to make changes as soon as you start. Will you become part of a team of sysadmins? Or did you get your first senior position? If you join a team, you probably will not have much say anyway, so better to observe first before you pitch your brilliant ideas. Well, it really depends on what your role will be. When you start a new job as a sysadmin, you might be wondering whether you should immediately start to implement changes or whether you should wait and observe first. In any case, let these 11 tips guide you on your new IT management journey. Just do not expect to be hailed a hero every day. Are you starting a new job as a system administrator? Or are you moving over to another company with a different IT estate? First off, congratulations! You are now the person who people will flock to if something goes wrong technically.