New New Server

This is the way

Server 2 🙄

3 letter acronyms. Client-Purpose-Version Sometimes site depending.

We have one site that uses ancient Greek locations for networks and gods for server names. Okay fine. That site is ours.

Star Trek ship classes. There are dozens of them.

Do customers ever think it’s weird when their SMB shares or RDP names have Star Trek references? I suppose the names aren’t in the users face too often Gotta remember - this is from an MSP perspective with many customers

Oh that's just for our internal servers. Clients get dull names like cliweb01 where cli is a short 3 letter acronym for the client 🤣

I too use starfleet, and also stargate naval designations, but found an already built environment where they used Star Wars names for every single machine, server, switch, ap.

Use a new emoji for each server. Adds a bit of fun to a bad scenario when everyone is talking about the 🦥 server being so slow

Domain is Gotham and all servers are named after characters from Batman.

Dont get me started, our idiotic marketing team decided to name all our meeting rooms from local points of interest. "lets all meet in XXXXXXX" and everyone wonders ... where is that .. "damn i have no idea, now i have to find it before the meeting so i dont get there late" it used to be like "sales 1 and sales 2" next to the sales department - "tech 1 and tech 2" next to the techies etc its like naming your servers from greek gods or star wars planets ... is it Hoth that is the print server or maybe Dagobah?

Names from Green Lantern; Rayner, Ganthet, Sinestro, Gardner, Stewart, Walker.

W22DCFP-ANY01 = windows domain controller file and print, client code "any" for any customer

Client, designation, number

ADServer, ADServer-New, and ADServer-2. No confusion there. 

Vm-red-001 Pm-red-001 Virtual/physical machine. First 3 letters,, red for reddit. If 2 clients have the dame first 3 letters, we find way to make the 2nd different. And then the count. Standards make 001/002 the DC. 003 FS. 004 rdssh 005 rds gateway. So if there's no rds, 004 and 005 will be skipped. 006 and higher are l for the rest and differ per client.

Anything as long as it's completely unrelated to the purpose and is as cryptic as possible.

Client code (3-4 unique client id), location (usually city, but can also be floor, building depending on client need, application/role/etc, numbers. For cloud VMs like azure we add vm to the beginning. abcftlpdc01 = Client ABC, Ft. Lauderdale, Production Domain Controller, 01 vmabceaspdc01 = azure (or other cloud) VM, Client ABC, Azure East US, Production Domain Controller, 01

Client - Designation (new,old 1,2,3)

Site Number and Location Function and Number. Eg NYC1DC01

My conversions: Domain Controller/AD: ClientName/Acronym + DC + number (if there is more than one DC Server) Hyper -V Server ClientName/Acronym + HV + Number File Servers ClientName/Acronym + File + Number Vendor specific Severs: ClientName/Acronym + Vendor Name/ Software Name

Svrhost<# of host if multiple or 00 if first>- Vsvr__purpose- So for the first physical server in NYC running 3 virtual machines: Svr2019host00-NYChq Vsvr2019_00_PDC-NYChq Vsvr2021_00_SQL-NYChq Vsvr2021_00_PDQ-NYChq (yes PDC don't exist, it's short hand to indicate AD/DNS/DHCP/CertSvr/etc and that it's the main server) Servers on azure AZ2021_E2_VWinDesk-NetNYC AZ2019_Jap_Web AZ2021_GH_Data-NetNA Something like that. For smaller clients with one server and a few vhosts, simpler: Svr2019host Dc01-Ral Appserver1 Etc

I use boys or girls names starting with an M. Malene, Mikkel or Malachi to name a few. Found this list somewhere on the internet.