Hi everyone, i have a question that i am hoping some of you can help with!
We have never used prefered servers, in fact, up until about a year ago we were only using LANDesk for remote support (not inventory/software deployment/OSD/Provisioning). We have recieved training, but often the training showed us what we wanted the suite to do, not what could be done, so long story short we dont know anything about prefered servers!
We are about to open a new building in the town centre, this will be a flagship building and will house alot of new technology (including some 400 machines). We would like the abillity to provision machines on site and have heard that a prefered server is the way forward - my question is "how the hell do we go about setting it up". The guides on here are good and informative - but there does not seem to be any kind of step by step guide to follow :-(
Any help would be greatly appreciated. :-)
Preferred Servers in provisioning does not work as it does with Software Distribution and Patch/Compliance. There is a third party application developed, I believe, by a LANDesk employee located << here. >> I am not clear on how it works so I do not use it in provisioning.
The following information assumes you already have your preferred servers setup and they contain the image and are maintained with either Content Replication or as we use Robocopy. This is what we do at my company to handle deployments on the East Coast, West Coast, and North East.
Each OS Image Template I create contains a template variable called SERVERSHARE. SERVERSHARE=UNC of Preferred Server and Image Location:
So for every map drive action instead of inserting the UNC of the share I now just use the SERVERSHARE template variable. Once I have a master template I can copy it, rename it, and change the Replacement Value for the SERVERSHARE variable to whatever preferred server I choose. Most software installed is an execute file action, as when we set this up the distribute software action was unreliable.
There have been some software titles that I could only get to work with a distribute software action but have since found out that this action uses SDCLIENT.exe and will figure out what preferred server to go to. Personally I find execute file to be a lot more reliable, fast, and easy. Just map the drive with this new variable and let it rip. Everything runs from source rather then taking the time to download, unzip if necesssary, and install on the client.
In the screenshot below you will see the Map Drive action using the %SERVERSHARE% Template Variable. The variables used for credentials are Public Variables created by clicking the button on the OS Deployment Toolbar.
If you do not yet have preferred servers setup they are real easy to do. Just mirror your software library and patch library shares on each preferred server. The LDMS 9.0 User Guide can easily walk you through it found << here. >> Pages 147-149 to setup the file/web share. Page 70 contains the instructions on configuring preferred server credentials. Pages 156-158 shows you how to set them up in the console, a little outdated for SP2 but same basic concept, and also gets into a little more details of how they work. Hope this helps!
Ascott tat is a very good explanation - good stuff. I echo the use of exe over sdclient on software distribution, significantly faster - for now. Here are some other posts on preferred server.