1 of 1 people found this helpful
We use Custom Software Packages for our Patrol Agent install process in BSA. One of the features of a Custom Software Package is the ability to select "Agent mounts source for direct use at deployment (no local copy)" when defining the "Installable source" part of the Custom Software package.
We then define the URL starting with smb: and pass the share username and password (using a BSA encoded Property to hold the password) and it works GREAT!
The installer payload is not dropped on the target, the install is run from the remote share!
Thanks Dan, I will try that out.
How do you parametrize the server name passed in the smb url?
I tried creating a server property called "Software_Source". I used it in the smb url as
I am getting the following error while applying the above.
How can I parametrize the servername in the SMB URL so that in the deploy job, I will provide servername as "asiaserver" or "americaserver" etc as per the location of the target servers.?
in case the Property "Software_Source" is set on the Server Property-Class, then in your Source-Location, you would need to use ??TARGET.Software_Source?? .
Best way to be on the safe side is to use the little button on the right, so you can go through the existing properties directly.
Thank you for the solution. That worked.
Here is what I did for this issue referring to your reply in other discussion "Using Repeaters for Windows & AIX Patching".
1.Created a server property Software_Source.
2.Created identical shares on 2 servers (1 in US & other in ASIA)
3.created custom software with "Agent mounts source for direct use at deployment (no local copy)" with source location as "smb://mydomain;prabhu:password123@??TARGET.Software_Source??/test-mount-smb/setup.exe"
4.Deployed on 2 set of servers, 1 set from US and other from ASIA
5.Though both deploy jobs show staging was done from fileserver location but they get actual installers from one of the above software_source.
So, Dan & Steffen Thank you for your suggestions & solution.
i think the Package Metadata is always coming from the FileServer, but that's just some XML's.