Network Management - Organizing + adding computers + users

We have 25~ now

But we are growing and that's why we want to change these.

A big issue is that we have our own server and we have applications that only apply to it. Everything is set to reconcile a username and password and that grants you access on our network, which in turn allows you access our software on the server

you username in the Local computer And the network would be:

BStalin

Since we get brand new computers, you have to register an email address to set it up. So we would use our domain name and create an email account called

BStalin@xxxxxx.com


But when you leave the company, we change the computer name on the local machine to the next person and then take out the logins for the server as well. When you have as much turn over as we do, you'll find changing computer names every 6 months is tiresome

Are you trying to do all this in house ? At worst, you should be looking into a local MSP

I have to have administrative access for these users. They will need to be admins logging into our server. Not just simple accounts

I'm helping the sys admin who says he does not no which direction to take.

I think we need to baby step this.


Question #1: How do big companies handle Microsoft licenses?

A problem we have is when Cody works there for 8 years and then up and leaves and we need to rebuild the machine for Tim cause he starts in 2 days, what's the easiest way to keep and organize my software license?

pretty sure this was the sysadmin interview going down.

As others said, use AD.

For naming conventions, you can name the PCs using asset ids or by the phone extension. I prefer the phone extension bc when I pull up AD, I know where a certain pc may be located. If there are PCs than phone extensions just use descriptive names (i.e. receptionist-pc , OpMgr-pc, etc)

fire sysadmin and go hire a managed service provider immediately. this guy doesnt have a clue if he hasn't figured this out.


if your attached to him tell him to start learning microsoft services like azure ad and move to cloud cause he sure as hell shouldn't be running infrastructure

Like others are saying, you need active directory. Your workstations will need Win10 Pro to be able to join the domain. Figure out a naming convention for your workstations, they don't need to, nor should they be named with their users name. Use a generic local username. All my PC's on each site have the same local user account name. The end user will never see the local account in an AD environment. They will use their AD account.

When setting up a new workstation, if you are using Win10 Pro, it should give you an option to set up the PC on a domain. With that option, you will not be forced to create and register an email.

All user accounts will be made and managed through AD. If a workstation is joined to the domain, anyone with an AD account in your domain will be able to log into it with their account. You can manage the accounts' admin rights through AD.

quote:

---

lol...@gmail me and I'll be happy to take his place

---

Pretty sure if this place paid well, they'd already have a legit sysadmin

What a clusterfrick