/build/static/layout/Breadcrumb_cap_w.png

Connet to network share from adv. client

So - after creating about twenty packages in SMS i recognize that all softw. deployment are running under local/system account in advanced client. But now i want to install soft. by batch file, with connection to some shared folder - another than distribution folder.
I have software installation accounts sets for legacy and advanced client to domain admin, but installation is allways run under local system account - without network permision.
So - when I try to map network drive by "net use ...." , the batch file stops.
Can anybody help me, or send me some clue to resolve this probelm ?
Thanks.

0 Comments   [ + ] Show comments

Answers (4)

Posted by: rebelpeon 19 years ago
Senior Yellow Belt
0
use UNC paths instead of mapped drives. ie "\\server1\share\blah.msi"
Posted by: kuji2000 19 years ago
Senior Yellow Belt
0
So - i was map network disks because i want do determine where is the problem, in first deployment of application a used the UNC path - it didnt work. I think that problem is in installation account - the bat file was run under local/system account and this account don't have any network permissions.... I want to run bat file under software installation account , but advanced client is against...
Posted by: Walter Schulz 19 years ago
Senior Yellow Belt
0
SYSTEM tries to use NullSessions to connect to network resources. Either run a batch to authentificate a given user

REM Batch for network connection
net use \\<servername>\ipc$ <password> /user:<dom>\<username>
\\<servername>\<sharename>\<dir>\<name of executable>
REM EOF

or open access to NullSessions for this share. Run REGEDT32 on the server and add the share name to HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters:NullSessionShares

Restart SERVER service.

Ciao, Walter
Posted by: kuji2000 19 years ago
Senior Yellow Belt
0
thx for help ...
The first one is easy, but i don't like the bat files with open typed passwords, but the second one is much more interesting - i tried to set permissions for workstations on server already - it didn't work. I'll try to set permissions for nullsession share - but it means that whichever workstation's system account will have permission to nullsession share? - (it is security problem) ... i'll try.
But , i don't understand why SMS advanced client doesn't use the software installation account for package deploying - WHY [:@] !!!
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ