Hi,

I have a problem, when i try to launch a comppuetr to WINPE Menu, the MFTP give me time out error, when i choose Provisioning Menu, it works !

Anybody already have this error.

help !

Thanks.

Ben

Hello,

we want to deploy x86 windows 7 Image on new HP devices with UEFI enabled bios.  Problem: with UEFI enabled, PXE automaticaly loads boot_x64.wim which is not able to install drivers in HII with DISM to x86 Images. I don't see any possibility to boot the x86 wim (boot.wim) on UEFI. I tried, to rename boot_x64 to boot.wim but get an error (winload.efi not available).

regards

Alex

The scenario doesn't work by design, as per Microsoft specifications:

http://technet.microsoft.com/en-us/library/hh290675%28v=ws.10%29.aspx

http://technet.microsoft.com/en-us/library/hh825186.aspx

With Provisioning, I'd like to run a powershell script after the workstation joins the domain. The script adds an AD group to the local admin's. I've thought about doing this on the build, but joining to the domain kicks me out of Audit mode when I am building the image and I'd like to avoid that if possible.

Can I run a powershell script from provisioning? Is there a better way I should do this?

(the workstations are win7 x86)

Description

This issue is characterized by selecting an OSD script from within the PXE Boot Menu inside WinPE, the Boot Menu window disappearing, and then no further pop ups or display windows occurring.

There are several causes for this behavior, and therefore, several possible solutions. This troubleshooting guide is centered around the issue of the OSD script failing to be initiated on the core server, or the OSD logs indicating that the machine is "OFF".

Identifying the Issue

To determine the troubleshooting path, it must first be determined how far the process is progressing. The fastest way to accomplish this is to determine if a CustJob log is being created. Follow the steps below to determine this:

1. On the core server, go to the log directory. This is located at the following path <Install Drive>:\Program Files (x86)\LANDesk\ManagementSuite\logs or can also be accessed via UNC share at <coreservername>\ldlog.

2. Once in the log directory, it is recommended to sort by Date Modified, with most recent at the top.

3. The log file will be named CJ-OSD-<scriptname>-<timestamp>.log

4. If there is a log file, open it with a text editor, such as notepad or word.

5. If the log file is similar to the one listed below, and indicates that the machine is OFF, then CBA is unable to contact the specified machine or CustJob has targeted an incorrect machine record.

"Machine","CbaStatus","ExitCode","Duration","Begin","End","Command"

"(OFF) XPSP2B","OFF","N/A","0:00:00","11/6/2008 12:19:28 PM","11/6/2008 12:19:28 PM","N/A"
; "Job Complete","0 Done","0 Failed","1 Off","0 Unknown"

 

Causes

Client cannot contact the Agent on UDP port 38293. (Firewall, or other filtering device is blocking this port.)

Core can send UDP packages to client machine, and client machine can send UDP packages to core server too, The below screenshot is the correct screenshot, if UDP packages only can send from core to client, the client machine will be treated as off status:

Resolutions

Open UDP port 38293 between the Core Server and the client machine.

Environment

LANDesk Provisioning
Target machine booting in UEFI mode

Problem/Issue/Symptoms

Booting a machine in UEFI mode in a network segment with an active PXE representative doesn't make the machine loading WinPE.
The PXE menu doesn't appear.
The machine reports the error PXE-E21: Remote boot cancelled

Solution

UEFI is still not compliant with the PXE menu specifications, therefore booting a machine in UEFI mode via PXE for provisioning works only when the machine is associated to a provisioning task on the core.

The error PXE-E21 appears when the machines not associated to a provisioning task on the core.

LANDesk submitted an enhancement request to the UEFI Forum regarding this issue. Once they add the support needed, LANDesk will be able to support the PXE menu for the devices booting vin UEFI mode as well.

At the moment, the only way to have the PXE menu functionality on a device booting in UEFI mode is setting it up to boot in BIOS mode.

Hi, I modified the xml file with %ldHostname% variable in order for Windows 7 to use the existing hostname from the LDMS inventory.  Windows 7 won't boot all the way once I added the %ldHostname% variable. It goes through the sysprep process then error out. It boots up fine without the %ldHostname% variable. The history.  Master image created / captured by LDMS9.5 SP1 initially without syspreped.  I deployed the image on to a machine with an attempt to sysprep that's where I got the error. When I click okay then Windows reboot and stuck at the same place.  I'm not sure if anyone has similar experience or workaround.  Thanks in advance.

We are using OSD with provisioning templates in our environment. The new requirement is to use the existing image and provisioning templates to do imaging from our warehose which has no connectivity to LANDesk Server. Can we perform  OSD through a DVD or portable harddisk in this scenario. Please suggest.

Hello,

I have to deploy ESXi 5.0 image on servers thanks to LANDesk PXE.

We currently have 9.5 SP1, but our PXE representative have 9.0 SP3 PXE version (the winpe image is a windows 7 version, not windows 8).

I try to boot on LinuxPE boot image, but it stops on "ACPI ; Assume root bridge [\_SB_.PCI0] bus is 0".

Does someone use LANDesk PXE to deploy ESXi image ? A way to do this through WinPE ?

Thanks

This document is intended to assist LANDesk® Management Suite users with the deployment of images to a Mac OS X device.

Is there a nice (read: Elegant) way to do this?  Besides using an AutoIT script I wrote...

Seems like you wouldn't want anyone on the "other end" attempting to log in while you are configuring, running HII, joining the domain, and just preparing to reboot anyways.

Here's my template after CTOS reboot:

Configure 'provisioning' agent

Join domain

Activate Windows

HII

Configure 'real' agent

Delete unattends

Install any other software...

Reboot

I already don't autologin here, there's no need to.  I want to disable logging in and bring the UI in front of the winlogon.  Possible?

Has anybody seen when you network boot with Windows PE Provisioning that it simply boots into WinPE and than stops at the command prompt after basic winpe functions have been ran.

Basically at this point, we se the X:\LDPROVISION folder is created but empty.

It was working fine. Suddenly one of the OS deployment tasks failed during an inject unattend file. Restarted PXE Rep and provisioning would no longer load. It doesn't load in Windows or in Win PE - However, Win PE Menu still works.

Hello

I was wondering if there is a way to change the script to capture more than one disk? Currently I am only able to capture one disk but noticed there is no option to capture anything other than that one drive on the GUI. Any help is appreciated.

Hi All,

Haven't posted on here in some time ! 

I've been tasked with updating a HII Provisioning template I built back in early 8.8 days FUN! As i'm sure you can imagine it's not working now. Before I start troubleshooting it, I was wondering if someone could shed some light on core changes in V9 SP2 done in provisioning which would effect my template. Right off the bat, I know were working with a new version of WINPE, and HII is now built into LANDesk suite so there are some process changes there.

I've noticed already that Templates built under a specific user and then moved to public folder get the error "The selected softare distribution package is invalid. Specify a valid software distribution package." It appears the Public templates only look at the software packages stored in the public folder vs looking back at the original creators folder like it did in V 8.8. Is this a known issue, or to expected functionality?

If there are any good docs, for HII with Provisioning which you all recommend that would be great. Figured I would hit the community to pick up on known issues with SP2, and Provisioning before diving into it.

Thanks all - and happy holidays!

-Ryse

Troubleshooting LANDesk Provisioning

Troubleshooting - Core Side

View histories for failures or error messages

View provisioning.log located in
CoreServer\ldlogon\provisioning folder for template execution messages

View PXE Rep deployment and prov_schedule log files in the
CoreServer\ldmain\log folder

Troubleshooting – Target Machine

View the launch.log in X:\ldprovision folder for provisioning loading status

View ldProvision.log in X:\ldprovision folder for error messages and XML content

View Output.txt in c:\ldprovision folder for application error messages only if app hangs

Use Alt + F2 to toggle to command prompt

View /var/log/messages for errors loading LinuxPE

View /var/log/taskmaster.log for errors load provisioning

View /var/log/provisioning.log for template errors and XML content

Windows Target device

View ldProvision.log in WinDir\Temp folder for error messages and XML content

View run##.tmp in WinDir\Temp folder for template execution messages

Linux Target device

View ldProvision.log in /tmp folder

Troubleshooting – PE Manual Execution

Load new console in PE and change to ldprovision folder X:\ldprovision – PXE, Z:\ldprovision – Boot Media

Launch provisioning by executing ldprovision.exe

ldProvision command-line options:

-c[corename] or IP

-d debug (Note: no space should be used after -c and the core server name)

-f task XML file name

-h help

-m mode 1-3 (1=default)

-t download directory

-s run as daemon (Linux only)

-v version (NOTE: This is lower case v)

-V # (1-255) Verbose logging (NOTE: This is capital V)

Example: ldprovision –c mycore –t x:\ldclient -V 255     

Troubleshooting – OS Manual Execution

Using target that has ld agent installed, map drive to or copy contents of
CoreServer\ldlogon\provisioning\windows from core to local folder

Execute ldprovision as shown in PE manual execution, note log files are placed in windir\temp

Using target that has ld agent installed, mount point to or copy contents of
CoreServer\ldlogon\provisioning\linux from core to local /tmp folder

Execute ldprovision as shown in PE manual execution, note log files are placed in var/log---

Greetings,

We have been using our PXE Representative for a few years, and I have found a solution for everything needed so far. This is the first time I have run into this issue without finding the answer.

It appears the Intel BIOS on the Lenovo X230 laptop has been updated and I have changed all settings to legacy. The laptop makes the handshake with the PXE rep and just stops at the MTFTP download. "MTFTP." displays and disappears from the screen, and that is as far as the process will go.

I placed a band aid on the issue for now by placing the X230 drivers into the T430 driver folder, imaging the T430, switching the hard drive to the X230 and updating the drivers.

Can someone point me in the direction to solve the issue? We are currently using LDMS 9.0 SP3, but LDMS 9.5 SP1 will be deployed in two weeks

Thanks in advance,

Jim J

Hallo,

ich habe folgendes Problem.

Wir setzen die Landesk managment Suite 9.5 mit SP 1 ein. Ich möchte nun beginnen unsere Clients zu Sichern bzw. wieder zu deployen. In der Alten version ging dies Prima mit dem PXE Client. Wenn ich nun versuche den PXE Client über PXE Representativ Deploy zu installieren, zeigt mir der task erfolgreich an, auf dem Client ist allerdgins kein PXE Client installiert worden.

Wo kann ich nachsehen? Woran kann das liegen?

Gruß

fisi

In LANDesk Managment Suite 8.8, there was a button in the OSD tool that allowed you to manage the free space in the WinPE image. However, in LANDesk Management Suite 9 and 9.5, no such button exists. Because of the change to WinPE 2.1 and the associated change to a .wim file, this task must be accomplished another way. The steps below are dependant on the OS running on the machine where you are editing the boot.wim, for simplicity's sake it is best to modify the boot.wim on a device with Windows 7, Server 2008 R2, or later, and then copy it back to the core if needed.

Important Note: Any increase in size of the free space inside the WinPE image requires that the corresponding space be available in RAM on the client machine. For example, a machine with only 512MB RAM WILL NOT load a WinPE image that is set to use 512MB of scratch space. The total space needed is approximately 365 MB plus free space. In WinPE Scratch Space can be set to 32, 64, 128, 256, or 512 MB.

Windows 7\Server 2008 R2 or Later Method:

1. Create the following folder structure C:\Mount\Bootwim
2. Copy \Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\boot.wim to the C:\Mount\ folder.
3. Open a CMD prompt as an Administrator.
4. Use DISM to mount the boot.wim:
   1. DISM /Mount-Wim /WimFile:C:\Mount\Boot.wim /index:1 /MountDir:C:\mount\bootwim
5. Use DISM to increase the Scratch Space (This example increases it by 256MB):
   1. DISM /image:C:\mount\bootwim /Set-ScratchSpace:256
6. Use DISM to commit the change, and unmount the image:
   1. DISM /Unmount-Wim /MountDir:C:\mount\bootwim\ /Commit
7. Copy the modified boot.wim from C:\Mount\boot.wim to \Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\boot.wim.
8. Update the PXE representatives. You can use the script from this article: Updating the WinPE image on PXE representatives

Windows XP\Server 2003 Method:

What you need:

A machine with Windows AIK installed

Access to \\<CORE>\ldmain\files\vboot\boot.wim

Note: This process involves modifying the boot.wim, or the WinPE image. For more information about mounting and editing the boot.wim or WinPE image please see: How to manually modify the boot.wim WinPE image in LDMS 9

What to do (Overview)

To increase the free space, or scratch space as it is called, you need to mount the boot.wim image, open the registry and modify the following key:

HKLM\SYSTEM\ControlSet001\Services\FBWF\WinPECacheThreashold (REG_DWORD) and set it to the desired number. Acceptable values are 32 (default for WinPE <=4), 64, 128, 256 and 512. Then commit the changes to the WinPE image and update the PXE reps with the new image.

What to do (Step-by-step)

• Open a command prompt on the machine that has Windows A IK installed
• Create a new folder on the root of C: named mount (C:\mount)
• Navigate to the folder containing imagew. In my case it was in C:\Program Files\Windows AIK\Tools\x86.
• Run: imagex.exe /mountrw "<Path to boot.wim>\boot.wim" 1 c:\mount
• Run: regedit.exe
• Inside regedit, select the HKEY_LOCAL_MACHINE hive, then select "Load hive"
• Navigate to C:\mount\Windows\System32\config and select the file SYSTEM. See graphic below. (Note: DO NOT select the SYSTEM txt file or the SYSTEM.SAV file)

• Enter a name to reference the freshly loaded hive. For example, WinPE
• Navigate through the hive to \ControlSet001\Services\FBWF\WinPECacheThreshold
• Create a new REG_DWORD value named WinPECacheThreshold
• Set the new REG_DWORD to the value desired. Allowed values are 32 (default), 64, 128, 256, 512. (20, 40, 80, 100, 200 in hex)

• Once the value is set, select the key that you loaded the hive into, for example WinPE and then select File -> Unload hive. Close regedit
• Run the following at the command prompt to commit the changes to the WinPE image: imagex.exe /unmount /commit c:\mount
• Update the PXE representatives. You can use the script from this article: Updating the WinPE image on PXE representatives

Once this is done, you can reboot any clients back into WinPE and you should see the corresponding increase in free space.

Important Note: Any increase in size of the free space inside the WinPE image requires that the corresponding space be available in RAM on the client machine. For example, a machine with only 512MB RAM WILL NOT load a WinPE image that is set to use 512MB of scratch space. The total space needed is approximately 365 MB plus free space.

Create image capture script

a. Open the LDMS console. Click Tools > Distribution >OS Deployment

b. Right click on All OSD/Profile Migration Scripts and select a new script based on the imaging environment you will use.

c. Select capture image. Give the script a name and a description.

d. Specify the credentials to be used

e. Specify the image information. If you will use LANDesk's imaging tools, choose LANDesk ImageW V2 for the Image type. Enter the UNC path where you will capture the image. For the path to the imaging application, use \\coreservername\ldmain\osd\imagew 2

Replace "coreservername" with the name of your core server. Replace "imagingtool" with imagew.exe (for Windows PE) or image.exe (for DOS).

f. Right click on the OSD script and click advance edit

g. Click Use editor button

h. Copy and paste this line, and modify OSD script as below:

i. If using the PXE Boot Menu, it is necessary to drag the script from the scripts folder to the PXE Boot Menu folder under the PXE Boot Menu section. This places the script in the bootmenu.cfg file.

NOTE: for LANDesk 8.8 and newer, it is adviced that you use the "Image Type" of "LANDesk ImageW V2", this will require the path to be altered for the image application in the last line of the script to reflect the correct path.  For version 9, it is "\\Coreservername\ldmain\osd\imagew 2\imagew.exe"

To open this screen select Tools | Distribution | PXE Boot Menu. Once this screen is open, drag the script to the PXE Boot Menu folder. After the script is copied to the PXE Boot Menu, click the Update button which refreshes the bootmenu.cfg file stored on the core.

Boot wim does not download from PXE Rep on Dell E7240. Device has Intel Boot Agent GE v1.5.38.01. MTFTP pops up but then nothing downloads.

Anyone else seen issues with this version of the Intel Boot Agent?

Regards