Running LDMS 9.6 SP3
When imaging a Windows 10 UEFI computer through Bare Metal when it gets to laying down the image I get a popup about can't get a lock on c and it goes on to say that something has it open. I choose Ignor.
Is anyone else getting this popup?
The PC is contacting the core server instead of the preferred server when loading images. Please help
Hi,
We have a template that we use for profile migration. It works fine, for the most part. However, we are limited to only one value that is acceptable as a test for success/failure. What I would like to happen is take the return value and use a conditional "IF" statement to take action based on the return value. Is this possible? For instance, a return value of 3 is acceptable because it means that some files were skipped for whatever reason. That fact is that there are more acceptable return values but that are not seqeuntial in nature.
Hello everyone:
I have a fairly simple unattend file. I use the %ldhostname% variable to allow dynamic naming during the imaging process. I have checked and the injected unattend has the correct computer name. However, when the computers boot, they will be named "Desktop-xxxx" Has anyone experienced this?
Unattend file:
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="auditSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<ValueRedacted</Value>
<PlainText>true</PlainText>
</Password>
<Description>Local Admin</Description>
<DisplayName>Redacted</DisplayName>
<Group>Redacted</Group>
<Name>Redacted</Name>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
</component>
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="wow64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideLocalAccountScreen>true</HideLocalAccountScreen>
<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<NetworkLocation>Work</NetworkLocation>
<SkipMachineOOBE>true</SkipMachineOOBE>
<SkipUserOOBE>true</SkipUserOOBE>
<UnattendEnableRetailDemo>false</UnattendEnableRetailDemo>
</OOBE>
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<Value>Redacted</Value>
<PlainText>false</PlainText>
</Password>
<Description>redacted</Description>
<DisplayName>redacted</DisplayName>
<Group>redacted</Group>
<Name>redacted</Name>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
</component>
<component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>en-us</InputLocale>
<SystemLocale>en-us</SystemLocale>
<UILanguage>en-us</UILanguage>
<UserLocale>en-us</UserLocale>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
<NetworkLocation>Work</NetworkLocation>
<SkipMachineOOBE>true</SkipMachineOOBE>
<SkipUserOOBE>true</SkipUserOOBE>
<HideLocalAccountScreen>true</HideLocalAccountScreen>
</OOBE>
<AutoLogon>
<Password>
<Value>redacted</Value>
<PlainText>false</PlainText>
</Password>
<Domain>.\</Domain>
<Enabled>true</Enabled>
<LogonCount>2</LogonCount>
<Username>redacted</Username>
</AutoLogon>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="wow64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ComputerName>%ldHostname%</ComputerName>
<ProductKey>redacted</ProductKey>
</component>
<component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>en-us</InputLocale>
<SystemLocale>en-us</SystemLocale>
<UILanguage>en-us</UILanguage>
<UserLocale>en-us</UserLocale>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ComputerName>%ldHostname%</ComputerName>
</component>
</settings>
<cpi:offlineImage cpi:source="wim:redacted" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
Hello!
We have a problem with a domain registration. In the past we created a "private data" variable for password under global variables and it worked fine with all PC models so far. Recently we get the error 1326 with some PC models (user data are wrong). As soon as I insert the password directly into the template or the variable as plain text, everything works fine.
We can live with that, but it would not be bad to correct this mistake.
Yours sincerely.
Translated with www.DeepL.com/Translator
This document contains the steps necessary to deploy a Windows 10 image in provisioning using ImageX. Although it mentions Windows 10, the same steps will work for Windows 7, 8 and 8.1.
For help with capturing the image, refer to the following Community article:
How to Capture a Windows 10 image with IMAGEX
1. Copy the Winx64Unattend.xml file to a directory on the Core Server. The file is in the ProvImageX.zip file attached to the following Community article:
How to Deploy a Windows 10 Image with ImageX
2. In the Operating system provisioning tool in the LANDESK Console on the Core Server, click on Provisioning templates in the left pane.
3. Click Tools at the top of the window then click Install Scripts.
4. In the Install scripts window, click the Browse button and browse to the folder where the Winx64Unattend.xml file was copied and select it.
5. In the Script name box, enter a name for this unattend file to uniquely identify it.
6. In the Description box, enter a description if desired.
7. Select Windows for the Target operating system.
8. Click the Import button to import the unattend file into the database. The Script name will appear in the Install scripts list if it is successful.
1. Copy the provisioning template DeployWin10ImageX.xtp to a folder on the Core Server. The template is in the ProvImageX.zip file attached to the following Community article:
How to Deploy a Windows 10 Image with ImageX
2. In the Operating system provisioning tool in the LANDESK Console on the Core Server, click on Provisioning templates in the left pane.
3. Click the Import templates icon along the top of the Operating sytem provisioning tool.
4. Click the Browse button in the Import templates window and browse to the location where the template was copied in step 1 and select it.
5. Click the Import button.
6. Click OK.
7. Click the Close button in the Import templates window. The imported template will show up in the Operating system provisioning tool under Provisioning templates | My templates | All my templates with a name starting with DeployWin10ImageX and includes a Date/Time stamp. The template name can be changed after it is imported.
1. In the Operating system provisioning tool, double-click the provisioning template that was imported in the Provisioning templates | My templates| All my templates folder.
2. Expand the OS-installation section of the template and click on the Deploy Image action.
3. Make sure that ImageX is selected for the image type.
4. Enter the UNC path including the filename to the Windows 10 image to be deployed. The file will have a .WIM extension.
5. Click the Validate button which updates the Command-line then click Apply.
6. Click on the Inject unattend file action under the Post-OS installation section of the template.
7. Select the unattend.xml file that was imported earlier from the Script name drop-down list.
8. Click the Apply button.
9. If the OS being deployed already has the drivers for the computer to be imaged or you are not planning on using LANDESK Hardware independent imaging, the Hardware independent imaging action can be deleted from the template in the Post-OS installation and System configuration sections.
10. Click on the Install LANDESK Agent action in the System configuration section of the template.
11. Select the desired LANDESK Agent from the Configuration name drop-down list.
12. Click the Apply button.
13. Add additional actions to the template if desired. Do this by right-clicking the section of the template and select the Add Action option. There is an action to join the domain and an action to run software distribution packages as well as many others. After adding any actions, be sure to click the Apply button.
14. Click OK to save the changes to the template.
1. In the Operating system provisioning tool, click on Provisioning templates in the left pane.
2. Click Tools and click Public Variables.
The public variables shown in the screenshot above are there by default. The Replace value for the variables corename and coreIP can be changed if needed but do not change the Search value (variable name) for them or it will break provisioning. The Search values are case-sensitive.
3. Click the Add button.
4. Enter AdminPass in the Search value box. This variable is used in the unattend.xml file.
5. Select Sensitive data from the Type drop-down list.
6. In the Replacement value and Confirm replacement value boxes, enter the password which will be assigned to the local Administrator account on the computer when the image is deployed.
7. Click OK.
AdminPass now shows up in the Public variables window.
8. Click Add.
9. Enter WinProdKey in the Search value box. This variable is used in the unattend.xml file.
10. Select String from the Type drop-down list.
11. Enter the Windows 10 product key in the Replacement value box.
12. Click OK.
13. Click Add.
14. Enter Company in the Search value box. This variable is used in the unattend.xml file.
15. Select String from the Type drop-down list.
16. Enter your Company name in the Replacement value box.
17. Click OK.
18. Click OK to close the Public variables window.
This step can be skipped if the HII actions were deleted from the template.
For help with HII, click F1 in the LANDESK Console and search for HII.
This section can be skipped if the devices are already in the LANDESK Console under All Devices.
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. The name entered will be the computers name after it is imaged.
6. Make sure the Identifier type has MAC address selected then enter the MAC address of the of the 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.
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
1. Drag the computer(s) from the Bare Metal Devices folder or from All Devices and drop them on the template that was imported earlier.
2. Click Save.
3. Make sure all devices targeted for the task are off.
4. Right-click the task and select Start now | All.
5. Wait a minute to give the task time to initialize.
1. Network boot (PXE boot) the computer(s) in the provisioning task. When the computer(s) are PXE booted, they will automatically load WINPE and run the template. For help with network booting the computer(s), refer to the computers documentation.
2. Wait for the provisioning task to complete. The computer(s) will reboot at least 2 times during the provisioning process. Following are screenshots of various stages of the provisioning process:
Downloading WINPE from the PXE Representative. The IP address shown is the IP address of the PXE Representative.
WINPE is loading.
WINPE has successfully loaded and has started to run the provisioning template.
ImageX is currently running to deploy the image.
The image has been deployed and the computer has rebooted to load the OS. It has started going through the sysprep process to load the OS for the first time.
The OS rebooted and is continuing to load for the first time processing the unattend.xml file.
Sysprep has completed and is now running the actions in the System Configuration section of the template. When the template is done, the computer will shutdown.
For this method, skip the following sections of this document:
Add Devices to be Imaged
Schedule the Template and Start the Task
Network Boot the Devices and Wait for the Task to Complete
1. If the computers all do a BIOS boot then you can skip to step 3. If the devices do a UEFI boot, Click Preboot | PXE Boot Options in the Operating system provisioning tool.
2. Make sure there is a check in the Always PXE Boot UEFI Devices and click Save.
3. Network boot (PXE boot) the computer and click F8 when it shows on the screen. Refer to the computers manual if you need help PXE booting it.
4. Select WinPE Provisioning and hit Enter on the keyboard.
5. WINPE is downloading from the PXE Representative. The IP address shown is the IP address of the PXE Representative.
6. WINPE has downloaded and is now starting on the computer.
7. Enter the Domain, Username and Password for an account that has rights to provisioning in the LANDESK Console. Use the same account that you login with to the LANDESK Console.
8. Click OK.
9. Click on the Provisioning template under All my templates and click OK.
10. The template is now running. Wait for it to finish. The computer will shutdown when the template is done. Refer to the screenshots in the previous section to see various stages of the provisioning process.
Applies to LANDesk Management Suite 9.0 and 9.5
Issue
Follow the instructions in the LD9590SP2SP3OSDCapture document attached to this article.
Is there a way to capture an image windows XP machine while the machine is on.
Thanks
Hello,
win10 v1703 is installed on our PCs. Installed with LDMS 2016.3.
Now we want to upgrade to 1709. We copied the 1703 package, Change the wim file and let it run.
Everything is ok. Win10 1709 is installed. But after that we want to install Office2016 and that dont work. I find out, the taskplaner don't work now. And so you can't install Office2016. I tried to find a solution, but I only see: after second reboot, after Installation of the provisioning Agent, the taskplaner failed. "Der Remotecomputer wurde nicht gefunden". "the remotecomputer wasn't found"
Anything I changed in my paket, after second reboot the taskplaner failed. The Taskplaner Service would'nt start. It's only with 1709 and LDMS Installation. A clean Installation with win10 from USB works fine.
Any Ideas for me?
Thanks a lot!
Kind regards Mike
We are trying to enable Remote Control in WinPE during provisioning, in LDMS 2016.3. I've read numerous articles on how to grab folders/files from the ldvpe1.img file, but can't seem to locate that image file anywhere (even in the install files). I have the startnet.cmd file that is supposed to work, but that doesn't seem to work (I get an error when trying to start issuser.exe as a service). Does anyone have any documentation on this?
For reference, we are actually using LDMS for application delivery, remote control, etc. We use MDT 2013 for WIM creation / OS Provisioning.
Hey guys,
Just wondering how everyone else does their one touch computer imaging. I'm getting started with this and would like to get to the point where the base image is laid down, drivers, then packages installed, name machine, join domain, add user account, wifi, printers, etc etc. Been searching for a bit and not really seeing anything that points to these.
For the time being the OS is Windows 10 running on Dell Latitude hardware. Anyone have links or tips on where to start would be much appreciated!
Thanks,
So
Issue:
You boot into WinPE from a VMWare Windows guest device configured with the VMXNET3 network adapter and/or the PVSCSI disk controller. In WinPE you don't have network and/or you don't see any disks.
Cause:
The drivers from the VMWare are not included in the WinPE image. Especially the 32-bit PVSCSCI driver is hard to find. As most OS's are 64-bit nowadays, the installed VMware Tools also contain only the 64-bit drivers. But if the device is non-UEFI, it will still boot the 32-bit WinPE image.
Solution:
Download the current version of the VMware Tools packages for Windows and Linux from https://my.vmware.com website. Use an archiving tool to extract the downloaded file (like 7-zip, for example). Look for the PVSCSI and VMXNET3 driver folders. Use the guide hereHow to add drivers to WinPE for Ivanti EPM OS Provisioning to add the attached drivers to the WinPE boot images. Please note that the VMXNET3 driver is the same for both the 32-bit and the 64-bit image, but that there are separate architecture drivers for the PVSCSI controller.
Hi,
I am running on weird situation I never saw before with just one computer in one location. 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.
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.
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
When Imaging machines with UEFI enabled i am running into a problem after rebooting from WinPE. the first reboot does not see the hard drive. If you check BIOS before it attempts to boot there is not option for the hard drive or windows boot manager under the UEFI options. After it fails to boot, BIOS then registers the harddrive and the machine will boot into windows and complete the OSD template.
Greetings all,
I have been working on setting up our new Windows 8.1 deployment and have encountered a problem. After I deploy the image via the LANDesk template and the computer reboots I get the following error:
"Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
...
...
File: \Boot\BCD
Status: 0xc000000f
Info: The Boot Configuration data for your PC is missing or contains errors."
I was able to run the startup repair from my install DVD and it booted right up. I'm thinking that I've somehow partitioned the drive incorrectly in my template.
I just create the one partition onto which to drop the image. Not sure exactly what I need to do to correct this. Any help that can be provided would be greatly appreciated. I am using LANDesk 9.5 SP3.
Thanks,
John
The PC is contacting the core server instead of the preferred server when loading images. Please help
I'm pretty frustrated with an issue in provisioning.
The issue appears with new computers that never have been in the Landesk database or with computers that were deleted because they didn't report in for a longer time.
I can choose my templates ( they are all public, so no user authentication), but it just runs through the 40 tries and then I end up where I started. I have to run through this process a couple of times until finally the template gets picked up and executed. This is not the case for machines that already exist in the Landesk database.
I'm in contact with Landesk support since 6 weeks, I checked about any cause and went through all troubleshoot steps that I could find here on the community, to no avail.
Now I had an idea how to get around this issue.
What if I would call a powershell script before launching the template, that checks if the MAC address already exists, and if not it adds an entry via MBSDK ?
Is anybody experiencing the same issue, or maybe somebody can help me to get further with my idea ? I don't know how to check if a MAC address exists, couldn't find a function that does this.
Your help is very much appreciated.
I'm still very new to Landesk. I'm trying to set up a menu that allows you to choose between various templates while in WinPE.
So basically I want to have one basic template with nothing in it but the start menu. This calls then the the actual installation template with the OS. We need this config because we have different base images for Europe/ US and Asia due to language issues.
I found the way how to create tasks through MBSDK.
Now I'm a bit stuck, as I get the task creation going if I start my script in Windows. But when I start the script in WinPE, the task is still created, but no computer name is not communicated, This means that the task has nothing in it and fails.
Do you know a way to communicate the computername so that I can lance a PROVISIONING task in WinPE.
Here is the snippet that I use :
Sub Template_1
Set objWMIService = GetObject( "winmgmts:\\.\root\cimv2" )
Set colItems = objWMIService.ExecQuery( "Select * from Win32_ComputerSystem" )
For Each objItem in colItems
strComputerName = objItem.Name
Next
SoapRequest = "<?xml version='1.0' encoding='utf-8'?>" & VbCrLf &_
"<soap12:Envelope xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xmlns:xsd=""http://www.w3.org/2001/XMLSchema"" xmlns:soap12=""http://www.w3.org/2003/05/soap-envelope"">" & VbCrLf &_
" <soap12:Body>" & VbCrLf &_
" <ScheduleProvisioningEx xmlns=""http://landesk.com/MBSDKService/MBSDK/"">" & VbCrLf &_
" <TaskName>HTA test</TaskName>" & VbCrLf &_
" <templateID>101</templateID>" & VbCrLf &_
" <StartTime>Start Now</StartTime>" & VbCrLf &_
" <Targets>""Computer"".""Display Name"" = """ & strComputername & """</Targets>" & VbCrLf &_
" <reserved></reserved>" & VbCrLf &_
" <deliveryMethod>Standard policy-supported push distribution</deliveryMethod>" & VbCrLf &_
" </ScheduleProvisioningEx>" & VbCrLf &_
" </soap12:Body>" & VbCrLf &_
"</soap12:Envelope>"
Set oHttp = CreateObject("Msxml2.XMLHTTP")
oHttp.open "POST", "HTTP://landeskcore.waters.com/MBSDKService/MsgSDK.asmx", false, "DOMAIN\USER","PASSWORD"
oHttp.setRequestHeader "Host" , "landeskcore.waters.com"
oHttp.setRequestHeader "Content-Type", "application/soap+xml; charset=utf-8; action=""http://landeskcore.waters.com/MBSDKService/MBSDK/ScheduleProvisioningEx"""
oHttp.setRequestHeader "Content-Length", Len(SoapRequest)
oHttp.send SoapRequest
strResult = oHttp.responseText
MsgBox strResult
End Sub
I hope someone has some experience with this....
Best regards, Michael
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!!