These days I´m implementing a SCOM 2012 R2 on a environement where I have one OMS, one Reporting server and a two node sql 2012 SP1 failover cluster.
The problem that I have been experiencing is when I was installing reporting services (SSRS) in the dedicated server for that porpouse. The error showed in installation log OpsMgrSetupWizard.log was:
Info: :Could not connect to Management Server: OperationsManagerServer with exception: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
[15:43:35]: Info: :StackTrace: at System.Version.TryParseVersion(String version, VersionResult& result)
at System.Version..ctor(String version)
at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupHelpers.IsManagementServerCurrentVersion(String managementServer)
In the wizard I saw the message: Unable to connect to the Data Access service for this management server. Ensure the Data Access service is running and that the service, the management group, and setup are all the same version.
I solved it adding data writter account, data access account and sdk account to a gpo that allow for these accounts log on locally in the Operations Manager servers.
Below I put the PLA link for IAAS. I hope it help you!
In a joint effort between Microsoft product development and Microsoft Services, the Infrastructure-as-a-Service (IaaS) Product
Line Architecture (PLA) has been created to help organizations develop and implement private cloud infrastructures quickly while reducing complexity and risk. The IaaS PLA utilizes the core capabilities of the Windows Server operating system, Hyper-V, and System Center to deliver a private cloud infrastructure for customers.
The IaaS PLA provides a reference implementation that combines Microsoft software, consolidated guidance, and validated configurations with partner technology such as compute, network, and storage architectures, in addition to value-added software components through a series of defined fabric infrastructure and fabric management design patterns. The PLA includes multiple fabric design patterns and storage architectures as well as a single highly available System Center designpattern.
These patterns serve as the foundation for a range of private and hybrid cloud solutions and offerings from Microsoft Services and its partners. By implementing private cloud configurations that align to the IaaS PLA, Microsoft and its hardware partners can help provide organizations the control and the flexibility that are required to reap the potential benefits of the private cloud.
At this time, there are two documents available to you – the Fabric Architecture Guide and the Fabric Management Architecture Guide
To sysprep a WS 2012 R2 for deploy virtual machines I do the following things:
Before to sysprep configure regional settings for all users and download/install windows updates
- In device manager from View pane enable show hidden devices and then in Network Adapters delete Micosoft Hyper-V Network Adapter
- Delete in %WINDIR%\Panther the Unattend folder
- Execute %WINDIR%\system32\sysprep\sysprep.exe /generalize /oobe /mode:vm /shutdown
Today MS has published a new rollup for SCVMM 2012 R2, this is Update Rollup 2 and here I put the link http://support.microsoft.com/kb/2932926
For a good installation remember:
- First install server update package (KB2932926)
- Second apply sql script
- Third install admin console update package (KB2932942)
If someday you need to create a guest cluster on Hyper-V 2012 R2 and have not hdd from a SAN with the following trick you can do it (not supported by Microsoft)
You can read in the below link, section 3, how to do too.
Connected to hyper-v 2012 R2 host we do:
- Create a folder where to save all shared disks for guest cluster (quorum, etc)
- Execute fltmc attach svhdxflt drive:
- Create all vhdx disks and save it in the path.
- Import disks in all guest cluster nodes and mark the following checkbox in everyone of them:
- Go to primary guest cluster node and create Windows cluster, etc..
Take care that every time you reboot a hyper-v node you will need to execute fltmc attach svhdxflt drive: in this node.
Like others SC products, you need to register the sdk service account that run OM services in your OMS with setspn to work correctly.
The syntax to execute are below:
setspn -S MSOMSdkSvc/OMS.domain.fqdn.com domainnetbiosname\SVC-SCOMsdk-PRE
setspn -S MSOMSdkSvc/OMS domainnetbiosname\SVC-SCOMsdk-PRE
To see if you did ok, use setspn -L SVC-SCOMsdk-PRE
If you want to know more about SPN for SCOM I put here a good article from Kevin Holman.