Below are the Pre-Planing and Planing Worksheets for SCCM 2016 / SCCM 1511 Implementation
| | |
Organizational Data Preplanning Worksheet | ||
Organizational structure | Example data needed, where applicable, and by location | Collected Data |
| | |
High-level organization charts to help determine the divisional structure of your organization, the design of your Configuration Manager hierarchy, and your method of communicating Configuration Manager implementation updates to departments | ||
| ||
Organizational structure | ||
| ||
Reporting hierarchy | ||
| ||
Communications methods | ||
| ||
Service level agreements (SLAs) | ||
| ||
IT organization and administrative policies | You should consider the following factors: | |
| ||
The structure and technical level of local and remote IT divisions, their reporting hierarchies, and local and global IT administrative policies | ||
| ||
Organizational structure | ||
| ||
Reporting hierarchy | ||
| ||
Local administrative policies and SLAs | ||
| ||
Global IT administrative policies and SLAs | ||
| ||
Long-term business direction | Any major business changes planned for the future, such as mergers, acquisitions, major physical moves, or network migrations | |
| | |
Information Technology Organization Preplanning Worksheet | ||
IT organization | Example data needed, where applicable, and by location | Data collected |
IT Organization | Collect information about your IT organization. You should also create an organization chart that maps your IT organization to your geographic profile. | |
| IT reporting hierarchy. | |
| IT departmental divisions that produce an overlap in Configuration Manager tasks (for example, a department separate from the Configuration Manager team manages all database servers, including computers running Microsoft SQL Server) | |
| Points where management control or policy issues exist. | |
| Level of technical sophistication and security clearance of IT staff members who will be working with Configuration Manager before, during, or after deployment. | |
| Auditing policies. | |
| Service level agreements for departments, end users, and IT groups. | |
| Operating systems used to support the network and end users. | |
| Sensitivity to security risks. | |
| Change control policy. | |
| | |
Geographic Profile Preplanning | ||
Geographic information | Example data needed, where applicable, and by location | Collected Data |
Date and time zone information | List the time zone for each location, and list any date and time difference between the remote site and headquarters. | |
| | |
| Time zone. | |
| | |
| Date and time differences. | |
| | |
Operating systems and international operating system versions | List the operating systems in use and locations that use language versions that are different from those of your platform operating systems. | |
| | |
Active Directory Preplanning | ||
Active Directory preplanning | Example data needed, where applicable, and by location | Data collected |
Logical Structure | The logical structure of your organization is represented by the following Active Directory components: organizational units, domains, trees, and forests. | |
Physical Structure | The physical structure of your organization is represented by the following Active Directory components: Active Directory sites (physical subnets) and domain controllers. | |
| | |
Network Topology Preplanning | ||
Network topology | Example data needed, where applicable, and by location | Data Collected |
High-level WAN/LAN architecture | Links, gateways, firewalls, extranets, virtual private networks, and | |
perimeter networks | ||
Network size | Number of servers and clients at each location | |
Network bandwidth | Link speeds and available bandwidth, including any known bandwidth issues | |
Network usage and traffic patterns | Categorize as Light, moderate, or heavy, and note times of day when network usage is heaviest (peak times) and scheduled times for backup and maintenance (nonpeak times) | |
Network types | Windows NT, Windows 2000, or Novell NetWare and other third-party network operating systems | |
Network protocols | TCP/IP, IPv6, NetBEUI, IPX/SPX, AppleTalk, DLC, and so on, and name resolution methods such as DNS and WINS | |
IP subnet structure | The Internet Protocol (IP) subnets on your network by subnet ID | |
Active Directory site structure | Active Directory organizational units, site names, trees, and forest | |
| | |
Server Environment Preplanning | ||
Server | Example data needed, where applicable, and by location | Data collected |
Location and function | Document the location and function of the computers that run the core services of your network, such as global catalog servers, domain controllers, DNS and WINS servers, Internet Information Services (IIS) servers, computers running Microsoft SQL Server or Terminal Services, Microsoft Exchange servers, print servers, and file servers. | |
Naming conventions | Document current naming conventions for products you use with Configuration Manager , such as computers running Windows Server 2003 and SQL Server. This helps you establish and document naming conventions for Configuration Manager hierarchy elements. These elements include sites, site codes, servers, and the objects that are used by or created in the Configuration Manager console. Because the Configuration Manager site code is used to uniquely identify each Configuration Manager site, it is especially important that these codes be assigned and tracked by the Configuration Manager central site administrators. | |
Hardware, software, network | Document hardware, software, and network information for each server that might be assigned a site role in your Configuration Manager site hierarchy. | |
For example, you should document at least the following information from each server that will be part of your Configuration Manager hierarchy: | | |
| | |
Azure Machine Type | | |
Processor type and speed | | |
Amount of RAM installed | | |
| | |
Disk and array controller configuration and characteristics, including size, MB of cache, and the drive models and types (for example, ultra-wide SCSI, 18 GB, 7200 RPM) | | |
| | |
Platform operating system, version, and language | | |
| | |
Whether the Windows Cluster service or Windows Network Load Balancing Service is enabled | | |
| | |
Relevant software applications located on servers, including antivirus software | | |
| | |
| | |
Client Environment Preplanning | ||
Clients | Example data needed, where applicable, and by location | Data collected |
Number of clients | Total number of client computers in use on your network, and the physical and logical groupings of clients. | |
IP subnet size | Number and types (operating systems) of client computers on each IP subnet, including projected number of clients in the upcoming year. | |
Logon scripts | Whether or not users use logon scripts, and if those scripts are customized. Note file name and location of each script, and users and groups associated with each script. | |
Security rights | Desktop security rights granted to end users | |
Operating systems | Platform operating systems (including language version) in use on each IP subnet. | |
Client stability/mobility | Computers that are shared by multiple users, those that travel from one location to another, all home-based client computers having remote access to the network, and any other client computer environments. | |
Software | A database or spreadsheet of all major applications in use in the enterprise, categorized by organizational division or by IP subnet. | |
Special applications | Divisions or departments that use Windows Terminal Services to run applications, or use other special applications, such as internally manufactured or obsolete applications. | |
Connectivity | Types of connectivity different organizational groups are using, including remote client connection speeds (dependent on the remote access method in use, such as ADSL, wireless, dial-up, ISDN, or Site to Site VPN, Express Route or other). | |
| | |
Client Environment Preplanning | ||
Security | Example data needed, where applicable, and by location | Data collected |
Security policies | Collect information about your organization’s security policies, such as the following: | |
| ||
Account password policies | ||
| ||
Account cycling policies | ||
| ||
Account rights policies | ||
| ||
Client and server lockdown policies (restrictions on disks and registry, services that are stopped, whether services use Domain Administrator accounts, and hidden shared folders that are removed) | ||
| ||
Auditing policies | ||
| ||
| Separation of or delegation of duties between IT divisions within the enterprise. | |
| The degree to which users must retain control of clients, and any exceptions to such policies (such as servers, or computers used by programmers). | |
| You should collect information about how security-related issues will be handled and supported, such as the following information: | |
| ||
Sensitivity to security risks | ||
| ||
Importance of ease of administration | ||
| ||
Special needs you have for secure data access and transmission | ||
| ||
Service level agreements (SLAs) for applying security updates | ||
| ||
Mobile Devices Management | Is it required ? | |
