Guide for Installing SCCM 2007

8/12/2019 Guide for Installing SCCM 2007

1/46

Hello sorry there Is no matter in this document I want to downlode so I uploadedthis empty file

SQL Server 2008 on Windows Server 2003 (!"#it$ I%! & ')* +ramewor,2'0 S-2

SQL Server ).press & ')* +ramewor, 2'0 S-2

%ll other editions of SQL Server 2008 & ')* +ramewor, 3'/ S-

+or a detailed #rea,down of Hardware 1 Software reuirments for relevant version on SQL 2008

(please clic, here$

Now we will start by installaing SQL 2008 step by step including screenshots to assist you all

the way in this process.

Before you start the installation, youll need to install the .Net .!." #ra$ewor%. &his co$espre'installed on (indows 2008 )2 Ser*er, but for earlier *ersions of (indows, youll need to

install it first. &his is a straightforward pre're+uisite and is usually included as part of theSQL Ser*er 2008 installation. ou can perfor$ a (indows update and install this if it is not

part of your -perating syste$.

It is suggested to install SCCM frst in an test environment then install in real

environment
http://msdn.microsoft.com/en-us/library/ms143506.aspxhttp://msdn.microsoft.com/en-us/library/ms143506.aspx


2/46

(hen installation of .N& #ra$ewor% .! S/" is co$plete, clic% close.

(indows nstaller 1.! is also re+uired, and $ight be installed by the nstallation (iard. f

you are pro$pted to restart your co$puter, restart it, and then restart SQL Ser*er 2008

setup.e3e.

)eboot your ser*er before starting your install of SQL 2008 S/".


environment


3/46

4reate a copy of you SQL $edia to your local partition of your ser*er, if your $edia is

da$aged and a file wont copy, you get to find out now, rather than halfway through theinstallation.

#ro$ the root folder, double'clic% setup.e3e. &o install fro$ a networ% share, locate the root

folder on the share, and then double'clic% setup.e3e. f the 5icrosoft SQL Ser*er 2008

Setup dialog bo3 appears, clic% -6 to install the prere+uisites, then clic% 4ancel to e3it SQLSer*er 2008 installation.


environment


4/46

4lic% on the 4onfiguration 4hec%er to ensure you $eet the re+uir$ents.

7ll $y tests ha*e passed as indicated abo*e so we will $o*e on further.


environment


5/46

4lic% on the nstallation hyperlin% on the left hand side of the screen

4lic% on the ew Server stand"alone installationlin% on the right side of the screen as

indicated abo*e.

(hen the prere+uisites are installed, the nstallation (iard will run the SQL Ser*ernstallation 4enter. &o create a new installation of SQL Ser*er 2008, clic% New nstallation or

7dd #eatures to an 3isting nstallation.


environment


6/46


7/46

not pre'populated. Basically this infor$ation is pic%ed auto$atically fro$ the ini file which islocated under the root of this installation $edia.

4lic% in the I accept the license termschec% bo3, then clic% on the e.tbutton again.


environment


8/46

4lic% on the e.tbutton again

#eature Selection

Select the co$ponents for your installation. 7 description for each co$ponent groupappears in the right pane after you select the feature na$e. ou can select any co$bination

of chec% bo3es.

ou can also specify a custo$ directory for shared co$ponents by using the field at thebotto$ of the #eature Selection page. &o change the installation path for shared

co$ponents, either update the path in the field at the botto$ of the dialog bo3, or clic%Browse to $o*e to an installation directory. &he default installation path is 4:>/rogra$

#iles>5icrosoft SQL Ser*er>"00>.


environment


9/46

4lic% on the e.tbutton


environment


10/46

nstance ? @ By default, the instance na$e is used as the nstance ?. &his is used to

identify installation directories and registry %eys for your instance of SQL Ser*er. &his is thecase for default instances and na$ed instances. #or a default instance, the instance na$e

and instance ? would be 5SSQLS);). &o use a nondefault instance ?, select thenstance ? chec% bo3 and pro*ide a *alue.

#or $ost installations, %eep the default settings.

4lic% on the e.tbutton


environment


11/46

&he ?is% Space )e+uire$ents page calculates the re+uired dis% space for the features thatyou specify. &hen it co$pares the re+uired space to the a*ailable dis% space.

&his screen Aust tells you if you ha*e sufficient dis% space on the dri*e youre installing to,

and whats going to be installed where.


environment


12/46

-n the Ser*er 4onfiguration @ Ser*ice 7ccounts page, specify login accounts for SQL Ser*er

ser*ices. &he actual ser*ices that are configured on this page depend on the features thatyou selected to install. ou can assign the sa$e login account to all SQL Ser*er ser*ices, or

you can configure each ser*ice account indi*idually. ou can also specify whether ser*icesstart auto$atically, are started $anually, or are disabled. 5icrosoft reco$$ends that you

configure ser*ice accounts indi*idually to pro*ide least pri*ileges for each ser*ice, whereSQL Ser*er ser*ices are granted the $ini$u$ per$issions they ha*e to ha*e to co$plete

their tas%s.


environment


13/46

ote6f this install is only being used for S445 on the S445 ser*er %indly change the7uthentication in the screenshot abo*e to only windows authenticationas S445 200

will co$plain at the ti$e of the installation pre re+ chec%s.


environment


14/46

Step #y step 7uide installin7 S9 200: -art ;

Step by step guide installing S445 200 /art C we will co*er installation of (SDS. &his can be done after

installing S445 200. &he 5icrosoft (indows Ser*er Dpdate Ser*ices E(SDS= .0 ad$inistrator console is

re+uired on the 4onfiguration 5anager 200 site ser*er to allow the site ser*er and re$ote 4onfiguration

5anager consoles to configure and synchronie software update points. &he (SDS .0 7d$inistration

console can be installed using the wiard or installed silently fro$ a co$$and line.

(e will need (SDS in future anyways in this lab so ha*e decided to not only install the console including

the full product .! S/2.

Before a software update point can successfully be installed and configured on a site syste$ ser*er in4onfiguration 5anager 200, (indows Ser*er Dpdate Ser*ices E(SDS= .0 $ust be installed on the ser*er.

ote6 ard'

&he (SDS .0 configuration wiard auto$atically starts after the Setup wiard co$pletes. Because

4onfiguration 5anager 200 $anages the (SDS settings, you should e3it the configuration wiard after it


environment


15/46

opens.

Note: while this wiard is co$pleting it ta%es a long period of ti$e to download the new *ersion fro$

5icrosoft so please be patient and watch out for the window below to open and start eh installation.

4lic% nstall


environment


16/46

4lic% e.t


environment


17/46

4lic% I accept the terms of the License a7reement, and then clic% e.t.

Select Store updates locally, specify the path, Epoint it to a partition of your choice which has enoughfree space to store the updates= and then clic% e.t


environment


18/46

4lic% e.t

ote: ?o not install (SDS integrated with SQL 2008 if you ha*e purchased a license which is the integrated

solution with S445 200 on a single ser*er i.e. S445 F SQL bundle.

&his is in breach of your license agree$ent as only S445 database can reside on the installation of SQL

2008.

t is one of those weird things which dont understand why it had to be such when (SDS can be integrated

within S445 a$ sure they should allow the (SDS database on SQL 2008 as well.

GGG 4ontact 5icrosoft Licensing for co$plete clarity GGG


environment


19/46


20/46

4lic% e.t


environment


21/46

4lic% #inish


environment


22/46

4lose


environment


23/46

ard'

&he (SDS .0 configuration wiard auto$atically starts after the Setup wiard co$pletes. Because

4onfiguration 5anager 200 $anages the (SDS settings, you should e3it the configuration wiard after it

opens.

Step #y step 7uide installin7 S9 200: -art 0

Step #y step 7uide installin7 S9 200: -art 0 will co*er how to prepare 7cti*e ?irectory 2008Sche$a in preparation for installaing Syste$ 4enter 4onfiguration 5anager 200.

3tending the 7cti*e ?irectory sche$a is a forest'wide action and $ust only be done once per forest.

3tending the sche$a is an irre*ersible action and $ust be done by a user who is a $e$ber of the Sche$a

7d$ins Hroup or by so$eone who has been delegated sufficient per$issions to $odify the sche$a. f you

choose to e3tend the 7cti*e ?irectory sche$a, it $ay be done before or after setup.


environment


24/46

(hile so$e 4onfiguration 5anager features are dependent on e3tending the sche$a, such as Networ%

7ccess /rotection in 4onfiguration 5anager and global roa$ing, there $ay be wor%arounds for not

e3tending the sche$a to enable other 4onfiguration 5anager features.

ote: Before you proceed any further please ensure:

". &he account you are using for this part has Sche$a 7d$in rights in 7cti*e ?irectory. i.e. Sche$a 7d$ins

Hroup.

2. &he ?o$ain controller has *erified bac%ups.

#our actions need to be ta%en in order to successfully enable 4onfiguration 5anager clients to +uery 7cti*e

?irectory ?o$ain Ser*ices to locate site resources:

Step : 3tend the 7cti*e ?irectory sche$a.

Step 2: 4reate the Syste$ 5anage$ent container.

Step 3: Set security per$issions on the Syste$ 5anage$ent container.

Step !: 7dd the Site Ser*er to the 7d$inistrators Security Hroup.

&he 7cti*e ?irectory sche$a can be e3tended for 4onfiguration 5anager 200 by running the 3t7?Sch.e3e

utility or by using the L?#? co$$and'line utility to i$port the contents of the 4onfig5grIadIsche$a.ldf

L?# file. Both the utility and the L?# file are located in the S5SS&D/>BN>i8J directory of the

4onfiguration 5anager 200 installation files.

Step 1: Extend the Active Directory schema.

ote: #or e3tending sche$a there is no 3J1 B& *ersion of e.tadsch'e.eyou need to use 38J *ersion

indicated below.

7s indicated below this is a du$p of the entire S445 200 $edia 4?.

)un e.tadsch'e.e, located at >S5SS&D/>BN>8J on the installation $edia, to add the new classes and


environment


25/46

attributes to the 7cti*e ?irectory sche$a.

&his screen will flash for a few seconds and close auto$atically. f you would li%e to loo% at the details please

read further.

;erify that the sche$a e3tension was successful by re*iewing the e.tadsch'lo7located in the root of the

syste$ dri*e.


environment


26/46

KKKKKK3t7?Sch.log log -utputKKKKKKK"2'2'200C ":2:00 5odifying 7cti*e ?irectory Sche$a ' with S5S e3tensions.

"2'2'200C ":2:0" ?S )oot:4NKSche$a,4NK4onfiguration,?4Kpilot,?4Klocal

"2'2'200C ":2:02 ?efined attribute cnK5S'S5S'Site'4ode.

"2'2'200C ":2:02 ?efined attribute cnK$S'S5S'7ssign$ent'Site'4ode.

"2'2'200C ":2:02 ?efined attribute cnK5S'S5S'Site'Boundaries.

"2'2'200C ":2:02 ?efined attribute cnK5S'S5S')oa$ing'Boundaries.

"2'2'200C ":2:02 ?efined attribute cnK5S'S5S'?efault'5/.

"2'2'200C ":2:02 ?efined attribute cnK$S'S5S'?e*ice'5anage$ent'/oint.

"2'2'200C ":2:02 ?efined attribute cnK5S'S5S'5/'Na$e.

"2'2'200C ":2:02 ?efined attribute cnK5S'S5S'5/'7ddress.

"2'2'200C ":2:02 ?efined attribute cnK$S'S5S'9ealth'State.

"2'2'200C ":2:02 ?efined attribute cnK$S'S5S'Source'#orest.

"2'2'200C ":2:02 ?efined attribute cnK5S'S5S')anged'/'Low.

"2'2'200C ":2:02 ?efined attribute cnK5S'S5S')anged'/'9igh."2'2'200C ":2:02 ?efined attribute cnK$S'S5S';ersion.

"2'2'200C ":2:02 ?efined attribute cnK$S'S5S'4apabilities.

"2'2'200C ":2:0 ?efined class cnK5S'S5S'5anage$ent'/oint.

"2'2'200C ":2:0 ?efined class cnK5S'S5S'Ser*er'Locator'/oint.

"2'2'200C ":2:0 ?efined class cnK5S'S5S'Site.

"2'2'200C ":2:0 ?efined class cnK5S'S5S')oa$ing'Boundary')ange.

"2'2'200C ":2:0 Successfully e3tended the 7cti*e ?irectory sche$a.

"2'2'200C ":2:0 /lease refer to the S5S docu$entation for instructions on the $anual

"2'2'200C ":2:0 configuration of access rights in acti*e directory which $ay still

"2'2'200C ":2:0 need to be perfor$ed. E7lthough the 7? sche$a has now be e3tended,

"2'2'200C ":2:0 7? $ust be configured to allow each S5S Site security rights to

"2'2'200C ":2:0 publish in each of their do$ains.=KKKKKK3t7?Sch.log log -utputKKKKKKK

Step 2: Create the System Management container.

4onfiguration 5anager does not auto$atically create the Syste$ 5anage$ent container in 7cti*e ?irectory

?o$ain Ser*ices when the sche$a is e3tended. &he container needs to be created once for each do$ain


environment


27/46

that includes a 4onfiguration 5anager site ser*er that will publish site infor$ation to 7cti*e ?irectory

?o$ain Ser*ices.

4*)6Because do$ains controllers do not replicate their Syste$ 5anage$ent container to other do$ains

in the forest, a Syste$ 5anage$ent container $ust be created for each do$ain that hosts a 4onfiguration

5anager Site

". Log on as an account that has the 4reate 7ll 4hild -bAects per$ission on the Systemcontainer in 7cti*e

?irectory ?o$ain Ser*ices.

2. -pen the 7?Sdit 554 console, and connect to the do$ain in which the site ser*er resides.

. n the console pane, e3pand


28/46

!. n the ;alue field, type System 9ana7ementand clic% e.t.


environment


29/46


environment


30/46


environment


31/46


environment


32/46


environment


33/46


environment


34/46


environment


35/46


environment


36/46


environment


37/46

In Site code, type HAPIn Site name, type Pilot Headquarters Site.


environment


38/46

Click Confguration Manager Mixed Mode.

I will cover Native mode at a upcoming article but or now we will stick to the miedmode.


environment


39/46


40/46


environment


41/46


environment


42/46


environment


43/46


44/46

Select the appropriate option or obtaining client prere!uisite component fles. "ilescan be downloaded as part o Setup, or they can be used rom an alternate location

to which the client prere!uisite component fles have already been downloaded.

Specify the path to store client prere+uisite co$ponent files downloaded during Setup or the path to the

alternate location to which client prere+uisite co$ponent files ha*e pre*iously been downloaded.

ote6ou can use the Setup co$$and'line option Setup Odownload pathItoIfiles to download client

prere+uisite co$ponent files without running the co$plete 4onfiguration 5anager Setup (iard.


environment


45/46


environment


46/46

Documents

Guide for Installing SCCM 2007