Running 2016 SP3
Has anyone out there had a problem where using Legeacy Rom bios setting works fine but UEFI bios settings do not even get the bootx64.wim pushed down?
I have tried 2 different computers. Took a computer that will boot using UEFI at another site but will not Pxe boot here using UEFI.
Tried different network jacks at different locations in case it was a switch or port.
Tried using 3 different designated PXE servers.
I have a case open but not seeming to get anywhere with support.
“Post converted to PDF and attached for Migration.
More details available here: https://community.ivanti.com/docs/DOC-71280”
Hi there everyone,
I'm not sure if I'm posting this in the correct location, but I spent a while working with the guys from LANDesk a while back in order to try and get an Intel NUC to build... it was refusing to build as it would Timeout looking for the Provisioning Template, and as I know I'm not the only one that will have this issue I figured I would put down what I did to resolve the problem, as it could save you a lot of time.
I tried a number of things such as trying to Provision of the OS from PXE boot, a bootable USB and even trying to Provision from an already running Intel NUC (with just the Agent installed).
After a while we changed some settings in LANDesk Management Console for it to look for MAC address instead of serial number, after that was changed the NUC built.
In our setup we don’t want to use MAC addresses to identify the device as we have a number of USB Ethernet Dongles which have the MAC addresses assigned to them, so moving them around machines can confuse LANDesk Management Console.
After finding out that MAC Address worked, I looked around in the BIOS and found that the Serial number, Manufacturer, Product Name and Version were all showing under “Board Information”, however both the Chassis and System Information sections in the BIOS were blank.
Based on that, I looked around online and I managed to find some information where someone had a similar issue with MDT and the NUCs, he explained how he used the "Intel Integrator Toolkit 6.1.8" tool to modify the BIOS in these sections.
I then downloaded the tool from: https://downloadcenter.intel.com/download/26307/Intel-Integrator-Toolkit, extracted the ITK6.UEFI file and saved saved it on to a FAT32 formatted USB.
I needed to get the serial number of the device and some other details, as well as change some BIOS settings,
On my Intel NUC that was achieved by doing the following:
I booted into BIOS (Pressing F2 on Bootup in my case)
I went to the screen that showed the serial number (Image above), and noted down the Manufacturer, Product Name, Version and Serial Number
Then you need to enable the Internal UEFI Shell in the BIOS
Click Advanced
Click on Boot at the top
In the Boot Screen click on the Boot Configuration
Under Boot Devices tick the Internal UEFI Shell box
Save the settings and exit.
Press F10 to Enter Boot Menu
Select UEFI : Built-in EFI Shell
Once your booted into the shell, it’s just a matter of typing a few commands to input the details you want to enter.
I’ve done it a few times now on different NUCS and the second and third time it’s a lot easier as I now know what I am doing, the first time was a little guesswork.
I skipped a number of the settings which I knew weren't needed for my case such as SKU and Asset Tag, but you may want to add these for your situation, you will just need to use SKU or Asset after the -f in the steps below
Below I will be using the following details for an example (changed the serial number), to give you a better idea how it looks
Serial : GERY123456789F8
Manufacturer : “Intel Corporation”
Version : H40999-504
Product : NUC5i5RYB
The commands to type once it's booted and you have changed to the correct drive (usually one of the following drives fs0:, fs1: or fs2:) are below
ITK6 -s -p (this will show you the fields that are empty, you can also run this at any stage to see if your changes have taken place).
ITK6 -s -t System -f Serial -v GERY123456789F8
ITK6 -s -t Chassis -f Serial -v GERY123456789F8
(Replace GERY123456789F8 with your devices serial number)
ITK6 -s -t System -f Manufacturer -v "Intel Corporation"
ITK6 -s -t Chassis -f Manufacturer -v "Intel Corporation"
ITK6 -s -t System -f Version -v H40999-504
ITK6 -s -t Chassis -f Version -v H40999-504
(Replace H40999-504 with your version number from BIOS)
ITK6 -s -t System -f Product -v NUC5i5RYB
(Replace NUC5iRYB with your devices Product name from BIOS)
Note that Product is only used for the System, and not for Chassis like the others do.
Confirm the details you have entered above have all gone in correctly by using the following command
ITK6 -s -p
You should see that the missing fields now have the information entered.
Reboot and confirm again in the BIOS settings.
If so then feel free to turn off the Internal UEFI Shell boot setting in the BIOS, then reboot and provision your machine.
Hopefully this helps those of you that like me have spent hours tearing your hair out it over a simple Provisioning Template timing out on the Intel NUCs.
While I've marked this down as 2016.x, it is likely it affects other versions of the Management Console as well.
This is an unofficial guide to manually creating a disconnected template. It is offered in the hopes it is helpful, but will not be supported by LANDESK support (in whole or in part).
Official Guide How to Create a Disconnected Provisioning Template
Note: This guide was assembled to address an issue where Disconnected Templates can not be created through the console. It is highly recommended you use the official method where possible.
Please Read the LANDESK Share IT Disclaimer
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ApplyDrivers.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ApplyDrivers_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\CaptureImageHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\CaptureImageHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\CaptureProfileHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ClientActionHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ClientActionHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ConfigHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ConfigHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ConfigTargetOSHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ConfigTargetOSHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\CopyFileHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\CopyFileHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\CoreFQDN.dll
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\DeleteFileHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\DeleteFileHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\DeployImageHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\DeployImageHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\DeployProfileHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\DeviceNamePromptHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\DeviceNamePromptHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\DownloadHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\DownloadHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ExecuteHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ExecuteHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\GetFileHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\GetFileHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\HIIHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\HIIHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\imagew.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\imagew_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\imagex.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\imagex_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\InjectScriptHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\InjectScriptHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\JoinDomainHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\JoinDomainHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\LANDesk.ManagementSuite.Diagnostics.dll
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\LANDesk.Provisioning.Business.dll
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\LaunchLdprovisionAsUser.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\LaunchLdprovisionAsUser_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ldProvision.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ldprovision_config.windows.xml
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ldProvision_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ldthumb32.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\MakeBootMedia.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ManageDirectoryHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ManageDirectoryHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\MappedSoftwareHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\MappedSoftwareHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\MaptoPreferredHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\MaptoPreferredHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\melto.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\Microsoft.VC90.CRT.manifest
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\msvcm90.dll
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\msvcp90.dll
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\msvcr90.dll
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\PartitionHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\PartitionHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\PatchHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\PatchHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\PEVerificationFile.bin
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\PKArchive84cb.dll
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\PKArchive88u.dll
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\provcomm.dll
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\provcomm_x64.dll
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ProvisionGUI.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ProvisionGUI_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ProvisioningInterfaces.dll
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\prov_hidecmd.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\prov_updateimg.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\prov_user.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\prov_user_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\RegUpdateHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\RegUpdateHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ReplaceTextHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ReplaceTextHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\SDClientHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\SDClientHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ServiceControlHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ServiceControlHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ServiceInstallHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ServiceInstallHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ServiceRemoveHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\ServiceRemoveHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\SmbShareHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\SmbShareHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\StartTemplateHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\StartTemplateHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\TimeoutApp.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\TimeoutApp_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\unrar.dll
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\unzip.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\UnzipHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\UnzipHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\unzip_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\WaitHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\WaitHandler_x64.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\WindowsRefreshHandler.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\WindowsRefreshHandler_x64.exe
There is an open defect (ID# 349947) where actions that are in the System Configuration section of the template will not continue after the machine reboots from WinPE to Windows. The current workaround is to manually copy the following files to the LDProvison folder on the thumb drive:
C:\Program Files\LANDesk\ManagementSuite\ldlogon\BrokerConfig.exe
C:\Program Files\LANDesk\ManagementSuite\ldlogon\BrokerConfig_x64.exe
Note: The included offline_task.xml contains actions for HII and MappedSoftwareInstallation. Neither of these will work in an disconnected template. Their presence in the xml should not adversely affect anything.
Hello,
Why at the time of integrating the drives during the provisioning, it integrates me of drivers of another other model, so when I assigned my drivers it was good?
For organizations that wish to disable auto win10 updates, the below is a useful hack. However, this does not prevent an end-user from going to System Settings and clicking the button "Check for Updates". When this happens, not only will they receive patches, but v1709 will be installed.
If you wish to prevent users from being able to self apply patches to their systems and only be allowed to be patched from EPM, please follow the following.
Apply the below registry entries and once applied users will see the message below
.
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
"DeferFeatureUpdates"=dword:00000001
"BranchReadinessLevel"=dword:00000020
"DeferFeatureUpdatesPeriodInDays"=dword:00000168
"PauseFeatureUpdatesStartTime"="2018-01-01"
"DeferQualityUpdates"=dword:00000001
"DeferQualityUpdatesPeriodInDays"=dword:0000001e
"PauseQualityUpdatesStartTime"="2018-01-01"
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
"NoAutoUpdate"=dword:00000001
"AuOptions"=dword:00000002
Just upgraded to LDMS 2016.3 and my tech was trying to make sure our provisioning templates for imaging new computers were working correctly in the new version. He attempted to image a computer several times and in the provisioning history it showed that the failure point was the Device Name Prompter action. We figured out that it was actually popping up in the background, hidden by the main provisioning window and the CMD window. In 9.6, the name prompter was displayed on top of all other windows until you enter a name or it times out.
As a workaround, we've extended the timeout period as well as minimizing all other windows at the start of the imaging process so that we can actually see the name prompter pop up.
Is this a known issue? And will it/can it be addressed in a future patch?
I have been trying to get better control with what is copied over using the USMT template that was setup for us when first starting to use the End Point Manager. By "better control" I mean the following
1. Exclude the Administrator and Public profiles from copying over
2. Exclude certain program files from transferring from "C:" and "C:\Program Files (x86)"
My attempts to do this consist of the following
1. Include this syntax in the "command line parameters" within the capture and restore templates
/ue:*\* /ui:testuser
/ue:*\Public /ue:*\Administrator /ui:testuser
Note: Testuser is a domain account and imports properly. Also, I have tried many variations (inverting the /ui and /ue triggers etc.) on this type of syntax. I am also familiar with the notion "/uel" supersedes "/ui" supersedes "/ue"
2. I have included the following type of lines in the MigExclude.xml file within the USMT on our core server and it doesn't ever seem to make a difference. I look at the log and it continues to process items I enter exclusions for with the following format.
<pattern type="File">C:\Program Files (x86)\K-Lite Codec Pack\* [*]</pattern>
<pattern type="File">C:\Python27\* [*]</pattern>
etc. etc. etc.
ist there a way to get am email notification after the deployment has finished. The mail should only contact the user which has started the deployment task. i know there are "Alert Rule Sets" but these can only send to the specified users/user.
I could send a final sendmal command but then i need a deployment username variable.
Regards,
Thomas
I have a problem with HII on the Dell Optiplex 5050.
With four out of ten identical computers, the HII ran smoothly.
Then in provsisioning no USB driver was installed.
(After aborting, the existing driver on the core could be easily installed)
Also the driver assignment in the HII-drivermanagement brought no improvement
Annotation:
Im using Ivanti 2017.3 SU3 (SU5) and i have to use USB-boot - for a variety of reasons
There are ten identical computers, no changes were made to the template or the driver location or otherwise, the drivers are the same from the beginning.
Troubleshooting:
The log files from the HII and Provisioning show that all required drivers were successfully copied to C:\Windows\LDDriverStore\DELL_Optiplex_5050\chipssatz\...
BUT the driver was missing.
Workaround:
Before the step HII in the provisionig template, I now manually copy the USB driver to C:\Windows\LDDriverStore\chipset\...
It is no longer HII, but I can finish the provisioning
Does anyone have an idea what this may be?
and how to fix it?
Hi,
Hope someone can help me with this as I have been stuck for days going through countless guides and documents and still not finding a resolution.
Environment Details
Our provisioning is not going past the 'Configure Target OS' stage. I have followed countless guides in regards to this issue which could be a countless number of things and none have helped.
I have managed to get the 'ConfigTargerOSHandler.log' file and had a look through it(attached below), but unfortunately I cant quite understand what is going on however I did notice one thing in regards to a folder path right at the end of the log "2018-12-20 01:30:33(1588-1868) ConfigTargetOSHandler_x64.exe:Setupcomplete.cmd location: c:\Windows\\setup\scripts\SetupComplete.cmd". That patch is definitely wrong as it has 2 backslashes but I am unsure how to change this and also why its doing that to begin with.
Can you guys help me out, the log file is attached below.
Thanks & Merry Christmas Everyone!
Jose
Hi All ,
we are just looking at rolling out windows 10 using out new core, our plan for provisioning is to have, out windows 10 image, then update to the latest feature pack during provisioning.
there is a system configuration option for windows 10 update, where you point it to the latest ISO and it works. The problem being it expecting a UNC Path. it there anyway of getting this to use the preferred server (as there is no preferred server option mentioned)
This document provides the steps necessary to capture a Windows 10 image using IMAGEW.EXE v2 for use in a provisioning template. The screenshots and steps in this document show Windows 10 but the same steps will work for Windows 7, 8 or 8.1.
1. Open the Operating System Provisioning tool in the LANDESK Console by clicking Tools | Provisioning | OS Provisioning.
2. In the Operating system provisioning tool, click on the All my templates folder.
3. Click New Template and select the Capture Template option.
4. Enter a name for the template.
5. Enter a description for the template which is optional.
6. Select LANDESK ImageW V2 for the Image Type.
7. Enter the UNC path including the filename to the location where the image file will be saved. The filename extension will be .tbi.
8. If the image share does not exist, create it before trying to capture the image. You will also need to setup a preferred server for the computer where the image share is located if it has not already been done. Following Community article has information on setting up preferred servers:
How to configure the Preferred Server (Target) for Content Replication
Note: You must have Write Credentials specified in the preferred server section, the account used must have modify rights to the image share in order to capture the image.
9. Click Create.
10. The template created will show up in the Operating system provisioning tool under All my templates.
If PXE representatives have not already been installed, install a PXE representative on the same subnet as the Windows 10 computer. Instructions for installing PXE representatives is available in the following Community article:
How to configure Self Electing PXE services in LDMS 2016.3 or higher
Note: PXE representatives cannot have multiple NICs/LANs and they cannot have WIFI.
1. Install Windows 10 on a computer or get a computer that already has Windows 10 installed. Make sure the LANDESK Agent is not already installed on the computer or it will need to be removed before capturing the image.
Note: Install the OS on the smallest partition possible so it can be deployed to as many different hard drives in the environment. ImageW captures all partitioned space and will only deploy to hard drives big enough to hold the captured partitions. It will expand the last partition to fill the drive if there is free space left over.
2. After the OS is installed, configure the OS with any Company requirements.
3. Install all OS patches currently available because this will save time in the long run so that the computers do not have to be patched later.
4. Install all applications that are common for all users in the company that this image will be deployed for their use.
SYSPREP.EXE is located in the Windows\System32\Sysprep folder on the Windows 10 computer.
For use in LANDESK, the computer can be sysprepped in Audit mode without the Generalize box checked or it can be sysprepped in OOBE mode with the Generalize box checked.
Select the options for sysprep then click OK to run it. When sysprep is complete, the computer will shutdown.
Note: Do not let the computer boot into the OS until after the image is captured or you will have to run sysprep again.
1. In the LANDESK Console, expand Configuration.
2. Right-click Bare Metal Devices and select Add Devices.
3. In the Add bare metal device window, select MAC address for the Identifier type from the drop-down list.
4. Click the Add button.
5. In the Bare Metal Device window, enter a name for the device in the Name box. Name it whatever you like because the name does not matter for the capture.
6. Make sure the Identifier type has MAC address selected then enter the MAC address of the Windows 10 computer in the Identifier box.
7. Click the Add button.
8. The MAC address will show up in Server identifiers. Click OK.
9. The computer added will show up in the Add a bare metal device window. Click OK.
10. The computer added will show up in the LANDESK Console in the Configuration | Bare Metal Devices folder after the LANDESK Inventory Server service processes it.
1. Drag and drop the Bare Metal device on the Capture Template that was created previously.
2. Click Save.
3. Right-click the task created in the Scheduled tasks tool and select Start now | All.
4. Expand the task and click on All devices under the task.
5. Give the task a minute to completely initialize and verify the task Status shows Waiting.
1. Network boot the computer. Refer to the computers documentation, if you need help with how to network boot the computer.
2. WINPE is downloading from the PXE representative. The IP address shown is the IP address of the PXE representative that the client is communicating with which is useful to know for troubleshooting.
3. WINPE has finished downloading and is now initializing to run the template.
4. The provisioning template is running.
5. ImageW is now running and capturing the image.
6. When ImageW finishes, it will report a success or failure. Hopefully, it will report a success as shown in the screenshot above. The template progress window will only remain open for short time before closing. Check the status in the scheduled task to make sure it was successfully.
This document is intended to cover the newly added feature of Conditionals in LANDESK Provisioning. Conditionals are best used to consolidate templates, allowing flexibility for:
In this case, a default Deploy Template will be customized using Conditionals. To create such a template, browse to Tools>Provisioning. In the Operating System Provisioning tool, clickNew Template>Deploy Template.
Fill out the required fields and clickCreate.Should look something like this:
Right Clickany of the actions, and selectAdd Condition> If or Else
In LANDESK 2016, a new action type was introduced called Compare Variable. This action is extremely useful when using conditionals in provisioning. The following is an example of where to use this new feature:
We have an Image for Laptops and an Image for Desktops. How do we utilize both images in one Template?
This scenario will use the same template created above. The first step in using conditionals is to find a characteristic that LANDESK can use to differentiate between devices. LANDESK Inventory yields a different value for Desktops and Laptops.
For this example, we have "Chassis Type" recorded as NoteBook and Mini Tower. These values can be used as conditional arguments using Public Variables.
To add "Chassis Type" to public variables, open the Operating System Provisioning tool and select theTools drop-down list from the toolbar. Then select Public Variables.
Select Add. Enter any Search Value that seems fitting - needs to be one word. The Type will be set to "Database value." The replacement value will be set to the entry in inventory; "Computer"."System"."Chassis Type"
SelectOK.
Open the properties of the base template created above and right click the OS installation section from the Action List. Select Add Condition> If.
Right click the newly created condition and select Add Action. Select Compare Variable in the "Type" drop-down list. Select the variable created above in the "Variable" drop-down list and enter Mini Tower in the blank space. Click Apply.
Right Click OS installation once more and select Add Action. Select Deploy Image from the drop-down list, name the action appropriately, and click OK. Fill out the action properties to deploy the desktop image.
Now do the same with the Notebook image, only this time use an Else conditional. It should look something like this:
Hi,
I'm new to LD imaging and wanted to know how to rename a PC during LanDesk provisioning. the organization I work for currently only used scripts (powershell and VB) and an access database to handle post imaging tasks. I'm in the process of getting away from those. attached is a snip of the task that I am trying to run. I read somewhere that the action to use is the device name prompter and to insert it once the image conveys (not sure if that's true so I wanted to know if I can tell the PC to do that at the start of the image). for my second question I am trying to have my template install several programs (like Mcafee and Global Protect), how would I mod my template to handle these post-imaging actions? apologies for what could very well be a basic inquiry and any feedback is appreciated!
Hi,
the idea of automatic download of drivers from the manufacturer is great. (Even greater if .cabs released by manufacturers would be up to date, but thats something else...)
But the function is not very well implemented I think.
If I am not mistaken, it is not possible to limit the download to that packages necessary for used OS - all versions are downloaded even XP if available.
Ok, I could live with that.
But why are old versions downloaded? And why arent even those deleted, which would not be downloaded any more?
Is there any file or table where data about the downloaded drivers are stored from where you could build a cleaning job?
Regards
Marco
OS Deployment template actions are failing. To determine the cause of the failures it's helpful to take a look at the log files, but WinPE is loaded onto a RAM drive and the logs disappear when the device reboots. If you log a support case, Ivanti support will ask you for these logs.
When you start a provisioning template, the computer boots into WinPE and will stay in WinPE until you get to the Configure Target OS action. After CTOS, the computer reboots and all logs and files generated in WinPE are lost. We need to pause the process prior to the CTOS action. Edit your template and insert a wait action just prior to CTOS. Specify a wait time in seconds. Usually 600 seconds (5 minutes) is sufficient.
Run your template again, and view the computer you are provisioning. If it's a remote computer you can use Ivanti Remote Control to view the WinPE environment. If you are on Ivanti EPM 2018.1+. you can now remote control UEFI PXE Boot devices from the console from the right click menu on the devices record.
Open a console window to locate and copy the logs to a remote computer:
xcopy *.log E:
Each OS Provisioning template action has a log file. In addition, the overall template process has a log, called "ldprovision.log". This should be your first stop. Open the log file and scroll through. You are looking for a section of the log similar to this:
2015-04-17 14:35:38(1404-1408) ldProvision_x64:********************************** Begin processing actions **********************************
This indicates the beginning of the template actions. You will see the start of each action called out in the log similar to this:
2015-04-17 14:35:38(1404-1408) ldProvision_x64:********* Begin an action - Map_toPreferred
You will also see that each action has it's own action handler. You will see the ldprovision.exe action handler calling additional handlers, similar to this:
2015-04-17 14:35:39(1404-1408) ldProvision_x64:Launching action handler [MaptoPreferredHandler_x64.exe] with parameters ["]
2015-04-17 14:35:39(1404-1408) ldProvision_x64:handler launched.
At the end of each action you will see an indication of success or failure, and then the next action starts. Keep in mind that some actions show failed but do not affect the success of the entire template. For example the vboot action, or in some cases HII may show failed but the template can continue and ultimately succeed. Locate the failed action that you are troubleshooting. Each action handler has it's own log file, so next pull up the log for the specific action handler that failed. If the name of the handler is "myactionhandler.exe" the log file will be "myactionhandler.log". If you have difficulty identifying the failed action, press CTR+F to open the Find box, and search for "failed".
The log file specific to the action which failed will give you greater detail into the cause of the failure. You will also see a failure error code. Sometimes these codes can be very generic, other times they are quite specific. Search the Ivanti community for your failure reason and error codes and you should find discussions and documents that help you resolve the failure. If you are not able to determine the cause of the failure, log a support case with Ivanti and provide the log files on your support request.
Hello,
I come to you with interesting OS provisioning failure. So let's start with presenting the configuration that I have:
LDMS version = 2016.3 SU02 on windows server 2012 R2 datacenter
Computer to install = DELL Precision 5510 with DELL TB16 (so the network cable is connected to the DELL TB16 and not directly to an RJ45 interface in the laptop)
Now time for describing the issue:
So we are testing the OS provisioning via LANDesk on a new DELL model which uses DELL TB16 (Thunderbolt 3 dock). The WinPE was successfully loaded and start to proceed the script "startnet.cmd" to load integrated drivers, check network connection and many other customized steps. Drivers were successfully loaded and WinPE get an IP address. One of these steps that I have mentioned is to create a folder under X:\ named "ldprovision" then use a CBA8 component called HTTPCLIENT.exe (under X:\CBA8\) to download ldprovision.exe from the core server to the folder "ldprovision" using HTTP
below is the command used:
httpclient -f ldprovision.exe http://%corename%/LdLogon/Provisioning/Windows/ldProvision.exe
Directly after this command the startnet.cmd will execute the executable file "ldProvision.exe" and here we get the error window (see picture in the attachment os_prov_error2.jpg)
After many hours of troubleshooting I found out that the root cause of this issue is that ldProvision.exe wasn't fully downloaded and when "startnet.cmd" reach the step where it launchs this executable file it fails because it is corrupted.
From WinPE I mapped a share to //%corename%/LdLogon/Provisioning/Windows/ and I tried to download this executable file by myself and guess what ... I had the same issue the download always fails to fully download "ldprovision.exe".
I checked the IIS log maybe I find some details and I found that everytime the HTTPClient try to download "ldprovision.exe" usgin HTTP Get method a new entry is added to the log file (see below):
2017-03-08 13:21:53 10.10.1.87 GET /LdLogon/Provisioning/Windows/ldProvision.exe - 80 - xxx.xxx.xxx.xxx - - 200 0 995 21374
so as you can see there is the windows error code 995 (sc-win32status) in the final HTTP Status (just after 200 0). The error description is : The I/O operation has been aborted because of either a thread exit or an application request. when I googled this error code most of web page refers to C# or ASP.net error related to closed sockets.
Does any one of you guys is using DELL TB16 or Thunderbolt 3 Dock and did he was able to provision it via LANDesk.
Thanks
This document is intended to show the versions of WinPE used in each version of LANDESK Management Suite. The goal is to facilitate getting the correct drivers for the WinPE version being used. Note, these drivers refer to drivers such as Storage or Network Card drivers in order for the Windows PE (Windows Pre-Execution) environment to be able to see the hard disk and access network resources. This is not related to the drivers that will be on the target operating system if booting into Windows PE for imaging a final OS is an objective.
If you upgrade your LDMS version or apply a service pack, your WinPE version will be updated as well. The WinPE image in contained in the boot.wim and boot_x64.wim files on your core and on your PXE reps. If you upgrade your LDMS version but do not redeploy your PXE reps they will have an older WinPE version. If you are unsure which version is running within WinPE you can open a console and type "ver". This will return the version in x.x.xx format. Match this up to the WinPE version using this chart:
| WinPE Version | PE Version | Derived From |
|---|---|---|
| WinPE 1.5 | 5.1.x | Win XP SP2 |
| WinPE 2.0 | 6.0.x | Vista |
| WinPE 3.0 | 6.1.7600.x | Windows 7 |
| WinPE 4.0 | 6.2.x | Windows 8 |
| WinPE 5.0 | 6.3.x | Windows 8.1 |
| 10.0.10240.x | 10.0.10240.x | Windows 10 1511 |
| 10.0.15063.x | 10.0.15063.x | Windows 10 1703 |
Note: WinPE 10 and Windows 10 share the same version number as part of Microsofts "One Windows" policy. It is included in Windows ADK (Windows KITS 10)
To find out exactly what PE version you are on, from within a Command Prompt in Windows PE you can look at the following registry key: HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinPE
The following Microsoft document describes what NDIS driver versions are required for each OS:
We have noticed that our Windows 10 ImageX image fails to apply on hard drives that have never had an OS installed. Is there a way to resolve this issue? Here is the DiskPart commands we are using to prepare the hard drive for the image. If we apply our Windows 7 ImageW image to the drive first then we can use the ImageX image without issue.
Thanks
x:\windows\system32\diskpart.exe /s X:\win10_UEFI.txt
win10_UEFI.txt:
select disk 0
clean
convert gpt
rem == 1. System partition =========================
create partition efi size=500
format quick fs=fat32 label="System"
assign letter="S"
rem == 2. Microsoft Reserved (MSR) partition =======
create partition msr size=128
rem == 3. Windows partition ========================
rem == a. Create the Windows partition ==========
create partition primary
rem == b. Create space for the recovery tools ===
shrink minimum=1000
rem == ** NOTE: Update this size to match the size of the recovery tools (winre.wim) plus free space **
rem == c. Prepare the Windows partition =========
format quick fs=ntfs label="Windows"
assign letter="C"
rem === 4. Recovery tools partition ================
create partition primary
format quick fs=ntfs label="Recovery tools"
assign letter="R"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001
list volume
exit
