One last one, here's a quick PowerShell script which you can use to add a domain group (WindowsAdmins) to a local group, in this case Administrators. We add this as a provisioning step so that our desktop support team can administer the station once built. Nice and simple!

$computername = Get-Content env:computername

$adgroup =[ADSI]"WinNT://subdomain.domain.com/WindowsAdmins"

$localgroup =[ADSI]"WinNT://$computername/Administrators"

$localGroup.PSBase.Invoke("Add",$adgroup.PSBase.Path)

Has anyone ever installed Terminal Services or Remote Desktop Services on the LANDesk Core Server after installing LANDesk software. Im not sure if I install terminal services now would it must up my application. Thanks...

Description:

Customer is trying the run Vulscan in a provisioning template using Executer file action

Customer is using the following parameters he saw in a custom script:

/repair "group=LDMS950-FR_v418" /maintEnable=false /AgentBehavior=LDMS950-FR_v1003

Issue:

The action fails with the follwoing error "PATH NOT FOUND"

Resolution:

Removed quotation marks in the command line around group to make it

/repair group=LDMS950-FR_v418 /maintEnable=false /AgentBehavior=LDMS950-FR_v1003

IT IS FIXED IN 9.5 SP2

Problem:

Selecting the WINPE Menu option in the F8 menu fails with a MTFTP timeout error.

Selecting the WINPE Menu option in the F8 menu is stuck at Boot Server IP and never loads WINPE.

Selecting the Managed WINPE option in the F8 menu fails with a MTFTP timeout error.

Selecting the WINPE Provisioning option in the F8 menu works.

Cause:

New BIOSes have broken the tftp multicast option that WINPE Menu and Managed WINPE options use.

Solution:

Obtain the latest BIOS update from your hardware vendor.  

As an example, Lenovo has released Bios Version 2.59 for various models that fixes this issue. 

(See http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/g1uj27uc.txt)

If your vendor does not yet have the latest Intel remote boot update within their bios, contact them and request that they update the BIOS to include this.

This was a defect introduced in newer versions of BIOS and should be remedied by the hardware vendor.

An alternative is to back-rev the  BIOS to an earlier version prior to when this defect was introduced, however this should be done with caution.

The issues lies with the MTFTP (Multicast TFTP) portion of the remote boot agent.   As a workaround, the usage of MTFTP within the LANDesk PXE Representative can be disabled:

In order to do this:

1. Set the following registry key to 0 on all PXE reps:

32-bit OS on PXE rep:

HKLM\SOFTWARE\Intel\PXE\Mtftpd\MCAST_ENABLE

64-bit OS on PXE rep:

HKLM\SOFTWARE\Wow6432Node\Intel\PXE\Mtftpd\MCAST_ENABLE

2. Restart the LANDesk PXE and LANDesk PXE MTFTP services on the PXE representative.

LD 9.5 No SP

Just curious if eveyone is just putting up with this as I have been for years. Every time I capture a image using imagew v2 and a windows 7 computer in PXE I have to go back and reset the active partition.

This is caused by what I think is a leftover scripting in Landesk for XP. Assvol marks the OS partition as C and makes it active which is not the case with windows 7.

We also capture images for XP and that is why I have not messed with the Assvol script.

Issue:

Removing the distribution action(s) from the template resolves the issue.

Provisioning template fails almost immediately when started.

Cause:

Push Delivery Method was selected which is not allowed with provisioning templates.

Solution:

Select a Policy or Policy-Supported Push Delivery Method when running or creating provisioning template tasks.

Hi,

I've installed a new Core Server with 9.5 SP2

I try all the things i'm using with by Landesk 9.5 Production Server and i've problem with provisionning.

I deploy MDT masters with Landesk and i need to change some configurations files to point to the preferred server instead of the core.

I was using Replaceprefserv.exe to make these changes.

It seems that the format in preferredservers.dat has change (there's now a "Null" characater at the end).

So now, by configuration files aren't correct.

Is someone has encountered this problem or have a solution.

I think that tool was wrote by Landesk, it' was by previous integrator that give it to me.

I've the source code of the éxécutable, but it's a little bit complicate for me to do changes in it.

Regards

Hello,

Has anyone attempted to Capture an image with a provisioning template?  I have been referring to the explanation of the process  that is found here:   http://help.landesk.com/Topic/Index/ENU/LDMS/9.5/Content/Windows/osd_prov_r_action_types.htm

My main question is what are you supposed to put down as the path to the image that you want to capture.  There is no path to this image...it should be asking where you want to store the captured image.  Am I wrong?

How are you supposed to know the path to the image to capture before the image is captured.  And why would you want to capture an image during the process of restoring an image? If I'm laying down an image on a machine, that means it has already been captured and prepped for deployment?  It seems to be a round and round scenario that really makes no sense.  Capturing works perfectly with OSD Scripts both with full Images and Hardware Independent Images, and the process makes sense and is well documented.  This is not the case for capturing an image with provisioning, and I don't believe that part of the template has been perfected or is working at all.  But we are attempting to move everything to the provisioning templates to standardize our procesess so this will become a vital piece. 

If anyone has gotten this to work in provisioning I'd love to hear your methods. 

Thank You,

I am trying to PXE boot HP EliteBook Folio 1040 G1 and none of the drivers are connecting to LANDesk Server. I have LANDesk version.9.50.26. The laptop has Intel (R) Ethernet Connection I218-LM netword card. I tried with different version of network card drivers for Windows 7 and Windows 8 (64 Bit).Any help will be appreciated.

Thanks

JT

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

I use Landesk 9.5 No SP

I have all Dell Computers. Most of my computers are on Windows 7. I have a few on XP.

Several of my XP computers use a Soundmax audio driver. I am trying to convert them over to Provisioning. When doing a HII Provisioning, the image is layed down ok, reboots and during HII it loads the Windows 7 Audio Driver which brings up a window that says it has not be verified for XP and then freezes.

We tryed putting the XP driver in the driver database but it screws up the Windows 7 HII Provisioning.

How do I get around this problem?

So, we swapped out to different switches at the end of last week, which caused all kinds of grief, which for the most part has been sorted out. We were having some DHCP errors, and when I'd try to boot off the PXE representitive it would return some appropriate error about not receiving a DHCP reply.

Well, now when I try to image a computer, it says something about the MTFTP Server not having an IP address? The error is up VERY briefly before it kicks me to the Start windows normally option screen. Last time I tried it I notice a bunch of zeroed out IP addresses, like something about subnet mask 0.0.0.0 etc.

I don't even know where to start on this one, a quick google/landesk search hasn't turned anything up for me.

The background of this project

Because there is no DHCP in LV reseller, and the network is limitted less than 100M, Most of the files need to put in local Usb drive in advance, if needed, deployment os will access these files from local Usb drive, not download these files from core server.

The request from LV reseller

Boot client machine into WinPE through Usb drive insteading of Pxe Rep
Provide OSD deployment script menu
Provide UI to input the static IP address and mask, gateway to setup network in WinPE
Add driver
Provide UI to select different location to rename the computername by this section
Add the client machine into LVMH AD automatically
Can deploy agent to client machine, and install antivirus program and active the Operating System.

LV门店没有DHCP，只能通过窄带跟核心服务器通讯，因此需要把image等超过100M的文件都放到本地U盘，部署操作洗头膏时用到这些文件都从本地读取，LV门店的需求如下：

*U盘启动门店终端
*进入landesk pe
*提供界面手工输入IP地址
*选择部署脚本
*开始进行系统部署
*加载驱动程序
*重启后再次提供UI界面人工输入IP地址
*提供UI，选择国家和地区（根据国家选择，决定机器名前缀 如CN-）
*自动加入LVMH AD
*自动部署landesk客户端，卡巴防病毒，激活win7系统

Configuration steps:

1. Create bootable USB drive：
1.1 Login Win Console to create bootable USB drive，please refer to following screenshot:
1.2 Update boot.wim:
  Copy boot.wim to local drive ，for example d:\lv，Use the following command to extract boot.wim:
  dism /mount-wim /wimfile:d:\lv\boot.wim /index:1 /mountdir:d:\lv\mount
  1.2.1 Replace d:\lv\mount \windows\system32\startnet.cmd
  1.2.2 Copy netsh.hta to d:\lv\mount
  1.2.3 shutdown all the folder and program which accessed mount folder, Use the following command to repackage boot.wim:
  dism /unmount-wim /mountdir:d:\lv\mount /commit
1.3 Copy the following files to U drive:
  1.3.1 Copy boot.wim to u drive’s boot folder             
  1.3.2 Copy netsh.hta to u drive’s root folder
  1.3.3 Copy image file to u drive’s root folder
  1.3.4 Copy the following files to U drive’s root folder:
   AssignDrvC.txt

   …..

   AssignDrvH.txt
  
2.    Configure OSD Script
2.1 Create OSD Script, Delete the following command：
  diskpart /s X:\LDClient\rmvol.txt
2.2.Modify the following command to rename the computer name
  REMEXEC39=ldrun tokreplw C:\unattend.xml COMPUTERNAME=%Location%%System - Serial Number%
  REMEXEC40=ldrun x:\Location.bat
2.3 Modify the following command to update the location of image files’ s location:
  REMEXEC25=ldrun h:\IMAGE_~2\LD9.5\imagew.exe /r /o /d:0 /f:"""z:\WIN7_X~1.TBI""" /rb:0
2.4 Configure the IP address for the Operation system：
  REMEXEC46=cmd /c xcopy /y /e x:\netshOS.bat C:\
2.5 The other thing need to do is configuring xml file：
  you can find the location to configure this commander here:
  Pre-boot commands-> Enter ‘RunOnce’ commands……
  After configure successfully, we need to adjust this command to the first one, It will be the last one by default:
     <FirstLogonCommands>
    <SynchronousCommand>
      <CommandLine>c:\netshOS.bat</CommandLine>
      <Description></Description>
      <Order>1</Order>
    </SynchronousCommand>

3. Deployment on the client machine:
3.1 Configure the BIOS settings:
  Boot from Usb drive
3.2 Boot the client machine from Usb drive
  Client machine will boot into WinPE through Usb drive, Please input IP address and mask and Gateway etc, please refer to the following screenshot:
3.3 After the OSD Deployment Script Menu pop up, Please choose the related OSD script to run, if it execute successfully, the operation system can be deployed to client machine successfully.

One of the most common uses of Provisioning is to extend the capacities and functions of imaging or new machine deployments to include the installation of the OS as well as a number of configuration settings and software installations. In order to bridge the gap between WinPE and the new OS LANDesk uses a process called Configure Target OS. This is a separate action that needs to be added to the template for a template that installs an image, and is included as part of the Scripted Install action. This article covers the function and troubleshooting of the Configure Target OS action

Configure Target OS overview

The Configure Target OS (CTOS) action is available only in the Post-OS installation section of the provisioning template. It needs to be the final action in the template before the System Configuration section. No actions can come after the CTOS. The CTOS prepares the machine to resume provisioning after the client boots into the target OS, then restarts the machine, leaving WinPE and allowing the computer to boot normally. In order for the CTOS action to work, the image that was deployed to the client MUST be sysprepped.

The Configure Target OS takes advantage of a few Microsoft technologies in order to resume when the machine completes booting into the target OS (Windows XP, 2003, Vista, 2008, 7). Files are injected to the root of the OS drive (C:\ldprovision) and commands are added to the appropriate files such that they are run during the mini-setup just prior to booting into the target OS.

Windows XP/2003

1. All needed files are copied to C:\sysprep\i386\ldprovision directory on the client machine. The C:\sysprep\i386 directory must exist and be accessible.

   Note: Sysprep is responsible for creating the i386 folder.  If the folder is not getting created, you can get around the issue by creating a new action in the script, putting the action in front of the CTOS action, that creates this folder.  If this folder does not exist it will cause the failure of any additional action after CTOS runs and reboots the client.
   

2. The cmdlines.txt file in the OEM folder on the client machine is created or modified. A line is added to call ldprovisioning.cmd. Windows will run cmdlines.txt at the end of the mini-setup, calling ldprovisioning.cmd.

Windows Vista/2008/7

1. All needed files are copied to C:\ldprovisioning directory on the client machine
2. The unattend.xml is modified and commands are added to call ldprovisioning.cmd from the C:\ldprovisioning directory

LDProvision.cmd

When run, ldprovisioning.cmd installs the basic LANDesk CBA agent in C:\Program Files\LANDesk\LDClient and configures it as a service to start on OS boot. It also modifies the actions.ini file in C:\Program Files\LANDesk\Shared Files\cbaroot to contain a line pointing to C:\ldprovision\ldprovision.exe with the needed command line options. The actions.ini file is used by the LANDesk CBA agent as instructions when starting, so the commands contained therein are run when the service starts

Troubleshooting Configure Target OS

Troubleshooting the CTOS action can be especially difficult. Because of the nature of the operation and how it works, LANDesk must give up control to the Windows installation processes for a time, and then resume afterwards. This can sometime make it difficult to determine where the problem is occuring. The problem can be in WinPE trying to copy and modify files, it can be somewhere in the mini-setup of the OS, and it can be after the OS has completed all setup tasks and has fully booted.

The first step to troubleshoot the CTOS action is to determine where in the process the failure is occuring. The CTOS action will not always get marked as failed. Often provisioning just fails to continue through the rest of the template.

WinPE

This is where it is most likely to see an actual failure of the template. Usually this means something could not be copied correctly or modified. The machine will stay in WinPE after the template fails so troubleshooting can be done in the exact condition the machine is in when it fails.

1. Open a new console in WinPE.
2. Check to make sure that the C: drive is accessible.
3. Change to the C: drive and look around. Does it look like the image was put down correctly?

If you deployed:

     Windows XP

1. Change to C:\sysprep directory. Verify that the I386 directory exists. Look to see if the ldprovision folder was created and populated

   Note: Sysprep is responsible for creating the i386 folder.  If the folder is not getting created, you can get around the issue by creating a new action in the script, putting the action in front of the CTOS action, that creates this folder.  If this folder does not exist it will cause the failure of any additional action after CTOS runs and reboots the client.  This also prevents the $OEM$ directory from being created in the i386 folder.
   

2. Check the cmdlines.txt in C:\sysprep\$OEM$\ and make sure it contains a line for ldprovisioning.cmd
3. Verify that ldprovisioning.cmd is in C:\sysprep\$OEM$\

     Windows Vista/2008/7

1. Change to C:\ldprovisioning directory. Verify the ldprovisioning.cmd is in the folder and the folder is populated. It should contain over 20 files.
2. Verify that the unattend.xml exists in C:\Windows\Panther
3. Verify that the commands calling ldprovisioning.cmd exist in the unattend.xml for the platform (x86, amd64, ia64) you have deployed.

Sometimes all of these will be correct and ready to go, but the machine will remain in WinPE. Usually there is not a failure of the task. It is possible that the reboot command didn't run correctly but everything else did. To verify this, simply restart the client and observe the results.

Between WinPE and Windows

After the client reboots out of WinPE it will boot off the hard drive into the target OS. Because the image was sysprepped, it will go through a mini-setup process. If no sysprep file was provided, it will prompt for a number of items such as the computer name, user names, time zone, product key etc. before completing the booting process into the target OS. LANDesk has no control over this process and is not running at all. Near the end of the mini-setup process Windows executes the commands that LANDesk added during the CTOS action. For Windows XP and 2003 the mini setup executes the commands in the cmdlines.txt at then end of the sysprep steps. For Windows Vista, 2008 and 7 the commands are exeucted during the Specialize pass in the unattend.

Windows XP/2003

The important file here is the cmdlines.txt This file should contain the call to ldprovisioning.cmd. It is here that LANDesk is again introduced into the process. When cmdlines.txt is executed it runs ldprovisioning.cmd from the same directory, which prepares the machine to resume provisioning after the whole mini-setup process is complete.

Windows Vista, 2008 and 7

Sections are added to the unattend.xml in the Specialize section. This is a special section of the unattend.xml that can also be used for things like setting the home page for Internet Explorer, etc. In this section, RunSynchronousCommand action is added calling ldprovisioning.cmd from C:\ldprovisioning\. The section of the unattend will look roughy like the following:

<settings pass="specialize" xmlns="" wasPassProcessed="true">
    <component name="Microsoft-Windows-Deployment" 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">
        <RunSynchronous>
            <RunSynchronousCommand action="add">
                <Description>LANDesk Provisioning Install</Description>
                <Order>1</Order>
                <Path>cmd /c %systemdrive%\ldprovisioning\ldprovisioning.cmd</Path>
            </RunSynchronousCommand>
        </RunSynchronous>
    </component>
</settings>

In Windows

Once the machine completes the mini-setup section, it will boot into the final OS. As the machine boots up, it runs the LANDesk Management Agent service that was installed by ldprovisioning.cmd. As part of the startup process, the LANDesk Management Agent will run the commands in the actions.ini file. The actions.ini file was also modified by ldprovisioning.cmd to contain the following command

C:\ldprovisioning\ldprovision.exe -c <CORE>

Troubleshooting Tip: If you would like to get extra logging for problems you are seeing later in the template, open this file BEFORE the machines competes the boot after the mini-setup and change it to the following:

C:\ldprovisioning\ldprovision.exe -c <CORE> -V 255 -L C:\<LOG FILE>

       Note: the -V is a captial V and is case sensitive

Once ldprovision.exe starts, it queries the core server for the next action in the template, and provisioning will continue with the actions in the System Configuration section

A bit of a newbie in OSD, so I need some input as to my issue with OSD.

Are using LDMS 9.5 SP2. Imaging a Dell E7440.

My steps have been:

On source PC configuring with WIn 7, install apps etc. Start sysprep Audit, no geneneralize, shutdown.

I check for partition # of C drive using diskpart

I capture the image using OSD script with Image W V2.

aWhen capture is done, source machine can't boot because no OS

Image capture itself seems to work

I deploy Image onto destination PC using OSD script configured to use sysprep.

Image deploys, PC boots successfully, sysprep OBE runs, Agent installs.

After boot complete desktop resolution is set at lowest level, device manager shows 3 unknown devices,

and the C; parttion is shrunk in half with the balance of space unallocated.

Comparing the source driver files to destination, the actual driver files are missing for the unknown devices.

Is this a sysprep thing, OSD, a combination or am I doing something very wrong.

Thanks in advance.

We are demoing an HP 840 and we have tried every 840 g1 nic driver in the WinPE 3.1 (LANDesk 9.5 no SP).  We are not in a place to update to 9.5 SP1 which has WinPE 4.0.  Is there anyone out there that has any ideas to get the Nic driver to load in WinPE 3.1?

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)

Schedule image capture/deployment with UEFI

1. OSD - Schedule template for the provisioning template you want to deploy
2. Scheduled provisioning template deployment machines must be in the device list or a bare metal machine.
3. Start schedule provisioning template
4. Once in pending status, boot machine and press F12
5. Deployment will change to active state.

NOTE: UEFI is only supported in Provisioning and not OSD. UEFI doesn't support a menu so you will need to use Scheduled Provisioning instead.

Provisioning OSD PXE Boot devices with UEFI. You must follow these steps to boot the device.

1. Add the client to the Inventory using the Bare Metal Server tool.
2. Schedule your Provisioning Template.
3. Add the machine to the task, but leave the physical device turned off.
4. Start the task. It will go to active, and then after a few seconds will go back to a Pending status.
5. Power on the device, and tell it to Network Boot (Usually F12 or Delete).
6. At this point the PXE Rep should see there is already a task waiting for that machine, and send it straight into WinPE, and automatically begin the Provisioning task.

My capture image provisioning task keeps failing.  For some reason it is not getting the credentials from the preferred server.  Here is the log of MaptoPrefferedHandler

2014-04-02 17:40:07(1236-1232) maptopreferredhandler.exe:******Mapping to: \\tech\landesk\Images

2014-04-02 17:40:07(1236-1232) maptopreferredhandler.exe:Drive letter = f

2014-04-02 17:40:07(1236-1232) maptopreferredhandler.exe:Mode - Require Direct, no preferred server.

2014-04-02 17:40:07(1236-1232) maptopreferredhandler.exe:Could not get credentials for preferred server.

2014-04-02 17:40:07(1236-1232) maptopreferredhandler.exe:End of Map Drive.  Path used: - \\tech\landesk\Images\.

2014-04-02 17:40:07(928-1296) maptopreferredhandler.exe:******UnMapping Drive

2014-04-02 17:40:07(928-1296) maptopreferredhandler.exe:Drive letter = f

2014-04-02 17:40:07(928-1296) maptopreferredhandler.exe:Could not map or unmap drive. Error code: 2250

2014-04-02 17:40:07(928-1296) maptopreferredhandler.exe:End of UnMap Drive.

Here is the template:

Any help would be greatly appreciated,

Mike