Quantcast
Channel: Ivanti User Community: Message List - OS Deployment and Provisioning
Viewing all 3345 articles
Browse latest View live

Mac Netboot Gives Flashing ? Folder

$
0
0

Hello all!

 

I am in the process of setting up a Mac imaging environment for the first time and am running into some difficulties. I have been following the steps for the LANDESK 2017 version of MacOS deployment but so far have not been able to Netboot successfully. Holding down N on boot eventually takes me to a flashing ? folder and initiating a reset/netboot with the Ivanti Management Console just takes me to a black screen before rebooting into the OS. I am not sure what all information you need to help, or if I am even asking the right questions. Any help would be greatly appreciated!!

 

Thanks!

DC


Windows 7 installieren mit WIN PE10

$
0
0

Hallo,

ich versuche verzweifelt mit DSM 2016.2 Laptops mit einer NVMe-Festplatte unter Windows 7 zu installieren.

Ich habe per DSM ein Bootenvirnment WIN PE 10 erstellt. Windows 10 lässt sich auf dem Rechner problemlos installieren. Dann habe ich mit NTLite die besagten DLLs getauscht.

Anschließend sann starte ich die Windows7-Installation mit besagtem Bootenvironment. Die Festplatte wird noch partitioniert, aber danach bleibt die Installation mit einem Fehler stehen. Das Config-package bringt eine Fehlermeldung. Das Windows 7-Image müsste funktionieren, da ich dieses mit einem WINPE10 von einem USB-Laufwerk auf die Hardware installiert bekomme.

Hat mir jemand evl. eine Schritt-für-Schritt-Anleitung was ich genau machen muss?

Wie kann ich setup.exe manuell starten bzw. wo finde ich logfiles um den Fehler einzugrenzen.

 

Bin für jede Rückmeldung dankbar.

Gruß Andreas

Slipping Ivanti Agent into MDT

$
0
0

Hi,

 

We do not want to use the entire Ivanti imaging process but are trying to install the Ivanti agent during the MDT task sequence and have it trigger the System Configuration portion of an OS Provisioning Template to install an Application Bundle of default apps.

 

Is there any known way to accomplish this?

Re: Slipping Ivanti Agent into MDT

$
0
0

If you can get MDT to install a binary, just build a single-file executable version of the agent & slip it into the MDT process ...?

 

Or - at the very least - install the advanced agent, so that we can (through reboots and other nonsense) slowly pull down the full agent & try to install that?

Re: One touch computer setup

Re: Windows 10 Enterprise v1703 is ignoring the computername is unattend.xml

$
0
0

So I recreated the image using then sysprepped using this command:  Sysprep /generalize /oobe

It was based on this note:   https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/boot-windows-to-audit-mode-or-oobe

Note

If you install Windows images by using the Sysprep /generalize /oobe command, the user experience will not be ideal. On the next reboot after you run the Sysprep /generalize /oobe command, Windows runs the specialize configuration pass, Plug and Play, and other Setup tasks before Windows starts OOBE. This process can take additional time and can delay a customer's first logon.

 

I needed to make sure the specialize pass was processed, and this command facilitated that.  Using the GUI didn't seem to do the same thing.

The entire article is here.

 

Boot Windows to Audit Mode or OOBE | Microsoft Docs

[Landesk] Problème déployement via Pxe, Ip reste local

$
0
0

Bonjour,

Nous utilisons Landesk 2016 pour déployer les Os Windows et applications, tout fonctionne correctement.

Dernièrement nous avons reçu de nouveaux ordinateurs portables Hp, nous avons suivi la procédure habituelle via le PXE.

Le début ce passe sans encombre mais la recherche de l'adresse Ip ne renvoi pas d'adresse de notre DHCP mais une IP en local.

Est-il possible que la carte réseau ne soit pas reconnu ? et qu'il faille mettre à jour le Win PE ?

 

Merci d'avance

 

Hello,

We use Landesk 2016 to deploy Windows OS and apps, everything works fine.

Recently we received new Hp laptops, we followed the usual procedure via the PXE.

The beginning goes smoothly but the search for the IP address does not return an address of our DHCP but an IP locally.

Is it possible that the network card is not recognized? and that it is necessary to update the Win PE?

 

thank you in advance

 

Ce message a été modifié par : david Faisant

LanDesk WinPE booting 32bit

$
0
0

Hello,

 

We are testing  Ivanti 2017.3 Console. We use provisioning for deploy computers. We have a problem with Windows 10 deploy that use the setup.exe unattend way to install. The problem is that USB stick load the 32bit version, so it's impossible for us installa a 64bit executable. We have some computer that are quite old, so we need to boot as "legacy" and not as UEFI (I'am told that if you use UEFI the WinPE switch to 64bit). Thanks a lot! F.


Re: LanDesk WinPE booting 32bit

$
0
0

That's correct -- BIOS based devices get provisioned with a 32-bit WinPE (because the "old" stuff tends to work safer that way), whilst UEFI devices get the 64-bit WinPE image assigned to them.

 

So - your hardware determines which provisioning image gets sent by the Core in regular provisioning.

 

Is your question in essence "how can I get a 64-bit PE image on a bootable USB stick" ?

Re: LanDesk WinPE booting 32bit

$
0
0

Dear Phoffmann,

 

yes, we are trying to use it via USB Stick. As I read elsewhere we just copied the boot_x64.wim and renamed to boot.win, the original boot.win has been renamed (boot.win.orig)... this is actually forcing to a x64 enviroment, that we need in order to install Windows 10. The workaround is ugly, but it works. I wonder why Ivanti couldn't make a simple choice at the start... maybe it is, but as you can understand we are very new to the Ivanti world ;-) The next step is test the PXE network enviroment... I don't know if it works the same way... Thanks a lot, again! F.

Re: LanDesk WinPE booting 32bit

$
0
0

"Effectively", it works the same.

 

Essentially, the PXE rep determines "which boot image should I get?", and then goes for that. So if you rename the WIM files, then - yes - that will affect your PXE booting as well.

 

I don't have issues with hacks like this by and large - the only caveat is that I always try to make sure that people don't shoot themselves into their own foot. So - by renaming the WIM-s be aware that even your BIOS devices will try to load the 64-bit WIM ... which CAN cause issues.

 

So - just "be aware" / prepared (and *TEST* ) ... find the "nastiest / oldest" device(s) you can/have, and see how they do ... if they work fine with your hacks, then you should be OK by and large. If anything's going to fail, likely it'd be those devices (and chances are you know exactly the make/model that's causing you the most regular headaches anyway).

PXE Rep not Broadcasting - Can't PXE Boot

$
0
0

All-

 

I'm having some issues with PXE. The PXE rep, regardless of what elected client it is, is not broadcasting as a rep. Sometimes the appropriate services are running, sometimes they aren't and I restart them. Very very strange that this all of a sudden started happening in our environment (I'm not aware of any changes we have made). For about 2 months prior to this issue reappearing, PXE booting and imaging worked great.

 

The first time something like this happened, it resolved itself. When a client would boot and search for reps, it would find a rep but the elected rep would have a randomly generated IP on it's own subnet. This was due to our computers using Cisco Umbrella ODNS as a filtering and traffic monitoring solution. At some point between Cisco updating Umbrella endpoint software and the ivanti core being updated/upgraded to the most current version (2017.3 SU2), the PXE reps started functioning properly.

 

Some notable information:

ivanti 2017.3 SU2 running on Server 2016 Standard

Reps vary from desktop to laptop running Windows 7/Windows 10 version 1703 and 1709

All Dell Optiplex (7010, 5040, 7050) or Dell Latitude (E5480, E5470, E5450, E5440)

Verified Firewall ports are open and allowing traffic to the best of my abilities on both clients and network appliances

Made zero changes to the .wim boot file except update the background

I noticed the .wim images are not replicating with the updated image (followed the troubleshooting on the community with no avail)

Tried PXE reps with and without any security (all of our security products as well as none and dropping the firewall)

*I had noluck whatsoever finding the registry keys to change the score of a PXE rep so it was by happen-chance I was working with the right computers

 

Attached are all of the logs and information I could possibly think of. All help is welcome! I may end up opening a support ticket but thought I'd post on here first. If I remember any other details, I'll be sure to reply with them. Thanks!

 

-Jon

Re: [Landesk] Problème déployement via Pxe, Ip reste local

$
0
0

Hi David,

 

Thanks for posting to the Ivanti Community!

 

Sorry that it seems no one has the answer to be able to assist you on this yet.  Did you manage to get any further information on this? Please share anything you deem useful and the community may be able to offer some help.

 

If not then please do consider the other ways to engage with us to get assistance:

https://community.ivanti.com/community/contact-support

Software Package failed

$
0
0

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.

Re: provisioning actions are not retrieved and provisioning GUI is empty

$
0
0

Hello,

 

Even without Client Certificate-Based Security, the clients will need to authenticate via SSL when interacting with Core Web Services. Broker runs during the Provisioning process in order to get the validation certificate so it can use Web Services such as ServerAuthentication.

 

When the device is failing vs Succeeding, is there a difference in what PXE Representative its getting the WinPE WIM Image from? Its possible you have a PXE Representative with a "Stale" version of the WinPE Image on it that is causing the failures.

 

Thanks

 

Aaron


Copydrivers in Windows 10 1703/1709

$
0
0

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

Re: get randomly error 1163 during Provisioning

$
0
0

It happens when the " mirror driver is not installed". Once installed the problem is solved.

For the installation you have to go to: C:\Program Files\LANDesk\LDClient\setupmirror.exe

Re: Cannot Join Domain or install Agent in Windows 10

Re: How to make provisioning select Drive 1 instead of drive 0

$
0
0

Hello Aaron,

 

thank you for answer.

Actually it's just half of solution, since from my testing came out that it's also necessary to reflect disk1 in command-line parameters on deploy stage.

Re: [Landesk] Problème déployement via Pxe, Ip reste local

$
0
0

no I did not get more information on the subject ...

The other way that you advise me is paying no?

Viewing all 3345 articles
Browse latest View live


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