Hi Team,
After we send a scheduled task to the LANDesk client portal, it is visible fine immediately after the push, but is disappearing from the client portal after some time. Kindly provide a resolution if this is a known issue. Please let us know for any queries. Thanks.
I'm trying to provision a Dell 7390 2 in 1 laptop. I can hit the pxe but right after it loads the boot64 wim I get a blue screen with the error kernel_security_check_failure. I added the SATA drivers into the winpe but that didn't seem to help. Has anyone seen this before?
For so many years, I've been seeing LANDESK/Ivanti touting their ability to have one template for all provisioning scenarios. For the most part, this is true. But, I am falling short of their nirvana because of OU joining.
Currently, we have 12 OU's that our PC's can land in and I have to maintain 12 separate templates that join the machines to these OU's. I am doing the OU join in the unattend.xml during sysprep processing, not the join domain action in the system configuration pass of the provisioning template.
I have been working on a batch file to run at the beginning of the provisioning process that will prompt the tech to enter the destination OU. What I need to figure out is how to have this batch file write to the template variable, say %destination_ou%, that gets resolved when the inject script action injects the unattend.xml file.
ie: <MachineObjectOU>OU=%destination_ou%,OU=Managed Computers,DC=COMAPANY,DC=CORP</MachineObjectOU> gets resolved to <MachineObjectOU>OU=MyOU,OU=Managed Computers,DC=COMPANY,DC=CORP</MachineObjectOU> after the unattend.xml is injected.
Even if I were to use the join domain action in the system configuration pass, I would still need a way to pass the user input to the provisioning variable. When testing to see the template variables, I can't see them in WinPE, such as %ldhostname% which gets set as a database variable in the template. From a cmd prompt in WinPE, echo %ldhostname% shows %ldhostname% when echo %path% gives me C:\Windows\system32;C:\Windows;C... etc.
Does anyone know of a way this can be done?
Thanks.
EPM 2017.3 SU2
I have been testing at work configuring Dell OptiPlex without HII when imaging with Windows 10 1709. I noticed it has saved a lot of time during the imaging process. Is this a good practice to follow or should I keep HII in the provisioning template?
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
I am using LD Management Suite v. 9.6 SP2. I have captured a Win 10 image and i'm trying to redeploy it to a computer using Sysprep. With my Win 7 images i have always used the %ldHostname% variable inserted into my sysprep file...which seems to work just fine. With this new Win 10 image I cannot seem to get it to rename the computer successfully. It just generates a random name instead. I have tried using %ldDeviceID% and %ldDisplayname% but i have had no luck with it.
Does anyone know how to successfully re-name a machine that has Win 10 on it. I do know about the device name prompt that lets you change the name on the fly. But that is not feasible in a 40 computer lab. I need the process as automated as possible.
any help would make my boss happy.
jeff
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.
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
I am running 2016 SP3.
New computer out of the box. Set it up and captured image.
During deployment it deploys image then fails next step Auto Assign Partitions, then Fails Inject unattend, then Ctos.
Never had one fail this before.
Ran Provisioning again but put a wait state after image deploy and after Auto Assign partitions. After deploy image I went in to a command prompt and attempted to do a C:
I got a message about bitlocker. I did not turn on bitlocker before capturing image.
Since the image was layed down on the hard drive I booted to the hard drive (Windows 10 Pro ver 1709) Went into control panel - bitlocker and it says awaiting to turn bitlocker on with a caution sign. Below it says Bitlocker off. In Computer Management C drive says bitlocker.
Any thoughts on how this is happening?
Hallo!
Ich muss die OS-Installation von herkömmlichen PXE-Server auf LANDesk-PXE portieren, aber es funktioniert nicht. Die Dokumentation ist auch irgendwie lückenhaft. Vielleicht kann mir jemand, der schon OS-Verteilung über LANDesk praktiziert, auf die Sprünge helfen.
Im DHCP-Server habe ich Option 66,67 deaktiviert und eine 43 so konfiguriert, dass der LANDesk-Server gesucht und auch gefunden wird.
Wenn der Client aber dann das PE-Bootimage sucht, schlägt es fehl mit der Fehlermeldung: "Could not locate boot server".
Das ist aus meiner Sicht auch logisch, da auf dem LANDesk-Server kein Bereitstellungs-Dienst läuft.
Ich habe den "Selbstwahldienst für Subnetz" aktiviert und konfiguriert.
Ich habe die Preboot-Einstellungen vorgenommen. Dabei ist mir aufgefallen, dass ich zwar das Bootmedium erstellen kann, aber es gibt keine Aktivierungs- oder Bereitstellungs-Option.
Was muss ich also noch tun, um dem anfragenden Client die Möglichkeit zu geben, das Start-OS zu laden?
Vielen Dank im Voraus
Frank
Install mapped software
Hallo Profis!
Ich habe ein Problem beim mapped Software Installation. Ich habe, wie in der Anleitung (Doku) steht alles gemacht.
Software Monitoring gemacht und Pakete zugewiesen.
Hello professionals!
I have a problem with mapped software installation. I've done everything as described in the manual (Docu).
Software Monitoring and assigned packages.
Template (Testweise) erstellt.
Template (for testing purposes).
Computerzuordnung gemacht.
Computer assignment.
Funktion Start.
Function Start.
Ergebnis.
Result.
Inventar habe ich überprüft und bei einigen Tests extra angestoßen.
Was mache ich falsch?
Mit freundlichen Grüßen.
I checked the inventory and toasted it during some tests.
What am I doing wrong?
With kind regards.
It seems like provisioning history is lost when the bare metal record is cleaned up as a duplicate ID. is there a way to preserve that history after provisioning is completed?
LDMS 9.6 SP3
Hi, I get this error while trying to provision a machine.
Any ideas?
Best.
Is this possible?
Hello,
So, I have a laptop here that when I set the HII drivers to the ones provided by the hardware vendor... Landesk goes off and does it's own thing and grabs drivers that are incorrect and proceeds to brick the laptop.
I have tried following the steps here:
How to use HiiClient in Preview Mode
But have gotten no where seeing as the HIIclient.exe file is not in the LDprovision directory.
So, can anyone point me in the direction of telling LanDesk what devices are on these laptops and then force it to install the right drivers instead of the shell game it currently is employing?
Thanks,
Matt
Imaging a device with a LANDESK Management Agent installed can cause the devices that receive the image to overwrite each other in the database.
LANDESK inventory looks at a Unique ID/Device ID when inserting the scan. This ID is created when the agent installed on the device.
Important:
It is strongly recommended that the LANDESK agent not be included in an image. The recommended way to install the LANDESK Agent with imaging is to use LANDesk Provisioning and include a Configure Agent action in your provisioning template. Besides causing duplicate devices, the LANDESK agent is often updated and adding it to the image will quickly cause your image to be outdated.
This method is NOT a supported process.
If the agent must be included in an image or Non-Persistent VDI image, the unique identifiers must be deleted out of the registry prior to the capture of the image. Before creating an image of the machine do the following:
LANDesk Management Suite 9.0 and later
HKLM\SOFTWARE\Intel\LANDesk\Common Api\UniqueID
HKLM\SOFTWARE\LANDesk\Common Api\UniqueID
HKLM\SOFTWARE\LANDesk\Inventory\LogonHistory\Logons
HKLM\SOFTWARE\LANDesk\ManagementSuite\WinClient\SoftwareMonitoring\MonitorLog contents
Delete the following Registry Keys for 64 bit clients:
HKLM\SOFTWARE\Wow6432Node\Intel\LANDesk\Common Api\UniqueID
HKLM\SOFTWARE\Wow6432Node\LANDesk\Common Api\UniqueID
HKLM\SOFTWARE\Wow6432Node\LANDesk\Inventory\LogonHistory\Logons
HKLM\SOFTWARE\Wow6432Node\LANDesk\ManagementSuite\WinClient\SoftwareMonitoring\MonitorLog contents
3. On Windows XP, delete C:\Documents and Settings\All Users\Application Data\LANDESK (delete the entire directory and subdirectories)
4. On Windows 7, 8, and 8.1, delete C:\ProgramData\LANDesk (delete the entire directory and subdirectories)
In addition, it is a good practice to ensure that the image does not contain any DRIVERS.DB3 file.
See Community discussion for additional tips and information:
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 template. After closer inspection, I can see that none of the files for the software packages in the template are being downloaded, so when it tries to execute, it fails immediately. I found an error in the ldprovisioning.log file -> Failed to download (C:\ldprovisioning\SDClientHandler.sig) <- that appears to be the issue, but I'm not sure how to go about resolving this. Wondering if anyone else has seen this, or has any ideas how to troubleshoot further? LDMS 2016.3 SU3
2017-11-07 16:41:00(8660-4724) ldprovision.exe:Looking for existing file (C:\ldprovisioning\SDClientHandler.sig)
2017-11-07 16:41:00(8660-4724) ldprovision.exe:Entering downloadbyproxy.
2017-11-07 16:41:00(8660-4724) ldprovision.exe:Create process (C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe) with args ( -f "C:\ldprovisioning\SDClientHandler.sig" http://mylandeskserver.com/LdLogon/Provisioning/windows/SDClientHandler.sig)
2017-11-07 16:41:01(8660-4724) ldprovision.exe:Waiting for process result: 0.
2017-11-07 16:41:01(8660-4724) ldprovision.exe:Process exit code:-1
2017-11-07 16:41:01(8660-4724) ldprovision.exe:Failed to download (C:\ldprovisioning\SDClientHandler.sig)
2017-11-07 16:41:01(8660-4724) ldprovision.exe:Informational: No sig file downloaded.
2017-11-07 16:41:01(8660-4724) ldprovision.exe:Done with download handler.
2017-11-07 16:41:01(8660-4724) ldprovision.exe:Launching action handler [SDClientHandler.exe] with parameters ["]
2017-11-07 16:41:04(8660-4724) ldprovision.exe:handler launched.
2017-11-07 16:41:04(8660-4724) ldprovision.exe:End of action - Distribute_software
2017-11-07 16:41:04(8660-4724) ldprovision.exe:Reporting action status: 5 to core.
We have a vendor who builds our devices for us and has a Ivanti replication server in the warehouse connecting over a VPN back to our head office and core server.
Our vendor is able to build new devices with no issues at all, if they build a device that has been seen by Ivanti before it will never be offered a PXE offer.
We have checked our inventory for the MAC address of these devices, and they do not ever appear in the Network view.
We have also check we have selected under PXE boot options, Always PXE boot UEFI devices.
I believe the issue is related to Ghosting in the database, but do not know how to investigate this. My guess would be that the MAC address is stored somewhere in the Ivanti database, and cannot be viewed in the console.
We are using Ivanti Management console 2017.1
Our devices are all UEFI with secure boot with UEFI network stack enabled.
We do not experience this issue here in head office.
I want to know how to deploy MDT from Landesk. Is it possible and how do i do that. Thanks
We're doing some comparisons with variables and db values during our provisioning processes and workflows, but obviously if it wasn't previously in IEM, it has no inventory records. It also doesn't seem to check 'on the fly', so this is resulting in some issues with our provisioning processes and workflows. I recall someone saying at Interchange last year that they were able to do a mini-inventory scan in PE and submit that to the core as part of their process while in PE, which then gave them the data for such use, but I don't see anything on this in the discussions/forums here. Can anyone share how they've done this?
Thanks!
Jey Bailey
Technology Support Specialist
Bucknell University