LANDESK Security and Patch News
· (April 8, 2016) Microsoft has released KB3114973 which is an update for Microsoft Project 2016.
Improvements and fixes included in this update.
Fixes the following issues:
After you apply status updates to project schedules, the actual work contours on some assignments unexpectedly display zero for actual work values in various time periods.
When you try to update budget costs on resources in Project 2016, Project 2016 may crash.
When you use an auto filter on a text type field, such as the task name, and the field contains many varied values, Project 2016 may crash.
Assume that you add the compliant field to a view and find something isn't compliant. When you make the item compliant, the field isn't updated until you leave the view and then come back again.
If you have the option to clear leveling values before leveling or you click the Clear Leveling button within the Resource Leveling dialog box, it doesn't always work correctly. Instead, tasks may be leveled to unexpected dates or values may still be found in the Leveling Delay field.
You can't create a project from a SharePoint task list if the list has data validation rules set.
When a resource is overallocated by a combination of actual work and remaining work, the work doesn't appear in red (overallocated) in that period when it's leveled on a day-by-day basis.
Microsoft Project doesn't always calculate the finish dates of some tasks that causes them to finish later than expected. This can occur in a scheduled from finish project where implied dependencies from a summary task to the sub tasks aren't always respected.
Assume that you have a summary task that contains one or more subtasks. Then, you make the summary task become a non-summary task either by outdenting all subtasks or by deleting all subtasks. In this scenario, the internal property on the task that specifies the duration format (minutes, hours, days, weeks, and months) may not be set correctly. Therefore, when you publish the project, the reporting data is inaccurate, and the duration of the given task isn't correct.
When you open a master project that has cross project links, Project 2016 may crash.
When you try to connect to a Project Web App instance in Project 2016 on a computer in which you have not recently connected to the PWA instance, the connection may fail.
When you select multiple tasks and try to replace a resource, the replace action doesn't work if the initial resource that you are replacing isn't assigned to all the selected tasks.
Please visit the following page for more details: https://support2.microsoft.com/kb/3114973
· Vulnerability ID – 3114973_INTL
· Vulnerability ID – 3114393_INTL (Added the replacement information.)
· Vulnerability ID – 3114538_INTL (Added the replacement information.)
· Vulnerability ID – 3114714_INTL (Added the replacement information.)
· Vulnerability ID – 3114865_INTL (Added the replacement information.)
New Patch Downloads
Where to Send Feedback
At LANDESK, we are constantly striving to improve our products and services and hope you find these changes reflective of our ongoing commitment to listen to you—our partners and customers—in providing the best possible solutions to meet your needs now and in the future. Please continue to provide feedback by contacting our local support organization.
LANDESK Product Support
Copyright © 2016 LANDESK Software. All rights reserved. LANDESK is either a registered trademark or trademark of LANDESK Software, Ltd. or its affiliated entities in the United States and/or other countries. Other names or brands may be claimed as the property of others.
Information in this document is provided for information purposes only. The information presented here is subject to change without notice. This information is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including any implied warranties and conditions of merchantability or fitness for a particular purpose. LANDESK disclaims any liability with respect to this document and LANDESK has no responsibility or liability for any third party products of any content contained on any site referenced herein. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. For the most current product information, please visithttp://www.LANDESK.com.