HI

i was wondering if i am the only one who are experiencing slow boot image / PXE /TFTP download from all my clients?
Im only getting arround 14 Mbit pr client. :S
i have tryed several things to speed up this process, but all the articles are related to Microsoft SCCM.

http://windowsdeployments.net/how-to-speed-up-pxe-boot-in-wds-and-sccm/

I tryed modifying the BCD file with the RAMDISKTFTPBLOCKSIZE + Windows size , with no luck, also tryed the NIC card thingy changing the bugger size ( cant remember link)

But all this without luck.

Im running Server 2008 ENT R2 REpository server and Server2012 Core server.
And Gigabit all the way to my clients witn no load on the network

Is there not any ways to speed up this tftp download process??
I cant find any refferences on the net discussing this , only one from year 2008, wich is outdated now.

Any help would be appriciated

I am trying to create a disconnected template and it is failing on making the USB drive bootable.  I have tried this on 2 machines with the remote console with both a 128 G and 8 G USB stick.  I have the 9.6 SP1 console on a Win7 x64 machine and an Win8.1 machine.

Checking the provisioning.log on the remote console machine, it shows this error:

ERROR POfflineProvisiong  1/20/2015 4:00:21 PM  : Could not make format USB.

ERROR POfflineProvisiong  1/20/2015 4:00:53 PM  : Could not make USB bootable.

Any idea why this may be happening?

Hi all, got a couple of questions..

1. Trying to figure out which format to be deploying our images in, TBI or WIM format and wether to use ImageW v2 or ImageX??

Can anyone point me the right direction, is TBI faster than WIM when deploying roughly same size files?

What are the benefits/drawbacks if any of both?

2. From my main provisioning template i can run another template, but is it possible to get it to return to the main template and carry on from where it left off? - If so how ?

Currently running - 9.6 SP1

Thanks in advance!

Geoff

Hi

We here found a limit in the PXE tftp server. We can only transmit the boot image to arround 50 clients at the time, the next client will recive this error:
pxe tftp: No slot is empty to process this client's request.

We are running landesk V 9.6 SP1
Is there any way you can incresse this number ?
Or is this limitation unchangeable?

Hi

Have anyone experienced this error while OS provisioning machines in their enviroment?

dhcpv4 client service is stopped. shutdown flag value is 1

This happens at random stages in our deployment templates, suddently after  a restart step the client boots up to continue the install progress, but without an ip address, and therefore is in a Zombiemode.

The client cant report back that it is failed, and it cant continue.

So it just remains as active in the LDMS console.
The error is from the windows Eventlog, and i can see in the device management that the Network card is disabled in WINDOWS S very strange problem i think.

i Am running Landesk MS 9.6 SP1

Windows 7 SP1  X64 - with latest Microsoft updates until this date ( 20-01-2015)

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 .

HI,

I am having two issues.

The devices i am trying to image are Dell Z90 Windows 7 Embedded Standard - 32 bit operating system units. which have been fully customised for our needs.

oh and the unit as a UEFI  64bit bios with no way to turn it off.

1.) I am trying to capture an image using LANDESK ImageW V2.

• The unit starts up and starts winpe just fine,
• connects to the server and launches the task.
• locks the C: Drive.
• fails to lock c drive and asks me if i want to force the lock.. i said yes force and tried to push the image and same error when pushing the image to a device

So i tried to run the imagew task manually and capture the output to a log file  and here it is.

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

[11/25/2014 12:00:18 PM] Image for Windows 2.90 (GUI)

[11/25/2014 12:00:18 PM] Starting ...

imagew.exe /b /d:w0@0x1,0x2 /f:"\\10x.xxx.xxx.xxx\ImageRepository\capture" /v

[11/25/2014 12:00:18 PM] Unable to obtain a lock on drive C:

Please ensure that PHYLock was installed and has not been disabled.

For troubleshooting information visit www.terabyteunlimited.com/kb/article.php?id=340

[11/25/2014 12:00:25 PM] Deleting incomplete or failed backup.

[11/25/2014 12:00:25 PM] Operation Completed with Error Code 68

[11/25/2014 12:00:25 PM] Stop

2.) Sometimes while booting off the usb (to start the provisioning.) (i cant do PXE booting here in the office - image sample attached.)

• winpe loads, resolves the core server name
• downloading prerequisites....
• Action #1
• Vboot
• FAILED
• error:[5H]An unknown error occured. if the problem persists, contact the LANDESK administrator

this one has me completely stumped

3.) renaming the device fails.

any help would greatly be appreciated.

Can someone please tell me if this is a bug or is it by design?

We can see the SCN file get created under the \\coreserver\ldlogon directory but the bare metal server never gets committed to the database. The same process works fine adding it from the core server.

All,

I am trying to setup provisioning within LANDesk and have hit a stumbling block CTOS! ..

I have read almost all forums posts regarding this action and I just cant work it out..

CTOS seems to not get passed the "Running" stage (because it hasn't received a inventory scan from the system)

I can confirm the following:

- The ldprovisioning folder is in the C:\

- The  ldprovisioning.cmd is in the ldprovisioning folder on the C:\

- The unattend.xml file has been populated with <Path>cmd /c %%systemdrive%%\ldprovisioning\ldprovisioning.cmd</Path>

- The location %systemdrive%\ldprovisioning\ldprovisioning.cmd is valid

- Running the ldprovisioning.cmd manually installs the LANDesk agent to continue

What seems to not be working is the running of the ldprovisoning.cmd script automatically which I don't understand as its in the unattend.xml

Can anyone suggest any steps to resolve? I know its not "strictly" LANDesk but its still a LANDesk process that's failing.

Thanks for any help - I am running LANDesk Ver 9.0 SP2 and I am deploying Windows 7 - The properties are set to "Windows 7" also.

Oliver

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.

Hi all,

I am a new LANDESK user (currently in the trial), and I need a bit of help/advice regarding OS Provisioning.

I have built a template which successfully deploys the image and inject's the unattended file but gets stuck on the Configure Target OS stage.

After the image is deployed on the target PC and the unattended file is successfully injected, the PC reboots but the sysprep process does not kick in.  It just returns to the CTRL+ALT+DEL logon screen.

Is there anything obvious I am doing wrong at this stage?

Thanks all

Applies to LANDESK Management Suite 9 SP3 and newer

Description

OSD.Upgrade.exe is run during the installation of a LANDESK Service Pack or any LANDESK patch that updates the WinPE image (boot.wim). It is responsible for configuring the image to function on a specific Core Server and migrating WinPE drivers from the boot.wim.bak into the new boot.wim. If OSD.Upgrade.exe fails, one or more of these steps may not be completed. This document will walk through re-running the OSD.Upgrade.exe installation step on the core server.

During the Service Pack or patch installation there may be a failure with the OSD.Upgrade.exe process. The install error may be similar to CommonCore.inf: (0xFFFFFFFF) OSD.Upgrade.exe,60000.  Review the osd.upgrade.exe log file found in C:\Program Files (x86)\LANDESK\ManagementSuite\log to get more specific information about the error. If desired the osd.upgrade.exe.log file can be renamed prior to running osd.upgrade.exe again to make current errors easier to find.

A common cause for this issue can be that one of the .WIM files is already mounted from a prior process or through manual intervention by an administrator.

Common Errors and Resolution

• Error: "Access Denied"
  • Errors referring to access denied indicates that a folder path in the boot.wim is too long. Often this path will be for a driver that was injected into the WinPE image. There are two option for correcting this error. The first option is to just start with a clean boot.wim and add the necessary drivers after completing the OSD.Upgrade.exe process. In LDMS 9 Service Pack 3 the WinPE boot environment requires Windows 7 32-bit drivers. Updating those drivers is a manual process so starting with a clean boot.wim may be a good option. The second option would be to mount the backup of the boot.wim (boot.wim.bak) and rename the directories in the InstalledDrivers directory to use shorter names. After completing one of these options follow the steps outlined below to re-run OSD.Upgrade.exe.
• Error: "CommonCore.inf: (0xFFFFFFFF) OSD.Upgrade.exe,60000"
  • This is a general error indication. Review the log for additional errors.
  • Check to make sure the boot.wim is not mounted on the Core server.
• Error: "DirectoryNotFoundException"
  • Errors referring to a .0 or an mpkg package indicate that a .0 file has been extracted to a sub-folder of the ldlogon folder. DO NOT delete any .0 files from the root of ldlogon. Navigate to the directory specified in the log (i.e. C:\Program Files (x86)\LANDESK\ManagementSuite\ldlogon\mac) and delete the .0 file. To prevent additional errors when re-running OSD.Upgrade.exe delete any additional .0 files that are found in sub-folders of the ldlogon folder leaving only the .0 files in the root of ldlogon. Follow the steps below to re-run OSD.Upgrade.exe.
  • Errors referring an ALL.REG file indicate that the wim file was still mounted when osd.upgrade.exe tried to execute. This is most likely due to errors in the previous attempt at running OSD.Upgrade.exe. Review the log and correct and additional errors found before following the steps below to re-run OSD.Upgrade.exe.
• Error Non-fatal error: FilterUnload failed, hr=0x801f0013
  • This is normal and does not indicate a problem. Continue reviewing the log file for additional errors.
• Error: System.ComponentModel.Win32Exception
  • You are running the process as a restricted user. Either log in as an administrative user or right click OSD.Upgrade.exe and select run as administrator.
    • Make sure that you are either logged directly into the core server or using Remote Desktop with a /admin switch as a full administrator.
      
• Error System.IO.IOException: Element not found.
  • This error indicates that there is still a wim file mounted. Review the log for additional errors prior to this error. Follow steps below to re-run the OSD.Upgrade.exe process.
• Error System.UnauthorizedAccessException
  • This error indicates either that there is still a wim file mounted, or that the bootmedia.wim.bak already exists. Bootmedia.wim.bak can be deleted as long as bootmedia.wim exists. Review the log for additional errors and then follow the step below to re-run OSD.Upgrade.exe.
• Error WAIK is not installed
  • This is normal and does not indicate a problem. Waik should have been uninstalled prior to upgrade. If Waik is installed, uninstall it. Continue reviewing the log file for additional errors.

Preparing to Re-Run OSD.Upgrade.exe

After reviewing your errors and completing the steps above perform the following steps:

1. Start an administrator command prompt (right click the command prompt and select run as administrator).
2. From the command prompt navigate to C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot.
3. Run the following command:
   
   DISM.EXE /Get-MountedWimInfo
   
   • The command should list all images that are currently mounted. There are instances however where a mounted image will not be listed. Check for the existence of the folder original_boot_wim and/or new_boot_wim in the C:\Users\logged in user \AppData\Local\Temp\imgtmp\ directory.
     
     
4. For each image listed and all folders found in the imgtmp directory listed in step 1, run the following commands:
   
   
   • DISM.EXE /Unmount-Wim /mountdir:"c:\path to dir(s) found in previous step" /discard  Where mountdir is the mount path listed from the dism.exe /Get-MountedWimInfo command or the folders specified in step 3.
   • DISM.EXE /Cleanup-Wim
   • Ensure that each unmount command completes successfully
   • Any errors that DISM may encounter will be logged in the %windir%\Logs\DISM directory.  (For further information see Understanding Failures and Log Files)
5. In Windows Explorer open the C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot directory.
   
6. Rename the existing boot.wim to boot.wim.bad.
7. Copy the backup boot.wim (the one from prior to upgrading) from C:\Program Files (x86)\LANDesk\ManagementSuite\backup\PatchName\ to the C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot directory.
   • If access denied errors occurred with drivers and a clean boot.wim file is desired, use the file listed in step 9 below.
8. Rename the restored boot.wim file in the vboot directory to boot.wim.bak.
9. Copy the boot.wim file from the installation package \image directory to the \vboot directory. You should now have a boot.wim and boot.wim.bak (either your backup or an additional copy from the patch) file in the vboot directory.
10. Run the OSD.Upgrade.exe from C:\Program Files (x86)\LANDesk\ManagementSuite\. This should take a few minutes to complete. If it exits quickly it is likely that there are additional errors.
11. Review the OSD.Upgrade.exe log found in C:\Program Files (x86)\LANDesk\ManagementSuite\logs to see if any additional errors were encountered. If additional errors were encountered, you must resolve each one and after resolving re-run OSD.Upgrade.exe.
12. If this still does not resolve the issue check "HKLM\SOFTWARE\Microsoft\WIMMount\Mounted Images" and remove any values in the key.

After OSD.Upgrade.exe has completed successfully you need to redeploy your PXE reps. Instructions for PXE deployment can be found at How to deploy PXE Representatives(step-by-step screenshots)

When a client machine boots into WinPE open a console to confirm the upgrade. The  version shown in the console should be 6.1.7601 or higher.

This article applies to LANDESK Management Suite 9.6

Issue

The option to install software using the "Run From Source" download option was not available in previous versions of LANDESK Management Suite.

This feature is now available in LANDESK Management Suite 9.6 Service Pack 1

Resolution

1. Download Service Pack 1 for LANDESK Management Suite 9.6.
2. Install on Core Server and Remote Consoles.
3. Open the Agent Settings Tool under the Configuration or Security and Compliance tool groups.
4. Select Distribution and Patch Settings under the section you want to modify (Either My Agent Settings, Public Agent Settings, or All Agent Settings.
5. Under Distribution-only settings select Download Options.
6. Select the "Run From Source" download option.
7. If including the Distribute Software action in an "end to end" Provisioning Template (Installing the OS, followed by the agent, etc) you will need to assign the configured Distribution and Patch Setting to the Agent Configuration you are including in your template.

Issue

Imaging a device with a LANDESK Management Agent installed can cause the devices that receive the image to overwrite each other in the database.

Cause

LANDESK inventory looks at a Unique ID/Device ID when inserting the scan. This ID is created when the agent installed on the device.

Resolution

It is strongly recommended that the LANDESK agent not be included in an image.  The recommended way to install the LANDESK Agent with imaging is to use LANDesk Provisioning and include a Configure Agent action in your provisioning template.  Besides causing duplicate devices, the LANDESK agent is often updated and adding it to the image will quickly cause your image to be outdated. 

If the agent must be included in an image or Non-Persistent VDI image, the unique identifiers must be deleted out of the registry prior to the capture of the image.  Before creating an image of the machine do the following:

LANDesk Mangement Suite 9.0 and later

1. Install the LANDESK agent, then STOP all LANDESK related services
2. Delete the following Registry Keys for 32bit clients:

           HKLM\SOFTWARE\Intel\LANDesk\Common Api\UniqueID
          HKLM\SOFTWARE\LANDesk\Common Api\UniqueID

          HKLM\SOFTWARE\LANDesk\Inventory\LogonHistory\Logons
          HKLM\SOFTWARE\LANDesk\ManagementSuite\WinClient\SoftwareMonitoring\MonitorLog contents

          Delete the following Registry Keys for 64 bit clients:

          HKLM\SOFTWARE\Wow6432Node\Intel\LANDesk\Common Api\UniqueID

          HKLM\SOFTWARE\Wow6432Node\LANDesk\Common Api\UniqueID

          HKLM\SOFTWARE\Wow6432Node\LANDesk\Inventory\LogonHistory\Logons

          HKLM\SOFTWARE\Wow6432Node\LANDesk\ManagementSuite\WinClient\SoftwareMonitoring\MonitorLog contents

     3. On Windows XP delete C:\Documents and Settings\All Users\Application Data\LANDESK (delete the entire directory and subdirectories)

     4. On Windows 7, 8, and 8.1 delete C:\ProgramData\LANDesk (delete the entire directory and subdirectories)

     5. From the command line (as administrator) in the \LDCLIENT directory run the following

"clientdbutil.exe /create"

     6. Verify that a new database, (LDClientDB.db3) was created in the same path as you deleted above

In addition it is a good practice to ensure that the image does not contain any DRIVERS.DB3 file.

See Community discussion for additional tips and information:

http://community.landesk.com/support/message/61210

Applies to LANDESK Management Suite version 9.5, 9.5 SP1 and newer

How to Manage Drivers in WinPE for LANDESK Management Suite 9.5

Description

In order to perform imaging in LANDESK Management Suite the WinPE image used during the imaging process must contain drivers for devices such as the network adapter or hard drive controller.

In LDMS 9.5 additional drivers for Intel network cards, Intel hard drive controllers, and Intel USB3 have been included in the WinPE image for convenience.

The drivers for the WinPE image should match the version of the network boot image file being used (32-bit for boot.wim and 64-bit for boot_x64.wim), not the OS being deployed.

For adding drivers in LANDESK Management Suite 9.0 see How to add drivers to WinPE for LANDESK 9.0

Additional information about the WinPE version and required driver versions for each version of LANDESK Management Suite can be found at
WinPE Version Information by LANDESK Management Suite Version

Resolution

To manage drivers to the WinPE image for 9.5 use the following steps.

1. From the console go to Tools > Distribution > OS Deployment.

2. On the Operating System Deployment screen select “Manage the drivers in the WinPE Image.

3. Select the WinPE Image that you want to manage drivers in. The default selection (boot.wim) is the WinPE image used for 32-bit vBoot and PXE.

4. To manage drivers in the 64-bit WinPE image select "Others (For user specific image)" option. Browse and select the boot_x64.wim in the vboot directory where the default boot.wim is located.

5. The image file will be processed to open the WinPE image and gather the list of drivers currently in the WinPE image file.

6. Select add or remove to manage drivers.  Note: Drivers that were included by Microsoft in the WinPE image cannot be removed. If the driver list is blank it indicates that the image file is mounted by another process and must be un-mounted before drivers can be added.You can do this by typing imagex /unmount in the command line. If nothing unmounts or this does not resolve the issue, check console.exe.log for an error in deleting a temporary file. (Path example, C:\Users\ldadmin\AppData\local\Temp\2\imgtmp\Apply) Navigate to this file and rename it. The image should open now and you should see all of the drivers and be able to add them as well.

7. When adding a driver a driver name must be provided. Using a name that easily identifies the driver and hardware is recommended for ease of use as additional drivers are added and removed. Browse to the location of the INF for the driver. Note: The driver must match version of the OS in the WinPE image, not the OS being deployed. The driver for the boot.wim must be a Windows 7 32-bit driver. The driver for the boot_x64.wim must be a Windows 64-bit driver.

Note: For LDMS 9.5 SP1 with later component patches, WinPE has been updated to version 4.0 based on Windows 8, and in Service Pack 2 it is updated to WinPE 5.0 based on Windows 8.1.    Windows 8 drivers should be used in this case.

8. After the necessary drivers have been added, select Finish and the drivers will be injected to the image.

9. After the image has completed processing it is necessary to update existing PXE representatives. Instructions on updating PXE representatives can be found atUpdating the WinPE image on PXE representatives

Hi,

I'm quite new to Provisioning so i might be doing something dumb.

I'm getting an error at the deploy image task of provisioning.

I was having this issue yesterday and i played around with a few settings and managed to get it working.

But now its failing again?

The HTTP authentication test is failing on the core as well? - Not sure if this was working yesterday, but the image process did work for 1 PC.

I have checked out landesk service account and permissions but none of that has changed since yesterday so i cant understand why its doing this.

Any assistance or suggestions would be greatly appreciated as I have been looking at this for too long new and im a bit brain dead.

Thanks,

Nathan

I'm running 9.6 SP1 on a test network trying to capture a Windows 7 64bit image. Do I need to need to set up a Preferred server or am I fine with just the Core?

We have a profile capture / profile restore provisioning template, before 9.6 SP1 we were able to right click on the provisioning template and select schedule task. Once the task was scheduled it was always a policy push and when we dropped a machine into the task and started the task it would run. Now when I create the task it shows up as a policy and we cant change it. I have attached a screen shot of what we are seeing. I have been working with Landesk support and they don't have any ideas. Please help

I have been fighting with this intermittent issue and spending way too much time on it.  It is maddening since it will fail 3 times in a row and then succeed without any modifications whatsoever on the same hardware. 

What is happening is that after the generalize pass of the sysprep run, it will install device drivers and then move onto applying system settings where it fail to parse the unattend.xml at C:\Windows\Panther saying the answer file is invalid.  Looking at the unattend file, it will be truncated at the line stated in the error message. 

I have tried injecting the unattend into the root of the drive, into C:\Windows\Panther with the same result.  I have put waits in the provisioning template after the inject to ensure that it is being written completely.  Looking at the unattend file before the generalize pass shows that the file is intact. Looking through the sysprep logs yeilds no clue as to what is happening.

I generated the unattend file with Windows Systems Image Manager and is attached below.  I am on LD 9.5 SP2 trying to provision Windows 7 Enterprise SP1 x64.

Anybody know what is happening to the unattend and any suggestions on making this more reliable?

Hi all,

Landesk newbie here, currently experimenting with OS Provisioning.

I am trying to get a Dell Optiplex 3020 to install its video driver, but what I am finding is that the driver is being UN-installed as part of the process and I am ending up with the standard VGA driver.

I have tried assigning both the .inf and driver package, but it always seems to revert back to the standard VGA adapter.

I even tried installing the setup.exe for the driver package as part of the system configuration phase of provision, but it fails and just displays a red cross error windows.  If I run the setup.exe manually, it works without a problem.

I am not sure if it matters, but the image I am using already contains the Optiplex 3020 drivers, so its a bit strange the way it decided to uninstall it and default back to the standard VGA adapter.

Any ideas?