Enterprise Solutions
Financial Management should not be left to the later stages
of implementing an ITIL framework. An early start on Financial
Management can help any organization, large or small get
an early lead on this complex undertaking
All of the texts on the subject and most of consultants
will tell you implementing ITIL should be undertaken in
bite size chunks with clear goals, objectives and key performance
indicators to measure progress.
Mile stone reviews are the norm with implicit understanding
that the next or dependent process should not be undertaken
until core processes are established and rock solid.
That’s the theory. But business is rarely this neat
and tidy. In practice, those companies that excel often
do so by virtue of their flexibility, their ability to adapt
to changing circumstances and improvise.
This is why early consideration of Financial Management
is recommended for the benefits it provides on business
planning, budget and accounting.
Financial Management for IT Services is one of the key,
if not key, processes that fall under the IT Service Delivery
umbrella. Unless we know how much service support is going
to cost, it is impossible to calculate the overall financial
imperatives for the business or put in place an appropriate
Service Level Management structure.
Financial management is first and foremost sound stewardship
of the financial resources of the organization in the planning
and execution of business objectives. It is not sufficient
to say we are doing the best with available resources. In
today’s climate, many companies are using extensive
financial analysis to first of all determine whether that
is true and secondly, whether it can be improved upon.
The common wisdom is that incident, problem and change
should be implemented first - - and usually in this order.
These are customarily followed in the implementation schedule
by configuration and release management as it is assumed
the organization will have reached sufficient maturity by
the time these two processes are implemented.
Very frequently the importance of Service Level Management
and Financial Management is glossed over. However, much
of the work associated with implementing financial management
process can be carried out quietly and carefully with no
impact to the organization.
Every company is different with different business needs
and demands. ITIL implementations need to be scoped entirely
in line with the business not a theoretical model.
Therefore, among the questions we must ask are::
• Is the business providing sufficient funds
to the services it requires?
• Have we costed those services appropriately?
• Have we looked at all the sourcing possibilities?
• Do we have the right business model? Are we
thinking cost center when really we should be thinking profit
center?
• If we change the costing paradigm how does
that affect the business model?
Until we know how much we can afford, it is impossible
to successfully develop a full fledged Service Level Management
process along with Service Level and Operating Level Agreements.
There are three core activities involved in Financial Management:
BAC
Budgeting - allowing the organization
to predict the spend rate and ensuring the Actual to be
in line with predicted
Accounting - for the tracking of the
dollars spent, while calculating cost of ownership and CB/ROI
analysis
Charging - for the recovery of costs from
each of the business units
Greater financial understanding can have can have profound
impacts on the organization. In particular, the break down
of the cost of IT services into service specific components
to specifically associate costs with specific individual
services and departments can provide immense value.
Financial Management works hand in hand with the other
IT processes and the Service Desk function. However, as
noted above, it has particular impact in four areas: Service
Level Management, Capacity and Configuration Management
and the Service Desk function.
Financial Management can have great impact on the way that
Service Level Management is structured through its ability
to create different charging mechanisms. IT Charging really
comes into its own when the SLA, OLA and under pinning contracts
are flexible and customers can determine their own level
of need - as determined by the business. Similarly with
capacity management, cost information can be used calculate
the costs of the system.
LANDesk and FrontRange’s suite of CRM products provide
a range of historical and reporting capabilities that support
these processes. LANDesk’s detailed asset information
can validate the accountability of IT Services Spending
while discovery and monitoring capabilities can help track
usage of applications and infrastructure.
Much of this information can be gatewayed into FrontRange
and assets assigned at an individual customer level with
roll up financial reporting for Business Intelligence.
Financial Management is an important building block in
the development and growth of IT services, providing strategic,
tactical and operational direction. Businesses are increasingly
likely to rely on its input as they evaluate the development
of IT.
Back To Top
PRODUCT: LANDesk(R) Software, Version 8.5
SP RELEASE: 2
DATE: October, 2005
This readme describes issues addressed in the LANDesk Software
8.5 Service Pack 2.
-----------------------------------------------------------------------------
EXCEPT AS RESTRICTED BY LAW, THE SOFTWARE PROGRAMS CONTAINED
IN THE FILE ARE PROVIDED "AS IS" WITHOUT WARRANTY
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT
NOT LIMITED TO, ANY IMPLIED WARRANTIES OF MERCHANTABILITY,
TITLE OR FITNESS FOR A PARTICULAR PURPOSE.
-----------------------------------------------------------------------------
------------------------------
USING THIS README
------------------------------
This readme contains important information about the SP2
patch. It's divided into the following sections.
* Installation procedure
* Issues resolved by this patch
Make sure you at least read the "Installation procedure"
section. You must follow the steps there to apply the service
pack successfully in your environment.
------------------------------
INSTALLATION PROCEDURE
------------------------------
You need to install this service pack on all core servers,
additional consoles, web console servers, and managed devices.
The easiest way to update managed devices with the service
pack is to use the Security and Patch manager tool.
We recommend that you back up your core server and databases
before applying this service pack.
*** On the CORE SERVER ***
1. Extract Setup.exe from the patch and run it.
NOTE 1: The status column for the patch update program
may pause for a moment while updating large files. This
is expected behavior, and progress will continue automatically
as soon as these large files finish updating.
NOTE 2: The percentage indicator updates on a per component
basis. Depending upon the number of components installed
on the core server, the status can potentially update up
to ten times for the patch.
NOTE 3: There will be an InstallShield* window on the task
bar that will show it is uninstalling during the patch install.
The necessary components will be re-installed later in the
patch installation.
2. When Setup finishes, reboot the core server.
3. Login to the core server after the reboot. This will
insure that coredbutil.exe will build the components necessary
for the patch to work. This may take several minutes on
larger databases. CoreDBUtil may cause the task manager
to report that its process is "Not Responding".
However, if you view the process list, the CoreDbUtil.exe
program will be consuming cycles. Please allow it to finish.
4. After the core server reboots, we recommend that you
reactivate the core server.
NOTE: If the Asset Manager add on product is installed
after installing SP2, or other components are added to the
core installation, the SP2 patch will need to be re-installed.
*** For all ADDITIONAL (REMOTE) MANAGEMENT CONSOLES not
physically located on the core server ***
1. Extract Setup.exe from the patch and run it on the additional
console.
2. When Setup finishes, reboot.
*** On all WEB CONSOLE WEB SERVERS not physically located
on the core server***
1. Extract Setup.exe from the patch and run it on the web
console server.
2. When Setup finishes, reboot.
NOTE: Regardless of how you install the patch, step 3 needs
to be performed manually.
3. In the Windows Component Services application, follow
the steps below to create a "LANDesk RBA" COM+
Application and add the LANDesk.ManagementSuite.Information.dll.
a. In the Windows Control Panel, open Administrative Tools
and double-click Component Services.
b. Within Component Services, go to Component Services >
Computers > My Computer > COM+ Applications.
c. Click COM+ Applications. From its shortcut menu, click
New > Application. The Welcome to the COM+ Application
Install Wizard will launch.
d. Click Next.
e. Click "Create an Empty Application".
f. Type "LANDesk RBA" as the name for the application
(Server application should be selected in the type list),
then click Next.
g. On the "Set Application Identity" page, click
"This user" and enter the credentials of a domain
user.
h. On the "Add Application Roles" page, click
Next.
i. On the "Add Users to Roles" page, click Next.
j. Click Finish.
k. In the COM+ Applications tree, select the "LANDesk
RBA" application. From its shortcut menu, click Properties.
l. Click the Security tab.
m. Make sure that the "Enforce access checks for this
application" check box is NOT checked.
n. Click Apply.
o. Click OK.
p. Expand the "LANDesk RBA" application. From
the Components tree item's shortcut menu, click New | Component.
q. Click Next.
r. Click the Import Components button.
s. In the list, select "LANDesk.ManagementSuite.Information.UserInformation".
t. Click Next.
u. Click Finish.
v. Close the Component Services application.
w. Reboot the server when finished.
*** On CLIENTS ***
a. Use the Security and Patch Manager tool to automate the
client update.
-or-
b. Use the Scheduled Tasks window to "push" a
client configuration to client computers.
-or-
c. Launch WSCFG32.EXE on selected client computers.
*** On SERVER MANAGER CLIENTS ***
a. Use the Scheduled Tasks window to "push" a
client configuration to client computers.
-or-
b. Launch SERVERCONFIG.EXE on selected client computers.
NOTE 1: If you are installing the server agent, the computer
will need to be rebooted for all of the monitoring information
to be available. The "Reboot if necessary" option
should be chosen if you can immediately reboot the server.
If the option is chosen to not reboot, the product will
not function properly until the server is rebooted.
NOTE 2: If you are using custom Linux agent configurations,
these will need to be rebuilt in the Agent Configuration
tool.
*** ON COMPUTERS WITH ASIC OR IPMI ***
If you have deployed 8.5 shipping agents to ASIC or IPMI
enabled computers, you must uninstall the original agent
and reboot the computer before the SP2 agents can be deployed.
This is because a legacy system driver is being updated
during the install. In order to update the legacy system
driver, the OS requires a reboot.
This can be accomplished in one of two ways:
1. Use a custom script to deploy a job to the ASIC or IPMI
servers. This job should
a. Run UninstallWinClient.exe found in the \LANDesk\ManagementSuite
directory
b. Perform a reboot.
c. Push the new agent.
2. Push the new agent to the server. The job will indicate
failure on ASIC and IPMI computers. This is because the
legacy driver has been marked for removal but will not be
removed until a reboot occurs. Reboot the servers indicated
in the job log and then redeploy the agent to only those
servers that were rebooted.
*** On SYSTEM MANAGER FOR CLIENT systems ***
a. If you have previously installed this add-on product,
you should uninstall it through the Add / Remove programs
and then re-install the latest release that can be downloaded
from http://kb.landesk.com.
NOTE: If the System Manager for Clients add-on product
is installed after installing SP2, the SP2 patch will need
to be re-installed.
*** On ROLLUP CORES ***
1. Extract Setup.exe from the patch and run it.
2. When Setup finishes, reboot the rollup core server.
3. Read the rollup documentation in the folder root that
you extracted the patch to. The documentation is in Adobe
Acrobat* format, and is called "Using the rollup.pdf".
------------------------------
ISSUES RELATED TO THIS PATCH
------------------------------
If you install LANDesk System Manager to a core server that
you just patched with LANDesk Software SP2, the System Manager
administrator console may hang if it is launched from the
Management Suite console. If this happens, reboot the core
server. You should only have to do this once.
------------------------------
ISSUES RESOLVED BY THIS PATCH
------------------------------
DATABASE
------------------------------
CR58118 -- Increased the size of the OrigFileName field
to be 255.
CR59138 -- Resetting the OSD options in the Configure Services
utility was not working correctly.
CR61181 -- LDAP queries were not resolving in scheduled
tasks.
CR62790 -- There could be an error when removing a Server
Manager client from the device view.
------------------------------
Fixed in previous SP release
------------------------------
CR49723 -- The inventory scanner was reporting different
versions of files with the same size as the same version.
CR57818 -- Fixed the remote control error - "remote
computer is not in your scope" when using certificate-based
security and a non-default scope.
CR57935 -- The APM service on the core server could stop
processing client requests.
CR58551 -- PXE pre-targeting was not working properly.
CR59049 -- Speed up the performance of database rollups.
CR59515 -- Fixed a situation where remote consoles could
not be logged into.
CR59910 -- Some queries, when used as a column set, could
time out. Added the ability to configure this through the
registry.
CR61261 -- There was a scenario where you could not download
new content for Patch Management.
CR61940 -- Increased the field length for CDROMDrivers.
CR62229 -- Increased the size of the FULLNAME column in
the COMPUTER table.
INVENTORY
------------------------------
CR35563 -- The AIX inventory scanner was not reporting the
processor speed correctly.
CR46278 -- The PDA section was not being created during
an inventory scan.
CR60420 -- Running inventory for Linux computers with Hyper
Threading turned on would report the number of processors
incorrectly.
CR60760 -- The inventory scanner was not collecting the
last start time from Windows XP computers.
CR62632 -- There could be a conflict regarding the files
to deny on a client with application blocking and software
monitoring.
CR63208 -- Fixed a problem in reporting the complete operating
system name.
CR63791 -- Enhancement: Put in registry keys to configure
the Max Connect Tries and Seconds Before Retry options.
CR65710 -- Fixed a decompression problem that would report
"Invalid scan sent from remote machine."
CR67098 -- The inventory scanner could pick up extra characters
when scanning the registry for a specific key.
CR67621 -- The inventory scanner would not pick up workgroup
names with double byte characters.
CR67783 -- The keyboard layout was always reported as English
in the inventory view.
CR70103 -- x64 systems would report an error during an inventory
scan when it attempted to call Inv16.exe.
CR71037 -- The inventory scanner was not reporting the workgroup
name when a power user was running the scanner.
CR71163 -- Fixed a compatibility issue with Compaq Deskpro*
EN clients running Windows NT 4 SP6a with a LTR-48126S CDRW
drive.
CR72288 -- The AIX inventory scanner was not always generating
a unique device ID.
CR72476 -- The remote control status in inventory was not
always correct.
CR72820 -- The Inventory scanner could gather the wrong
data for the primary owner of a computer.
CR73009 -- The Inventory scanner was not handling service
display names over 200 characters.
CR73078 -- The /nocd switch was not preventing deletion/addition
of custom data to the scan file.
------------------------------
Fixed in previous SP release
------------------------------
CR49723 -- The inventory scanner was reporting different
versions of files with the same size as the same version.
CR53292 -- Inventory history was not recording changes correctly.
CR56112 -- We were having errors when starting the inventory
service.
CR56381 -- The 'Application Delete' alert notification was
firing twice when an application was deleted.
CR57912 -- Persistent custom data could be deleted by a
full scan.
CR58457 -- Network adapters that were removed from the computer
were still detected because the drivers were left behind.
CR58466 -- Some remote control inventory information was
being removed when a delta scan was inserted.
CR58595 -- Certain characters in the version field could
cause a file to not be denied properly.
CR58906 -- NetWare* scans were not being inserted into the
database correctly.
CR59210 -- Database maintenance was removing all computers
without MAC Addresses from the Computers section every time
it ran.
CR60013 -- Client computers could use 99% of the CPU when
the inventory scanner was running.
CR60896 -- Inventory scanner would abend Compaq* servers
running NetWare* 8.5.
CR60974 -- Delta scans during first 12 days of month were
being rejected on Oracle* databases.
CR61483 -- Old custom data was not being removed from the
database.
CR61581 -- Duplicate device removal was not working when
the MAC address was used in the detection logic.
CR61621 -- The inventory tree was not displaying NICs that
were disabled.
CONSOLE
----------------------------
CR52217 -- The "Last Used" column was being sorted
as a string instead of as a date.
CR57318 -- Computers with Japanese characters in the filename
would not display correctly when a unmanaged device discovery
was performed. This will only work if the core and client
computer are both double-byte languages.
CR58922 -- Duplicate items could be inserted in the ldappl3.ini.
CR59342 -- Queries that were exported could not be imported
on another server.
CR59621 -- Running an agent distribution as a scheduled
task could fail with the error: "Failed, task handler
exception."
CR59700 -- UDD would not scan some IP ranges correctly.
CR60675 -- Report users had rights to the Handheld File
Exchange.
CR61201 -- Added a way to add or remove the /user parameter
to tasks that may run on a server OS.
CR61796 -- There were some cases where the Ldappl3.ini would
not import properly.
CR62296 -- The find function was not working properly in
Spanish.
CR63089 -- The members of the Remote Control Operators group
were not updating when a client update was scheduled.
CR63361 -- The "Removed spyware by date" report
would show all of the recorded dates regardless of the date
you were trying to report on.
CR63803 -- If a product is deleted from one application
group, the license information was also deleted from the
other groupings.
CR63823 -- Enhanced the performance of software license
monitoring.
CR64311 -- Fixed a problem with queries returning results
when a particular sort order was used.
CR64593 -- The qualifier would disappear if a query was
copied and pasted.
CR65326 -- Running with an Inventory Only license would
leave the custom data form options grayed out.
CR65503 -- LDAP reports below the top level OU were not
working properly.
CR66414 -- Task completion was trying to execute failed
multicast jobs. Task completion is not allowed when a multicast
job fails.
CR66906 -- When creating a CSV report there could be an
extra field with the Computer ID in it.
CR67002 -- The title window did not display correctly in
French.
CR67283 -- The insert button on the query dialog could change
to update but it would still act like insert.
CR68393 -- The OS Version was not filled out when displaying
scope computers.
CR68908 -- Running an automatic refresh of an LDAP query
would not work in APM if all the members were removed from
the group.
CR68980 -- The computer name is not displayed in the title
of the inventory screen after adding a string value.
CR68988 -- Duration and Days since last used columns would
not sort properly.
CR69044 -- Trying to delete more that 1000 nodes at the
same time from an Oracle database could cause the nodes
to not be deleted from the database.
CR69103 -- A console user without rights could access the
Agent configuration window.
CR69241 -- The time filter was not getting added to the
local scheduler task when a vulnerability scan was created.
CR69622 -- Some reports were not filtering the report based
on the groups.
CR71451 -- The local scheduler command line was missing
the space before /ipaddr.
CR71629 -- You could not use an "_" in a custom
inventory name.
CR71705 -- The remote control security type was being overwritten
when rebuilding all client deployment packages.
CR71959 -- When selecting "On IPAddr change" in
the software distribution options, a separate task was not
being created.
CR72136 -- The login OK Button was not displaying correctly
in French.
CR72324 -- You could not manually add double bytes strings
into the inventory data.
CR72381 -- You could not configure alerts when logging in
using the FQDN of the core server.
CR73001 -- Fixed a problem with installing the remote control
mirror driver with the run as command.
------------------------------
Fixed in previous SP release
------------------------------
CR45542 -- Fixed a misspelling in the Configure Services
utility.
CR50116 -- The find query dialog in the custom Crystal*
Reports was not showing existing queries.
CR50139 -- Enhancement: added a registry key to configure
strings to help identify printers in the OS description
CR54179 -- The decimal point was missing when exporting
the "Available Hard Drive Space" to a csv file.
CR54634 -- The report window was not opening when there
were large amounts of log files on the Core Server.
CR55710 -- There was a situation where the Ldappl3.ldz file
was not getting compressed properly.
CR56496 -- Moving files from "To be Excluded"
to "To be Scanned" could cause them to be deleted.
CR56767 -- When switching core servers without closing the
console, some of the data from the old core was still in
the cache.
CR57239 -- Fixed a problem where the selected nodes were
not reporting correctly.
CR57454 -- Deleting an LDMS user could generate a constraint
error and the user would not be deleted.
CR57465 -- Fixed a memory leak in the Inventory Summary
window.
CR57475 -- The status bar was not displaying the count of
selected computers in the Unmanaged Device Discovery window.
CR57564 -- Custom Data was not being inserted by the inventory
service even though it was included in the scan.
CR57617 -- The domain information was not populating when
trying to add users to the Remote Control Operators group
for Remote Control NT/local template.
CR57744 -- Fixed an upgrade condition where you could be
unable to create queries.
CR57798 -- Fixed a case where some SLM data would not import
properly.
CR57821 -- LDAP-based scopes with multiple containers was
not working properly.
CR57950 -- Local Scheduler Scripts created in 8.5 insert
the quote command in the wrong location.
CR58037 -- Unmanaged devices were not displaying in the
agent configuration tasks when the administrator had a custom
scope
CR58211 -- Added the ability to configure the ldappl3.ini
with an inventory only license.
CR58224 -- Fixed the XML license import.
CR58416 -- Unable to configure SLM-based scopes in the Inventory-only
solution.
CR58703 -- Asset reports were showing all computers instead
of the selected computers in the Network view.
CR58747 -- Database maintenance was not removing all of
the old computers from the database.
CR59046 -- Fixed the COM+ error that was listed in the event
log when the Web console was being used.
CR59144 -- Users with software distribution rights could
not remove multicast domain representatives.
CR59242 -- An Inventory Only license needed to include agent
configuration.
CR59322 -- Saving the "Default Configuration"
was not updating the configured on date in the NTSTACFG.INI
file.
CR59863 -- Unmanaged devices were not displaying in the
agent configuration tasks when the administrator had a custom
scope
CR59886 -- Fixed a server error in the DotNetReports application.
CR59911 -- With an Inventory only license, you could not
schedule a UDD scan.
CR60235 -- Query conditions could be truncated when the
query was too long.
CR60349 -- Fixed a connection error to the inventory database.
CR60675 -- Report users had rights to Handheld File Exchange.
CR61170 -- Queries were stripping out the directory paths,
causing the query to be saved incorrectly.
CR61643 -- The console was sorting some dates as strings
instead of by the actual date.
CR61658 -- A nested group in the LANDesk Management Suite
group would not authenticate properly.
CR61867 -- Consoles that were using the UK date format were
displaying the US format.
CR62115 -- Synchronized the inventory cache with the inventory
service.
CR62336 -- The client path was not always in the inventory
for a client computer.
CORE
----------------------------
CR45547 -- Fixed the remote control blank remote screen
option. It wasn't blanking the remote screen reliably.
CR59745 -- Enhancement: Removed the miniscan from PDS and
put it into its own application.
CR59789 -- Uninstalling the client using the uninstallwinclient.exe
from an 8.5 core server could remove files that were still
needed.
CR62336 -- The client path was not always in the inventory
for a client computer.
CR62721 -- Device Monitor was not reporting changes in a
computers status.
CR63072 -- Some items could be left in the LANDesk Management
group on an upgrade from an 8.1 client.
CR64462 -- There could be an NTVDM error when attempting
to push an agent to a Windows 9x computer.
CR64895 -- Some of the Linux inventory information was not
displayed correctly.
CR68105 -- Reinstalling the client on a core server would
cause the alertqueueservice.exe to be uninstalled.
CR68597 -- Added better status reporting on Macintosh client
deployments.
CR70266 -- You could not configure duplicate Device ID detection
on Spanish core servers after installing SP1.
------------------------------
Fixed in previous SP release
------------------------------
CR50420 -- Selecting the Wake on LAN option when deploying
would shut down a client, even if it was already on.
CR56490 -- Logging into the OS with a domain user and using
a remote console would not show the correct agent status.
CR57523 -- Uninstallwinclient.exe was not allowing a reboot
without user intervention.
CR57615 -- Stopping the Web service during an upgrade stops
the Application Policies from being upgraded.
CR57656 -- Device monitoring alerts were not working with
the 'monitor on time' option.
CR57814 -- The client computers could stay in an active
state when pushing the agent.
CR57841 -- Client configuration was rebooting the computer
before the MSI package had finished installing.
CR57846 -- Scheduling a inventory scan to a Macintosh* 9
client would not execute the scan.
CR57973 -- Custom Data is being removed from the database
after running agent configuration.
CR58141 -- Some XXstacfg.ini settings were overridden when
using a client package.
CR58160 -- You could not deploy a client to a NetWare* server
without manually copying files into the LDLOGON folder.
CR58908 -- Full scans were being forced when an Administrative
user logged in after a normal user.
CR58921 -- The timeout for Client Configuration in Service
configuration was not remembering the changes.
CR59686 -- Clients would sometimes fail to report status
back from clients running application policies.
CR59912 -- Wscfg32 would not handle multiple sets of quotation
marks in a REG# command in the ini file.
CR60166 -- The software distribution portal Web link was
not removed by UninstallWinClient.exe.
CR61641 -- The registry entry for Softmon was not being
updated when upgrading older client computers.
CR61690 -- Client configuration was not removing old local
scheduler tasks when upgrading a client from 8.1 GA2.
CR63219 -- The c:\ldclient directory could be left behind
when performing an upgrade.
CLIENT
----------------------------
CR48280 -- Fixed a compatibility problem with another software
program.
CR57345 -- Blocked applications were displaying a warning
dialog when they were not supposed to.
CR58088 -- Sdclient could abort if a security scan was currently
running.
CR58920 -- Windows 98 computers were not shutting down properly
if they were not connected to the network.
CR60552 -- The software distribution portal buttons were
missing the text when run on a Norwegian client.
CR61226 -- Policies were being re-applied when a different
regional setting was used.
CR62051 -- Enhancement: Made it so that the Preferred Package
Server would be used even when the bandwidth options were
disabled.
CR62304 -- Softmon.exe was causing Symantec Antivirus Tamper
Protection to fire alerts.
CR63360 -- Unable to deploy a package in the software distribution
portal using an LDAP Query for an individual user.
CR63713 -- Pushing a package could cause the Targeted Multicast
Service on the client to crash.
CR64764 -- A task could not run on the client if custjob
was set to use UDP detection only.
CR66836 -- Amclient.exe could hang when trying to process
a policy.
CR67113 -- Running a compliance report on a rollup core
could fail due to an integer value for a field being exceeded.
CR67286 -- Remote control language files were not installed
on Windows 9x.
CR67619 -- Enhancement: Removed the miniscan from PDS and
put it into its own application.
CR67938 -- All policies were being reapplied after upgrading
a client from 6.62 to 8.5 SP1.
CR68217 -- Policies with dependencies were not applied when
a non-admin user logged into a client.
CR69916 -- Packages with dependencies were not getting delayed
properly.
CR69983 -- Updated to the latest versions of CBA and PDS.
CR71817 -- Multiple delayed packages were not always being
installed properly.
CR71818 -- Fixed a problem where a reboot was required after
installing the first MSI package and another one needed
to install.
CR71958 -- Software distribution of MSI packages was populating
the install-uninstall registry values with local paths causing
uninstalls of MSIs to fail.
CR72465 -- SWD packages with multiple cascading dependencies
get redeployed when they are already installed.
CR73631 -- Policy packages were being redeployed after changing
the delivery method's properties.
------------------------------
Fixed in previous SP release
------------------------------
CR57086 -- Application Policy status would not update for
domain users without local admin rights.
CR57152 -- Pulling a package that has a dependent package
could cause targeted computers to stay in the active queue.
CR57441 -- When scheduling a Local scheduler task in the
past, the task would run immediately.
CR57531 -- In the Web portal, once a package was allowed
with a policy, it was always allowed.
CR57684 -- APM could fail due to a client-side time out
or heavy network traffic.
CR57708 -- SDclient was not always using the file in the
sdmcache to install a Multicast package.
CR57946 -- APM policies with dependencies or additional
files would not change status from "active" to
"successful" upon completion.
CR58088 -- Sdclient could abort if a security scan was currently
running.
CR58290 -- You could not download a custom data form if
the user had locked down permissions on the system.
CR58901 -- Bandwidth detection would fail on certain RAS
clients.
CR59439 -- Users could not write to the LDCustom.dat file
with default folder permissions.
CR61226 -- All policies were being re-applied when a user
with a different regional setting language logged in.
CR61790 -- Sdclient.exe could take over 1 hour to close
when network connectivity is lost at the core server.
REMOTE CONTROL
----------------------------
CR60801 -- Some clients with double-byte characters in the
computer name could not be remote controlled.
CR62792 -- There was a scenario where the system tray icon
would not display properly.
CR63119 -- Enhancement: Put the 8.6 keyboard mapping feature
into 8.5.
CR63858 -- In certain languages you could have 2 IME toolbars
show up on the desktop.
CR66438 -- The local computer administrators group was always
added to the remote control operators group.
CR67246 -- The on demand agent cleanup code would remove
extra files.
CR68021 -- Some applications were losing focus during a
silent agent install.
CR70209 -- Remote control shift keys would get stuck when
typing in a command window.
CR71393 -- You could not file transfer from a core to a
Mac OS X client.
CR71602 -- The remote control history report was showing
the username in the wrong column.
CR72478 -- The remote control agent status was not always
returned correctly.
CR72543 -- You could not remote control certain clients
when the screen saver was active.
CR72548 -- Locking and unlocking a Windows NT 4 client during
a session causes the computer to slow down.
CR73582 -- Transfering a file with Japanese characters in
the filename would fail with an error (-43) on Mac OSX.
------------------------------
Fixed in previous SP release
------------------------------
CR57348 -- Remote control would only display the primary
screen on multi-monitor systems.
CR57608 -- The LANDesk Remote Control Service could stop
on computer after ending a remote control session with it.
CR57671 -- Fixed a wallpaper suppression problem where customers
were using a different shell program.
CR57700 -- Fixed a co-existence problem with the LANDesk
Remote Control agent and the LANDesk Instant Support Suite
agent.
CR57746 -- Fixed a co-existence problem with the LANDesk
Remote Control Viewer and the LANDesk Instant Support Suite
console.
CR57795 -- Windows 9x clients that have been configured
with NT security were prompting for credentials.
CR57875 -- Macintosh OS 9 systems with a space in the name
could not be remote controlled.
CR58070 -- The certificate based RC was not asking for permission
when the permission required flag was set.
CR58549 -- Fixed a scenario where you could not remote control
clients when manually running the viewer.
CR58887 -- Permission required dialog message was incorrect
on an Italian client.
CR58918 -- Certificate-based remote control of a Windows
9x computer could cause an endless loop.
CR59513 -- The ldmirror.dll driver could cause Microsoft
Office* applications to fail.
CR60101 -- The Web console was not opening the correct viewer
for Macintosh clients.
CR60562 -- Remote Controlling Windows Server 2003 with SP1
would cause a blue screen.
CR60699 -- A restricted user could stop the remote control
session by ending the task in the Task Manager.
CR61062 -- Added an option to not suppress the shell animation
effects.
CR62063 -- Remote control could fail to connect to an client
that had not been upgraded.
DISTRIBUTION
----------------------------
CR59891 -- Policy-supported push tasks were not changing
to a policy after a push failure.
CR60313 -- Deploying Macintosh packages with a command line
did not call the sub-install program correctly.
CR62250 -- Having the Software Distribution right would
allow you to delete tasks that were not associated with
Software Distribution.
CR63209 -- MSI packages that used a transform with a space
in the name would fail to distribute.
CR68034 -- The console could crash when creating a distribution
package with software that contained default Web pages.
CR68056 -- Package deployment to multiple Macintosh computers
would fail on the second computer.
CR69115 -- Software distribution jobs were not reporting
correctly when they failed on a Macintosh client.
CR69245 -- Dependant uninstall packages were not uninstalled
during a push.
------------------------------
Fixed in previous SP release
------------------------------
CR57640 -- Scheduled tasks could stay in a pending state.
CR57753 -- Fixed a memory leak when looking at distribution
package properties.
CR58284 -- Fixed a rights issue with administrative tasks.
CR58753 -- Fixed a memory leak in the "Software Distribution
Properties" window.
CR59720 -- Software Distribution was not handling some MSI
switches.
CR60874 -- Updated the UI to clarify what happens when you
reschedule an agent configuration task.
CR60924 -- Canceling a Multicast could cause some clients
to go to the package server to get the package.
CR61286 -- Allowed the LAN and WAN packet timing to be adjustable
up to 2000 ms.
SCHEDULER
----------------------------
CR68064 -- APM targets could not be updated because SchedQry.exe
was keeping them from running.
CR72314 -- Restarting a policy-based task by clicking "Start
now" reschedules the task for all targeted computers.
------------------------------
Fixed in previous SP release
------------------------------
CR51280 -- Fixed a memory leak in the scheduler service
when APM policies were being processed.
CR58270 -- The APM Service would use up all of the non-paged
pool memory.
CR60697 -- There was a scenario when you were unable to
successfully cancel out of a scheduled task.
WEB CONSOLE
----------------------------
CR61177 -- Some reports in the Web console were not working
properly.
CR63454 -- The scope on the Web console was not loading
the language properly causing some computers to be removed
from the scope.
CR71603 -- A "Could Not Overwrite" error could
occur when attempting to distribute a script.
------------------------------
Fixed in previous SP release
------------------------------
CR46360 -- Unable to log into the Web console across domains.
CR55033 -- Some queries would display incorrect results
when executed.
CR56514 -- The dates were not displayed correctly for scheduled
tasks when European regional settings were used.
CR57547 -- If custom data included a "." in its
name, the Web console would fail to expand the inventory
tree.
CR57868 -- The certificate-based remote control was not
functioning properly when using the find function in the
Web console.
CR58026 -- The remote control screen in expert mode was
blank.
CR58071 -- Wildcard searches in the Web console were not
returning results.
CR58382 -- Users in nested groups would not see all of the
available options.
CR58835 -- The remote control viewer was being downloaded
every time you attempted to use it.
CR60004 -- Fixed a memory leak in the Web console custom
scripts.
CR60494 -- The /hash parameter was not being places in the
Web console software distribution scripts.
CR61177 -- Some reports in the Web console were not working
properly.
CR62330 -- The attributes to display were not fitting in
the window.
SHARED TECH
----------------------------
CR63222 -- Symantec: XFR and/or HNDLRSVC service crash on
service restarts on Windows 2003.
CR64020 -- IAO crashes after install of Symantec.
CR65338 -- UDD was returning a MAC address of 0000000000.
CR72114 -- Remote control would fail if the only client
that was installed was the NetWare client.
------------------------------
Fixed in previous SP release
------------------------------
CR60208 -- Multicast domain representatives were not waking
up devices as specified.
CR61476 -- The scheduler service account could be locked
out during an agent push.
OSD
----------------------------
CR63076 -- Cisco 7902 Series IP Phones send CDP packets
that would crash the LANDesk PXE service.
CR65540 -- Network drives that were being accessed would
not be removed after deploying a sysprep'd image.
CR66274 -- Some sysprep'd images would continue to log in
the administrator automatically.
CR66867 -- Increased the string length that TokRepl.exe
could handle.
CR72585 -- Enhancement: Added the ability to OSD to send
a WOL packet via the Multicast Domain Representative.
CR73108 -- Computers with MSIEXEC 3.x would not restore
profiles that worked with MSIEXEC 2.
------------------------------
Fixed in previous SP release
------------------------------
CR51727 -- Changed OSD scripts to not allow a dash "-"
in the name because they would not execute properly.
CR57638 -- When using a boot floppy the computer would fail
to boot properly.
CR57915 -- Enhancement: Custom PXE Boot Menu options are
now static.
CR61216 -- The newer version of Sysprep for Windows* XP
and 2003 was not working when using a template sysprep.inf
file
MACINTOSH
----------------------------
CR63275 -- The Italian permission required message was incorrect
on the Mac OS X client.
CR64014 -- Client pushes could fail to a Mac OS X client.
CR68072 -- The remote control logging was not working on
the Macintosh OSX client.
CR71057 -- Enhancement: Added the ability to track Macintosh
OS server licenses.
CR71168 -- Mac OS X clients don't generate new ID's when
they were deemed duplicates
CR71212 -- Clients were not reporting their Network - AppleTalk
- Zone information
CR71331 -- The newest Macintosh iBook hardware was not reported
in inventory.
------------------------------
Fixed in previous SP release
------------------------------
CR57566 -- You could not push an update to a Mac OS 9 client.
CR57567 -- You could not push an update to a Mac OS X client.
CR57888 -- Software distribution to multiple targets will
fail due to commands not running in SYNC mode.
PACKAGE BUIDLER
----------------------
CR65380 -- Fixed some truncated text in the Package Builder
UI.
------------------------------
Fixed in previous SP release
------------------------------
CR32896 -- Package Builder could save a file that contained
incorrect syntax.
CR57323 -- The "If Search" function in Package
Builder would improperly skip lines containing the specified
characters.
CR59438 -- Inst32.exe could use all of the available CPU
when using the "Run At Exit" option.
CR61578 -- You could not use the $RIGHT$ variable in a single
package more than once.
CR62078 -- Inst32.exe could use all of the available CPU.
PATCH MANAGER
----------------------------
CR64310 -- Fixed Patch Manager to support multiple Microsoft
Office versions.
CR65568 -- Enhancement: changed vulscan to add an option
to install patches using specific credentials.
CR65904 -- Fixed the download logic to not throw an exception
when comparing a non-null checksum value to a null one.
CR68193 -- Speed up the comparison times when downloading
new content.
CR68786 -- Enhancement: Added zip logic to files sent to
the clients.
CR69393 -- Vulscan was trying to execute msiexec.exe in
the system32 directory on Windows 98 computers.
------------------------------
Fixed in previous SP release
------------------------------
CR53808 -- Vulscan.exe would stay in the RunOnce key if
the user did not have sufficient rights to remove it from
the registry.
CR56243 -- Translated the Deny File Properties window.
CR56744 -- Vulscan would detect patched vulnerabilities
on Windows 2000 clients that had the multi-language pack
installed.
CR57076 -- The Blocked Application report was consuming
all of the available memory.
CR57164 -- On Linux, the rule name was not sent to the core
if the patch name was blank.
CR57701 -- Using the snooze option with no user intervention
would not reboot the system.
CR58076 -- Some installed patches were not showing up in
the Security and Patch Information dialog.
CR58516 -- An alert would not fire when downloading vulnerabilities
within a scheduled task.
CR59992 -- Vulscan was failing to correctly scan a core
server during a reboot after vulnerabilities had been applied.
ASSET MANAGER
----------------------
CR68225 -- You could not add some asset types in German.
CR71065 -- Quotes were being added to the default values
when they were saved.
CR71437 -- Using an apostrophe in the notes section of an
SLM license would cause Asset Manager to not move that license.
CR72815 -- CSV files created by Excel were not able to be
imported properly.
------------------------------
Fixed in previous SP release
------------------------------
CR55755 -- Added the ability to correctly add some French-named
assets.
CR56849 -- Data that was imported from a CSV file was not
being overwritten by linked data.
CR58059 -- Asset Manager was not correctly converting the
Italian regional format.
CR58111 -- Asset Manager tables were getting corrupted when
a new field was added into the Computer - Service History
section.
CR58162 -- After defining associations of contracts, invoices
etc. with a computer, The "Computers and associated
items" report fails.
CONNECTION CONTROL MANAGER
----------------------
CR66842 -- Connection control manager would not always block
devices correctly.
CR68450 -- Some USB mice were blocked even when connection
control manager was set to allow USB mice.
CR69253 -- Connection control manager blocks the serial
port when the parallel port is selected to be blocked.
------------------------------
Fixed in previous SP release
------------------------------
CR58209 -- Disabling removable devices would also disable
the USB, Com1, Com2, and LPT ports.
CR61183 -- Connection Control Manager would block keyboards
that had a built-in USB hub.
SERVER MANAGER
----------------------
CR63256 -- The Web-based remote control reports would not
run properly.
CR67555 -- The local scheduler task for inventory has a
/user switch so it would not scan unless a user was logged
into the server.
CR68087 -- We were only putting down the English version
of defaultserver.in#.
CR69697 -- The application log date was off by one day.
------------------------------
Fixed in previous SP release
------------------------------
CR61280 -- You could not create a "Custom Remediation
Script" in the French Server Manager.
CR59592 -- Enhanced the refresh of the server list.
CR57969 -- Fixed a memory leak in pfcntrs.exe on server
manager clients.
ROLLUP CORE
----------------------
CR68740 -- Fixed rolling up roll-up servers.
CR71819 -- Fixed a collation error during roll-up.
CR73194 -- Fixed a collation error during roll-up.
------------------------------
Fixed in previous SP release
------------------------------
CR56912 -- Speed up the performance of database rollups.
Please refer to the "Using the rollup.pdf" in
the root folder of the patch.
HANDHELD MANAGER
----------------------
CR58609 -- The software inventory could report the wrong
vendor.
CR58618 -- The scanner was reporting the memory size incorrectly.
CR58626 -- The software inventory could report the wrong
screen resolution.
CR61048 -- The WinCE agent could stop running unexpectedly.
CR61050 -- WinCE devices were not sending inventory unless
they were connected between 12:00 and 13:00.
*Other names and brands may be claimed as the property
of others.
LANDesk retains the right to make changes to this document
or related product specifications and descriptions at any
time, without notice. LANDesk makes no warranty for the
use of this document and assume no responsibility for any
errors that can appear in the document nor does it make
a commitment to update the information contained herein.
Back To Top
