Hello,
in our organization we do not have access to group policy so this is an out for us.
What method is best to choose to push websites to the trusted site list for Internet Explorer.
So far I have been unsuccessful and have tried adding a registry key to do this:
The distribution runs successful, but it does not show up in the Trusted Site list or even in the registry. I have tried "64bit" and "Not Applicable" under "Architect Options"
This is my first time posting but I have been trying to get a package built to use an unpacked iso to do an upgrade. I was following the instructions from this posting (Windows 7 to Windows 10 1703 Inplace Upgrade ) but my packages hang on installing or when I tweak the command prompts I also see a Client has started processing task and nothing ever happens.
Under Install/Uninstall options I have /auto upgrade /quiet . Has anyone else had success in doing in place upgrades?
Thanks,
Doug
We currently have 11 Preferred Servers which each also acts as the Replicator. With this being the case we have a patches folder (D:) and also the sdmcache folder (C:) becomes populated.
Last week we became concerned that the sdmcache folders were taking up a large amount of disk space. Therefore we decided to "limit the number of days file are kept in the cache" to 14 days from within Run options of the Preferred server options. Replicaton ran over night but the sdmcache folder was still the same size.
We contacted support who informed us that this was controlled via "Client Connectivity Settings".Configured a new Client Connectivity settings called Preferred Server Client Connectivity Settings with "number of days files stay in cache" set to 14. And pushed this successfully to two preferred servers as a test.
Content replication then ran overnight.
Next day checked Content Replication task history to make sure this had been successful, which it had. Checked the sdmcache folder and this was still the same size.
We decided to run "Start content replication now" against both preferred servers to look at a log file but after 10 minutes the Status of requested actions "Lost contact" on both. Decision was then made to revert both servers back to the original Client Connectivity settings they previously had.
Problem now is that the task created for this constantly sits at an ACTIVE state and never changes. Checking the inventory of these two Preferred Servers shows that they are still using the new settings created above.
We have checked the other 9 preferred servers who have the original settings and these are all able to replicate with no issues.
Also strangely enough the scheduled replication seems to have been succesful over night!? BUT still the sdmcache folder is the same size. We have checked all ports are open and they are. We have also checked client access and all approved.
Could anyone help with this rather time consuming issue!?
Thanks
Neil
Hello,
i would like to make an update of bios on DELL Computer.
I've got the bios exe files but when i create the schedule task installation didn't works
I ve create a batch file with this command:
start "Latitude_5X80_Precision_3520_1.9.3.exe" /s /p=password
But it doesn't works,
Please could you help me
Thanks
This article discusses an issue where the client cache location is not updated on a Client/Preferred Server after a change.
After updating the Client Cache Location (via Client Connectivity Settings) files downloaded to a Device or Preferred Server still revert to SDMcache.
After updating the Client Cache Location within Client Connectivity Settings (seen below), the downloadmulticastconf.xml file on the Client is not updated properly.
Verification can be done by opening the downloadermulticastconf XML file (located at \ProgramData\LANDesk\TMCdownload on the client), and seeing one of two things:
1. The XML file shows the following line:
Original
<CacheDirectory>C:\ProgramData\LANDesk\ManagementSuite\sdmcache</CacheDirectory>
This line shows that the sdmcache is still the primary Client Cache location.
2. The XML file will be completely blank upon opening.
Delete the existing XML file from the \TMCDownload\ directory.
From the client device open a run prompt and enter the following:
Once the update has completed, verify the <CacheDirectory> line within the downloadmulticastconf.xml file (this will be re-written with the changesettings task) to verify the updated location of your Client Cache.
Hi there
I would like to use Patch & Compliance to push out up to date versions of applications.
However, the issue I am seeing is that if, say, my device has Software X v10.1 then the security scans detects this as a vulnerability and suggests it needs v10.2.
But I am wanting to install 10.4
If I try to deploy v10.4 using Patch & Compliance it completes but doesn't install as it Ivanti doesn't see it as a vulnerability.
Is there a way I can deploy the latest version using Patch & Compliance without, as it seems is the case, having to deploy the versions in between first?
Cheers
Phil
With the release of Endpoint Manager 2018.1 there are some new features to help improve your Software Distribution deployments. Please review the attached document to see the new features for Software Distribution in EPM 2018.1.
| Software Distribution for Ivanti Endpoint Manager and Endpoint Security |
|---|
This is a list of highly recommended documents for increasing overall knowledge of this component. The articles listed below are applicable to Ivanti Management Suite 2018, 2017, 2016 and 9.6
If you want to review additional content regarding this component, please see the Documents or Discussions buttons on the overview page. |
Notice: Any E-Learning content is available by default to Members who have a minimum support agreement at the Professional level.
This article is not a comprehensive list of documents and issues. You can continue to search the rest of the community or the portion specific to Software Distributionif this page hasn't help
Hello Everyone,
I'm currently working on a strategy on updating Google Chrome in our enterprise. We currently have around 6000 devices and Chrome and IE are the 2 browsers we support for our enterprise applications. With that said, we turn off Auto Updates to Chrome so we can test it before rolling it out to all of our devices. These updates are turned off through a couple of commands that disable the google update services.
sc config "gupdatem" start= disabled
sc config "gupdate" start= disabled
The Chrome update process is as followed:
1. Chrome Installation starts
2. If a user is in Chrome, a new_chrome.exe is created and when the browser is closed the google update service will make the proper renames of the executable(s).
3. Since we have Google Update services turned off, that rename never takes place, which leaves them using an older version of the application until the next update.
We reached out to Google and they gave us a solution:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Issue - The setup.exe tries to replace chrome.exe during install, instead of aborting with an error code if the exe is already in use, it uses its own logic to dump a 'new_chrome.exe' beside the in use chrome.exe. When the user drops the instances of chrome.exe and re-opens, the logic between chrome.exe and googleupdate.exe see this new_chrome.exe and attempt to overwrite the chrome.exe with new_chrome.exe. Using the credentials of the non-administrator who just fired it, causing the UAC prompt.
Solution/workaround -
Using command script
1. Install the MSI
2. Delete any old_chrome.exe if it exists.
3. If new_chrome.exe exists, rename chrome.exe to old_chrome.exe (yes, you can rename an in use exe file)
4. Rename new_chrome.exe to chrome.exe
5. Using movefile.exe from pstoolkit, schedule a rename of new_chrome.exe to chrome.exe and a deletion of old_chrome.exe
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The problem with Google's solution is that, after renaming the chrome.exe to old_chrome.exe, users are unable to go to another website. Links from within the website work, but you're not able to type another website in the browser until you close and re-open.
I was hoping on suggestions or possibly other solutions on what other businesses are doing to update their Chrome. We can't be the only company that's has the auto updating turned off.
Any thoughts or suggestions would be greatly appreciated.
Thanks,
Jamie
If i have a application published to Portal Manager with setting:
Task Settings:
Frequency: Run Once
Checked: Optional (display in portal) and "allow users to run as desired (keep in portal after selected)
Problem 1:
First time i run the schedule task the software is availible in Portal Manager for my users.
What i have noticed is when a computer is re-installed with new OS the software will not be availible again in Portal Manager for the computer because it have already been succesfully publish to Portal Manager before.
Very annoying... any setting to fix this problem?
Problem 2:
First time i run the schedule task the software is availible in Portal Manager for my users.
If i choose "re-run task" on a computer that alrady successfully published a software to portal manager, it WILL INSTALL the software?! Even if i have the task setting: Optional (display in portal)
Or if i choose Task settings frequency to Run Daily, the first time it will publish to portal manager, the next day it will INSTALL the software...
This must be a bug?
Regards Johan
This document outlines how to successfully create and test a .msi and .exe software distribution package. For the purpose of this document we will be discussing a silent install method.
This is where you will select the exe/msi and give a description for the package.
This is where you will put the required switches for a silent install.
For msi packages the switches for a silent install are standard and if there are no special requirements for the package you can typically leave the Install/Uninstall options at the default. You can also find out the default msi switches using command prompt by navigating to the location of the msi and calling it with a /?. Example below
For exe packages the switches vary from vendor to vendor and typically a Google search will reveal the correct switches for a silent install. You can also try to call the exe with the /? switch, however in my experience a lot do not show the switches and just go to the install. In those cases using Google or contacting the vendor may be required. Example of an exe that gives switches below.
Some installations require more than just the main exe/msi to complete successfully. This section is where you can add those additional required files. Deployments like Office use the functionality of additional files.
This is where you can change the account that installs the package. By default all packages are created to be run by the system account and in most cases this is the best practice. However there are some applications that require being installed by the user profile that will be using the software. I do not have any known examples but I have seen applications that have to be installed on the user profile versus the computer itself.
Important: If you cannot manually install the software using the switches you have configured, then the Ivanti EPM install will also fail. It is vital that you fully test your software configuration manually before building the package in Ivanti EPM.
The most common issue is that the correct switches for a silent install were not used in the package creation. You can test this by calling the exe/msi manually with the switches you have in the package and see if it installs without prompting for any user interaction. Example below.
If there are any prompts visible you will need to continue working with the switches to get a completely silent install.
Once you have the correct switches and information in place it is now time to test. I recommend testing on a handful of machines you have access to in order to troubleshoot if needed. Pushing it out to a limited amount of machines you have full access to will avoid any widespread issues with the package.
If the install fails please see the following documentation.
Preferred Servers can be enabled in the Ivanti EPM Console. It now includes the ability to authenticate to a UNC share or a web share using the credentials configured for the preferred package server. That way, when the share is accessed by an Agent workstation's Local System account, it will be able to access the share using the credentials specified instead of simply trying to authenticate as Local System.
For example, if the packages on the core server can be found here:
CoreServer\packages\
Then on the package server called PackageServer, they should be found here:
PackageServer\packages\
Note: The maximum number of allowed characters for a UNC path is 260 characters. If the characters are include double-byte characters this limit will be less (2 bytes for each double-byte character instead of one).
For web it is similar:
For how to set up a web share
Installation |
|---|
System Requirement: Ivanti InstallEase requires: • Windows Vista or Server 2008 or above • Microsoft .NET 3.5 with Service Pack 1 • The appropriate service packs: - Windows Vista: Windows Vista: SP2, “Security update for Windows Graphics Component” (see Microsoft KB31457396), and “Update for C Universal Runtime” (see Microsoft KB2999226) - Windows 7: SP1 - Windows 8 and 8.1: “Update for C Universal Runtime” (see Microsoft KB2999226) - Windows 10: no service pack required - Windows Server 2008: SP2 - Windows Server 2008 R2: SP1 - Windows Server 2012: “Update for C Universal Runtime” - Windows Server 2016: no service pack required
Installing Ivanti InstallEase: To install Ivanti InstallEase, copy the application folder to a suitable location on your computer and start "IvantiInstallEase.exe"
By default InstallEase is located in the following directory on the core server:
|
Settings |
|---|
The settings let you set some basic options for the application’s operation. The factory defaults are appropriate to most circumstances, so there will often be no need to set the settings before using Ivanti InstallEase.
Temporary directory InstallEase stores temporary data for creating and comparing snapshots. This option lets you specify a convenient location for that folder.
File and registry search filters A large number of files on a computer hard disk are changed all the time by the operating system or by automated background processes unrelated to the installed software and should not be included in any snapshots. You can specify in these lists the files – e.g., log files, temporary files, or indexing files – and registry entries that are to be excluded from snapshots. This is just the default list; you can customize it for individual snapshots, as described below. To add a new file or registry entry, click the appropriate + button. You can specify files and folders by their names or their paths and registry entries by their keys or values; regular expressions are supported. To remove an existing file or registry entry, click the appropriate – button. You can also temporarily deactivate a filter by unchecking it. Clicking a Default Filters button resets the corresponding list to the factory defaults. |
Automatic Operation | ||||||||
|---|---|---|---|---|---|---|---|---|
| NOTE: This procedure describes using Ivanti InstallEase to create an installer package from two snapshots taken before and after an installation. For information on creating an installer package from scratch | ||||||||
Before you begin the process of creating an installer using snapshots, you may want to disable any software on the computer that autonomously writes to the disk, such as mail clients set to download mails in regular intervals or applications with auto-save functions. To use Ivanti InstallEase to create an installer package: 1. Start Ivanti InstallEase. 2. In the About Ivanti InstallEase screen, click Next.
3. Choose the Automatically method. 4. Specify the installation type and installer type. For the installation type, decide whether the software is to be installed for only the currently active user on each client computer or for all users of the computer. For the installer type, choose between a 32-bit and 64-bit installer. This should normally match the type of installer you use in step 9 to install the software for taking the snapshot. The installer type choice is not available when you are running InstallEase on a 32-bit system; in that case, you can only generate 32-bit installers. 5. Click Next. 6. Specify the volume or special directory of which InstallEase is to take the snapshots, or use the Directories list to specify a range of folders of which to take a snapshot. Certain types of files are automatically excluded from any snapshots, mostly known temporary, system maintenance, or log files. To review and edit this list, click Adjust File Filter. You can exclude files by their names or paths; regular expressions are supported. The default file filters are set in the Settings dialog. If you just want to capture registry changes, you can skip the file snapshot by choosing Don’t capture file changes. 7. Specify whether you want to capture changes in the entire registry by choosing Entire registry or just in specific parts by choosing Registry keys and specifying the desired key. Certain registry entries are automatically excluded from any snapshots. To review and edit this exclusion list, click Adjust Registry Filter. You can exclude entries by their keys or their values; regular expressions are supported. The default registry filters are set in the Settings dialog. If you just want to capture file changes, you can skip the registry snapshot by choosing Don’t capture registry changes.
8. Click Take Snapshot. Ivanti InstallEase records the current state of the specified volume or folders and registry keys. 9. As soon as possible – i.e., without first performing any other tasks on your computer – install the software from which you want to create an installer package. Take the installation as far as needed for your purpose. For example, if you want the installer package to include custom preferences for the software, launch the software and set its preferences as desired. After having configured the software, quit it again. If the installed software includes services or other software that runs automatically, stop it. Otherwise, Ivanti InstallEase may be unable to access the newly installed files to pack them into the installer. Note: If a restart is required as part of the software’s installation process, simply reopen Ivanti InstallEase when you have completed the installation. It will automatically resume from where it left off. 10. Click Take Snapshot to take the second snapshot. If at all possible, do not perform any tasks on the computer until the second snapshot is complete. When the second snapshot is complete, InstallEase compares both and creates a list of changes, displaying a progress dialog as it does so. When the list of file changes is complete, Ivanti InstallEase displays it in the Snapshot Data: Files screen. Objects that are to be removed during the installation are indicated by a superimposed red sign: .
Note: Ivanti InstallEase cannot include files larger than 2 GB in snapshots. If such files are found to have changed, you are informed of the issue.
11. Review the list and make changes as needed using the context menu. (When the context menu is used, items are added to the currently selected folder.) You can: - Specify additional items to be installed. Choose: ■ Add File to add a file from your computer. ■ Add Predefined Folder to add a special folder. ■ Add Drive to add an entire volume. ■ Add Folder/File with Hierarchy to add a file or folder and all folders that enclose it. ■ Add Folder to add an existing folder and its contents. ■ Add Empty Folder to create a new empty folder. Delete items by selecting them and pressing the Delete key. - Specify items that are to be removed from the target computers during installation: ■ Specify File to be Removed (by Name) lets you specify a file by name that is to be removed from target computers when found at the current location. ■ Specify Folder to be Removed (by Name) lets you specify a folder by name that is to be removed from target computers when found at the current location. By selecting an item and choosing Properties from the context menu, you can see its location as well as the sizes and modification dates of files. You can also set additional options for that item: ■ Read-only: The file is marked as read-only on the target system. ■ Hidden: The item is marked as hidden on the target system. ■ System: The file is marked as system file on the target system. (This option does not apply to folders.) ■ On uninstall, delete this directory even when it is not empty: This option applies only to uninstallers. It causes the directory to be deleted during the uninstallation even if it contains files or subdirectories. (This option does not apply to files.) ■ Action: What to do with the item on the target system. “New” adds the item, creating enclosing folders if necessary. “Remove” deletes the item. “Change” replaces an existing item with the same name in the same location. If there is no such item, the item is installed. When you are done, click Next. 12. In the Snapshot Data: Registry screen, you have similar options as on the last screen to tweak the registry part of your installation: - Show Predefined Key displays the contents of one of a number of frequently used registry keys. - Add Key lets you add a registry key from your computer. - Specify Key to be Removed by Name lets you name a registry key that is to be removed from the target system. - Delete deletes the selected item. - Properties: For individual keys, you can see basic information and edit the name and value. For folder keys, you can specify that it is removed during uninstallation, even when it is not empty. - The Action option lets you specify what to do with the key on the target system. “New” adds the key, creating enclosing keys if necessary. “Remove” deletes the key. “Change” replaces an existing key with the same name in the same location. If there is no such key, the key is installed. - The New context menu lets you add a registry key of a desired type to the list of keys. Note: You cannot create values at the top level of registry hives (i.e., in the roots of HKEY_CURRENT_USER, HKEY_CLASSES_ROOT, HKEY_LOCAL_MACHINE, HKEY_USERS, or HKEY_CURRENT_CONFIG). - Specify Value to be Removed by Name lets you name a registry value that is to be removed from the target system.
When you are done, click Next.
13. Specify the metadata for the installer package: - MSI file: The name and full path of the MSI installer file you want to create - Product name: The name of the product that is being installed - Description: A description of the installed software for the user - Version: The version of the software that is being installed - Manufacturer: The company providing the installer - Product code, Upgrade code: Unique codes for the installer options. You can click Generate to generate a new code. - Register product: Check this option to leave an entry for the installed software in the Add or Remove Programs control panel, allowing deinstallation by the user. Unchecked the option to not create such an entry.
Click Create when you are done. |
Manually Creating a Package |
|---|
Manually creating a package works mostly the same as using snapshots (described above), with the following differences: • Instead of choosing Automatically in step 3, choose Manually. • This takes you directly to step 11 when you click Continue, where you can manually specify all objects to be installed or removed.
In all other respects, the process is the same in both cases. |
During Inventory scan or Software Distribution task LDAPWhoami.exe triggers smartcard reader dialog box (on the devices with smartcard reader installed).
Example 1:
Example 2:
Changes implemented in the product in version EPM 2017.3 within ldapinfo.dll code (used by ldapwhoami.exe). Ldapinfo.dll is part of the agent package so the issue is client-oriented.
Replace ldapinfo.dll with the file from a previous version of EPM (attached to this document) on affected devices. If you encounter this issue in your environment, please raise a case with Ivanti.
The engineering team is currently working on fixing this issue (DSI 232949). If you have any additional questions, please contact Ivanti Support.
I have had a couple clients whose portal is broken. It doesn't have the launchpad and a reboot doesn't help.
Anything I can try to get it back other than uninstalling and reinstalling the agent?
Running Ivanti 2017.3 SU3.
hi everyone,
i'm unable do install a software using a provisionning task, in my SCDCLIENTHANDLER.log i get stuck to :
Sdclienthandler.exe checking for sdclient Mutex,
and still repeating this action.
for the same package, i can install it using a schedule task.
is any body can't tell me what's wrong ?
Deploying adobe reader 11.10 multiple agents reporting Return Code 1110 Cannot Find Agent. Yet several agents are online and pingable. I can also force an inventory scan but not deploy anything.
Hey Folks,
Been having an issue with false positives when deploying the OffScrub10.VBS script to workstations. Within Endpoint Manager the task succeeds, however Office 2010 is not actually removed from the workstation. when you examine the logs generated by the VB script you get the following message at the end of the log.
Successfully rolled back the uninstall of package: Office64WW path:C:\MSOCache\All Users\{90140000-0011-0000-0000-0000000FF1CE}-C\Office64WW.MSI
SystemRestore : Attempting to cancelling System-Restore-Point for Product [Microsoft Office Professional Plus 2010] (with RestorePointType [1, Removed]).
SystemRestore : Successfully cancelled System-Restore-Point for Product [Microsoft Office Professional Plus 2010] (with RestorePointType [1, Removed]).
Not showing completion dialog because it was not requested.
Reboot requested never. Skipping reboot attempt.
Catalyst execution finished: 03/26/2018 21:21:08. Return code: 1913.
PERF: TickCount=266371 Name=RunSetup Description=End function
i have added the 1913 return code to the Default non MSI template to return a failure, but i am still encountering a scenario where the task succeeds according to Endpoint Manager but does not "actually" succeed.
Has anyone had any experience with this particular issue? Also how have you been tackling office 2010 uninstalls during the migration to O365?
Hello,
in our organization we do not have access to group policy so this is an out for us.
What method is best to choose to push websites to the trusted site list for Internet Explorer.
So far I have been unsuccessful and have tried adding a registry key to do this:
The distribution runs successful, but it does not show up in the Trusted Site list or even in the registry. I have tried "64bit" and "Not Applicable" under "Architect Options"
I have an executable that i created that allows an end user to enable network connections that have been disabled. (Our users are not admins)
I thought i could precache the executable for a day it is needed and then allow them to run a task from the portal so they can run it as system.
It seems though that the portal manager doesn't look at the sdmcache and still tries to download the files so the job always fails.
Running EPM 2017.1
