Re: Distribution folder on wrong drive

The option you specify in the console is only were the compressed packages
are stored. You have no control over the DP itself using this option.

/Rune

"GillRilla" <leeg@xxxxxxxxxxxxxxxx> wrote in message
news:OD6vKFdfGHA.4080@xxxxxxxxxxxxxxxxxxxxxxx
Thanks guys,

Interesting...I wonder what the point is then of specifying a drive letter
if SMS is not going to use it. SMS itself installed in the drive I wanted,
its only the SMSPKG<driveletter>$ folder that got created on a different
drive than I had specified.


Gill



"Rune Norberg" <runeno@xxxxxxxxxxxxxxxxxxx!> wrote in message
news:upA%230vcfGHA.3572@xxxxxxxxxxxxxxxxxxxxxxx
With the NO_SMS_ON_DRIVE.SMS file and SMS 2003 SP2 this issue is somewhat
solved: http://support.microsoft.com/?kbid=871234, although it requires
you to actually specify the drive(-s) you don't want SMS to operate on.

I prefer the method Steve mention; using a server share gives you the
control you need in termes of placing packages on correct disk drive...

/Rune


"Steve Thompson" <stevethompson@xxxxxxxxxxxxx> wrote in message
news:eDr68dcfGHA.1456@xxxxxxxxxxxxxxxxxxxxxxx
"GillRilla" <leeg@xxxxxxxxxxxxxxxx> wrote in message
news:%231DteIbfGHA.3888@xxxxxxxxxxxxxxxxxxxxxxx
On a fairly new SMS 2003 SP1 implementation, during our first package
distribution, I noticed that the SMSPKG<drive letter>$ is not what is
configured. Two secondary sites are configured to use the E:\ drive
(under Component Configuration-->Software Distribution) however the
drive used is different. This has happened on 2 of 22 secondary sites.
All secondary sites were created via the wizard. Anyone have this
happen, or know what might have caused this?

From a previous newsgroup post:

The SMS 2003 Distribution Manager will allways select the drive with the
most free diskspace.


To Force a Distribution Point to use a specific drive, you can do the
following:


1. Create a directory on the drive.
2. share this directory
3. create a new server share as site system in SMS Administrator
console.
4. Give the unc path of the share created in step 2.
5. push the packages to this new site system.











.

Relevant Pages

  • Re: Automating Application Deployment
    ... osdswdexec app deploy queries the SMS database for packages, you specify the ...
    (microsoft.public.sms.tools)
  • Re: msi wrapper
    ... You are saying you can't deploy MSI's using SMS in your environment? ... machine here <specify> then execute the file with these command ... Have you tried to do these tasks with SMS Installer? ... > I want to do is launch my installer packages. ...
    (microsoft.public.sms.installer)
  • Re: Reboot after running batch file doesnt work
    ... You need to specify the time you think it will take to run this program in ... Since program is taking longer than specified by the admin, SMS considers ... ensure the program properties allow the user to ... > simple .wsf file that calls a batch file which calls a text file. ...
    (microsoft.public.sms.swdist)
  • Re: problem with programs
    ... aptitude: invalid option -- e ... install - Install/upgrade packages ... -O order Specify how search results should be sorted; ... Perform an install run on startup. ...
    (Ubuntu)
  • SV: [opensuse] Priorities in the build package?
    ... Specify path where to find the RPMs for the build system ... That will specify the paths to the RPMs, ... priorities for the packages, ...
    (SuSE)