Hi,

We have just done a fresh install of Management Suite 2016 on Windows Server 2012 with a new database. I have begun packaging some of our applications and have run into a new issue I did not have with 9.6. All of my packages are getting stuck on active with a 1354 return code and a result note saying the "Client has started processing the task". The example below is a simple MSI distribution package which shows the issue. This issue is happening on all of our packages.

Task ID:

Policy XML

<?xml version="1.0" encoding="utf-8"?>

<ClientPolicy xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

  <PolicyInfo>

    <PortalInfo>

      <p>

        <Name>Title</Name>

        <Val>Google Chrome</Val>

      </p>

      <p>

        <Name>Description</Name>

        <Val>Google Chrome</Val>

      </p>

      <p>

        <Name>Category</Name>

        <Val>Browser</Val>

      </p>

      <p>

        <Name>CategoryID</Name>

        <Val>14</Val>

      </p>

      <p>

        <Name>ID</Name>

        <Val>28</Val>

      </p>

      <p>

        <Name>Size</Name>

        <Val>52396032</Val>

      </p>

      <p>

        <Name>Type</Name>

        <Val>MSI</Val>

      </p>

      <p>

        <Name>PublishedDate</Name>

        <Val>3/1/2016 9:23:40 AM</Val>

      </p>

      <p>

        <Name>Tags</Name>

        <Val>64 Bit,Microsoft Windows</Val>

      </p>

      <p>

        <Name>Logo</Name>

        <Val />

      </p>

      <p>

        <Name>ScreenShot_0</Name>

        <Val />

      </p>

      <p>

        <Name>ScreenShot_1</Name>

        <Val />

      </p>

      <p>

        <Name>ScreenShot_2</Name>

        <Val />

      </p>

      <p>

        <Name>ApplicationVendor</Name>

        <Val>Google</Val>

      </p>

      <p>

        <Name>EstDownloadTime</Name>

        <Val>5</Val>

      </p>

      <p>

        <Name>EstInstallTime</Name>

        <Val>5</Val>

      </p>

      <p>

        <Name>RebootExpected</Name>

        <Val>False</Val>

      </p>

      <p>

        <Name>TaskName</Name>

        <Val>Google Chrome - 2/26/2016 10:55:38 AM</Val>

      </p>

    </PortalInfo>

    <Mode>Required</Mode>

    <ItemType>SWD</ItemType>

    <TaskIdn>1104</TaskIdn>

    <LeaveInPortal>false</LeaveInPortal>

    <Interval>Once</Interval>

    <PolicyHash>S1PKtSSJ7NH8hC0GTw5P2lg2U/o=</PolicyHash>

    <TaskName>Google Chrome - 2/26/2016 10:55:38 AM</TaskName>

    <MultiTaskProtection>false</MultiTaskProtection>

    <TaskLastSavedDate>Tuesday, March 1, 2016 9:23:40 AM</TaskLastSavedDate>

    <PushTask>false</PushTask>

  </PolicyInfo>

  <RunInfo>

    <Settings>

      <p>

        <Name>IgnoreSubsequentAttempts</Name>

        <Val>False</Val>

      </p>

    </Settings>

    <IgnoreSubsequentAttempts>false</IgnoreSubsequentAttempts>

  </RunInfo>

</ClientPolicy>

SDCLIENT LOG

• C:\Program Files (x86)\LANDesk\LDClient\Data\sdclient.log

Tue, 01 Mar 2016 09:23:54 Core name 'Our Sever' obtained from the registry

Tue, 01 Mar 2016 10:06:25

Tue, 01 Mar 2016 10:06:25 CPolicyHistory::LoadHistoryDaysToKeep: Registry settings for task history maintenance mode (Days To Keep) is '5'

Tue, 01 Mar 2016 10:06:25 PostInstallInventoryScan: Getting post package install inventory delay setting.

Tue, 01 Mar 2016 10:06:25 PostInstallInventoryScan: Not running post package install inventory scan, the inventory scan delay value is out of range, min is 5, max is 60, current value is '-1'

Tue, 01 Mar 2016 10:06:25 The nostatus flag has NOT been set.

Tue, 01 Mar 2016 10:06:25 Core name 'Our Sever' obtained from the registry

Tue, 01 Mar 2016 10:06:25 Sending task status, cmd line -coreandip=Our Sever -taskid=1104 -retcode=229638145 -complete -pkgid=28

sdclient_task1104  

• C:\Program Files (x86)\LANDesk\LDClient\Data\sdclient_task1104.log

Tue, 01 Mar 2016 09:23:55 ******* sdclient starting to process task *******

Tue, 01 Mar 2016 09:23:55 Task id to process: 1104

Tue, 01 Mar 2016 09:23:55 Command line: /policyfile="C:\ProgramData\LANDesk\Policies\CP.1104.RunNow._chDj1tTzFaLrt2OsiRQH9ZQC0pM=.xml"

Tue, 01 Mar 2016 09:23:55 The nostatus flag has NOT been set.

Tue, 01 Mar 2016 09:23:55 Core name 'Our Sever' obtained from the registry

Tue, 01 Mar 2016 09:23:55 Sending task status, cmd line -coreandip=Our Sever -taskid=1104 -retcode=229392442 "-ldap=CN=user,OU=Faculty&Staff,DC=ourdomain,DC=EDU" -pkgid=28

Tue, 01 Mar 2016 09:34:02 File (\\ourserver\Deploy\Software\Google\googlechromestandaloneenterprise64.msi) is cached locally

Tue, 01 Mar 2016 09:34:02 The nostatus flag has NOT been set.

Tue, 01 Mar 2016 09:34:02 Core name 'Our Sever obtained from the registry

Tue, 01 Mar 2016 09:34:02 Sending task status, cmd line -coreandip=Our Sever -taskid=1104 -retcode=229392444 "-ldap=CN=user,OU=Faculty&Staff,DC=ourdomain,DC=EDU" -pkgid=28

Tue, 01 Mar 2016 09:44:04 About to call DownloadFiles (1 files) with these settings:

Tue, 01 Mar 2016 09:44:04 m_allowedBandwidthWAN: 50

Tue, 01 Mar 2016 09:44:04 m_allowedBandwidthLAN: 75

Tue, 01 Mar 2016 09:44:04 m_discardPeriodSeconds: 604800

Tue, 01 Mar 2016 09:44:04 m_preserveDirectoryStructure: 1

Tue, 01 Mar 2016 09:44:04 m_bUseWanBWForPush: 0

Tue, 01 Mar 2016 09:44:04 m_bSynchronize: 0

Tue, 01 Mar 2016 09:44:04 Allowed download methods(m_downloadControl):

Tue, 01 Mar 2016 09:44:04 PeerOneSource

Tue, 01 Mar 2016 09:44:04 Peer

Tue, 01 Mar 2016 09:44:04 Source

Tue, 01 Mar 2016 09:44:04 m_preferredServerControl: AttemptPreferredServer

Tue, 01 Mar 2016 09:44:06 The nostatus flag has NOT been set.

Tue, 01 Mar 2016 09:44:06 Core name 'Our Sever' obtained from the registry

Tue, 01 Mar 2016 09:44:06 Sending task status, cmd line -coreandip=Our Sever -taskid=1104 -retcode=229392444 "-message=100%" -pkgid=28

Tue, 01 Mar 2016 09:44:06 The nostatus flag has NOT been set.

Tue, 01 Mar 2016 09:44:06 Core name 'Our Sever' obtained from the registry

Tue, 01 Mar 2016 09:44:06 Sending task status, cmd line -coreandip=Our Sever -taskid=1104 -retcode=229392258 "-ldap=CN=user,OU=Faculty&Staff,DC=ourdomain,DC=EDU" -pkgid=28

Tue, 01 Mar 2016 09:54:39 ExpandEnvironmentVariables Result: /i /quiet /norestart

Tue, 01 Mar 2016 09:54:39 MSI Client Thread

Tue, 01 Mar 2016 09:54:39 PackagePath: [\\ourserver\Deploy\Software\Google\googlechromestandaloneenterprise64.msi]

Tue, 01 Mar 2016 09:54:39 Execute Msiexec.exe with command Line: "Msiexec.exe"  /quiet /norestart /i "C:\Program Files (x86)\LANDesk\LDClient\sdmcache\Deploy\Software\Google\googlechromestandaloneenterprise64.msi" REBOOT=ReallySuppress

Tue, 01 Mar 2016 09:55:55 MSI result DB50000

Tue, 01 Mar 2016 09:55:55 Rebooting system if needed

Tue, 01 Mar 2016 10:06:25 processing of package is complete, result 229638145 (0x0db00001 - code 1)

PolicyTaskHandler.exe.log

03/01/2016 09:23:43 INFO  13736:1     RollingLog : Core has changed, resetting the core language cache

03/01/2016 09:23:43 INFO  13736:1     RollingLog : Getting core language for Key:CurrentLanguage Language:ENU

03/01/2016 09:23:43 INFO  13736:1     RollingLog : Getting core language for Key:LegacyLanguage Language:ENU

03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\LANDesk.ManagementSuite.Data.dll> returned True.  wasVerified: True

03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\package.data.dll> returned True.  wasVerified: True

03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\LANDesk.ManagementSuite.HPPowerSettings.dll> returned True.  wasVerified: True

03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\LANDesk.ManagementSuite.HPBiosSettingsPolicy.Business.dll> returned True.  wasVerified: True

03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\LANDesk.ManagementSuite.SecureEraseSettings.Business.dll> returned True.  wasVerified: True

03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\AVBiz.dll> returned True.  wasVerified: True

03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\patchbiz.dll> returned True.  wasVerified: True

03/01/2016 09:23:44 INFO  13736:1     RollingLog : Current language: ENU

03/01/2016 09:23:44 INFO  13736:1     RollingLog : Using culture info: en-US

03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\PatchManagement.dll> returned True.  wasVerified: True

03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\LANDesk.ManagementSuite.SoftwareDistribution.Business.dll> returned True.  wasVerified: True

03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\LANDesk.PWM.Data.dll> returned True.  wasVerified: True

03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\AlertBiz.dll> returned True.  wasVerified: True

03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\PanelManager.dll> returned True.  wasVerified: True

03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\UserManagement.Business.dll> returned True.  wasVerified: True

03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\RCBehaviorBiz.dll> returned True.  wasVerified: True

03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\CommonAgentSettingsProvider.dll> returned True.  wasVerified: True

03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\LANDESK.MDM.Console.dll> returned True.  wasVerified: True

03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\LANDesk.PWM.Business.dll> returned True.  wasVerified: True

03/01/2016 09:23:44 INFO  13736:1     RollingLog : Verify strong name for <C:\Program Files\LANDesk\ManagementSuite\ManageLdappl.dll> returned True.  wasVerified: True

03/01/2016 09:23:44 INFO  13736:1     RollingLog : [Task: Google Chrome - 2/26/2016 10:55:38 AM, TaskID: 1104, ProcID: 13736] : ***PolicyTaskHandler run options***

03/01/2016 09:23:44 INFO  13736:1     RollingLog : [Task: Google Chrome - 2/26/2016 10:55:38 AM, TaskID: 1104, ProcID: 13736] : Accelerated push: [True]

03/01/2016 09:23:44 INFO  13736:1     RollingLog : [Task: Google Chrome - 2/26/2016 10:55:38 AM, TaskID: 1104, ProcID: 13736] : Use DNS/WINS resolution for discovery: [True]

03/01/2016 09:23:44 INFO  13736:1     RollingLog : [Task: Google Chrome - 2/26/2016 10:55:38 AM, TaskID: 1104, ProcID: 13736] : Wait for machines to finish: [False]

03/01/2016 09:23:44 INFO  13736:1     RollingLog : [Task: Google Chrome - 2/26/2016 10:55:38 AM, TaskID: 1104, ProcID: 13736] : Maximum Push or Policy-supported push run time minutes: [15]

03/01/2016 09:23:44 INFO  13736:1     RollingLog : [Task: Google Chrome - 2/26/2016 10:55:38 AM, TaskID: 1104, ProcID: 13736] : Verbose logging: [False]

03/01/2016 09:23:46 INFO  13736:1     MDMConsole.MDMTaskHandler : MDMTaskHandler.FilterNodesAndProcess(): Called with 1 computer IDs, Task ID 1104

03/01/2016 09:23:46 INFO  13736:1     MDMConsole.MDMTaskHandler : Queueing 0 devices to notify pipe.

03/01/2016 09:24:07 INFO  13736:1     RollingLog : [Task: Google Chrome - 2/26/2016 10:55:38 AM, TaskID: 1104, ProcID: 13736] : PolicyTaskHandler finished processing task, setting task status to [PULL_AVAILABLE]...

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

Hallo zusammen,

hat jemand schon Erfahrungen mit Windows 10 LTSB gesammelt?

Die Einführung von Windows 10 ist ja irgendwie unausweichlich. Aber nach der interessanten NWC-Roadshow kommen halt doch verschiedene Fragen auf bzw. wir machen uns Gedanken über verschiedene Szenarien.

Für den Standard-Office-Arbeitsplatz wird (da Volumenlizenzen vorhanden) ein "normales" Windows 10 Enterprise sicherlich zum Einsatz kommen. Mit dem Nachteil oder Effekt, dann man hier relativ häufig aktualisieren muss (Inplace-Upgrades). Sprich, bei einem normalen Lebenszyklus eines Rechners von 3 Jahren wird dieser min. ein, eher zwei oder gar drei Inplace-Upgrades bekommen. Länger lebende Rechner dementsprechend mehr.

Wenn ich jetzt überlege, wie lange das zu Hause mit dem Upgrade von Win 7 auf Win 10 gedauert hat, geht das in der Firma ja nicht mehr tagsüber, sprich das Upgrade muss nach Feierabend laufen. Allerdings gibt es bei uns auch genügend Rechner, die im 24/7-Betrieb laufen, hier müssen wird uns überlegen, was sinnvoller ist:

a) die LTSB-Variante nehmen und hoffen, dass die fehlenden Funktionien dort auch nicht gebraucht werden

b) regelmäßig die Rechner tauschen und durch aktuelle Installationen ersetzen. Sofern das mit der installierten Spezialsoftware und den Lizenzbedingungen verbeinbar ist...

Die LTSB-Variant hätte dann auch zur Folge, dass ein "anderes" Betriebssystem zum Einsatz kommt, sprich  man hat zuerst mal ein Win 10 1709 Enterprise und dann ein Win 10 Enterprise LTSB. Später werden sich die Zahl der Installationsquellen erhöhen, wenn dann Win 10 1803 und 1809 hinzukommen, und irgendwann wird es auch Win 10 LTSB 2020 (oder ähnlich) geben...

Wie ist hier Eure Planung?

Gruß

Nils

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?

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

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

Anyone having any luck provisioning machines with a Windows 10 1703 image?  I built the image the same as I have for all of our other builds using the ISO from the Volume Licensing site, but I'm having trouble.  Everything works properly in PE, but then after CTOS runs and the machine logs into Windows, I'm having a few different random issues:

• About half the time, ldprovision is running, but no GUI is being displayed.  These machines typically finish successfully, but the desktop analysts cannot see the progress of provisioning from the machine.
• About half the time, ldprovision doesn't launch.  The machine just sits in an active state and does nothing.  On a few occasions I was able to restart the machine, log in with the admin account, and then ldprovision would start running.
• Sometimes when ldprovision runs after CTOS, it fails at agent installation and the template stops even though everything in the logs appears to be successful.

Just wanted to see if anyone else had any experience with any of this.  Everything works properly if we use our Windows 10 1607 image.

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.

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.

Hi All,

We have an import scheduled to run every midnight that imports new users from AD based on a particular attribute used to filter only users requiring LANDesk access.

Everything works perfectly but we have a large number of external users who we need the default SelfServiceUser role to be removed when imported and another external role (SelfServiceGuest) added to the users profile.

Can't seem to figure this out, even if I remove the SelfServiceUser role it gets added back every day during import.

Can anyone advise the best way to do the below:

Remove SelfServiceUser role from user after import and assign another specified role.

Any help will be greatly appreciated and we might help others who might have similar issues.

Kind regards,

Ajani.

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

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?

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

Hello,

On one particular computer all patches that apply to the Windows Operating System are failing.  Patches like Adobe, Office, Java are installing fine. The error is

"C:\windows\system32\wusa.exe" returned failure exit code (2149842967)

This computer definitely has some DNS/Network issues so I may rebuild it.  I had to register the DNS from the computer to get it to show in DNS again so this may not be an issue Landesk can resolve.  Just looking for tips. Thank you!

Jonathan

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

Hallo zusammen,

hat jemand schon Erfahrungen mit Windows 10 LTSB gesammelt?

Die Einführung von Windows 10 ist ja irgendwie unausweichlich. Aber nach der interessanten NWC-Roadshow kommen halt doch verschiedene Fragen auf bzw. wir machen uns Gedanken über verschiedene Szenarien.

Für den Standard-Office-Arbeitsplatz wird (da Volumenlizenzen vorhanden) ein "normales" Windows 10 Enterprise sicherlich zum Einsatz kommen. Mit dem Nachteil oder Effekt, dann man hier relativ häufig aktualisieren muss (Inplace-Upgrades). Sprich, bei einem normalen Lebenszyklus eines Rechners von 3 Jahren wird dieser min. ein, eher zwei oder gar drei Inplace-Upgrades bekommen. Länger lebende Rechner dementsprechend mehr.

Wenn ich jetzt überlege, wie lange das zu Hause mit dem Upgrade von Win 7 auf Win 10 gedauert hat, geht das in der Firma ja nicht mehr tagsüber, sprich das Upgrade muss nach Feierabend laufen. Allerdings gibt es bei uns auch genügend Rechner, die im 24/7-Betrieb laufen, hier müssen wird uns überlegen, was sinnvoller ist:

a) die LTSB-Variante nehmen und hoffen, dass die fehlenden Funktionien dort auch nicht gebraucht werden

b) regelmäßig die Rechner tauschen und durch aktuelle Installationen ersetzen. Sofern das mit der installierten Spezialsoftware und den Lizenzbedingungen verbeinbar ist...

Die LTSB-Variant hätte dann auch zur Folge, dass ein "anderes" Betriebssystem zum Einsatz kommt, sprich  man hat zuerst mal ein Win 10 1709 Enterprise und dann ein Win 10 Enterprise LTSB. Später werden sich die Zahl der Installationsquellen erhöhen, wenn dann Win 10 1803 und 1809 hinzukommen, und irgendwann wird es auch Win 10 LTSB 2020 (oder ähnlich) geben...

Wie ist hier Eure Planung?

Gruß

Nils

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.