Академический Документы
Профессиональный Документы
Культура Документы
MSDN) and mount it via daemon tools or similar, and click onSQL Server 2000 Components
if you get a warning about the version of SQL you are using, make a note of what it says (we'll come back to that later)
Quote SQL Server 2000 Microsoft -------------------------------------------------------------------------------Issue Description: SQL Server 2000 sp2 and below is not supported by this version of Windows. Please apply sp3 after installation of SQL Server 2000.
stick with the defaults and go with 'create a new instance of SQL server'
accept the default of server and client tools and click next
next we get to choose the instance name of the SQL server, let's leave it as default and click next.
when prompted for setup type, leave it as typical and click next
enter the password for your administrator account as we are going to use the domain user account
now you enter your licensing options..... in this example i chose 1000, you can click on help to find out more about your options.
Install SP3
so now we have to install SP3 that it mentioned earlier.. so let's download it I chose sql2ksp3.exe from the list of 3 available options and once done, ran it, the file asked me where to install and i chose the default C:\sql2ksp3 once done, navigate to the folder and run setup.bat you should see the Service pack 3 wizard
accept the defaults and click next for the instance name which we setup earlier
accept the default security optionand when prompted for SA Password warning enter a password
choose your error reporting option and click ok to get things done.
and then its ready to begin copying files for the sp3 upgrade
you will eventually be informed that its time to backup your databases, but seeing as we didn't create any yet, there's no need.
that's it, you've now installed SQL server 2000 and the required Service pack 3
a reboot at this point would be a nice idea to see your SQL server running in the system tray ;-)
IIS installation and Configuration:----------Insert your Windows 2003 Server cd and click on Start/Control Panel/Add or Remove programs and then click on Add/Remove Windows components. Highlight Application Server by clicking on it, and then click on the Details button.
make sure the following items are selected: Application Server Console ASP.NET Enable network COM+ access Internet Information Services (IIS)
when done click on Internet Information Services (IIS) to highlight it and then click on the details button, in the window that appears make sure to select the Background Intelligent Transfer Service (BITS) Server Extensions
Then scroll down to World Wide Web Service and click on it to highlight it, then click on the details button
make sure to select the WebDAV Publishing option and click on ok.
click ok again, then ok, then next to start copying files from the cd.
at this point you can start the IIS Manager (All Programs/Administrative tools/Internet Information Services (IIS) Manager
as you can see here none of the SMS extensions are listed and also .NET v2 is also not installed. So let's download it and install it.
Click here to download the Microsoft .NET Framework Version 2.0 Redistributable and once done, install it.
once .NET 2 is installed you can verify this by refreshing the IIS manager
make sure your extensions are set to allow for the ones in the screenshot below:-
AD Schema:-----------
Download the Windows Server 2003 Support Tools to get the AdsiEdit utility. From a Windows 2003 Server DC logon as an account that is a member of the Schema Administrator group. From the Start - Run line type in Adsiedit.Msc then and click OK. Click the + sign next to your Domain (ServerName.DomainName.Com\Net) Click the + sign to expand the DC=DomainName,Dc= Com\Net Click the + sign to expand the CN=System container. Right mouse click the CN=System container and from the context menu select New and then select Object to begin the Create Object wizard. From the Create Object Select A Class dialog box select Container then select Next to continue. In the Value: line type in System Management and click Next to continue. Select Finish to complete the System Management container creation process. Verify that the CN= System Management object has been created successfully. From the Administrative Tools program group select Active Directory Users And Computers From the View menu select Advanced features to allow the System leaf to be displayed.
Click the + sign to expand the Systems leaf then select Right mouse click on the System Management container and from the context menu select Properties. From the System Management Properties dialog box select the Security leaf. Select Add then select Object Types and make sure that both the Users and Computers object types are checked then click OK to close the window. Select Advanced and the Users, Computers, or Groups dialog box will be displayed. Select Find Now and select your SMS Service account if you are running in Standard Security Mode or your SMS server name if you are running inAdvanced Security Mode then click OK to continue. Highlight the account that you are using (from the step above) and grant the account the following rights:
o o o o
Read Write Create All Child Objects Delete All Child Objects
Click OK to complete the task. Insert your SMS Installation CD-ROM media in the CD drive and from the Start Run line browse to the SmsSetup\Bin\I386 directory folder and select Extadsch.Exe and click OK Click OK once again and the command prompt window opens and the application begins. When the process has completed open the ExtADSch.Log file located in the root dive (C:\) of the server from which it was executed from and verify that the last line states: SMS Setup completed successfully!
***************************************
Make sure that Advanced Features is selected under the View option.
Once it is, in the left pane select System, and then scroll down to the System Management Container.
Right-click it and choose properties, then select the Security tab (should be the third TAB in Windows 2003 Server SP1, it may be different in SP2.) Verify your SMS server computer account is listed ini the Group or user names, scroll down to check, if it is not there then add it by clicking on Add. Click on Object types as in the screenshot below
Click on OK and then click on Advanced to expand the view, then Find now. When you see your computer listed, highlight it and click OK. click ok again to add it to the Security tab.
Now that we have added it, we need to edit it's security permissions to make sure that the permissions apply to both the Container and child objects. So let's click on Advanced.
At this point you should see your computername listed but with read permissions that apply only to This object only. We are going to change that to Full access to This object and all Child objects. to do so highlight our computername and click on Edit.
In the window that appears click the drop down menu called Apply onto: and select This object and all Child objects. Once done, click on Full Control for the Allow permissions plus select 'Apply these permissions to onjects and /or containers within this container only.' Click ok when done. In an enterprise, please verify the correct AD permissions for this container and set them accordingly, for advice on this please visit technet.
Double click on hardware Inventory client Agent on the right side and enable it.
Click on the inventory collection tab, and delete the default scan listed.
Click on the yellow start and add files of type *.exe then click on Set beside location, and enter %ProgramFiles%\ as the location so that it only scans that area for EXE files.
Next you can enable the Advertised programs client agent , and under the General tab, select Enable software distribution to clients and that the New Program notification icon opens Add or Remove Programs.
Next we have the Software Metering Client agent, enable it if you wish and set your schedule.
Step 3. Client Installation Methods In the left pane, select Client installation methods and double click on Client Push Installation Properties.
adjust your settings removing Servers and domain controllers from your choice of installing onto...
Set your accounts to install software, in this example i used the domain administrator, but you should really setup a separate account and give it the appropriate permissions for SMS in AD by creating a user in your domain called SMSInstall and adding it to the domain admins group, and then adding it to the accounts Tab in the screenshot below.
Next click on the Advanced client tab and set your Installation Properties string to something like this SMSSITECODE=WIN SMSCACHESIZE=8000 the above sets our SMS site code to WIN and the SMS cache size on the client to approx 8GB.
Step 4. Configure Discovery methods In the Discovery section, you'll see 8 possibilities, of which we only need to configure 5, the first 2 are NT related (not needed), we do however need the Heartbeat Discovery setup and enabled, the next option is also not needed (Network discovery). The final 4 options are all required (AD) so we'll set them accordingly. Set the discovery methods to the following values:* Heartbeat Discovery every 1 hour
* Active Directory System Discovery 1 hour * Active Directory User Discovery 1 hour * Active Directory Security Group Discovery 1 hour * Active Directory System Group Discovery 1 hour
Note: You may want to set these values to 1 minute in a lab environment. We also need to tell SMS where to look for these computers and that is done in each of the 4 AD options above, So bring up the Active Directory System Discovery properties and click on the Yellow star to add an Active Directory container
In the Browse for Active Directory window, make sure Local Domain is selected and click ok.
when the Select New Container window comes up, click ok.
now your container is selected click ok to exit and do the same actions for each of the 3 remaining AD discovery methods.