Quick question. We have a system set up where we have a server with an embedded device image in a LAN.  We can PXE boot clients within the local network, which picks up on the PXE request and automatically does a Restore from the embedded image on thes server via a script.  Since we are now using Landesk, the formatting on the file has changed and I am looking to do the same thing if I can, but I need to find out how I can plant the LinuxPE PXE loader on my server and be able to image my clients within the local network.  The other "catch" is that this local network does not talk to the Core and does not contain a PXE rep (per say) that reports into the Core.  I would need this as a stand-a-lone, just a basic imaging solution where the Landesk image is on a server within the LAN and clients can PXE boot to the server , which offers DHCP, and also contains the image to be restored from via PXE  Any help would be appreciated, thank you..

This a NEW Dell Optiplex 7010, right out the box. Just received a shipment of 200 computers, have already imaged 25 of the set with Our Windows 7- Dell 7010 image and then cpu # 26 - 40, will not do anything after you select the deploy option. Tried swapping ram and hard drives. Verified that the configuration for the first batch (cpu #0 - 24) was that same as the second batch (#25-40). Funny thing is that, if I take one of the cpu's from the first batch (#0-24) and try to reimage it using the same 7010 image, EVERYTHING works ok or if I take one of the hard drives from the first batch (that is imaged) and place it in the second batch, it will boot to our startup script. Using LANDesk ver 9.0.3.1.

Description

It has been noticed by some customers that an issue is occuring with Imagew V2 in SP2 regarding an error that states the file NTLDR is missing.  This occurs after the image has successfully deployed and rebooted from PE.

Cause

The version of imagew in 8.8 SP2 (2.1.5) seems to have a problem with correctly setting the MBR for XP machines.

Resolution

If Windows Vista is not the target OS, use the attached version of Imagew (2.0.6).

1. Download the attached version of Imagew.

2. On the core, browse to the <InstallDrive>\Program Files\LANDesk\ManagementSuite\osd\imaging\2.0 folder.

3. Rename or delete the current Imagew file (version 2.1.5).

4. Copy the attached file into the folder.

         Description

If using just the WINPE you never see the WINPE script menu following the F8 menu.  This happens more at remote sites with a slow links back to the Core, but can happen on any network with slow links or heavy network traffic.

         Cause

pxemenustart.exe is being run before the Core has received and processed the most recent miniscan containing the IP address of the machine.

         Resolution

Edit the startnet.cmd file, in the ldvpe1.img file with WinImage (http://www.winimage.com/), to run ldsleep with a wait of 5 or 10 right before the wait4ip command. The startnet.cmd file is found in the ldvpe1.img file at \i386\system32. See below for an example:

 REM wait to get a valid IP       X:\ldclient\ldsleep 10      \ldclient\wait4ip /t 180           if %errorlevel% gtr 0 goto fail

After you have edited the startnet.cmd and reinjected it to the the ldvpe1.img file you will need to redeploy the PXE reps.

Description

Cause

Resolution

Increase the amount of free space in ldvpe1.img file and redeploy All PXE Rep's and try the OSD deployment again.

Description

When PXE booting an E74 is given and no F8 menu appears. Error: "PXE-E74 bad or missing pxe menu and or prompt information". Also, the PXE F8 menu does not come up. The proxy IP indicates the correct address. Re-deploying the PXE representative does not resolve the problem. Installing PXE rep on another machine does not resolve the issue.

Causes

• The PXE rep installation software is corrupt.
• Port 69 Traffic is blocked to the PXE Representative
• The PXE Agent embedded in the firmware of the NIC is handling DHCP option 43 incorrectly
• The BIOS and NIC firmware have a limited capacity for PXE Boot Menu options. This has been seen on a number of computers including:
  • Lenovo machines with BIOS 3.11 or later

Resolution

Disable some PXE Boot Menu options

• It has been found that some updated versions of BIOS from some manufacturers do not properly handle large PXE boot menus
• To reduce the PXE boot options see: 'How to hide LinuxPE, WinPE, or DOS PE PXE Boot Options from the F8 Menu?'
• It is recommended to remove the LinuxPE and DosPE options, as they are normally not used

Obtain a new osdrep.msi installation package from LANDesk Support.

• Copy the osdrep.msi file into the C:\Program Files\LANDesk\ManagementSuite\landesk\files folder.

• Run the PXE Rep deployment script on the target machine.

Enable traffic on port 69 to the PXE Representative

• This would be configured in the client firewall, or possibly a switch on the network

DHCP Options 43 and 60 should not be used when using LANDesk to PXE boot

• Options 43 and 60 should not be configured on the DHCP server when using LANDesk PXE boot as they will conflict with the information and data sent to the client from the PXE representative. See below for step is resolving this.

Windows Server 2003

1. Open DHCP on Windows 2003 Server
2. Go to -> Scope -> Scope Options
3. Right click and choose Scope Options and choose Configure Options
4. Uncheck either option 060 and option 043 (they are not be needed)

DHCP Configuration when using LANDesk PXE Boot

When neither option 60 nor option 43 is set, PXE clients will wait until a PXE server contacts them. The LANDesk PXE representative will listen to DHCP discovery packets sent by PXE clients and answer at the same time as the DHCP server does. The LANDesk PXE and LANDesk PXE MTFTP services on the PXE representatives handle the requests made by clients attempting to PXE Boot.

In order to support PXE clients on a network, the DHCP server is usually configured in one of the following three modes:

• Option 60 not set, Option 43 not set
• Option 60 set to 'PXEClient', Option 43 not set
• Option 60 set to 'PXEClient', Option 43 set

When neither option 60 nor option 43 is set, PXE clients will have no clue where the PXE server is, and they will therefore wait until a PXE server contacts them. In this mode, the PXE server must listen to DHCP discovery packets sent by PXE clients and answer at the same time as the DHCP server does.

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, 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.

In most situations, option 43 does not need to be setup, because the PXE server will either listen to DHCP discovery packets (DHCPProxy), or be on the same computer as the DHCP server. However, if the PXE server is on a separate subnet (it cannot listen to DHCP discovery packets), or if there are several PXE servers on the same subnet, option 43 is the only viable solution in order to instruct PXE clients on what to do.

For more information on PXE boot errors please see:

PXE Boot errors and descriptions.

For more information on troubleshooting PXE boot please see:

Troubleshooting PXE boot (OSD)

Cause

Resolution

If on 8.7 SP1 or earlier, do the following:

1.  

   Update the Core Server is updated to the Latest Service pack.

2.  

   Uninstall and reinstall all PXE Representatives with the PXE Rep from the latest service pack.

If 8.7 SP3 or Later is installed already, do one of the following:

Run the mini-scan again manually from within WinPE by opening a command prompt and running this command:

Startnet.cmd

OR, modify the startnet.cmd to give wait4ip.exe more time to run by following the steps below on the core:

1. Using WinImage, open the LDVPE1.img file located in the landesk\vboot folder.

2. Inside the i386\system32 folder, locate and extract the startnet.cmd file.

3. In the startnet.cmd file, locate the wait4ip line and add the following line immediately before the wait4ip line:

X:\LDClient\LDSleep.exe 15

For example:

REM wait to get a valid IP

X:\LDClient\LDSleep.exe 15
\ldclient\wait4ip /t 180

if %errorlevel% gtr 0 goto fail

4. Save the changes to the startnet.cmd and then inject back into the LDVPE1.IMG, then save the changes to the IMG file in WinImage.

5. Re-deploy the PXE Reps in the environment.

When machines are attempting to PXE boot they are failing with error; **

BOOT SERVER IP: x.x.x.xMFTP...PXE-T00 Undefined error code,  or PXE-T01 Undefined error codePXE-E36: Error received from TFTP serverPXE-M0F: Exiting (NIC Manufacturer) PXE ROM.

This is being caused by the PXE Representative attempting to redirect the Client machine to a PXE Rep in another subnet for file download. Currently there are only two solutions;

1) Remove all PXE Representatives except the one you are attempting to use.

2) Disable the Multicast option for the MTFTP service on the PXE Representative.

There is only one supported option for disabling Multicast on the MTFTP server. Disabling Multicast on the MTFTP server will not have a significant effect on the process of imaging machines even if using the Multicast option in the script or template.

Instructions for how to manually disable Multicast (this will need to be performed on all PXE Representatives);

1) On PXE Rep, go to C:\Program Files\LANDesk\PXE\System, double click to run PxeConfig.exe.         

2) Right click "Boot Server", then click "Configure Boot Server..", select the "MTFTP Options" tab, and un-check the Multicast option checkbox.         

3) Restart both LANDesk PXE services on the PXE Rep and boot into WinPE

**This solution is known to resolve this issue in 8.7, and 8.8. If this is not helpful in resolving the issue please contact support at 1-800-581-4553 or https://emea.salesforce.com/sserv/login.jsp?orgId=00D20000000003a

For more information on PXE boot errors please see:

PXE Boot errors and descriptions.

For more information on troubleshooting PXE boot please see:

Troubleshooting PXE boot (OSD)

Problems/Symptoms:

When booting a machine via DOS PXE, one of the following errors may occur.

HTGET: Could not get connected, retry 0

Causeway 9

3510:255 Image stream corrupt (image process aborts mid-operation)

Type the name of the Command Interpreter (e.g., C:\WINDOWS\COMMAND.COM)

"Hanging" on "Waiting for command"

Fix:

Download the updated LANDesk DOS PXE Boot Images:

http://community.landesk.com/downloads/patch/PXE_BOOT_4.5.0.zip

The updated PXE DOS Boot Images will work with any version of LANDesk.

Before any work can be done with the boot images, it is necessary to download the Winimage utility and install on the Core Server.

WinImage can be downloaded here:

http://america.winimage.com/download/winima81.exe

How to fix Name Resolution Issues:

Download the updated DOS Boot Images and copy them to the core server.

1.  Open CoreServer\Program Files\LANDesk\Managementsuite\LANDesk\Files\DOSUNDI.1 with Winimage.

2.  Extract the file STARTENV. BAT from the root of the boot image.  This can be done by dragging it to the desktop.

3.  Open the STARTENV.BAT and change SET COREHOST= [YourCoreServer] to SET COREHOST=[coreserver ip address]

4.  Save the modified STARTENV.BAT file and re-inject into the root of the image. Remember to save the image after injecting the new STARTENV.BAT file.

5.  Using WinImage, navigate to the \NET directory of the image.

6.  Extract the LMHOSTS file from the image

7.  Edit the LMHOSTS file with notepad and add entries for ANY server that will be referred to in OSD tasks

Example:

       # x.x.x.x This entry is the core server where the image utility is stored

       # x.x.x.x This entry is for an image store other than the core server

8.  Save the LMHOSTS file, and re-inject into the \NET directory of the DOSUNDI.1 image. Remember to save after injecting

9.  Make the same changes listed above to CoreServer\Program Files\LANDesk\Managementsuite\LANDesk\Files\BOOTMENU.1

NOTE:  Do not forget to update the BOOTMENU.1 file with the same changes.  A DOS PXE Boot uses the BOOTMENU.1 as the boot image, and the name resolution issues must be fixed here as well.

Adding Drivers to the boot images

1.  Download the manufacturer driver(s) from the appropriate vendor

2.  On the core server, open the  \Program Files\LANDesk\Managementsuite\LANDesk\Files\DOSUNDI.1 boot image using Winimage.

3.  Navigate to the \NET directory of the image. Extract the net.zip file from the image

4.  Open net.zip with preferred tool (WinZip, WinRar, etc.) and add the *.DOS driver file downloaded from the vendor

5.  Save the changes to NET.ZIP and inject back into the \NET directory of the boot image

6.  Navigate to the \NET directory of the image. Extract the nic.txt file from the image

7.  Copy nicinfo.exe from [Your_Core_Server]\ldmain\landesk\vboot directory to a machine with desired NIC running Windows.

This will generate a file "dosnic.ini" in the same directory as the executable with the vendor and PCI device information of the network card.

8.  Open the nic.txt and verify the information returned in the nicinfo.ini is listed. If not, add the vendor and/or deviceid following the existing

format.

9.  Save the nic.txt file and inject into \net directory of the DOSUNDI.1 boot image using the Winimage utility.

10.  Make the same changes listed above to CoreServer\Program Files\LANDesk\Managementsuite\LANDesk\Files\BOOTMENU.1

NOTE: DRIVER WILL NOT BE USED IF MAPPING DOES NOT EXIST IN NIC.TXT 

Note that the Intel Universal NDIS Driver (UNDI) is loaded. If a manufaturer specific driver was desired and the undi driver still

loaded, double check the steps above.

Note:  Re-deploy PXE representatives for changes to take effect

Problem

PXE-E52: ProxyDHCP offers were received. No DHCP offers were received. PXE Boot Fails

Cause

This occurs when the PXE client receives a response from a PXE proxy but cannot contact the DHCP server.

Fix

Resolve the problem with the DHCP server.

Common issues and things to check

• Is the IP Address scope full
• Are any addresses available for the PXE client
• Is the DHCP server down or is the DHCP Service stopped
• Are BootP packets being blocked between the PXE client and the DHCP server

For more information on PXE boot errors please see:

PXE Boot errors and descriptions.

For more information on troubleshooting PXE boot please see:

Troubleshooting PXE boot (OSD)

Description

When attempting to PXE boot, the following error appears:

PXE-E53: No boot filename received

Also,

PXE Boot fails.

No F8 option is recieved by clients.

Unable to PXE Boot machines.

Unable to network boot machines.

Cause

Possible causes:

• No PXE representatives are deployed
• Deployed PXE Representative is turned off.
• PXE representative is not in 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.

Resolution

Possible steps for resolution:

• Ensure that a PXE rep 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(R)PXE Service" and "LANDesk(R) 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.

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

For more information on PXE boot errors please see:

PXE Boot errors and descriptions.

For more information on troubleshooting PXE boot please see:

Troubleshooting PXE boot (OSD)

Problems/Symptoms:

When trying to create a new PE configuration (DOS or WinPE), the following message appears:

"Before you use OS Deployment, please supply the legal license first."

Cause:

Fix:

To validate your OSD credentials for the following environment types, please follow the steps below:

WinPE Validation

1.  If you have the 2005 WinPE CD, you can validate the environment by following the steps below:

a.  Open the console on the core.

b.  In the toolbar, select Configure &gt; Services.

c.  At the bottom of this window is a button labeled OSD Validation.  Select this button.

d.  On the new window, select "Validate now" in the box labeled "Windows PE imaging environment"

f. When prompted, browse to the location of the 2005 WinPE CD and select OK.

g.You will also need to provide a Server 2003 SP1 CD as part of this validation process and willbe prompted to browse to this as well.

Once the files have been verified, you will be able to create new PE configurations.

NOTE:  Please see the following article as the licensing availability has changed:

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

DOS Validation

In the LANDesk console go to Configure &gt; Services.

Thereis a button labeled OSD Validation. Select this buttonand the OS Deployment validation tool will open.

Select "Validate now" in the box labeled "DOS imaging environment".

When you click on the browse button, the path to browse to will appear on the top of the browse dialog.

The path is highlighted here:

You will need to provide a Windows NT 4 Server CD and a Windows 98 CD.

The files needed to validate the DOS environment are provided by these disks.

For NT 4 server the path is: {CD DRIVE}:\CLIENTS\MSCLIENT\DISKS

For WIN 98 the path is: {CD DRIVE}:\WIN98

Hello, I have created a windows 8 image to test with.  We currently have landesk 9.5sp1 in our environment and its working perfectly. I want to be able to update Windows 8 to 8.1 when released but need to keep the partition small as when I first created the image.  How do I update the current image without capturing the entire 128gb hard drive?

I have just upgraded LDMS from 9.0sp4 to 9.5, then immediately rebooted and upgraded to 9.5 sp1.

I am now trying my OSD scripts for the first time, and am having issues.

When I boot, I get into WINPE, but the PXEMENU is blank or white.

Upon further reading, I see that I need to inject win8 64bit ethernet drivers.

• Even though I can ping my core without any updating.

Now when I try and click on the "Manage the drivers in the WinPE image" button, it is greyed out, and I am not sure how to fix it.

I have now been on the phone waiting for tech support for 1 hr and 44 minutes.  Any help would be appreciated. :-)

Anyone been able to boot a UEFI enabled device using a PXE rep from LDMS 9.5. I have tried two Dell devices (Latitude 10 Tablet and an Latitude E6430), both timeout when 'Stert with PXE IPv4'

On occasion we'll have a file transfer interruption when moving files across our WAN.  By default, the file split is at ~2GB, which means that the entire file needs to be re-transferred.

What do i need to do to create smaller files?  Smaller files would make it easier to recover from a file transfer error since less data would need to be retransmitted.

Hello

We've just started using Provisioning instead of OSD for PC deployment.  The primary goal is to use HII and have a hardware independent base image that we can use on multiple systems.

Our security requirements state that an end-user cannot install any devices on the PC (including printers) and we are deploying batches (50+) of sytems to remote users.

The company provides very basic USB print (some MFPs) devices to the end-users, but I do not have information on which device a particular user has during the deployment process, so we were installing the standard five print devices in our OSD images.  When the end-user plugged in the device, they were set.

I've been using a VM to create my hardware independent base image and do not have a way to plug these printers into the VM to perform the device installs.  I can load the drivers which is somewhat helpful, but without the print device being installed we are guarnteed 50+ help desk calls per batch of PCs released to perform printer installs. 

Has anyone had to include installed printers in your images?  If so can you share how you made it work?

Thanks!

All my .MSI distribution packages are reporting as failed although they have installed.

This started yesterday and am unaware of any changes that have been made

I used diskpart to reduce the size of a volume/partition from 500gb to 251 gb on a 500gb hard drive. How do I capture only the 251 gb volume and the not the extra space . Thanks

Applied Version:

9.5 SP1

Problem Description:

FixWindows.exe action failed after upgrading to 9.5 SP1. When checking the file FixWindows.exe it's already downloaded to the path x:\cba8. And when running it manually from command line console, it's showing the error %C:\boot\bcd does not exist.

Error details:

Action Type = Execute_file

FAILED

error:[8000 1000H]File x:\cba8\FixWindows.exe not found

X:\cba8>FixWindows.exe

retOS=0 osPartitionID=1 osPartitionDrive=

retSystemOS=0 systemPartitionDrive

%c:\Boot\BCD does not exist

Below is the error screen for your reference:

Reason:

When checking the volume information in the CMD console by using the diskpart command, you will notice there are 2 volumes.   One is a 100MB system drive with partiion ID 1.   The other is a > 200GB with partition ID 2.   Both drives have no drive letter assigned.

Resolution:

Add a partition action to assign drive letter C to partition 2 before fixwindows.exe runs.

In the fixwindows.exe action, input 2 in the command-line parameters.  This will refer to the 2nd partition.