Hi,

I working on provisioning and when I go to HII Driver Manager, I can not disable drivers or run the build library. When I build the library, I get a permission error on the drivers.db3. What permissions are needed to do this operations.

Thanks ahead of time for any information.

We are using LDMS 9.5 SP1

I am trying to create a provisioning template thatwill build a system from OS deployment to final install steps. Have been successful but have one problem that prevents usage on a Global scale. Installing the Advanced agent. If I use the Configure Agent Action item I am successful all the time. The down side is sites in Eastern Europe or Greater Asia, agent install is 30 - 60 minutes, if lucky. Using a complied Agent EXE that provisioning template runs is a little more tricky. If I use a complied EXE that contains Desktop Manager, the device fails to communicate to the core properely and the next 'Map/UnMap to Preferred Server' fails with "unable to establish session with Server <our core>'. If I use a complied EXE that has Portal Manager instead again successful all the time. Issue here is that we have found an issue with Portal Manager when a certain number of packs containing a certain size total source is selected it crashes the Portal Manager. LANDesk Engineering are aware of the issue and state "will be fixed in the next version of LDMS" So has anyone ever done this using the complied EXE w/ Desktop Manager or have an idea how I can make it work Globally?

Regards

Laszlo

Hi All,

I wonder if anyone is still using this method. We had some old scripted install templates that we use once in a while that now do not seem to work since our upgrade from 9.5 to 9.5 SP2. The template consists of the following up to the failure:

WInPE:

Pre OS Installation:

partition - remove all

partition - create

partition - mount

partition - make bootable

partition - format

OS Installation:

Map drive to LANDesk (for OS install files and drivers)

copy drivers

wait 5 seconds

Scripted install

Basically it gets to the point of booting after sysprep and we see this error before ldprovision closes. We have verified no firewall is interfering, along with making sure the NIC drivers are installed properly and we can access the core server via http and ping. Has something changed in this service pack? Can anyone make sense of this error code?

Thanks in advance,

Hi All, I'm fairly new to Landesk (9.5 SP2), I've setup a provisioning template using the guide here. The template works through fine until I hit the CTOS stage. It deploys my image, injects my unattend.xml (which is basically unchanged from the example) and performs HII. It then boots into windows and nothing happens. The windows machine now has:

c:\ldprovisioning folder populated with files

unattend.xml in both c:\ and c:\ windows\panther

It does not seem to have a scripts folder or setupcomplete.cmd in c:\windows\setup

If I manually run the file in c:\ldprovisioning\ldprovisioning.cmd then it continues as normal onto the next steps of template. Is there something i'm missing here? Why isn't it automatically running the ldprovisioning.cmd. It's such a small thing but its doing my brains in!

Cheers!

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!

In "My OSD Scripts" i can delete, but in the ALL OSD Scripts, i cannot.

Is there a way?

thanks.

I am new to provisioning so please bear with me. I am using LDMS 9.5. I am trying to setup a Windows 7 64bit image using Ghost32.exe I have my template set to:

1)Delete partition

2)Map imaging Drive

3)Deploy Image

From there it will inject my ghost image, add drivers, join domain, add software and run inventory scan via Landesk.

When I start the template it maps my drives but fails at deploy image. The error i get is: error 80001803h : Execute Result 5 The action failed. I have attached a copy of my xml file and screenshots of the error message.

Any help would be greatly appreciated.

Thanks,

James P

I am trying to deploy to a Dell 7010 using provisiong and HII. Everything goes well until you get to the HII part. It will install all the drivers and then get to the end and say it failed. Does anyone have any clue what would be causing this?

CMD screenshot:

HIIHandler Log:

2013-12-20 00:16:07(1856-896) HIIHandler.exe:Going to excute HIIClient  /uncpath /taskid 100

2013-12-20 00:16:59(1856-896) HIIHandler.exe:Failed to execute HIIClient  /uncpath /taskid 100

2013-12-20 15:23:03(1352-2004) HIIHandler.exe:Failed to execute HIIClient  /uncpath /taskid 101

2013-12-20 15:34:05(1332-1328) HIIHandler.exe:Failed to execute HIIClient  /uncpath /taskid 102

I have also attached the dism.log

any help would be great.

Using LD 9.5 SP2 we are still running into an issue where if we use the PXE Representative Deployment task the install works fine.

After modifying the boot image, the instructions are to redeploy the PXEs.

If we re-run the deployment task, the only thing that appears to happen is an uninstallation of the PXE rep and services.

We then have to run it a second time and the services all re-appear.

Is this a known issue? This is the same problems we saw in LD 9.0 SP2.

We currently work around the problem by not following the instructions to re-deploy and simply use robocopy to copy the files out to the PXE reps.

I am using a provision template and when I install my default agent vulscan kicks off.  This slows down the provisioning process greatly as the template does not progress until vulscan completes.  How can I stop vulscan from running when the agent is installed.  I am using the "Install Agent" action item in the template and there are no command line aparamenters to use.

Thanks,

Jim

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)

Applies to LANDESK Management Suite 9.5 SP2

Issue:

How do you set up provisioning to deploy a Windows 8.1 image to BIOS booted computers with the LANDESK imaging tool (IMAGEW.EXE v2)?

How do you set up provisioning to deploy a Windows 8 image to BIOS booted computers with the LANDESK imaging tool (IMAGEW.EXE v2)?

How do you set up provisioning to deploy a Windows 7 image to BIOS booted computers with the LANDESK imaging tool (IMAGEW.EXE v2)?

What mode is required by provisioning for sysprep?

Solution:

Follow the instructions in the LD95SP2ProvisioningBIOS document attached to this article. The document only shows Windows 8.1 but the same steps will work for Windows 8 and Windows 7.

I've read multiple documents on how to provision a new Windows7 workstation starting with an image.  I'm looking for a way to provision a workstation WITHOUT using an image as a starting point - rather, install Windows7 from scratch using an unattended file and within the same provisioning template, applying all relevant drivers, a standard list of applications and patching it all before placing it into production.  I'm not worried about the time this process takes, because once it is started, it just runs.  I'd rather manage a few text files (unattended, driver locations, etc.) than manage an image repository that needs to be updated periodically.  At a high level, I'm envisioning booting to WinPE, having my provisioning script run that maps a drive to my OS source location, and runs setup.exe /unattended.  Have people tried this and failed, or is it just not possible, or realistic to provision without an image file?

Has anybody succeeded in using profile migration to migrate from WXP to W8? Tried to use UMA to migrate a profile from a WXP machine to a new W8 pc and it copies the SMA file to the W8 ws but does not restores the contents of the profile. The task completes without errors but nothing is restored. Same task sent to a WXP machine works perfectly. Is LDMS 9.5 SP2 profile migration feature compatible with W8?

Any ideas?

Hi,

we have an issue with the HII Driver Management. I tried populating the db for a HP EliteBook2170p. So far it worked for all the pnp drivers which are perfectly installed during the first startup after the image deployment. Now we have a dedicated graphics card driver (Intel) which should be installed instead of the "default-vga-grphics card" (don't know if its called like that in english, just a guess).

So here is what I did:

- created a package with the setup files and the correct command line

- went to HII Driver Management and selected "Assign"

- chose the correct Make, Model, OS and Architecture. It showed me a list from a captured inventory with all the drivers in there

- selected "Driver Package" and the respective device out of the device list on the left (the hardware id is the one i can see in the device manager on the HP machine)

- created a provisioning template with a HII action in "system configuration"

- scheduled the template and ran it on the client but nothing happened

All the configurations were done on the core directly. We are running 9.5SP2 with no component patches so far. Does anyone have a similar issue? Am I doing something wrong?

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.

I am trying to image a HP t510 thin client using LANDesk and Image W.  Below are the Image W commands I used.

Capture -  /b /d:0 /rb:0 /f:\\coreserver\ldimaging\Images\Image.tbi

Restore- /r /o /x /d:0 /rb:0 /f:\\coreserver\ldimaging\Images\image.tbi

I captured the image and send it back out to the thin client.  I followed the instructions in the link below.

HP Thin Client Management with LANDesk Management Suite 9.5

  When Windows goes to start up I receive the error below.

I noticed the errors below in the "setuperr.log."

According to the link below this is an issue with the second partition not being created.

Windows Embedded Stanard 7 - Sysprep Failure occurred while executing ewfcfg.dll,EwfSysprepSpecialize

With all that being said I have a few questions for the community:

• What is the best way to create multiple partitions with LANDesk?
• Has anyone found documentation on the imagew switches?

Message was edited by: Chris Clinton

Hey guys - can anyone tell me if they have the requirepref switch for sdclient working in winpe?

if i run these

sdclient.exe /f /o /dest=x:\win_prov_files.xml /p=http://CORE/ldlogon/provisioning/win_prov_files.xml

sdclient.exe /f /o /dest=x:\win_prov_files.xml /p=http://CORE/ldlogon/provisioning/win_prov_files.xml /attemptpref

it works but no preferredservers.dat file ( as expected )

if i run this..

sdclient.exe /f /o /dest=x:\win_prov_files.xml /p=http://CORE/ldlogon/provisioning/win_prov_files.xml /requirepref

I get an error downloading file... and no dat file. this used to work fine in winpe ( been using it in the past ).

This is 64Bit winpe ( need to try 32bit yet... will update my findings. tried 32Bit and its fine...so )

however same command on full client in windows - works fine so the it just appears to be winpe... can anyone else try that command in provisioning and tell me if it works for them?

Its a download of an xml of the core - it serves no purpose the file could be any file for this test.

Has anybody had any sucess provisioning a Lenovo Thinkpad Tablet2 device? We're running 9.5 SP2, and I cannot get it to boot from a Provisioning Boot medium writen to a USB stick. The tablet is 32bit UEFI, it seems the slightest hint of anything 64bit on the boot medium causes it to fail.

Is there anyway of forcing 32bit only when creating the \ldmain\landesk\vboot\bootmedia.wim file?

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:

How to use a "Provisioning Agent" with a single agent install method