Deploy Image failing for MacOS.

Hi All,
We are running into an issue where Netboot is failing to mount the SMB drive, the password is considered bad.

It was working a few days ago but has stopped working recently.

The account that is passed through via preferred server has the correct password, we also tested manually mounting it using our own credentials (which failed).

It looks like some where along the way, instead of using "Authentication Package: Kerberos", its switched to "Authentication Package: NTLM" but im not sure what services passes the credentials or how its changed.

(or im completely looking at the error incorrectly)

Regards

Michael

Issue

When attempting to PXE boot, the following error appears:

• PXE Boot fails.
• No F8 option is recieved by clients.
• Unable to PXE Boot machines.
• Unable to network boot machines.
  
  

Cause

• No PXE representatives are deployed.
• Deployed PXE Representative is turned off.
• PXE representative is not in the same broadcast domain as target machine.
• Firewall on PXE representative is blocking requests from target machine.
• PXE services are not running.
• Windows Deployment Services (WDS) are installed on the PXE representative.
• Another service on the server is using port 67
  
  

Resolution

• Update BIOS on device
• Ensure that a PXE representative is on and is deployed in the same broadcast domain as the target machine.
• Ensure that no firewall is blocking requested packets from PXE booted machines.
• Ensure PXE services are running.  The two services are "LANDESK® PXE Service" and "LANDESK® PXE MTFTP Service".
  If they are running, restart the services.
• Redeploy the PXE Representative.
• If PXE services repeatedly stop on PXE representatives, download and install the latest service pack on the core, then remove and redeploy PXE representatives.
• Disable the Windows Deployment Services (WDS) on the PXE representative.
• Run the "netstat -abn" command to find the service which is using port 67 and disable/reconfigure this service.

Note: The PXE Representative may need to be rebooted if the services are running, the firewall is off, but it still does not respond.

LANDESK 2016 introduced Device Naming Templates as a new method for naming devices during the Provisioning process.

Device Naming Templates combine Public Variables, Number Sequences, and Truncation to provide a flexible, easily controlled device naming solution.

Creating Device Naming Templates

In the LANDESK Management Console, select Tools> Provisioning> OS Provisioning.

Within the OS Provisioning Tool, selectTools> Device Naming.

Click Add. The Edit Naming Template window should appear.

Clicking Insert on either section of the Window will apply value to the "Template" field. Keep in mind that clicking Insert again will not overwrite previous data; rather it will add to it.

Click Save when finished. The saved Template should now appear in the "Device Naming" window.

Adding Device Naming Templates to Provisioning Templates

In a Provisioning Template, right-click "Pre-OS Installation," "OS Installation," or "Post-OS Installation" and select Add Action.

In the "Type" drop-down list, select Device Name Prompter. Click OK.

Within the Device Name Prompter action, check Name Template and select the template created earlier.

Device Name Prompter in WinPE

When the Device Name Prompter action runs in WinPE, the following window will appear and the configured countdown timer will begin:

From here, various configured Naming Templates can be selected for use. The option to fall back to the Default "LDHostname Variable" is also available. Click OK to continue provisioning.

Expectations

• Device Naming Templates do NOTupdate the name of the computer directly. They simply update the ldHostname variable for the host workstation within LANDESK. This variable is then utilized to replace the %ldHostname% entry in the Unattend Script.
• Extending from above, Device Naming Templates will NOThave an effect on the workstation within "System Migration" or "System Configuration" sections of the template.
• The Inject Script action MUST be run after the Device Naming Template within the Provisioning Template.
• Currently, allowing the timeout (configured in the action properties) to run down will result in the Naming Template NOTbeing utilized. The%ldHostname% variable will be populated with the default value for ldHostname within LANDESK. This was a defect and has been fixed in post LDMS 2016 patch, please contact support for more info if needed.

We are adding an administrator account  with provisioning and we have a public variable setup as sensitive data for the account password.   When we provision with execute file and the command-line parameters: of account name %variable name% /add on a Windows 10 device, the template just hangs at Action 1 with the cmd.exe screen.  It doesn't add the account at all.

This template works without issues and immediately on Windows 7.  I've tested it more than once with different accounts and different passwords set as variables for Win 7 with success.  No luck with this same thing for Windows 10.  It just hangs and doesn't create the account.  Clicking the X in the cmd.exe immediately closes that action and returns an error that the password is longer than 14 characters.  The variable and the password are not even close to 14 characters.  For example a variable named %test%   (just test in LANDesk public variable page) doesn't work.  Actual password is well within 14 characters and again works when I eliminate the variable and type it plainly in the action.

I can add the actual account password in the command-line parameters and it will instantly be created on Windows 10.    This seems to be some bug where this sensitive data when passed as %variablename%   doesn't work in Windows 10.   We don't want to put the account passwords in clear text for provisioning.  That's the purpose of the sensitive data variables.

Works in Win 7, doesn't work in Win 10.    Suggestions?

Problem:

You will see an error under Self-Electing Subnet Services for the "Current State" which will show "Subnet Error"

To review the cause of this error you will need to go to the PXE Rep / Client that is running PXE Services and open the Registry. Navigate to the following key:

HKLM|SOFTWARE|Wow6432Node|LANDesk|ManagementSuite|WinClient|CSEP

PXE Service "Subnet Error" (Boot.wim)	PXE Service "Subnet Error" (NBI / Netboot Image)

Log files to reference for Information about PXE:

Logs are located on the PXE Client - C:\ProgramData\LANDesk\Log\

PXESVC.Log

PXEMTFTP.Log

TMCSVC.Log

SelfElectController.Log

Sometimes its best to enable Xtrace logging to get more information from the logs - How to enable Xtrace Diagnostic Logging - https://community.ivanti.com/docs/DOC-32532

Resolution:

How to Fix issue with Boot.wim/Boot_x64.wim :

You will first want to make sure that the Boot.wim/Boot_x64.wim is copied to the PXE Rep in the following directory: C:\Program Files (x86)\LANDesk\PXE\System\images\Boot

If the file is not located here we should review the PXE Logs to find out why the Boot.wim & Boot_x64.wim are not being copied over. You can also try to manually copy the files from the core server from \\%corename%\ldmain\landesk\vboot\

How to Fix issue with Netboot Image:

Navigate to OS Provisioning by going to Tools - Provisioning - OS Provisioning from your Console.

Click on "Preboot" drop down and select "Manage NetBoot Image Mappings"

Manage NetBoot Image Mappings	Mac NetBoot Image Mappings

Browse to the location of your NBI (NetBoot Image file) and select it. Click Apply

Hi,

I'm a bit confused by the supported features matrix

Supported Platforms and Compatibility Matrix for LANDESK Management Suite/Ivanti Endpoint Manager

Does Endpoint manager 2018.1 support OS provisioning for Ubuntu and Linux OS?

thanks!

Hello,

I'm using LDMS 207.3.2 and I want to use OS Provisioning.

I have a problem with Self-Electing Subnet Services. The PXE Representative elected is not a device that always

works : its state is often "deactivated" and I can't change it on my own.

I would like to have a single PXE Rep on my subnet (for instance, a computer I have chosen before, with PXE service  activated in client connectivity). How can I do that ?

Thanks for help.

All right, so I am a member of 2 groups, Provisioning Development and my team. We keep our dev / testing templates in the Provisioning Development group, and the public templates that our techs use to deploy in Public. I have recently converted all public templates to locked templates.

Directory structure as such:

• Provisioning templates
  • My templates
  • Provisioning Development templates
    • Included Templates
    • Standalones
    • Windows 10
      • Win10x64 Enterprise CBB – SSC- Dev
      • Win10x64 Enterprise CBB – Standard- Dev
      • Win10x64 Enterprise LTSB – Production- Dev
    • Windows 7
    • Windows 8.1
    • All team templates
  • Public
    • Windows 10
      • Win10x64 Enterprise CBB – SSC
      • Win10x64 Enterprise CBB – Standard
      • Win10x64 Enterprise LTSB – Production
    • Windows 7
    • Windows 8.1
    • All public templates

Notice the difference between the names is the dev templates contain “- Dev” in the title.

So when I have to update a template, I create a locked version of the Dev template, delete the Public version out of Public → All public templates, and move the locked template over to Public → Windows 10.

However, when I attempt to rename the locked template to remove the “- Dev” out of the title, I get the error message:

I can find no reference to the template that supposedly already exists. Any ideas? Bug perhaps?

We have started getting in the new Latitude 5490 and 5590 laptops, noticed that they now only allow legacy external devices. My image templates kick off fine but when they reboot I get 'No bootable devices found'!

I have enabled 'Always boot UEFI devices' in the preboot settings, injected the dell drivers into the boot.wim and boot_x64.wim, redeployed PXE servers and still nothing.

Created a brand new template, used variations of templates that work with all previous. I have tried various different BIOS settings, RAID on, AHCI, secure boot off, nothing! What have I missed!?

I'm in a sticky situation, new starters etc piling up...... Help appreciated!

Steve

Hello,

we currently got a provisioning problem with some of our PCs.

The System information are the following:

-Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz

-Windows 10 IoT Enterprise LTSB 2016 64Bit

-UEFI System

-RAID 1 with two HDDs

-2 On-Board NICS and 1 extra network adapter.

The provision always fails at a specific action when we got the extra network adapter connect..

When i disconnected the adapter the template runs without any error.

Here is the ldprovision log:

2018-07-24 13:50:18(3480-3484) ldProvision.exe:***********   Processing Action - Disable Action Center

2018-07-24 13:50:18(3480-3484) ldProvision.exe:Not able to set action as running

2018-07-24 13:50:18(3480-3484) ldProvision.exe:Handling Action - Execute_file

2018-07-24 13:50:18(3480-3484) ldProvision.exe:Do EnvironmentCheck

2018-07-24 13:50:18(3480-3484) ldProvision.exe:Is WinPE Action=0, Is WinPe Environment=0

2018-07-24 13:50:18(3480-3484) ldProvision.exe:Report might reboot status to core.

2018-07-24 13:50:18(3480-3484) ldProvision.exe:Call web service SetActionStatus()

2018-07-24 13:50:18(3480-3484) ldProvision.exe:Calling Program:C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe  -b ncs -H"C:\ldprovisioning\header.txt" -o"C:\ldprovisioning\body.txt" -f"C:\ldprovisioning\result.xml" https://LANDESK/LANDesk/ManagementSuite/Core/ProvisioningWebService/WebService.asmx

2018-07-24 13:50:18(3480-3484) ldProvision.exe:Web service call attempt:0. ExitCode:0

2018-07-24 13:50:18(3480-3484) ldProvision.exe:In Handle Action.

2018-07-24 13:50:18(3480-3484) ldProvision.exe:About to download handler.

2018-07-24 13:50:18(3480-3484) ldProvision.exe:Same action type, no need to download handler.

2018-07-24 13:50:18(3480-3484) ldProvision.exe:Done with download handler.

2018-07-24 13:50:18(3480-3484) ldProvision.exe:Launching action handler [ExecuteHandler.exe] with parameters ["]

2018-07-24 13:50:27(3480-3484) ldProvision.exe:handler launched.

2018-07-24 13:50:27(3480-3484) ldProvision.exe:Could not find tag response

2018-07-24 13:50:27(3480-3484) ldProvision.exe:Could not parse status node in xml

2018-07-24 13:50:27(3480-3484) ldProvision.exe:Caught exception in main: code=80001802H, file=..\shared\src\LDProvisionResponse.cpp, line=298

2018-07-24 13:50:27(3480-3484) ldProvision.exe:Call web service GetStatusString()

2018-07-24 13:50:27(3480-3484) ldProvision.exe:Calling Program:C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe  -b ncs -H"C:\ldprovisioning\header.txt" -o"C:\ldprovisioning\body.txt" -f"C:\ldprovisioning\result.xml" https://LANDESK/LANDesk/ManagementSuite/Core/ProvisioningWebService/WebService.asmx

2018-07-24 13:50:27(3480-3484) ldProvision.exe:Web service call attempt:0. ExitCode:0

2018-07-24 13:50:27(3480-3484) ldProvision.exe:StatusString = The action handler output is invalid.

2018-07-24 13:50:27(3480-3484) ldProvision.exe:Got a socket Error: 10054.

2018-07-24 13:50:27(3480-3484) ldProvision.exe:Could not connect to UI on socket.  Continuing

2018-07-24 13:50:27(3480-3484) ldProvision.exe:Call web service SetActionStatus()

2018-07-24 13:50:27(3480-3484) ldProvision.exe:Calling Program:C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe  -b ncs -H"C:\ldprovisioning\header.txt" -o"C:\ldprovisioning\body.txt" -f"C:\ldprovisioning\result.xml" https://LANDESK/LANDesk/ManagementSuite/Core/ProvisioningWebService/WebService.asmx

2018-07-24 13:50:27(3480-3484) ldProvision.exe:Web service call attempt:0. ExitCode:0

2018-07-24 13:50:28(3480-3484) ldProvision.exe:Could not connect to UI on socket.  Continuing

2018-07-24 13:50:30(3480-3484) ldProvision.exe:Could not connect to UI on socket.  Continuing

2018-07-24 13:50:30(3480-3484) ldProvision.exe:Provision GUI still found alive, waiting.

2018-07-24 13:50:31(3480-3484) ldProvision.exe:Entering downloadbyproxy.

2018-07-24 13:50:31(3480-3484) ldProvision.exe:Create process (C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe) with args (  -f "ldsleep.exe" http://LANDESK/landesk/files/ldsleep.exe)

2018-07-24 13:50:31(3480-3484) ldProvision.exe:Waiting for process result: 0.

2018-07-24 13:50:31(3480-3484) ldProvision.exe:Process exit code:-1073741502

2018-07-24 13:50:31(3480-3484) ldProvision.exe:Entering downloadbyproxy.

2018-07-24 13:50:31(3480-3484) ldProvision.exe:Create process (C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe) with args (  -f "ldsleep.exe" http://LANDESK/landesk/files/ldsleep.exe)

2018-07-24 13:50:31(3480-3484) ldProvision.exe:Waiting for process result: 0.

2018-07-24 13:50:31(3480-3484) ldProvision.exe:Process exit code:-1073741502

I hope you may be able to help me!

Thanks in advance

Regards

Christopher

In response to this Community thread, I have created a tool that will modify the ComputerName value in a Sysprep Unattend XML file after being injected during WinPE Provisioning.

The purpose of this tool is to eliminate the need to chose between automatic and manual computer naming when injecting an Unattend XML.

Syntax:

CompName.exe N "C:\Path\To\YourUnattend.xml"

The first command line argument is the number of seconds to wait before the tool exits and makes no modifications to the Unattend XML.

The second argument is the path to the Unattend XML you wish to modify.  You must wrap this string in quotes, even if there are no spaces in the pathname.

Both arguments are mandatory or the tool will default to 300 seconds and "C:\Unattend.xml"

Use:

In a Provisioning template, make a new Action of the type "Execute File" and have it execute CompName.exe.  Supply the number of seconds and the path to the newly injected XML as the command parameters.

Place this action directly after the existing Inject Script action in your template (or any other point after the Inject Script action, but before the system boots to the new image)

** In the ZIP file there is a _Demonstrate.bat that runs the tool against a sample Unattend XML file so you can try it out before putting it into LANDesk.

Warranty:

None

How it works:

1 - In WinPE, a Provisioning action launches the tool and waits a configurable number of seconds before moving on.

2 - Supply a computer name

3 - Script checks the hostname length and illegal characters

4 - Once validated, script displays old name and new name.

Unattend XML before:

Unattend XML after!

Application exit codes:

I look forward to your feedback!

Thanks,

Jesse McCoppin

Hi,

is there any way to restrict the download to a certain OS?

Regards

Marco

We have started ordering Dell Precision T7820's.  We downloaded the driver cab for it and put the drivers in the driver store, rebuilt the driver database, and did an auto-detect and assign drivers for the T7820's.  All good so far.  Then we went to image the first machine (Windows 10, 64 bit), and once it begins to load windows, it blue screens.  The problem is with amdkmpfd.sys (system thread exception not handled).  OK, so we go into assign driver, find where that driver is assigned (in this case, PCI Exrpess Root Complex), and remove that one driver.  Then we try imaging again, and windows still blue screens on that same driver.  I am at a loss as to how it is blue screening on a driver that isn't even being used at this point.  Am I missing something with removing the driver?  How do I get Endpoint Manager to stop loading this bad driver into the image?  Should I remove the driver entirely from the driver store?  I am just worried that may cause issue with other PC models.

We are on ivanti Management Console version 11.0.0.164

Thanks

Hi,

I am using OSD to deploy Windows 10. I am using the Microsoft partition scheme with 4 partitions: System, MSR, Windows and Recovery.

Unfortunately OSD always tries to install windows in to the first partition. Since this partition is too small (260MB), the installation fails.

How can I define the destination partition ?

Thank You!

Greetings, Andy.

Purpose:

The purpose of this document is to review the differences between Legacy BIOS PXE booting, UEFI PXE booting and why it matters.

What is the difference:

The difference is the process that the firmware uses to find the boot target, Legacy Boot is the boot process used by BIOS firmware and UEFI boot is used by UEFI firmware. UEFI is the newer standard and is more secure. In regards to imaging the major difference is the partition structure used. UEFI booted systems use a GPT (GUID Partition Table) partition structure where Legacy BIOS booted systems use a MBR (Master Boot Record) partition structure.

Why it matters:

The default option when creating a provisioning template is to use LANDESK ImageW v2, this method captures/deploys the entire partition including the partition table structure. The other most common method to capture/deploy is using ImageX, ImageX captures just the bytes on the drive and does not contain the partition table structure. If you are using ImageX with a .wim extension this information is not applicable since ImageX does not capture the partition table structure.

When is this important:

This information is important if you have an environment with both Legacy BIOS booting machines as well as UEFI booting machines and you are using an ImageW (.tbi) image. This is because an image captured with ImageW has the partition structure so you can not capture on a Legacy BIOS booting machine then deploy to a UEFI booting machine because the partition structure is not compatible. They are starting to make systems without the Legacy BIOS boot option so that is also something to keep in mind.

More information:

What happens if I deploy a .tbi file that was captured with a Legacy BIOS booting device and attempt to deploy to a UEFI booting machine or vice a versa? The image will deploy successfully, however on first boot the firmware will be unable to find the boot device and will act as if there is no OS installed.

Useful links:

- Boot to UEFI Mode or Legacy BIOS mode | Microsoft Docs

- Windows and GPT FAQ | Microsoft Docs

- BIOS/MBR-based hard drive partitions | Microsoft Docs

We are having an issue trying to do the naming and joining in our unattended.xml.

See below:

Beginning of XML:

<?xml version="1.0" encoding="utf-8"?>

<unattend xmlns="urn:schemas-microsoft-com:unattend">

    <settings pass="oobeSystem">

        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

            <AutoLogon>

                <Password>

                    <Value>password=</Value>

                    <PlainText>false</PlainText>

                </Password>

                <Username>user name</Username>

                <LogonCount>4</LogonCount>

                <Enabled>true</Enabled>

                <Domain>domain name</Domain>

            </AutoLogon>

            <OOBE>

                <HideEULAPage>true</HideEULAPage>

                <HideLocalAccountScreen>true</HideLocalAccountScreen>

                <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>

                <HideOnlineAccountScreens>true</HideOnlineAccountScreens>

                <NetworkLocation>Work</NetworkLocation>

                <SkipMachineOOBE>true</SkipMachineOOBE>

                <SkipUserOOBE>true</SkipUserOOBE>

                <UnattendEnableRetailDemo>false</UnattendEnableRetailDemo>

            </OOBE>

        </component>

    </settings>

    <cpi:offlineImage cpi:source="catalog:c:/users/samuola/desktop/win10entx64/sources/install_windows 10 enterprise.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />

</unattend>

End of XML

HI all,

I am currently on a Landesk trial and experimenting with provisioning and am hving some problems with the 'Join Domain' action.

I have created a few different templates and I have had this working in the past, but for some reason it no longer works.

Instead of joining the domain, the client joins a workgroup with the same name as my domain.

Below is my Join Domain action:

I have checked and double checked the username/password and everything is correct.  I have also tried using variables and it also fails.

Any ideas?

we have Precision 5520 unable to boot from network through Type - C adapter

Issue

Imaging a device with an Ivanti EPM Agent installed can cause the devices that receive the image to overwrite each other in the database.

Cause

Ivanti EPM inventory looks at a Unique ID/Device ID when inserting the scan. This ID is created when the agent installed on the device.

Resolution

It is strongly recommended that the LANDESK agent is not included in an image.  The recommended way to install the Ivanti EPM Agent with imaging is to use Ivanti EPM Provisioning and include a Configure Agent action in your provisioning template.  Besides causing duplicate devices, the Ivanti EPM agent is often updated and adding it to the image will quickly cause your image to be outdated.

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:

1. Install the Ivanti EPM agent, then STOP all LANDESK or Ivanti related services
2. Delete the following Registry Keys for 32bit clients:
   
   

           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:

http://community.landesk.com/support/message/61210

Description

To show how Ivanti EPM can be used to recycle existing information from the Ivanti EPM Database back into a newly re-imaged computer.

For this document, I chose to use the Windows "Description" inventory data, but the methodology could certainly be applied to any number of other useful pieces of Inventory data - the possibilities are endless!

Background

In a former environment, I used a VBScript for Device Name (NetBIOS/hostname) creation after OSD.  The PC naming convention is to use a 3-digit alpha code unique to each physical location, and the last six digits of the onboard Ethernet MAC address.  The alpha code is determined in VBScript by obtaining the IP address of the Ethernet adapter and matching the 2nd octet up to a string in a dictionary.

For example:

Arapahoe Ridge High School = ARH - network is 10.66.x.x - VBScript says if 2nd octet is 66 then device name will begin with ARH

Pioneer Elementary School = PIE - network is 10.67.x.x

Manhattan Middle School = MAM - network is 10.68.x.x

So device names end up being ARH3CF1BF, PIE789FAC, MAM82EF08, etc.

This naming convention is EXCELLENT when it comes to writing LANDESK scopes, queries, Active Directory automation, and custom scripts that must know the physical location of the computer.  This convention is TERRIBLE for actual identification of a single machine in the flock.

That is what Microsoft created the "Description" for, AKA the SRVCOMMENTvalue data in the HKLM\SYSTEM\CurrentControlSet\Lanmanserver\Parameters\ registry key.  Computers need a standardized network name that makes scripting easy, AND a Friendly-Name that is useful to us Humans.

When reimaging a whole lab like the BOH Library, it's time-consuming to go around and re-describe each computer, especially when the description is the same as it was before.

_________________________________________________________________________________________________________________________________

HOW-TO for Provisioning (added September 13, 2011, tested on 9.0 SP2 and SP3)

Attached to this document is a Provisioning "Include" template for 9.0 SP2/SP3 - it greatly simplifies the Description injection over the Classic OSD method outlined in the next section.  It uses no INI or BAT files, requires no image modifications, and occurs in WinPE before an image ever boots up.

The Include template performs the following steps, and should be added to the Post-OS Installation phase at some point after the new OS image has been laid down to C: and the volume is writable:

Step 1 - Back up the SYSTEM registry hive to SYSTEM.BAK

Step 2 - REG.exe mounts the SYSTEM registry hive as OSDSYSTEM

Step 3 - REG.exe writes the new Description to the registry, using a Variable called "DeviceDescription" which references "Computer"."Description" from the DB

Step 4 - REG.exe unmounts the OSDSYSTEM registry hive.

That's it!  All you have to do is import the attached Include and include it in your Post-OS Installation phase of a Provisioning template.

Voila!  Every time you reimage a computer, Ivanti EPM can now recycle the current Description from the DB.