No edit summary |
No edit summary |
||
Line 27: | Line 27: | ||
### Check "Database Engine Services" | ### Check "Database Engine Services" | ||
### Change the "Instance root directory", "Shared feature directory", and "Shared feature directory (x86)" drive letter to your Program Files disk. In my case, this is drive D. Leave the rest of the path untouched. | ### Change the "Instance root directory", "Shared feature directory", and "Shared feature directory (x86)" drive letter to your Program Files disk. In my case, this is drive D. Leave the rest of the path untouched. | ||
### | ## On the Instance Configuration screen, the defaults are fine. Click Next. | ||
## Perform the following steps on the Server Configuration page: | |||
### Open Active Directory Users and Groups and create a service account for SQL to run under. I am using [[Users and Groups:svc_scsmsql]]. | |||
### Change the Account name for both services and input the password. Make sure this account is documented. SQL Server Browser cannot be modified. | |||
### Set the Startup Type to Automatic. | |||
### On the Collation Page, the default of SQL_Latin1_General_CP1_CL_AS is fine, just note you will not be able to change the language without reinstalling SQL. I only speak English. | |||
### Click Next. | |||
## |
Revision as of 22:35, 24 May 2024
History
System Center Service Manager:System Center Service Manager provides an integrated platform for automating and adapting your organization's IT service management best practices, such as those found in Microsoft Operations Framework (MOF) and Information Technology Infrastructure Library (ITIL). It provides built-in processes for incident and problem resolution, change control, and asset lifecycle management. Official documentation can be found here.
This service was setup to enable internal sysadminafterdark operations staff to receive tickets from devices and track internal change management requests. This enables us to have one central console for everything alert related so we can easily prioritize and track our time.
Deployment
It is recommended to snapshot often when deploying Microsoft System Center Products. To deploy Service Manager, follow these steps:
- Begin with a clean install of Windows Server 2022 Desktop Edition. You can find specific VM requirements for this server at Servers:SAD-SCSM01.
- A total of five virtual disks are needed for a proper installation:
- 128GB OS Disk - For Windows Server 2022.
- 256GB Program Data Disk - For Database: Microsoft SQL Server 2022 and System Center Service Manager:System Center Service Manager program files.
- 256GB Database Disk - To store database files.
- 256GB Logs Disk - To store SQL log files.
- 64GB TempDB Disk - To store SQL TempDB files.
- A total of five virtual disks are needed for a proper installation:
- Install Microsoft SQL Server 2022.
- Mount the Microsoft SQL 2022 ISO and run setup.exe.
- Click "Installation" on the sidebar then click "New SQL Server standalone installation or add features to an existing installation".
- On the Edition screen, enter your product license key.
- On the License Terms screen, Accept the license terms.
- No action needed for section Global Rules.
- Choose whether or not to use Windows Update on the Microsoft Update tab. I choose not to.
- Click Next on the Install Rules tab.
- Note: I received a warning about Windows Firewall, we will fix this later.
- Perform the following actions on the Feature Selection screen:
- Check "Database Engine Services"
- Change the "Instance root directory", "Shared feature directory", and "Shared feature directory (x86)" drive letter to your Program Files disk. In my case, this is drive D. Leave the rest of the path untouched.
- On the Instance Configuration screen, the defaults are fine. Click Next.
- Perform the following steps on the Server Configuration page:
- Open Active Directory Users and Groups and create a service account for SQL to run under. I am using Users and Groups:svc_scsmsql.
- Change the Account name for both services and input the password. Make sure this account is documented. SQL Server Browser cannot be modified.
- Set the Startup Type to Automatic.
- On the Collation Page, the default of SQL_Latin1_General_CP1_CL_AS is fine, just note you will not be able to change the language without reinstalling SQL. I only speak English.
- Click Next.