If I am talking to a user that uses that server I only refer to the resource that they use:
This weekend we are performing system maintenance that will make WizBangApp unavailable from....... That's what they want to know, and all they need to know. From: [email protected] [mailto:[email protected]] On Behalf Of geoff Sent: Monday, July 14, 2014 1:51 PM To: ntsysadm Subject: [NTSysADM] Stupid terminology question OK sanity check please. When referring to the system your windows O/S tied to whether it is physical or virtual what term do you use? Essentially I need a good term that covers both physical and virtual in a single term. The best I have come up with is host but even that is confusing in some circles. Rant below if you want to read it <steps up on soapbox> I have numerous clients that refer to their server by their application name. OK, I get that. They see their environment as important, and don't care about the underlying O/S. But when I report some problem to them that involves the hostname they are like the proverbial deer in the headlights. "But that's not what it is called!" they retort. In the old days I would bite my tongue and patiently explain that my hostname is the physical system supporting their environment and with faces sufficiently saved we would move on. Now I get "But there isn't this a virtual server?" Hence my question. Don't even think about the discussion that ensues when it is getting underlying ESXi server that has an issue. <soap box stowed beneath desk till next needed> gt I'm just Playbookin' around
