Does anyone have any guidlines on how to image a MS Surface Pro 2 device.  I know that it is UEFI which we have never done.

Thanks! 

Hello

I was wondering if there is a way to change the script to capture more than one disk? Currently I am only able to capture one disk but noticed there is no option to capture anything other than that one drive on the GUI. Any help is appreciated.

Has anyone found a NIC driver that will work with LDMS v9.5 Sp1 (WinPE 4) for the Dell Optiplex 9020 Intel NIC?

I have someone with issues and dont have this hardware to test with so hoping someone else has had the same problem. We have tried the Windows 8 drivers from both Dell and Intel with no luck.

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

Hi all,

Im testing LD 9.5 sp1 in my lab

I have provisioning tempeltate for restoring Windows XP, tempeltate looks like:

In WinPE:

- delete all partition

- create system partition

- restore image (Windows XP)

- inject script (sysprep.ini from DOC-2513)

- configure target OS

After reboot to Windows XP:

- install agent

Basicly this is simple image restore based on DOC-2513

All is going well till coputer reboot after configure target OS task. In LD console I see that last job is configure target OS and status might reboot

On test machine after reboot the Windows XP is configures automaticlly (using info form sysprep file) and after Windows XP run nothing happends....

I see ldprovision folder on C drive and the residentAgent.exe process in Task Manager but nothing else happends.

Has anyone had a similar problem?

Thanks

Hi,

I have problems with provisioing, before it was ok, but for few days, when i use provisioning, just after the CTOS, the computer reboot and make the sysprep installation, after that... nothing happens...

Please help.

Thanks

Ben

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?

I recently provisioned 150 HP/Lenovo laptops using LDMS 9.5 SP1 with HII.  For some reason, 3 HPs stopped during the middle of the provisioning template.  The task quit in the system configuration section of a template.  Is there a way to continue the task (I tried to PXE boot again to WinPE Provisioning, but no go) OR should I just delete the existing task and restart?  I appreciate any help given.  See pic.

Thanks,

Jeremiah

Problem

The provisioning task is failing to load. It will attempt to load the template and retry for 40 attempts and then the job hangs and the PC stays in the WinPE screen or brings back the template section window.

Logs on the core may indicate a few different errors:

In prov_schedule.exe.log:

     In LDMS 8.8 this log is at \\core\ldmain\ in LDMS 9 it will be at \\core\ldmain\log

Template is not flattened, will attempt to flatten.
Flattening  template failed.

In provisioning.log:

     In LDMS 8.8 and LDMS 9 this log is at \\core\ldmain\log\provisioning. It may be necessary to enable additional logging.

Unable to find the history task

or

Unable to find template for computer idn ###

Causes and Resolutions

First, make sure that the latest service pack and the latest miniroll-up are applied to the core.

Scheduler service being stopped

• If the scheduler service is not running, provisioning jobs will not start.
• DCOM errors can causing the scheduler service to stop.

Resolution

• Change the service to run as a domain admin and started the  scheduler service. Once this is done, the provisioning task should work.
• Reset the password for the admin account that was running the LANDesk and LANDesk1 COM+ objects. This prevents the scheduler service from failing which prevents the provisioning template from running.

Current Provisiong Task in Progress on Selected Machine

• If a provisioning task has already been assigned to the machine in question, the task will fail. If you review the provision.log file on the core you will see a line "Computer is Busy with another task {taskID}"

Resolution:

1. Determine the TaskID from the log, Go to your Core and delete that task.
2. Delete client from database
3. PXE boot client, or run a manual inventory scan from the device
   1. A Manual scan can be initiated from WinPE by running X:/Windows/System32/Startnet.cmd from a command prompt
4. Run the provisioning task

Corrupt Template

• A corrupt template can prevent correct scheduling. One cause if this is if a template is imported, the drop down boxes are not filled in as they were pointing to objects from the previous core. For example, Software Distribution actions do not have a package specified. Same with Configure Agent actions. Also any actions with scripts will have this issue.
• Another way to determine if your template is not configured properly is by reviewing the Provisioning.log on the core. If you see the following:

INFO    PROV_SCHEDULE        8/18/2011 5:06:50 PM     : Action LANDesk.Provisioning.Business.PAction_Distribute_software
INFO    PROV_SCHEDULE        8/18/2011 5:06:50 PM     : Got package ID 60, requesting snippet
INFO    PROV_SCHEDULE        8/18/2011 5:06:50 PM     : Requesting snippet for packageId 60
INFO    PROV_SCHEDULE        8/18/2011 5:06:50 PM     : Requesting SWD snippet with task IDN 2214, package ID 60
ERROR    PROV_SCHEDULE        8/18/2011 5:06:50 PM     : Exception encountered trying to get snippet (LANDesk.ManagementSuite.SoftwareDistribution.Business.PackageNotFoundException): This package has been deleted.
ERROR    PROV_SCHEDULE        8/18/2011 5:06:50 PM     : GetSoftwareSnippet failed

Resolution:

• Recreate the template, or make sure that all dropdown boxes and options are configured in the template and all included templates.
• If you are getting the error where you are unable to get the Software Snippet, you will need to go into your Provisioning Template and make sure that all software packages are available and working. Determine which package is failing and resolve the software package. Save your template and retry the provisioning task.

Template is trying to perform an invalid action

• Error when attempting to save template

Cannot save changes to the template . Verify that the template name you have chosen is not already used by another template. Database Error.

Resolution:

• If you are adding included templates to a main template you will want to start with adding the included templates one at a time until you find the problem template. Then address the specific of that template and what it is doing. Try to recreate a new template that duplicates the problem template and see if you get any errors while saving the template.
• Here is a situation that a customer came across.
• The problem template was one to Update Registry action item and the Registry Operation of Import File. Because the file that was being imported was a combination of different registry export files, and remarked out descriptions had been added to the file, the template would return error: "Cannot save changes to the template . Verify that the template name you have chosen is not already used by another template. Database Error." The initial problem came from the fact that the original template did save when maybe it should not have, which caused the provisioning task to fail and the Prov_Schedule.exe.log file to show "Flattening template failed". Once we isolated the issues with the remarked out lines in the reg file and removed them, the template saved and the provisioning task worked properly.
  The real resolution came after adding the included templates to the main template one at a time until we found the problem template. The problem template was one to Update Registry action item and the Registry Operation of Import File. Because the file that was being imported was a combination of different registry export files, and remarked out items had been entered, the template would return error: "Cannot save changes to the template. Verify that the template name you have chosen is not already used by another template. Database Error." The initial problem came from the fact that the original template did save when it should not have, which caused the provisioning task to fail and the Prov_Schedule.exe.log file to show "Flattening template failed". Once we isolated the issues with the remarked out lines in the reg file and removed them, the template saved and the provisioning task worked properly.
  In my customers environment, having the remarked out comments failed, but in my lab the customers reg file worked fine. After getting the reg file to import and save, we found that the script failed on the reg file when trying to run the reg file. What we discovered is that in his situation, the header in the reg file that says: "Windows Registry Editor Version 5.0" was causing it to fail, but I was unable to duplicate any of his problems in my lab. This seems to be a unique situation and may or may not apply to other customers that are having the 40 of 40 retries issue.

 

LANDesk is trying to find a provisioning task from a failed distribution

• The provisioning log will show  "Unable to find the history task"

Resolution:

1. Delete client from database
2. PXE boot client, or run a manual inventory scan from the device
3. Run the provisioning task

To many PXE Reps to update with the Provisioning information for the device

• If there are a large number of PXE representatives in the environment, this error will occur as the core tries to update them all with the needed information. If it cannot complete in time for the 40 retries, the task will not start. However, if you keep waiting the template may start.

Resolution:

• Reduce the number of PXE reps and remove all PXE Reps that are not active.

Hello,

At my company we used Windows Deployment Services (WDS) together with

pxelinux ( http://syslinux.zytor.com/wiki/index.php/WDSLINUX ).

This made it possible to boot/install window and several linux flavours like this:

DHCP with PXE, then via tftp pxelinux.0 was loaded with pxelinux.cfg/default containing a menu to select boot/install of windows/linux etc.

Now my company switched to LanDesk and I need to integrate our old pxelinux menu.

LandDesk brings it's own dhcp/tftp server which serves an "F8 Menu".

I see two options:

1) extend the current LanDesk "F8 Menu" to have an option to load our old pxelinux.0 and pxelinux.cfg/default

    into the  ROM of the network card.

    How could I add an extra option to the "F8 Menu" ?

2) or replace the inital boot rom:

    As far as I know the first file that gets loaded via tftp during pxe boot is X86PC\UNDI\BStrap\BStrap.0 so I guess tis is what responsible for the "F8 menu"

    Is it possible to tell LanDesk to use e.g. X86PC\UNDI\pxelinux\pxelinux.0 instead of X86PC\UNDI\BStrap\BStrap.0 ?

    How and where could I change this setting ?

   I already tried to overwrite X86PC\UNDI\BStrap\BStrap.0 with pxelinux.0 .

   But although I restarted "LanDesk PXE" service nothing happened, I still got the "F8 menu"

   In context  to this I am wondering what the function of C:\Program Files (x86)\LANDesk\PXE\System\BStrapOpts.Dll  is about.

Any help is much appreciated

Hi

Is there a way to automate the hostname of a machine from the service tag in the bios when its deployed?

OR

A script that can change the service tag in the bios to be the same as the hostname?

Thanks in advance for any help.....

Colin

Hi,

I'm trying to deploy an image for the first time in our LANDesk 9.5 environment using provisioning templates, everything runs smoothly until I get to the deploy task which fails every time.  Having looked in the ldprovisioning.log which in turn has pointed me to the maptopreferredhandler.log the error seems to be cause by the task failing to map to the location the image is stored:

maptopreferredhandler.exe:*******Mapping to: \\server01\d$\images\image01.img

maptopreferredhandler.exe:Drive letter - f

maptopreferredhandler.exe:Attempt preferred server

maptopreferredhandler.exe:Could not map or unmap drive. Error code: 86

maptopreferredhandler.exe:*******Unmapping drive

maptopreferredhandler.exe:Drive letter = f

maptopreferredhandler.exe:Could not map or unmap drive. Error code: 2250

maptopreferredhandler.exe:End of UnMap Drive.

I thought the issue may be caused by the account on our preferred server being unable to UNC to the server, however I was able to map a drive manually from the Win PE to the server using the account.  To further complicate matters the credentials test for UNC on the preferred server for the same account fails (I have re-entered the password).

Any help greatly appreciated.

I am trying to deploy a PXE rep on one of my subnets but keep hitting my head against the dreaded PXE-E32 error.

I've tried both with "Transmit MTFTP large packets" on and off in the PXE config, I've tried toying with the MTFTP timeout delay but keep getting the error : the client gets a DHCP IP address without a hitch, I select WinPE and then PXE-E32 happens.

I've tried redeploying the PXE rep, no luck there.

What really troubles me is that if I create a VM on that server and deploy the PXE on that VM....it works flawlessly. The only difference I can see there is that the server has 2 NICs (one with a fixed IP and one with DHCP) whereas the VM only uses one (it's bound to the DHCP NIC on the physical server).

While I could just use the VM as a PXE rep on this subnet, I'm trying -not- to do that : we've done it in the past and the VM would need to be restarted every few days, due to not responding to pings anymore and therefore PXE boot not working. We also have a bad case of VM's and AD not liking each other that much, but that's another story entirely.

I've read that the error could be due to the physical switch not allowing MTFTP (tried with regular TFTP and was greeted by PXE-E35 and PXE-E39) but since it works fine on the VM, I don't see how that could be possible.

Obviously, I've compared the PXE config of the VM to the physical server's one, and they're identical.

This is with LDMS 8.7 SP5, if it makes any difference.

Any ideas before I go ahead and open a case ?

Hello,

Since recently upgrading our LANDesk core from 9.0 sp0 to sp2, our provisioning tasks have been failing.  In the cmd.exe window during the pxe process, it successfully gets past the "reg import all.reg" command.  The next part lists partitions, then displays the error message, "VBoot partition not found on disk."  After a few seconds, it then appends, "Value CoreServer exists, overwrite (Yes/No)?" to the end of that line.  If this came up before, it managed to get past it on its own.  Now, you have to answer.

If you hit yes, it claims the operation completed successfully, and spits out the dhcp address along with 127.0.0.1.  Then it says resolving core server name (/f)..... and fails.  It repeats this several times until it errors, "Timed out when resolving core server name."  If you hit no, it reports, "The operation was canceled by the user," and again spits out the ip addresses.  Then, it says, "resolving core server name (%mycoreserver%)..." and fails after multiple retries as before.

In either case, the suggestion printed at the end is to check your network and to inject drivers into the WinPE image.  However, we've deployed to these exact machines before and had no driver issues.  No drivers have been added or removed to the image since the upgrade (drivers were added before and have been working just fine for us).

I notice in the readme for sp2, "Enabled VBoot in provisioning" is listed under Important changes and additions SP2.  I've been unable to determine how to disable that to see if that would resolve our issue.  Can anyone offer some guidance on where to go from here?

thanks,

Brian

Does anyone have any idea why when using the symantec imaging tool with LANDesk that the system just hangs at the LANDesk screen but images fine with LANDesk images.

Does anyone know what this log file means?

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

"MES-4545-C2-041","OK",0,0:00:00,2/7/2014 2:46:38 PM,2/7/2014 2:46:38 PM,"WINPE, TIMEOUT=1800"

"MES-4545-C2-041","OK",-2147024809,0:00:02,2/7/2014 2:46:39 PM,2/7/2014 2:46:41 PM,"diskpart /s X:\LDClient\rmvol.txt"

"MES-4545-C2-041","OK",230227968,0:00:00,2/7/2014 2:46:42 PM,2/7/2014 2:46:42 PM,"ldrun drvmap.exe dcps\administrator 20D539FDE10D33266E245BE8FEF04423A990E383452 I: """\\DHS-FS2.DCPS.Dinwiddiek12.org\NSCap""", STATUS FACILITY=3513"

"MES-4545-C2-041","OK",230227968,0:00:00,2/7/2014 2:46:43 PM,2/7/2014 2:46:43 PM,"ldrun drvmap.exe dcps\administrator 20D539FDE10D33266E245BE8FEF04423A990E383452 H: """\\dhs-altiris-3.DCPS.Dinwiddiek12.org\ghost""", STATUS FACILITY=3513"

"MES-4545-C2-041","OK",0,0:00:05,2/7/2014 2:46:44 PM,2/7/2014 2:46:49 PM,"ldrun sdclient /f /o /dest="X:\LDClient\LDPathExist.exe" /p="http://10.11.11.101/landesk/files/LDPathExist.exe" /disableclientqueue, STATUS"

"MES-4545-C2-041","OK",0,0:00:00,2/7/2014 2:46:50 PM,2/7/2014 2:46:50 PM,"ldrun LDPathExist.exe """I:\bin\Deployment\Packages\Images\e1c9f75c-d0d5-404d-bea5-cdf289639a0a\DHS-MLAB7.gho""", STATUS"

"MES-4545-C2-041","OK",0,0:00:01,2/7/2014 2:46:51 PM,2/7/2014 2:46:52 PM,"ldrun LDPathExist.exe """H:\x64\Ghost64.exe""", STATUS"

"MES-4545-C2-041","OK",0,0:00:02,2/7/2014 2:46:53 PM,2/7/2014 2:46:55 PM,"diskpart /s X:\LDClient\wipeDisk0.txt"

"MES-4545-C2-041","OK",0,0:00:04,2/7/2014 2:46:56 PM,2/7/2014 2:47:00 PM,"cmd /c format /Y /FS:NTFS /Q /V:C-DRIVE c:"

"MES-4545-C2-041","ERR_Fail",-1917321432,0:00:00,2/7/2014 2:47:01 PM,2/7/2014 2:47:01 PM,""ldrun RunBatch -1 h:\x64 Ghost64.exe -clone,mode=load,src=i:\bin\DEPLOY~1\Packages\Images\E1C9F7~1\DHS-ML~1.GHO,dst=1 -sure -auto", STATUS FACILITY=3511"

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

Hey All,

Just getting into the world of Hardware Independent Imaging and everything I've found says that in order to properly use HII you have to use LANDesk Image V2 type images.  Up until this point we have been using ghost images and I would like to continue using them if possible.  So my question is, is it possible to do hardware independent imaging with ghost images?  Thanks

Using a PXE server and windows PE, I have used the landesk osd wizard to create my pxe menu and captured an image. when I went to deploy this image, however, nothing happens. I followed the deployment instructions in the guide word for word (sans sysprep) and instead of going to a screen where the image is being deployed, my deployment script opens a console window for a minute, and then closes with no message, to the windows pe background.

nothing happens.

This is the script generated when I use the deployment wizard to create a osd script.

h:\osd\IMAGEW~1\imagew.exe /r /o /d:0 /f:"""i:\Images\6410\LD5C26~1.TBI""" /rb:0

Hi,

I have problems with provisioing, before it was ok, but for few days, when i use provisioning, just after the CTOS, the computer reboot and make the sysprep installation, after that... nothing happens...

Please help.

Thanks

Ben

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