Release Notes for System Center 2012 - Cloud Services Process Pack
Applies To: System Center 2012 - Service Manager, System Center 2012 SP1 - Service Manager
Read these release notes before you install and use the System Center Cloud Services Process Pack software.
Activity Implementer Does Not Have Sufficient Permission
This problem can occur when an activity implementer attempts to assign cloud resources to subscriptions and is only a member of the System Center 2012 – Service Manager Activity Implementers user role. The error message might resemble
User does not have sufficient permission to perform this operation.
WORKAROUND: To fix the issue, add the activity implementer to the Service Manager Administrator user role.
Orchestrator Update SM Activity of the CreateVMMUserRole from SCVMM Runbook Fails
This problem can occur when the Cloud Services runbooks is installed before the System Center 2012 – Service Manager Integration Pack is imported into Orchestrator. The error message might resemble
Failed to get the extension ID. If you see this error, open the SM-CloudServices runbook in the System Center 2012 - Orchestrator runbook designer and view the properties of the Update SM Activity. If you see an error that says
The properties of this activity cannot be viewed The activity may not be installed or was not converted from an Opalis v4 configuration, use the workaround to correct the problem. Reinstalling the Cloud Services runbooks will not fix the problem.
WORKAROUND: To correct the problem, follow these steps in Orchestrator Runbook Designer:
In the CreateVMMUserRole runbook, right-click Update SM Activity and select Delete.
In the Activities pane, click SC 2012 Service Manager, select Update Object and drag the control to the CreateVMMUserRole runbook.
In the CreateVMMUserRole runbook, select Update Object, right-click and select rename. Change the name to “Update SM Activity”.
Set the Update SM Activity as the next task after CreateVMMUserRole.
Select the Update SM Activity task, right-click and select Properties.
Under Details, set the Connection to the desired System Center Service Manager connection.
Set the Class to Runbook Automation Activity.
Set the Object Guid to activityId from “Initialize Data”.
Under the Fields section, set the LongText2 field to jobStatus from “CreateVMMUserRole”.
Cloud Services Process Pack Setup Wizard Fails After Entering the System Center Orchestrator User Account and Database Server
This problem will occur if runbooks has been manually installed.
WORKAROUND: Reinstall System Center 2012 - Orchestrator using the System Center 2012 - Orchestrator Setup Wizzard.
Runbooks are Not Imported
If the user installing System Center 2012 - Orchestrator Runbooks only has datareader permission on Orchestrator database, then installation is successful, however, runbooks are not imported. The user who installs System Center Cloud Services runbooks must be an administrator in the Orchestrator database.
WORKAROUND: Contact your administrator for permissions.
Virtual Machine is Unintentionally Decommissioned
This problem will occur if the decommission date is not manually entered in the Update Virtual Machine request. By default, the Optionally change virtual machine decommission date field in the Update Virtual Machine request is automatically populated with a new decommission date. The date in the Optionally change virtual machine decommission date field will be the submission date + 1.
WORKAROUND: If you do not want to change the decommissioning date to the date displayed in the Optionally change virtual machine decommission date field, make sure that you manually enter an appropriate decommission date in the Optionally change virtual machine decommission date field when submitting an Update Virtual Machine request.
Virtual Machine Decommission Date in the Service Manager console is Displayed as 1 Day Prior to the Date Entered in the Request
This problem may vary depending on your time zone. The Virtual Machine Decommission Date is displayed as 1 day prior to the date that is entered in the Update Virtual Machine request.
WORKAROUND: Submit a change request with a new decommissioning date.
The Storage Cost Value is Not Included in the Cost Per Day Calculation Displayed on the Templates
The Storage Cost value on the Virtual Machine Cost Settings page is not being included in the cost per day calculation that is displayed on templates having a space in their name. As a result, the cost per day is not correctly displayed on the subscribe cloud resources request or request for virtual machine templates. The cost, however, is correct on the reports.
The Cloud Services Cube May Need to be Manually Removed When the Cloud Services Process Pack is Re-installed
The cloud services cube is not automatically removed when the process pack is uninstalled. If the process pack is re-installed, deployment of the "ServiceManager.CloudServices.Cubes.Library" management pack to data warehouse may fail when the management pack Sync job runs. If this happens, the cloud services cube will need to be manually removed from the analysis services database.
WORKAROUND: If this problem affects you, do the following:
Log on to the Data Warehouse database server.
Open Microsoft SQL Server Management Studio.
On the Connect to server page, select Server Type as Analysis Services and Connect.
Open Databases\<DWAS Database name>\Cubes.
Select CloudServicesCube, right-click and select Delete.
Click Ok in Delete Objects window.
Blank Spaces Not Supported in the Virtual Machine Owner User Name
This problem will occur when a Service Manager Self-Service Portal user enters a virtual machine owner name that includes blank spaces when submitting a request to create or update a virtual machine. When this occurs, an error message that says
Enter a vaild domain user or group is displayed.
WORKAROUND: Use the VMM administration console to assign virtual machine owner.
Cloud Resources Subscription Picklist is Not Populated
The picklist is not populated for a user associated with over 500 cloud resources subscriptions.
WORKAROUND: Do not associate the user with more than 500 Cloud Resources Subscriptions.
Migration Error "Invalid Object Name: Global Settings"
The migration wizard displays the error "Invalid Object Name: Global Settings " when there is a database with name DITSC and the database is not an actual VMMSSP 2.0 SP1 database.
WORKAROUND: Verify that the database is an actual VMMSSP2.0 SP1 database.