I've been trying to figure out what is the best way of doing multi site deployment with dingle pdq server (so that we have one central pdq deploy server and local fileshares on all sites).
There are few other posts conserning this issue and they offer dfs or host file changes as a solution. I think both of these options are not good and can cause nightmare later on.
What I have figured is to create a fileshare on all sites to store local installation files. Then create a custom variable on pdq to point to that share. e.g. @(MYLOCALRepository) and use that in jobs instead of system default $(Repository) variable.
This seems to work but I was wondering is rhere a way (hack, script whatever) to run to folders in pdq depoy console to change all $(Repository) variables in all jobs in one folder to my @(MYLOCALRepository) so I could organize my pdq console to keep sites separated in their own folders and all jobs on that folder would automatically point to that folder's own repository?
Please sign in to leave a comment.