Guys, I got stucked with our Win 10 Deployment. The Office 2016 distribution package doesn´t continue within the Win 10 Provision template. It doesn´t abort, it downloads all the files and holds on. It stays till I kill the provisioning task. The software package as a standalone task works.
Anyone with similar experience or even a solution?
I attached some of the logfiles, the office 2016 package ID is 374.
Hi,
I am running on weird situation I never saw before. The Windows PE is loaded successfully and the startnet.cmd script is running until it reaches the step "A subdirectory or file \ldprovision already exist". Normally the provisionin GUI should start now but it is not the case. It will take too much time (more than 10 minutes) before it is displayed and the problem is it shown no provisioning actions.
I made a dummy template on which I have added just 1 provisioning action which is wait(xx). and I tried on the same device and I got the same behavior. I deleted the device and import it again and I am still seeing the same weird behavior.
I don't think that it is a general problem since some other devices were able to finish successfully provisioning tasks!!
From the core server I checked the follwing log files :
VERBOSE ProvisioningWebService 3/12/2018 11:12:07 AM : Identifiers to use - Mac Address: True, Serial Number: True, AMT GUID: True
VERBOSE ProvisioningWebService 3/12/2018 11:12:07 AM : Identifiers:
VERBOSE ProvisioningWebService 3/12/2018 11:12:07 AM : MACAddress: XXXXXXXXXXXX
VERBOSE ProvisioningWebService 3/12/2018 11:12:07 AM : SerialNumber: XXXXXXX
VERBOSE ProvisioningWebService 3/12/2018 11:12:08 AM : Returning task XML
DEBUGGING TemplateFinder 3/12/2018 11:12:07 AM : GetProvisioningTaskForComputer.computerIdn 11334
VERBOSE TemplateFinder 3/12/2018 11:12:07 AM : info.taskId 7255.info.templateId 226
==> since it is the right task ID and the right template ID I presume that the provisioing task (with the provisioning action wait(xx) was successfully retrieved by the core server).
From the client I can see that all prerequisite files were succesfully downloaded:
2018-03-12 20:12:28(1696-1704) ldProvision:Using [CORESERVER] for Core
2018-03-12 20:12:28(1696-1704) ldProvision:Getting server identifiers
2018-03-12 20:12:28(1696-1704) ldProvision:Getting BIOS Serial number by WMI.
2018-03-12 20:12:28(1696-1704) ldProvision:Serial Number by WMI: XXXXXXX
2018-03-12 20:12:28(1696-1704) ldProvision:Serial Number: XXXXXXX
2018-03-12 20:12:28(1696-1704) ldProvision:ldProvision started
2018-03-12 20:12:28(1696-1704) ldProvision:Entering downloadbyproxy.
2018-03-12 20:12:28(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args ( -f "x:\CBA8\cbaroot\alert\provisioning.ruleset.xml" http://CORESERVER/LdLogon/alertrules/provisioning.ruleset.xml)
2018-03-12 20:12:28(1696-1704) ldProvision:Waiting for process result: 0.
2018-03-12 20:12:28(1696-1704) ldProvision:Process exit code:1
2018-03-12 20:12:28(1696-1704) ldProvision:Entering downloadbyproxy.
2018-03-12 20:12:28(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args ( -f "x:\CBA8\cbaroot\alert\provisioning.ruleset.xml" http://CORESERVER/LdLogon/alertrules/provisioning.ruleset.xml)
2018-03-12 20:12:28(1696-1704) ldProvision:Waiting for process result: 0.
2018-03-12 20:12:28(1696-1704) ldProvision:Process exit code:1
2018-03-12 20:12:28(1696-1704) ldProvision:Entering downloadbyproxy.
2018-03-12 20:12:28(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args ( -f "x:\CBA8\cbaroot\alert\provisioning.ruleset.xml" http://CORESERVER/LdLogon/alertrules/provisioning.ruleset.xml)
2018-03-12 20:12:28(1696-1704) ldProvision:Waiting for process result: 0.
2018-03-12 20:12:28(1696-1704) ldProvision:Process exit code:1
2018-03-12 20:12:28(1696-1704) ldProvision:Entering downloadbyproxy.
2018-03-12 20:12:28(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args ( -f "x:\CBA8\cbaroot\alert\provisioning.ruleset.xml" http://CORESERVER/LdLogon/alertrules/provisioning.ruleset.xml)
2018-03-12 20:12:28(1696-1704) ldProvision:Waiting for process result: 0.
2018-03-12 20:12:28(1696-1704) ldProvision:Process exit code:1
2018-03-12 20:12:28(1696-1704) ldProvision:Entering downloadbyproxy.
2018-03-12 20:12:28(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args ( -f "x:\CBA8\cbaroot\alert\provisioning.ruleset.xml" http://CORESERVER/LdLogon/alertrules/provisioning.ruleset.xml)
2018-03-12 20:12:28(1696-1704) ldProvision:Waiting for process result: 0.
2018-03-12 20:12:28(1696-1704) ldProvision:Process exit code:1
2018-03-12 20:12:28(1696-1704) ldProvision:Entering downloadbyproxy.
2018-03-12 20:12:28(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args ( -f "X:\ldprovision\ldprovision_config.windows.xml" http://CORESERVER/LdLogon/Provisioning/windows/ldprovision_config.windows.xml)
2018-03-12 20:12:28(1696-1704) ldProvision:Waiting for process result: 0.
2018-03-12 20:12:28(1696-1704) ldProvision:Process exit code:0
2018-03-12 20:12:28(1696-1704) ldProvision:The file (X:\ldprovision\ldprovision_config.windows.xml) was successfully downloaded
2018-03-12 20:12:28(1696-1704) ldProvision:Entering downloadbyproxy.
2018-03-12 20:12:28(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args ( -f "X:\ldprovision\ProvisionHandlerLibrary.dll" http://CORESERVER/LdLogon/Provisioning/windows/ProvisionHandlerLibrary.dll)
2018-03-12 20:12:29(1696-1704) ldProvision:Waiting for process result: 0.
2018-03-12 20:12:29(1696-1704) ldProvision:Process exit code:0
2018-03-12 20:12:29(1696-1704) ldProvision:The file (X:\ldprovision\ProvisionHandlerLibrary.dll) was successfully downloaded
2018-03-12 20:12:29(1696-1704) ldProvision:Entering downloadbyproxy.
2018-03-12 20:12:29(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args ( -f "X:\ldprovision\ProvisioningCommon.dll" http://CORESERVER/LdLogon/Provisioning/windows/ProvisioningCommon.dll)
2018-03-12 20:12:29(1696-1704) ldProvision:Waiting for process result: 0.
2018-03-12 20:12:29(1696-1704) ldProvision:Process exit code:0
2018-03-12 20:12:29(1696-1704) ldProvision:The file (X:\ldprovision\ProvisioningCommon.dll) was successfully downloaded
2018-03-12 20:12:29(1696-1704) ldProvision:Entering downloadbyproxy.
2018-03-12 20:12:29(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args ( -f "X:\ldprovision\ClientRollinglog.dll" http://CORESERVER/LdLogon/ClientRollinglog.dll)
2018-03-12 20:12:29(1696-1704) ldProvision:Waiting for process result: 0.
2018-03-12 20:12:29(1696-1704) ldProvision:Process exit code:0
2018-03-12 20:12:29(1696-1704) ldProvision:The file (X:\ldprovision\ClientRollinglog.dll) was successfully downloaded
2018-03-12 20:12:29(1696-1704) ldProvision:Entering downloadbyproxy.
2018-03-12 20:12:29(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args ( -f "X:\ldprovision\log4net.dll" http://CORESERVER/LdLogon/log4net.dll)
2018-03-12 20:12:30(1696-1704) ldProvision:Waiting for process result: 0.
2018-03-12 20:12:30(1696-1704) ldProvision:Process exit code:0
2018-03-12 20:12:30(1696-1704) ldProvision:The file (X:\ldprovision\log4net.dll) was successfully downloaded
2018-03-12 20:12:30(1696-1704) ldProvision:Entering downloadbyproxy.
2018-03-12 20:12:30(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args ( -f "X:\ldprovision\ClientRollingLog.log4net" http://CORESERVER/LdLogon/ClientRollingLog.log4net)
2018-03-12 20:12:30(1696-1704) ldProvision:Waiting for process result: 0.
2018-03-12 20:12:30(1696-1704) ldProvision:Process exit code:0
2018-03-12 20:12:30(1696-1704) ldProvision:The file (X:\ldprovision\ClientRollingLog.log4net) was successfully downloaded
2018-03-12 20:12:30(1696-1704) ldProvision:Entering downloadbyproxy.
2018-03-12 20:12:30(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args ( -f "X:\ldprovision\ldprovision.sig" http://CORESERVER/LdLogon/Provisioning/windows/ldprovision.sig)
2018-03-12 20:12:30(1696-1704) ldProvision:Waiting for process result: 0.
2018-03-12 20:12:30(1696-1704) ldProvision:Process exit code:0
2018-03-12 20:12:30(1696-1704) ldProvision:The file (X:\ldprovision\ldprovision.sig) was successfully downloaded
2018-03-12 20:12:30(1696-1704) ldProvision:Entering downloadbyproxy.
2018-03-12 20:12:30(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args ( -f "X:\ldprovision\LaunchldprovisionAsUser.exe" http://CORESERVER/LdLogon/Provisioning/windows/LaunchldprovisionAsUser.exe)
2018-03-12 20:12:30(1696-1704) ldProvision:Waiting for process result: 0.
2018-03-12 20:12:30(1696-1704) ldProvision:Process exit code:0
2018-03-12 20:12:30(1696-1704) ldProvision:The file (X:\ldprovision\LaunchldprovisionAsUser.exe) was successfully downloaded
2018-03-12 20:12:30(1696-1704) ldProvision:Entering downloadbyproxy.
2018-03-12 20:12:30(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args ( -f "X:\ldprovision\ProvisionGUI.exe" http://CORESERVER/LdLogon/Provisioning/windows/ProvisionGUI.exe)
2018-03-12 20:12:31(1696-1704) ldProvision:Waiting for process result: 0.
2018-03-12 20:12:31(1696-1704) ldProvision:Process exit code:0
2018-03-12 20:12:31(1696-1704) ldProvision:The file (X:\ldprovision\ProvisionGUI.exe) was successfully downloaded
2018-03-12 20:12:31(1696-1704) ldProvision:Entering downloadbyproxy.
2018-03-12 20:12:31(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args ( -f "X:\ldprovision\provcomm.dll" http://CORESERVER/LdLogon/Provisioning/windows/provcomm.dll)
2018-03-12 20:12:32(1696-1704) ldProvision:Waiting for process result: 0.
2018-03-12 20:12:32(1696-1704) ldProvision:Process exit code:0
2018-03-12 20:12:32(1696-1704) ldProvision:The file (X:\ldprovision\provcomm.dll) was successfully downloaded
2018-03-12 20:12:32(1696-1704) ldProvision:download prerequisite files OK
2018-03-12 20:12:32(1696-1704) ldProvision:Running in Daemon mode.
2018-03-12 20:12:32(1696-1704) ldProvision:Provision Mode = PROVISION_MODE_CORE_SID
2018-03-12 20:12:32(1696-1704) ldProvision:Calling Program:x:\cba8\httpclient.exe -b ncs -H"X:\ldprovision\header.txt" -o"X:\ldprovision\body.txt" -f"X:\ldprovision\result.xml" https://CORESERVER/LANDesk/ManagementSuite/Core/ProvisioningWebService/WebService.asmx
2018-03-12 20:12:33(1696-1704) ldProvision:Web service call attempt:0. ExitCode:0
2018-03-12 20:12:33(1696-1704) ldProvision:Computer ID: 11334
2018-03-12 20:15:51(1696-1704) ldProvision:Saving DeviceID to file.
2018-03-12 20:15:51(1696-1704) ldProvision:Found BrokerConfig.exe in PE path x:\cba8\BrokerConfig.exe
2018-03-12 20:15:51(1696-1704) ldProvision:Serial Number: XXXXXXX
2018-03-12 20:15:51(1696-1704) ldProvision:Program: x:\cba8\BrokerConfig.exe
2018-03-12 20:15:51(1696-1704) ldProvision:Args: /b x:\cba8\ /p /a 28F10E48230D /s "XXXXXXX" /i 7255
2018-03-12 20:20:51(1696-1704) ldProvision:Warning, not able to obtain a client certificate. Secrets may not be able to be decrypted.
2018-03-12 20:20:51(1696-1704) ldProvision:Session Data: <session><variable name="XXXXXXXXX" type="none">CORESERVER</variable><variable name="XXXXXXXX" type="none">Unassigned</variable><variable name"XXXXXX" type="none">XXXXXX</variable><variable name"XXXXXXX" type="sensitive">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</variable><variable name"XXXXXXXXX" type="sensitive">XXXXXXXXXXXXXXX</variable><variable name="XXXXXXXX" type="none">CORESERVER</variable><variable name="XXXXXXXXXX" type="none">XXXXXXXXX</variable><variable name="XXXXXXXXXXX" type="none">XXXXXXXXXXX</variable><variable name="XXXXXXX" type="none">XXXXXX</variable><variable name="XXXXXXXXXX" type="none">XXXXXXXXX</variable><variable name="XXXXXXXXX" type="none">XXXXXXXXXXXXXXXX</variable><variable name="XXXXXX" type="none">XXXXXXXXX</variable><variable name="xXXXXXXX" type="sensitive">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</variable><variable name="XXXXXXXXXXXX" type="none">XXXXXXX</variable><variable name="xXXXXXXXX" type="none">XXXXXXXXXXXX</variable><variable name="XXXXXXXXX" type="none">XXXXXXXXXXXX</variable><variable name="XXXXXXXXX" type="none">XXXXX</variable><variable name="XXXXXXXXXX" type="none">Unassigned</variable><variable name="XXXXXXXXXXXXX" type="sensitive">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</variable><variable name="XXXXXXXXXXX" type="none">XXXXXX</variable><variable name="XXXXXXXXX" type="none">XXXXXXXXXX</variable><variable name="XXXXXXXXXX" type="none">XXXXXXXXXXXXXXXX</variable><variable name="_XXXXXXXXX" type="none">wait30</variable><variable name="XXXXXXXXXXXXXXX" type="sensitive">XXXXXXXXXXXXXXXXXXXXXXXXX</variable><variable name="XXXXXXX" type="none">XXXXXXXXXX</variable><variable name="XXXXXXX" type="none">XXXXXXXX</variable><variable name="XXXXXXXXXXXXXXXXXX" type="none">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</variable><variable name="XXXXXXXXXX" type="none">XXXX</variable><variable name="XXXXXXXXX" type="sensitive">XXXXXXXXXXXXXXXXXXXXXXXXXXX</variable></session>
2018-03-12 20:20:51(1696-1704) ldProvision:Going to have the core decrypt a password
2018-03-12 20:41:10(1696-1704) ldProvision:Decrypting Provisioning Password http://coreserver:443/LANDesk/ManagementSuite/Core/serverauthentication/serverauthentication.asmx
2018-03-12 20:41:10(1696-1704) ldProvision:Requesting for deviceId: {9CB96B07-766C-EC4F-B482-17DAF597922C} !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2018-03-12 20:41:10(1696-1704) ldProvision:Found httpclient.exe at x:\cba8\httpclient.exe
2018-03-12 20:41:10(1696-1704) ldProvision:Making web service call via proxyhost.
2018-03-12 20:41:10(1696-1704) ldProvision:httpclient args: -b ncs -p"127.0.0.1:9592" -H"X:\ldprovision\wscheader.txt" -o"X:\ldprovision\wscbody.xml" -f"X:\ldprovision\wscresult.xml" http://CORESERVER:443/LANDesk/ManagementSuite/Core/serverauthentication/serverauthentication.asmx
2018-03-12 20:41:40(1696-1704) ldProvision:TryallWebService exitcode: -1
2018-03-12 20:42:15(1696-1704) ldProvision:TryallWebService exitcode: -1
2018-03-12 20:42:55(1696-1704) ldProvision:TryallWebService exitcode: -1
2018-03-12 20:43:05(1696-1704) ldProvision:Unable to decipher attribute name: 11
For the log file proxyhost.log it was empty. I tried the same template with another device and proxyhost.log wasn't empty. There was some HTTP traffic.
Proxyhost.log (!!! not on the affected device but in another device that succesfully retrieved and started processing provisioning task)
2018-03-12 17:49:49(364-332) proxyhost.exe:127.0.0.1:49688 - - [12/Mar/2018:09:49:49 -0800] "POST http://CoreServer/landesk/managementsuite/core/core.anonymous/ClientCertificateRequest.asmx HTTP/1.1" 200 1621 2292
2018-03-12 17:49:49(364-332) proxyhost.exe:127.0.0.1:49688 EOS on request
2018-03-12 17:49:49(1220-1204) proxyhost.exe:FIPS mode = 0
2018-03-12 17:49:49(1220-1204) proxyhost.exe:IsProcessSigned succeeded - returning: 1
.
.
2018-03-12 17:49:49(1220-1204) proxyhost.exe:127.0.0.1:49690 - - [12/Mar/2018:09:49:49 -0800] "POST http://CoreServer:443/LANDesk/ManagementSuite/Core/serverauthentication/serverauthentication.asmx HTTP/1.1" 200 721 862
2018-03-12 17:49:49(1220-1204) proxyhost.exe:127.0.0.1:49690 Connection terminated reading request line for socket 4 error code -2
2018-03-12 17:49:49(348-352) proxyhost.exe:FIPS mode = 0
2018-03-12 17:49:49(348-352) proxyhost.exe:IsProcessSigned succeeded - returning: 1
In the IIS log file I can see this traffic. But for the device that keeps failing I can't see any traffic related to certificate or serverauthentication.
One more thing, in the device that successfully started the provisioning task, the folder X:\cba8\cbaroot\broker there was .csr file + .Key file + proxy.state.xml + crt file but for the failed device this folder was empty.
Many community articles and conversation talks about borkerconfig.exe /r I tried it but without any success.
Could any one support me with this issue. I don't understand what is the role of brokerconfig.exe and why the device should apply for a certificate since I am not enabling client certificate-based feature and I don't have any blocked device.
Is anyone using copydrivers.exe for windows 10 deployment ?
we have been using it and it has been working fine, in the new versions of windows 10 the drivers copy over to the device (c:\windows\inf\lddriverstore) but don't actually install automatically, you have to right click and update each driver and point to the central location, anyone else experiencing this issue? and know a work around
Hey guys,
I need a little bit of help with the following problem:
Long time ago I created a bunch of single software distribution packges, bundled within a Provisioning package. This package worked like a charm.
A while ago (I think after the LD 9 SP2 upgrade) this package got stuck each time it ran. The curious thing is, that it gets stuck always on a different position - sometimes after the 3rd software, sometimes after the 5th and so on. What always is the same is the error message: for the whole Provisioning task, it's always 1163 (A provisioning action failed - good to know). But the single tasks (when you take a further look into the software that got stuck) always have the External Status '0' (which generally means success), even the one that stopped the whole thing.
What I tried, but didn't helped, was, to add this error code to the 'Return Code template Manager' as 'success' - but because it is under 'Distribution Packages' (and they run successfully with Error 0) it's clear that it doesn't help at all.
Could one of you guys help me with this? Do you need more info, and if so which?
All the best,
Norman
Hello All,
I cannot seem to get my windows 10 images to provision correctly.
We use ImageX in our environment. When I capture the image I used Sysprep with OOBE.
However when deploying the image, the task seems to stop at "Configuring Target OS" and stays "working". There is a cmd window that appears for a split second and then the machine reboots and loads into Windows and stops at the log in screen. Once I log in nothing happens. In our windows 7 images, the task window would appear after log in and continue running, adding to the domain and installing the agent.
There is an LDprovisioning folder in the C drive, however when clicking any .exe the whole folder disappears.
If I boot the machine back into PXE, it loads up the task again and finishes configuring the target OS task, then fails the "Add to domain" and "configure agent" tasks.
Also of note, the Device name prompter does not actually change the name of the machine. The original image name is retained despite the task saying it succeeded.
Any ideas as to what I am doing incorrectly? This same process works great with our windows 7 images, however I did not build those and the employee who did is no longer here.
I got some new HP Pro-books with 2 drives (SSD+HDD). For some reason system detects the HDD (Data) is as disk 0 and SSD (system) as disk 1.
I need to provision those devices, but can't figure out how to make landesk provisioning install OS on SSD (disk 1)
It always select the HDD marked as disk 0 as a system disk and install OS there.
Of course I could remove the HDD from the notebook, but it's not the way I want to solve it.
Thank you for help.
I am having difficultly capturing an HP Thin Client image to use in provisioning. I have captured the image using HP's software and it creates a .ibr file and to change this to a .tbi file I am lost. I can create an iso using their tool but it doesn't allow me to boot up to it in a VM to capture. There are old documents for how to do this but none of the links work it appears. Is anyone aware of the process they use or can provide me the instructions. If I PXE to the thin client the capture fails each time. Maybe there is a way to get that to work?
I've only messed with Provisioning Templates on the local network but now I am looking to expand into the remote field, but its not looking like I can utilize Provisioning through the CSA. In my experience CSA packages or deployments need to be accessed via http: and when a provisioning task starts it tries to download the files it needs into the root of C:\ldprovisioning only via UNC. This is failing on my end, but no way to switch the download to http.
Is it even possible to do this through the CSA? Has anyone done it?
Provisioning stops and to resume an HP USB to Ethernet adapter has to be removed and reinserted.
HP USB 3.0 to Gigabit RJ45 Adapter 829834-001
https://support.hp.com/hk-en/document/c04883825
RESOLUTION: Disabled the automatic driver update function of the HP USB 3.0 to Gigabit RJ45 Adapter 829834-001 using an HP Flash Disable Tool
ftp://ftp.hp.com/pub/softpaq/sp76501-77000/sp76691.exe
ftp://ftp.hp.com/pub/softpaq/sp76501-77000/sp76691.html
TITLE: HP Flash Disable Tool
VERSION: 1.0 REV: A PASS: 1
DESCRIPTION: This package provides HP Flash Disable Tool for supported models running a supported operating system. This applet disables the automatic driver update function of the supported accessories connected to the system. This accessory-specific applet may be needed in certain PXE environments that require automatic driver installations to be disabled.
PURPOSE: Routine
SOFTPAQ FILE NAME: SP76691.exe
SOFTPAQ MD5: 697d018d1ce7d5139cec47987041b7c3
SUPERSEDES: None
EFFECTIVE DATE: July 15, 2016
CATEGORY: Utility-Tools
SSM SUPPORTED: Yes
PRODUCT TYPE(S): Port Replicators;Cable Adapters
HARDWARE PRODUCT MODEL(S):
OPERATING SYSTEM(S):
Microsoft Windows 10 32
Microsoft Windows 10 64
Microsoft Windows 7 Enterprise 32 Edition
Microsoft Windows 7 Enterprise 64 Edition
Microsoft Windows 7 Home Basic 32 Edition
Microsoft Windows 7 Home Basic 64 Edition
Microsoft Windows 7 Home Premium 32 Edition
Microsoft Windows 7 Home Premium 64 Edition
Microsoft Windows 7 Professional 32 Edition
Microsoft Windows 7 Professional 64 Edition
Microsoft Windows 7 Starter 32 Edition
Microsoft Windows 7 Ultimate 32 Edition
Microsoft Windows 7 Ultimate 64 Edition
Microsoft Windows 8 32 Edition
Microsoft Windows 8 64 Edition
Microsoft Windows 8.1 32 Bit
Microsoft Windows 8.1 64 Bit
LANGUAGE(S): Global
DEVICES SUPPORTED:
HP USB 3.0 to Gigabit LAN Adapter (N7P47AA)
HP USB-C to RJ45 Adapter (V7W66AA)
HP USB-C to RJ45 Adapter (V7W66UT)
PREREQUISITES:
HOW TO USE:
1. Download the file by clicking the Download or Obtain Software button and saving the file to a folder on your hard drive (make a note of the folder where the downloaded file is saved).
2. Double-click the downloaded file and follow the on-screen instructions.
3. Go to the folder where the file was unbundled, double-click the FW_UPGRADE.exe file, and follow the on-screen instructions.
I'm running landesk 2016.3
I'm provisioning a Windows 10 machine, ver 1709
During provisioning I have a batch file that fails. It is set to install under current user account. If push it to a logged on computer it works as long as I have it set to run under the current user account.
During provisionining it always fails,
During Provisioning after CTOS the computer logs in on the Administrator account to continue provisioning. I've placed the install after joining the domain, before joining the domain, changed it to run as system account and domain account but it still fails.
The batch file just has 2 lines both REG ADD.
This article covers how to enable PXE logging. This can be helpful when troubleshooting PXE representatives.
Hello All!
I have a question about his error I am getting when I try to deploy a High Sierra Image to on of my new Macbook Pros. The attached pictures shows both the error I am getting and my Deploy template. I was able to capture my image the other day, but so far have not been able to deploy it to the same machine it was captured from. I took out the step or formatting the partition just to see if there was something wrong there, but it still does not deploy. Any guidance on this error would be fantastic! Let me know if you need any kind of clarifications to anything.
Thanks!!
Hello, community!
I just recently updated my Ivanti Endpoint Manager from 2017.1 to 2017.3 after learning (from the Ivanti Bootcamp) that 2017.3 has integrated the Profile Capture / User Migration Assistant from AppSense.
According to the official Ivanti Endpoint Manager 2017.3 users guide, we should have access to this "UMA" (User Migration Assistant). However, after selecting the Capture Profile action in the Capture Template within OS Provisioning, we are completely unable to find any folder named "UMA" or find any indication that the tool is there.
In fact, the actual guide doesn't offer much insight to the actual tool.
My question is whether or not this tool was actually implemented in 2017.3 as we were told within our Ivanti Bootcamp course. If it was, I'd like to know how to find it and use it. We have a massive Windows 10 deployment project underway, and we cannot migrate to Windows 10 until we have a secured and confirmed working method of backing up user data.
Does anyone have any insight on this?
Some clients boot into the windows boot manager after booting them to WinPE through a provisioning template. I always need to press Enter to continue the boot process.
Has someone expirienced similar things? How can I skip this?
Hello,
I'm using LDMS 207.3.2 and I want to use OS Provisioning.
I have a problem with Self-Electing Subnet Services. The PXE Representative elected is not a device that always
works : its state is often "deactivated" and I can't change it on my own.
I would like to have a single PXE Rep on my subnet (for instance, a computer I have chosen before, with PXE service activated in client connectivity). How can I do that ?
Thanks for help.
I am having a very hard time getting an image to deploy to a surface pro 3
The deploy image handler gives me this error each time.
2018-02-02 22:39:57(3044-2140) DeployImageHandler_x64.exe:Replacing path string \\knt001ap21\ldimaging\images, with e:
2018-02-02 22:39:57(3044-2140) DeployImageHandler_x64.exe:New Args: /r /o /x /d:0 /rb:0 /f:e:\KentW10Ent64Surface.tbi
2018-02-02 22:39:57(3044-2140) DeployImageHandler_x64.exe:Going to execute imagew.exe /r /o /x /d:0 /rb:0 /f:e:\KentW10Ent64Surface.tbi
2018-02-02 22:39:57(3044-2140) DeployImageHandler_x64.exe:ExecuteCmd imagew.exe /r /o /x /d:0 /rb:0 /f:e:\KentW10Ent64Surface.tbi
2018-02-02 22:39:57(3044-2140) DeployImageHandler_x64.exe:Could not create process, error: 2
2018-02-02 22:39:57(3044-2140) DeployImageHandler_x64.exe:Tearing down Environment.
2018-02-02 22:39:57(3044-2140) DeployImageHandler_x64.exe:ExecuteCmd maptopreferredhandler_x64.exe /unmap /driveletter=e:
2018-02-02 22:39:57(3044-2140) DeployImageHandler_x64.exe:created process, file handle bc with non-readonly parameter
2018-02-02 22:39:57(3044-2140) DeployImageHandler_x64.exe:Process Exit Code: 0
2018-02-02 22:39:57(3044-2140) DeployImageHandler_x64.exe:execute failed with 2
the image is there. I can see it when I manually check. HELP!!
This document describes an error in which users are unable to access the provisioning client unless they are granted the "LANDesk Administrator" role.
ProvUserValidator.Validate(), user does not have RBA rights
Change the identity of the app pool "LDAppMain" from "NETWORKSERVICE" to "LOCALSYSTEM"
During provisioning while deploying or capturing you may get the following error. Most commonly this error occurs when deploying an image but can occasionally occur during capture as well.
---------------------------
Error - LANDesk® OS Deployment
---------------------------
Unable to obtain a lock on drive C:
The volume is in use by an application or Windows itself. Please close the offending application and retry or use a recovery boot disk.
Visit www.terabyteunlimited.com/howto/ for details.
You can also attempt to invalidate all opened handles and force a discmount by choosing ignore.
---------------------------
Abort Retry Ignore
---------------------------
As the error indicates ImageW is unable to lock the C drive because the volume is in use by an application or by the OS.
You can overcome this issue by forcing the dismount of the volume. You will need to add an additional command to the command line parameters in your deploy or capture image action within your template. The switch is /fd. The /fd needs to be placed after the /rb:0 switch. Below is an example.
*** Important ****
Do not use the validate button after making the changes. The validate button resets the command line back to default and will remove the /fd switch.
More information about the fd switch is found below.
(/fd Use this option to force dismounting a volume (partition) that can't be locked for backup when PHYLock or VSS is not used. Using this option will invalidate all opened handles to the volume, which may result in lost data. Image for Windows will attempt to lock the volume after forcing the dismount.)
ImageW manual.
http://www.terabyteunlimited.com/downloads/ifw_en_manual.pdf
Hello,
on a server (Server 2016) incl.
PXE Representative fails.
This doc did not resolve the Issue:
Issue: Running a scheduled task to deploy the PXE Representative fails
there are NO four folders:
... that is the result.
On a client:
Console:
... no other log files
No log Files such as:
C:\ProgramData\LANDesk\Log\SelfElectController.log
C:\ProgramData\LANDesk\Log\pxesvc.log
Can you help me?
(Is there a way to (re)build the files "C:\Program Files (x86)\LANDESK\PXE\System\images\*.*")
Best regard
lucky devil
Note: In LANDESK Management Suite 9.6 or 2016 the software distribution architecture has been completely redesigned, and the case of templates taking a long time to start should be improved or eliminated.
The provisioning task is failing to load. It will attempt to load the template and retry for 40 attempts and then the job hangs and the client stays in the WinPE screen or brings back the template section window.
In 2016, the LDPROVISION.LOG file in WINPE has the following error:
“Not able to obtain a client certificate. Aborting provisioning”
Logs on the core may indicate a few different errors:
Template is not flattened, will attempt to flatten.
Flattening template failed.Unable to find the history taskUnable to find template for computer idn ###Unable to find computer
If the LANDESK Inventory Server service is stopped on the Core Server, the device will not show up in the LANDESK Console when the Mini Scan runs when WINPE loads. If this is happening the Provisioning.log file will show the "Unable to find computer" error.
The Inventory service is set to ignore Mini Scans which will cause new computers to not show up in All Devices in the Console and consequently prevent templates from running.
If a provisioning task has already been assigned to the machine in question, the task will fail. If you review the provision.log file on the core you will see a line "Computer is Busy with another task {taskID}"
A corrupt template can prevent correct scheduling. One cause if this is if a template is imported, the drop down boxes are not filled in as they were pointing to objects from the previous core. For example, Software Distribution actions do not have a package specified. Same with Configure Agent actions. Also any actions with scripts will have this issue. Another way to determine if your template is not configured properly is by reviewing the Provisioning.log on the core. If you see the following:
INFO PROV_SCHEDULE 8/18/2011 5:06:50 PM : Action LANDesk.Provisioning.Business.PAction_Distribute_software
INFO PROV_SCHEDULE 8/18/2011 5:06:50 PM : Got package ID 60, requesting snippet
INFO PROV_SCHEDULE 8/18/2011 5:06:50 PM : Requesting snippet for packageId 60
INFO PROV_SCHEDULE 8/18/2011 5:06:50 PM : Requesting SWD snippet with task IDN 2214, package ID 60
ERROR PROV_SCHEDULE 8/18/2011 5:06:50 PM : Exception encountered trying to get snippet (LANDesk.ManagementSuite.SoftwareDistribution.Business.PackageNotFoundException): This package has been deleted.
ERROR PROV_SCHEDULE 8/18/2011 5:06:50 PM : GetSoftwareSnippet failed
Error when attempting to save template - "Cannot save changes to the template . Verify that the template name you have chosen is not already used by another template. Database Error."
If you are adding included templates to a main template you will want to start with adding the included templates one at a time until you find the problem template. Then address the specifics of that template and what it is doing. Try to recreate a new template that duplicates the problem template and see if you get any errors while saving the template.
Example Customer Situation:
The problem template was one that used the Update Registry action item and the Registry Operation of Import File. Because the file that was being imported was a combination of different registry export files, and remarked out descriptions had been added to the file, the template would return error: "Cannot save changes to the template . Verify that the template name you have chosen is not already used by another template. Database Error." The initial problem came from the fact that the original template did save when maybe it should not have, which caused the provisioning task to fail and the Prov_Schedule.exe.log file to show "Flattening template failed". Once we isolated the issues with the remarked out lines in the reg file and removed them, the template saved and the provisioning task worked properly.
In the customers environment, having the remarked out comments failed, but in a test lab the customers reg file worked fine. After getting the reg file to import and save, we found that the script failed on the reg file when trying to run it. What we discovered is that in his situation, the header in the reg file that says: "Windows Registry Editor Version 5.0" was causing it to fail, but I was unable to duplicate any of his problems in my lab. This seems to be a unique situation and may or may not apply to other customers that are having the 40 of 40 retries issue.
If there are a large number of PXE representatives in the environment, this error will occur as the core tries to update them all with the needed information. If it cannot complete in time for the 40 retries, the task will not start. However, if you keep waiting the template may start.
Reduce the number of PXE reps and remove all PXE Reps that are not active.
Software packages that contain a large amount of additional files will require the core to hash the files and prepare manifest files each time a new template is run.
This can cause significant slowdown. As an example, Microsoft Office 2013 can contain ~ 570 files if the files are included as additional files to the main setup program.
It is recommended to package something like this into a single file or into a few files. This should significantly speed up the distribution process.
Due to the Software Distribution architecture changes in LDMS 9.6, this issue and most other issues with templates taking a long time to start should be eliminated.
The user that is selecting the template cannot see the devices in the Console that are being imaged.
Give the user that is running the template the All Devices scope or create a scope that sees the devices and assign it to the user in the User Management tool.
Add the account that is configured in the scheduler service into the LANDesk Administrators group and add the account into the console. Once you can see the user in the Console (in the "User Administration" module) run ResolveUserGroups.exe and CreateLandeskRights.exe as an admin from the ManagementSuite Directory. Verify that the User is configured as an LDMS Admin and then restart the scheduler service.