Installing Systems Management Server Console:
**Note: This installation is for Systems Management Server 2003**
1) Locate the autorun.exe file by going to the Search for Files and Programs in your Start Menu and type in this specific location:
2) After double clicking autorun.exe, a window will appear asking if you are sure you wish to continue. Select "Run".
3) After selecting "RUN", Click Next that appears on the next window. The window that should appear is:
4) The next window that will appear is a Systems Configuration. Click "Next" in this window.
5) After the Systems Configuration window, the next window will be a Systems Management Server Setup. There will be a list of options. Select "Install the SMS Administrator console and related tools".
6) After selecting the option to install SMS Admin, select "I Agree" and click "Next".
7) After accepting Terms and Agreements, fill in the SMS site server name with CAMPUS-SMS-NTS then click "Next"
8) Click "Next" in the next window.
9) After the previous window, the Finish window will appear. Click "Finish".
10) After selecting Finish, the SMS console will begin to install. Please wait till the program finish installing.
11) After the program has installed, COPY the SMS-NTS-Support MMC to your desktop (Do not create a short cut, as it will always display a warning when launched from the network).
12) If using a Windows XP workstation with SP2 installed and Firewall enabled.
Windows Firewall has three settings: On, On with no exceptions, and Off. When you select the Don’t allow exceptions check box,, the SMS Administrator console cannot connect to any SMS site database from the Windows XP client. This is by design. If Windows Firewall is set to On (recommended), the SMS Administrator console cannot display all of the items in the console tree until you add the program unsecapp.exe (located in C:\windows\system32\wbem) and the port TCP 135 to the list of programs and services on the Exceptions tab of Windows Firewall.
In certain situations, adding these two exceptions is not sufficient. You might also require anonymous remote access rights in DCOM. You should only make this change if adding the program unsecapp.exe and the port TCP 135 to the exceptions list does not resolve the problem.
Remote Access in DCOM:
1) From the Start Menu, Click RUN and type DComcnfg.exe
2) In Component Services, Click Console Root, click Component Services, click Computers, and then click My Computer. On the Action menu, click Properties.
3) In the Properties dialog box, on the COM Security tab, in the Access Permissions section, Click Edit Limits
4) In the Access Permissions dialog box, grant Anonymous Logon allow Remote Access
5) Restart your computer.