At a guess, it can't load the template because something in IIS has died - provisioning works through a WebService.
Give your IIS a boot up the backside via an "iisreset" and see if it starts working then. If it does, you need to look at your IIS configuration.
Similarly, your IIS log file might be worth having a look at as well, to check for any 4xx or 5xx status codes.
LANDesk EMEA Technical Lead.
Just noticed that this is in Software Distribution.
For your info - I'll move this into Provisioning, since it's more appropriate there.
LANDesk EMEA Technical Lead
But I use LANDesk provisioning to distribute software, I think it belongs to here
The mechanisms through which Provisioning versus "traditional" Software Distribution work are quite different. And in this case it's not the Software Distribution that's causing problems, but the Provisioning - hence the move of the topic to the appropriate area.
If the Software Distribution side of things were broken, it'd belong to SoftDist, yes - but since it isn't, it does not.
LANDesk EMEA Technical Lead.
OK, I known it, thanks for your reminding
I found if I executed the ldProvision.exe in c:\ldprovisioning, the task complete successfully, but why it not executed automatically?
I've some questions...
Which version of LANDesk do you use? (8.8? SP?)
With which account do you start ldProvision.exe? Was it a domain account or a local account? Is your client member of a domain?
Do you use some of your Distribution Packages in your Provisioning Task?
Do you use a HTTP path or a (null-session) share path to your installation files for the Distribution Packages?
Do you've had the same error after restarting the IIS?
Hello ahe, thinks for your reply.My landesk is 8.7 sp5, and I can use provisioning to deploy OS with software successfully, but if I use provisioning to distribute software individually, the error occured. I used a domain account to manage all client, this account in loacal administritors group
I'm not restart IIS service, and the normal software distribution works well, I used the same software package
I executed the ldProvision.exe with local administrator, and the computer in domain.
Do you use a HTTP path for your Distribution Packages or a file share path to a package server?
If you use a file share path, you don't use HTTP in "normal" SW deployment... so it works without running IIS...
So it could be a good idea to restart your IIS...
Hello ahe, I use the unc to distribute software,I mean use file share, is the provisioning use IIS to perforn the task? I'll do this tomorrow. Thank you very much! BTW,the document regarding provisioning too rare to troubleshooting.
I restarted the IIS, the problem still not resolved, who can give me a process to call the provisioning to distribute software?
1 of 1 people found this helpful
I did it in this way:
- open "Operating system deployment" - "Provisioning templates" - "My templates"
- create a new group and than create a new template with a "Name" and a "Description", the parameters "Boot enrionment" and "Target OS" are set to "Not applicable"
- start "edit" of your template
- open "Action list" - "Sytem configuration"
- press the "Add..." button
- Add a name of your wished package and a short description
- Change the type to "Distribute Software" That's very IMPORTANT (otherwise you can start again with this package and delete it, a change later is not possible... -)
- Press the OK button
- mark your new added software package and select on the right site "Selected action properties" your package from the "Software distribution package" (if you didn't change the type before to "Distribute Software", than you can start again )
- press the "Apply" button and add the next software package (if you want) in the same way as before.
- if you added all, press OK and then you can schedule your template with a right click on your template
- The Scheduled Task properties will be opened and you must add/change the "Delivery Method" you want (I used policy supported push - without interaction)
- Save it and you can use it.
Our Delivery Method - Policy-supported push:
Mark "Require a non-RAS network connection" - "Allow any non-RAS network connection"
Feedback and timing
Hide all feedback from user
Run the package immediately
Type and frequency of policy
Required - once
Fail if operating system cannot handle...
Fail if agent cannot handle...
Discovery timeout: 500 MS
Timeout for broadcast: 2500 MS
mark Disable subnet broadcast and DNS/WINS lookup
Tested on 8.7 SP5
Message changed by ahe: add Delivery Method
My steps are same with you, but I am failed, I really not know why I failed,I find the log from core server provisioning folder, it indicate as below:
4/16/2009 5:34:50 PM : GetTaskXML has been called *****
4/16/2009 5:34:50 PM : GetTaskXML, SIDS:
4/16/2009 5:34:50 PM : MACAddress: 5449768E1F03
4/16/2009 5:34:50 PM : MACAddress: 001AA04FA69C
4/16/2009 5:34:51 PM : Unable to find template for computer IDN 280
4/16/2009 5:34:52 PM : GetValidTemplates for WindowsPE
4/16/2009 5:35:10 PM : ProvUserValidator.getInstance(), strAuth = Basic dHMtYXBcanN1bjohcWF6MndzeA==
4/16/2009 5:35:10 PM : ProvUserValidator.ProvUserValidator(), strAuth = Basic dHMtYXBcanN1bjohcWF6MndzeA==
One error that "Unable to find template for computer IDN 280", did you ever met this error?
Thank you very much