I'm attempting to perform a capture through a Provisioning task and I am recieving a Return:-1 every time.  I have mapped the drive location I want the image to copy to.  I have tried the following scenerios.

ImageX

F:\NewImage.wim

/compresss fast /capture C: F;\NewImage.com C_DRIVE

LANDesk ImageW V2

F:\NewImage.tbi

/b /d:0 /rb:0 /f:F:\NewImage.tbi

LANDesk ImageW V2

F:\NewImage.tbi

/b /uy /d:0 /rb:0 /max:2GB /f:F:\NewImage.tbi

All result in the same thing.

Error

Return:-1

Any thoughts about this. I am very new to using Provisioning. we had previously been using OSD only, and I'm moving all the scripting over to use Provisioning now.

Hi,

We are trying to setup OS deployment with LANDesk following the steps in this document - "How to Capture a Windows 7 image with OSD using Imagew.exe v2 in 9.0 SP2 & SP3 and 9.5"

We are running LDMS v 9.5 (9.50.0.530) on Server 2008 R2.

We have deployed PXE rep to another server 2008 R2 server, build an a heathly Win7 64 OS, sysprep the machine and booting from PXE.

We see the menu with proxy and gateway ip information and select WinPE menu.

A new line pops up with "BOOT SERVER IP: 172.#.#.# which is the IP of the PXE rep. (See attached file)

It basically just sits there and do nothing.

What I noticed on the PXE rep machine there appears to be missing files under C:\Program Files (x86)\LANDesk\PXE\System\images\x86pc\undi\wpemenu

There is only 2 files in there - bootmgr.exe and startrom.0.

Is there a step we are missing? We have a log which i can paste in here from the core - CJ-PXE Representative Deployment-284-11122013-111201.log or if there is anything else you would like us to check please let me know.

Any help will be greatly appreciated.

Kind regards,

Adrian S

Hi all,

We have one core server on 9.5 SP1 which I'm trying to get up and running to replace our old box.

When I try to do HII, it tells me I need to configure a preferred server first - fair enough.

If I go to preferred servers, I can put in the credentials of a new user I created and click on test - if I try to test UNC I get 'UNC authentication failed'.

If I try HTTP with no Path I get 'Unable to validate HTTP authentication , the server allows anonymous access'.

I tried adding the new user I created to the \\servername\packages$ folder permissions but it made no difference.

SO... the question is, when it says UNC authentication failed, what is it trying to authenticate TO? Should HTTP be working on a standard core by default or will it need further config?

All the docs I can find just say 'put in credentials and click test' but nothing about giving those credentials any permissions. I'm guessing this should have been set up properly by the engineer who put in our core but it's been missed?

Hi all,

Anyone had any luck deploying Windows 8.1 via Provisioning yet? I've got the patch installed for support BTW.

I've got the easy bits going, it deploys the image and injects the unattend.xml I created. Problem is, it then boots to a login prompt for Administrator and says 'Incorrect Password'. If I put in the password (which is the same as the one in the unattend.xml) it gives me a black screen which does nothing. I can Ctrl-Alt-Del to get to Task Manager, and from there launch Event Viewer (no errors, including no failed logins) and I can get to c:\ldprovisioning which again looks fine. The c:\unattend.xml file is there, which implies it might not have finished all the steps in there because I believe one of them removes the unattend.xml file.

Can't seem to see any other logs that might be useful.

In Provisioning History, it shows the machine as still being on the step 'Configure Target OS' with a status of 'Might Reboot'. All other steps have green ticks and none actually fail, it just hangs on CTOS:

Remove Partitions

Map drive to imaging tool

Map drive to image

Deploy image

Expand partition

Mount C partition

Inject unattend.xml

HII

Configure target OS

Install full agent

Anyone done any better than me yet?

Im have troubles trying to capture an image from a HP t5740 ThinClient. I can get it to PXE boot, I then select WinPE Menu, its goes out to the server and I get Windows is loading files...It runs all the way thru that then come up with just a black screen. It doesnt go any further and cant do nothing with it. Has anyone captured a image from a ThinClient, and if so what am I doing wrong? Any help would be greatly appreciated. Ive loaded the nic drivers in the manage the driver in the WinPe image, but there isnt a driver for the HD that I can find because its a flash HD.

Greetings,

We have been using our PXE Representative for a few years, and I have found a solution for everything needed so far. This is the first time I have run into this issue without finding the answer.

It appears the Intel BIOS on the Lenovo X230 laptop has been updated and I have changed all settings to legacy. The laptop makes the handshake with the PXE rep and just stops at the MTFTP download. "MTFTP." displays and disappears from the screen, and that is as far as the process will go.

I placed a band aid on the issue for now by placing the X230 drivers into the T430 driver folder, imaging the T430, switching the hard drive to the X230 and updating the drivers.

Can someone point me in the direction to solve the issue? We are currently using LDMS 9.0 SP3, but LDMS 9.5 SP1 will be deployed in two weeks

Thanks in advance,

Jim J

We have begun to convert all of our existing OSD scripts into the newer Provisioning method.  I had a little trouble with the Image Capture but was able to get that to work.  We are now however stuck with the deployment of an image.  I'll outline what we are doing now and where the process seems to be failing.

Pre-OS Installation

     -Remove Partitions

          -Remove all partitions: disk = 0

OS Installation

     -Deploy Image

          -LANDesk Image2 V2

               -Default Parameters

     -Set Active

          -Make Bootable

               -Disk =0, Partition ID = 1, OS Partition ID = 2

Post-OS installation

     -Configure Target OS

              -Insert Provisioning Agent (CTOS)

     -Reboot/shutdown

          -Reboot (have attempted adding this and removing it as well)

     -Inject Script

          -Win 7 Current CL XML

               -Target: c:\unattend.xml (also tried d:\unattend.xml)

The part I'm getting stuck at and can't seem to continue on from is the Inject Script.  As soon as the Image is deployed I can't seem to see the drives or access them to write the unattend to.  It never shows up when the OS reboots.  When the OS does finish rebooting after the deployment it is still in sysprep mode.

Do I need to add a step to mount the drive after it's been imaged? Or am I missing something else entirely?  I've been going nuts with this for about 2 weeks now.  Thanks very much for anyones assistance on this one.

I am running SP1 9.5. Since upgrading I have been noticing an increase of OSD scripts that when run aren't starting as well as scripts actually not showing up on the menu. On the PXE Boot menu configuration, I will see something I can equate to a placeholder, but the script name is no longer there.

Has anyone else been running into this since 9.5 SP1?

-Jonathan

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

The Goal:

To create a scheduled provisioning task, which will deploy a new operating system successfully to the targeted devices regardless if they are online or offline.

It is assumed, that a working operating system deployment template already exists. If you need additional information regarding provisioning and operating system deployment, please refer to the following article:

LDMS Provisioning Launch Page

http://community.landesk.com/support/docs/DOC-9485

Configuration steps:

Step 1:

Add a "shutdown/reboot" action to the "System migration" phase in your template. DISABLE the "stop processing the tempalte if this action fails" option in the action before saving it, then select the "Boot to Managed WinPE" option in action properties in the tempalte.

This action will fail, if the device is offline (but the template will continue) and reboot the device to WinPE if the device is online.

Step 2:

Schedule your updated template. DO NOT select "Wake up devices" in the scheduled task properties > Targeted devices

Step 3:

Create a dummy task. Eg. Open Tools > Distribution > Manage Scripts > click on the "New Custom Script" icon and save the default script as a new managed script. This will not contain any commands - in the below example the script is called "Does Nothing". Then right click it and select schedule.

Step 4:

Open the properties of the task created in Step 3 and ENABLE "Wake up devices" in the scheduled task properties > Targeted devices

At this point, you should have 2 scheduled tasks.

Task 1 should contain the default custom script (which does not contain any commands but has WoL enabled) and Task 2 should contain the modified provisioning tempalte (which DOES NOT has WoL enabled)

Step 5:

Add all targeted devices to both Task 1 and Task 2

Step 6:

Start Task 2 and wait some minutes, until the offline devices will go to "pending" status

Step 7:

Start Task 1

Result:

Task 2 will most likely fail on all devices, but it will wake up the offline ones (in the example "DOES NOTHING only for WOL")

Task 1 should succeed on the online devices and also on the offline devices (in the example "TEST")

If the device is online:

The Virtual boot action will be executed and reboot the device into WinPE and it will progress your template

If the device if offline:

The Device will be woken up, then PXE boot starts and the device should automatically go to WinPE provisioning. The Virtual Boot action will fail - as it can only be performed if Windows is already running on the device - but the template will continue and process all configured actions.

Hoping someone can help us out quickly here. We are in the middle of rolling out new workstations to 100+ offices across the country.  The first 90% of them have gone fine.  Imaging over 1000 PCs so far.  Then all of a sudden 2-3 weeks ago, the provisioning tasks won't auto load past the Press F8 menu at boot. 

Every workstation must now be manually booted, with monitor and keyboard just to press F8 and load into WinPE Provisioning.  Once that WinPE system loads up it auto starts the task that is already started and continues the image without issue.  We just cannot get them to auto-load past the Press F8 menu.  They used to prompt the menu ONLY when a scheduled task is not already started for that MAC.  Now it doesn't matter if he have a task already started, it still prompts the menu, and if we don't hit F8 and choose provisioning it just loads into the stock OS from the manufacturer.

We have tried re-deploying our PXE rep multiple times to no avail. 

We are having some other issues with Provisioning as well that might be related.  I'll mention here only in case they are related.  I am the admin on the LD system and provisioning works fine for me (besides the issue above).  But for other users when they try to choose an provisioing task in the menu, it will delay and say Loading template.... over and over and over.  Sometimes it will eventually kick in, or else they just give up and I login and start it right away.

Please help us out.

LD 9.0 (I know there is an upgrade available just haven't got around to it yet).

Thanks

D

Hi,

I'm trying to multicast an OSD image task to some cliet nodes using PXE to boot the client nodes. Once the client nodes are up and the task start to work sending the multicast part for each of them, then it fails with a error message in the multicast task window of the core server:

The client nodes suppossed to receive the multicast image show a "Disk Full" error message, but there is not such lack of disk space in the client node. In fact if I try the same OSD task but without multicast option the task completes correctly in each of the client computers.

I have tested this behaviour in two diferent LDMS 9.5 SP1 core servers with different network environments and in both cases the results are the same. More over one of the network environments doesn't have routers or switches betwen the core server and the client nodes so they are connected in a simple hub in a lab environment and the resut is exactly the same.

Ani ideas?

We recently updated to LANDesk 9.5 SP1 by installing clean on a new Windows Server 2008-R2 VM. (Essentially we did a "side-by-side" migration. Our previous LANDesk core server, running LDMS 9.0SP4, still exists but has been de-activated.)

My question is regarding what seems to be a change in the folder structure on our new core server. In all previous versions of LANDesk Management Suite we would see a folder structure on the core server "C:\Program Files (x86)\LANDesk\Management Suite" where the "Management Suite" folder was shared as "LDMain". On our new core server we are seeing "C:\Program Files (x86)\LANDesk\Management Suite" with a subfolder called "LDMain" and it is the subfolder that is shared.

I don't think we did anything special during our latest install which would have caused this different folder structure. And I don't think we had customized our previous installs - I think the Management Suite folder always used to be shared as LDMain. So I presume that the new folder structure is there by design, but I haven't found anything in the documentation, readme, or the forums.

This is causing a problem for us as our Help Desk staff was accustomed to using the LANDesk CSVImport utility in provisioning new computers. With this new folder structure, they don't have access to copy the miniscan files into the LDScan folder - it is no longer a subfolder of LDMain.

Has anybody else noticed this? Any easy solutions that you can think of?

Jayson

Hi,

We have just upgraded from Landesk 9 SP3 to 9.5 SP1 and I am unable to get provisioning working again.

I used to add devices as bare metal and then schedule a deployment and leave it to it.  I am now getting to the OSD Deployment tasks and am able to select a template but it does not load, it just loops for 40 times and then fails.  part of the log file is attached.

I need help on installing a lab environment with a close network to use PXE boot on reimaging PCs.

This is what I have so far:

1. A 2008 server with DHCP server, LANDesk 9.51 also installed on the same server.

2. A VM Win7 machine as PXE rep

3. A 24 port Switch

Both VM and everything that connected to the switch receive IP as part of the assign scope and communicate with the core, but does not pick up PXE rep. I have tried combination with option 60 and 43 on/off but still get PXE-053 error.

Any help would be appreciated!

Environment:

LANDesk Management Suite 9.5 (with HP ElitePad Integration Update and/or the BASE 0228A patch) or LANDesk Management Suite 9.5 SP1

Description:

After upgrading to 9.5 SP1 (or 9.5 with HP ElitePad Integration Update and/or the BASE 0228A patch), some software within a WIM image is not working properly anymore.

Example:

The mail icon in the Control Panel created by Microsoft Office is missing.

Cause:

The version of WinPE used by OSD/provisioning is version 4.0 instead of version 3.1 and Microsoft changed the way it formats partitions. The 8.3 file format is not active which causes some files from the WIM file not to be copied or to be corrupted when copied over to the hard drive.

Solution:

Format the drive using the following switches : format C: /fs:<FS> /q /s:enable /y

The /s:enable turns the 8.3 format back on and should resolve issues when files are copied over from the WIM to the partition.

Reference:

This document was generated from the following discussion: LDMS 9.5 SP1 PXE Rep Issue

I would like to pre stage about 1500 computers for provisioning and I would like to import those devices as a Bare Metal Server by importing a CVS file. What headers need to be used in the CVS and so on create a new Bare Metal Server? I would like to create the new Bare Metal Servers using the MAC address or the devices serial number. Also, as you import the devices can you set variables through the CVS file too such as a ComputerName variable?

Greetings,

We are running LDMS 9.5 sp1 and are getting our feet wet with trying to successfully deploy Win7 using a Provisioning Template. We are in hopes to use provisioning as a mass deployment method. We are generally a MDT (LiteTouch) shop and have several .wim files we use to deploy images using MDT/WDS.

We've come to understand that LD doesn't really support using ImageX to deploy images as they want you to use ImageW. This is fine, however, we really want to use our existing .wim files (syspreped/captured using MDT) to deploy to the masses. We've had some level of success in setting up a template, but keep running into issues with getting the partitions setup and working correctly. I have read that since we're using ImageX, both the system reserved partition and actual OS partition need to be created before the image can be applied. We must be missing some option/action to not get a working OS. Here's a rundown of our first couple steps:

We first remove any existing partitions:

Then create the system reserved partition:

Then create the OS partition using rest of HDD space:

Then we apply the image using ImageX:

We noticed the problems after adding in the step to create the system partition, the template fails when the image is applied. In this scenario, we use the following command to apply:   /apply \\mis-landesk\ldlogon\Images\Rev3.3_x32.wim 2 C:     Using diskpart, I can see the on the disk that Volume 1 has no drive letter and is not formatted (raw partition), Volume 2 is labeled as C and is formatted as NTFS

If we take out the step to create the system partition, the image does get applied and the template will run all the way through to the Reboot step after HII (in post OS install section), but after this reboot, we get a non-system disk error as if there is no OS loaded. In this scenario we use the following command to apply:   /apply \\mis-landesk\ldlogon\Images\Rev3.3_x32.wim 1 C:     When running diskpart this time, the only volume that shows of course is just C.

Another thing we're confused about is if there are any additional steps that are critical to getting a working, running OS. I have seen posts about using FixWindows.exe and FixUnattend.exe and am wondering if these need to be thrown in somewhere.

Just to gripe: I can definitely see the usefulness of provisioning and what it all can be used for, but initially getting to the point where the product is use-able is a struggle it seems. We're wishing that LD would have supplied some OOTB examples of the different scenarios of provisioning. IMO, the few templates that are available on the community don't seem to help folks like us that are starting from scratch and trying to make use of this product.

Attached is our template. As always, any help is appreciated!

Applies to LANDesk Management Suite 9.0 SP3 and newer

Issue:

Cannot right-click a provisioning template to schedule it.

Schedule option is greyed out.

Cannot schedule OSD scripts.

Cannot create OSD scripts.

Cannot select Windows PE for the Boot environment when creating a new provisioning template.

Cause:

Installed a new 9.0 SP3 Core Server using the existing 9.0 SP3 Core Server's DB.

Note:  The issue can also be caused by moving the existing LANDesk database to a new database server.  Also take note that the same symptom can occur for LANDesk(R) Management Suite 9.5 and 9.5 SP1.  The solution below is the same.

Solution:

1. Run the following SQL statement against the LANDesk database:

update keyvalue set intvalue=0 where applicationname='WAIKLicenseAgreement'

2. Reopen the LANDesk Console and accept the license agreement.

Boot wim does not download from PXE Rep on Dell E7240. Device has Intel Boot Agent GE v1.5.38.01. MTFTP pops up but then nothing downloads.

Anyone else seen issues with this version of the Intel Boot Agent?

Regards