As long as the rscd agent on windows machine is able to mount the source location, it should not be a problem.
Hope this helps.
I've had varying amounts of success with this. I attempted it in version 7.4.2 and was able to get it to work, until I decided that I wanted to go back to the file storage location to deploy files. Any patch that was added while using the Agent Mount had the network location locked into the patch and when that location went away, so did my ability to deploy that patch. I tried to edit each patch to go back to the file storage location but it never seemed to take. I think I ended up deleting the patches entirely and rebuilding the patch repository.
I haven't tried it under version 8.0 yet. I would hope they fixed the database locking the location issue but I'm not willing to chance it.
It’s pretty straightforward to change the payload url, though very tedious when you have hundreds of patches… the blcli can do this.
Is it possible to keep the "Network URL for payload deployment" variable ?
E.g. the targets have a definition for this as a property depending on the location.
Does it work ?
The next question:
if I use the 'Agent Mount' feature for patching have I to copy the patches manually to the the source location (network url for Payload deployment) or the patches will be copied automatically on demand ?
1 of 1 people found this helpful
when you create the catalog you can specify the payload url and type. the catalog update job or the download job will pull down the patches to the location specified in the catalog.
Yes, you should be able to keep it variable by using a property.
However, if it’s variable, I’m guessing you will have multiple locations of the payloads based on location of the target? in that case you will pull the patches down to one central place and you will need something to push those patches out to the remote file servers.
and if the payload url is variable ?
e.g. I use a special target property in the parameter "Network URL For Payload Deployment" to parameterize it depending on locations.
Bill, I have just seen, you have already answered my question. Many thanks !
The disadvantage of this solution is that I have to replicate the patches manually.
The greate advantage in this case is that I have only one patch catalog !
You can use a file deploy job to do the replication.
We have a problem via 'Agent Mount' that the remidiation job can't get patches from the share.
The Error Massages are:
Failure to add UNC credentials.
Asset could not setup local mount/map/UNC to payload source
The setting in the "Network URL For Payload Deployment" is like in help:
Some ideas ?
Thanks in advance.
Did you set the values of the MOUNT_PWD property correctly?
What do you mean, if you say "correctly" ? We have this values in a special property. What do I have to consider ?