So we just upgraded to 9.5 SP2, and I now get some kind of error that a coworker told me is because now the PXE Boot service is based on Windows 8, so I'll need to download and embed the video and network drivers for the computers we support into the PXE agent.

My question, is will I need to get the drivers for 8.0 or 8.1, and 32bit vs 64bit?

Greetings,

     i just upgraded from 9.5 base to SP2. we are now trying to image comptuers with OSD and are getting the following error message in the CL-OSD script on the Core server. i have created a support ticket already but am wondering if anyone out in the community has any thoughts or knowledge on what could be causing this. basically i can boot all the way into the WinPE Menu. when i try to deploy my Win7_32bit OS it loads all the drivers successfully and then get stuck on a blank X:\ldclient\drvmap.exe console window. asside from the CJ-OSD log on the core i am not sure what other logs to reference in troubleshooting.

"Machine","CbaStatus","ExitCode","Duration","Begin","End","Command"

"0023245D7423","OK",0,0:00:00,2/14/2014 11:54:48 AM,2/14/2014 11:54:48 AM,"WINPE, TIMEOUT=1800"

"0023245D7423","OK",-2147024809,0:00:01,2/14/2014 11:54:49 AM,2/14/2014 11:54:50 AM,"diskpart /s X:\LDClient\rmvol.txt"

"0023245D7423","ERR_Fail",-1917190230,0:02:00,2/14/2014 11:54:52 AM,2/14/2014 11:56:52 AM,"ldrun drvmap.exe [DOMAIN]\[USER] 21081D86E67C2FCCA5E43557D31058CF111685F0F13 I: """\\[SERVER]\[IMAGESHARE]""", STATUS FACILITY=3513"

; "Job Complete","0 Done","1 Failed","0 Off","0 Unknown"

In "My OSD Scripts" i can delete, but in the ALL OSD Scripts, i cannot.

Is there a way?

thanks.

Since we use LD 9.5 SP1 we have problems with the Software Deployment in provisioning templates.

The Template seems to be installed succesfully. The logged provisiong-process in the console shows that everything was succesfully installed.

But in fact not every Software of our provisioning template was installed on our clients. So we have to install it afterwards via our software packages, which work fine.

The affected Software which is not installed, change with every client and every deployment. So it is not a particular software or a particular package type which will not be installed.

We analyzed the eventvwr but we find nothing "special" that can be associated with this problem. We find no (interesting) logs concerning the provisioning template. Has someone else this problems? Is it a known issue? Do we something wrong?

Again: This problem exist since SP1.

Thank you in advance,

Agnes

I got capture/restoring profile provisioning actions to work from Win7 to Win7 machines. The same migration command xml doesn't work when I try to go to Win8.1 from Win7 however. I tried to cut back what it captured to just a user's file and I'm still getting failures. I'm not sure where the logs for these actions are stored either.

Using: v9.5 sp1

Has anyone had luck with this?

Thanks.

When any of my provisioning templates run, I have a patch system task that runs in the template.  Before upgrading to 9.5SP1, the patch system task worked.  Now, after the upgrade, the task runs and says it was successful but no patching is done.  It just blows threw the task and marks it complete.

I tried creating a new task using the same patching group but to no avail.

Anyone have any ideas?

Jeff

Greetings all,

     is there a way to exclude drivers from being installed on a specific machine? i have downloaded the correct drivers from the manufactures website but durring the HII part of the script it is pulling the drivers for a different model, thus casuing the machine to bluescreen... the problem is the drivers it keeps using are for a machine type that consumes 40% of my fleet and i dont really want to get rid of them. any thoughts? btw i am using 9.5 with SP2 and the workstations are Lenovo

Description

This issue is characterized by selecting an OSD script from within the PXE Boot Menu inside WinPE, the Boot Menu window disappearing, and then no further pop ups or display windows occurring.

There are several causes for this behavior, and therefore, several possible solutions. This troubleshooting guide is centered around the issue of the OSD script failing to be initiated on the core server, or the OSD logs indicating that the machine is "OFF". If the OSD script indicates that it is launching at least one EXEC line against the target, then this troubleshooting guide can be skipped.

A visual representation of this process is attached as a flowchart below:

Step 1 - Identifying the Issue

To determine the troubleshooting path, it must first be determined how far the process is progressing. The fastest way to accomplish this is to determine if a CustJob log is being created. Follow the steps below to determine this:

1. On the core server, go to the log directory. This is located at the following path <Install Drive>:\Program Files (x86)\LANDesk\ManagementSuite\logs or can also be accessed via UNC share at <coreservername>\ldlog.

2. Once in the log directory, it is recommended to sort by Date Modified, with most recent at the top.

3. The log file will be named CJ-OSD-<scriptname>-<timestamp>.log

4. If there is a log file, open it with a text editor, such as notepad or word.

5. If the log file is similar to the one listed below, and indicates that the machine is OFF, then CBA is unable to contact the specified machine or CustJob has targeted an incorrect machine record.

"Machine","CbaStatus","ExitCode","Duration","Begin","End","Command"

"(OFF) XPSP2B","OFF","N/A","0:00:00","11/6/2008 12:19:28 PM","11/6/2008 12:19:28 PM","N/A"
; "Job Complete","0 Done","0 Failed","1 Off","0 Unknown"

 

If there is no log, then the process did not complete to the point of initiating CustJob to launch the OSD script. See below for actions.

First, verify that the following service are installed and running on the core server:

LANDesk Inventory Server

LANDesk Management Agent

If these services are running, it may be beneficial to restart these services. If the LANDesk Management Agent service is missing, go to the "No logging generated on the core" section below. Once restarted, reboot the machine into WinPE and select the script from the menu.  If the same behavior occurs, follow the indicated directions:

If there was no log file generated in the log directory on the core, go to the "No logging generated on the core" section below.

If there was a log and it indicated that the machine was OFF, go to the "Machine shows OFF" section below.

No logging generated on the core.

The process to request a script to run on the client machine involves a series of processes to request, resolve and schedule the task from the client to the core server. The below steps will attempt to identify and resolve the issue related to these processes.

Missing LANDesk Management Agent service

If the core does not have a LANDesk Management Agent service, you can install this service by following the steps listed below:

1. On the core, pull up the Start > Run window

2. In the field, type or paste the following command and then hit enter:

"C:\Program Files (x86)\LANDesk\Shared Files\residentagent.exe" /register

Once the service is installed, start the service and then try the OSD process again.

If there is not a C:\Program Files (x86)\LANDesk\Shared Files folder on the core server, please contact LANDesk Technical Support for further assistance.

If the LANDesk Management Agent service is installed and running and a service restart did not resolve the issue, please follow these additional troubleshooting steps:

Verifying the Inventory Record

OSD needs an inventory of the device being imaged in order to create the task and begin logging.  New machines that have not been inventoried before will be listed by its MAC address in the Device Name column in the console.

If there is no inventory record for that device, restart the inventory service and reboot the client and try imaging again.  If still no inventory record appears for the device please contact LANDesk Technical Support for further assistance.

Verifying the PXE.amsx Web Service functionality

• Open the CoreWebServices.dll.log located in the log directory on the core server. The log should contain lines that are similar to those listed below:

RunScript: started with client mac address 000C29461DD1, script GUID bc6a8a9c-3edc-4845-83fb-5e1cceb60b71
RunScript: completed successfully with client mac address 000C29461DD1, script GUID bc6a8a9c-3edc-4845-83fb-5e1cceb60b71

Note: Each script has an associated GUID.  The GUID is contained in the Script (Located in the ManagementSuite\Scripts directory).   This must match in the PXEMENU table in the database in order for the script to be associated properly.

Line in Script: GUID=71e307da-bb27-46ab-ac8d-ef9641f3139f

Entry in Database:

• Can the LANDesk PXE.asmx web page be accessed? (Note: This must be run locally on the Core Server

• Open a web browser on the core and type/paste the following address:

http://localhost/landesk/ManagementSuite/Core/core.webservices/PXE.asmx

This should display the web page shown below:

• Will the GetObjIDFromMacAddress function resolve a Mac address to a Computer_Idn from the PXE.asmx web page? (Note: This must be run locally from the Core Server)

1. Click on the GetObjIDFromMACAddress link in the web site.

2. On the MAC Address field, enter in the mac with no spaces or dashes.

3. Click on the "Invoke" button to process.

4. The following return should be displayed:

NOTE: The number encased by > < is the object ID and corresponds to the machine's ID assigned by Inventory.

If this process fails, then there is most likely a missing record. Ensure that the Inventory contains the MAC address associated with a machine record.

• Will the RunScript function start the job by manually putting in the MAC Address and ScriptGUID? (Note: This must be run locally from the Core Server)

1. Click on the RunScript link in the website.

2. On the indicated fields, input the MAC Address and the script GUID.

3. Hit the Invoke button.

A CustJob window should launch on the core and start processing the script. You can also look to see if this process generates a log file in the log directory. If this process succeeds, then it indicates that IIS may be hung or not correctly processing SOAP requests. Try running an "IISreset" command from Start > Run. You may also need to re-register ASP.NET on the core with the following command:

For 8.7 Core

"C:\Windows or WINNT\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i"

For 8.8 Core

"C:\Windows\Microsoft.NET\Framwork\V2.2.50727\aspnet_regiis.exe -i"

• Enable the OSD Web Tracing by doing the following:

1. Edit the web.config file in C:\ProgramFiles\LANDesk\LANDesk\ManagementSuite\LANDesk\ManagementSuite\Core\Core.WebServices so that the line "<trace enabled="false"" reads "<trace enabled="true"" and restart the WWW Publishing service.

2. The following URL may be used to pull up the Web Trace to track what requests are made to the OSD Web service on the core: (Note: This must be run on the LANDesk Core Server)

http://localhost/landesk/ManagementSuite/Core/core.webservices/trace.axd

• An http caching appliance will respond to the http requests made by the client. Due to the caching appliance responding, the client will not receive the subsequent lines of the script. Configure the caching appliance to not cache the http traffic from the Core Server.

Verifying the LANDesk Management Agent Service functionality.

• Run script calls a local execute on the Core Server. The LANDesk Management Agent service must be running on the Core Server.

• To test the Management Agent service, run the following command line:

"C:\Program Files (x86)\LANDesk\Managementsuite\custjoblaunch.exe"

/objid=<object id of machine> /script="<script name without directory path>" /bootonly

For Example:

"C:\Program Files (x86)\LANDesk\Managementsuite\custjoblaunch.exe" 83 "DeployGhostImage.ini" /bootonly

If this does not launch the script, remove and re-install the LANDesk Management Agent service with the following commands:

Remove:

"C:\Program Files (x86)\LANDesk\Shared Files\residentagent.exe" /unregister

Install:

"C:\Program Files (x86)\LANDesk\Shared Files\residentagent.exe" /register

If these steps do not resolve the issue, please contact LANDesk Technical Support for further assistance.

Machine shows "OFF"

NOTE: When troubleshooting Inventory related issues, please ensure that you are logged in to the core console with a user that does not have any restricted scopes applied and that is allowed to view the Default All Machines scope.

Causes

1. Another machine in the database has the IP address assigned to the machine in WinPE.  Custjob.exe is targeting that device.

2. The inventory scan had not yet processed the ip address from the miniscan. This could be because the inventory service is stopped or hung.

3. Duplicate devices (two machines with the same MAC Address) in the database.

4. Core cannot contact the Agent on UDP port 9595. (Firewall, or other filtering device is blocking this port.)

5. Under Configure | Services | Custom Jobs, the Discovery setting may be set to TCP only.  WinPE only responds to UDP.

6. DNS can be in a state where the client can resolve the Core Server but the Core Server cannot resolve the agent workstation.

7. NIC driver may not be entirely functioning properly.

8. Name resolution problems may prevent the core from targeting the machine by DNS name.

Resolutions

1. Start or restart the inventory service.

2. Search for the IP address that WinPE has.  If another device has this IP address, delete that inventory record.

3. That device may show up twice in the database.  Delete all devices with that MAC Address.  See
   community article 1569 for assistance with this.

4. Open UDP port 9595 between the Core Server and the Agent workstation.

5. Go to Configure | Services | Custom Jobs and set the Discovery to try both UDP and TCP.

6. Go to Configure | Services | Custom Jobs and check the box to Disable DNS/WINS Lookup.

7. Make sure the Core Server can ping the Agent workstation by name and IP.

8. Update the NIC driver In the WinPE image.

9. Make sure the Core Server and PXE reps are running the same version of software.

10. Verify that the client miniscans are being received by the core server. Enable the Store Scans option in Configure | Service | Inventory | Advanced. Set the value to 1 and restart the Inventory service. Browse to the ldmain\ldscan\Storage directory and verify that .IMS files are being received when the client boots into WinPE.

11. Verify that the core is processing mini scans. Check Configure | Services | Inventory | Advanced | Ignore mini scans. This value needs to be set to 0

Hello,

I am curious if anyone might have any insight into this problem.

I am creating a USB boot drive using the LDMS console. I can use this boot drive to get into PE on any new devices (we are a Lenovo shop) with the haswell chipset and UEFI without any issue. For any older devices that do not use UEFI, these boot drives will not load into winPE. Thus, we cannot image a machine using provisioning with a USB boot drive.

Thanks in advance!

Marc

We have a vbs script that runs in the OSD template while deploying to run the Windows Update for us. It hangs up on the EULA acceptance because it doesn't accept it. Any suggestions? The WUA_SearchDownloadInstall.vbs I don't believe can be altered to accept the agreement because the interaction takes place through cscript. Please correct me if I am wrong! Thanks for any help!

Deploying Windows 7 64bit

LANDesk 9.5 sp1

Hello all,

I am trying to create a template to capture a profile, reinstall the OS and then restore the profile with 9.5 SP2 using the profile capture provisioning action.  I have created a standalone template for the profile capture and have tried running that, but it keeps failing on "retry 40 of 40".  I can run other templates on the machine I am testing it on, so it is not a locked template that is hanging it up.  The provisioning log only shows: "Unable to find template for computer IDN 4117". 

Here is the xml from the template:

<template id="af42a399-9dbe-4dc0-9222-0304720a1807" name="Profile Migration" version="4">

<description />

<preboot-os>WindowsPE</preboot-os>

<final-os>

  <name>Windows</name>

  <type-id>All</type-id>

  <family-id>Windows</family-id>

  <vendor-id>All</vendor-id>

  <major-ver>-1</major-ver>

  <minor-ver>-1</minor-ver>

  <architecture>All</architecture>

</final-os>

<variables>

  <variable name="_ShowClientUI" transform="none">True</variable>

  <variable name="_CloseClientUI" transform="none">wait30</variable>

  <variable name="_RemoveClientFolder" transform="none">True</variable>

</variables>

<section id="SystemMigration" name="System migration">

  <description>Back up personal or custom files before the system is modified.</description>

  <action name="Capture Profile" version="4">

   <description />

   <action-type>Capture_profile</action-type>

   <variables />

   <options>

    <option name="StopProcessingTemplateIfActionFails">true</option>

   </options>

   <parameters>

    <ProfileUNCPath>\\{preferredserver}\profiles\</ProfileUNCPath>

    <ComputerNameOption>True</ComputerNameOption>

    <MacAddressOption>False</MacAddressOption>

    <SerialNumberOption>False</SerialNumberOption>

    <UmaCommandFile>\\{coreserver}\ldlogon\uma\commandxml\Profile-Migration.xml</UmaCommandFile>

    <SMAFileSpecified>False</SMAFileSpecified>

   </parameters>

  </action>

</section>

There really isn't that much to this template and I cannot for the life of me fire it up to see it pull the profile.  Is there some other step I am missing?

Thanks.

PS.  I've searched the community and most all of what I've found relates to previous versions of profile migration, not the improved version in 9.5.

I have a VBS Script that while in Provisioning in the Pre-OS Installation Action, auto names the computer by gateway.  I am looking for a script that will prompt me to ask for the computer name in WinPE.  Does anyone have something written?

Hello,

We have been using the out of the box user migration tool that comes with Landesk. The tool works somewhat OK, however it's not reliable. I'm looking to see what others are doing and/or if you have any suggested tweaks to change the experience.  I'm currently on Landesk 9.0 SP3 and I'm open to the possibility to using a third party tool if that is a better option, unless the new version of LDMS has a better tool?

Thanks for all the support.

We are looking into Hii for imaging moving forward.....I can't find a document explaining the process

Is there a lot of issues with 9.5 sp1 hii?  I've seen quite a few unanswered posts regarding blue screens and slowness....is it unstable?

Is there a way to import all HP/Dell Drivers

We have selected a number of package bundles to be deployed as part of an OSD provisioning template. While the package bundle deploy actions succede, none of the applications within the bundle are installed. Is this a supported method to install software in a provisioning task?

I have launched a provisioning template that works fine but when I launch it with a distribution package, the package fails. Keep in mind that the distribution package works great when launch as a schdueled tasks. Also, I have a 3minute wait just befor the distribution package is kicked off.

When I run packages it will tell me the landesk agent needs updating. I have 9.5 service pack 2. Should I need to update?

After creating an image the computer I create it from crashes. It would either say "Operating system not found" or "Missing file or corrupt" (winload.exe). When creating an image it should do nothing to the harddrive but it fails for some reason. Sometimes I can deploy the image and sometimes I cant. Anyone have had this experience?

With Provisioning, I'd like to run a powershell script after the workstation joins the domain. The script adds an AD group to the local admin's. I've thought about doing this on the build, but joining to the domain kicks me out of Audit mode when I am building the image and I'd like to avoid that if possible.

Can I run a powershell script from provisioning? Is there a better way I should do this?

(the workstations are win7 x86)

The first thing to check when this happens is to look at the Inventory Server Service to make sure that it is running.  Any entry in the console for Bare Metal devices will need the Inventory Service running in order to insert the device into the database.

- If the Inventory Service is in a state of "Starting", then there is a problem and the core may need to be rebooted to resolve.  If this does not resolve the problem with the Inventory Service starting, there may be an issue with the database or with connectivity to the database.

Possible workaround if the Inventory Service is running:

You can run barescan.exe from the managementsuite directory.

barescan.exe -v name=test mac=123456789aac

When using the command line method for testing if the following error was displayed:

unable to create ScanDirEmitter connection to core server:"CORE SERVER NAME"

Resolution:

• To resolve this issue the following steps were taken:
  Needed to add the non LDMS Administrator account to the LDSCAN folder with the following Security permissions
  Modify, Read & Execute, List Folder Contents, Read, Write

• Determine what is causing the Inventory Service to not start.  (You may need to contact the Inventory Support Team to resolve)
  Once the Inventory Service will start the Bare Metal devices will show up in the database.