Q1: We have dedicated Windows based file servers in the company already (accessible through Windows AD shares such as \\domain.com\production\folder -- Is this an allowable "path" for the file server to store its data in?
Not exactly. Appserver communicates with the Fileserver just like with any target managed by it... You install BladeLogic RSCD Agent on the fileserver, and reference it by the NSH path, so your fileserver location should be:
Q2: If we have a lot of files to store on the file server is there a bulk load command for the Depot? Or is it all strictly through the console?
The question is rather general.
In Depot you do not technically store files, you store Objects of various types (Custom Software, AIX Patch, Solaris Cluster, BLPackage, MSI Package, etc....). Each object has its own procedure of how it should be added. For each object there is probably a blcli command available as well to add it to the Depot. Explore BLCLI space, find the command for your object, script it for your bulk operation. If you have a more specific request, you could ask in Scripting sub-forum under 'Server Automation'.
When you say Windows AD shares … are you talking about using the UNC path to the share?
Are the Windows File Servers set up as DFS?
If so, on which server is your file server agent installed? As Lazar stated, you have to use NSH path, not the UNC path to configure your FileServer path on the AppServer.
The ‘file server’ for bsa cannot be a unc path. however, if you already have a significant number of objects in a share, you can use the ‘network deploy’ type of package where you provide the creds and unc path to the payload and that is mounted by the target during deploy. however you still need a bsa file server that has an agent in front of it.
When you load payload into the depot, you are creating software objects – so they include install instructions, uninstall instructions, payload and some other information – this can be scripted, but you would not do like a ‘bulk load’ of just payloads.