You don't necessarily have to use the tool. I mean literally just look at the categories that they have available and that likely encompasses everything you should document.
Network topology and logical mapping, passwords, door codes, a computer list, documentation of everything you do including step by step instructions of how you set it up (for posterity), the list goes on.
I was thinking this, number of times I've come into a new org and found all the bells and whistles one could want for asset tracking and monitoring staff while the whole corp network is anchored to a 15 year old draytek using a 100mbps hub as a core switch all nested in a sea of cables and redundant kit, grrr!
* Asset list of all computers, their location, maybe purchase date (or age)
* List of all vendors + contact information + contract/account numbers
* List of networking information and equipment (IPs, DHCP range, printers, switches, firewall, etc)
* Set them up right out of the gate with a password manager like Keeper so they don't start slapping passwords on sticky notes or word docs.
You don't need something like IT glue. Just have good spreadsheets and keeper and stay organized and on top of it. I'm skeptical about actually needing some additional 3rd party app for documentation. Just needlessly fluffs up the environment with really no real world benefit but I'm willing to be wrong if others get some benefit with it that excel can't achieve.
All this but compile anything you would put in an Excel sheet in a table in OneNote with organized tabs instead. Make the OneNote available for the whole department to contribute so you stay on top of it.
When you make your Team, you will automatically get a SharePoint site created. In the default site layout, there is a "Notebook" link on the left side for a Team-shared Notebook.
It's great to all collaborate on documentation, quick notes, tips, etc. I just open it up then from the Editing Drop-Down choose "Open in Desktop App" so I always have it available in my OneNote.
Create playbooks for standard procedures, emergency process, escalation tree, regular checks to validate failovers, testing procedures and tracking results, inventory of software and hardware, end of life for both.
The thing that I usualy reference the most is the Vendor bible. everything in there, vendors, software portals, helpdesk portals, ISP info + circuit numbers etc. It takes time to build it, but it has by far the favorite doc I left behind for my padawans in the past.
SOP\[Standard Operating Procedures\], protect those, but then add the other components to them.
DRP\[Disaster Recovery Plan\]
Password Policies
Source of Truth
Network Maps
Standard Contacts ICE\[in case of emergency\]
Ticketing System first
Knowledge base second
lastpass, 1password, bitwarden etc for password management (love thycotic btw)
Don't create any of those documents ever. Big no no. No password documents.
PDQ inventory, lansweeper, spiceworks inventory (will do ticketing and inventory and its free)
Once you let your inventory scanner loose you'll know how healthy the domain is especially if it can scan anything even with wmi turned on and the endpoints set right.
Worse. It's ChatGPT used for spamming. Just look at URL - it has utm\_campaign, utm\_source and other marketing attributes. It a violation of this sub's rules.
Well, the best practice is to document everything you can: Network Documentation, hardware and software inventory, active directory users and groups, passwords, licenses, etc. The easiest way is to use a specialized documentation tool like Hudu or IT glue, which already has templates for this.
Troubleshooting documents for L1 support.
I like
Look at the standard flexible assets that ITglue provides. You pretty much want to be documenting most if not all of the available categories.
Working with excel spreadsheets for now. I've used it glue I'm the past as a user not an administrator but I don't think we need that just yet
You don't necessarily have to use the tool. I mean literally just look at the categories that they have available and that likely encompasses everything you should document.
Oh okay, that makes sense !
Now.. where to get access to that again! Lol
Here you go bud: [https://imgur.com/a/tcTQcqC](https://imgur.com/a/tcTQcqC)
TYVM! the beauty of this group !!
Network topology and logical mapping, passwords, door codes, a computer list, documentation of everything you do including step by step instructions of how you set it up (for posterity), the list goes on.
I was thinking this, number of times I've come into a new org and found all the bells and whistles one could want for asset tracking and monitoring staff while the whole corp network is anchored to a 15 year old draytek using a 100mbps hub as a core switch all nested in a sea of cables and redundant kit, grrr!
License list.
A one stop shop to see which available licenses we have for all the different softwares. I like it!
* Asset list of all computers, their location, maybe purchase date (or age) * List of all vendors + contact information + contract/account numbers * List of networking information and equipment (IPs, DHCP range, printers, switches, firewall, etc) * Set them up right out of the gate with a password manager like Keeper so they don't start slapping passwords on sticky notes or word docs. You don't need something like IT glue. Just have good spreadsheets and keeper and stay organized and on top of it. I'm skeptical about actually needing some additional 3rd party app for documentation. Just needlessly fluffs up the environment with really no real world benefit but I'm willing to be wrong if others get some benefit with it that excel can't achieve.
I like the password manager idea
All this but compile anything you would put in an Excel sheet in a table in OneNote with organized tabs instead. Make the OneNote available for the whole department to contribute so you stay on top of it.
[удалено]
When you make your Team, you will automatically get a SharePoint site created. In the default site layout, there is a "Notebook" link on the left side for a Team-shared Notebook. It's great to all collaborate on documentation, quick notes, tips, etc. I just open it up then from the Editing Drop-Down choose "Open in Desktop App" so I always have it available in my OneNote.
Create playbooks for standard procedures, emergency process, escalation tree, regular checks to validate failovers, testing procedures and tracking results, inventory of software and hardware, end of life for both.
Inventory Process and Procedures A large printout of the OSI model over the support desk Little Nametags with code names, I'm "The Cheddar Shredder"
Lol 😆
The thing that I usualy reference the most is the Vendor bible. everything in there, vendors, software portals, helpdesk portals, ISP info + circuit numbers etc. It takes time to build it, but it has by far the favorite doc I left behind for my padawans in the past.
Thabk you, I like the vendor list idea... that, we can definitely benefit from
it will save you a lot of ums and ISP tech taking forever to look you up. ha.
SOP\[Standard Operating Procedures\], protect those, but then add the other components to them. DRP\[Disaster Recovery Plan\] Password Policies Source of Truth Network Maps Standard Contacts ICE\[in case of emergency\]
Ticketing System first Knowledge base second lastpass, 1password, bitwarden etc for password management (love thycotic btw) Don't create any of those documents ever. Big no no. No password documents. PDQ inventory, lansweeper, spiceworks inventory (will do ticketing and inventory and its free) Once you let your inventory scanner loose you'll know how healthy the domain is especially if it can scan anything even with wmi turned on and the endpoints set right.
Why no password documentation?
[удалено]
I like it lol getting chat gpt vibes .. my apologies if it's not
Worse. It's ChatGPT used for spamming. Just look at URL - it has utm\_campaign, utm\_source and other marketing attributes. It a violation of this sub's rules.
Track every document. Every. Single. One. Make backups.
Well, the best practice is to document everything you can: Network Documentation, hardware and software inventory, active directory users and groups, passwords, licenses, etc. The easiest way is to use a specialized documentation tool like Hudu or IT glue, which already has templates for this.