Pre-Relocation Inventory for SBS Server 2008

livpie

Member
Reaction score
8
Location
Northeast Ohio
I have a IT documentation manual that I prepare for all of my clients. The goal is to provide the client with something they can easily reference to either assist them when I am not present or to help me when I am onsite so that I do not have to constantly ask for login information, etc. (As a disclaimer: I will include as little or as much information as the client wants documented) The manual consists of the following:

Network Device Configuration
  • Type of Device (From switches to workstations)
  • Manufacturer/Model/Hardware/Firmware Info
  • Login Information (if any)
  • Network Settings (MAC Address/Speed/DHCP or Static/IP Address/Subnet/DNS Servers)
  • Network Settings - Devices (Similiar to above with relevant settings to that device)
Network Plot
  • A graphical representation of the network to help easily identify where devices are located
Login Information
  • Workstation Login Info
  • Router Logins
  • Wireless Network Login Info
  • Email Login Info
  • Any logins that are acquired while working with client (This can be anything from website specific logins to proprietary software logins.)
Software License Inventory
  • Software Title
  • License or Serial #
  • Specific computer software is licensed to
Miscellaneous Information
  • Any information that is gathered over time that is relevant to servicing their IT needs that does not fit into a previous category
Work Log
  • Detailed description of work completed along with the date of the visit

Currently, I am in the process of quoting a relocation for a small office which consists of 1 SBS 2008 Standard, 8 workstations, 2 network printers, using DSL Internet with a static IP. I don't have any other clients that have SBS and I am just now starting to learn it. In my quote I am allowing time for a Pre-Relocation Inventory which will allow me to gather the above information.

My question is for the SBS. I want to make sure I perform a proper inventory on it as well but am not experienced enough to know all the things I should inventory. I would appreciate if anyone could tell me what they feel I should inventory that would be relevant information that I could include in the manual and also help me make sure I am prepared on the day of the move.

Any thoughts would be greatly appreciated.
 
Last edited:
I actually used to make something very similar, but I also used it for myself when going on-site. It really helped to look at one for a quick refresh of the entire scenario. Since a lot of the scenarios included multiple servers, each server would have its own guide. On the guide I had the same as you, but I also included:

What the role of the server was & what it provided the company with (was it a Terminal Server ,a File Server, Exchange server).

ALL of the serial key associated to that server. Be it the Windows server key, Office, or any other application running on there.

Server schedules. What/When/Where is the server doing. For example, backups. What time does the server backup, when does it backup, where is it saving said backups.
 
I might just use this, if you don't mind. My biggest client is looking for a new location and with about 70 computer and a server (which might soon turn into 2) this would be very handy.
 
I might just use this, if you don't mind. My biggest client is looking for a new location and with about 70 computer and a server (which might soon turn into 2) this would be very handy.

No problem at all. PM me and I will gladly give you my spreadsheet.
 
Back
Top