I have the same situation and this is what I have done. I create a master deployment template, that is nothing but a bunch of includes. One for the image, one for the agent installation done by the self contained executable, one for base image applications, and finally one to clean up that includes Encryption programs and Antivirus.
For each action where I map to my core server library for media/image/client, I create a map drive action first that references a global variable such as SERVERSHARE or WIN7IMAGE. This global variable is set to wherever the software or image share is located.
Now I clone this master template for each site. And within that cloned templates I set a template variable that replaces the global variable with \\Preferredservername\share. So instead of going to my core local server where I am at they point to the preferred servers for their images and software. So in essence you just have to clone and enter in a few template variables to point to whatever location your setting it up for.
1 of 1 people found this helpful
In addition to the good comments here, if you have DFS setup in your shop this could be used. Also, this functionality needs to be baked into OSD with true X64 Winpe support. You can vote on these ERs for this:
Also to my knowledge Jan no longer works for LANDesk so unless your are good with Autoit, weigh this in your decision to use these utilities._____________________________________________________________Please consider voting for these ERs:Provide Better Pre/Post LDMS Patch/Sp/.0 Information To The CommunityCumlative Patch List for LANDesk ProductsQuery Builder ImportProvide bulk client deletions without carpal tunnel syndrome.Core Synchronization Allow Mirror functionality from Master Core