Quantcast
Channel: Ivanti User Community : All Content - OS Deployment and Provisioning
Browsing all 1803 articles
Browse latest View live

Image may be NSFW.
Clik here to view.

Error: "The user name or password specified is not correct" when...

Issue Receiving the error "The user name or password specified is not correct.   Provide new credentials" when authenticating using the Provisioning Client UI.  Cause First, double-check that the...

View Article


Image may be NSFW.
Clik here to view.

How to Deploy an Image to Multiple Computers Using Multicast

This document describes how to deploy an image to multiple computers using multicast. LANDESK Provisioning can take advantage of a feature called "self-organizing multicast".  Please review this...

View Article


Image may be NSFW.
Clik here to view.

How to distribute software using "Run from source" OS Provisioning

Issue How to installed software using "Run from source (execute on share)". Resolution Open the Agent Settings Tool under the Configuration or Security and Compliance tool groups.Select Distribution...

View Article

Image may be NSFW.
Clik here to view.

Failed to download (C:\ldprovisioning\SDClientHandler.sig)

When using provisioning packages for complex software deployments, I am seeing an issue where some of the devices are failing to install any of the software packages that I have included in the...

View Article

Image may be NSFW.
Clik here to view.

Ivanti 2017.3 Provisioning problem with map/unmap drive to preferred server

HI All After Upgrade from Ivanti 2017.1 to Ivanti 2017.3 We have a problem with Map / Unmap drive to preferred server     Previously everything workedThere are no errors in the logdo you have any idea?...

View Article


Image may be NSFW.
Clik here to view.

Error: "68" during deploy image action in Ivanti Provisioning

Issue When running a provisioning template, the template fails on the Deploy Image action. This occurs in Windows PE when running imagew.exe. The error is "68".The full error is "-2147477501". Error as...

View Article

Issue: Ivanti Antivirus or Policy Invoker Services not installing during OSD...

Issue Ivanti Antivirus or Policy Invoker Service is not installing with the agent during the sysprep process on OS deployment Cause The network drive to the LDLogon folder is being deleted before the...

View Article

Image may be NSFW.
Clik here to view.

Error: PXE-E74 bad or missing PXE menu and or prompt information

IssueThe following error occurs when attempting PXE boot:PXE-E74 bad or missing PXE menu and or prompt information             This issue can be caused by a variety of different problems.  The...

View Article


Image may be NSFW.
Clik here to view.

How to add drivers to WinPE for Ivanti EPM OS Provisioning

DescriptionResolutionDescription In order to perform imaging in Ivanti Endpoint Manager, the WinPE image used during the imaging process must contain drivers for devices such as the network adapter or...

View Article


Issue: OSD.Upgrade.exe error during installation

DescriptionCommon errors and descriptionError: "Access Denied"Error: "CommonCore.inf: (0xFFFFFFFF) OSD.Upgrade.exe,60000"Error: "DirectoryNotFoundException"Error: "Non-fatal error: FilterUnload failed,...

View Article

Image may be NSFW.
Clik here to view.

How to change the WinPE wallpaper

Issue The WinPE wallpaper can be changed to allow for branding or customization. Resolution The WinPE wallpaper can be modified using the following steps: From the Ivanti Endpoint Manager Console to...

View Article

How To: Troubleshoot Provisioning Template Action Handlers

DescriptionCore LogsClient LogsSteps to disable removal of the client provisioning folderUnderstanding Action Handler Flow (Client)Action Handler LogsRelated Video: How to Troubleshoot Provisioning...

View Article

Image may be NSFW.
Clik here to view.

Error: PXE-E21: "Remote boot canceled" when PXE booting

Issue Booting a machine in UEFI mode in a network segment with an active PXE representative doesn't make the machine load WinPE.The PXE menu doesn't appear.The machine reports the error PXE-E21: Remote...

View Article


Issue: Provisioning and OSD fail after enabling FIPS on the core server

Issue After enabling FIPS on the core server, Provisioning templates stop working. If you select a Provisioning template to execute, it will attempt to run but will fail with error 80001803H Cause This...

View Article

About Ivanti Support for Unattend.XML

Question: I am attempting to use an Unattend.xml as part of my Ivanti EPM Provisioning job. What support does Ivanti offer for troubleshooting or customizing my unattend.xml? Answer: Ivanti provides a...

View Article


Image may be NSFW.
Clik here to view.

Does anyone know this fix for this?

2017-11-10 16:38:40(2856-2828) ldProvision.exe:The file (C:\ldprovisioning\ApplyDrivers_x64.exe) was successfully downloaded2017-11-10 16:38:40(2856-2828) ldProvision.exe:Looking for existing file...

View Article

Image may be NSFW.
Clik here to view.

ldprovison.exe This app can't run on your PC

LDMS 9.6 SP3 Hi, I get this error while trying to provision a machine.   Any ideas?Best.

View Article


Default unattend.xml why two time sysprep

Dear collegues. I'm starting these provisioning phases with landesk. Befor capturing an image i do sysprep and i turn my pc off. ( I start this command C:\Windows\System32\Sysprep\sysprep.exe /oobe...

View Article

HII Driver Provisioning Conundrum

Hello all, We are using Ivanti Management Console 10.1.10.287 to provision images to our brand new Dell 7480s. They were mistakenly shipped to us with win7 instead of win10. Unfortunately our WinPE...

View Article

Image may be NSFW.
Clik here to view.

Ivanti 2017.3 Provisioning problem with map/unmap drive to preferred server

HI All After Upgrade from Ivanti 2017.1 to Ivanti 2017.3 We have a problem with Map / Unmap drive to preferred server     Previously everything workedThere are no errors in the logdo you have any idea?...

View Article
Browsing all 1803 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>