Quantcast
Channel: Ivanti User Community : All Content - OS Deployment and Provisioning
Viewing all 1803 articles
Browse latest View live

LDMS 9.5 SP2 Scripted OS installation

$
0
0

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,

 

untitled.JPG


Provisioning won't logon as Administrator

$
0
0

I have been trying to use the sample provisioing templates and sysprep xml files. I can everything to work ok except that after the macines images, goes through HII and reboots it says it can't logon as Administrator. If I log it on manually it works fine (runs through the sysprep, installls agent etc). I've been working with support and so far haven't really gotten any help. I've double checked the AdminPass variable is set right, the autologon count in sysprep is set. Any ideas or has anyone else had this problem? We currently use ghost and landesk to re-image all our computers but we'd rather really just use one product. I really don't want to go around and logon hundreds of computers to the admin account manually...

 

Thanks

Steve

After CTOS, provisioning don't continue

$
0
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

Provisioning tasks stopped, except from the core

$
0
0

hello,

we are having this odd issue.

all provisioning tasks are failing except from the core they work.

this has been working forever until last week.

no gpo's, patches, etc have been deployed..

 

we found that running this command fixed it.

C:\Windows\SysWOW64\inetsrv\appcmd.exe" set config /section:staticContent /+[fileExtension='.bat',mimeType='application/bat']

 

has anyone else run into this?

 

thanks


Windows Setup cannot access install sources

$
0
0

Hi,

 

i got a strange problem i cant make sense of,

i got a couple of DELL Workstations, that i need to install with win7 32 bit.

 

i got a working provisioning template via unattended xml for 32 bit

 

on the dell workstation it keeps telling me it is unable to access the installation source right of windows setup starts.

 

i tested both a vmware virtual machine, a xen virtual machine, both are installing from the source without error, a hp desktop also is installing from same source.

 

i swaped memory of the dell workstation, changed bios settings for ahci / ata, reset bios, updated bios.

 

anyone has had that problem or another hint what to try?

 

Thanks

 

Dirk

9.5 SP 2 any action other than HII and inject script in Post OS installation fails and halts progress including CTOS, Wait, Make directory

$
0
0

This is a brand new core server with LANDesk SP2 installed. We do have a case open but I wanted to post this to the community to see if anyone else has seen this.

 

HII runs normally and is sucessfull then CTOS fails with the following erro from the log:

 

2014-04-29 22:40:13(1512-1992) ldProvision:*********  Begin an action - Configure_target_os

2014-04-29 22:40:14(1512-1992) ldProvision:Do EnvironmentCheck

2014-04-29 22:40:14(1512-1992) ldProvision:Is WinPE Action=1, Is WinPe Environment=1

2014-04-29 22:40:14(1512-1992) ldProvision:Report might reboot status to core.

2014-04-29 22:40:14(1512-1992) ldProvision:Call web service SetActionStatus()

2014-04-29 22:40:14(1512-1992) ldProvision:Start TryallWebService Attempt:0.

2014-04-29 22:40:14(1512-1992) ldProvision:End TryallWebService Attempt:0. ExitCode:0

2014-04-29 22:40:14(1512-1992) ldProvision:Session Data: <variables/>

2014-04-29 22:40:14(1512-1992) ldProvision:Caught exception in main: code=80001800H, file=..\shared\src\ProvisionAction.cpp, line=207

2014-04-29 22:40:14(1512-1992) ldProvision:Call web service GetStatusString()

2014-04-29 22:40:14(1512-1992) ldProvision:Start TryallWebService Attempt:0.

2014-04-29 22:40:14(1512-1992) ldProvision:End TryallWebService Attempt:0. ExitCode:0

2014-04-29 22:40:14(1512-1992) ldProvision:StatusString = An unknown action was specified: {0}.

2014-04-29 22:40:14(1512-1992) ldProvision:Call web service SetActionStatus()

2014-04-29 22:40:14(1512-1992) ldProvision:Start TryallWebService Attempt:0.

2014-04-29 22:40:15(1512-1992) ldProvision:End TryallWebService Attempt:0. ExitCode:0

 

I seaarched for the file ProvisionAction.cpp on the core and it does not exist

Also, the unattend.xml is at the correct location J:\unattend.xml

CTOS is not creating the directory LDProvision on the J:\ directory

 

So I thought ok I will put a wait command of 120 seconds before the CTOS command..

It failed also with the same type of error "An unknown action was specified"

 

I also tried to create an action  to Make the Directory J:\Ldprovisioning which gave me the same error as above..

 

I also tried a wait and make driectory command before HII and the task action fails If I take any commands out of the secotion and just leave inject script and HII  that part works but CTOS is failing so Provisioning is borken.. Mind you this is a brand new install of 9.5 SP2.

 

Has anyone seen this and offer a fix??

PXE Representative Deployment - Reinstall Fails

$
0
0

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.

How to Deploy a Windows 8.1 UEFI image with IMAGEW.EXE v2 in LANDESK® Management Suite 9.5 SP2

$
0
0

Applies to LANDESK Management Suite 9.5 SP2

 

Issue:

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

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

What mode is required by provisioning for sysprep?

 

Solution:

 

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


provisioning - map drive fails

$
0
0

Hello All,

 

I am working on provisioning and it failed my first time around. So I have decided to take it step by step to see what has gone wrong.

 

I can get it to wipe and format a drive and assigned it as “C” drive, however I cannot map a drive from the server to the C drive.

 

The following shows on the window called LANDesk Provisioning Agent:

 

Connect to core: (server name)
Loading Template
action index=573
FAILED

Error:[800001803H]The action failed.

Execute result:

Return:1326

Output:

 

Any clue?

Thanks!

Hang after reboot action

$
0
0

Hi

 

We install several software during the provisioning, one software needs a reboot after installation. So we put in the reboot action in the template. When we start the scheduled task from the template with 12 clients, 8 clients do the task successfully. The other four clients hang after the reboot action and do nothing (the provisioning agent do not start after the reboot). There are still a few actions pending, the task is active and after a few hours the task is failed.

 

Have someone an idea, what the problem is with the reboot or why the provisiong does not start after the reboot?

 

Thanks

Landesk HII

$
0
0

When I open my HII Driver Management, there are no files there. If I go to assign, there will be an inventory of the drivers for a model there that I am working on. If do Build library that work fine and show results like it should be. I am working on setting up provisioning but having issues with installing drivers. How to get the drivers to appear in the HII Driver Management? Any thoughts on how to fix this?

 

Thanks,

Losing drivers and partition sizing on OSD deployment

$
0
0

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

Are using LDMS 9.5 SP2. Imaging a Dell E7440.

My steps have been:

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

I check for partition # of C drive using diskpart

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

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

Image capture itself seems to work

 

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

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

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

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

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

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

Thanks in advance.

HII During System Config Causes Blue Screen

$
0
0

I am on 9.5 SP2 and I have certain models that if I assign a package to the drivers it causes the computer to blue screen at the HII step in system configuration.  If I remove the assignment it works fine.  Shouldn't it only try installing the package and not any other dirvers?  Seems like thats the case.  If I run the package as a step in the provisioning it works fine.  Not sure what's going on.

 

jv

Provisioning with HII

$
0
0

I am using 9.5 SP2 and working on getting provisioning to work. I have a video driver that doesn't installl during provisioning. The files get downloaded to the workstation and the files are in the c:\windows\lddriverstore. Once the image is complete if I try to update the driver manually and point to the c:\windows\lddriverstore it works fine.  Any toughts as to why it does not install via provisioning? I see the Landesk mirroring driver get installed but not the correct video driver. Thanks

Scheduled Tasks vs Provisioning deployment

$
0
0

Has anyone else encountered or noticed that a scheduled task of a distribution package can run rather quickly, but take the same distribution package and include it in a provisioning template and it just takes forever? Was trying to make a provisioning bundle if you will that includes multiple distribution packages into 1 single provisioning template. If i was them separately as a scheduled task they complete in a few minutes. As a provisioning template my first install is taking over 12 hours and isn't even halfway done downloading.

 

Can't seem to figure this one out


Assigned drivers install order

$
0
0

Is there a way to specify the order assigned driver packages will install?  I am trying to assign drivers for a panasonic toughbook, but the panasonic driver bundle package loses network connection when it installs.  Then other assigned driver packages do not install (intel proset, sierra wireless, usb3) because it does the panasonic driver first.

Powershell. The Jelly Belly with LANDESK Provisioning.

LDMS 9.5 SP1 - cannot restore domain account profile using Provisioning Deploy Profile

$
0
0

Environment:

- LDMS 9.5 SP1

- Agent installed on Windows 7 64bit SP1

 

I have this case when I wanted to Deploy Profile using Provisioning, Local account always successfully restored, but not a domain account.

 

Every time this domain account login, on system tray always show a baloon that said "this is temporary account bla..bla..bla".

Already tried restart and then login again, always the same baloon poped out...and after the 3rd login attempt windows throw "The group policy client service failed the logon".

 

This is the steps that I do for testing, and the PC are already join domain and theres already a domain account set up:

1. Login using local account

2. Capture Profile using provisioning, this contains one local account and one domain account. (Success)

3. Restore windows to its original state with an empty local account profile.

4. Deploy Profiles using provisioning, the tasks sequence are all success.

5. Restart.

6. Login using local account, the delayed UMA windows appear and then automatically restart.

7. Login using local account and check whether the profile are restored correctly. it is restored correctly (success)

8. Logged off and then logged in using domain account.

9. The delayed UMA appears again and then automaticcaly restart.

10. Login using domain account, then the baloon pop up started appear.

11. Restart again, login using domain account, the baloon pop up appear again.

12. Restart again, login using domain account, then the account are locked out and show  "The group policy client service failed the logon".

 

Another behavior that I'm observed is, it seems like SMA creating a profile called TEMP on the C:\users folder

 

Any insight, solution or workaround are appreciated

OSD Capture Script Issues

$
0
0

I have a few questions about your product in regards to
capturing a Windows 7 image using the steps “How to Capture a Windows 7
image with OSD using Imagew.exe v2 in 9.0 SP2 & SP3 and 9.5
” which can be found at this link How to Capture a Windows 7 image with OSD in LANDesk® Management Suite 9.5, 9.0 SP2 and SP3. I added the link that I used so that you can see what I have already
completed and the step that I’m getting stuck on and perhaps you can give me a
solution to this issue.

 

So the step that I’m having trouble with is the last step on
this document. Once I select the “OSD capture script
(Capture_Windows_7_Imagew)
” at the end of this document I’m not seeing the
process that the last page shows (which is the progress of Creating Image).
Instead I see two or three command prompt windows that appear and disappear and
then I just see the LANDesk background only. I do not see the image in the last
step of this document. Any ideas what this could be from?

 

I have tried the different options for running SYSPREP.EXE
for the Image Capturing and still have had no luck.

Installing LD agent with preferred server

$
0
0

Currently we copy the LD agents used for provisioning to an OSD folder which contains items we replicate for the preferred servers. We then use an action in PRE-OS to copy the agent to the c: drive.Then in system config we execute that file to install the agent. Before the recent component patch upgrades I believe the system would wait for that agent to install. However now it does not seem to be doing that and just moves to the next tasks.

 

I would use the action "configure agent"  but it seems to pull this from the core in the ldmain directory. I don't want to replicate all of ldmain to preferred server just for agent installing.

 

Anyone else noticing what I am?

Viewing all 1803 articles
Browse latest View live