Release Notes for the Authoring Tool in System Center 2012 - Service Manager
Updated: May 13, 2016
Applies To: System Center 2012 SP1 - Service Manager, System Center 2012 R2 Service Manager, System Center 2012 - Service Manager
Read these release notes before you install the System Center 2012 – Service Manager Authoring Tool.
Authoring Tool Prerequisite Check Might Fail for Microsoft Visual Studio Shell 2008
When you install the Visual Studio 2008 Shell Isolated Mode Redistributable Package using the link in Authoring tool Setup, it might not install the package completely. This can result in prerequisite check failure.
WORKAROUND: Perform the following steps.
Download and run AppEnvRedist.exe using the link in Setup, which extracts its contents to <InstallationDrive>:\VS 2008 Shell Redist\Isolated Mode\.
In this folder, double click VS_Shell_isolated.enu.exe to install Microsoft Visual Studio Shell 2008.
After the installation completes, the prerequisite will pass.
Authoring Tool Setup Might Fail Due to Missing Files
For System Center 2012 and System Center 2012 SP1 versions, the Service Manager Authoring Tool Setup might fail due to it missing files such as msvcr100.dll.
WORKAROUND: Download and install the Microsoft Visual C++ 2010 SP1 Redistributable Package (x86) on the computer where you are trying to install the Authoring Tool. Afterward, try installing the Authoring Tool again.
Upgrading to the RTM version of System Center 2012 – Service Manager Authoring Tool
The version of the Authoring Tool that you run must always match the version of Service Manager. If you are running the Release to Manufacturing (RTM) version of System Center 2012 – Service Manager, you must use the RTM version of the System Center 2012 – Service Manager Authoring Tool.
The Authoring Tool does not support a direct upgrade. Therefore, if you are using the RTM version of System Center 2012 – Service Manager, uninstall any older versions of the tool and then install the RTM version of the System Center 2012 – Service Manager Authoring Tool.
For more information, see the Authoring Guide for System Center 2012 - Service Manager.
Localized Versions of the Authoring Tool
All localized versions of the System Center 2012 – Service Manager Authoring Tool are named SCSM_AuthoringTool_2012.exe. Ensure that you download and install the version of the tool for the language of your choice.
PowerShell Tasks Created with the Authoring Tool Do Not Work Properly
When you use the Service Manager SP1 version of the Authoring tool to create a workflow, then custom scripts called by the workflow fail. This is due to a problem in the Service Manager MonitoringHost.exe.config file.
WORKAROUND: To work around this problem, update the MonitoringHost.exe.config XML file using the following steps.
Navigate to %ProgramFiles%\Microsoft System Center 2012\Service Manager\ or the location where you installed Service Manager.
Edit the MonitoringHost.exe.config file and add the section in italic type from the example below in the corresponding section of your file. You must insert the section before <publisherPolicy apply="yes" />.
Save your changes to the file.
Restart the System Center Management service on the Service Manager management server.
For System Center 2012 R2 Service Manager, the System Center Management service was renamed to Microsoft Monitoring Agent.
<?xml version="1.0"?> <configuration> <configSections> <section name="uri" type="System.Configuration.UriSection, System, Version=22.214.171.124, Culture=neutral, PublicKeyToken=b77a5c561934e089" /> </configSections> <uri> <iriParsing enabled="true" /> </uri> <runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="Microsoft.Mom.Modules.DataTypes" publicKeyToken="31bf3856ad364e35" /> <publisherPolicy apply="no" /> <bindingRedirect oldVersion="6.0.4900.0" newVersion="7.0.5000.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="Microsoft.EnterpriseManagement.HealthService.Modules.WorkflowFoundation" publicKeyToken="31bf3856ad364e35" /> <publisherPolicy apply="no" /> <bindingRedirect oldVersion="6.0.4900.0" newVersion="7.0.5000.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="Microsoft.EnterpriseManagement.Modules.PowerShell" publicKeyToken="31bf3856ad364e35" /> <bindingRedirect oldVersion="6.0.4900.0" newVersion="7.0.5000.0" /> </dependentAssembly> <publisherPolicy apply="yes" /> <probing privatePath="" /> </assemblyBinding> <gcConcurrent enabled="true" /> </runtime> </configuration>
The Authoring Tool Does Not Automatically Adjust After You Change the Language of the Operating System
If you install the Authoring Tool and then change the language that the operating system uses on the computer, the Authoring Tool may not work correctly. The Authoring Tool is not supported in this situation.
WORKAROUND: Before you install the Authoring Tool, ensure that the language that the operating system uses on the computer is the correct language. Or, before you change the language of the operating system, if the Authoring Tool is already installed, do the following:
Uninstall the Authoring Tool.
Uninstall the Microsoft Visual Studio 2008 Shell.
Change the language of the operating system.
Reinstall the Authoring Tool.
Some Default Forms Are Not Supported for Customizations
The following default forms are not supported for customizations:
The problem form
The user form
The service map form
The knowledge form
Binding Fails If a Property Name Contains a Period
If a class is extended with a property name that contains a period, binding that property to a custom control fails.
WORKAROUND: For extended properties, do not use a period in the property name.
Extended Properties of the Decimal Type Cannot Be Used in a View Criterion
A view that is defined with a criterion that is based on an extended property of the decimal type is not saved correctly and cannot be used.
A Decimal Value for an Extended Property Is Not Saved Correctly
If you extend a class with a decimal property and bind a form control to the extended property, a decimal value in that control is truncated when it is saved. For example, the number 1.23 is saved as 1.
Workflows That Are Created with Previous Versions of the Authoring Tool Might Need Rebuilding
The Active Directory Name property of the Add AD DS Computer To Group activity has been renamed to Computer Domain. In addition, the internal name of the same property has been renamed from ADServer to ComputerDomain for consistency. This can prevent workflows that are authored with the previous version of the Authoring Tool that use the Add AD DS Computer To Group activity from working with the latest version.
WORKAROUND: Rebuild workflows containing the Add AD DS Computer To Group activity with the latest version of the Authoring Tool.
When You Add the IfElse Activity to a Workflow, You Cannot Use Some Properties in the IfElse Condition
When you attempt to set a condition for the IfElse activity, the Rule Condition Editor dialog box might not display the correct set of available workflow activities. This is due to a refresh issue.
WORKAROUND: Save the respective management pack before you open the Rule Condition Editor dialog box.
Release Notes Copyright Information
This document is provided "as-is". Information and views expressed in this document, including URL and other Internet website references, may change without notice.
Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred.
This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. You may modify this document for your internal, reference purposes.
© 2012 Microsoft Corporation. All rights reserved.
Microsoft, ActiveX, Active Directory, Bing, Internet Explorer, MSDN, SharePoint, Silverlight, SQL Server, Visual Basic, Visual Studio, Windows, Microsoft Intune, Windows PowerShell, Windows Server, and Windows Vista are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners.