Enterprise Service Cloud - Docs

Change States

Enter Customer Maintenance

  1. Select the VM in the Swisscom Portal
  2. Under Actions choose Enter Customer Maintenance Mode
  3. Check the progress in the Requests tab

In the vRA Portal you can check the current state in the Properties tab of the VM. The property Scc.Ms.State has the value customerMaintenance.

Return to Full Managed

  1. Select the VM in the Swisscom Portal
  2. Under Actions choose Return to Full Managed
  3. Check the progress in the Requests tab

Request Temp Admin

  1. Select the VM in the Swisscom Portal
  2. Under Actions choose Enter Customer Maintenance
  3. Under Actions choose Request Temp Admin
  4. Define a password for the temporary admin user custadm
  5. Check the progress in the Requests tab

In the vRA Portal you can check the current state in the Properties tab of the VM. The property Scc.Ms.State has the value tempAdmin.

  • For Managed Windows, you then can login via RDP and the custadm user.
  • For Managed RHEL, you then can login with an ssh client and the custadm user. Use the sudo framework for executing commands.

For installing software use this instructions

Return to Full Managed

  1. Select the VM in the Swisscom Portal
  2. Under Actions choose Exit Temp Admin
  3. Under Actions choose Return to Full Managed
  4. Check the progress in the Requests tab

In the vRA Portal you can check the current state in the Properties tab of the VM. The property Scc.Ms.State has the value fullManaged

The Exit Temp Admin action will execute a compliance check.

The compliance checks are a set of checks that check whether changes have been made to the operating system that no longer guarantee a stable operation by Swisscom. For more information about the compliance checks see the Technical Description.

Check the result for the compliance check in the Requests tab of the portal. If a check fails, the customer is responsible for troubleshooting and fixing the issue. Then you can try again to execute the Exit Temp Admin action.

Possible fixes for failed compliance checks for Managed Windows

DescriptionSolution
Compliance Checks failed:
The difference between the last Windows updates should not be more than 45 days		1. Please check that nobody else is logged in. If this is the case, the Software Center will be empty
2. Open the Software Center (Start \ Microsoft Systemcenter \ Software Center)
3. Start the Task P00_All_TAS_WindowsUpdates-Available
4. The Server will reboot itself if needed
5. Try it again to exit the Temp Admin state
Compliance Checks failed:
Local Administrators should have only allowed accounts as member		Remove your added Accounts from the local Group.
In the Managed OS version, only Swisscom has administration authorization on the server
Compliance Checks failed:
Local RemoteDesktopUsers should have only allowed accounts as member
Local DistributedCOMUsers should have only allowed accounts as member
Local PerformanceMonitorUsers should have only allowed accounts as member		Remove your added Accounts from the local Group and authorize them in the Active directory
Compliance Checks failed:
The avarage CPU usage over n seconds should be less than 95 Percent		Change the resource management of your applications or increase the number of CPUs for your instance
Last Updated: