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

Move into a specific OU

November 15, 2017, 3:25 am
$
0
0

Hello,

 

we are using the LANDESK MANAGENET SUITE 2017.

 

When I deploy a new computer with OS and APPLICATIONS, I can choose between laptop or workstation.

After 5 minutes the computername is automatically.

The computer itself is located in the OU COMPUTERS after AD join.

 

Now my question.

Is it also possible to move the computer to another OU when deploying it ?

In our AD we have several locations for our computers, not only one.

Is it possible to build a function like my previous with the computername ?

The provisioning stopps and wait for 5 minutes, I can choose the OU, then provisionig goes on.

After 5 minutes the computer will be put automatically to computers OU.

 

Is this possible ?

↧
Search

Provisioning never launches - Failed to call web service

October 17, 2016, 10:38 am
$
0
0

I have 3 laptops that won't launch provisioning. If I try to launch it manually, I see the error "WebServiceCall" returned. Provisioning is working fine for all other computers. I initially thought it was a hardware issue, but can't find anything wrong with them.

 

Here is the relevant info from the ldprovision.log on the client:

 

2015-08-12 06:16:56(1160-1156) ldProvision:download prerequisite files OK

2015-08-12 06:16:56(1160-1156) ldProvision:Running in Daemon mode.

2015-08-12 06:16:56(1160-1156) ldProvision:Provision Mode = PROVISION_MODE_CORE_SID

2015-08-12 06:16:56(1160-1156) ldProvision:Copy the headers off

2015-08-12 06:16:56(1160-1156) ldProvision:Start TryallWebService Attempt:0.

2015-08-12 06:16:56(1160-1156) 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

2015-08-12 06:16:56(1160-1156) ldProvision:End TryallWebService Attempt:0. ExitCode:2

2015-08-12 06:17:02(1160-1156) ldProvision:Start TryallWebService Attempt:1.

2015-08-12 06:17:02(1160-1156) 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

2015-08-12 06:17:02(1160-1156) ldProvision:End TryallWebService Attempt:1. ExitCode:2

2015-08-12 06:17:07(1160-1156) ldProvision:Start TryallWebService Attempt:2.

2015-08-12 06:17:07(1160-1156) 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

2015-08-12 06:17:07(1160-1156) ldProvision:End TryallWebService Attempt:2. ExitCode:2

2015-08-12 06:17:19(1160-1156) ldProvision:Failed to call web service. exitCode=2

2015-08-12 06:17:19(1160-1156) ldProvision:Caught exception in main: code=80001500H, file=ProvisioningWebSvc.cpp, line=1080

 

Any suggestions? Thanks.

↧
↧

Clients wont elect themselves as PXE rep in 2016.3

May 16, 2017, 6:08 am
$
0
0

Hi Everyone,

 

I recently upgraded my core server to 2016.3 and I'm struggling to get a client computer to elect itself as pxe rep.

 

Here is what the SelfElectController.log file has:

Tue, 16 May 2017 07:59:32   CSEP_Enabled = true  XDD_ARP_PromoteDesktops = true  Services Enabled:  XDD_ARP : PXE_SVC

Tue, 16 May 2017 07:59:32 SelfElect::GetInterfaceInfoList - Incorrect response message type 102

Tue, 16 May 2017 07:59:33 SelfElect::WhoProvidesService - Incorrect response message type 108

Tue, 16 May 2017 07:59:48 SelfElect::GetInterfaceInfoList - Incorrect response message type 102

Tue, 16 May 2017 07:59:48 SelfElect::WhoProvidesService - Incorrect response message type 108

Tue, 16 May 2017 08:00:04 SelfElect::GetInterfaceInfoList - Incorrect response message type 102

Tue, 16 May 2017 08:00:05 SelfElect::WhoProvidesService - Incorrect response message type 108

Tue, 16 May 2017 08:00:20 SelfElect::GetInterfaceInfoList - Incorrect response message type 102

Tue, 16 May 2017 08:00:20 SelfElect::WhoProvidesService - Incorrect response message type 108

 

Has anyone had this before? If so, how do I fix it?

 

Thanks!

↧

How to capture User Profiles Using LANDESK Provisioning - Video

December 10, 2014, 1:23 pm
$
0
0

This video demonstrates how to capture a profile using a provisioning template.

 

Click HERE to play in a separate browser window (You can maximize the video if you use that link)

 

↧

Provisioning Action: Agent Install Fails When Last Action In WSCFG32.Log Is Running SCSDiscovery.exe

October 11, 2017, 7:15 am
$
0
0

Error message:

The error message is located in the agent install log (C:\ProgramData\LANDesk\Log\wscfg32.log). The last message in the log will look like so:

 

Tue, 12 Sep 2017 09:32:59 INI:  EXEC49=C:\Program Files (x86)\LANDesk\LDClient\SCSDiscovery.exe, /Output Silent SystemDiscovery /NoFile, NOWINDOW + INSTALLONLY

Tue, 12 Sep 2017 09:32:59 Starting process: C:\Program Files (x86)\LANDesk\LDClient\SCSDiscovery.exe /Output Silent SystemDiscovery /NoFile

The agent install will be hung from that point on.

 

Cause:

SCSDiscovery.exe Is used to determine if the device is vPro capable. The device may not be ready to run that EXE and it may not have access to the DLL's it needs to determine vPro functionality. This is usually because the OS is booting up for the first time and goes through additional configuration on the initial boot.

 

Solution / Workaround:

Add a 200 second wait (This time can be adjusted as needed) as the first action is System Configuration. This will allow the OS to go through it's initial configuration/OS setup. In general, it's a good idea to put a wait at the beginning of System Configuration to allow the OS enough time to boot properly.

 

WaitForMe_ImNotReadyQuiteYet.png

↧
↧

how to configure DHCP server or Router to have Landesk as a PEX server

November 15, 2017, 10:05 am
$
0
0

Currently, we have a Windows WDS as our PEX server and set up ip helper on routers virtual interface. It works 75% times that sometimes with PEX server not found/time out errors. I found out that Landesk has a built in function for PXE boot. That's why we are moving this approach to make Landesk 2016 as a PXE boot server.   I would like to know how to configure DHCP server or Router to have Landesk as a PEX boot server without any PEX representative on each subnets. 

Correct me wrong, from my understanding about PXE Representative, it needs to have at least one one each subnet. If the PXE Representatives are down on this subnet, you will lose you PEX boot option on this subnet. If this is right, I don't want to have more administrative time to manage those PXE Representatives.

So, I need to configure my DHCP server with option 43 and 60 set, can someone explain a little more on detail with examples? From the documentation How to configure DHCP to work with LANDESK PXE boot , it said not option 66 and 67, if you are using Landesk PXE boot.

if I set ip helper on routers virtual interface, is this a better option?

Pro and Con on each configurations?

↧

stuck in running configure agent

November 26, 2017, 9:15 pm
$
0
0

Hi, Guys,

 

I met a problem when deploying image on MAC.

After netboot by network, chose the template, it will stuck in running configure agent, never will finished or failed message.

The log on the core server will show:

 

VERBOSE ProvisioningWebService 11/27/2017 12:52:00 PM : GetDeviceNaming for DeviceID 1015

VERBOSE ProvisioningWebService 11/27/2017 12:52:00 PM : DeviceNaming for DeviceID 1015 returned:

 

The template history displayed

 

 

But if reboot by USB flash, it will finished successfully .  The log on the core server are as below:

 

VERBOSE ProvisioningWebService 11/27/2017 11:47:21 AM : DeviceNaming for DeviceID 1015 returned:

VERBOSE ProvisioningWebService 11/27/2017 11:48:24 AM : SetActionStatus (historyTaskIdn 704, historyEntryIdn 4362, next 4363): state SUCCESS

VERBOSE ProvisioningWebService 11/27/2017 11:48:28 AM : SetActionStatus (historyTaskIdn 704, historyEntryIdn 4363, next 4364): state REBOOTING

 

Hope someone can help me to solve this problem. Many thanks!

↧

Task sequence stops as USB network adapter not installed in Windows 10

November 28, 2017, 5:03 am
$
0
0

I have some HP X2 210 devices.

 

As they are tablet / laptop hybrids they are a bit short of inputs so don't have a network socket.  So I have to use a HP USB network adapter.  This all works fine and the task sequence starts.

 

The OS is installed, the drivers are installed etc until the first reboot into the OS where it would normally continue and install the Ivanti Agent and all the apps etc.

 

However at this point nothing happens as it seems that the USB network adapter isn't found and installed.

 

But I can continue the task sequence if I remove and reinsert the USB network adapter.  Windows 10 picks it up instantly as the drivers are there (injected earlier in the task).  The task sequence continues.

 

I really want the USB adapter to be picked up when the device restarts and the task sequence to continue normally without manual intervention.

 

Can anyone help?

 

Cheers

 

 

 

Phil.

↧
Search

UEFI Boot LANDESK Management Console

November 28, 2017, 9:18 am
$
0
0

I am new to Landesk and I am having an issue setting up UEFI.  As I have been searching around for solutions, I have seen that on the Management Console under provisioning/OS Provisioning/preboot/pxe boot options there is an option to enable uefi booting.  However I don't see that on our management console.  Am I not on a version that the feature was enabled?  Is it something that the company I work for would need to buy?  I am on version 10.0.0.271 and attached is what I see.  Thanks for the feedback!

↧
↧

Injecting drivers to boot64.wim using Dism fails with an error

November 29, 2017, 5:53 am
$
0
0

I'm on Landesk 9.6 SP3

I have a new model Dell 5050 that boots to PXE but errors out with 127.0.0.1 when going into Winpe. Research says I need to inject nic driver into Winpe.

However I have tried adding driver through Landesk, Manage drivers in Winpe, and it doesn't fix the problem. Now I'm trying to inject into bootx64.wim using Dism and it fails with a error. Googling the error leads me nowhere.

Any suggestions?

↧

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

November 8, 2017, 12:24 pm
$
0
0

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.

↧

Need Help with default profile settings and unattend file

November 29, 2017, 12:42 pm
$
0
0

Hello All,

 

I am a novice at best when it comes to unattend files. I have currently built out my image using an unattend file provided to me. The last thing I am missing is copying over default user settings/default user profile for my image. I want to use the settings from my local admin account. Settings I want copied over include default apps, pinned task bar programs, start menu settings and privacy settings.  We are working in a Windows 10 environment. Any help with the following questions is appreciated:

 

-Do I need to do anything before sys prepping the image?

-What do I need to do with my unattend.xml file in order to copy and enable the local admin as the default user account.

 

Thanks,
Brian

↧

Choose OU for computer object

July 18, 2017, 9:16 am
$
0
0

Hi,

 

Hope someone will be able to help.

 

I'm creating a Windows 10 imaging routine and would like to be able to choose an OU in which the AD computer object of the machine being imaged would be created. So, the engineer building a machine has the option to place the computer in an OU that's relevant to the hardware type (desktop/laptop) and the machine's function in the business (Finance, Marketing etc).

 

Are there any menu-driven/choice options out there where the user can select the OU in which the computer object will be created? If that solution also takes into account that a (Windows 7) computer with the same name may already exist in AD - so much the better.

 

Thanks in advance,

 

Matt

↧
↧

NBI Disk Stamper Error: The NBI OS version is different than the agent OS version

November 29, 2017, 11:55 am
$
0
0

Issue:

When stamping your NBI with the Ivanti Startup Disk Stamper you are unable to click create and get a message that "the NBI OS version is different than the agent OS version.", as seen below.

 

NBI1.PNG

 

Cause:

The cause of this message is that the NBI Source (the installer placed in the applications folder to create the NBI) and the Agent Source (OS of the machine that is used to create and stamp the NBI) does not match.

 

MisMatch.PNG

 

As you can see the main version of the OS is the same, however the update version is mismatched which is what is causing the message and the create button to be grayed out.

 

Solution:

The best way to ensure the versions match is to download your installer first. Then use that to install the OS on the machine you plan to create the NBI on, make sure you do not update the OS then create your NBI and stamp it. Most users end up with issues because the first thing they do is update the OS and in this case is causing the issue.

↧

LANDesk Bare Metal Provision with Serial Number as UID

December 1, 2017, 2:26 am
$
0
0

Hi guys, just wondering if anyone else is having the same issues I am with Bare Metal provisioning of devices with the Serial Number as the Unique Identifier?

 

We are running LANDesk 2016.3 SU5 and trying to deploy devices, especially Surface Pro 4s, which use a shared network adaptor; in this case a Surface Pro 4 dock. That means using the MAC address as the main unique identifier is out, otherwise each new device will wipe out the inventory record of the previous device, and/or the new device tries to use the device name of the last provisioned device.

 

PXE booting is working ok. I have un-ticked everything except 'Serial Number' from 'Machine unique identifying attributes' in 'Provisioning Settings' under Operating system provisioning'.

 

I add the device under Bare Metal Devices, using the Surface Pro 4's serial number (in the BIOS) as the unique identifier.

I boot into WinPE and choose my task sequence to deploy Windows 10, and the first action is 'Device Name Prompt'.

The Device Name Prompt comes up with the ldHostname of the previous Surface Pro 4 I provisioned yesterday.

 

If I try deleting the Bare Metal entry and re-start the task-sequence, it runs through 40 of 40, then on the second retry again picks up the ldHostname of the previous device.

 

Any thoughts/help?

↧
Search

Move into a specific OU

November 15, 2017, 3:25 am
$
0
0

Hello,

 

we are using the LANDESK MANAGENET SUITE 2017.

 

When I deploy a new computer with OS and APPLICATIONS, I can choose between laptop or workstation.

After 5 minutes the computername is automatically.

The computer itself is located in the OU COMPUTERS after AD join.

 

Now my question.

Is it also possible to move the computer to another OU when deploying it ?

In our AD we have several locations for our computers, not only one.

Is it possible to build a function like my previous with the computername ?

The provisioning stopps and wait for 5 minutes, I can choose the OU, then provisionig goes on.

After 5 minutes the computer will be put automatically to computers OU.

 

Is this possible ?

↧

PXE not working after adding drivers

December 1, 2017, 5:33 am
$
0
0

Hello,

 

I really have a problem with PXE boot now.
I have new clients from Lenovo and I have added the drivers from the PREBOOT menue in the IVANTI Management Console.

 

But now the whole PXE boot process is broken.

 

Any ideas to solve it ?

↧
↧

Mac Provisioning Questions

September 21, 2017, 12:38 pm
$
0
0

I have a few questions and problems with Mac provisioning. We are currently using LD 2016.3 SU3. Our NetBoot image is based on macOS 10.12.6.

 

1. Do preferred servers work with Mac provisioning, or do I need a separate template for each of our locations?

2. Does NetBoot work with preferred servers? We have our NBI hosted on our source preferred server which is defined in "Mac Netboot Image Mappings". This is replicated to our preferred servers at each location with a matching HTTP share. NetBoot seems very slow at all locations, almost like it's downloading over the WAN.

3. Is there a way to prevent the NBI from going to sleep? It might just be the display that's going to sleep. Sometimes when it goes to sleep, it will hang on the agent install and only finish after it's been woken up.

4. We have our building techs assigned to a specific device scope. When they go to image a new Mac out of the box, it will schedule the template in the console, but never run on the Mac. The only way we've found around this is to have them refresh the scope after the device is booted into NetBoot, then choose the template. Is this expected behavior, or is there something I need to add to their device scope to allow them to "see" new Mac devices? It doesn't happen with new Windows devices.

 

I think that's all... thanks for any help you can provide!

↧

Ivanti Endpoint Manager and Endpoint Security - Provisioning Frequently Asked Questions

July 7, 2011, 2:30 pm
$
0
0

Provisioning for Ivanti Endpoint Manager and Endpoint Security

This is a list of highly recommended documents for increasing overall knowledge of this component.

If you want to review additional content regarding this component, please use the Provisioning Discussion Tab or Provisioning Documents Tab

 

Initial Install and Configuration
Additional Information and UpdatesCommon Issues
Whats new in OS Provisioning in LANDESK 2016.3What's new in Provisioning in LDMS 9.6 Service Pack 1Issue: Capture Image or Deploy Image Action Fails
What's New for Provisioning in LANDESK Management Suite 2016About LANDESK Hardware Independent Imaging (HII)Issue: MaptoPreferredHandler.exe Fails in Provisioning After 9.6 SP1 Upgrade
How to Deploy a Windows 8.1 image with IMAGEW.EXE v2 in LANDESK® Management Suite 9.6About the LANDESK HII Driver RepositoryIssue: Provisioning History shows "Running" state on completed task
How to capture an image using IMAGEW.EXE with provisioning in Management Suite 9.6About the LANDESK HII Driver Database
Use a "single agent install" to create and use a "provisioning agent" for end to end provisioningAbout Windows PE versions used in Ivanti Endpoint Manager
How to Provision a UEFI Tablet using ImageW

 

 

Ivanti Momentum Content

[Tech Brief On-Demand Webinar 2017] Technical Provisioning Configuration and Troubleshooting

[Tech Brief On-Demand Webinar 2017] Windows 10 Migration with Management Suite 2016.3

[Tech Brief Recording] Provisioning with LANDESK Management Suite

 

 

"How To" Documents

GeneralProvisioning ActionsHII (Hardware Independent Imaging)Profile MigrationPXE, vBoot and WinPE

How to use Conditionals in LANDESK 2016 Provisioning

How to Detect and Install Patches within Provisioning

How to add drivers to WinPE for LANDESK OS ProvisioningHow to: Build a Profile Migration Command Line with sample scriptHow to configure DHCP to work with LANDESK PXE boot
How to use ImageX with LANDESK Management SuiteHow to use the LANDESK OS Provisioning "Patch System" actionHow to manage drivers using the HII toolHow to capture user profiles using LANDESK ProvisioningHow To: Redeploy PXE Representatives
How To: Use Inject Scripts in ProvisioningHow to use Product to Package MappingHow to use HIICLIENT in preview modeHow to deploy user profiles using LANDESK ProvisioningHow to troubleshoot the LANDESK PXE Process
How to use the 'Includes' option in a Provisioning Template to link to other TemplatesHow to use DISM to manually inject drivers into the Boot.wimHow to configure preferred servers as a PXE representative and host a web share for Vboot files
How to use Variables in OS ProvisioningHow to change the Hii Driver Download Location Within the Patch Manager Download Updates ToolHow to Create OS Provisioning Boot Media
How to rename computers using LANDESK Provisioning "Device Name Prompter" action
How to Import/Export Provisioning Templates - Video
How to Import/Export Provisioning Templates - Video
How to Create a Disconnected Provisioning Template - Video
How to Join Specific OU in LDMS 9.6

 

General Troubleshooting

 

GeneralPXE IssuesHII IssuesTemplate Issues
Windows PE Issues
How to Troubleshoot Provisioning Template Actions - VideoHow to troubleshoot the LANDESK PXE ProcessHow to troubleshoot PXE boot (OSD and Provisioning)How to troubleshoot Provisioning Template Action HandlersHow to Troubleshoot WinPE hanging after selecting an OSD script from the Boot Menu.
How to troubleshoot the Configure Target OS (CTOS) Action in Provisioning Templates

 

NOTE:This page is not a comprehensive list of documents and issues. You can continue to search the rest of the community or the portion specific to Provisioning if this page has not helped.

↧

Boot.wim copy very slow during WinPE boot

December 6, 2017, 1:59 am
$
0
0

When I boot on PXE first step is the copy of boot.sdi + boot.wim

It's very slow, the copy certainly is done from core server even if I have boot.wim locally on my PXE machine

How to check and manage that ?

Thanks

↧
Viewing all 1803 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>