Dear All,
Since I've created a batch file with below command:
@echo off
cls
echo Set Default Printer
pushd %~dp0
rundll32 printui.dll,PrintUIEntry /y /q /n "FX ApeosPort-III C5500 PCL 6"
The process result with error code 16386 but the specific printer is set to default successfully!
How to make it be "Succeed" Result???
Please adivse, thanks!
RAY CHAN
Core: LDMS9.0 SP2 SD MSD PATCH 2011-0428 in Windows Server 2003 R2
Hello, I have a .msp file that I need to push to my computers. I know LANDesk does not have a .msp distribution package so does anyone have any suggestions or know of a solution? Thank you.
Has anyone successfully created a Distribution to install UltraEdit 18? I have earlier versions that work OK but we are upgrading to the latest version for new installs and we're having no success at all. We've tried it by extracting the .msi from the .exe wrapper as well as an .exe DPackage. No luckie.
1. The .exe is copied to c:\Program Files\LANDesk\LDClient\SDMCache\Package$ correctly.
2. Task Manager shows the following Processes running:
SDClient.exe
ue_english.exe (UltraEdit executable)
msiexe.exe
policy.client.invoker.exe
3. Just for grins I opened C:\Program Files\LANDesk\LDClient\SDMCache\Package$\UltraEdit18 and manually launched the executable. It installed perfectly.
Any ideas?
Thanks,
Lanell
I have been trying to build a simple msi software distribution package and keep getting an error 1603 "A fatal error occurred during installation".... I have looked on google and the forums on LANDesk support site with no avail... The transform file was created with only change to serial and name of company and to remove any existing versions of acrobat... This is what I have tried so far and that has worked in the past with other msi deployments---
-transform file is in the root of the install UNC path on the software server (\\software1234.domain.abc\packages\adobe\acrobat\10)
-created distribution package as msi and selected the main msi (AcroStan.msi) under the fully qualified UNC path
- the install options I have tried have been as follows
/i /quiet /norestart TRANSFORMS=AcroStan.mst (double checked the name of the mst)
/i TRANSFORMS=AcroStan.mst /qn /n
/i /quiet /norestart (thinking it would automatically pickup the transform file, yes optimistic here)
-the additional files I have included are as follows
AcroStan.mst
Data1.cab
I have also tried adding in all the files and have also tried just the AcroStan.mst
-no other changes in the default settings - system account to install it and have also tried to use a domain admin account to install it
-scheduled task as Policy-Supported push via Standard policy supported push distribution
-started task immediately
-shortly after the deployment (depending on the addtitional files) it fails with the reminence of the transfer of the files for the installation in the sdmcache
-pops up with a 1603 error code "A fatal error occurred during installation"
-I have also tried resetting the hash of the package and redeploying it
-tried moving the install files to a new location on the server
We are running version 9.5 sp1 and I have tried this in the remote management console and on the core. Deploying to Windows 7 all current updates.
Let me know if I am missing anything and any and all help is greatly appreciated as this one has my head spinning!
- Jon
We have the LD agent running on devices that are reboot often, with a login to a default Windows account. I would like the agent to check for policies every time the user logs on (in case the device was reboot in the middle of a package install), so I checked that option under Agent configuration. I set the "max random delay" to 0 hours, which I hope means immediately. However, the agent did not resume an interrupted package download (using a policy-supported push) until after I performed an inventory scan. Can anyone help me with what these options are actually doing? Any tips for best practices to get an agent to check in frequently? Or should I control it from the core and change the task to run on failed devices more frequently? Thank you in advance.
I ran into an issue with a distribution task that had me a bit stumped.
The task was a simple vbscript to perform some custom developed application upgrades. I created a custom vulnerability definition that scanned for a specific file and version on the client computers. I then used the "create query for affected computers" option to establish the target for the software package and set the scheduled time for the task to kick off at a predetermined time.
All the required steps went according to plan except when the task launched at the specified time, every single client reported "the client has initiated an asynchronous policy execution". Then sat there and did nothing. After waiting nearly 45 minutes for the task to execute, I removed all the targets, then manually dropped them back in from the console and relaunched the task. They immediately started downloading and installing the software package and upgraded normally.
So my question is, why did this task do this and how do I prevent it in the future? Many of our software repairs for custom software require us to roll patches within a specified time window and I can't afford to babysit a task every time we need to update it.
We just upgraded to v9.6 from 9.5 SP1 this week. After the upgrade I checked for all the RBA settings, and they appear to be migrated without issues. Everything looks like just how I left it.
Today I discover that when I try to move a task from "My Tasks" folder into a "Team Tasks" folder, it would allow me to drag and drop, but the task doesn't actually get moved and it is still stuck in My Tasks folder.
Things I have checked -
1. I have LANDESK administrator rights
2. I am a member of this Team.
What else am I missing here? Thanks in advance...
After upgrading from 9.0 sp1 to 9.0 sp2 with any Push - Standard Multicast Distrubtion that I create I nor my colleagues cannot view the succesful devices or the All Devices section once 3 machines have entered successful.
It is very odd and I have only seen a similar issue posted in the forum but it discusses an 8.8 to 9.0sp2 migration.
If a colleague of mine creates the scheduled task I can view the successful machines fine, as can everyone else. So it seems to be isolated on me.
Attached are the error messages I see in the Web Console and regular Console.
Console Error:
Web Console Error:
Does anyone have a step by step guide to getting Office 2013 deployed out to computers? Computers are all Windows 7.
Thanks,
Jason
Hi there, we're using MarXtar to wake individual computers up at a time by right clicking them. It works great. Is there a way to wake multiple computers at al time instead of just one at a time? When you highlight multiple computers and right click and select MarXtar it seems to only bring up the first computer from the list of highlighted ones... It would be great if you could wake multiple computers, or even better to wake a folder up... This could easily be done in SCCM, it would be nice to see it with Landesk as well (maybe it can be done, already, and I'm just not doing it right)..
Hi, I'm testing an LD 9 core right now (also with Patch Manager, but that's a side issue to this, really). The vast majority of my machines are behind a Management Gateway and are firewalled, which means that push deployments often are not an option. I use policies and policy supported pushes all the time. Under 8.8 SP3, the feedback I got from policies was decent--sometimes machines wouldn't leave the active state, or wouldn't ever sync a policy down, but for the most part it worked. Under LD9, it's much worse.
5 days ago, I created a policy to install Silverlight on my test group of 27 computers. I know that it was not installed on any of those computers before now. On 5 of the machines, LD9 reported that the installation failed, and gave me a return code of 1514 or 1512 (these return codes don't seem to correspond to anything I've been able to find online). 18 reported "The action completed successfully" with a return code of 0. Good. 2 reported "Successfully completed installation of package" with a return code of 16385 (!). 2 merely say "Policy has been made available" with a return code of 1001.
However, 22 are listed as active, 5 are listed as failed. I've cancelled the running of the scheduled task, and they're still sitting there like that. Wha?
Further, if I run a query on silverlight, all 27 show as having it installed.
Using policies with Patch Manager is even worse. I did a test run yesterday, and I have 1 pending, 4 successful (saying "The client does not support batch file packages"), and 22 failed.
On other tests, I've seen the local policy.sync.log reporting no packages available for multiple checks, while on the core, there's a package, sitting there pending, which clearly has never been run on the client computer.
This is all very frustrating to me. Anyone else seeing this sort of issue, or is my core just special again?
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.
Hi everyone,
We are facing a big challenge at one of our customers with LDMS 9.6. In the past (pre 9.6), when a push task was started and the target couldn’t be reached, the task fails and stay failed. With this behaviour you had a bit of a control that a software distribution runs only out of business hours and didn’t interfere the daily business. Now with 9.6, if the client gets online and the policysync runs, the missed out push task is synched too and starts immediately.
Now you could say ok, I use the maintenance window to exclude business hours for the push tasks, unfortunately this option is only available for patches.
I’d like to know if others are experiencing the same and how you get around this.
I have an idea to run a windows scheduler, that moves the “push client policy” task.XML files to a backup folder at business hours and bring them back out of business hours. That will work but from my point of view there should be a solution in the application.
Any ideas would be much appreciated.
Kind regards
Christian
LD 9.0 sp3, we use LANDesk for patching our servers, and a batch file software distribution task to run the restart of the servers. It used to distribute the batch files (3 files, under 1mb in size) to the servers very quickly, less than 5 minutes to hundreds of servers. Since our desktop team put in preferred servers(desktops) on their side, the batch file software distribution task takes literally 20 minutes to just download the files. It copies them over from the core server, then goes down the list of preferred servers and tries and tries to download the files???
As a work around, I added in a blank preferred.coreserver.dat file to the reboot task, and replace the current file first, so it forces it not to look at the preferred servers.
We are also seeing this issue on the new version as well, 9.6.
The /check parameter is not working anymore in 9.6. Is there another paramater to wait for policies (specially in provisioning templates)?
Thank you for your advices.
Regards,
Kevin
I have created a Enhanced Package Builder package with a couple of DWORD registry settings. I have "built" the package, but when I install the package instead of the values in package, I just have zero's.
Has anyone seen this before, or have any ideas as to what I can do to resolve the issue?
Landesk Push is stuck in Pending, Do you know why would hang the sofware push, I have used the same exact push before. Any suggestion?
Dear All,
As titled,
How to kill the last running task Which is stop processing already in target machine?
The targer machine is rebooted and I've re-deployed the task again to it but the result show "Another installing is in processing"!
How to completely clear the processing task?
pls advise! thanks!
RAY
I'm sure everyone on here has to have adobe packages, and we may have all different ways to make them. I've had to write a quick procedure so anyone in my office can update the package when a new version comes out. I thought I would post this for other to use. If you think it's usefull, let me know and I'll post more as I do them, and maybe other will post theirs. (I'm thinking of making up a template to fill in)... I would be great to have a library of these type of directions..
Erik
D.F. Tehnologies Ltd.
How to package adobe flash and Acrobat reader (Acrobat writer is same directions as reader)
1. Sign up for ‘official rights’ at (takes minutes):
a. http://www.adobe.com/products/players/fpsh_distribution1.html
2. DL the adobe reader and flash (active X) from the links provided in email from adobe
a. For flash DL the MSI
b. For reader you have to DL an exe
3. DL the adobe customizer wizard (for acrobat)
a. http://www.adobe.com/support/downloads/detail.jsp?ftpID=3993
b. Install software and copy reader.exe file to the local machine (Use c:\temp for easy typing)
4. Unpack the reader.exe file
a. Open dos window
b. Cd c:\temp (or where ever you put the file)
c. adbeRdrXXXXX.exe -nos_o"reader9" -nos_ne
d. you should now have c:\temp\reader9 with all the install files
5. Use customizer to open the MSI from above
a. Set your options and press save
6. You can test your reader install manually with the command:
a. msiexec.exe /i AcroRead.msi TRANSFORMS=acroRead.mst /qn
7. Create new distribution packages (MSI) for flash
a. Just pick the MSI you DL’d earlier
8. Create new distribution package (MSI) for reader
a. Pick AcroRead.msi as the main MSI
b. Add extra file acroread.mst
i. NOTE: MST files may not pass your IIS server if using HTTP - add as a mine type
c. Add extra file data1.cab
d. Add ‘TRANSFORMS=acroRead.mst’ after the options on the command line
9. Schedule the template and run
10. Run a patch run after to update Reader to the latest version (if you have security suite)
I ran into an issue with a distribution task that had me a bit stumped.
The task was a simple vbscript to perform some custom developed application upgrades. I created a custom vulnerability definition that scanned for a specific file and version on the client computers. I then used the "create query for affected computers" option to establish the target for the software package and set the scheduled time for the task to kick off at a predetermined time.
All the required steps went according to plan except when the task launched at the specified time, every single client reported "the client has initiated an asynchronous policy execution". Then sat there and did nothing. After waiting nearly 45 minutes for the task to execute, I removed all the targets, then manually dropped them back in from the console and relaunched the task. They immediately started downloading and installing the software package and upgraded normally.
So my question is, why did this task do this and how do I prevent it in the future? Many of our software repairs for custom software require us to roll patches within a specified time window and I can't afford to babysit a task every time we need to update it.