×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

No_SMS_on_drive.sms file not effective

No_SMS_on_drive.sms file not effective

No_SMS_on_drive.sms file not effective

(OP)
We have packages being delivered to a system's C-Drive when we want them to be delivered to the E-Drive.  In an earlier post I was directed to place the text file "no_sms_on_drive.sms" on the root of (in my case) the C-Drive.  I went to the SMS console and removed all DP from each package that resided on the C-Drive. I did see the SMSPKGC$ share go away as well as all packages.  BUT, when I went to repush these packages back, they all went back onto the C-Drive, even with this special file.

It appears that SMS is ignoring this file and installing on the drive with the most drive space (C-Drive in this case).

Does this no_sms_on_drive.sms file get overwritten by other SMS rules?  
Anything I missed?
Any help/direction would be greatly appreciated.

RE: No_SMS_on_drive.sms file not effective

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.

RE: No_SMS_on_drive.sms file not effective

(OP)
Thanks for getting back with me.
Well, we are running versoin 2003 SP2, that's the weird thing about this.
How can I verify that we are indeed running 2003 SP2?

RE: No_SMS_on_drive.sms file not effective

(OP)
Update - I went to the Admin console on my system, went to help/about SMS
It lists the version as: 2.50.3174.1000

Is this SMS 2003 SP2?

RE: No_SMS_on_drive.sms file not effective

nope, thats sp1

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close