The documentation that I can find no longer lists supported OS for PXE reps in 9.6. My tests have proven unsuccessful getting windows 8 and server 2012 r2 working as a PXE rep. It installs and the services run but they seem to do nothing. Is there any news if the supported OS list changed from 9.5 to 9.6 sp1

Hello, I'm following this guide How to capture an image using IMAGEW.EXE with provisioning in Management Suite 9.6

I'm pretty sure I have everything in order, all machines are in the same gateway/network the bare metal server has been set as well as my PXE reps.

When I get tot the last step which is boot the machine form NET PXE I keep getting error PXE-E53 : No boot filename received, my scheduled task looks good and it gets the IP of the machine I want to image (the bare metal server for which I entered its MAC address) so I assume it can see it in the network.

So I gave up on booting from PXE and booted from USB (provisioning Boot Media) and the weird thing is that I do not get the usual Enter domain credentials and select Template, it just starts working (using the PXE provisioning Template that I created), meaning that the capture starts and completes just fine, creating the .tbi file as expected. at this time my PXE task changes to working...

And the Bare Metal Server restarts (after the capture task finished -due to setting in the capture task, as expected), the working stat has been like that for a while so I do not know if is still working or not, since the size of the .tbi has been the same for a few minutes now

Questions:

1. Is this the expected behavior? I thought the concept of using PXE Net Boot was to NOT use the USB (provisioning Boot Media) and that it would get the task from the network.

2. If the above is not as expected, what do I suppose to see once the system boots from PXE Net Boot? Is a DOS screen so I imagine it will be some kind of task detailing the progress of the capture?

Your help is really appreciated.

Thank you.

HI

i was wondering if i am the only one who are experiencing slow boot image / PXE /TFTP download from all my clients?
Im only getting arround 14 Mbit pr client. :S
i have tryed several things to speed up this process, but all the articles are related to Microsoft SCCM.

http://windowsdeployments.net/how-to-speed-up-pxe-boot-in-wds-and-sccm/

I tryed modifying the BCD file with the RAMDISKTFTPBLOCKSIZE + Windows size , with no luck, also tryed the NIC card thingy changing the bugger size ( cant remember link)

But all this without luck.

Im running Server 2008 ENT R2 REpository server and Server2012 Core server.
And Gigabit all the way to my clients witn no load on the network

Is there not any ways to speed up this tftp download process??
I cant find any refferences on the net discussing this , only one from year 2008, wich is outdated now.

Any help would be appriciated

Hi!

I've go a new Dell Latitude E7450 but it does not boot into PXE although the network adapter seems to be the same as in previous E7440 model.

I am only getting message:

IP addresses: 127.0.0.1

waiting for IP address...

Regards,

Vesa.

Hello,

I use provisioning to deploy my machine, on the windows 7 64 bits, I want to modify this registry keys :

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\

DefaultUserName

DefaultDomainName

AutoAdminLogon

Autologoncount

when I use provisonnig, the modified keys are :

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\

and windows 7 64 bits don't use the good keys.

I test with the REG ADD action, the problem is the same.

What soluce to modify the good keys ??

Thank and sorry for my bad english.

Joaquin

Problem

Deploying an Image or Capturing an Image fails during OS Provisioning.

Downloading prerequisites...
Connect to core:96-CORE3
Loading template...                                              
Action #1
Capture image
FAILED
error:[80001803H]The action failed.
Execute result:
return:-1
output:

Provisioning History Shows:

Internal Status: -2147477501

Cause

The Preferred Server listed in the template fails to resolve or authenticate. This is can be caused by a few things:

• The Preferred Server is not defined in the LDMS core.
  • If this is the case, the maptopreferredhandler.log on the client will show:

maptopreferredhandler.exe:******Mapping to: \\PreferredServer\share
maptopreferredhandler.exe:Drive letter = e
maptopreferredhandler.exe:Mode - Require Direct, no preferred server.
maptopreferredhandler.exe:Could not get credentials for preferred server.
maptopreferredhandler.exe:End of Map Drive.  Path used: - \\PreferredServer\share\.

• The Preferred Server credentials could not successfully authenticate.
  • This is often caused when the password for the Preferred Server is incorrect.
  • It may also occur if the Client cannot resolve the Preferred Server
  • The maptopreferredhandler.log on the client will show:

maptopreferredhandler.exe:******Mapping to: \\PreferredServer\share
maptopreferredhandler.exe:Drive letter = e
maptopreferredhandler.exe:Mode - Attempt preferred server.
maptopreferredhandler.exe:Could not map or unmap drive. Error code: 86

Solution / Workaround

Check the each cause to identify which one may be causing the current issue.

• Verify the Preferred Server that is used in the template is defined in the LDMS Core under Tools | Distribution | Content replication / Preferred Servers.

Note: Preferred Servers are mapped to as literal strings. This means that if a Preferred Server is added by FQDN, Maptopreferredhandler.exe (used in provisioning) will only recognize that it has credentials for that Preferred Server if it is listed in the template by FQDN. If you enter it by Short Name / Netbios, it requires that a Preferred Server be added to match. Because of this, there may be multiple Preferred Servers in the LDMS Core that point at the same machine.

• Verify the client can resolve the Preferred Server
  • From the MaptoPreferredHandler.log identify the Drive Letter and Share that is being mapped to. Use this information to manually map the share.
  • To test the credentials open a new Console window on the Client in WinPE and enter the following command:

  • Net Use e: \\PreferredServer\Share

• If it resolves the share, the window will prompt for credentials.

• If it fails to resolve the share it will give an error with information about the cause.

System error 53 has occurred.
The network path was not found.

• If the client cannot resolve the Preferred Server, it will be unable to map the drive necessary for provisioning.
  • Try using alternative names such as FQDN, Netbios, or IP in the template. If none work, correct the underlying issue preventing the machine from resolving the Preferred server.
• Verify the Credentials defined for the Preferred Server are current and have permission.
  • From the MaptoPreferredHandler.log identify the Drive Letter and Share that is being mapped to.
  • Use this information to manually map the share.
  • To test the credentials open a new Console window on the Client in WinPE.
  • Enter the following command:

  • Net Use e: \\PreferredServer\Share

Note: (use the information from maptopreferredhandler.log we gathered in your command i.e. Net Use e: \\96-Core\Images)

• Enter the same credentials that are defined for the Preferred Server within the LDMS Core when prompted
• The command window will indicate if successful.

• If it lists a failure, this is what is happening when Maptopreferredhandler.log tries to map to the share.

System error 86 has occurred.

• If manually mapping the drive fails, identify working credentials and update the Preferred Server in the LDMS Core accordingly.

Hi Everyone,

I have issue when i try to deploy images win7 using PXE provisioning .

map_preferred server error

how can i resolve this ???

see in attachment snapshot .

Thanks for you help

I want to in the process of OSD, the user needs to enter the computer name, system deployment, after the completion of automatic configuration fixed IP address, how to implement?

Applies to LANDESK Management Suite 9.0 SP2 and earlier

A fix was introduced in LDMS 9.0 SP3 that makes these steps unnecessary

It is always recommended to update to the latest service pack.

Issue

A device in the process of being provisioned will often have the following steps:

1. Prepare the hard drive and deploy the OS (either through image deployment or scripted install)
2. Join the domain and other first start actions
3. Install the LANDESK Agent
4. Using the LANDESK Agent install software deployment packages, patch the system, etc.

There is a known issue that can cause seemingly random software deployment failures in step 4.  The issue is that when the LANDESK agent is installed it will enter the local scheduler information for the client machine to run a security scan and a policy sync.  Because of the way the LANDESK scheduler works these will attempt to run immediately, but with up to a 60 minute random delay.  (Note: This is a default setting and can be changed)

The problem occurs if the security scan or a policy task gets initiated and is running when a distribute software provisioning action starts.  In that scenario the distribute software action will attempt to run the task, view that the other task is already running, and exit with a failure.

If you have multiple distribute software actions chained together you will likely see the process fail on different packages.  This is because of the random delay at the start time that will make it so you might get the error early on, later in the process, or sometimes even succeed completely.

Description of Local Scheduler Behavior on Agent Deploy:

The LANDESK Local Scheduler service is set to launch tasks after a series of filters are passed.  These filters include passing a certain date and time, day of week, ip address changes, log on events, or others.  Our default daily tasks will use only the filter to check and see if we have already passed a certain date and time.  By default the security scan and the policy sync are set to run once every 24 hours with a 1 hour random delay.  The first run time is set to the current date and time.  This means that when the agent is deployed all the tasks listed are already passed, so the scheduler will launch them immediately, with (by default) up to 1 hour random delay.  Usually this is desired behavior so your device will attempt to make sure it is up to date on all tasks from the core, but during provisioning this can cause the problem listed above (see next section for details).

Cause

When our software distribution agent runs (sdclient.exe) it will perform a check to make sure that no other task is running.  It will check for any other instances of sdclient, any instances of vulscan (security scanner), and also do a few other checks that aren't relevant here.  If it sees sdclient.exe or vulscan.exe already running it will return an exit code that a task is already in progress, so it can't run.  As we described in the previous section, our agent deployment will launch vulscan.exe within an hour of agent deployment.  This can cause a provisioning distribute software action to fail.

In addition to the possible timing of another task starting before our software deployment agent can run there is the feature that vulscan.exe (security scanner) is very persistent.  Because it relates to security of the device it will not immediately fail if it sees a different task already running; it will wait until the other task finishes.  This is the most common scenario for the tasks to fail.  The process looks something like this:

• Agent gets installed.  Security scan is set to trigger within 1 hour.
• Software deployment tasks start and are running, as per the provisioning template.
• During one distribute software action the security scan is launched by the agent.
• The security scanner sees that a task is running, so it remains memory resident waiting for the other task to finish and for sdclient.exe to close.
• The distribute software action finishes and sdclient.exe closes until the next action can be started.
• The security scanner receives notice that it can now begin to scan, because there are no other currently running software deployment tasks.
• The next distribute software action starts, launching sdclient.exe to handle the process.
• Sdclient.exe sees that the security scanner is already running, returns a failed status code, and the provisioning template fails.

Since the timing of the security scan starting can be different you will see the failure at different points in the overall provisioning process, or sometimes not at all.

Resolution

To work around this known problem you can create an agent to be used for provisioning that does not start the security scan or the policy sync immediately upon installing the agent.  We don't have the option to disable the tasks completely, but we can set them to start at some point in the future, such as the year 3000.  That should give us enough time.

After all distribute software or patch system tasks have completed you can then finish the provisioning template by installing the agent you would actually like to use on the device long term.

To configure an agent in this way the following settings are recommended:

Change the Policy sync to not run until the year 3000 (or some other point in the distant future), as seen in the screen shots below.

Change the Security scanner to not run until the year 3000 (or some other point in the distant future), as seen in the screen shots below.

Conclusion

Following the above steps should improve the success rate of end to end provisioning tasks.

Also of interest:

Use a "single agent install" to create and use a "provisioning agent" for end to end provisioning

HII Driver Management

Hardware-Independent Imaging is a vital part of a successful imaging process. Additional features have been added to provide control and flexibility to the drivers being deployed to devices. The ability to disable drivers, assign drivers to specific hardware, and assign setup drivers has been added. It is not required to assign drivers, auto detection and assignment of drivers will still occur for devices that do not have a specifically assigned driver. The HII driver library should be rebuilt after applying Service Pack 1 to update the HII driver client database (drivers.db3).

The HII driver management has been moved from an icon on the Operating system deployment toolbar and is now a a tool in the Distribution Toolbox

Disable drivers

After building the HII library you may notice that some drivers automatically have new entries under disabled. The drivers were disabled for the generic matches included in the inf file that would have matched hardware the driver was not designed for. Reviewing these entries will show device IDs beginning with *PNP, indicating the driver could match a number of plug-and-play devices. If the driver is needed for a device in the environment, the entry can simply be removed from the disabled list.

When adding a driver to the disabled list, the driver library folder structure will be shown. Locate and select the inf file for the driver to be disabled. After selecting the driver the list of available OS and architecture will auto populate with the versions found inside the inf you selected. Set the desired OS and architecture to list the available device IDs for the selected driver. Check the disabled box for the device ID to disable and click update to disable the driver. Select any other OS and architecture combinations and disable as needed. When complete click update and close.

Assign Drivers

Assigning drivers will be matched on the make, model, OS and architecture of a device. The inventory scan now includes hardware IDs for use in HII driver management. When a driver is being assigned the hardware listing will only be shown if a devices has returned an inventory scan from an Service Pack 1 agent that matches make, model, OS and architecture.

In this example Windows 7 is selected, however on the core server there are no devices on Windows 7 for that make and model so the device tree is blank.

A device running Windows 8 for that make and model does exist, so when selected the device tree is shown.

Assign Driver .inf file

After selecting the desired option in each of the drop-downs, locate and select the device that will be assigned a driver from the device tree. The option populate by selected device ID can be used to auto fill the search box.

Searches can be made more generic by searching for just the vendor id and device id. Other Device IDs that would apply can be viewed on the device if no driver is found.

Check the appropriate driver to assign it to the selected device. Once assigned the text for the device will turn green to indicate an assigned driver. To remove the assignment, select the device and click the red x next to the assigned driver.

Assign Driver Package

Devices requiring a setup package can also be assigned. Selecting the radio button driver package and select the appropriate software distribution package for that device. In the provisioning template add an HII action in the system configuration section to install the setup packages.

Managing Assigned and Disabled Drivers

Assigned and/or disabled items are visible in the console. Those entries can be edited and removed by selecting the item and the selecting edit or remove.

I upgraded to 9.6 SP1. Since the update, I cannot get OSP to install an agent.  The agent I use is small just for provisioning then I install the full agent at the end but I get the same error with all my images.

These images worked in 9.5 SP 3. I have my core listed as a preferred server.  Here is an image, log files just state the task failed...

Here is the log file:

Provision.exe:*********  Begin an action - Configure_agent

2015-03-17 13:34:18(2012-2016) ldProvision.exe:Do EnvironmentCheck

2015-03-17 13:34:18(2012-2016) ldProvision.exe:Is WinPE Action=0, Is WinPe Environment=0

2015-03-17 13:34:18(2012-2016) ldProvision.exe:Report might reboot status to core.

2015-03-17 13:34:18(2012-2016) ldProvision.exe:Call web service SetActionStatus()

2015-03-17 13:34:18(2012-2016) ldProvision.exe:Start TryallWebService Attempt:0.

2015-03-17 13:34:19(2012-2016) ldProvision.exe:End TryallWebService Attempt:0. ExitCode:0

2015-03-17 13:34:19(2012-2016) ldProvision.exe:In Handle Action.

2015-03-17 13:34:19(2012-2016) ldProvision.exe:About to download handler.

2015-03-17 13:34:19(2012-2016) ldProvision.exe:Need to download handler:

2015-03-17 13:34:19(2012-2016) ldProvision.exe:Handler remote: /LdLogon/Provisioning/windows/ConfigHandler.exe

2015-03-17 13:34:19(2012-2016) ldProvision.exe:Handler local: C:\ldprovisioning\ConfigHandler.exe

2015-03-17 13:34:19(2012-2016) ldProvision.exe:Looking for existing file (C:\ldprovisioning\ConfigHandler.exe)

2015-03-17 13:34:19(2012-2016) ldProvision.exe:Entering downloadbyproxy.

2015-03-17 13:34:19(2012-2016) ldProvision.exe:Create process (C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe) with args (  -f "C:\ldprovisioning\ConfigHandler.exe" http://<servername>/LdLogon/Provisioning/windows/ConfigHandler.exe)

2015-03-17 13:34:19(2012-2016) ldProvision.exe:Process exit code:0

2015-03-17 13:34:19(2012-2016) ldProvision.exe:The file (C:\ldprovisioning\ConfigHandler.exe) was successfully downloaded

2015-03-17 13:34:19(2012-2016) ldProvision.exe:Done with download handler.

2015-03-17 13:34:19(2012-2016) ldProvision.exe:Launching action handler [ConfigHandler.exe] with parameters ["]

2015-03-17 13:34:19(2012-2016) ldProvision.exe:handler launched.

2015-03-17 13:34:19(2012-2016) ldProvision.exe:Reporting action status: 5 to core

2015-03-17 13:34:19(2012-2016) ldProvision.exe:Call web service GetStatusString()

2015-03-17 13:34:19(2012-2016) ldProvision.exe:Start TryallWebService Attempt:0.

2015-03-17 13:34:19(2012-2016) ldProvision.exe:End TryallWebService Attempt:0. ExitCode:0

2015-03-17 13:34:19(2012-2016) ldProvision.exe:StatusString = The action failed.

2015-03-17 13:34:20(2012-2016) ldProvision.exe:Call web service SetActionStatus()

2015-03-17 13:34:20(2012-2016) ldProvision.exe:Start TryallWebService Attempt:0.

2015-03-17 13:34:20(2012-2016) ldProvision.exe:End TryallWebService Attempt:0. ExitCode:0

2015-03-17 13:34:20(2012-2016) ldProvision.exe:End of action - Configure_agent

2015-03-17 13:34:20(2012-2016) ldProvision.exe:Last action failed

I schedule my provisioning task, add my device, Start Now->All and the little icon changes from inactive to active as indicated by the following icons:

Inactive

Active

After few seconds later it changes back to the inactive icon.  It stays inactive, and my device never initiates the task until I right-click it and select Start Now again.  Some times it takes two or three tries before it works.  Other times, it works on the first try.

Has anyone experienced this?  It's not a big concern, but it's quite annoying when it doesn't "catch".  We're on LD 9.6 SP1.

Provisioning for LANDESK Management Suite

• 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

• LDMS 9.6 OS Provisioning - What's New
• Getting Started: How to Deploy a Windows 8.1 image with IMAGEW.EXE v2 in LANDESK® Management Suite 9.6
• How to capture an image using IMAGEW.EXE with provisioning in Management Suite 9.6
• Getting Started With LANDESK Provisioning in LDMS 9.5
• Use a "single agent install" to create and use a "provisioning agent" for end to end provisioning
• How to Provision a UEFI Tablet using ImageW

Additional Information and Updates

• What's new in Provisioning in LDMS 9.6 Service Pack 1
• About changes to Provisioning Action Handlers in 9.5 SP1
• About Provisioning Action Handlers - Changes in LDMS 9.5
• About LANDesk Hardware Independent Imaging (HII)
• About the LANDESK HII Driver Repository
• About the LANDESK HII Driver Database

Common Issues

• Issue: Capture Image or Deploy Image Action Fails
• Issue: MaptoPreferredHandler.exe Fails in Provisioning After 9.6 SP1 Upgrade
• Issue: Provisioning History shows "Running" state on completed task

"How To" Documents

General

• How to use ImageX with LANDESK Management Suite
• How to use Inject Scripts in Provisioning
• Video:How to use the 'Includes' option in a Provisioning Template to link to other Templates
• Video:How to use Variables in OS Provisioning
• How to rename computers using LANDESK Provisioning "Device Name Prompter" action
• Video:How to Import/Export Provisioning Templates - Video
• Video:How to Create a Disconnected Provisioning Template - Video
• How to join specific OU in LDMS 9.6 and 9.6 SP1
• Video:How to use Machine Mapping in LANDESK Management Suite 9.6

Provisioning Actions

• How to Detect and Install Patches within Provisioning
• Video:How to use the LANDESK OS Provisioning "Patch System" action
• Video:How to use Product to Package Mapping

HII (Hardware Independant Imaging)

• How to add drivers to WinPE for LANDESK OS Provisioning
• How to manage drivers using the HII tool
• How to use HIICLIENT in preview mode
• How to use DISM to manually inject drivers into the Boot.wim
• How To: Change the HII Driver download location within the Patch Manager Download Updates tool

Profile Migration

• How to: Build a Profile Migration Command Line with sample script
• Video:How to capture user profiles using LANDESK Provisioning
• Video:How to deploy user profiles using LANDESK Provisioning

PXE, vBoot and WinPE

• How to configure DHCP to work with LANDESK PXE boot
• How to: Redeploy PXE Representatives
• How to troubleshoot the LANDESK PXE Process
• How to configure preferred servers as a PXE representative and host a web share for Vboot files
• Video: How to Create OS Provisioning Boot Media

Troubleshooting this Component

General Troubleshooting

• Video:How to Troubleshoot Provisioning Template Actions - Video
• How to troubleshoot OSD: The log files

PXE Issues

• How to troubleshoot the LANDESK PXE Process
• How to troubleshoot PXE boot (OSD and Provisioning)

HII Issues

• DISM/HII Log File Locations

Template Issues

• How to troubleshoot Provisioning Template Action Handlers
• How to troubleshoot the Configure Target OS action in Provisioning template

Windows PE Issues

• How to Troubleshoot WinPE hanging after selecting an OSD script from the Boot Menu.
  

NOTE:This article 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.

working on trying to capture the image with Provisioning in 9.5 with the elitepad integration patch.

I have thrown practically every NIC I can think of into my boot.wim & still can't get it to pick up a valid IP address.

I have the HP docking station with the LAN9512-LAN9514 USB 2.0 to Ethernet 10-100 Adapter driver, along with several PROWIN64 drivers. Can anyone point me to the correct driver that needs to be loaded?

I have a scheduled task set up that boots to PE fine & also have a USB boot stick that also loads PE fine, but it keeps bombing on finding the ip address...  PXE reps have also been re-deployed btw.

Thanks!

-Dave

Currently in 9.5 we have a home grown way to  vboot from the sites preferred server so we don't have to keep pushing the 200+ meg wim file across the wan link to the target devices at remote site.  Some of tour remote sites in other countries have a very small pipe(<1 meg) and there is just no way we can push this 200 megs over and over again for re imaging

So in 9.5 we did the following as a work around.  Basically we are using template actions to do this exact work that is found in the OSD script but we copy the files that are needed from the local preferred server.

Example of the section in the osd script below. 

REMEXEC0=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/bootfile.exe"

REMEXEC1=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/tlibr16.dll"

REMEXEC2=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/tlibr32.dll"

REMEXEC3=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/lddefrag.exe"

REMEXEC4=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/cicfgmgr.vxd"

REMEXEC5=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/cindis.vxd"

REMEXEC6=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/copyfile.exe"

REMEXEC7=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/tokreplw.exe"

REMEXEC8=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/boot.img"

REMEXEC9=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/ChangeBCD.exe"

REMEXEC10=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/BCD"

REMEXEC11=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/files/bcdedit.exe"

REMEXEC12=<qt/>%LDMS_CLIENT_DIR%\ChangeBCD<qt/> <qt/>%LDMS_CLIENT_DIR%\bcdedit.exe<qt/> <qt/>%LDMS_CLIENT_DIR%\BCD<qt/>

REMEXEC13=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /dest="C:\boot.wim" /p="http://%CUSTJOBHOSTIP%/landesk/vboot/boot.wim"

REMEXEC14=<qt/>%LDMS_CLIENT_DIR%\copyfile.exe<qt/> <qt/>%LDMS_CLIENT_DIR%\boot.img<qt/> <qt/>%LDMS_CLIENT_DIR%\BCD<qt/> \boot\BCD

REMEXEC15=<qt/>%LDMS_CLIENT_DIR%\lddefrag.exe<qt/> <qt/>%LDMS_CLIENT_DIR%\boot.img<qt/>, STATUS

REMEXEC16=<qt/>%LDMS_CLIENT_DIR%\bootfile.exe<qt/> %LDMS_CLIENT_DIR%\boot.img /keep /bootunsafe, ASYNC

We want to do the same for 9.6 but the vboot files are very different. Seems like they are only 3.   Since there is no OSD scripts in 9.6 that we can take a peak at to see how this is done, does any one know how to achieve this in 9.6?  I personally cant believe that VBOOT from pref server inst an option. Landesk needs to realize that although most places in the US have very high speed fat pipes they are just as many places around the globe that does not.  This is where Pref. Servers play a crucial role in having a replica of the data that is stored locally and is reliable unlike a peer.   Hopefully landesk will add this feature in later releases and expand on the roles of preferred servers.  But for now any advice on how to get this done would be great!

Description:

When provisioning a device with an OEM license provisioning doesn't continue after the reboot into windows.

Cause:

With Windows 8 and Windows 8.1 Microsoft made a change to the sysprep environment to improve the end user experience by skipping the SetupComplete.cmd section if an OEM license is detected. This allows the end user to get to the Welcome Screen faster. This is what causes provisioning to fail to start after the reboot.

To see if you are experiencing this issue look in C:\Windows\Panther\UnattendGC\Setupact.log after you have booted into windows and provisioning doesn't continue.

You should find this line.

[msoobe.exe] OEM license detected, will not run SetupComplete.cmd

Resolution:

To resolve this you need to add a First Logon Command to your unattend file. This typically is placed immediately after AutoLogon within the unattend.xml.

It should look like this.

<FirstLogonCommands>                <SynchronousCommand wcm:action="add">                    <Order>1</Order>                    <CommandLine>C:\Windows\Setup\Scripts\SetupComplete.cmd</CommandLine>                    <RequiresUserInput>false</RequiresUserInput>                </SynchronousCommand></FirstLogonCommands>

If the SetupComplete.cmd file is not there, you can create your own file or script to inject to reference.

SetupComplete.cmd needs to have this command:

C:\ldprovisioning\ldprovisioning.cmd

An addition, change the following path to match your new file location:

<CommandLine>C:\Windows\Setup\Scripts\SetupComplete.cmd</CommandLine>

I'm trying to edit a working provisioning template. I want to uncheck the "Stop processing the template if this action fails" box under the HII task. When I do and click apply this error appears: The UNC path is invalid. Enter a valid UNC path. When I click ok on the error message, it then jumps me to the Map Image Tool page of the provisioning task.

I'm assuming it's complaining about the UNC path on that page however, the UNC path on the Map Image Tool page is not invalid. (The path is \\<coreserver>\ldmain\osd\imagew 2\ )

I have also tried putting the path in quotes. It didn't not help.

We are on 9.6 SP1 and recently upgraded from 9.5 SP3.

I have a provisioning task which copies and runs a *.hta file that displays a message to the user on what is happening and has a proceed button on one and a finish button on another.

The task starts OK and the first HTA files loads up OK. The task waits for the user to click proceed. An uninstall takes place, the PC reboots.

After the reboot the task installs a new version of the software with correct program options. It then runs a second HTA file with a message the process has complete and once the user clicks the Finish button the tasks shuts down and completes OK.

This all works OK on x86 machines but on x64 machines I get the below issue:

The task I am using is below:

Can anyone suggest what I need to do to stop the last popup message loading in the interactive service detection??

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

Hi all,

Wondering if anyone has had this problem before and can help me.  I am trying to find a NIC driver that will work in WinPE on a Dell R210 II server.  The Hardware ID of the NIC is B06BDRV\L2ND&PCI_163B14E4&SUBSYS_04DD1028&REV_20 and the target OS is Windows Server 2008 R2.

I am running the Core on Server 2012 R2, LANDesk 9.6 SP1.

I downloaded Dell's WinPE driver CAB as well as this driver most recently: http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=W1XTR

I stuck them on a flash drive and ran the DRVLOAD <driver_inf> command, which several said they loaded successfully YET, there is no network adapter.

Thanks in advance for any help you can offer.

Cheers,

Kevin Beattie