Using Landesk 9.5 SP2.
Using a Provisioning template and HII I can deploy a image to a Lenovo X131e Notebook until it gets to CTOS. On rebooting during CTOS it blue screens with a message "can't find autochk".
I checked and all the partitions are there, the correct one is active and bootable. Any help would be appreciated.
One other note here is this is the first Lenovo I have dealt with all other computers are Dells.
According to this: http://help.landesk.com/Topic/Index/ENU/LDMS/9.5/Content/Windows/rba_c_edit-public.htm
A tool's Public group is visible to all users. Items in the public group are read-only, unless you have the "Edit public" right. Users that have "Edit public" rights on a feature can only edit public items for that feature. Other public items will be read-only. Read-only items are still useful, since users can copy those items to the "My ..." tree group and edit them there.
I have not found this to be the case for OS Provisioning. The goal is to have locked down public templates, but allow users to copy them to their private templates and edit/tweak them.
LANDesk 9.5 SP2.
When WinPe starts and kicks off startnet.cmd. It fails at the "Downloading Prerequisites" section of the batch file. I noticed the following errors in the provisioning log. Does anyone know what causes the try "TryallWebService" to fail?
014-08-26 23:02:42(1732-1652) ldProvision:Provision Mode = PROVISION_MODE_CORE_SID
2014-08-26 23:02:42(1732-1652) ldProvision:Start TryallWebService Attempt:0.
2014-08-26 23:12:42(1732-1652) ldProvision:End TryallWebService Attempt:0. ExitCode:259
2014-08-26 23:12:56(1732-1652) ldProvision:Start TryallWebService Attempt:1.
2014-08-26 23:22:56(1732-1652) ldProvision:End TryallWebService Attempt:1. ExitCode:259
2014-08-26 23:23:07(1732-1652) ldProvision:Start TryallWebService Attempt:2.
2014-08-26 23:33:07(1732-1652) ldProvision:End TryallWebService Attempt:2. ExitCode:259
2014-08-26 23:33:13(1732-1652) ldProvision:Failed to call web service. exitCode=259
2014-08-26 23:33:13(1732-1652) ldProvision:Caught exception in main: code=80001500H, file=.\ProvisioningWebSvc.cpp, line=933
2014-08-26 23:33:13(1732-1652) ldProvision:Call web service GetStatusString()
2014-08-26 23:33:13(1732-1652) ldProvision:Start TryallWebService Attempt:0.
2014-08-26 23:33:14(1732-1652) ldProvision:End TryallWebService Attempt:0. ExitCode:0
2014-08-26 23:33:14(1732-1652) ldProvision:StatusString = The call to the Web service failed.
2014-08-26 23:33:14(1732-1652) ldProvision:Call web service SetActionStatus()
2014-08-26 23:33:14(1732-1652) ldProvision:Start TryallWebService Attempt:0.
2014-08-26 23:33:15(1732-1652) ldProvision:End TryallWebService Attempt:0. ExitCode:0
Landesk 9.5 SP2
I have a brand new Dell Latitude 3340 that goes as far as hitting F8 then boot menu comes up, choosing WinPE Menu, then Boot Server IP comes up then MTFTP shows dots, then nothing.
All other model computers boot OK.
I have upgraded bios to the latest V2. The bios is set with Secure boot Off, UEFI is off and Legacy is selected.
This computer came with Windows 7 64bit installed.
Any suggestions?
Hi Guys,
Im using 9.5 SP1 and we have started receiving some tablets and because of our harddrive encyption software we need to build images in UEFI mode. I cant find any information or documentation on this. Does anyone have any useful information or better searching skills?
Thanks all!
Dear Support
Good day...
Kindly, in need install (landesk PXE server) i read on the web site must two service working :-
1- LANDesk PXE Service (pxesvc.exe).
2- LANDesk PXE MTFTP Service (pxemtftp.exe) .
but i don't have the program for PXE server and how to configure it ,can you help me for two qustion below :-
* if i deploy win 7 for 20 pc at the same time ,what is the best Requirement for LANDesk PXE representative (Computer or Virtual server) from (CPU & Ram & Hard ) ?
* can i install LANDesk PXE representative on virtual server or it must seperate computer ? , we installed landesk core server on virtual server
B.R
Haider Ahmed
Has anybody succeeded in using profile migration to migrate from WXP to W8? Tried to use UMA to migrate a profile from a WXP machine to a new W8 pc and it copies the SMA file to the W8 ws but does not restores the contents of the profile. The task completes without errors but nothing is restored. Same task sent to a WXP machine works perfectly. Is LDMS 9.5 SP2 profile migration feature compatible with W8?
Any ideas?
LANDESK Management Suite 9.5
LANDESK Management Suite 9.6
These features are not available at the moment for provisioning tasks, as they work only as a push and for all the machines attached to the scheduled task.
Items such as "Start now for computers that did not try the task" do not work, as well as selecting other delivery methods.
Basically a task run will act like "Start now" for any clients, and any additional runs prior to the current provisioning task will queue up the clients to run the provisioning task again.
In addition changing the delivery method will either fail, or will have no effect.
An enhancement request can be opened to request the feature to be implemented in a future release of the LANDESK Management Suite at the following address:
http://community.landesk.com/support/community/enhancementrequests/ldms
LANDesk 9.5 SP2
Under public distribution packages, I created a software package bundle called "Adobe Products". Inside this bundle, I toss Flash Player plugin, Flash Player active X, Adobe Reader, Adobe Shockwave Player, etc As part of my OS Provisioning Template, I have a software distribute action: Install Adobe Products which installs all the packages listed. I want to update OS Provisioning to install Adobe Reader 11.0.09 from 11.0.08
I rename the Adobe Reader 11.0.08 package to 11.0.09, add the 11.0.09 msp, edit the setup.ini to reference the 11.0.09 MSP and then reset the package hash.
Do I now need to recreate my OS Provisioning Template? Can I continue running a locked one? What's the best way to handle this?
Purpose:
How to query for machines that are PXE representatives.
Steps:
When trying to capture in LDMS 9.6 I receive the following error. First attempt after following the LD "how to" manual. Any assistance or direction would be great.
Here is a screenshot of the error from the scheduled task.
Hello,
I work for a school district and am fairly new to LanDesk. I have to distribute electronic textbooks to hundreds of Windows 8 devices. I know how to do this through a provisioning template, but I was told it is better to use the Distribute Task method because I can use multicast to keep bandwidth cost low. The books range from 1.5 to 3.5 GB and are broken into pdf files. Can someone point me in the right direction on how to set this up? It is something that I need to have ready in a limited amount of time. Thanks.
Patrick
The following flowchart illustrates the process flow for the PXE process used with LANDESK to PXE boot machines.
(Click image for expanded view or download the attached image file)
I am trying to copy a file using provisioning.
Since it is a mixed I wanted to use a DB value.
I called my public variable ALLUSERPRO
Type: Database Value
Replacement Value: "Computer"."Environment"."Variable"."ALLUSERSPROFILE"."Value"
Core Prov log:
XML Snippet to be used:
<variables /><Copy_file><source>\\vmlandeskcore\software\Packages\GDPicture\ScanViewLive.lnk</source><destination>%ALLUSERPRO%\desktop</destination><copySubItem>False</copySubItem></Copy_file>
The file would not copy. If I hard coded the destination path it worked flawlessly. This leads me to belive the variable is returning NULL
Before you reply I did remember I could just use %%ALLUSERSPROFILE%% and get the local variable from the client. I still want to use variables in the future
My questions are:
why was the variable null?
How can I test a public variable ?
General
HII (Hardware Independant Imaging)
PXE
General Troubleshooting
PXE Issues
Template Issues
Windows PE Issues
NOTE:This article is not a comprehensive list of documents and issues. You can continue to search the rest of the community or the portion specific to Provisioning if this page has not helped.
Problem:
Issues arise in the instal software section of the provisioning process if the scheduler tasks in the agent are permitted to run as designed. A full description of the cause and consequences of these issues can be found in the following document;
http://community.landesk.com/support/docs/DOC-9526
The resolution in the above document has you create a provisioning agent that resolves the issues referenced, but requires the installation of the "desired" agent at the end of the provisioning process to restore the scheduler tasks for normal agent behavior. This can add 15+ minutes to the template to get the "desired" agent installed.
Resolution:
Instead of installing a second agent at the end of the provisioning template, you can simply restore the local scheduler tasks with a script in the provisioning template. This adds seconds to the template process and accomplishes the same thing.
In order to accomplish this and have it work properly, the name of the agent has to start out having the name of the agent you want it to end with. We change the "desired" or "default" agent, create a self contained exe, then change the agent back to the "desired" state.
This is accomplished by the following steps;
1. Go to your "desired" or "default" agent. The one you want to end up on the client machines. Right click > Properties to edit it's settings. We are going to make 4 simple changes.
2. We want to change each one of the schedules in the agent to run at a future time;
a. first, the inventory scanner;
Uncheck the mini scan option,
Select the change settings button, then;
Change the start date to the year 3000.
b. Now the same with the policy scanner;
Select the change settings button, then;
Change the start date to the year 3000.
c. and the last to change is the patch and compliance scanner;
Select the change settings button, then;
Change the start date to the year 3000.
3. Save the agent. Do not change the name of the agent.
4. Right-click on the agent and select "Create self-contained client..."
5. Now that you have a "self-contained" of your "Desired" agent install in a "Provisioning Agent" form, you want to go back into the agent and resore the date of the schedules in back to the way you had them. Repeat steps 2a through 2c, only change the year back to the current year.
6. Use the self contained agent instal in your provisioning template at the place you would install the provisioning agent.
7. Download this bat file. It will add each of the schedules back.
8. You must edit the bat file to change the word "CoreName" with your core server's name. It may or may not require the Core's FQDN depending on your environment. You can modify the script to remove one or more line if you do not want all of the schedules active in your environment, or to change the schedules they are set to run. As it is set, it will resore;
a. the mini scan option (once every 10 minutes)
b. the Inventory scan (once a day with an auto delay of up to an hour)
c. the policysync scan (once every 8 hours no delay)
d. the vulnerability scan (once every 2 days with an auto delay of up to an hour)
9. If you have a drive mapped to the core, you can place the bat script there. (This example shows drive P: mapped)
10. At the end of the provisioning template, right before the reboot or shutdown, run the script to add back the local scheduler tasks to the agent.
a. Use an execute file action to kick off the bat script as shown below;
Q1- can I install PXE representative server in the same Landesk core server?
Q2– can I OSD deploy 20 PC’s at the same time from PXE representative?
Q3- my network three Vlans ,
Vlan 24 install core server, it’s working normally.
Vlan 22 install PXE representative server, successfully installation .
Vlan 167 will use for OSD deploy win 7 .
- I completed open ports in firewall between VLANS , as shown in web site https://community.landesk.com/support/docs/DOC-1591
know my question what configure need to can deploy PC from different VALN ?
hint: All VLANs use the same DHCP server but different subnet , i must use one PXE representative server .
Description
LANDESK provides the ability to put one PXE Rep on each subnet so that settings on the network never have to be configured.
While not having to change any the configuration on any network device is a good feature, it may be beneficial and easier in certain environments to make network changes. For example, an environment that has 5 sites with 20 subnets each, would require 100 PXE Reps to avoid network configuration. However, with network configuration, they would only have to manage 5 PXE Representatives. Such a design would likely be preferred and LANDESK supports this design.
A PXE Representative can be used for multiple subnets similar to how any DHCP/Bootp server can be used for multiple subnets. This requires that a DHCP Relay agent exist that can forward DHCP/Bootp requests.
The following diagram shows how subnets do not have a PXE Representative. Instead a DHCP Relay agent (often called an IP Helper with Cisco switches) exists on the network and must be configured to forward traffic to both the DHCP server and the PXE Representative, which can be on any other subnet.
Troubleshooting the PXE Representative is as simple as using Wireshark to verify that the PXE Rep received the DHCP/Bootp packets and responded.
Add the following filter to limit Wireshark traffic to bootp protocol on port 4011:
bootp || udp.port == 4011
Also, for TFPT, Wireshark can demonstrate the packet arriving and the response.
This article describes the new features and changes in the OS Provisioning tool in LANDESK Management Suite 9.6.
The focus on changes for OS Provisioning in LDMS 9.6 has been geared towards simplifying the process.
The older "OSD" product has been removed from the product and has been fully replaced by the Provisioning product.
LANDESK Provisioning takes the previous OSD concepts and extends them even further LANDESK Provisioning offers true end-to-end Provisioning of a device from a "Bare Metal" metal state (No Operating System installed) to completely imaged, software installed, domain joined, LANDESK Agent installed, etc.
There is no upgrade process for existing OSD Scripts. It will be necessary to create provisioning templates to perform the previous imaging tasks that OSD did. Remember, Provisioning is not just for deploying images. It can be used to distribute software, patch systems, execute scripts, etc.
The beauty of Provisioning is that you can chain an endless array of actions together.
LDMS 9.5 and subsequent service packs simplified the Provisioning templates and consolidated previously complex actions.
LDMS 9.6 furthers this by include simple template creation "wizards" to build a template foundation.
Creating a capture job has been simplified down to 5 steps within a single dialog:
Similarly, LDMS 9.6 has simplified creating a Deploy Image template into a single dialog:
There are two new partitioning actions that are referred to as "Smart Partitioning" actions.
Auto Assign Partitions
OS Partition will be mounted as C:
Boot partition will be mounted as S:
Windows XP and Windows 7 and higher with a separate boot partition:
OS/Boot partition will be mounted as C:
Create default partitions
LANDESK Provisioning takes advantage of the new "self-organizing" multicast. This and other improvements to the software distribution model provide drastically improved imaging and software deployment speeds.
LANDESK Management Suite 9.6 offers a new "smart migration" feature that allows you to use your Software License Monitoring data to install or reinstall software as part of an imaging and system migration solution. IProducts can be linked to packages, and in turn called as a group through a single "Install Mapped Software" action.
In addition any standard LANDESK query can be created as a "product" within the Software Licensing Monitoring tool. An example of the use of this would be if you wanted to install software on laptops only, you could create a LANDESK query that would return results for only laptops.
"Smart migration" can also be used to upgrade or change software:
Examples:
Upgrade example: Map Office® 2010 to Office® 2013
Change software example: Map iTunes® to VLC Media Player
This action changes the %ldhostname% variable to what is typed in. This is to be run before an inject script action. When the "Device Name Prompter" action runs it will pop up a windows asking the operator to enter the desired computer nam.e
This new option allows you to deploy templates from a thumb drive.
To create, put in the USB device, right click the template, and choose “Create disconnected template”. (USB thumb drive will be formatted) . The template will deploy the image, do CTOS, install the agent (Self-contained.exe) and attempt any other action that does not require a core connection.
With connection to the core, Distribute Software, Patch System and other core-dependent actions will succeed.
This new action is used in migration scenarios for migration from one computer to another computer. This action utilizes machine to machine mapping. The actions from the launched template are not included into the sections of the current template, it is run entirely just after the first template.
Improved! Change Changes to the "Wait" action
Hi
I need your help from starting to finish the procedure of PXE boot?
Thank you