Escolar Documentos
Profissional Documentos
Cultura Documentos
Contents
[hide]
1 Deployment
Environment
2 Deployment Checklist
3 Deployment
o 3.1 Active
Directory
o 3.2 Windows
Servers
o 3.3 SCCM
Deployment Environment
SFAC would like to deploy SCCM2K7 primarily for the Operating System Deployment
functionality. A secondary interest is in Software and Update publishing. Currently
UoA ITS host a SMS2003 server which SFAC utilise for OSD. Due to time constraints
the decision was made to proceed with a standalone SCCM2K7 deployment in SFAC.
Ideally the SFAC site should be able to be integrated at a later date with an ITS
SCCM environment, so consideration of naming conventions and also name
resolution (FQDN and DNS SRV Records) is important.
The SFAC geographic profile, organisational structure and network topology can be
considered fairly flat in terms of this deployment so a single site mixed mode (native
- umm may upgrade to native at a later date, possibly issues with ITS instance with
native mode) SP1 (R2 - when RTM) installation will be deployed. SFAC AD contains
roughly 2600 Computer objects and is configured as 1 site. Internet based clients
will not be supported. Core network infrastructure services are predominately Linux
based (i.e. DHCP, DNS, PXE, Firewalls, etc) so attention needs to be given to name
resolution and remote boot options.
The web, application and database tier's will be installed on Windows 2003 Servers,
with the exception of the System Health Validator service which requires a Windows
2008 Server.
(reuse/decomission sfac-sms-tmk)
Deployment Checklist
Deployment
Active Directory
This procedure needs to be done by someone with schema modification rights (i.e
Schema Admins). You can extend the schema by opening a command prompt,
browsing the contents of your SCCM files (assuming you have extracted the exe) in
the SMSSETUP\BIN\I386 directory locate the extadsch.exe file, and drag it into the
command prompt window and execute it. After it completed, which should take less
than a minute, browse to the root of your boot drive and open the log ExtADSch.log,
open that file and look for the line
If you see this then it worked. Once you have extended the schema and the SMS
Admin account has been created you will want to log off as the Administrator and
logon as the SMS admin before you run setup.
5. In the System Management Properties dialog box, click the Security tab
6. Click Add to add the site server computer account and grant the account Full
Control permissions
7. Click Advanced, select the site server’s computer account, and click Edit
8. In the Apply onto list, select This object and all child objects, click OK
On the Advanced tab of site properties, select the Publish this site in Active
Windows Servers
Deploy Win2K3 Servers from template with latest service pack / hotfixes
Install SQL
Install MS SQL 2005 STD (SQL Data D:\SQL) (Use Domain User account for
services)
Install SQL 2005 SP2
Add SCCM Server Computer Account to local Administrators group
Add "s-MSSQL Administrators" to local Administrators group
Register Service Principal Name (SPN) for Domain User Service account
FQDN
setspn -A MSSQLSvc/<FQDN>:<SQL_PORT> <SQL_Service_User_Account> NOTE: YOU MUST
SCCM
You will need to have the following updates installed for the SCCM prerequisite
checker to complete successfully :
NOTE:
If you get this eventID: 1020, you need to run aspnet_regiis.exe /i to register
ASP.NET in IIS.
Updates to the IIS metabase were aborted because IIS is either not installed or is
disabled on this machine. To configure ASP.NET to run in IIS, please install or enable
IIS and re-register ASP.NET using aspnet_regiis.exe /i.
In order to install SCCM on a Windows 2000 or Windows 2003 server to avoid having
any IIS based Installation Prerequisite Check(s) fail there are certain things that
need to be installed. For example you must have BITS installed and configured and
you must have WebDAV installed and configured. Other wise you will receive Errors
when the Installation Prerequisite Check is performed.
Install SCCM
- Custom setttings
- Primary Site
- Install to D:\SCCM
During the installation the installer will prompt you to check for updates or supply a
path to the update files if you have already downloaded them. Once the install
routine has completed you should see "Setup completed all operations successfully".
NOTE: Configuration Manager 2007 will not install component files on a drive that
contains an empty file named "no_sms_on_drive.sms". Instead, site role
components will be installed on a different NTFS formatted disk drive that does not
contain the no_sms_on_drive.sms file. This is useful to prevent files being installed
on the system partition.