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

Has anybody figured out how to completely partition a laptop during provisioning with a EFI System Reserved partition, Microsoft Reserved partition (MSR), C:Windows, and Recovery partition? Can this be done?

In other words, can the following partition scheme be implemented?

Can this be done using Actions in LANDesk provisioning?

Here is a list of all the EM templates and their location. As new ones get posted I'll update this list in this thread.

Landon.


Template Name - Location

1. Word - OOB
2. Excel - OOB
3. PowerPoint - OOB
4. Outlook - OOB
5. Clip Organizer - OOB
6. Graph - OOB
7. InfoPath - OOB
8. Media Catalog - OOB
9. Picture Manager - OOB
10. Project - OOB
11. SharePoint Workspace - OOB
12. Visio - OOB
13. Internet Explorer - OOB
14. Windows Media Player - OOB
15. Acrobat Reader - OOB
16. Lotus Notes - OOB
17. Firefox - OOB
18. Remote Desktop Client - OOB
19. Accessibility Keyboard - OOB
20. Audio and Sounds - OOB
21. Tablets - OOB
22. Visual Settings - OOB
23. Action Center - OOB
24. Active Setup - OOB
25. General Folder Settings - OOB
26. Libraries - OOB
27. Links - OOB
28. Mapped Drives - OOB
29. Mapped Printers - OOB
30. Network Location Shortcuts - OOB
31. Search Folder Options - OOB
32. View Folder Options - OOB
33. IE 10 Cookies - OOB
34. IE 10 History - OOB
35. Input Keyboard - OOB
36. Mouse - OOB
37. Mail Signatures - OOB
38. MAPI Profile - OOB
39. Input Language - OOB
40. Language Bar - OOB
41. Locale - OOB
42. MUI - OOB
43. Certificates - OOB
44. Credentials - OOB
45. Notification Area - OOB
46. Start Menu - OOB
47. Start Menu - Recently Launched Applications - OOB
48. Taskbar - OOB
49. Toolbars - OOB
50. Icons - OOB
51. Themes - OOB
52. Windows Color and Appearance - OOB
53. Account Picture - OOB
54. ClearType - OOB
55. Icon Position and Views - OOB
56. Screen Saver - OOB
57. Visual Effects - OOB
58. Wallpaper - OOB
59. Acrobat - Acrobat and Acrobat Reader Template
60. BlueZone - Rocket Software - BlueZone
61. Snagit - TechSmith - Snagit
62. iManage - Office 2010 - [Legal] iManage + MS Office 2010
63. iManage - Office 2013 - [Legal] iManage + MS Office 2013
64. AccuRoute - [Legal] AccuRoute
65. Camtasia - [Legal] Camtasia Studio
66. Chrome - Google Chrome Template
67. WinZip - Winzip Template
68. Notepad++ - Notepad++ Template
69. Cisco Jabber - Cisco Jabber Template
70. AppSense Consoles - AppSense Consoles Template
71. Photoshop - Adobe Photoshop Template
72. Persinfo - Persinfo Template
73. Visual Studio - Visual Studio Template
74. Lync - Lync Template
75. Sticky Notes - StickyNotes Template
76. Printers - Printers Template
77. Command Prompt - Command Prompt Template
78. Sysinternal Tools - Sysinternals Template
79. Regedit - Regedit Template
80. PuTTY - PuTTY Template
81. 2012 Server Manager - 2012 Server Manager Template
82. Adobe Illustrator - Adobe Illustrator Template
83. Angry Birds - Angry Birds Template
84. Notepad - Notepad Template
85. Wordpad - Wordpad Template
86. MS Paint - MS Paint Template
87. Calculator - Calculator Template
88. Snipping Tool - Snipping Tool Template
89. FileZilla - FileZilla Personalization Template
90. Microsoft Management Console - Microsoft Management Console Personalization Template
91. Citrix App Center - Citrix App Center Personalization Template
92. AOL Instant Messenger - AOL Instant Messenger (AIM) Personalization Template
93. Helios TextPad - Helios TextPad Personalization Template
94. Microsoft Dynamics SL - Microsoft Dynamics SL 2011 Personalization Template
95. Firefox - FireFox Template
96. GoToMeeting - GoToMeeting Template
97. AutoCAD - AutoCAD Template
98. Taskmanager - Task Manager Template
99. Windows Media Center - Windows Media Center Template
100. Windows Fax and Scan - Windows Fax and Scan Template
101. Windows DVD Maker - Windows DVD Maker Template
102. WinRAR - WinRAR Template
103. Avaya IP v6 - http://www.appsense-exchange.com/Tools/AEL00180
104. Avaya IP v7 - http://www.appsense-exchange.com/Tools/AEL00181
105. 7-Zip - 7-Zip Personalization Template
106. Open Office - Open Office Template
107. ArcGIS - ArcGIS Personalization Template
108. Client Access (HTE) - Client Access (HTE) Personalization Template
109. Laserfiche - Laserfiche Personalization Template
110. Cute FTP - GlobalScape CuteFTP 9 Personalization Template
111. Skype - Skype Template
112. Track-IT - Track-IT Template
113. Auto Audit - Auto Audit Template
114. Beyond Compare - Beyond Compare Template
115. SAP - SAP Personalization Template
116. Remote Desktop Connection Manager - Remote Desktop Connection Manager (RDCMan) Template
117. Microsoft Office 2016 - Office 2016 Template
118. Webex - Webex Personalization Template
119. WinSCP - WinSCP Template
120. vSphere - vSphere Template
121. KeePass - KeePass Template
122. Hyper-V Management Console - Personalization Template for Hyper-V Management Console

Hallo zusammen!

hoffentlich kann uns von euch jemand weiterhelfen - wir stecken in der Paketierung des Windows 10 Upgrades auf 1709.1 fest und kommen nicht mehr weiter.

Wir haben aktuell großflächig v1703 im Einsatz und wollen demnächst mit 1709 in die Breite gehen. Bare-Metal Installationen sind dabei kein Problem, allerdings treten wir beim Upgrade bestehender Clients auf der Stelle.

Wir haben aktuell noch DSM 2016.2 R2.1 im Einsatz, für das Upgrade nutzen wir zwei Pakete:

1. Im Autoinstaller läuft ein Paket das den User fragt ob er das Upgrade durchführen will. Wenn ja, wird das Computerobjekt in eine statische Gruppe verschoben, der die Upgrade Pakete zugewiesen sind und dann der Rechner neugestartet

2. Im ServiceInstaller (unser Service läuft als SYSTEM), wird dann nach dem Reboot das Upgrade und entsprechend weitere Pakete ausgeführt

Und genau dort kommen wir nicht weiter:

Setup.exe startet mit den entsprechenden Parametern (wir sind mittlerweile mit fast allen denkbaren Kombinationen durch) und hört nach kurzer Zeit einfach auf, etwas zu "tun", keine CPU Last, keine Speicher Last auf der Festplatte tut sich nix mehr.

Das Setupact.log ist keine 150KB groß, im ganzen $Windows.~BT Verzeichnis tut sich kaum was bis der ExecuteEx in einen Timeout läuft. Der Timeout tritt auch schon bei einem /Compat Scanonly auf.

Manuell lässt sich das Update allerdings problemlos installieren.

Hat hier schon jemand ähnliches Verhalten gesehen oder hätte einen Ansatzpunkt wo wir suchen können?

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

Hello Community,

I have a few questions which you can hopefully answer easily. Googleing for an answer didnt give me any useful results.

I work at a company where Landesk is being used. Sometimes, for example when I need assistance from the IT Helpdesk they access my computer via Landesk remote access. I get a popup asking me if i want to allow access and when I click Yes thesy can use my computer remotly.

This is all ok, but I have the feeling that sometimes I am being accessed remotly whithout my allowance/interaction and someone is spying on me

I hope that doesnt sound to paranoid!

1) is it possible to access a computer with Landesk remote, while a local user is logged on and watch the screen without that user knowing it?

2) If yes, how can this be prevented by the user and how can the user notice when this remote spying happens? Can I monitor some ports or processes?

I have full local admin rights on my machine btw. and we run Win7.

Thanks for any useful answers.

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.

Hallo Community

Ich habe jetzt schon mehrere Einträge in diesem Forum gesehen bezüglich Upgrades der einzelnen Windows 10 Updates. Es gibt ja aus meiner Sicht mehrere Möglichkeiten welche möglich sind.

- WSUS
- DSM (In-Place Upgrade)

Welche Variante ist aus euerer Sicht die bessere? Wir haben aktuell die Version 1607 installiert und müssen jetzt wohl oder übel auf die neue Version 1709 Upgraden.

Ich bin euch sehr dankbar über Ratschläge.

Gruss Flavio

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

Hello Community,

I have a few questions which you can hopefully answer easily. Googleing for an answer didnt give me any useful results.

I work at a company where Landesk is being used. Sometimes, for example when I need assistance from the IT Helpdesk they access my computer via Landesk remote access. I get a popup asking me if i want to allow access and when I click Yes thesy can use my computer remotly.

This is all ok, but I have the feeling that sometimes I am being accessed remotly whithout my allowance/interaction and someone is spying on me

I hope that doesnt sound to paranoid!

1) is it possible to access a computer with Landesk remote, while a local user is logged on and watch the screen without that user knowing it?

2) If yes, how can this be prevented by the user and how can the user notice when this remote spying happens? Can I monitor some ports or processes?

I have full local admin rights on my machine btw. and we run Win7.

Thanks for any useful answers.

Attached is the latest version of PersInfo.

PersInfo is a visual debugging aid for AppSense Environment Manager Personalization. It allows users or administrators to view information in real-time regarding the current session, such as connectivity state, configuration and cache size (amongst others). In addition it allows instant verification that applications are being managed (virtualized) via the use of coloured 'window frames', and popup notifications can alert the user when server or client synchronisation is occurring, new configurations have been loaded or when errors have occurred.

This version is compatible with all versions of Environment Manager Personalization from 8.4 onwards.

Hi

I am very new to the forums and Landesk in general

I have a problem upgrading windows 10 from 1511 to 1709 using patch and compliance.

Here is what I've done so far

I followed the below guide, downloaded the ISO from our Microsoft portal, we have both Enterprise and Pro in our environment so I created a file for both of them and  Landesk accepts them both as downloaded

How to upgrade to Windows 10 Creators Edition using Ivanti Patch Manager

Then I distributed the ISO's to our preferred server and created a repair job

this job I sent to a specific machine and within 2 minutes it showed Success

now for my stress factor..

Noting happened on the machine itself, I cannot see the package on the machine and it does not patch.

I have created several software packages and set up PXE booting for the environment but this one I cannot solve

I sent a package to the machine to check if I could install to it, and that works as it should

I hope you guys can point me in the right direction

Last change 23rd Mar 2018

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

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

The RC of DSM 2018.1 is not intended for productive use, but solely for testing purposes. We are making this latest RC release available here in the community one week before the actual release.

It is supposed to be the final release version

The RC version of DSM 2018.1  7.4.1_build4461 can be downloaded here

Release notes RC 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 RC 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

I am using EPM 2017.3, and have imported my existing database from 9.6.  I have a couple of rogue devices that show up in inventory but have no data.  I can delete them, but after a length of time, they just show up again.  My database was moved to a SQL server managed by our DBAs due to its size, so I no longer have the ability to look around for the information I need.  What table does EPM store computers in?  If a DBA goes in and deletes a record from said table, are there any other items of concern?  Thanks for any assistance.

Habe ein Problem im Classic PM festgestellt, das auch durch den IVanti Support bestätigt wurde, jedoch nicht mehr gefixed werden soll.

Das hat mich ziemlich erstaunt, weil das classic PM noch ganz offiziell im Support ist.

Der Fall wird hier beim Kunden jetzt auch rechtlich geprüft.

Auch eine Ankündigung seitens Ivanti, dass es hierbei Änderungen gibt, kenne ich nicht.

Wisst ihr was dazu?

Wer benutzt denn von euch das Classic PM und wer das APM?

Gruß

Jan

Hallo zusammen!

hoffentlich kann uns von euch jemand weiterhelfen - wir stecken in der Paketierung des Windows 10 Upgrades auf 1709.1 fest und kommen nicht mehr weiter.

Wir haben aktuell großflächig v1703 im Einsatz und wollen demnächst mit 1709 in die Breite gehen. Bare-Metal Installationen sind dabei kein Problem, allerdings treten wir beim Upgrade bestehender Clients auf der Stelle.

Wir haben aktuell noch DSM 2016.2 R2.1 im Einsatz, für das Upgrade nutzen wir zwei Pakete:

1. Im Autoinstaller läuft ein Paket das den User fragt ob er das Upgrade durchführen will. Wenn ja, wird das Computerobjekt in eine statische Gruppe verschoben, der die Upgrade Pakete zugewiesen sind und dann der Rechner neugestartet

2. Im ServiceInstaller (unser Service läuft als SYSTEM), wird dann nach dem Reboot das Upgrade und entsprechend weitere Pakete ausgeführt

Und genau dort kommen wir nicht weiter:

Setup.exe startet mit den entsprechenden Parametern (wir sind mittlerweile mit fast allen denkbaren Kombinationen durch) und hört nach kurzer Zeit einfach auf, etwas zu "tun", keine CPU Last, keine Speicher Last auf der Festplatte tut sich nix mehr.

Das Setupact.log ist keine 150KB groß, im ganzen $Windows.~BT Verzeichnis tut sich kaum was bis der ExecuteEx in einen Timeout läuft. Der Timeout tritt auch schon bei einem /Compat Scanonly auf.

Manuell lässt sich das Update allerdings problemlos installieren.

Hat hier schon jemand ähnliches Verhalten gesehen oder hätte einen Ansatzpunkt wo wir suchen können?

Hallo Community

Ich habe jetzt schon mehrere Einträge in diesem Forum gesehen bezüglich Upgrades der einzelnen Windows 10 Updates. Es gibt ja aus meiner Sicht mehrere Möglichkeiten welche möglich sind.

- WSUS
- DSM (In-Place Upgrade)

Welche Variante ist aus euerer Sicht die bessere? Wir haben aktuell die Version 1607 installiert und müssen jetzt wohl oder übel auf die neue Version 1709 Upgraden.

Ich bin euch sehr dankbar über Ratschläge.

Gruss Flavio

I need some help, we are on 9.6 SP2. We recently recieved two new Dell Models, the Precision Laptop 7710 and the 5510. Both of these units come with a Samsung NVMe Solid State Drive, we tired the image the computers and they keep blue screening after the image is laid down. Has anyone been able to image a NVMe SSD?