Installing System Center Virtual Machine Manager (SCVMM) 2012 SP1

1.     Logon to the server using SCVMM Service Account.

2.     Download and install Windows Assessment and Deployment Toolkit (http://www.microsoft.com/en-us/download/details.aspx?id=30652)

3.     Start the installation wizard for SCVMM 2012 SP1.

4.     Under Select Features to install, select both Management Server and Console.

5.     Enter your Username and Organization and input the Product ID(if no product key was typed, SCVMM will go into evaluation mode).

6.     Accept the License Agreement.

7.     Confirm to join or not the Customer Experience Improvement Program (CEIP)

8.     Turn on/off the Microsoft Update

9.     Select default installation location.

10.   Verify Pre-Requisites.

11.   Under Database Configuration, input your SQL Server on Server Name, Port 1433 under Port, your SQL Instance for Instance Name and select New Database – VirtualManagerDB.

12.   Under Configure service account and distributed key management, select Domain Account and input your SCVMM Service Account and its password.

13.   Select default Port Configuration.

14.   Select default Library Configuration.

15.   Verify the Installation Summary and start the installation.

Permissions for System Center Orchestrator runbooks

Okay, here's a good scenario on  System Center Orchestrator. You create a runbook that connects to a remote server. You tried to start/stop a service but it failed or gives you a warning or error. So how do you resolve this issue?

I've tried so many other ways as being told in other sites but the simplest thing worked out for me. 

Add the Orchestrator run as account as local administrator on remote server that the runbook is working with. And whoala, the runbook can now start/stop a service!

If you want to check other permissions required, check it out here.

Free Microsoft Jacket! Join the MCSA Challenge!

Limited edition jacket for those who are taking the MCSA Certfications. See image below for more details. (Upgrade certifications are not accepted; you must take the entire set of exams to qualify)

Visit Microsoft Partners Philippines for more details. 

Officially A Microsoft V-TSP

This is a great day! I'm now officially selected a Microsoft vTSP! I'll be working closely with MSFT with regards to Pre-Sales and Implementation of Hyper-V 2012, WS 2012 and System Center 2012.

So what's a vTSP? I've googled down and found this this phrase from Ryan:

The Microsoft Virtual Technology Specialist Program (VTSP) is a select group chosen from the elite in Microsoft’s partner community, whose focus is to augment Microsoft’s internal Technology Specialist team. Their primary role is to communicate the value of Microsoft Solutions to customers and to provide architectural guidance for Enterprise Integration solutions. The Microsoft VTSP program was designed to create a deeper relationship with Microsoft Partners, the Product Teams at Microsoft Corporate, and Regional Microsoft Offices, in order to provide highly skilled solution specialists to Microsoft customers. It is designed to enable a high performance team of partner-based resources to deliver pre-sale activities and resources to empower customers and help them meet their solution and integration needs.

I'm hoping to learn more from this program and hope to level up more in this industry of Cloud Computing!

SCOM Management Servers Greyed out

I recently found out this morning that my SCOM Server was down and after logging in to my SCOM I see that my management server is greyed out.

Partial fix that worked for me was to fix the error first that says " partitioning and grooming processes for the operational database (OperationsManager) on the server scom, 1433 have either not been run recently or have been failing. At the time this alert was raised, the partitioning and grooming process had not completed for 1 days." Verify the SQL server if there are any errors and the SCOM events. After that let the error resolve on its own. If the management server wont go green, restart the affected SCOM server.

SCSM 2012 Self-Service Portal Access Denied

If you're getting an error from Service Manager 2012 Self Service Portal which looks something like this:

Error: Access Denied

Here's how to resolve the issue:

1. Logout and Sign in as a Sharepoint Administrator.
2. From SCSM 2012 Portal, select Site Permissions (located on Sharepoint Tab).
3. You'll see a warning "This Web site inherits permissions from its parent (Team Site)". Select Manage Parent.
4. Select Grant Permissions.
5. Add the group/users of choice, to give general permissions, add the group Domain Users and make sure to tick/give Read Permissions. 

Basically, after installing Service Manager 2012 Web Parts, the only user that can access the Self-Service Portal is the Sharepoint Administrator. So make sure to add the required users to the list after installing the Web Parts. 

SCSM 2012 Web Part on Windows Server 2012

I've recently encountered one of the strangest flaw on SCSM 2012, and it's installing all of Service Manger 2012 Web Part on Windows Server 2012. 

So let's review the requirements:

• Windows Server 2008 R2 RTM or with SP1
• IIS 7.5 with IIS 6 metabase compatibility installed
• Self-signed SSL certificate
• ASP.NET 2.0
• Microsoft .NET Framework 4.0
• Microsoft Analysis Management Objects
• Microsoft SharePoint Foundation 2010
• Or Microsoft SharePoint Server 2010
• Or Microsoft SharePoint 2010 for Internet Sites Enterprise
• Excel Services in SharePoint 2010 is required for hosting dashboards for advanced analytical reports

So to install Service Manger 2012, you're going to need Sharepoint 2010, may it be Foundation or Server. But note that Sharepoint 2010 only supports up to Windows Server 2008 R2. Even if you have SP1, still it's a no go. And Sharepoint 2013 is not supported by Service Manager 2012. 

So the answer to the question on can we install all of Service Manager 2012 Web Parts on Windows 2012? NO, you cannot install ALL Service Manager Web Parts until an SP2 for Sharepoint 2010 or Service Manager 2012 receives an SP2(that provides support for Sharepoint 2013). What you can do (if you still want to use Windows Server 2012) is to have a separate Sharepoint Server on Windows 2008 R2 and let it host the Sharepoint Web Part.