Quantcast
Channel: Ivanti User Community: Message List - Software Distribution
Viewing all 1834 articles
Browse latest View live

Re: code 17006

$
0
0

Setting   <Property Name="FORCEAPPSHUTDOWN" Value="TRUE" /> in the XML config file the installer uses instead of FALSE seemed to fix the same error code for me. Were the devices in use with a user at the time?


Re: Software distributions fail for upgraded 2017 clients

$
0
0

Hi WimVH,

 

That error has been tied to certificate issues & the details you've provided also hint to this.

 

Perform the following steps on the computers experiencing this issue:

 

Check the client connectivity setting being used for the agent to confirm only the cert you want is selected.

Remove old certs from C:\Program Files (x86)\LANDesk\Shared Files\cbaroot\certs on affected device

Run "C:\Program Files (x86)\LANDesk\LDClient\brokerconfig.exe" -r on affected device

Run "C:\Program Files (x86)\LANDesk\LDClient\vulscan.exe" /reset on affected device

 

 

Reference the following document regarding how to clean up certs in detail:

 

https://community.ivanti.com/docs/DOC-61933

 

Feel free to mark this answer as correct if it helped!

How to publish provisioning template to Portal?

$
0
0

I have seen references in some places about being able to publish provisioning templates in the portal.  But no matter what I do, I am unable to get it to show up in my portal.

 

About the Portal Manager

Adding items to Portal Manager

The default Portal Manager deployment doesn't include any launchpad items. Use software distribution to add items to Portal Manager.

Items you can add to Portal Manager include:

  • Mobile Android and Apple iOS packages
  • Universal links, streamed documents, and OS provisioning templates

 

This is what I ended up doing, though it did not work.

 

I created the os provisioning template and added actions.  In Distribution Packages I made a new universal package | Provisioning.  I included the template I had created before.  I created scheduled task, went into the task, associated it to my workstation, set it to policy push, kicked it off.  It shows as active in the progress window but nothing ever shows up in the Portal, even after I refresh it.  I can add and remove typical distribution packages and it is reflected in the Portal window, so I know I can get some things to work.

 

I looked around and have yet to find documentation showing how to do this.  Anyone know where such documentation would be?

Re: Powershell Software Distribution always return code 0

$
0
0

I know this is old, but your solution "[Environment]::Exit(<CODE>)" worked for me.  I think this should be listed as the correct answer.

Re: Software distributions fail for upgraded 2017 clients

$
0
0

Hi Gregory,

 

 

The article you referenced is spot on.

 

After a side by side upgrade, the older certificates were no longer available on the Core Server, while the .0 files were still in the LDLOGON share.

Deleting the olsolete .0 files from \\CoreServer\LDLOGON and running the managed script fixed the client issues easily.

 

Good to know that manage scripts can be run even in this situation. This is an amazing feature.

 

 

Thank you

Wim

Re: How to publish provisioning template to Portal?

$
0
0

Did you set it to "Policy-supported push" or "Policy" on the task settings?  It needs to be set to "Policy".  Did you set it to either "Recommended (display in portal)" or "Optional (display in portal)" on the portal settings?

 

The steps you went through were correct and I just successfully added a template to Portal Manager in the same manner.  I'd double check the settings.

Re: How to publish provisioning template to Portal?

$
0
0

They were set to Policy-supported Push.  I stopped the tasks, changed them to Policy, restarted the tasks, and refreshed the portal on one of the target workstations, but they aren't showing up.

 

I'll give them some more time and see what happens.  I may just start over from scratch, too, in case I screwed up something else along the way.  Thank you!

Will Software Distribution Download continue after the device is restart?

$
0
0

Hi,

 

I have a scenario here on the software distribution:

 

If I'm required to push a 3GB software to a client device. While pushing the 3GB software to client and the status is "downloading 50%", then the client turn off the their device. 

 

Question:

1. When the client turn back on their device, will the download continue at 50% or it will start the download again?

2. If the download will continue at 50%, do I required to configure any specific setting?


Re: Will Software Distribution Download continue after the device is restart?

$
0
0

Hi, yes this should be happening automatically using checkpoint and restart.

 

If you start this and watch in the client's sdmcache folder you will see the folder structure get created and with the folder that matches the source you should start to see a 'partial' file get created and it will gradually grow. If the process restarts it should restart from the same point.

 

Mark McGinn

MarXtar Ltd/MarXtar Corporation

http://ivantione.marxtar.com

Ivanti One Development Partner

 

Try MarXtar Enterprise Notifer for Ivanti to Better Communicate with Your Service Subscribers

Try MarXtar State Management for Ivanti to Better Understand and Manage your Assets

How can I run a powershell as administrator over the software distribution

$
0
0

Hello together,

 

I want to update a registry entry over the software distribution, but it doesn't work with the actions task because the entry needs to be updated as administrator.

I tried to run the task under the LocalSystem account and also unter a local administrator account with a specified user. Both of them didn't work and didn't update the registry.

 

I copied the preview of the PowerShell-script(from the actions-package) and ran it manually on a computer with a powershell started as administrator.

The registry entry was now updated.

 

How can I run a powershell as administrator over the software distribution?

 

Thanks in advance

Dominik

PowerCLI (vsphere) script as a scheduled task

$
0
0

EPM 2017.3

i need to restore a snapshot before sending an install task on some clients, the vms are running in vmware, I was able to complete an script using powershell (in conjunction with powercli) to restore the snapshot, the thing is that to run the script, the machine that runs it has to have certaing prerequisites installed, powercli and some variables.

So as far as I can see it now (I don't really know) I need to:

1. Run the script from a machine with this configuration (I would need to have a machine in stand by just to run the powershell/powercli commands)

2. Run my normal Software distribution task after the restore is completed.

 

Is there another way to do this?

I found this: Creating and deleting snapshots the reference doc is for hyper-v for which Normal powershell would work (installed on the core) but no the additional powercli requirements.

Can I install powerCLI in my core?

 

Any reference is appreciated.

Best.

Re: PowerCLI (vsphere) script as a scheduled task

$
0
0

You should be "fine" with installing PowerCLI on the Core.

 

Why on earth VMWare can't / won't "just" do normal web-services is beyond me, but ah well. That's a VMWare decision (which I question) - but you're right ... if you want to talk to VMWare you need one of the VMWare interfacing tools installed (annoyingly).

 

I *would* suggest you install PowerCLI on a test Core first (just to make sure that they don't blow up anything obvious), but I can't think of anything it should fool around with (since usually the "more sensitive" components tend to be either IIS-related and/or .NET related).

 

I wouldn't expect any problems, but if you don't make sure, "something will go wrong" - because sod's law.

 

Alternatively, install PowerCLI on a "dedicated box" (say - one of your VM-s) and store your script(s) there, and just schedule the scripts to be launched from that box. You can access data from the Core if you need with your account via a dynamic query (for example) in Getting Started with the MBSDK (Example Scripts Included) .

Re: PowerCLI (vsphere) script as a scheduled task

$
0
0

I have an old core, I'll try the PowerCLI there and see if it works...

I'm a little hesitant on installing anything on the core so I may have to test this carefully before passing it to production.

I didn't wanted to have an extra box just for this, but may be safer.... thinking... thinking

I'll have to get back to you on this.

Thx!

Re: PowerCLI (vsphere) script as a scheduled task

$
0
0

That paranoia / reluctance  to install "stuff" on the Core is a healthy thing! Don't knock it.

 

<It's why I suggested nabbing some alternate device, so as to avoid fooling around with the Core and potentially causing headaches. >

autofix patches for specific scope

$
0
0

Hello,

 

I have created a scope called "OS reinstall" and I setup certain updates to be autofixed for all devices in this scope (global patch settings - do not autofix). This scope selects systems based on device group called "OS reinstall". Another words - I move my systems manually to group "OS reinstall" and I expect these systems to autofix all patches for "OS reinstall" scope. Problem is that for some reason after I move system to group this system is still not able to apply patches - it acts like these patches do not have "Autofix" enabled. Do I need to do something like "wake up agent" or "update agent settings" so agent knows it is inside "OS reinstall" scope?


Re: autofix patches for specific scope

$
0
0

Clients are not aware (at all) what scope they are part or not part of.

 

The Core handles that bit in all regards.

 

After dragging clients into a scope, you may want to re-resolve the scope (this happens normally 1x per hour roughly otherwise), so that everything is resolved properly.

 

As far as the clients are concerned -- all they "need" to do is run vulscan.

 

Essentially the entire rest is down to the Core (i.e. "Say, I notice you're vulnerable to X, Y and Z ... and since you're in scope ABC, you best patch those things right now via Autofix, buddy!").

 

The clients (more or less) essentially just do stuff like "Hey boss - here's what I'm vulnerable to. Do I need to do anything?" ... they're pretty unaware in other respects.

 

Does that make sense?

Re: autofix patches for specific scope

$
0
0

About Auto fix, if we create a repair task, we can see is the repair passed or failed and troubleshoot from there.

Is there a way to know what happens when Auto fix "is not doing anything" ? I have the same situation as  rspychaj that even when I have set certain vulnerabilities to Autofix for a specific scope, nothing happens.

 

-CS

Re: autofix patches for specific scope

$
0
0

Autofix "only" tries to repair a few times, before giving up for a certain device (if the repair fails continuously).

 

You can see / configure that option here:

 

And then THESE options:

 

... that may be responsible for "it not doing anything" potentially?

 

(The idea being that we don't try to install things "ad infinitum" as if a patch fails to install, there's usually a good reason for it -- or something on the box is borked).

Re: autofix patches for specific scope

$
0
0

Correct, and is there a way to see when/why it failed?

Re: autofix patches for specific scope

$
0
0

Would be usually on the affected client-side vulscan log(s) -- at least for the "attempting to install // reason why it failed as reported by Windows" stuff.

 

If it failed (say) 10 vulscan ago, you're a bit out of luck since those logs would've been overwritten through log-iteration (default is 7).

 

The Core MIGHT have some traces from a "uh uh - you tried & failed before, so not trying again" type call in the WSVULNERABILITY log potentially, but that's more of a suspicion (my labs don't tend to survive through any failed patch installs  for overly long due to frequent reverting to snapshots, so I don't exactly have anything I can go and verify / check up on, sorry) .

Viewing all 1834 articles
Browse latest View live


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