brasilferro.blogg.se - Install spiceworks inventory on server 2016 core

#Install spiceworks inventory on server 2016 core update#

The core and CPU counts will get you a head start on licensing, although I have to confess that we’re not going to cover licensing as part of our training plan. If you’d like to get ambitious, add additional columns for Core Count, CPU Count, and Memory. (Me personally, I’d like to be at a poolside bar right now, but noooo.) There’s no wrong answers here: this step is about understanding where we’re at today, not where we’d like to be.

#Install spiceworks inventory on server 2016 core update#

That last column gets a little tricky – it means, if this server dies in a fire, what’s our Plan B? Are we going to restore the databases from another server? Will we fail over to a log shipped copy? Or will we update our resume and head out for an early lunch? As we go farther into the training, we’re going to get much more specific about Plan B.

Application Names (internal or external product names).

Business Users Affected (list of people to email when the server dies).

Department (sales, HR, accounting, IT, mixed use).

Environment (Production, QA, development, disaster recovery).

Edition (Standard, Enterprise, Developer).

SQL Server Version (2017, 2016, Azure SQL DB… well, maybe 2008 too, sadly).

My point is that when you’re in charge, you need to know exactly what you’re in charge of.

Or ask the CFO how much the annual budget is. Or walk into the CEO’s office and ask how many employees he has. But I mean, imagine if you COULD walk into his office and ask him that. NO, I mean, don’t actually DO that, because he’s going to ask you why the sales app is so slow. At your company, walk into the VP of Sales’s office and ask them how many salespeople they have.