We have several versions of Acrobat standard and pro installed, that I need to find a quick way to uninstall them.   I have not been able to find uninstall script from adobe that would do this, does anyone know of one or how I could use LANDesk to go about doing this?    The reason we have to remove is the versions we are using are very old and no longer supported, plus have several security issues.

Thanks

I would like to know any progress on the latest release of 10.3 for the Ivanti worksapce control?

Patch Collection DSM 2017 Download

These are the known issues of DSM 2017 which we have found internally and their regarding status and think are worth being published here.

History of this document:

Link to the Patch Collection for DSM 2017

Known Issues Status:

268358

Hi

We have just downloaded the LANDESK 9.50 on a server. It is still running in trial mode. Im trying to test Distribution packages.

Im distributing a msi package. The destination has the new agent and it appears to be working fine. When I run the task it fails on a return code 105.

Here  is an extract of what I see in the "view log file" option.

Processing package : Cisco VOIP Agent
Wed, 10 Apr 2013 10:14:23 File (\\-----\-----\------\-------\-------AgentDesktop.msi) is not in cache
Wed, 10 Apr 2013 10:14:23 Will attempt Peer Download.

Wed, 10 Apr 2013 10:14:23 Will attempt Preferred Server Download.

Wed, 10 Apr 2013 10:14:23 About to call DownloadFiles (1 files) with these settings:
Wed, 10 Apr 2013 10:14:23 m_allowedBandwidthWAN: 100
Wed, 10 Apr 2013 10:14:23 m_allowedBandwidthLAN: 100
Wed, 10 Apr 2013 10:14:23 m_maxDiscoveryThreads: 15
Wed, 10 Apr 2013 10:14:23 m_discardPeriodSeconds: 604800
Wed, 10 Apr 2013 10:14:23 m_preserveDirectoryStructure: 1
Wed, 10 Apr 2013 10:14:23 m_bUseWanBWForPush: 0
Wed, 10 Apr 2013 10:14:23 m_bSynchronize: 0
Wed, 10 Apr 2013 10:14:23 m_downloadControl: AttemptPeer
Wed, 10 Apr 2013 10:14:23 m_preferredServerControl: AttemptPreferredServer
Wed, 10 Apr 2013 10:14:45 processing of package is complete, result -1918107543 (0x8dac0069 - code 105)

Where should I be looking to resolve this and any ideas what my problem might be?

Regards

Mike

The boot.wim and boot_x64.wim that ship with LDMS include the Threshold I RTM version of WinPE.  There have been two newer releases of WinPE since this version.  The current most up to date version is RedStone I / 1607.  New versions of WinPE are released every 6 months from Microsoft.

Some hardware such as the Surface Studios require this newer version in order to be PXE booted and provisioned.

Here are the steps to take to upgrade your boot files to a newer version of WinPE:

Step 1:

Download and install the latest version of the Windows ADK (or the version you need) from the below link to get Microsoft's release of the WinPE files that match the specific OS version:

Windows ADK downloads - Windows Hardware Dev Center

Step 2:

Run the Deployment and Imaging Tools Environment as administrator:

Step 3:

Download and run the following script from with-in the Deployment and Imaging Tools Environment CMD box that will prepare your WinPE files from Microsoft with the required modules for LDMS:

Create-WinPE.bat (attached to this document)

Step 4:

Take your prepared boot.wim and boot_x64.wim files from c:\winpe_x86 and c:\winpe_amd64 and copy them to this folder on your core:

Letter:\Program Files\LANDesk\ManagementSuite\landesk\vboot\clean\

*Note - backup the original files that are there incase you need to revert to the version that Ivanti ships with LDMS.

Step 5:

Backup your old production boot files.  Create copies of the files located at Letter:\Program Files\LANDesk\ManagementSuite\landesk\vboot and put them some where safe (step 6 will overwrite them).  However you must keep a copy of your old boot files here still.  Do not simply move them to another location.  Step 6 will be looking for these old boot files in order to migrate the HII drivers over to the new boot files, so if you rename them or move them instead of just making a copy of them - that step will not work completely.

Step 6:

On your core server launch an elevated command prompt and run:

This will upgrade your existing LDMS boot.wim and boot_x64.wim to now be RedStone I / 1607.

These updated files will be located at:

Letter:\Program Files\LANDesk\ManagementSuite\landesk\vboot

Additional notes:

- Bitlocker support is added via the Create-WinPE.bat script.  (can use manage-bde.exe with-in WinPE)

- PowerShell usage without requiring full path is additionally added.

Hi all,

I have a number of servers that we use LANDesk to stage patches to but not install.  The installation is being done manually by someone from the server team.  However, if a large number of patches get pushed to the server, then it can be a challenge to install manually (time consuming and questionable about what goes on first, second, etc....).   I figured that I would just put a batch file on these servers that would then allow the server team to run and install using calls to vulscan.  However, this doesn't seem to be working for me.  Maybe I'm misunderstanding the capability of vulscan but here is what I have tried:

vulscan /repair vulnerability=all /allowusercancelrepair /rebootifneeded

and

vulscan /repair vulnerability=all /fix /allowusercancelrepair /rebootifneeded

When I run these commands, nothing happens.

Suggestions on what I'm doing wrong?

Thanks everyone.

What is the release date for 2017.3 for on-premise customers?

Hi,

Everytime when I installed the LDMS 9.0 agent (manually, push or via provisioning) on Windows 7 only there is a folder created in the root system (C:\) called %LOCALAPPDATA%. It's look like a variable wrong coded.

Some people can confirm that?? In that case I will open a call....

Regards

Lionel

The boot.wim and boot_x64.wim that ship with LDMS include the Threshold I RTM version of WinPE.  There have been two newer releases of WinPE since this version.  The current most up to date version is RedStone I / 1607.  New versions of WinPE are released every 6 months from Microsoft.

Some hardware such as the Surface Studios require this newer version in order to be PXE booted and provisioned.

Here are the steps to take to upgrade your boot files to a newer version of WinPE:

Step 1:

Download and install the latest version of the Windows ADK (or the version you need) from the below link to get Microsoft's release of the WinPE files that match the specific OS version:

Windows ADK downloads - Windows Hardware Dev Center

Step 2:

Run the Deployment and Imaging Tools Environment as administrator:

Step 3:

Download and run the following script from with-in the Deployment and Imaging Tools Environment CMD box that will prepare your WinPE files from Microsoft with the required modules for LDMS:

Create-WinPE.bat (attached to this document)

Step 4:

Take your prepared boot.wim and boot_x64.wim files from c:\winpe_x86 and c:\winpe_amd64 and copy them to this folder on your core:

Letter:\Program Files\LANDesk\ManagementSuite\landesk\vboot\clean\

*Note - backup the original files that are there incase you need to revert to the version that Ivanti ships with LDMS.

Step 5:

Backup your old production boot files.  Create copies of the files located at Letter:\Program Files\LANDesk\ManagementSuite\landesk\vboot and put them some where safe (step 6 will overwrite them).  However you must keep a copy of your old boot files here still.  Do not simply move them to another location.  Step 6 will be looking for these old boot files in order to migrate the HII drivers over to the new boot files, so if you rename them or move them instead of just making a copy of them - that step will not work completely.

Step 6:

On your core server launch an elevated command prompt and run:

This will upgrade your existing LDMS boot.wim and boot_x64.wim to now be RedStone I / 1607.

These updated files will be located at:

Letter:\Program Files\LANDesk\ManagementSuite\landesk\vboot

Additional notes:

- Bitlocker support is added via the Create-WinPE.bat script.  (can use manage-bde.exe with-in WinPE)

- PowerShell usage without requiring full path is additionally added.

We have a Windows 2016 with Office 2016 Office setup with environment manager 10.1 (FR1).  Our mail is in Office 365

when launching outlook 2016, we keep getting a prompt to enter username and password, although we have configured roaming of the credentials.  From what I can tell, credentials are stored in

Contorl Panel > Credential Manager.  There are two types:

MicrosoftOffice16_data: SSPI and MicrosoftOffice16_Data:ADAL

The first one has persistence set to Enterprise, which is correct.  Data:ADAL entries have persistence set to Logon session.

It seems after logging off, the ADAL credentials are discarded (which makes sense from the persistence description).

After logging back in, we get prompted for Outlook credentials, and the Data:ADAL credentials are added again to the credential manager.

I found ADAL is related to Office Modern authentication, which can be disabled, but we don't want to do this.

any idea's?

many thanks

Hi all,

I'm having some issues trying to deploy a batch file that will copy some powerpoint, excel, and word templates to their desktops. (We just had a rebranding)

On my test machines, the batch file runs fine for both Windows XP and Windows 7. I don't know what the problem is here as the batch files work fine without LANDesk, but when I go to distribute the task through LANDesk I get a "Package deployment failed" and a Return code 4.

Everyone has access to this share, I'm using a policy supported push, and I tried sifting through the log files with no real answer for why it isn't deploying.

I still haven't been able to find documentation on return code 4 as well.

Here's my scripting for both OS's:

Windows 7:

@ECHO ON
::Copies files to dekstop of current user *For Windows 7

xcopy "\\networkshare\tempstorage\Templates" "%systemdrive%\users\%username%\Desktop\Templates\" /O /X /E /H /K

Windows XP:

xcopy "\\networkshare\tempstorage\Templates" "%userprofile%\Desktop\Templates\" /O /X /E /H /K

Would appreciate any help in this matter!

Thanks.

We save the registry of our users during logon. We can see that the keys associated with recent files in office are indeed captured by Ivanti Appsense. (personalization Analysis --> edit users registry)

they are stored in the following key:

[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Excel\User MRU\ADAL_C8C3012C979E9D2A2CFF145E26C67C833808516F060DEB7E56C71A9F0F3A86E6\File MRU]

"Item 1"="[F00000000][T01D2CB2A602B2170][O00000000]*H:\\"FILENAME"xlsx"

When the user logs on next time, recent files do not show in the office application and the registry setting is not present in the users registry. Other settings are remembered and loaded correctly.

Anyone any ideas? Would be much appreciated!

Ivanti DSM 2018.1enriches usability, cloud readiness, and Windows 10 upgrades

Join the beta program, we’d love to hear from you

The BETA version of DSM 2018.1 is not intended for productive use, but solely for testing purposes. We are making this latest beta release available here in the community three weeks before the actual release.

The beta version of DSM 2018.1  7.4.1_build4447 can be downloaded here

Release notes BETA can be downloaded here

Endpoint Management can get complex. The new version of DSM 2018.1 is packed with various usability and performance enhancements to make administration a breeze. Here just some of the highlights of this release:

Zero day support of Windows 10

Benefit from the latest and greatest Windows 10 version when you are ready to stage your inplace-upgrade, migration or deployment. DSM is providing zero day support of every new Windows 10 version.

Improved usability

DSM packaging and eScripts that you love, just got even better. Benefit from improved software tag handling and eScript command extensions to display custom maintenance timeframes. Accelerate remediation with improved log formats for easier and automated analysis of log files.

Cloud-ready

Embark on your journey to the cloud. DSM will officially support Amazon RDS with MS SQL server for the DSM database with version 2018.1.

Enhanced notifications
Wondering whether a change task has been transmitted to your endpoints? The DSM console provides you with alerts and notifications for change tasks and also improved visibility on property group levels. You can filter your own tasks in the “Infrastructure Task” view and benefit from automated updates.

Want to be a Beta Tester?
This version is bursting with updates that will make managing your endpoints easier, incl. infrastructure changes, OSD enhancements,  Web UI Dashboard updates, and overall improved performance and stabilization. DSM 2018.1 is planned to release end of March.

If you are interested in participating in the Beta Program, please contact us via this thread on the community. We’d love to hear from you.

New Features:

• Improved SW-tag handling using type-aheads
• "GetMaintenanceTimes" now works with custom time frames - New Command GetTimeTableTimes
• Writing custom log file entries by a new WriteLogEntry command
• Log format for Splunk interface allows easier automatic analysis by writing the current date in every line
• CallScriptAs for scripting host using any account

Windows 10:

• Every new version of Windows 10 is supported on day 0
• Ability to stage Windows 10 in-place upgrades and usage of peer to peer functionality

Patch Management:

• Make administration of DSM Patch Management easier by moving all Patch Management Settings into one place
• Support Linux patching for CentOS and Ubuntu (via PatchLink add-on)

Web UI

• New Dashboard capabilities – create your own dashboards in a BI like style

DSM Console:

• The view "Infrastructure Task" now has a filter for my own tasks and auto refreshes
• The "execute change" Task now shows a concluding message to confirm that it was successfully transmitted to the endpoint
• Execution Attempts of software set components are now aggregated for the set
• Ability to set the visibility option on the property group level (not only on the property definition level)

Infrastructure:

• DSM 2018.1 officially supports SQL Server 2017
• Fast package distribution to any depot so that packages will be available faster in any location
• Possibility to configure the logfile path -> LogFilePath can now be overwritten in the registry
• Possibility to define the unique identification order of clients (SMBIOS GUID, SID, MAC, FQDN)

OSD:

• Possibility to change the OS flavor and language of an OS Setup File Package after its creation
• Synchronization of computer properties before installing packages, so that dynamic group memberships can be built even for pre OS phase

Cloud:

• Official support of Amazon RDS with MS SQL Server for DSMDB

The boot.wim and boot_x64.wim that ship with LDMS include the Threshold I RTM version of WinPE.  There have been two newer releases of WinPE since this version.  The current most up to date version is RedStone I / 1607.  New versions of WinPE are released every 6 months from Microsoft.

Some hardware such as the Surface Studios require this newer version in order to be PXE booted and provisioned.

Here are the steps to take to upgrade your boot files to a newer version of WinPE:

Step 1:

Download and install the latest version of the Windows ADK (or the version you need) from the below link to get Microsoft's release of the WinPE files that match the specific OS version:

Windows ADK downloads - Windows Hardware Dev Center

Step 2:

Run the Deployment and Imaging Tools Environment as administrator:

Step 3:

Download and run the following script from with-in the Deployment and Imaging Tools Environment CMD box that will prepare your WinPE files from Microsoft with the required modules for LDMS:

Create-WinPE.bat (attached to this document)

Step 4:

Take your prepared boot.wim and boot_x64.wim files from c:\winpe_x86 and c:\winpe_amd64 and copy them to this folder on your core:

Letter:\Program Files\LANDesk\ManagementSuite\landesk\vboot\clean\

*Note - backup the original files that are there incase you need to revert to the version that Ivanti ships with LDMS.

Step 5:

Backup your old production boot files.  Create copies of the files located at Letter:\Program Files\LANDesk\ManagementSuite\landesk\vboot and put them some where safe (step 6 will overwrite them).  However you must keep a copy of your old boot files here still.  Do not simply move them to another location.  Step 6 will be looking for these old boot files in order to migrate the HII drivers over to the new boot files, so if you rename them or move them instead of just making a copy of them - that step will not work completely.

Step 6:

On your core server launch an elevated command prompt and run:

This will upgrade your existing LDMS boot.wim and boot_x64.wim to now be RedStone I / 1607.

These updated files will be located at:

Letter:\Program Files\LANDesk\ManagementSuite\landesk\vboot

Additional notes:

- Bitlocker support is added via the Create-WinPE.bat script.  (can use manage-bde.exe with-in WinPE)

- PowerShell usage without requiring full path is additionally added.

We have a Windows 2016 with Office 2016 Office setup with environment manager 10.1 (FR1).  Our mail is in Office 365

when launching outlook 2016, we keep getting a prompt to enter username and password, although we have configured roaming of the credentials.  From what I can tell, credentials are stored in

Contorl Panel > Credential Manager.  There are two types:

MicrosoftOffice16_data: SSPI and MicrosoftOffice16_Data:ADAL

The first one has persistence set to Enterprise, which is correct.  Data:ADAL entries have persistence set to Logon session.

It seems after logging off, the ADAL credentials are discarded (which makes sense from the persistence description).

After logging back in, we get prompted for Outlook credentials, and the Data:ADAL credentials are added again to the credential manager.

I found ADAL is related to Office Modern authentication, which can be disabled, but we don't want to do this.

any idea's?

many thanks

Hi all,

I'm having some issues trying to deploy a batch file that will copy some powerpoint, excel, and word templates to their desktops. (We just had a rebranding)

On my test machines, the batch file runs fine for both Windows XP and Windows 7. I don't know what the problem is here as the batch files work fine without LANDesk, but when I go to distribute the task through LANDesk I get a "Package deployment failed" and a Return code 4.

Everyone has access to this share, I'm using a policy supported push, and I tried sifting through the log files with no real answer for why it isn't deploying.

I still haven't been able to find documentation on return code 4 as well.

Here's my scripting for both OS's:

Windows 7:

@ECHO ON
::Copies files to dekstop of current user *For Windows 7

xcopy "\\networkshare\tempstorage\Templates" "%systemdrive%\users\%username%\Desktop\Templates\" /O /X /E /H /K

Windows XP:

xcopy "\\networkshare\tempstorage\Templates" "%userprofile%\Desktop\Templates\" /O /X /E /H /K

Would appreciate any help in this matter!

Thanks.

Hello all,

   We have just gotten some new HP elite book 840 G4 and HP elite desk 800 SFF G3 desktops.  I am unable to image these and I have tried everything I can think of, hopefully someone out there has some insight.

In Legacy mode "Legacy boot enabled, Secure Boot disabled", the computer will boot and connect to the PXE server.  The boot.wim file loads but after applying drivers, the computer cannot get an IP address.  I thought that it was because of a missing network driver so I found the WinPE 10 packs from Dell, HP and Intel.  Although the drivers load, it doesn't change the behavior.

I tried the UEFI mode, "Legacy boot disabled, Secure Boot enabled".  The computer does not even PXE boot.  Other computers we have in the environment will boot this way, so I am stumped.  The screen will show that it is trying to UEFI PXE IPv4, but then beep and return to the boot menu.  IPv6 also does not work, but I had no expectation that it would.

Any help is appreciated.  Thanks in advance,

-Pat

Is there an easy way to unpin Edge from the taskbar in windows 10 (1703)? Every time a user unpins and reboots it comes back. I have tried using the start.xml file with <CustomTaskbarLayoutCollection PinListPlacement="Replace"> but I cannot seem to get this working. Just wondering if anyone had a way to do it with AppSense 10.1 FR3.

Thanks

The boot.wim and boot_x64.wim that ship with LDMS include the Threshold I RTM version of WinPE.  There have been two newer releases of WinPE since this version.  The current most up to date version is RedStone I / 1607.  New versions of WinPE are released every 6 months from Microsoft.

Some hardware such as the Surface Studios require this newer version in order to be PXE booted and provisioned.

Here are the steps to take to upgrade your boot files to a newer version of WinPE:

Step 1:

Download and install the latest version of the Windows ADK (or the version you need) from the below link to get Microsoft's release of the WinPE files that match the specific OS version:

Windows ADK downloads - Windows Hardware Dev Center

Step 2:

Run the Deployment and Imaging Tools Environment as administrator:

Step 3:

Download and run the following script from with-in the Deployment and Imaging Tools Environment CMD box that will prepare your WinPE files from Microsoft with the required modules for LDMS:

Create-WinPE.bat (attached to this document)

Step 4:

Take your prepared boot.wim and boot_x64.wim files from c:\winpe_x86 and c:\winpe_amd64 and copy them to this folder on your core:

Letter:\Program Files\LANDesk\ManagementSuite\landesk\vboot\clean\

*Note - backup the original files that are there incase you need to revert to the version that Ivanti ships with LDMS.

Step 5:

Backup your old production boot files.  Create copies of the files located at Letter:\Program Files\LANDesk\ManagementSuite\landesk\vboot and put them some where safe (step 6 will overwrite them).  However you must keep a copy of your old boot files here still.  Do not simply move them to another location.  Step 6 will be looking for these old boot files in order to migrate the HII drivers over to the new boot files, so if you rename them or move them instead of just making a copy of them - that step will not work completely.

Step 6:

On your core server launch an elevated command prompt and run:

This will upgrade your existing LDMS boot.wim and boot_x64.wim to now be RedStone I / 1607.

These updated files will be located at:

Letter:\Program Files\LANDesk\ManagementSuite\landesk\vboot

Additional notes:

- Bitlocker support is added via the Create-WinPE.bat script.  (can use manage-bde.exe with-in WinPE)

- PowerShell usage without requiring full path is additionally added.