Anyone been able to boot a UEFI enabled device using a PXE rep from LDMS 9.5. I have tried two Dell devices (Latitude 10 Tablet and an Latitude E6430), both timeout when 'Stert with PXE IPv4'

We have about 1500 devices with LD agents. What I notice is that over time, these agents stop reporting back to the core; the last scan dates stretch out for weeks. So as I get ready to push out the new SP1 agents, I'm thinking of adding the Agent Watcher piece to see if I can figure out why.

Does this add any significant overhead to our client machines?

Thanks...

Hello,

We're trying to deployed Lotus Notes 8.5.x which on its own is a standard MSI package and therefore very easy to handle using LDMS.  However, we also want to chain Fix Pack 3 (a standard .exe installation) afterwards.  We want to deploy the two packages together at logon with the option to defer the installation, forcing a reboot when it has all finished.

I have created a new delivery method with the right options which works as I want it - But only with a single package.  When I chain the two packages together, the delivery method kicks in multiple times, i.e. The machine reboots between the two installations and then I get the deferral option page up a second time before the installation of the fix pack - Then there's another reboot!

Is there a way to stop this?  I want the deferral page to appear only at the start of the chain and then only a single reboot after the second installation.

Please help!

Regards,

Stephen.

PS. We're using LDMS 8.8 with SP4

I have upgrade a core from 9.5 with SP1 and I have built a new 9.5 core and install SP1. Both cannot activation online.  I get "Unable to send the activation file to the LANDesk Activation server."

I went to my other 2 core servers that are just 9.5 (no SP1), and reactivated both without issue. Anyone else come accross this?

I am trying to create a new process based off of the Full Incident process. I imported it into our Test system. With the imported process, the Declare Major Incident action works fine. However, when I copy the process, Declare Major Incident stops working. I tried the scripts in one of the other articles for fixing Declare Major Incident when you make a change to that action, but those scripts didn't fix the problem. Any suggestions?

Hi Guys,

I want to create a boolean attribute which will check the attachment and will return "True" if there is an attachment and "False" if there is no attachment. Please suggest me if this can be done by calculations or any other method.

Thanks in Advance.

Srinivas

I have a couple of Bulk Action items that are scheduled to run each night.  That list adds up really quick and the only way I can see to go in and clean up the results is to manually delete one by one.  Is there a script that I could run on the DB to remove these in bulk?

Thanks,

Jamie  7.3.1

.

Anyone been able to boot a UEFI enabled device using a PXE rep from LDMS 9.5. I have tried two Dell devices (Latitude 10 Tablet and an Latitude E6430), both timeout when 'Stert with PXE IPv4'

Greetings,

I have set up ACDSee for deployment but the push job goes to Failed even when the installation is successful.

The ACDSee msi does actually prompt for a reboot after installation but this is halted due to LD using REBOOT=ReallySuppress.

In earlier distributions I have bypassed the 'Failed' status creating a batch script which returns Code 0 instead

of 3010 (ERROR_SUCCESS_REBOOT_ REQUIRED).

However in this case I can't find any msi return code which is related to a reboot required,

would have been great if anyone could have a look at the LD log and clarify why LD returns a Failed status in this case:

Note that in this case ACDSee is successfully installed and the machine is not rebooted,

ACDSee works as it should:

Processing package : ACDSee

Fri, 28 Mar 2008 13:09:00 File (
....\ACDSee for Pentax 2.0.msi) is not in cache

Fri, 28 Mar 2008 13:09:00 MSI Client Thread

Fri, 28 Mar 2008 13:09:00 PackagePath:      http://\\....\ACDSee\ACDSee for Pentax 2.0.msi

Fri, 28 Mar 2008 13:11:11 Installing MSI package

Initializing the MSI package information

Starting the installation of the MSI package

Installing MSI package from '
....\ACDSee\ACDSee for Pentax 2.0.msi' using options 'ALLUSERS=1 COMPANYNAME="xxxx" USERNAME="xxxx" REBOOT=ReallySuppress ALLUSERS=1'

Stating Action : Action 13:09:07: INSTALL.

Stating Action : Action 13:09:07: AppSearch. Searching for installed applications

Stating Action : Action 13:09:07: LaunchConditions. Evaluating launch conditions

Stating Action : Action 13:09:07: WMPVersionCompare.

Stating Action : Action 13:09:08: FindRelatedProducts. Searching for related applications

Stating Action : Action 13:09:08: ValidateProductID.

Stating Action : Action 13:09:08: setUserProfileNT.

Stating Action : Action 13:09:08: setAllUsersProfile2K.

Stating Action : Action 13:09:08: CHECK_REG_KEY.

Stating Action : Action 13:09:08: CostInitialize. Computing space requirements

Stating Action : Action 13:09:08: FileCost. Computing space requirements

Stating Action : Action 13:09:08: IsolateComponents.

Stating Action : Action 13:09:08: SetARPInstallLocation.

Stating Action : Action 13:09:08: CostFinalize. Computing space requirements

Stating Action : Action 13:09:08: SetARPReadme.

Stating Action : Action 13:09:08: SetPageLibraryDirectory.

Stating Action : Action 13:09:08: SetODBCFolders. Initializing ODBC directories

Stating Action : Action 13:09:08: MigrateFeatureStates. Migrating feature states from related applications

Stating Action : Action 13:09:08: InstallValidate. Validating install

Stating Action : Action 13:09:08: SetParentExeProperty.

Stating Action : Action 13:09:08: SetSIPHomeProperty.

Stating Action : Action 13:09:08: RemoveExistingProducts. Removing applications

Stating Action : Action 13:09:08: InstallInitialize.

Stating Action : Action 13:09:09: AllocateRegistrySpace. Allocating registry space

Stating Action : Action 13:09:09: ProcessComponents. Updating component registration

Stating Action : Action 13:09:09: GenerateScript. Generating script operations for action:

Stating Action : Action 13:09:09: UnpublishComponents. Unpublishing Qualified Components

Stating Action : Action 13:09:09: UnpublishFeatures. Unpublishing product features

Stating Action : Action 13:09:09: StopServices. Stopping services

Stating Action : Action 13:09:09: DeleteServices. Deleting services

Stating Action : Action 13:09:09: UnregisterComPlus. Unregistering COM+ Applications and Components

Stating Action : Action 13:09:09: SelfUnregModules. Unregistering modules

Stating Action : Action 13:09:09: UnregisterTypeLibraries. Unregistering type libraries

Stating Action : Action 13:09:09: RemoveODBC. Removing ODBC components

Stating Action : Action 13:09:09: UnregisterFonts. Unregistering fonts

Stating Action : Action 13:09:09: RemoveRegistryValues. Removing system registry values

Stating Action : Action 13:09:09: UnregisterClassInfo. Unregister class servers

Stating Action : Action 13:09:09: UnregisterExtensionInfo. Unregistering extension servers

Stating Action : Action 13:09:09: UnregisterProgIdInfo. Unregistering program identifiers

Stating Action : Action 13:09:09: UnregisterMIMEInfo. Unregistering MIME info

Stating Action : Action 13:09:09: RemoveIniValues. Removing INI file entries

Stating Action : Action 13:09:09: RemoveShortcuts. Removing shortcuts

Stating Action : Action 13:09:09: RemoveEnvironmentStrings. Updating environment strings

Stating Action : Action 13:09:09: RemoveDuplicateFiles. Removing duplicated files

Stating Action : Action 13:09:09: RemoveFiles. Removing files

Stating Action : Action 13:09:09: RemoveFolders. Removing folders

Stating Action : Action 13:09:09: CreateFolders. Creating folders

Stating Action : Action 13:09:09: MoveFiles. Moving files

Stating Action : Action 13:09:09: InstallFiles. Copying new files

Stating Action : Action 13:09:09: InstallPFC.

Stating Action : Action 13:09:09: DuplicateFiles. Creating duplicate files

Stating Action : Action 13:09:09: PatchFiles. Updating files

Stating Action : Action 13:09:09: BindImage. Binding executables

Stating Action : Action 13:09:09: CreateShortcuts. Creating shortcuts

Stating Action : Action 13:09:09: RegisterClassInfo. Registering class servers

Stating Action : Action 13:09:09: RegisterExtensionInfo. Registering extension servers

Stating Action : Action 13:09:09: RegisterProgIdInfo. Registering program identifiers

Stating Action : Action 13:09:09: RegisterMIMEInfo. Registering MIME info

Stating Action : Action 13:09:09: WriteRegistryValues. Writing system registry values

Stating Action : Action 13:09:09: WriteIniValues. Writing INI file values

Stating Action : Action 13:09:09: WriteEnvironmentStrings. Updating environment strings

Stating Action : Action 13:09:09: RegisterFonts. Registering fonts

Stating Action : Action 13:09:09: InstallODBC. Installing ODBC components

Stating Action : Action 13:09:09: RegisterTypeLibraries. Registering type libraries

Stating Action : Action 13:09:09: RegisterComPlus. Registering COM+ Applications and Components

Stating Action : Action 13:09:09: InstallServices. Installing new services

Stating Action : Action 13:09:09: StartServices. Starting services

Stating Action : Action 13:09:09: SelfRegModules. Registering modules

Stating Action : Action 13:09:09: RegisterUser. Registering user

Stating Action : Action 13:09:09: RegisterProduct. Registering product

Stating Action : Action 13:09:10: PublishComponents. Publishing qualified components

Stating Action : Action 13:09:10: PublishFeatures. Publishing product features

Stating Action : Action 13:09:10: PublishProduct. Publishing product information

Stating Action : Action 13:09:10: ScheduleReboot.

Stating Action : Action 13:09:10: RegisterACDEncodeQT.

Stating Action : Action 13:09:10: registerACDEncodeRM.

Stating Action : Action 13:09:10: RegisterACDFX.ax.

Stating Action : Action 13:09:10: registerACDWaterMark.

Stating Action : Action 13:09:10: ACDRegInstaller.

Stating Action : Action 13:09:10: SetSTXProperty.

Stating Action : Action 13:09:10: SetFileAssociation.dll.

Stating Action : Action 13:09:11: DBUpgrade603. Upgrading existing database

Stating Action : Action 13:09:11: InstallFinalize.

Stating Action : Action 13:09:11: ProcessComponents. Updating component registration

Stating Action : Action 13:09:11: RemoveODBC. Removing ODBC components

Stating Action : Action 13:09:11: CreateFolders. Creating folders

Stating Action : Action 13:09:12: InstallFiles. Copying new files

Stating Action : Action 13:10:59: CreateShortcuts. Creating shortcuts

Stating Action : Action 13:11:00: RegisterClassInfo. Registering class servers

Stating Action : Action 13:11:00: RegisterProgIdInfo. Registering program identifiers

Stating Action : Action 13:11:00: WriteRegistryValues. Writing system registry values

Stating Action : Action 13:11:00: RegisterTypeLibraries. Registering type libraries

Stating Action : Action 13:11:00: RegisterUser. Registering user

Stating Action : Action 13:11:00: RegisterProduct. Registering product

Stating Action : Action 13:11:01: PublishFeatures. Publishing product features

Stating Action : Action 13:11:01: PublishProduct. Publishing product information

Stating Action : Action 13:11:03: RegisterACDEncodeQT.

Stating Action : Action 13:11:04: registerACDEncodeRM.

Stating Action : Action 13:11:04: RegisterACDFX.ax.

Stating Action : Action 13:11:05: registerACDWaterMark.

Stating Action : Action 13:11:05: DBUpgrade603. Upgrading existing database

Stating Action : Action 13:11:05: RollbackCleanup. Removing backup files

Stating Action : Action 13:11:05: SetFileAssociations.

Stating Action : Action 13:11:10: AutorunDevDetect.

Failed to install the MSI package.

Installing MSI package (-127 seconds)

Installation of the MSI package failed

Fri, 28 Mar 2008 13:11:11 MSI result 8DAC4002

Fri, 28 Mar 2008 13:11:11 processing of package is complete, result -1918091262 (0x8dac4002 - code 16386)

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

HI All

I'm having another problem with a simple calculation in a pre-condition:

import System
static def GetAttributeValue(Request):
Value = 'False'
for item in Request.Tasks:
  if item.Category.Title == 'Build Task' and item.Status.Title == 'Completed':
   Value = 'True'
return Value

I use this precondition to setup mulitple parallel and seiral tasks.  However, when this pre-condition is used after several add tasks and when the other tasks are completed, then I get an unusal error where the following automatic action add task after the pre-condition suddenly becomes an action instead.

Once I remove the calcultion condition then everything flows ok so I'm assuming it's the calculation that's causing my issues.

I'm looking to configure WEB emulation in Wavelink TE on a batch of Motorola MC3190s but am getting unusual results when trying to navigate to any web page. Upon connecting it is returning a File Download dialogue box asking whether I want to run the program from its location or save it to disk. If I press ok on either option I get an error message saying there is no application associated with the file.

I've tried this both on my destination website and also a couple of test websites (Google, BBC) but always get the same result, it tries to download a file with the same name as the website.

Any ideas? I can't see anything obvious in the emulation parameters.

Greetings,

I have set up ACDSee for deployment but the push job goes to Failed even when the installation is successful.

The ACDSee msi does actually prompt for a reboot after installation but this is halted due to LD using REBOOT=ReallySuppress.

In earlier distributions I have bypassed the 'Failed' status creating a batch script which returns Code 0 instead

of 3010 (ERROR_SUCCESS_REBOOT_ REQUIRED).

However in this case I can't find any msi return code which is related to a reboot required,

would have been great if anyone could have a look at the LD log and clarify why LD returns a Failed status in this case:

Note that in this case ACDSee is successfully installed and the machine is not rebooted,

ACDSee works as it should:

Processing package : ACDSee

Fri, 28 Mar 2008 13:09:00 File (
....\ACDSee for Pentax 2.0.msi) is not in cache

Fri, 28 Mar 2008 13:09:00 MSI Client Thread

Fri, 28 Mar 2008 13:09:00 PackagePath:      http://\\....\ACDSee\ACDSee for Pentax 2.0.msi

Fri, 28 Mar 2008 13:11:11 Installing MSI package

Initializing the MSI package information

Starting the installation of the MSI package

Installing MSI package from '
....\ACDSee\ACDSee for Pentax 2.0.msi' using options 'ALLUSERS=1 COMPANYNAME="xxxx" USERNAME="xxxx" REBOOT=ReallySuppress ALLUSERS=1'

Stating Action : Action 13:09:07: INSTALL.

Stating Action : Action 13:09:07: AppSearch. Searching for installed applications

Stating Action : Action 13:09:07: LaunchConditions. Evaluating launch conditions

Stating Action : Action 13:09:07: WMPVersionCompare.

Stating Action : Action 13:09:08: FindRelatedProducts. Searching for related applications

Stating Action : Action 13:09:08: ValidateProductID.

Stating Action : Action 13:09:08: setUserProfileNT.

Stating Action : Action 13:09:08: setAllUsersProfile2K.

Stating Action : Action 13:09:08: CHECK_REG_KEY.

Stating Action : Action 13:09:08: CostInitialize. Computing space requirements

Stating Action : Action 13:09:08: FileCost. Computing space requirements

Stating Action : Action 13:09:08: IsolateComponents.

Stating Action : Action 13:09:08: SetARPInstallLocation.

Stating Action : Action 13:09:08: CostFinalize. Computing space requirements

Stating Action : Action 13:09:08: SetARPReadme.

Stating Action : Action 13:09:08: SetPageLibraryDirectory.

Stating Action : Action 13:09:08: SetODBCFolders. Initializing ODBC directories

Stating Action : Action 13:09:08: MigrateFeatureStates. Migrating feature states from related applications

Stating Action : Action 13:09:08: InstallValidate. Validating install

Stating Action : Action 13:09:08: SetParentExeProperty.

Stating Action : Action 13:09:08: SetSIPHomeProperty.

Stating Action : Action 13:09:08: RemoveExistingProducts. Removing applications

Stating Action : Action 13:09:08: InstallInitialize.

Stating Action : Action 13:09:09: AllocateRegistrySpace. Allocating registry space

Stating Action : Action 13:09:09: ProcessComponents. Updating component registration

Stating Action : Action 13:09:09: GenerateScript. Generating script operations for action:

Stating Action : Action 13:09:09: UnpublishComponents. Unpublishing Qualified Components

Stating Action : Action 13:09:09: UnpublishFeatures. Unpublishing product features

Stating Action : Action 13:09:09: StopServices. Stopping services

Stating Action : Action 13:09:09: DeleteServices. Deleting services

Stating Action : Action 13:09:09: UnregisterComPlus. Unregistering COM+ Applications and Components

Stating Action : Action 13:09:09: SelfUnregModules. Unregistering modules

Stating Action : Action 13:09:09: UnregisterTypeLibraries. Unregistering type libraries

Stating Action : Action 13:09:09: RemoveODBC. Removing ODBC components

Stating Action : Action 13:09:09: UnregisterFonts. Unregistering fonts

Stating Action : Action 13:09:09: RemoveRegistryValues. Removing system registry values

Stating Action : Action 13:09:09: UnregisterClassInfo. Unregister class servers

Stating Action : Action 13:09:09: UnregisterExtensionInfo. Unregistering extension servers

Stating Action : Action 13:09:09: UnregisterProgIdInfo. Unregistering program identifiers

Stating Action : Action 13:09:09: UnregisterMIMEInfo. Unregistering MIME info

Stating Action : Action 13:09:09: RemoveIniValues. Removing INI file entries

Stating Action : Action 13:09:09: RemoveShortcuts. Removing shortcuts

Stating Action : Action 13:09:09: RemoveEnvironmentStrings. Updating environment strings

Stating Action : Action 13:09:09: RemoveDuplicateFiles. Removing duplicated files

Stating Action : Action 13:09:09: RemoveFiles. Removing files

Stating Action : Action 13:09:09: RemoveFolders. Removing folders

Stating Action : Action 13:09:09: CreateFolders. Creating folders

Stating Action : Action 13:09:09: MoveFiles. Moving files

Stating Action : Action 13:09:09: InstallFiles. Copying new files

Stating Action : Action 13:09:09: InstallPFC.

Stating Action : Action 13:09:09: DuplicateFiles. Creating duplicate files

Stating Action : Action 13:09:09: PatchFiles. Updating files

Stating Action : Action 13:09:09: BindImage. Binding executables

Stating Action : Action 13:09:09: CreateShortcuts. Creating shortcuts

Stating Action : Action 13:09:09: RegisterClassInfo. Registering class servers

Stating Action : Action 13:09:09: RegisterExtensionInfo. Registering extension servers

Stating Action : Action 13:09:09: RegisterProgIdInfo. Registering program identifiers

Stating Action : Action 13:09:09: RegisterMIMEInfo. Registering MIME info

Stating Action : Action 13:09:09: WriteRegistryValues. Writing system registry values

Stating Action : Action 13:09:09: WriteIniValues. Writing INI file values

Stating Action : Action 13:09:09: WriteEnvironmentStrings. Updating environment strings

Stating Action : Action 13:09:09: RegisterFonts. Registering fonts

Stating Action : Action 13:09:09: InstallODBC. Installing ODBC components

Stating Action : Action 13:09:09: RegisterTypeLibraries. Registering type libraries

Stating Action : Action 13:09:09: RegisterComPlus. Registering COM+ Applications and Components

Stating Action : Action 13:09:09: InstallServices. Installing new services

Stating Action : Action 13:09:09: StartServices. Starting services

Stating Action : Action 13:09:09: SelfRegModules. Registering modules

Stating Action : Action 13:09:09: RegisterUser. Registering user

Stating Action : Action 13:09:09: RegisterProduct. Registering product

Stating Action : Action 13:09:10: PublishComponents. Publishing qualified components

Stating Action : Action 13:09:10: PublishFeatures. Publishing product features

Stating Action : Action 13:09:10: PublishProduct. Publishing product information

Stating Action : Action 13:09:10: ScheduleReboot.

Stating Action : Action 13:09:10: RegisterACDEncodeQT.

Stating Action : Action 13:09:10: registerACDEncodeRM.

Stating Action : Action 13:09:10: RegisterACDFX.ax.

Stating Action : Action 13:09:10: registerACDWaterMark.

Stating Action : Action 13:09:10: ACDRegInstaller.

Stating Action : Action 13:09:10: SetSTXProperty.

Stating Action : Action 13:09:10: SetFileAssociation.dll.

Stating Action : Action 13:09:11: DBUpgrade603. Upgrading existing database

Stating Action : Action 13:09:11: InstallFinalize.

Stating Action : Action 13:09:11: ProcessComponents. Updating component registration

Stating Action : Action 13:09:11: RemoveODBC. Removing ODBC components

Stating Action : Action 13:09:11: CreateFolders. Creating folders

Stating Action : Action 13:09:12: InstallFiles. Copying new files

Stating Action : Action 13:10:59: CreateShortcuts. Creating shortcuts

Stating Action : Action 13:11:00: RegisterClassInfo. Registering class servers

Stating Action : Action 13:11:00: RegisterProgIdInfo. Registering program identifiers

Stating Action : Action 13:11:00: WriteRegistryValues. Writing system registry values

Stating Action : Action 13:11:00: RegisterTypeLibraries. Registering type libraries

Stating Action : Action 13:11:00: RegisterUser. Registering user

Stating Action : Action 13:11:00: RegisterProduct. Registering product

Stating Action : Action 13:11:01: PublishFeatures. Publishing product features

Stating Action : Action 13:11:01: PublishProduct. Publishing product information

Stating Action : Action 13:11:03: RegisterACDEncodeQT.

Stating Action : Action 13:11:04: registerACDEncodeRM.

Stating Action : Action 13:11:04: RegisterACDFX.ax.

Stating Action : Action 13:11:05: registerACDWaterMark.

Stating Action : Action 13:11:05: DBUpgrade603. Upgrading existing database

Stating Action : Action 13:11:05: RollbackCleanup. Removing backup files

Stating Action : Action 13:11:05: SetFileAssociations.

Stating Action : Action 13:11:10: AutorunDevDetect.

Failed to install the MSI package.

Installing MSI package (-127 seconds)

Installation of the MSI package failed

Fri, 28 Mar 2008 13:11:11 MSI result 8DAC4002

Fri, 28 Mar 2008 13:11:11 processing of package is complete, result -1918091262 (0x8dac4002 - code 16386)

I'm finding that creating a new stand alone agent after my 9.5 core has been SP1'ed does not work on Windows 7 or Windows XP.  Based on the install logs, looks like its the install is failing on ClientSideEnableWOL.vbs.  Before SP1 this usually meant that something was broken with WMI

How ever in my case these are fresh plain vanilla iamges in both cases( win7 & win XP).  WMI is functioning fine when checked.

My work around for now is to install the old 9.5( no sp1) stand alone file.  After that's done, run the SP1 Agent update and every thing works flawlessly

Any one else seeing this?

Need to normalize devices with the same serial number within Asset Control; however, each duplicate has pertinent information which needs to be merged into one record.  Any ideas.  DTS....I know.  But an example would be great.

We currently use the Add Assigment action for our Analysts, I have been asked to create another version of the Add Assignment, the only difference being that the Analysts can only assign the Incident to a group and not an individual Analyst. so the ANalyst has two options add assignment and escalation.

On the face of it I need two different windows but not sure if I can assign the same process to each and it seems to create and new action I need to create the entire object so a new object for Escalation that is identical to the Assignment object. (tried to do this I can't replicate the assignment object simply can't locate all the collections)

Is there a way to copy Assignment and rename it Escalation? bit lost there must be a simpler way!!

Any Ideas welcome.

Anyone been able to boot a UEFI enabled device using a PXE rep from LDMS 9.5. I have tried two Dell devices (Latitude 10 Tablet and an Latitude E6430), both timeout when 'Stert with PXE IPv4'

I am using a template to provisiona device and I am having issues only with the HII Action:

When I add the Action item I set the Action Properties as in the image:

If I apply, and close and then go into the HII Action item again the properties disappear as follows:

and some drivers actually fail to load during the Provisioning task on the device.

If I recheck the option and immediately schedule the task all drivers install correctly.  The strange part is that the HII Action does not really fail in the status, the drivers just don't install properly.

I'm using 9.0 SP3.

Anyone ever see this?

-   Jim

I have been asked to look at the wording that is emailed to the assignee when the add assignment task is used to assign an Incident to another analyst.

Currently if notify assignee is ticked the assignee recieves a plain text email that shows the Detail field from the add assignment window for both the subject line and body of the email.

I need to add by default at least the Incidnet number and set the Title field as the subject and leave the description as the body. however I can not find how where this email is generated in the system, what is defining the content of the emails sent for the add assignement task?

Thanks,