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

HP ProBook 6460b Specialize pass / HII issue

$
0
0

About two weeks ago (can't for the life of me figure out what changed to cause this), our HP ProBook 6460b laptops imaged with Windows 7 x64 Pro started failing to join the domain after OSD.  All other machine models are working fine.  I started looking closely at the setupact and setuperr logs and they basically say "Domain cannot be contacted".  I've tried injecting several different drivers using HII and all have the same result. 

 

After the image is laid down and HII injects drivers (correct drivers, I've double checked), the machine begins the Specialize pass.  When it gets to "Setup is applying system settings", I Press Shift + F10 to open a CMD prompt and run devmgmt.msc.  The Intel 82579LM Gig NIC is there, but states it cannot start.  If I right click the computer name and kick off a "Scan for hardware changes", the NIC is all the sudden "found" as an Intel 82579V (what it actually is).  The machine grabs an IP and adds to the domain with no issue.

 

Odd thing is, if I let the "Applying system settings" action time out and fail, the machine reboots and LOADS THE DRIVER CORRECTLY, finishing all its network-based installs.  It just isn't installing the correct NIC during Specialize.

 

I've added this particular driver to the image, I've added/removed several different driver sets to the HII driver library.  So far, none of these has fixed the issue.  The 6460b does not install the NIC properly.

 

Has anyone else had issues like this?  It's not 100% an HII issue as it is pulling an acceptable driver.  Windows is just deciding to install the wrong hardware from the right driver during the Specialize pass.


LDMS 9.5SP1 HII Failure

$
0
0

Hello, I've installed the SP1 Update to our 9.5 server but when trying to provision HII fails because the drivers are unsigned. This behavior did not existed on 9.0 or 9.5.

 

DISM return code 50

 

is there a way to modify HII to use the /forceunsigned ?

 

anyone else has this issue?

 

Thanks

Windows Startup Repair after Image Deploy

$
0
0

Hi All,

 

We have an existing TBI based image that has been pushed out to out Dell Optiplex 780 machines for the past two years.

We typically boot into WinPE Menu, select the specific image and deploy. (Have also tried Provisioning via Win7/Agent/Reboot-to-WinPE)

What happens is the image extracts the appropriate partitions, then when it has finished copying files it reboots. (as it should)

When it reboots it goes into "Windows Startup Repair", checks for errors that can be fixed, then announces that it cannot find any problems, asks if we would like to report to Microsoft and then switches off.

When we switch the PC back on it continues into sysprep mode and completes the image install with no further problems.

 

My questions are;

  1. Is this, as I suspect, a problem with the image created by my predecessor?
  2. If so, what is the recommended method of taking a system back to pre-image capture if you only have access to PCs that have had the image deployed to them? (There are so pretty obscure driver and software installs that had to be crowbar’d into this install and I have no documentation on how it was all done.)
  3. If not, can you tell me what the problem might be? Previous attempts at provisioning (another SOE) with the wrong bootable partition/OS partition failed terminally, so given this is fixed by a reboot I don't think it is that.

 

Thanks very much, I don't know what logs anyone might like, but if you're willing to ask for them and help out, I'll bend over backwards to solve this.

 

Regards,

Dean

User Migration Assistant

$
0
0

I just recently finished a bootcamp and am about to deploy a number of machines, previously we used USMT and in the capture batch file we could exclude profiles over X days. I am going to attempt this with the User Migration Assistant, during the bootcamp I asked if it was possible to restrict the profiles migrated by the same method, older than X days, I was told yes it could be however it wasn't an option in the GUI and I'd have to use the advance edit and edit the XML directly. What I'd like to know is what would the correct syntax be for excluding profiles that hadn't been modified in over 30 days? During the bootcamp they weren't sure of the syntax but were sure it could be done.

 

I've looked through the IBM documentation and haven't come across a reference to this particular option. There are references to exluding profile names, that's no problem and can use this for profiles I know I don't wish to migrate but really would like the option of not migrating profiles over the 30 days.

 

Any suggestions?

LDMS 9.5 SP1 HII fails during provisioning because of unsigned drivers.

$
0
0

I have been having issues with provisioning in LDMS 9.5 SP1. it seems to drop the image fin but fails during the HII portion, when i look at the dism log it seems to point to some unsigned drivers. HAs anyone else run into this issue?

 

Thanks

Sean

Provisioning Template - CTOS does not copy whole ldprovision folder or run after first boot

$
0
0

Hello,

 

I have a Win7 x64 image which has been sysprepped (generalized and audit mode) which used to work, but for some unexplained reason it now does not finish the whole provisioning process  No errors are reported in LDMC for it.

 

After the WinPE process completes the machine goes through the process of installing drivers, which is normal.  However once this is done and it boots into Windows for the first time it just sits there.  The provisioning process does not complete.  I have looked around and done as much research as possible, but I have not found an actual solution to the problem at this time.  I have found after CTOS reboots that "C:\ldprovisioning" is created with two files in it - launchldprovisionasuser.exe and ldprovision.exe.  If I execute the first and then the second executables the provisioning process picks up where it left off and installs the agent and any additional packages that I have added to the template.

 

Has anyone else seen this or have any ideas what I can do to resolve it?

TBI name change causes issue with provisioning

$
0
0

We have some images that were captured, & have deployed successfully.  I needed to modify the name of the file & all of a sudden after the pc is imaged, I get a Windows Boot error as if there is no boot device available.  It could just be a coincidence, so I am re-pulling the image & will test again. 

 

Not sure why this is happening - my gut instinct is it may have something to do with a changed hash code, but I don't see anything in Provisioning regarding hashes.

 

Working with LDMS v9.5 (no sp1 installed yet) - also this is a complete windows install - not sysprepped.

 

I'll repost later once I have more results, but if anyone has any ideas I welcome them.

 

Thanks!

HII preview works but not when running HII in regular mode

$
0
0

After updating to 9.5 sp1, HII doesn't seem to be working properly. When trying to image an optiplex 780 with HII it doesn't find any drivers for it. I loaded the HIIClient.exe onto a base 780 machine to run preview on it and as you can see in the log files it finds the drivers just fine but when trying to run it with out /preview it says it can't find any drivers.

 

Commands used were: HIIClient.exe /uncpath \\(path here) /preview /os win7 /arch x86

                                  HIIClient.exe /uncpath \\(path here) /os win7 /arch x86

 

Now I'm not sure if it was sp1 that caused HII to stop working or not because pre sp1 I never tried to image any 780s but our lenovo all in ones worked fine and now post sp1 I don't have any lenovos right now to see if they still work, all I know is the 780s aren't working.

 

Any ideas?

 

Thanks!


Using serial number as computer name in provisioning

$
0
0

Hi,

 

I have followed the following article and successfully used OSD, Sysprep and the computername.ini file to set a computer name to it's seial number.

 

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

 

How would I go about doing the same thing using provisioning?

 

The OS is Windows XP if it makes a difference.

 

Thanks.

9.5 SP1 HII Lenovo drivers

$
0
0

I am working on migrating our provisioning process over to our new 9.5 SP1 core.  Previously, I had used an execute file action in the system configuration section to run the Lenovo Thininstaller for driver installation.  This required a separate template for our laptops as we were using HII to do our Intel based desktop machines.  I would like to use the HII in 9.5 to have one template for both our desktops and Lenovo laptops. 

 

I downloaded the drivers from Lenovo's support site and tried to extract out the drivers from the exe downloaded with 7Zip and it did not extract to a useable form, ie. there were no inf's in the subfolders extracted. I could pull out the driver files by running the exe and getting the inf's from the folder the driver setup creates, but that seems like it would be more work to maintain than continuing using the Update Retriever/Thininstaller process.

 

Is there a possibility that I could find a workable solution with Lenovo drivers and HII?  Anyone had any success with this?  Any other viable solutions?

 

Thanks.

Can you lock screen or input during Provisioning? Esp after CTOS

$
0
0

Is there a nice (read: Elegant) way to do this?  Besides using an AutoIT script I wrote...

 

Seems like you wouldn't want anyone on the "other end" attempting to log in while you are configuring, running HII, joining the domain, and just preparing to reboot anyways.

 

Here's my template after CTOS reboot:

 

Configure 'provisioning' agent

Join domain

Activate Windows

HII

Configure 'real' agent

Delete unattends

Install any other software...

Reboot

 

I already don't autologin here, there's no need to.  I want to disable logging in and bring the UI in front of the winlogon.  Possible?

Provisioning - New C:\ keeps changing drive letters

$
0
0

Hi

 

I have a big of a straonge issue since upgrading to 9.5 Sp1.

 

When we provision, the WinPE image is M, now after the image is  deployed, if i run diskpat and look at the volumes on some machine the new C is N, and on other it is N.

 

I do not know why it does this.

 

Of course the issue is that the sysprep has to be pushed to a drive letter and It fails on half the machines.

 

Can anyone help?

Error 3513

$
0
0

When I tried to deploy my computer stay's in PE

 

On this forum i see many people with this problem,

They have problems with map sharing.

 

both maps I've full controll for every one.

 

What can i do?

Capture script - Ghost spitting out multiple .ghs files instead of one GHO

$
0
0

Hi Everyone,

 

Quick question for those of you more familiar with Ghost that I am. When I create a capture script using Ghost, it is capturing the image and spitting it out as sever 2gb GHS files. I'd like to change that so that it only compiles 1 .gho of the image. I was able to easily do this in the imageW script, but cant seem to find the right trigger for Ghost.

 

 

Thanks in advance!

HP ProBook 6460b Specialize pass / HII issue

$
0
0

About two weeks ago (can't for the life of me figure out what changed to cause this), our HP ProBook 6460b laptops imaged with Windows 7 x64 Pro started failing to join the domain after OSD.  All other machine models are working fine.  I started looking closely at the setupact and setuperr logs and they basically say "Domain cannot be contacted".  I've tried injecting several different drivers using HII and all have the same result. 

 

After the image is laid down and HII injects drivers (correct drivers, I've double checked), the machine begins the Specialize pass.  When it gets to "Setup is applying system settings", I Press Shift + F10 to open a CMD prompt and run devmgmt.msc.  The Intel 82579LM Gig NIC is there, but states it cannot start.  If I right click the computer name and kick off a "Scan for hardware changes", the NIC is all the sudden "found" as an Intel 82579V (what it actually is).  The machine grabs an IP and adds to the domain with no issue.

 

Odd thing is, if I let the "Applying system settings" action time out and fail, the machine reboots and LOADS THE DRIVER CORRECTLY, finishing all its network-based installs.  It just isn't installing the correct NIC during Specialize.

 

I've added this particular driver to the image, I've added/removed several different driver sets to the HII driver library.  So far, none of these has fixed the issue.  The 6460b does not install the NIC properly.

 

Has anyone else had issues like this?  It's not 100% an HII issue as it is pulling an acceptable driver.  Windows is just deciding to install the wrong hardware from the right driver during the Specialize pass.


problem with Variables in COPY FILE action

$
0
0

I am working within the SYSTEM CONFIGURATION section of provisioning on LDMS 9.5 unpatched.  I need a FILE COPY action to run as one of the last steps in provisioning.  The file that I want to copy to the local disk is a .TBI backup of the original image which was written to a network share early in provisioning.  I am using a variable for the .TBI that is created:

 

%ImageShare%%imagepath%%ldDeviceID%.tbi

 

when I enter this same variable in the SOURCE PATH & FILE NAME part of the provisioning action, I get the following error message:

 

"The source path and file name is blank or invalid.  Type a valid source path and file name."

 

If I hard-code the initial part of the string and include the variable at the end like this:

 

\\hostname\path\%ldDeviceID%.tbi

 

it seems to work.

 

 

I was under the assumption that support for variables was universal, but I guess not.  Is there any documentation of where variables don't work?

Windows 2012 Server options missing from Target OS list in OSD template - 9.5 SP1

$
0
0

Hi,

 

Was hoping someone could confirm they can see Windows 2012 Server options listed under the Target OS dropdown list uder OSD when creating new templates in LANDesk 9.5 SP1?

I can see Windows 8 and Windows 8 x64, but no Windows 2012 Server options.  is this an oversight?

 

Regards,

Richard.

Questions on Sysprep during Windows 7 deployment

$
0
0

Continued from http://community.landesk.com/support/docs/DOC-7444

 

Silvercoup,

thanks for explaining why you use sysprep /audit /shutdown. I have been frustrated by the Landesk doc which is written for Windows XP. Then trying to find something here that is up to date and works. From all my research I was totally confused as to why the above doc says to use sysprep /audit but you have cleared that up for me.

 

I have a question you said something about not changing the administrator account. Will it hurt to give the administrator a unique password before capturing or does that mess things up?

You also said to let landesk make the unattend.xml file on deployment. Does that mess things up if I use my own? Or should I tweak the landesk one?

Do you know (as I've read somewhere) if deleteing out the whole computername line will cause it to prompt you for a computername?

Our computernames are unique and can't be named using variables in the unattend.xml computername section

 

I'm also interested in your vbs script to inject .exe drivers.

HII preview works but not when running HII in regular mode

$
0
0

After updating to 9.5 sp1, HII doesn't seem to be working properly. When trying to image an optiplex 780 with HII it doesn't find any drivers for it. I loaded the HIIClient.exe onto a base 780 machine to run preview on it and as you can see in the log files it finds the drivers just fine but when trying to run it with out /preview it says it can't find any drivers.

 

Commands used were: HIIClient.exe /uncpath \\(path here) /preview /os win7 /arch x86

                                  HIIClient.exe /uncpath \\(path here) /os win7 /arch x86

 

Now I'm not sure if it was sp1 that caused HII to stop working or not because pre sp1 I never tried to image any 780s but our lenovo all in ones worked fine and now post sp1 I don't have any lenovos right now to see if they still work, all I know is the 780s aren't working.

 

Any ideas?

 

Thanks!

Provisioning tasks don't auto boot

$
0
0

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

Viewing all 1803 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>