Note: This is customer submitted information.   This is not officially supported by LANDESK Software.

Description

When PXE booting using LANDESK PXE boot, a DHCP server is necessary to provide an IP Address. However, there are 4 scope options in DHCP that are related to PXE. This article summarizes them and their settings.

DHCP Scope Options

There are 4 DHCP Scope options related to PXE that can work in 2 sets of 2:

• 43 and 60
• 66 and 67

When a PXE client boots, it sends out a DHCP request. This DHCP request contains option 60 to identify it as coming from a PXE client and not an OS.

A normal (Microsoft) DHCP server will reply with a DHCP provided IP address but, when neither option 60 nor option 43 is set in the DHCP Scope options, the PXE clients will still have no clue where the PXE server is and will therefore wait until a PXE server contacts them. In this way, the PXE server must listen to DHCP discovery packets containing option 60 sent by PXE clients and answer at the same time as the DHCP server does. This is the default method and also the reason why you might need to add IP Helper addresses of the IP of your PXE Representative to your VLAN configuration in the same way you would for a DHCP server when the clients and your DHCP/PXE are in seperate VLANS.

However, a DHCP Server that also has the PXE representative installed will send out only 1 reply, so we need option 60 set in DHCP. When option 60 is set to 'PXEClient', it means that the DHCP server knows where the PXE server is. If option 43 is not set, it means the PXE server is on the same computer as the DHCP server (same IP address). If option 43 is set, PXE clients must decode option 43 to know how to reach the PXE server.

Option 60 is not normally available in DHCP, but can be created and set automatically by running the following commands:

netsh dhcp server add optiondef 60 PXEClient String 0 comment=PXE support

netsh dhcp serverset optionvalue 60 STRING PXEClient

After the client receives the PXE answer it needs to go to the next step, which is to download a boot environment. This is where DHCP options 66 and 67 come in. Option 66 tells the PXE booted client what the Bootserver is and option 67 the Bootfile that needs to be loaded.

These 2 options (66 and 67) don't work with LANDESK PXE representatives and should always be left unconfigured.

The LANDESK PXE makes use of an extra layer in the bootprocess, the LANDESK PXE menu, which includes options for Local Boot, WinPE menu, WinPE Provisioning etc. Configuring the DHCP option 66 and 67 means a PXE Boot will equal a boot to a boot environment like WinPE, which presents no flexibility.

Summary:

• Set Option 60 if the PXE representative is installed on a DHCP Server, leave option 43 unconfigured.
• Set Option 60 in combination with option 43 if the PXE representative is not on the DHCP server, but also not in the broadcast range of the client
• Options 66 and 67 should NOT be set.

Applies to LANDESK Managment Suite 9.6

Issue:

How to capture a Windows 8.1 image with a provisioning template using IMAGEW.EXE v2.

How to capture a Windows 8 image with a provisioning template using IMAGEW.EXE v2.

How to capture a Windows 7 image with a provisioning template using IMAGEW.EXE v2.

Solution:

Follow the instructions in the LD96Capture document attached to this article. The document only shows Windows 8.1 but the same steps will work for Windows 7 or Windows 8. The instructions work whether the computer is doing a BIOS boot or a UEFI boot.

Applies to LANDESK Managment Suite 9.5

Issue

• How do you set up provisioning to deploy a Windows 7 image with the LANDESK imaging tool (IMAGEW.EXE v2)?
• What mode is required by provisioning for sysprep?

Resolution

Follow the instructions in the LD95Provisioning document attached to this article.

Refer to following document

http://community.landesk.com/support/docs/DOC-23248

How to Capture a Windows 7 image with OSD in LANDesk® Management Suite 9.0 SP2

I followed the document P.11 and put the OSD script, which is a windows 7 image"  I created in the schedule and started it.

Windows AIK is for Windows 7 base.

This is not first time to use OSD deploy feature of LDMS 9, so I don't know why it was failed this time. Please advice...

----------------------------------------------------------------------------------------

Applies to LANDESK Management Suite 9.6

Issue:

How do you set up provisioning to deploy a Windows 8.1 image to BIOS booted computers with the LANDESK imaging tool (IMAGEW.EXE v2)?

How do you set up provisioning to deploy a Windows 8 image to BIOS booted computers with the LANDESK imaging tool (IMAGEW.EXE v2)?

How do you set up provisioning to deploy a Windows 7 image to BIOS booted computers with the LANDESK imaging tool (IMAGEW.EXE v2)?

How do you set up provisioning to deploy a Windows 8.1 UEFI image with the LANDESK imaging tool (IMAGEW.EXE v2)?

How do you set up provisioning to deploy a Windows 8 UEFI image with the LANDESK imaging tool (IMAGEW.EXE v2)?

What mode is required by provisioning for sysprep?

Solution:

Follow the instructions in the LD96Provisioning document attached to this article. The document only shows Windows 8.1 but the same steps will work for Windows 8 and Windows 7.

Does LANDesk 9.6 has the capability to deploy Image without connecting to LANDesk Server. Same feature like MDT server has

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.

Problem:

New templates appear in the template window in the console. It is very hard to manage templates with all of these unwanted templates.

Provisioning history is very hard to follow when it is split up among all of the different spawned/locked templates.

Cause:

Scheduling open template causes new locked templates to be scheduled. This is done to prevent corruption of the template/database if it is in use and someone else is allowed to edit it.

Resolution:

• When having your techs schedule a template, you want to have them only schedule a template that is locked.

• Once you are done configuring a template, you can lock it by scheduling it against a "dummy device" in the database. Then put your new locked template in the public folder so that your techs can only see the locked template.

• If you want to change the name of your locked template, you can do so in the database. You want to go into the PROV_TEMPLATE_DEF table and change the value in the NAME column that corresponds to the locked template you are trying to make available to be scheduled.

Remember to always have regular backups of your database before making changes in the database. The change suggested here is relatively simple, but if you do not know your way around a SQL database, you do not want to accidentally make a change that can bring your database down. A good rule to adhere to; If you do not have a backup less than 24 hours old, make one before altering your database.

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 ?

We have pxe booting set as our primary boot order.  We have a preferred server acting as our pxe rep as well.  Pxe booting works perfectly fine when we boot only 1-3 or so machines at a time, or as many machines as we want as long as we boot them slowly, ie several seconds between powering on machines.  However, if you rapidly boot several computers at once, it results in the pxe-e32 tftp open timeout.  We are a school district with computer labs around 30 machines per lab.  If students come in and boot up 30 computers at once, they will all open timeout.  So far I have adjusted the mtftp timeout settings on the pxe rep however that did not resolve the issue.  Any ideas would be greatly appreciated.  Like I said, pxe booting fully works otherwise.  It is only upon rapid booting do we receive timeout issues.

Thanks for the help!

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?

I started with the provisioning and unattend templates  with the Deploying Windows 7 best known methods article.   I had to do some tweaks to get it to actually deploy the image to my machine but now it deploys and labels the drives properly.  Now  however I am getting an error during the inject script section of the template. in the status it gives me the error [80001501H] The web service responded with an invalid call"  

If I look at the inject script action in the provision history, I have the internal value result code of : -2147478271

If I look in the ldprovision log file from the client I get the following....

2013-06-18 21:32:57(1064-1024) ldProvision:*********  Begin an action - Inject_script

2013-06-18 21:32:58(1064-1024) ldProvision:Do EnvironmentCheck

2013-06-18 21:32:58(1064-1024) ldProvision:Is WinPE Action=1, Is WinPe Environment=1

2013-06-18 21:32:58(1064-1024) ldProvision:Session Data: <variables/>

2013-06-18 21:32:58(1064-1024) ldProvision:Create process (x:\cba8\httpclient.exe) with args (  -f "X:\ldprovision\InjectScriptHandler.exe" http://myserver/LdLogon/Provisioning/windows/InjectScriptHandler.exe)

2013-06-18 21:32:58(1064-1024) ldProvision:Process exit code:0

2013-06-18 21:32:58(1064-1024) ldProvision:The file (X:\ldprovision\InjectScriptHandler.exe) was successfully downloaded

2013-06-18 21:32:58(1064-1024) ldProvision:Download handler ok.

2013-06-18 21:32:58(1064-1024) ldProvision:Launching action handler [InjectScriptHandler.exe] with parameters ["]

2013-06-18 21:32:58(1064-1024) ldProvision:handler launched.

2013-06-18 21:32:58(1064-1024) ldProvision:Reporting action status: 5 to core

2013-06-18 21:32:58(1064-1024) ldProvision:Call web service GetStatusString()

2013-06-18 21:32:58(1064-1024) ldProvision:Start TryallWebService Attempt:0.

2013-06-18 21:32:58(1064-1024) ldProvision:End TryallWebService Attempt:0. ExitCode:0

2013-06-18 21:32:58(1064-1024) ldProvision:StatusString = The Web service responded with an invalid call.

2013-06-18 21:32:58(1064-1024) ldProvision:Call web service SetActionStatus()

2013-06-18 21:32:58(1064-1024) ldProvision:Start TryallWebService Attempt:0.

2013-06-18 21:33:02(1064-1024) ldProvision:End TryallWebService Attempt:0. ExitCode:0

2013-06-18 21:33:02(1064-1024) ldProvision:End of action - Inject_script

2013-06-18 21:33:02(1064-1024) ldProvision:Last action failed

2013-06-18 21:33:02(1064-1024) ldProvision:**********************************  End processing actions  **********************************

The injectscripthandler.exe log is below..

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:CreateHeaderFile - X:\ldprovision\setupinstall.header.txt

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:CreateBodyFile - X:\ldprovision\setupinstall.body.txt

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:Args = -V -H"X:\ldprovision\setupinstall.header.txt" -o"X:\ldprovision\setupinstall.body.txt" -f"X:\ldprovision\setupinstall.result.xml" http:/myserver/landesk/managementsuite/core/ProvisioningWebService/WebService.asmx

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:going to call x:\cba8\httpclient.exe -V -H"X:\ldprovision\setupinstall.header.txt" -o"X:\ldprovision\setupinstall.body.txt" -f"X:\ldprovision\setupinstall.result.xml" http://myserver/landesk/managementsuite/core/ProvisioningWebService/WebService.asmx

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:start Try httpclient No=0.

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:end Try httpclient No=0.exitCode=0

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:Exit Code of InstallCallHTTPClient = 0

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:FindElement returned 0, value is false

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:invalid result

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:FindElement returned 0

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:An internal error has occurred with the management product.

I can navigate to the path where webservice.asmx is located and seems to be fine there at least from a different computer in a web browser, and I have the drive mapped where the unattend file is located.

Any advise on where to check would be greatly appreciated..  I can't tell if it is something in IIS, or if there is somewhere else I have a file missing...  Any help would be appreciated.

Thanks

Chris

Environment:

LDMS - 9.x versions

Description:

In a Provisioning template, you added an action "Inject Script" in order to add the Unattend.xml file and you get an error message in the injectscripthandler.exe.log file telling (cf. article How to troubleshoot Provisioning Template Action Handlers to get this log);

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:CreateHeaderFile - X:\ldprovision\setupinstall.header.txt

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:CreateBodyFile - X:\ldprovision\setupinstall.body.txt

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:Args = -V -H"X:\ldprovision\setupinstall.header.txt" -o"X:\ldprovision\setupinstall.body.txt" -f"X:\ldprovision\setupinstall.result.xml" http:/myserver/landesk/managementsuite/core/ProvisioningWebService/WebService.asmx

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:going to call x:\cba8\httpclient.exe -V -H"X:\ldprovision\setupinstall.header.txt" -o"X:\ldprovision\setupinstall.body.txt" -f"X:\ldprovision\setupinstall.result.xml"http://myserver/landesk/managementsuite/core/ProvisioningWebService/WebService.asmx

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:start Try httpclient No=0.

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:end Try httpclient No=0.exitCode=0

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:Exit Code of InstallCallHTTPClient = 0

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:FindElement returned 0, value is false

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:invalid result

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:FindElement returned 0

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:An internal error has occurred with the management product

Solutions:

1- Double-Check if the Variables of the unattend.xml are correct (Tip: Try to replace the variables by some real values to isolate the issue first)

2- It may be due to some permissions on LDLOGON folder on the Core Server, then follow these instructions;

     a - Add the "Network Service" account to the LDLOGON folder permissions with Full Control and propogate the rights to all subfolders.

     b - Add the "Network Service" account to the LDLOGON share with Full Control.

     c - Restart IIS on the Core Server.

     d - Retry the OS deployment

Issue

PXE Boot fails with a "TFTP TIMEOUT" error. This can also present as the following errors:

• PXE T04
• PXE-E36
• PXE-E32
• PXE Error M0F

Cause

• The most likely cause is that the LANDESK PXE MTFTP service is not running or needs to be restarted on the PXE Representative:
• VPN software has changed the MTU setting in the registry on the PXE Representative causing TFTP to fail.
• A network device in the network is dropping or malforming network packets.

Resolution for TFTP Service not started or needs restarted

1. Open the Services applet on the PXE Representative (through Control Panel or type "services.msc" from the Run line"

2. Check the status of the LANDESK PXE TFTP service.   If it is not running, start it, if it is already running, restart it.

Resolution for PXE Representive MTU size

On the PXE Representative, do the following:

1. Open Regedit
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces
3. Search for "MTU" and select "Match whole string only".
4. There will be an MTU value for each network interface
5. Verify that the value is set to 1500
6. The PXE Representative may need to be rebooted

Resolution for Network Device Dropping or Malforming Packets

More information on PXE boot errors:

PXE Boot errors and descriptions.

How to troubleshoot LANDESK PXE boot:

Troubleshooting PXE boot (OSD)

Issue

When attempting to PXE boot, the following error appears:

• PXE Boot fails.
• No F8 option is recieved by clients.
• Unable to PXE Boot machines.
• Unable to network boot machines.

Cause

• No PXE representatives are deployed.
• Deployed PXE Representative is turned off.
• PXE representative is not in the same broadcast domain as target machine.
• Firewall on PXE representative is blocking requests from target machine.
• PXE services are not running.
• Windows Deployment Services (WDS) are installed on the PXE representative.
• Another service on the server is using port 67

Resolution

• Update BIOS on device
• Ensure that a PXE representative is on and is deployed in the same broadcast domain as the target machine.
• Ensure that no firewall is blocking requested packets from PXE booted machines.
• Ensure PXE services are running.  The two services are "LANDESK® PXE Service" and "LANDESK® PXE MTFTP Service".
  If they are running, restart the services.
• Redeploy the PXE Representative.
• If PXE services repeatedly stop on PXE representatives, download and install the latest service pack on the core, then remove and redeploy PXE representatives.
• Disable the Windows Deployment Services (WDS) on the PXE representative.
• Run the "netstat -abn" command to find the service which is using port 67 and disable/reconfigure this service.

Note: The PXE Representative may need to be rebooted if the services are running, the firewall is off, but it still does not respond.

More information on PXE boot errors:

PXE Boot errors and descriptions.

How to troubleshoot PXE boot:

Troubleshooting PXE boot (OSD)

Issue

When booting into WinPE via PXE server, the following error message occurs:

PXE-E55 ProxyDHCP: No reply to request on port 4011

Cause

• Option 60 is enabled on the DHCP Server
• A firewall may be blocking client traffic to the PXE representative

Resolution

• Create firewall exceptions that allow the client traffic to reach the PXE Representative.
• Disable Option 60 on the DHCP Server according to manufacturer/vendor specifications.

For additional information, please visit Microsoft KB Article 259670

More information on PXE boot errors:

PXE Boot errors and descriptions.

Troubleshooting PXE boot:

How to troubleshoot PXE boot (OSD)

Issue

The following error shows up when PXE booting:

PXE-E51: No DHCP or proxyDHCP offers were received.

• PXE Boot Fails
  
  

Cause

• This error occurs when the PXE client does not received any offers from a DHCP server or a PXE Representative.
• Ensure that the client can access the DHCP server and/or PXE Representative over the network.
• Ensure that the client has connectivity (something as simple as an unplugged network card can cause this error)
  

Resolution

Ensure that the client can contact a DHCP server.
Ensure that the PXE representative can be reached on the network, and that the LANDESK PXE service is started.

Common issues and things to check

• Is the IP Address scope full?
• Are any addresses available for the PXE client?
• Is network latency causing the client to time out before contacting the DHCP server?
  (Check ping between between client subnet and DHCP)
• Is the DHCP server down or is the DHCP Service stopped?
• Are BootP packets being blocked between the PXE client and the DHCP server?

More information on PXE boot errors:

PXE Boot errors and descriptions.

How to troubleshoot PXE boot:

Troubleshooting PXE boot (OSD)

Hi everyone,

i have a little problem with my provisionning, i can't make a system partition and i get the error : An operating system wasn't found. try disconnecting any drives that don't contain an operating system.

I try to solve that with command bcdboot.exe.

I see that in the LD955Provisioning.pdf  :

When i import my template i have not the same

I have that :

I'm in version 9.5 SP2.

Anyone have the same problem or know how to solve it?

Hi all

All our OS deployment templates have Patch system as the last action under system configuration. They all set to Scan Only. I tried and tried to get a good explanation on what this means and all i keep coming up with is that it ... well ... scans local system for what is missing. But seems like i cant find more fine details - Scans local system against what? Once scan what does it do? Etc... Just missing info to understand what it actually does.

Thanks a lot

I have a strange problem with LanDesk 9 Sp2. I can download provisioning template in one side of the floor. If I try to download LanDesk  provisioning template on other side of the floor, I am getting this message "Provisioning Task failing after try 40 of 40". I am using the same ID and password. Both sides are using same PXE Rep. and same subnet mask. Any idea? But when I use my administrative account, this works. This problem only for regular LanDesk accounts.

Thanks