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

About Windows PE versions used in Ivanti Endpoint Manager

$
0
0

 

Description

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.

 

Ivanti Endpoint Manager 2018.1

  • EPM 2018.1 uses WinPE 10.0.15063.x and requires Windows 10 drivers

 

Ivanti Endpoint Manager 2017.3

  • EPM 2017.3 uses WinPE 10.0.15063.x and requires Windows 10 drivers

 

Ivanti Endpoint Manager 2017.1

  • EPM 2017.1 uses WinPE 10.0.10240.x and requires Windows 10 drivers

 

LANDESK Management Suite 2016.3

  • LDMS 2016 uses WinPE 10.0.10240.x and requires Windows 10 drivers

 

LANDESK Management Suite 2016

  • LDMS 2016 uses WinPE 10.0.10240.x and requires Windows 10 drivers

 

LANDESK Management Suite 9.6 SP3

  • LDMS 9.6 SP3 uses WinPE 5.0, requiring Windows 8.1 drivers, the same as LDMS 9.6 SP2

 

LANDESK Management Suite 9.6 SP2

  • LDMS 9.6 SP2 uses WinPE 5.0, requiring Windows 8.1 drivers, the same as LDMS 9.5 SP3


Determining your WinPE version

 

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 VersionPE VersionDerived From
WinPE 1.55.1.xWin XP SP2
WinPE 2.06.0.xVista
WinPE 3.06.1.7600.xWindows 7
WinPE 4.06.2.xWindows 8
WinPE 5.06.3.xWindows 8.1
10.0.10240.x10.0.10240.xWindows 10 1511
10.0.15063.x10.0.15063.xWindows 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:

NDIS Versions in Network Drivers (Windows Drivers)


Computer Name prompter

$
0
0

EPM 2017.3

 

Is it possible to load the provisioning task and run it from a USB?

Answer:Disconnected Template Best Practices

 

 

Also, does anyone know how the Computer Name Prompter works? is this a stand alone app that I can use?

 

Best Regards,

UEFI Device will not PXE Boot after going through provisioning once already

$
0
0

So I have a test device in which I am testing all stages of deployment and for a while the Unattend file was failing and I couldnt get past the inject unattend file. I got that sorted and the machine provisioned correctly apart from it failed to install the LANDesk Agent. However now when I got to PXE boot the machine it just hangs for a second and then returns me back to the boot menu along with 1 beep.

 

I have tried this on multiple machines but once they have been provisioned once already I am unable to pxe boot them again. Does anyone have any idea what is going on?

 

SeanNye please add anything as a reply that I may have missed.

OSD bleibt im Status "Waiting".

$
0
0

Hallo Community,

 

ich habe momentan ein Problem bei der Neuinstallation eines Notebooks. Sobald ich das OSD starte bleibt es bei Pending stecken. Ab einem gewissen Punkt überspringt er die Neuinstallation und installiert die vorgesehene Software.

Andere Computer oder Notebooks machen keine Probleme. Ich kann mich über Ivanti auf das Notebook schalten und auch pingen.

Ich hoffe ihr habt Lösungsansätze wie ich das Problem beheben kann.

 

Vielen Dank

MaptoPreferredHandler.exe failing with error 100001

$
0
0

MaptoPreferredHandler.exe failing with error 100001, started this week. The MaptoPreferredHandler.log shows it is trying to use http:// for path which causes the failure. This only occurs on Win10, Win 7 works fine path used is UNC... Anyone have any ideas? Also Our Production core does not have this behavior and nobody is admitting to any changes.

 

Runnning LDMS 9.6 SP2 Sustaining Patch 1223I

 

2016-05-04 15:13:37(6448-6452) MaptoPreferredHandler.exe:******Mapping to: \\KOESAPPN150\LDShares

2016-05-04 15:13:37(6448-6452) MaptoPreferredHandler.exe:Drive letter = M

2016-05-04 15:13:37(6448-6452) MaptoPreferredHandler.exe:Mode - Require preferred server.

2016-05-04 15:14:05(6448-6452) MaptoPreferredHandler.exe:Could not map or unmap drive. Error code: 100001

2016-05-04 15:14:05(6448-6452) MaptoPreferredHandler.exe:End of Map Drive.  Path used: - http://ROCLDP4124.ekc1.ekc.kodak.com/LDShares/.

Provisioning finished email to the deployment user

$
0
0

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 an deployment username variable.

 

Regards,

 

Thomas

Dell Optiplex 7060 PXE boot issues.

$
0
0

Post converted to PDF and attached for Migration.

OSD task fails after Reboot action executed

$
0
0

Post converted to PDF and attached for Migration.


Dell 7470 HII assignments - Windows 10

$
0
0

Post converted to PDF and attached for Migration.

Partitions not being expanded during imaging

$
0
0

Post converted to PDF and attached for Migration.

Provisioning hang

$
0
0

Post converted to PDF and attached for Migration.

Need Help with capturing an image

$
0
0

Post converted to PDF and attached for Migration.

Provisioning template-System Config-Distribute software

$
0
0

Post converted to PDF and attached for Migration.

PXE-E53: no boot filename received - when trying to PXE boot to upload a syspreped image -Documented fix doesn't work

$
0
0

Post converted to PDF and attached for Migration.

Landesk 9.5 sp1 Hii Best Practices

$
0
0

Post converted to PDF and attached for Migration.


HII not working in provisioning template

$
0
0

Post converted to PDF and attached for Migration

Need some help with Windows 10 Unattend xml file. Why am I getting duplicate accounts?

$
0
0

Post converted to PDF and attached for Migration.

H.I.I. cannot find network drivers for Dell T7910

$
0
0

Post converted to PDF and attached for Migration.

Run a script during provisioning

$
0
0

We have a PowerShell script that I need to run during provisioning after the device has joined the domain.

 

I have copied this script to a folder on the local device and then used execute file in the provisioning tasks to run the script.

 

My question is under what context does that script now run?

 

Is it local system?

 

The script runs but hangs and when I run this locally it has access denied.  I have found that I need to run PowerShell elevated for the script to run.  Is there a way to do this during the provisioning task?

 

Or do I need to do some PS jiggery pockery to get it to run elevated?

 

Any thoughts welcome.

Software installations fail during provisioning. Return -1918091226, Code 16422, error 8dac4026h

Viewing all 1803 articles
Browse latest View live


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