By default, when you install a Microsoft Systems Management Server (SMS) 2003 remote Site System, the SMS Site Component Manager service installs the binaries (SMS folder) for the Site System on the NTFS-formatted volume that contains the most free space. You may prefer to use an NTFS volume other than the default volume for your remote Site Systems by preventing SMS from enumerating certain NTFS volumes.
To prevent SMS from enumerating an NTFS volume, on the remote server, you must create a text file that is named NO_SMS_ON_DRIVE.SMS and put the NO_SMS_ON_DRIVE.SMS file on the root folder of all NTFS volumes where you do not want to install the binaries (SMS folder) for the following SMS 2003 components:
- Client access point (CAP)
- Management point (MP)
- Server locator point (SLP)
- SQL_Monitor (SMS Provider)
When you install a Site System on a remote server, the SMS 2003 Site Component Manager service enumerates all NTFS volumes and installs the Site System related binary files in an SMS folder on the drive with the most available space. If Site Component Manager encounters the NO_SMS_ON_DRIVE.SMS file, the binaries (SMS folder) for the components listed earlier in this article are NOT installed on the NTFS volume where the NO_SMS_ON_DRIVE.SMS file resides.
Some SMS files are installed in folders outside the SMS folder. These default file locations cannot be changed. For example, files are installed in the following folders:
- The CAP_sitecode folder
Files are installed in this folder if the CAP site system role is defined as "system."
- The SMS_CCM folder
Files are installed in this folder if the management point site system role is turned on on the computer.
- The Inetpub\wwwroot\SMSComponent and Inetpub\wwwroot\SMSReporting_sitecode folders
Files are installed in these folders if the reporting point role is turned on on the computer.
- The %windir%\System32 folder
The default SMS CAP (CAP_sitecode
) share and the distribution point share are not affected by the
NO_SMS_ON_DRIVE.sms file. Alternatively, their location can be controlled by specifying a system type of share and using a custom share created by the SMS Administrator.
SMS 2003 SP2 enables CAPs and distribution points to recognize NO_SMS_ON_DRIVE.sms
In versions earlier than SMS 2003 SP2, the default SMS CAP (CAP_ sitecode) share and the distribution point share are not affected by the NO_SMS_ON_DRIVE.sms file. Alternatively, their location can be controlled by specifying a system type of share and by using a custom share that is created by the SMS Administrator. Installing SMS 2003 SP2 provides CAPs and Distribution Points with the ability to use an NTFS volume other than the default volume by preventing SMS from enumerating certain NTFS volumes.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
You cannot specify the location of the default Client Access Point when you install Systems Management Server