Suggestion for the first 90 days as sysadmin in new company ?

People,

What would be your suggestion as the task to do for the first 90 days as a System Administrator in the new company you joined ?

Thanks in advance.
LVL 13
Senior IT System EngineerSenior Systems EngineerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Shaun VermaakTechnical SpecialistCommented:
Fix over-permission accounts and check best practices
JohnBusiness Consultant (Owner)Commented:
I would spend the first part of your time learning the people and learning the systems. There may be reasons why things are the way they are (right or not right) and you need to understand the reasons before making changes.

Then, ask users what their pain points are. Good users will not be bashful. Address the pain points as best you can while observing good system practice.  Having passwords may be a pain point, but do not remove passwords to solve it.

Look at security practices and make sure the system has edge protection to prevent attacks.

Make sure there is a top notch spam filter is place. This will help prevent ransomware.

Good luck, make friends and integrate with the new company.

By the way, I provided Business Consulting to my clients and I have done this successfully for over 15 years. I practice what I wrote above and it pays off handsomely with return business.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Patrick BogersDatacenter platform engineer LindowsCommented:
I agree on all off the above.
But, make sure you have a helicopter view of what you are administrating, understand, correct and update the network documentation.
Make sure you understand how machines are licensed and how it is administrated.
Also learn about the backup policies so you know how to act in case off an emergency.

Cheers
Starting with Angular 5

Learn the essential features and functions of the popular JavaScript framework for building mobile, desktop and web applications.

arnoldCommented:
Agree with John and Patric, get a picture of use/utilization from the user perspective. This is part and parcel of John's suggestion to get an understanding of the issues users are experiencing.
Though one caviate deals with exactly what your role/responsibility is. In smaller firms a Sysadmin would likely be responsible for applications running in the systems for which they have responsibility while in larger firms that would be a responsibility of a separate group of which you might be the internal Sysadmin...  Understanding what your Role and having it clearly defined to avoid potentially attempting to access resources/system to which you shoukd not.

While John softly rebutted the suggestion Shaun made, I think under no circumstances are you when starting a new position start tailoring system setups, configuration management.
Best practices shoukd be ingrained in your approach, any changes you think are needed after the establishment of knowledge on the existing setup, interactions, etc. have to be presented to those in the decision making position with full description of all the remedies that have to be accomplished prior to implementation to minimize operational impact.
I.e. The permission setup is lax, so after tightening them over best practice a significant number of users are no longer able to perform their job.

In a small firm, be open to dealing with end user to understand/learn the applications in use whether those application are running on or tangentially relying on systems for which you gave responsibility.
Senior IT System EngineerSenior Systems EngineerAuthor Commented:
Thanks for the response guys, the company is quite large 1000+ people so in this case I will have to ask the service desk team about the most commonly occurring incidents.
arnoldCommented:
have your area of responsibility been clearly defined. I.e. You are responsible for this, that and the applications that are relying on these systems...
Senior IT System EngineerSenior Systems EngineerAuthor Commented:
Thanks all for the suggestions !
It's all make sense.
JohnBusiness Consultant (Owner)Commented:
You are very welcome and I was happy to help you with this.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
IT Administration

From novice to tech pro — start learning today.