System Center Configuration Manager 2007-Step by step guide installing SCCM 2007 Part 2

Step by step guide installing SCCM 2007 Part 2 In this part of the Article we will prepare the earlier install of Windows 2008 & configure Active Directory + DNS.

How to install Active Directory on Windows 2008

The reason for me walking you through these steps is to ensure they are done in a methodical approach & steps are not skipped out of sequence.

There was no point in me duplicating the screen shots in this Part 2 as this article had already been written and published earlier.

Read More

System Center Configuration Manager 2007-Step by step guide installing SCCM 2007 Part 6

used by System Center Configuration Manager 2007 & SQL 2008.

Open ADUC and create two accounts:

1. SQL 2008.
2. SCCM 2007.




Watch this space for Part 7

Read More

System Center Configuration Manager 2007-Step by step guide installing SCCM 2007 Part 5

Step by step guide installing SCCM 2007 Part 5 Step by step guide installing SCCM 2007 Part 5 we will configure Windows Update on both the servers i.e. PILOT-DC-01 & PILOT-SCCM-01



















Reboot your servers and ensure all updates have been installed successfully.

Watch this space for Part 6

Read More

System Center Configuration Manager 2007-Step by step guide installing SCCM 2007 Part 4

Step by step guide installing SCCM 2007 Part 4 series we will install & confiure Windows Deployment Service on PILOT-SCCM-01.

Note: I am assuming that you have now installed PILOT-SCCM-01 Operating System.

Windows 2008 R2 x64 BIT

How to Install Windows Server 2008 R2 Step by Step

The Windows Deployment Services is the updated and redesigned version of Remote Installation Services (RIS).

In this lab because we want to use the rich features of System Center Configuration Manager 2007 & not WDS; is capable of deploying images by itself with limited functionality.We will use WDS to assist us in this process.

WDS is the PXE server for System Center Configuration Manager 2007. System Center Configuration Manager 2007 hands off the request to WDS after checking it's own database to make sure it knows about the computer.

Note: System Center Configuration Manager 2007 R2 also introduces the ( Unknown computers support ) once again.
Known issues with configuring Windows Deployment Services
If you are running Windows Deployment Services and a non-Microsoft DHCP server on the same computer, in addition to configuring the server to not listen on port 67, you will need to use your DHCP tools to add Option 60 to their DHCP scopes.
If DHCP is installed on a server that is located in a different subnet, then you will need to do one of the following:
(recommended) Configure your IP Helper tables. All DHCP broadcasts on UDP port 67 by client computers should be forwarded directly to both the DHCP server and the Windows Deployment Services PXE server. Also, all traffic to UDP port 4011 from the client computers to the Windows Deployment Services PXE server should be routed appropriately (these requests direct traffic to the server, not broadcasts).
Add DHCP options 66 and 67. Option 66 should be set to the Windows Deployment Services server, and option 67 should be set to REMINST/SMSBoot/x64/pxeboot.com.

NOTE: In this lab WDS is also our SCCM server & DHCP is running on our Domain Controller !!!


Prerequisites for installing Windows Deployment Services:

Active Directory.  PILOT-DC-01
DHCP. You must have a working Dynamic Host Configuration Protocol (DHCP) server with an active scope on the network because Windows Deployment Services uses PXE, which relies on DHCP for IP addressing.
DNS. PILOT-DC-01
NTFS partition: The server running Windows Deployment Services requires an NTFS file system volume for the image store.

To install the role by using the command line, run one of the following two commands:

For Deployment Server, run ServerManagerCmd -install WDS.
For Transport Server, run ServerManagerCmd -install WDS-Transport.

To install the role by using Server Manager, click Add roles, which is located in the Roles Summary pane. Click Next and then select Windows Deployment Services.












Click Next >





Click Next >



Click Next >



Click Finish
Note: In some documents you will come across where you will be instructed NOT to configure WDS & some will recommend configuring WDS initial wizard & not importing any images.
From my testing you can do either and it works fine results are indentical.
I personally ensure that the PXE request delay (explained further in the article) in WDS is set to longer than the PXE service point in SCCM.









Right click > Configure Server














Untick the " Add images "

Click Finish.





We need to allow WDS to respond to all ( Known & Unknown ) Computers.

Also set the PXE response delay to 1

Note: This will ensure that SCCM PXE service point will respond before WDS responds.



We need to ensure that the WDS service is also set to " Automatic Delayed Start " this simply ensures that WDS service does not fail at auto start or else everytime you restart the server WDS services will need to be manually restarted.




When WDS service is set to "Automatic Delayed Start" this change is also reflected in the registry at the following location.


Watch this space for Part 5

Read More

System Center Configuration Manager 2007-Step by step guide installing SCCM 2007 Part 3

Step by step guide installing SCCM 2007 Part 3 series we will install & configure DHCP server & DHCP Scopes.

How to Install and Configure Windows Server 2008 DHCP Server


There was no point in me duplicating the screen shots in this Part 3 as this article had already been written and published earlier.


Watch this space for Part 4

Read More

System Center Configuration Manager 2007-Step by step guide installing SCCM 2007 Part 1

System Center Configuration Manager 2007 is the solution to comprehensively assess, deploy, and update your servers, clients, and devices—across physical, virtual, distributed, and mobile environments. Optimized for Windows and extensible beyond, it is the best choice for gaining enhanced insight into, and control over, your IT systems.
In this article we will cover the ZTI - Zero Touch Installation.

This guide covers integeration of various technologies which are mentioned below:

1. Windows 2008 R2 x64 BIT.
2. SQL 2008 SP1.
3. Windows Deployment Services.
4. Microsoft Deployment Toolkit - MDT
5. Internet Information Services 7.5.
6. System Center Configuration Manager 2007 - SCCM.

Prerequisites for Installing Configuration Manager

This Guide will be split in various parts & currently I am not even sure how many parts will there be in the end but I will update this as I go along.

If you want a 70000 feet veiw of the key points involved before reading all the various steps involved in this article series the summary is as follows:

Planning & Installation SCCM 2007

1. Install Windows 2008 ( PILOT-DC-01 + PILOT-SCCM-01 )
2. Configure Domain controller & Configure DNS
3. Configure DHCP
4. Install & configure Windows Deployment Server ( WDS )
5. Perform Windows Update.
6. Create Users for SCCM
7. Install & configure IIS 7.5 ( Internet Information Services )
 a. Install relevant IIS features.
 b. Install & configure Webdav.
 c. Install Desktop Experience
 d. Configure Authentication + Authorization + Install Remote Differential Compression + BITS
 e. Configure Application Config file & than test WebDav
8. Install SQL 2008 ( including sp1 )
9. Install WSUS.
10. Extend Active Directory Schema.
     Step 1: Extend the Active Directory schema.
     Step 2: Create the System Management container.
     Step 3: Set security permissions on the System Management container.
     Step 4: Add the Site Server to the Administrators Security Group.
11. Add DHCP Scope options for PXE.
12. Install System Center Configuration Manager 2007 - SCCM
13. Install System Center Configuration Manager 2007 - ( SP2 )
     a. Uninstall AIK & Install AIK version compatible with Windows 7.

Configuring SCCM 2007

14. Configure the Network Access Account.

Depending on the media you are using the SCCM build versions may vary accordingly.

RTM	4.00.5931.0000
SP1	4.00.6221.1000
SP2 BETA	4.00.6425.2000
SP2 Release Candidate	4.00.6468.2001
SP2 Final	4.00.6487.2000
SP2 + R2	No Build changes ( Only features are added )

Before we go ahead let me quickly cover the setup we are working with.

Fully qualified domain name (FQDN): PILOT.LOCAL
PILOT-DC-01: Domain Controller

Property	Value	Property	Value
IP address	192.168.1.200	Subnet mask	255.255.255.0
Default gateway	192.168.1.254	DNS	192.168.1.200

PILOT-SCCM-01:  System Center Configuration Manager 2007 - SCCM

Property	Value	Property	Value
IP address	192.168.1.201	Subnet mask	255.255.255.0
Default gateway	192.168.1.254	DNS	192.168.1.200

So to compelte Part 1
Task 1:  Install Windows 2008

Read More

Typical Installation Using Exchange Server 2007 Setup

Typical Installation Using Exchange Server 2007 Setup

Microsoft has taken Messaging to the next level & it is truly worthy of praise. In this article I will only cover a "Typical" install of Exchange 2007 32 BIT on a single server. How easy it is to simply deploy an Exchange 2007 server and the out of box experience. Your messaging solutions will be up and running especially if it is a brand new domain in no time. You will surely impress your boss and get a pay rise. :)

Lets see how this can be achieved.

Lab environment:

Hostname = DC1 (AD + DNS + DHCP) ( Windows 2003 R2 SP2 )
Hostname = CS1 (Exchange server) ( Windows 2003 R2 SP2 )

Note: Once both the servers are setup ensure DNS is setup and working correctly and the Exchange server is a member of the domain and can resolve all forward & reverse lookup queries.

For getting started with a new (Domain Controller) domain click here.

For this Demo I will be using Exchange 2007 "32 BIT version" the key reasons is none of my server's at home are x64 BIT.
Note: If you are deploying this in a production environment you will have to use x64 BIT.

Compare 32 BIT & x64 BIT click here.
To download the 32 BIT version of Exchange 2007 Click here.
For Exchange 2007 System Requirements click here:

Key pre install checks in a new Windows 2003 Domain:
1: The domain functional level to be at Windows 2000 native mode or higher.

Key pre install checks for the Exchange server:
1: Install .NET 2.0 (This is part of the Windows OS Win2k3 R2 under additional components so no need to download.)
2: You must also install the following hot fix:
    .NET 2.0 Framework + 32 BIT hot fix
    .NET 2.0 Framework + 64 BIT hot fix
3. MMC 3.0 (This is already part of my Windows 2003 R2 SP2 OS)
4: IIS (default install)
5: Windows PowerShell 1.0 (I will use the 32 Bit version due to my hardware)

Additional Windows 2003 components:
Mailbox Server: Network COM+, IIS, World Wide Web.
Client Access Server: World Wide Web, RPC over HTTP Proxy.
Hub Transport: None

Note: Do NOT install (SMTP & NNTP) like you did back in Exchange 2000 / 2003.

Step 1: Browse to the installation source files click setup.exe.



Step 2: The Windows simply indicates that the initial requirements have been installed already or else the links would be activated and you will need to complete the pre-requisites first.



Step 3: Click "Install Microsoft Exchange" and you will see the setup screen indicated below.



Step 4: You can read the "Intro" :) or if you are too excited Click next.



Step 5:  "Accept the License Agreement" once you have read it of course. Select "I accept" and click next. :)



Step 6: This is an option for you to either (enable or disable) this would not affect the product features in anyways BUT I would highly recommend to enable this as it will help Microsoft to help us to enhance the product and eliminate any errors in the product. Select the option of your choice and click next.



Step 7: In this demo we will only select "Typical Installation" but if you notice in the same dialogue box below it gives you options for a few more roles which are not pat of the "Typical Exchnage 2007 Installation". Some of which can be installed on the same server and some you cannot i.e. "Edge Transport Role".  For now select "Typical Installation" and click next.

In a production environment it will depend on many key factors where each role should be placed. i.e. Consolidated on one single server like this demo OR Distributed i.e. "Client Access Server" also known as CAS, Hub Transport server also known as HT, Mailbox Server also known as (MB). Each role can be deployed individually on a separate server.

There are some exceptions to the rule when it comes down to deploying Clusters. I will cover this in the upcoming articles.



Step 8: Plan your names right from the beginning not on the fly at the time of the installation.
Note: The organization name cannot be changed once the server is installed.



Step 9: Type you org name > click next.



Step 10:  I will select yes and click next simply for my testing purpose. This can be enabled once the server is installed as well. This will enable "Public Folders" and ensure Outlook 2003 clients can connect successfully for OAB.

Note: I have come across some engineers saying that "Public Folders" feature has been completely removed from Exchange 2007 which is NOT true. Microsoft simply says some features are "De-Emphasized".

Some features were not part of the initial release which will be part of Exchange 2007 SP1. Some of which also includes "Public Folder MGMT". :)



Step 11: The wizard starts doing all its required checks.




Step 12: Don't be surprised after looking at the next screen shot!!!

I left this on purpose to demo how errors are displayed while the installation is carried out. The link I referred to earlier in this article "How to install Active Directory on Windows 2003" does not cover how to upgrade the "Domain functionality".

So i decided to leave the defaults and show you how this screen appears when setup detects some of the problems. I am sure you did notice at the start of this article I did mention the "Domain requirements".



Step 13: How to raise domain and forest functional levels in Windows Server 2003


Step 14:  Ensure once this change has been carried out wait for replication to complete go back and verify this change has been applied and than restart your Exchange 2007 Setup.



Step 15: It has passed all the "Readiness Checks" but it is clearly alerting "Exchange 2007 32 BIT" is not supported in a production environment.



Step 16: Exchange 2007 Installation has completed successfully click finish.



Step 17:  This is the most annoying bit with this version and I guess you will have to learn to live with it. :)

You cannot get all the goodies with it being a freebie. :)



Step 18: Now it will mail enable the Administrator account by default and I have just verified that by clicking > recipient configuration > Mailbox.



Step 19: If you click on "Organisation Configuration" > Hub Transport > Accepted Domains. The default Active Directory domain is already listed as "Authoritative".



Step 20: So all I do now is to check if mail is flowing "internally" logon to Exchange using OWA.

Now this has changed a little but I will cover this later for now I will open my browser and open https://CS1/OWA. Logon with my Admin credentials and be prepared to get impressed with the new OWA. I cannot say enough about it, absolutely fantastic.

Keeping in mind I have not made any changes to OWA yet, even the SSL certificate option is a self generated certificate by the installer. This is the out of the box secure messaging environment approach from Microsoft..

I have sent an email to myself & received the email successfully with a confirmation as I requested it!!!

You can go ahead and create a new mailbox using Exchange 2007 MMC and send emails between different users.



Now there are few other things you will need to do but what I have covered uptil now will get you excited enough to start playing with the features.

In the upcoming articles I will cover how to configure the server further in various different ways so if you are patient enough you can wait for the other articles or else do some research by yourself and get the ball rolling.

I will also cover how to verify a successful Exchange 2007 Install very soon.

Hope this was informative enough!!! :)

Read More

Compare Exchange 2007 32 BIT & Exchange 2007 64 BIT versions

Microsoft has released two different versions of Exchange 2007.

Exchange 2007 32 BIT
Exchange 2007 64 BIT

The Exchange 2007 64 BIT does have a subset i.e.

Standard Edition
Enterprise Edition

For this article I will only cover differences between 32 BIT & 64 BIT.

Some of you might be wondering this is absolute rubbish & I am not too surprised either. Simple reason being I have recently come across a few engineers who were so sure and simply would not agree a 32 BIT version exists.

So lets look at some differences.

Before we go any further click here to download the 32 / 64 BIT version from Microsoft website.

Note:The first and most important thing to keep in mind is Excahnge 2007 32 BIT version is NOT supported by Microsoft in a production enviroment.

Exchange 2007 32 bit	Exchange 2007 64 bit
Not Supported in a production environment.	This is the only version which is supported by Microsoft.
32 BIT Management tools can be deployed to manage  a production environment running on 64 BIT versions.	Fully supported in a production environment.
The schema can be upgraded using the 32 BIT version.	Fully supported in a production environment.
SCC + CCR can be used for testing purpose only in a non production (LAB) environment. These are enterprise edition features but do work in this version.	Fully supported in a production environment.
Unified Messaging can be tested in a non production environment.	Fully supported in a production environment.
This version can NOT be purchased from Microsoft OR Microsoft partners.	This can be purchased through the normal Microsoft channels.
No Trial License keys are required	License keys will be provided when the product is purchased.
Automatic spam updates don’t work in this version.	Can be updated using Microsoft Windows Updates.
Available editions: Exchange 2007 32 BIT Standard edition.	Available editions: Exchange 2007 64 BIT Standard edition. Exchange 2007 64 BIT Enterprise edition.
Storage groups and databases: You can have a maximum of 5 databases per server in as many as 5 storage groups on the 32-bit version. Note:This limit is also applicable on X64 BIT Standard Editions)	Storage groups and databases:  You can create a maximum of 50 storage groups on each Exchange 2007 server, with up to a maximum of 50 databases.
This SHOULD NOT be used as a edge Transport server either as it is considered as a production environment	Fully supported in a production environment.

I personally think this is an absolute excellent option for customers to test this product and get a feel of it before going ahead in a production environment.
To give it a thought you can always use an old server which is not currently utilized to have a play with the 32 BIT version which will bring you up to speed & without impacting your production environment.
You can also test power shell scripts & gear yourself before hand for your move over to Exchange 2007. The same scripts can be edited as necessary and re utilized if your LAB domain does not reflect the production environment. For example:
LAB Domain: Lab.local
Production domain: abc.com

Read More

How to Import - Export Mailboxes Exchange 2010

Many procedures have changed since Exchange 2003 days where we would use a tool called Exmerge. Nowadays we only use the power of Power Shell. Let’s take a look at the process involved to achieve this task.

If migrating mailboxes from Exchange 2003 from one organisation to a new Exchange 2010 organisation you need to first perform a export on exchange 2003 using Exmerge.

1. Export PST from old system. Article ID: 292509
How to configure an account to use the ExMerge utility in Exchange 2000 Server and in Exchange Server 2003


2. Exchange 2010 install Outlook 2010 X64bit (ideally I would initiate an install from the x64bit folder itself)


3. Create RBAC Exchange 2010 Groups
==============================

Understanding Role Based Access Control http://technet.microsoft.com/en-us/library/dd298183.aspx


Get-ManagementRoleAssignment -role "Mailbox Import Export" | ft Identity

Get-ManagementRoleAssignment -role "Support Diagnostics" | ft Identity


New-RoleGroup -Name "Exchange Mailbox Import Export" -Roles "Mailbox Import Export" -DisplayName "Exchange Mailbox Import Export" -Description "This group will provide access to mailbox import and export cmdlets within entire Exchange Organization."


New-RoleGroup -Name "Exchange Support Diagnostics" -Roles "Support Diagnostics" -DisplayName "Exchange Support Diagnostics" -Description "This group will provide access to support diagnostics cmdlets within entire Exchange Organization."


Note: These groups will be created by default in "Microsoft Exchange Security Groups" OU assign relevant users to these groups for performing relevant task. Once the task has been performed and the user no longer requires relevant access remove the user from the group.

4. Manual Task using ADSIEDIT
=========================

Note: This is a known bug and will be either fixed in Update Roll Up 5 OR Exchange 2010 SP1
Open adsiedit

Add system account in adsiedit the correct permissions for the Mailbox Store.

Read
Administer information store
Allow Impersonation to Personal Exchange…
Create named properties in the information store
Open mail send queue
Receive as
Send as
View information store status

5. Import Single Mailbox
==================

Import-Mailbox –Identity “Huzaifah” –PSTFolderPath F:\PST\Huzaifah.PST

6. Bulk Import All Mailboxes
=====================

Get-Mailbox | Import-Mailbox –PSTFolderPath F:\PST

Get-MailboxStatictics -Database "Admin Database"

Read More

SQL Server 2008 installation

Step by Step guide to installing SQL Server 2008

 Step by Step guide to installing SQL Server 2008 in this article I plan to cover the installation of SQL 2008 std edition. The initial idea behind this article was to only integerate this article with the SCCM 2007 step by step guide but than I thought this can help others who dont need SCCM at all, hence a entirely independant article for anyone who needs any help with installing SQL 2008.
 

What's new in SQL 2008

Component	Requirement
Framework2	SQL Server Setup installs the following software components required by the product: ·.NET Framework 3.5 SP11 ·SQL Server Native Client ·SQL Server Setup support files
Software2	SQL Server Setup requires Microsoft Windows Installer 4.5 or a later version After installing required components, SQL Server Setup will verify that the computer where SQL Server 2008 will be installed also meets all the other requirements for a successful installation. For more information, see Check Parameters for the System Configuration Checker.
Network Software	Network software requirements for the 64-bit versions of SQL Server 2008 are the same as the requirements for the 32-bit versions. Supported operating systems have built-in network software. Stand-alone named and default instances support the following network protocols: ·Shared memory ·Named Pipes ·TCP/IP ·VIA Note   Shared memory and VIA are not supported on failover clusters.
Virtualization	SQL Server 2008 is supported in virtual machine environments running on the Hyper-V role in Windows Server 2008 R2 and Windows Server 2008 Standard, Enterprise and Datacenter editions. The virtual machine must run an operating system supported for the specific SQL Server 2008 edition listed later in this topic. In addition to resources required by the parent partition, each virtual machine (child partition) must be provided with sufficient processor resources, memory, and disk resources for its SQL Server 2008 instance. Requirements are listed later in this topic.3 Within the Hyper-V role on Windows Server 2008, a maximum of four virtual processors can be allocated to virtual machines running Windows Server 2008 32-bit or 64-bit editions. A maximum of 2 virtual processors can be allocated to virtual computers that are running Windows Server 2003 32-bit editions. For virtual computer that host other operating systems, a maximum of one virtual processor can be allocated to virtual computers. Notes: ·It is recommended that SQL Server 2008 be shut down before shutting down or the virtual machine. ·For more information about the Hyper-V role in Windows Server 2008, see the Windows Server 2008 Web site. ·Guest failover clustering is supported in SQL Server 2008. For more information about the supported versions of SQL Server and operating systems for guest failover clustering, and the support for virtualization, see Support policy for Microsoft SQL Server products running in a hardware virtual environment.
Internet Software	Microsoft Internet Explorer 6 SP1 or a later version is required for all installations of SQL Server 2008. Internet Explorer 6 SP1 or a later version is required for Microsoft Management Console (MMC), SQL Server Management Studio, Business Intelligence Development Studio, the Report Designer component of Reporting Services, and HTML Help.
Hard Disk	Disk space requirements will vary with the SQL Server 2008 components you install. For more information, see Hard disk space requirements later in this topic.
Drive	A CD or DVD drive, as appropriate, is required for installation from disc.
Display	SQL Server 2008 graphical tools require VGA or higher resolution: at least 1,024x768 pixel resolution.
Other Devices	Pointing device: A Microsoft mouse or compatible pointing device is required.

¹The following .NET Framework versions are required:

• SQL Server 2008 on Windows Server 2003 (64-bit) IA64 — .NET Framework 2.0 SP2
• SQL Server Express — .NET Framework 2.0 SP2
• All other editions of SQL Server 2008 — .NET Framework 3.5 SP1

For a detailed breakdown of Hardware & Software requirments for relevant version on SQL 2008 (please click 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, you’ll need to install the .Net 3.5.1 Framework. This comes pre-installed on Windows 2008 R2 Server, but for earlier versions of Windows, you’ll need to install it first. This is a straightforward pre-requisite and is usually included as part of the SQL Server 2008 installation. You can perform a Windows update and install this if it is not part of your Operating system.




When installation of .NET Framework 3.5 SP1 is complete, click close.

Windows Installer 4.5 is also required, and might be installed by the Installation Wizard. If you are prompted to restart your computer, restart it, and then restart SQL Server 2008 setup.exe.

Reboot your server before starting your install of SQL 2008 SP1.




Create a copy of you SQL media to your local partition of your server, if your media is damaged and a file won’t copy, you get to find out now, rather than halfway through the installation.

From the root folder, double-click setup.exe. To install from a network share, locate the root folder on the share, and then double-click setup.exe. If the Microsoft SQL Server 2008 Setup dialog box appears, click OK to install the prerequisites, then click Cancel to exit SQL Server 2008 installation.







Click on the Configuration Checker to ensure you meet the requirments.




All my tests have passed as indicated above so we will move on further.




Click on the Installation hyperlink on the left hand side of the screen >

Click on the "New Server stand-alone installation" link on the right side of the screen as indicated above.

When the prerequisites are installed, the Installation Wizard will run the SQL Server Installation Center. To create a new installation of SQL Server 2008, click New Installation or Add Features to an Existing Installation.




The System Configuration Checker will run a discovery operation on your computer. To continue, click OK. Setup log files are created for your installation. For more information, see How to: View and Read SQL Server Setup Log Files.
If any checks have failed, click on the Show details button or "View detailed report link" to find out the cause, correct it, then click on the Re-run button to perform the checks again.




Note that the product key box may already be populated, depending on which edition you have.

Note: I have removed the key from the above screenshot. :) Type your product key if it is not pre-populated. Basically this information is picked automatically from the ini file which is located under the root of this installation media.





Click in the "I accept the license terms" check box, then click on the Next button again.




Click on the Next button again

Feature Selection >

Select the components for your installation. A description for each component group appears in the right pane after you select the feature name. You can select any combination of check boxes.

You can also specify a custom directory for shared components by using the field at the bottom of the Feature Selection page. To change the installation path for shared components, either update the path in the field at the bottom of the dialog box, or click Browse to move to an installation directory. The default installation path is C:\Program Files\Microsoft SQL Server\100\.





Click on the Next button




Instance ID — By default, the instance name is used as the Instance ID. This is used to identify installation directories and registry keys for your instance of SQL Server. This is the case for default instances and named instances. For a default instance, the instance name and instance ID would be MSSQLSERVER. To use a nondefault instance ID, select the Instance ID check box and provide a value.


For most installations, keep the default settings.

Click on the Next button >





The Disk Space Requirements page calculates the required disk space for the features that you specify. Then it compares the required space to the available disk space.

This screen just tells you if you have sufficient disk space on the drive you’re installing to, and what’s going to be installed where.






On the Server Configuration — Service Accounts page, specify login accounts for SQL Server services. The actual services that are configured on this page depend on the features that you selected to install. You can assign the same login account to all SQL Server services, or you can configure each service account individually. You can also specify whether services start automatically, are started manually, or are disabled. Microsoft recommends that you configure service accounts individually to provide least privileges for each service, where SQL Server services are granted the minimum permissions they have to have to complete their tasks.

For more informationhttp://msdn.microsoft.com/en-us/library/cc281953.aspx
http://msdn.microsoft.com/en-us/library/ms143504.aspx






Note: If this install is only being used for SCCM on the SCCM server kindly change the Authentication in the screenshot above to only windows authentication as SCCM 2007 will complain at the time of the installation pre req checks.

Read More