I noticed in 9.6, ImageX shows the progress of laying the image down.

Any chance we can replace whatever piece does this in 9.5 SP2 (or is it fixed in 9.5 SP3)?

Has anything successfully PXE booted their Surface Pro 3?

Surface Pro 3 - all updates

Official MS Surface Ethernet adapter

PXE Rep on same subnet (confirmed working with other computers)

When I attempt, I hold down volume down, tap power. It goes into PXE mode, then release volume down when Surface logo pops up. It then states it's looking for IP over IPv4, then switches to looking for IP over IPv6, then boots into Windows.

I've read elsewhere it will say to press enter if you want to boot into Windows PE, but I never get that.

I've tried turning safeboot off, no luck

Any help would be appreciated. .

Hi all,

Running into a funky issue.  I have a 9.6 Core up and running (fresh install on Server 2012).  I used the nice new "Capture Template" available.  This is quite handy, but I'm running into an issue.

By default, the Dell Venue ships with 6 Partitions (that's right, 6).  After pre-populating a record in the new Core with the MAC address (serial number did not seem to work as the unique ID), and ensuring that the UEFI Network Stack was enabled on the Venue (in the BIOS/UEFI menus, still getting a grasp on what to call them now), I was able to boot to PXE on the Venue and the Prov Capture began (yay!)

The issue is, this Venue is running the Atom processor and the Dock only has a 10/100 NIC.  I'm using Imagew v2 and the capture was going to take about 2.5 hours to complete so I all but gave up, until I realized it wasn't only capturing the used data on each partition.  It was attempting capture of all 50GB of the Windows partition (only about 15GB are used on the partition).  I looked at the command lines of my capture scripts under 9.5 SP2 and they look the same, minus the /UY which just tells the imaging program to continue with no prompts.

Has anyone run into this?  I'd love to capture a hardware-specific reference image of one of these but it would be almost useless if it will take 2.5 hours to capture and potentially another 2.5 to re-deploy (haven't got that far yet).

Is anyone deploying Win 8.1 and have any insight?  Or more specifically doing tablet devices with multiple partitions?  This particular venue is UEFI only (no legacy boot ROMs) if that helps.  Thanks.

I am currently deploying Office 2010 via UNC admin share and settting the deployment method to "run at source"

This works perfect, but I have some apps that need to be copied to the target machine and installed locally on the workstation.

I read some other posts that suggest for multiple files to create a SFX and deploy.

Just wondering what steps others are using to deploy via this method.

I'm trying to find out if there is a way to easily convert the date format in LDMS (Version 9 SP3) inventory data from USA date to UK date ie from mm/dd/yyyy to dd/mm/yyyy.

I do quite a few reports by creating custom queries in LDMS and Exporting as CSV, and Excel (in UK installation) doesn't like some of the dates in the exported CSV but does like others.  IE excel doesn't like 03/19/2012 as it think its the 3rd day of the 19th month, but it does like 12/01/2012 which it thinks is 12th of Jan but its really 1st or Dec. 

From what i can see in the inventory all dates are stored as USA date format, so im guessing maybe there is a simple setting somewhere to change the date to a more Excel firendly UK format?

Hi,

We just upgraded to Management Suite 9.60.0.244

When I try to distribute an exe file I get this message and return code 1354.

There is also an exclamation mark on the task and when I start it is possible to restart direcly after. Just as it is not really run?

The file gets copied to the client machine but the file is not executed.

I have tried to run it both silently and with a progress bar but nothing happends.

The log file does not tell me anything I manage to understand.

I have seen this happen to others but no solution how to solve this.

This is found in the sdclient_taskxxx file

The file is distributed from server1

Wed, 15 Oct 2014 07:53:03 ******* sdclient starting to process task *******

Wed, 15 Oct 2014 07:53:03 Task id to process: 512

Wed, 15 Oct 2014 07:53:03 Command line: /policyfile="C:\ProgramData\LANDesk\Policies\CP.512.RunNow._lIW0e3L0PG&#47vd8TIqNKU9OBgrGU=.xml"

Wed, 15 Oct 2014 07:53:03 File (\\server1\app\Landesk distribution\Microsoft\Patches\kb2878218\mso2010-kb2878218-fullfile-x86-glb.exe) is not in cache

Wed, 15 Oct 2014 07:53:03 The nostatus flag has NOT been set.

Wed, 15 Oct 2014 07:53:03 Core name 'server2' obtained from active task list

Wed, 15 Oct 2014 07:53:03 Sending task status, cmd line -coreandip=server2 -taskid=512 -retcode=229392444 "-ldap=CN=name,OU=IT,OU=HQ,OU=Con,OU=Users,OU=Company,DC=server1,DC=local" -pkgid=367

Wed, 15 Oct 2014 07:53:04 About to call DownloadFiles (1 files) with these settings:

Wed, 15 Oct 2014 07:53:04 m_allowedBandwidthWAN: 25

Wed, 15 Oct 2014 07:53:04 m_allowedBandwidthLAN: 75

Wed, 15 Oct 2014 07:53:04 m_maxDiscoveryThreads: 1430663218

Wed, 15 Oct 2014 07:53:04 m_discardPeriodSeconds: 604800

Wed, 15 Oct 2014 07:53:04 m_preserveDirectoryStructure: 1

Wed, 15 Oct 2014 07:53:04 m_bUseWanBWForPush: 0

Wed, 15 Oct 2014 07:53:04 m_bSynchronize: 0

Wed, 15 Oct 2014 07:53:04 Allowed download methods(m_downloadControl):

Wed, 15 Oct 2014 07:53:04 PeerOneSource

Wed, 15 Oct 2014 07:53:04 Peer

Wed, 15 Oct 2014 07:53:04 Source

Wed, 15 Oct 2014 07:53:04 m_preferredServerControl: AttemptPreferredServer

Wed, 15 Oct 2014 07:53:08 The nostatus flag has NOT been set.

Wed, 15 Oct 2014 07:53:08 Core name 'server2' obtained from active task list

Wed, 15 Oct 2014 07:53:08 Sending task status, cmd line -coreandip=server2 -taskid=512 -retcode=229392258 "-ldap=CN=name,OU=IT,OU=HQ,OU=Con,OU=Users,OU=Company,DC=server1,DC=local" -pkgid=367

Wed, 15 Oct 2014 07:53:09 ExpandEnvironmentVariables Result:

Wed, 15 Oct 2014 07:53:09 The nostatus flag has NOT been set.

Wed, 15 Oct 2014 07:53:09 Core name 'server2' obtained from active task list

Wed, 15 Oct 2014 07:53:09 Sending task status, cmd line -coreandip=server2 -taskid=512 -retcode=229392406 "-ldap=CN=name,OU=IT,OU=HQ,OU=Con,OU=Users,OU=Company,DC=server1,DC=local" -pkgid=367

Wed, 15 Oct 2014 07:53:11 LSWD or Executable Client Thread

Wed, 15 Oct 2014 07:53:11 PackagePath:             [\\server1\app\Landesk distribution\Microsoft\Patches\kb2878218\mso2010-kb2878218-fullfile-x86-glb.exe]

Wed, 15 Oct 2014 07:53:11 Processing generic executable

I guess it has something to do with the delivery method? If I check Agent settings in old sheduled tasks I can see they refer to my earlier configured delivery method. In my new task it is default set to  "keep agent's current settings" and it is not possible to find my earlier created delivery methods.

I really would appreciate any help. :-)

Hi,

I've done a query to get all the Dell machines warranty details. When I do so, I'm getting multiple Warranty End dates, as Dell has some NBD, Parts only Warranty and etc., kinds of warranties associated with the single system. Is there any way to get exact warranty end-date. Anyone faced this situation earlier. Please help!!!

The following image will tell you. For the same service tag there are different warranty-end dates. (L12 is the last three letters of the Dell service tag )

Regards,

Sukumar. R.

After doing an inplace upgrade from 9.0 sp4 to 9.6, we've been having a lot of trouble with our pre-9.6 scheduled tasks.  This was no big deal as we can create new tasks, since the old ones simply failed... but the odd thing is now we can't do anything with the old tasks.

And by "can't do anything", I mean we can't right click on them, can't delete them, if we click on one the charts never show up.  This started this morning. Has anyone else experienced issues with the Scheduled Tasks tab, and unable to right click or see any information in the right hand pane?

I'm trying to deploy a batch SD job with about 10 additional files (dll, exe, cab, etc), and on several machines I am getting this error, while on 90% of the other machines it works just fine.

The error in the console is "Package is not supported on this operating system", and this is the SD log file;

Wed, 29 Jun 2011 10:00:28 Checking preferred server path \\<software repo>\software$\apps\DLO\InstallDLO.bat instead of \\<software repo>\software$\apps\DLO\InstallDLO.bat
Wed, 29 Jun 2011 10:00:28 Path \\<software repo>\software$\apps\DLO\InstallDLO.bat was redirected to \\<software repo>\software$\apps\DLO\InstallDLO.bat
Wed, 29 Jun 2011 10:00:28 File (\\<software repo>\software$\apps\DLO\InstallDLO.bat) is not in cache
Wed, 29 Jun 2011 10:00:28 processing of package is complete, result 229392414 (0x0dac401e - code 16414)

Wed, 29 Jun 2011 18:38:01 Sending task status, cmd line -coreandip=<core server>:10.x.x.x -taskid=519 -retcode=229392397 "-ldap=CN=<lastname>\, Gary,OU=Employees,OU=Users,OU=Irvine,DC=<company>,DC=com"
Wed, 29 Jun 2011 18:38:12 File (\\<software repo>\software$\apps\DLO\InstallDLO.bat) is not in cache
Wed, 29 Jun 2011 18:38:17 Downloading file to C:\Program Files (x86)\LANDesk\LDClient\sdmcache\taskmanifest.<core server>.519.124.ini, attempt 0
Wed, 29 Jun 2011 18:38:18 DownloadFile returned 8d860016
Wed, 29 Jun 2011 18:38:18 ..\AdditionalFiles.cpp(65): (8DAC4026): Failed to download file http://LANDesk.Gateway@10.x.x.x/ldlogon/FileLists/taskmanifest.<core server>.519.124.ini : (8D860016)
Wed, 29 Jun 2011 18:38:18 Sending task status, cmd line -coreandip=<core server>:10.x.x.x -taskid=519 -retcode=-1918091226 -complete "-ldap=CN=<lastname>\, Gary,OU=Employees,OU=Users,DC=<company>,DC=com" "-log=sdclient_task519"
Wed, 29 Jun 2011 18:38:21 processing of package is complete, result -1918091226 (0x8dac4026 - code 16422)

The machine doesn't even attempt to download the files, the client appears to be working just fine otherwise.

Any ideas?

I am working with LD support but what I am curious about is after CTOS and the machines boots into Windows how long until the ldprovision fully loads? There is some version of an "agent" loading but they are telling me to build in a 10 minute wait after CTOS and once it boots into Windows.

In system config is wait your first action? If so how long is it?

I have a machine that has agent installed fine, is displaying in the all devices. However i have noticed that the remote agent control status has not been loaded. When i run a scan from the machine itself it seems to work and data has been sent to the core server. When i run a scan from the LDMS server console it fails- cba8, unable to contact the remote agent

when i do a repair job it says straight away- Cannot Find Agent

The agent has been removed and re-installed. Same agent version as other machines.

i have re ran the cba8inst.msi file no issues.

Cant do any repair jobs or scans from the LDMS?!?!?

Any help would be appreciated. **(FYI-im away next week so no reponse until the following week)**

We use the package creator role to enable IT users to create packages. If they copy a package from the public packages the owner stays as public so they cannot modify or delete the package. Is there any thing which can be set so that they do not need to export and import the package?

Recently we applied patch   LD88-Spyware-20722-882v2to our Management Suite 8.8SP2A.

I have a ticket open, but curious if anyone else is experiencing the following issues:

1          Performance issues when doing a security and patch scan. Vulscan.exe now hammers the pc resources and can take up to 30 minutes to complete a scan. Previously it would take about 5 minutes to do a complete scan.   This affects PCs that have real time spyware scanning enabled or disabled on  PCs.

2           V   ulscan.exe 8.80.2.31 is faulting module ceapi.dll 7.1.0.13 on random PCs.

3             Vulscan.exe encounters a problem and needs to close messages on other PCs.

Especially looking for how to take an msi and use LANDesk to publish the application installation via Active Directory Groups or GPO.  There was a video that included the information a few months ago but cannot find it now.  New role being assigned to me to find out how to do this using LANDesk.

Thank you,

Alan

LDMS version 9.50.0.530

Core Server 9.5 SP2

PXE-E53: no boot filename  received   -  when trying to PXE boot to upload a syspreped image in OOBE general mode for provisioning

Prepared the device and OSD as per these instructions:

http://community.landesk.com/support/docs/DOC-23248

BIOS was updated on the image machine before attempting to upload image

Windows PE on the core has the correct drivers for the NIC

I have tried the following:

• Update BIOS on PXE representatives
• Put the PXE rep on the same switch as the PXE booting machine
• Turned the firewall off on the core server, no firewall on the PXE rep, turned antivirus (symantec) off on the PXE rep
• Restarted the PXE services on the PXE reps
• Redeploy the PXE reps
• Recreated the PXE rep and redeployed
• Recreated the OSD capture script with the following command line parameter (LDMS put it in for me, I have no clue):

  RunBatch -1 H:\osd\IMAGEW~1 backall.bat 0 i:\%Computer - Device Name{6}%, STATUS FACILITY=3510, SYNC  

·         Update the entry on the PXE boot menu

• No (WDS) is present on the PXE representative.

Not sure what else to try

I have pushed the agent out to 10 workstations.  3 workstations are complete.   Now I have three that failed Result Code = Unable to contact the specified machine.  The machine may be off or unreachable.  Return Code = 1087.  I have the log file attached.

Then I have 4 workstations that failed with the Result Code = The agent setup succeeded and is now rebooting.  Return Code = 1086.

If someone can tell me where I need to start looking to resolve these and get the agent on them, I would appreciate very much.

Regards

Cathy

Running LANDesk Management Suite 9 with Service Pack 2. I'm attempting to install an executable package on a Windows 7 machine. When I try, the console shows a status of "Failed" and the error message "Sdclient.exe or the installation program was terminated at the client. Return code 1." I have never encountered this error before, and all of my other software packages have installed successfully in the past. To be sure, I also deployed a test package that ran successfully.

All LANDesk services are running under the local system account. The log file shows that all of the required files were downloaded to the client, and there are no indications of errors. Here is the last block of text from the log:

Fri, 20 Apr 2012 09:56:21 6316 6712 Downloading file 614 of 614 from 'http://betty.rf.odu.edu/packages/SageMIP/Support/Scripts/TECleanup/48253_XPsp3_11000_TE_Cleanup.sql'

Fri, 20 Apr 2012 09:56:22 6316 6712 LSWD or Executable Client Thread

Fri, 20 Apr 2012 09:56:22 6316 6712 PackagePath:           [http://betty.rf.odu.edu/packages/SageMIP/setup/Setup.exe]

Fri, 20 Apr 2012 09:56:22 6316 6712 Processing generic executable

Fri, 20 Apr 2012 09:56:22 6316 6712 Launched application 'C:\Program Files\LANDesk\LDClient\sdmcache\packages\SageMIP\setup\Setup.exe' ('/passiveui') result 1

Fri, 20 Apr 2012 09:56:22 6316 6712 Installation result 8DB50001

Fri, 20 Apr 2012 09:56:24 6316 6712 Sending task status, cmd line -coreandip=BETTY.RF.ODU.EDU:10.2.184.18 -taskid=82 -retcode=-1917517823 -complete -pkgid=20

Fri, 20 Apr 2012 09:56:25 6316 6712 processing of package is complete, result -1917517823 (0x8db50001 - code 1)

There are no errors in the event logs for the device, either. I'm stuck. Appreciate any insights!

Anyone successfully get USB 3.0 Host and Hub drivers to inject via HII in a Windows 7 image with the new WinPE 4.0 that came with SP1?

I used to be able to load the host drivers in WinPE 3.0 to allow it to see the hub so HII could detect it was there.  In WinPE 4.0, there are no USB 3.0 drivers for it since its Windows 8 based (at least none that i can find).  I tried using the windows 7 drivers but it errors on loading during WinPE setup script. Using Lenovo devices, FWIW.

I've asked Mr. Google about this, but he hasn't been very helpful. 

I've created my thin base image of Win7 x64 Enterprise and generalize it before capture.  I have steps in the System Configuration phase that set the registry keys for pointing updates to our WSUS server.

I just recently noticed that updates are off after the template has finished.  A simple click of the button will turn them on, but that leaves it up to the technician to ensure that is done.

I went back to my base image vm and the updates are turned on before generalization, but when I generalize the vm, sysprep appears to be turning it off before shutting the vm down for capture.

I am running 9.5 SP2 and am planning on moving to 9.6 soon, but this doesn't seem to be a problem with LD.  Am I missing a reg key that turns them on?  Below are the registry settings that are being made in my template:

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
"WUServer"="http://windowsupdate.WSUSServer.com"
"WUStatusServer"="http://windowsupdate.WSUSServer.com"

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
"AUOptions"="4"
"NoAutoRebootWithLoggedOnUsers"=dword:00000001
"NoAutoUpdate"=dword:00000000
"RescheduleWaitTime"=dword:00000001
"ScheduledInstallDay"=dword:00000000
"ScheduledInstallTime"=dword:0000000c
"UseWUServer"=dword:00000001
"NoAUAsDefaultShutdownOption"=dword:00000001

I am doing an Agent Upgrade after updating from 9.5 SP2 to 9.6. I have reboot turned to never in all settings.

I am creating a reboot task to run independantly tonight between midnight and 2am. I have NOT assigned any devices to the task yet.

As soon as I created the task (NO devices assigned to it yet) I started getting reboot in 12 hours notification and prompts.

I have gone back through the Reboot Settings and the implemented Reboot Policy says Act as if Reboot is Never Needed.

Any thoughts?