SMS Package Deployment

[RSR1]

I am trying to deploy packages to remote sites that do not have SMS servers and I do not want to use SMS distribution points for this as it will clog up the bandwidth. I have tried using batch files as packages and then advertising them to the these remote sites through the collection in the local SMS server, ie I have records of workstations of these remote sites in the local SMS. The batch files get advertised correctly, but the problem is that the commands cannot run using the builtin SMS accounts due to security.

Eg of batch file

net use x: \\servername\sharename
x:
update.exe

The SMS accounts used to connect to the share do not have rights to the server "servername" and I am not sure what account to use to provide these rights. Does anyone know of a way to do this?


Thanx

 

[tbrennans]

Depends on how you setup the package and what you have it setup to use (like run whether user is logged in or not then select run with administrator rights in the package -program-properties-environment tab) which is how you should run this...

Make sure the share you create has rights allowed to the client software installation account. then you should be good to go!

Tim B

 

[rsekar]

How do I assign rights for client installation account to the share that I create? To my knowledge this account is created by SMS, eg SMSCliSvcAcct&?

 

[tbrennans]

About the SMS Windows NT Client Software Installation Account
The SMS Windows NT Client Software Installation account provides a security context that might be needed by certain advertised programs when they run on client computers. When you configure the software distribution component, you can specify an account for programs to use on Windows NT clients when no user is logged on.

The SMS Windows NT Client Software Installation account must have the rights needed to access the necessary network resources. (the share in question here)

Note This account does not work for NetWare clients accessing NetWare distribution points.