Quantcast
Channel: Ivanti User Community: Message List - OS Deployment and Provisioning
Viewing all 3345 articles
Browse latest View live

Re: Template is not being picked up - runs through the 40 tries

$
0
0

dgonzalez, your comment was pointing in the right direction.

 

I had the provisionin tasks created under my personal account. Even though I have admin rights, I have a limited scope. My scope includes PXE added devices, so I didn’t question that further.

 

Now we created a dedicated user with admin rights and no scope limitations and the templates are being picked up as expected.

 

I already had opened a support case a year ago, and the problem couldn’t get solved. I raised a new case recently, this time the support engineer saw the issue during our first web meeting.

 

Very annoying bug that caused a lot of frustration for a long time. 


Re: LANDesk 2016 provisioning failed to map network drive

$
0
0

We still have the issue occasionally with 2017.3 SU2 so the problem still lingers

Re: Template is not being picked up - runs through the 40 tries

$
0
0

Hi Mike,

 

It looks like we are having the same issue, If I start the template with my credentials (has no scope limitations) and it works.

For a standard Landesk Operator with a scope limit, he cant provision and it goes to 40/40 template fail.

 

Did you get a reply from Landesk Support? a Fix perhaps!.

 

Thanks

Re: Template Action to determine OS and apply software for that OS

$
0
0

Im not sure if this will help, but we use the same software template for both Windows 10 & 7. We use the following:

The software installs would happen after the Agent assuming the Agent has done a scan before the software installs start occurring, the values should be in inventory?

Re: Template Action to determine OS and apply software for that OS

$
0
0

Thanks for the info.

I tried it and in one case it worked and another it failed. This is a little flaky because it depends on the agent doing a inventory scan and it going directly into the database on a new computer.

In the case of the one that failed something must have delayed the inventory scan being put into the database as both  the successful provisioning job and the failed one were both in the same sequence in the template.

How do you use dism.exe in the Deploy Image action?

$
0
0

I would like to use dism.exe to restore images using OS provisioning since ImageX has been deprecated since Windows 8 but I have not found instructions for how to do it.

 

This is what I have tried so far, with varying results.

  1. Use an "Execute file" action to launch dism.exe and specify the appropriate parameters.  E.g. /Apply-Image /ImageFile:"\\<servername>\<path_to_Image>\win10x641709base.wim" /Index:1 /ApplyDir:C:\ .  This launches a new command prompt window and restores the image using dism.exe, however we do get visual feedback in neither the command prompt window nor the provisioning window until the task has completed.  The behavior is the same whether we capture output or not.
  2. I created a new "Deploy image" action, and chose "Other".  I specified the \\<servername>\<path_to_Image>\win10x641709base.wim for the image name.  The task currently downloads dism.exe files from the server and runs that, so I set imaging tool path to C:\Misc\Pre-OS_Installation\GetDISM\dism.exe .  For command line parameters I specified /Apply-Image /ImageFile:"\\<servername>\<path_to_Image>\win10x641709base.wim" /Index:1 /ApplyDir:C:\ .  It restores the image but it neither launches a command prompt window nor provides any output in the provisioning window while it is restoring the image.

 

So, I have two questions:

  1. How do you force provisioning template actions to display in real-time output rather than waiting until the action has completed?
  2. Is there a recommended way to use DISM as the method for restoring an image, and if so, is there a way to make it display in real-time the progress of the restore?

Update Base OS Deployment Image

$
0
0

Does anyone out there have a reliable way of integrating / updating a base windows OS image with MS updates for deployment?

 

Currently when we deploy our desktops and servers from LANDesk we have to sit for a couple of hours whilst it patches and updates.

 

I would love to be able to capture an updated image to use as a base deployment image but can't seem to find a reliable way to do this.

 

Just wondered if anyone else was doing anything that works.

Anyone know how to submit inventory from/during PE environment?

$
0
0

We're doing some comparisons with variables and db values during our provisioning processes and workflows, but obviously if it wasn't previously in IEM, it has no inventory records.  It also doesn't seem to check 'on the fly', so this is resulting in some issues with our provisioning processes and workflows.  I recall someone saying at Interchange last year that they were able to do a mini-inventory scan in PE and submit that to the core as part of their process while in PE, which then gave them the data for such use, but I don't see anything on this in the discussions/forums here.  Can anyone share how they've done this?

 

Thanks!

 

Jey Bailey

Technology Support Specialist

Bucknell University


Re: Anyone know how to submit inventory from/during PE environment?

Re: Anyone know how to submit inventory from/during PE environment?

Re: Anyone know how to submit inventory from/during PE environment?

$
0
0

Looks like that's been replaced with LDISCN32.EXE /MINI, but still not documented well on what switches/options are available for that.  The regular run of LDISCN32.exe may have worked, but I'm also in the 64-bit PE, which won't work with the 32-bit version of LDISCN32.exe since there's no WOW64 in PE...  This shouldn't be this hard.  Other ideas?

Re: Anyone know how to submit inventory from/during PE environment?

$
0
0

Thanks, yeah that's one of the pages I found on that, but there isn't a 64bit version of the inventory tool, and 64bit PE doesn't have WOW64 to run 32bit apps, at least not out of the box...  Hopefully Ivanti puts attention to making all of their processes 64bit native, or integrates WOW64 in their PE build process soon...

Re: LANDesk 2016 provisioning failed to map network drive

Re: Template is not being picked up - runs through the 40 tries

$
0
0

Did these instruction not help? How to enable a console user limited by scope to provision new devices that do not have a scope

 

Also I have you tried creating a query and creating a scope based on that query that has Computer.OS.Preboot OS or you can use Computer.Network.PXEBoot or if your scopes are based on network "Computer"."LANDesk Management"."Agent Configuration Name" NOT EXISTS AND "Computer"."Device ID" = "Unassigned" AND "Computer"."Inventory Server" = "Your Core server name" AND("Computer"."Network"."TCPIP"."Address" LIKE "Put in your Address Range" OR "Computer"."Network"."TCPIP"."Address" LIKE "Put in your Address Range")

Re: Unable to obtain a lock on drive C: popup message

$
0
0

I just had this issue.  you have to use the /fd switch.  don't validate it because it removes it.  example below

 

/r /o /x /d:0 /fd /rb:0 /f:\\CORE\ldlogon\Images\Win10.tbi


loading images from landesk core not from the preferred server

$
0
0

The PC is contacting the core server instead of the preferred server when loading images. Please help

Re: How do you use dism.exe in the Deploy Image action?

$
0
0

I don't think dism offers an easy way to provide a progress bar as ImageX can do. It may require a function to read the output file and show it then, but nothing easy. I might be wrong.

Maybe it won't suit your purpose, but why don't you try to use the "LANDESK ImageW V2" (From Teradata actually) we provide to capture & deploy the images? It will provide a full screen with the progress bar.

If you really need to use dism for whatever reasons and then show a progress bar, you will need to create an Enhancement Request on our platform, but it may be available in future versions, not in the short term.

Re: Unable to deploy image to Surface pro

$
0
0

Did you have a look of the maptopreferredhandler.log either?

Re: How do you use dism.exe in the Deploy Image action?

$
0
0

Thank you for the feedback.  I figured out a workaround that allows us to use DISM and shows a progress indicator, though it does not give real-time updates on estimated time remaining but it is better than no feedback at all.

 

First, we had to add the required DISM Powershell modules to the Ivanti OS provisioning boot images.  I had already installed the Windows 10 "Assessment and Deployment Kit" on my workstation.  I used UltraISO to extract the boot.wim and boot_x64.wim from the provisioning ISO's Boot directory into my C:\Misc\PE folder.  I created the mount point folders C:\Misc\PE\x86 and C:\Misc\PE\x64.  Then I ran the following commands to mount each .wim file, install the necessary Powershell modules, and then commit those changes.:

 

Dism /Mount-Image /ImageFile:"C:\misc\pe\boot_x86.wim" /Index:1 /MountDir:"C:\Misc\PE\x86"
Dism /Add-Package /Image:"C:\Misc\PE\x86" /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\WinPE-WMI.cab"
Dism /Add-Package /Image:"C:\Misc\PE\x86" /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\WinPE-NetFx.cab"
Dism /Add-Package /Image:"C:\Misc\PE\x86" /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\WinPE-Scripting.cab"
Dism /Add-Package /Image:"C:\Misc\PE\x86" /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\WinPE-PowerShell.cab"
Dism /Add-Package /Image:"C:\Misc\PE\x86" /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\WinPE-DismCmdlets.cab"
Dism /Unmount-Image /MountDir:"C:\Misc\PE\x86" /Commit

Dism /Mount-Image /ImageFile:"C:\misc\pe\boot_x64.wim" /Index:1 /MountDir:"C:\Misc\PE\x64"
Dism /Add-Package /Image:"C:\Misc\PE\x64" /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-WMI.cab"
Dism /Add-Package /Image:"C:\Misc\PE\x64" /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-NetFx.cab"
Dism /Add-Package /Image:"C:\Misc\PE\x64" /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-Scripting.cab"
Dism /Add-Package /Image:"C:\Misc\PE\x64" /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-PowerShell.cab"
Dism /Add-Package /Image:"C:\Misc\PE\x64" /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-DismCmdlets.cab"
Dism /Unmount-Image /MountDir:"C:\Misc\PE\x64" /Commit

 

Then I replaced the existing boot.wim and boot_x64.wim files in the os provisioning .ISO with the modified .wim files.

 

In my provisioning template's "OS Installation" section I created a "Map to Preferred Server"  action called "Map drive to preferred server".  I mapped P: to our Packages folder on our server.

 

Right below that action I created an "Execute File" action with the following settings:

  • Target path and filename: X:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
  • Command-line parameters: -executionpolicy bypass -nologo -noprofile -file "P:\Provisioning\OS_Installation\RestoreImage\win10x641709base.ps1"
  • Expected return value: = 0
  • Stop processing the template if action fails: True

 

I created a Powershell script called "P:\Provisioning\OS_Installation\RestoreImage\win10x641709base.ps1" with the following in it:

Import-Module dism

$StartTime = Get-Date
write-host "StartTime = $StartTime"
Expand-WindowsImage -ApplyPath C:\ -ImagePath "P:\images\win10x641709base.wim" -Index 1
$EndTime = Get-Date
write-host "EndTime = $EndTime"
$Duration = NEW-TIMESPAN –Start $StartTime –End $EndTime
write-host "Duration = $Duration"

 

This way we are now able to use DISM - Microsoft's recommended method for capturing and restoring Windows images - with a progress indicator in Ivanti's OS provisioning environment.

dism.png

Re: How do you use dism.exe in the Deploy Image action?

$
0
0

This looks great, thanks for the info.  Have you tried leveraging self-organizing multicast to deploy your image with this?  I'm thinking this would not work for that as you're hard coding a path to your WIM file.  The Multicast in WinPE will create a temp partition to download the WIM file that may be a different drive letter on each machine (depending on if it had a DVD/card reader, or maybe that's been fixed with 2017.3 SU2.).  Just curious.

Viewing all 3345 articles
Browse latest View live


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