Quantcast
Channel: Virtual Machine Manager – Setup forum
Viewing all 581 articles
Browse latest View live

Migrate Hyper-V Switch to SCVMM for Clouds

$
0
0

I have a four port NIC that is bound to a Hyper-V switch team (standard Windows Server team, not 3rd party) with an untagged VLAN, where a majority of my VMs are, and a tagged VLAN ID 2. This is on Windows Server 2012 R2. I will be adding a second Windows Server 2012 R2 Hyper-V host very soon with the same NIC/VLAN configuration.

What I would like to do is migrate this to SCVMM. SCVMM of course recognizes my existing Virtual Switch, but here is what I want to do:

On the untagged VLAN, this will belong to the Cloud 'Home'. This cloud has a VM subnet defined in SCVMM with the untagged VLAN (0) and leverages DHCP from an external DHCP server to assign IP addresses in a specific range of the subnet. Works fine.

The tagged VLAN (2), is assigned the Cloud 'Lab'. I have a different subnet defined where all VMs will be using statically assigned IP addresses by SCVMM, except in particular scenarios (primarily 2 Domain Controllers).

For each Cloud, the only Logical Network I have is 'Virtual Network' (the name of the VNet as represented in the Hyper-V MMC). This logical network has both the untagged and tagged subnets defined on it.

What is the best way to make this transition so I can select the appropriate VM network and VM subnet for each Cloud? Will I need to destroy the Hyper-V created virtual switch and start anew?

So to kind of lay this out:

2 Hyper-V hosts

Both hosts have a Windows Server team for their NIC, with the physical switch ports assigned the untagged VLAN and VLAN ID 2. The untagged VLAN is using an external DHCP server. VLAN ID 2 will be static assignment only, performed by SCVMM.

'Home' cloud will only be using untagged.

'Lab' cloud will only be using VLAN ID 2.


Trevor Seward

Office Servers and Services MVP



Author, Deploying SharePoint 2016

This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.


Unable to connect to the VMM database because of a general database failure. Ensure that the SQL Server is running and configured correctly, then try the operation again.

$
0
0

Dear All,

When i tried to install VMM "Retain Data" it is show the issue below...

Unable to connect to the VMM database because of a general database failure.
Ensure that the SQL Server is running and configured correctly, then try the operation again.

NOTE

1. i can able to login to SQL

2. i can able to ping sql

3. SCVMM detected DataBase during Installation.

Thanks


FZ2H

scvmm 2012 R2 on sql 2014

$
0
0

Hallo,

i have installed the dB for scvmm 2012 R2 on a sql 2014, because it was just there and i read that with RU5 it is supported.

No errors during scvmm install, all seems to work fine after install: added cluster, hosts, configured subnets, tested storage and vm live-migration, ...

Than i want to install the RU11, to be fully compatible with the sql 2014, but the install breaks and after that the DB was corrupted, scvmm-service doestn start anymore.

I couldn find a downlaod vor SCVMM R2 with Rollup 5 (or 11) just installed.

So now the steps are:

- Install the scvmm dB on a sql 2012sp1

- Install RU11

- Migrate dB to sql 2014

But the 'official' way to migrate an scvmm DB, is to reinstall scvmm itself, microsoft says. But when i uninstall scvmm i can only reinstall it without the RU and i am on the same situation as before.

So what are supported steps to have an scvmm 2012 R2 DB running on an sql 2014 ?

Thanks a lot

AM

Operating System not supported

$
0
0

Hi,

I'm trying to install the SCVMM2012 on a Windows Server 2012 R2 Standard server but I keep no getting the error..... 

"Virtual Machine Manager server is not supported on this operating system. For more information, see 'System Operating System for VMM' in Virtual Machine Manager Setup Help."

Regards

System Center 2012 R2 Virtual Machine Manager – Evaluation (VHD) Can't complete installation

$
0
0

I've downloaded the System Center 2012 R2 Virtual Machine Manager – Evaluation (VHD)

I was able to create the Virtual Machine and configure SQL per the instructions.

When I run the Configure VMM  I will get the following error message

The specified logon credentials are not valid on the local server.  Set a valid domain username and password and try the operation again.  I am logged in as the Domain Administrator.  I can not figure out why this will not complete.  Does anyone have any ideas.

Thanks,

Download SCVMM 2012 (not SP1)

$
0
0

Hi,

I am looking for the SCVMM 2012 (not SP1) installation files but I couldn't find it anywhere. Is there a way to access it somewhere ?

Thank you

Installing VMM 2016 failed

$
0
0

I'm trying to install VMM2016 from command line (run as administrator), but I'm getting error and install fails. First tried using wizad too, but also failed.

10:11:49:VMMPostinstallProcessor threw an exception: Threw Exception.Type: Microsoft.VirtualManager.Setup.Exceptions.BackEndErrorException, Exception.Message: A Hardware Management error has occurred trying to contact server 'vmm2016.domain.ee'  .

WinRM: URL: [http://vmm2016.domain.ee:5985], Verb: [GET], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scvmm/FileInformation?Filename=\\vmm2016.domain.ee\MSSCVMMLibrary\VHDs\Blank Disk - Small.vhd]

Check that WinRM is installed and running on server 'vmm2016.domain.ee'. For more information use the command "winrm helpmsg hresult" and http://support.microsoft.com/kb/2742275.
10:11:49:StackTrace:   at Microsoft.VirtualManager.Setup.DBConfigurator.SetupAsLibServer(Nullable`1 existingServerGuid, IVmmDbConnection dbConnection)
   at Microsoft.VirtualManager.Setup.VirtualMachineManagerHelpers.AddLibrary(IVmmDbConnection dbConnection)
   at Microsoft.VirtualManager.Setup.InstallItemCustomDelegates.<>c__DisplayClass13.<PangaeaServerPostinstallProcessor>b__e(IVmmDbConnection _dbConnection)
   at Microsoft.VirtualManager.DB.SqlContext.Connect(Action`1 action)
   at Microsoft.VirtualManager.Setup.InstallItemCustomDelegates.PangaeaServerPostinstallProcessor()
10:11:49:InnerException.Type: Microsoft.Carmine.WSManWrappers.WSManProviderException, InnerException.Message: A Hardware Management error has occurred trying to contact server 'vmm2016.domain.ee'  .

WinRM: URL: [http://vmm2016.domain.ee:5985], Verb: [GET], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scvmm/FileInformation?Filename=\\vmm2016.domain.ee\MSSCVMMLibrary\VHDs\Blank Disk - Small.vhd]

Check that WinRM is installed and running on server 'vmm2016.domain.ee'. For more information use the command "winrm helpmsg hresult" and http://support.microsoft.com/kb/2742275.
10:11:49:InnerException.StackTrace:   at Microsoft.Carmine.WSManWrappers.ErrorContextParameterHelper.ThrowTranslatedCarmineException(WsmanSoapFault fault, COMException ce)
   at Microsoft.Carmine.WSManWrappers.WsmanAPIWrapper.RetrieveUnderlyingWMIErrorAndThrow(SessionCacheElement sessionElement, COMException e)
   at Microsoft.Carmine.WSManWrappers.WsmanAPIWrapper.Get(MyWSManResourceLocator resLocator, WSManUri url, Type type, Boolean forceTypeCast)
   at Microsoft.Carmine.WSManWrappers.WsmanAPIWrapper.Get(WSManUri url, Type type, Boolean forceTypeCast)
   at Microsoft.Carmine.WSManWrappers.WSManCachedRequest`1.Get(String url)
   at Microsoft.Carmine.VSImplementation.WindowsAgentHostFileInformation.Refresh()
   at Microsoft.Carmine.VSImplementation.HostFileInformation.GetHostFileInformation(WSManConnectionParameters connParams, String filename)
   at Microsoft.VirtualManager.Engine.ImageLibrary.ItemBase.RetrieveFileInfo(Boolean throwOnError, ErrorInfo& errorInfo, IVmmDbContext ctx)
   at Microsoft.VirtualManager.Engine.ImageLibrary.VHD.RetrieveFileInfo(Boolean throwOnError, ErrorInfo& errorInfo, IVmmDbContext ctx)
   at Microsoft.VirtualManager.Setup.DBConfigurator.<>c__DisplayClass32.<AddLibVHD>b__30(IVmmDbConnection _dbConnection)
   at Microsoft.VirtualManager.Setup.DBConfigurator.SetupAsLibServer(Nullable`1 existingServerGuid, IVmmDbConnection dbConnection)
10:11:49:InnerException.Type: System.Runtime.InteropServices.COMException, InnerException.Message: The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol. 
10:11:49:InnerException.StackTrace:   at WSManAutomation.IWSManSession.Get(Object resourceUri, Int32 flags)
   at Microsoft.Carmine.WSManWrappers.MyIWSManSession.Get(Object resourceUri, Int32 flags)
   at Microsoft.Carmine.WSManWrappers.WsmanAPIWrapper.Get(MyWSManResourceLocator resLocator, WSManUri url, Type type, Boolean forceTypeCast)
10:11:49:ProcessInstalls: Running the PostProcessDelegate returned false.
10:11:49:ProcessInstalls: Running the PostProcessDelegate for PangaeaServer failed.... This is a fatal item.  Setting rollback.
10:11:49:ProcessInstalls: Rollback is set and we are not doing an uninstall so we will stop processing installs

Installation Can't Continue - Windows Assessment and Deployment Kit 8.1 not Detected

$
0
0

VMM 2012 R2 setup doesn't detect an installed ADK 8.1 (or ADK 8.0). Per VMM system requirements, I've installed ADK 8.1 with Deployment Tools and Windows PE features installed. ADK install and logs appear to indicate successful installation. I'm trying to install VMM onto a fresh WS2012R2 VM for each attempt with latest Windows update. All other prerequisites per logs seem to be met, w/ this exception (shown below). I've also tried per other similar VMM/ADK problem threads here:

  • Install ADK and VMM sourced from C:
  • Install 8.0 instead of 8.1
  • Installed all ADK features besides Deployment Tools and Windows PE

Any thoughts?

Thanks, MWfor64bit

PrereqCheck.txt file shows:

Both the Deployment Tools and the Windows Preinstallation Environment features from the Windows® Assessment and Deployment Kit for Windows 8.1 must be installed on this computer to run Microsoft System Center 2012 R2 – Virtual Machine Manager.
</Description>
    <Resolution>To download the Windows® Assessment and Deployment Kit, go to</Resolution>
    <ResolutionDownloadPageTitle>Windows Assessment and Deployment Kit (ADK)</ResolutionDownloadPageTitle>
    <ResolutionUri>http://go.microsoft.com/fwlink/?LinkId=302319</ResolutionUri>
    <LogInformation>&lt;![CDATA[CheckPrerequisites:   Logic Type:and WADK-Fail: 2]]&gt;</LogInformation>


MWfor64bit



Networkservice.NSPluginConnectionFailedexception: the remote server returned an error 409 conflict error

$
0
0

I'm trying to connect the ODL VSEM provider plugin in SCVMM to the VTN coordinator. Currently i'm facing the 'conflict' problem which is not allowing the SCVMM connect to the VTN coordinator. The Network Service wizard also not passing the tests for 'Test API connection' etc..

If anyone worked on this, please help. I'm unable to attach the error message to this forum.

Error message " Microsoft.SystemCenter.NetworkService.NSPluginConnectionFailedexception the remote server returned an error 409 conflict "

SCVMM 2016 failing to install at database configuration

$
0
0

I'm running into an issue trying to install SCVMM 2016 as a single server setup that will be managing under 100 VMs.  First a background of what I've done.


I'm running Windows Server 2016 Standard with Desktop Experience, SQL Server 2016 Standard installed with only Database Engine Services selected (Since the management features are no longer included in the SQL 2016 installer).  The SQL Server Agent and Database Engine are running with a dedicated AD service account with the Agent set to Manual startup.  The Authentication mode is Windows with the SQL Server administrators set to the Local Administrators group of the server.  SQL Server Management Studio was installed separately.


The ADK for Windows 10 was installed only selecting the Deployment Tools and Windows Preinstallation Environment, SQL Server 2014 Command Line tools were installed which required the ODBC 11 driver to be installed to support the 2014 Command Line Tools.  It's interesting that the Installation and Upgrade Requirements page ( https://technet.microsoft.com/en-us/system-center-docs/vmm/plan/plan-install ) states the Command Line Tools that you install should match the version of SQL you installed.  In my case this would be 2016 but the SCVMM prerequisite check fails with the 2016 version stating to install the 2014 version.


When I run the SCVMM installer I proceed to the "Database configuration" page which has my server name pre-populated.  I'm entering a dedicated service account name in the domain\username format.  This account is a member of the local administrators group on the server.  The instance name drop down box automatically detects the instance name that I will be using.  New database is automatically populated with the default VirtualManagerDB name.  When I click Next there is a pause and then I receive this error:


The existing Virtual Machine Manager database is not accessible.  Ensure that SQL instance "ServerName" is installed properly and running.  Also ensure that VirtualManagerDB is accessible.  (Note: ServerName = name of the actual server)


The error is a bit odd that it states the existing database is not accessible since I selected the default New database option.  Checking SQL Server Management Studio Logs I see two errors.


Error: 18456, Severity: 14, State 146.

Login failed for user 'domain\username'.  Reason: Token-based server access validation failed with an infrastructure error.  Login lacks Connect SQL permission. [CLIENT: <local machine>]  (Note: domain\username = name of the actual user)


I've referenced this blog ( https://blogs.msdn.microsoft.com/psssql/2016/07/09/why-do-i-get-the-infrastructure-error-for-login-failures/ ) for assistance but I'm unable to determine the root cause as everything seems to be correctly configured.

What am I missing here?  Any ideas?

SQL requirements for VMM2016 unclear...

System Center VMM error 20408 when adding virtual machine host

$
0
0

Error (20408)
VMM could not get the specified instance Microsoft:{7172d33e-7a0b-4b32-b93b-e958f5cf7356} of class http://schemas.microsoft.com/wbem/wsman/1/wmi/root/standardcimv2/MSFT_NetAdapterRssSettingData on the server xxx. The operation failed with error NO_PARAM

I have not found any solution to fix this error.

Any help would be really appreciated!

Thanks in advance

System Center VMM 2016 error 20408 when adding virtual machine host

$
0
0

Error (20408)
VMM could not get the specified instance Microsoft:{7172d33e-7a0b-4b32-b93b-e958f5cf7356} of class http://schemas.microsoft.com/wbem/wsman/1/wmi/root/standardcimv2/MSFT_NetAdapterRssSettingData on the server xxx. The operation failed with error NO_PARAM

I have not found any solution to fix this error.

Any help would be really appreciated!

Thanks in advance


VMM 2016 on WS2016 Domain Controller?

$
0
0

All,

Currently working on planning an upgrade/migration to VMM 2016, which includes installation on a WS2016 Domain Controller. 

I know that in previous versions of VMM, this configuration was supported as long as the Domain Controller had been stood up prior to installation of VMM. However, I have not yet found if this is yet supported for 2016 or not. 

Has anyone else found if this configuration is supported in 2016? 

Cheers! 

Jonathan

Install virtual machine manager server failed at the step "Granting database access"

$
0
0

the machine used to install scvmm is just a fresh VM, sql server and vm server are in the same machine, login and installed vmm server by using domain admin.
also run configuratin analyzer, did not see any issue.

note the vm vhd is used by several VMs. Not sure SPN is duplicate, I run "setspn -x", did not see any duplicate item for this vm.

Error log:

[7/25/2010 10:59:48 PM] Data : sqlCmdPath = "c:\Program Files\Microsoft SQL Server\90\Tools\Binn\SqlCmd.exe"
[7/25/2010 10:59:48 PM] Data : bcpPath = "c:\Program Files\Microsoft SQL Server\90\Tools\Binn\bcp.exe"
[7/25/2010 10:59:49 PM] Information : Retrieve share path
[7/25/2010 10:59:49 PM] Information : Create folder
[7/25/2010 10:59:49 PM] Information : Copy a file
[7/25/2010 10:59:49 PM] Information : Copy a file
[7/25/2010 10:59:50 PM] * Exception :  => Virtual Machine Manager cannot process the request because an error occurred while authenticating SH-SCVMM-T1.testdomain.com.

Possible causes are:
1) The specified user name or password are not valid.
2) The Service Principal Name (SPN) for the remote computer name and port does not exist.
3) The client and remote computers are in different domains and there is not a two-way full trust between the two domains.Log in by using an account on the same domain as the VMM server, or by using an account on a domain that has a two-way full trust with the domain of the VMM server, and then try the operation again. If this does not work, purge the Kerberos tickets on the VMM server by using kerbtray.exe, available athttp://go.microsoft.com/fwlink/?LinkId=93709. Then, reset the SPN for SH-SCVMM-T1.testdomain.com by using setspn.exe available fromhttp://go.microsoft.com/fwlink/?LinkId=93710. If this still does not fix the problem, make SH-SCVMM-T1.testdomain.com a member of a workgroup instead of a domain, restart the computer, rejoin the domain, and then try the operation again.Microsoft.VirtualManager.Setup.Exceptions.BackEndErrorException: Virtual Machine Manager cannot process the request because an error occurred while authenticating SH-SCVMM-T1.testdomain.com.

Possible causes are:
1) The specified user name or password are not valid.
2) The Service Principal Name (SPN) for the remote computer name and port does not exist.
3) The client and remote computers are in different domains and there is not a two-way full trust between the two domains.
Log in by using an account on the same domain as the VMM server, or by using an account on a domain that has a two-way full trust with the domain of the VMM server, and then try the operation again. If this does not work, purge the Kerberos tickets on the VMM server by using kerbtray.exe, available at http://go.microsoft.com/fwlink/?LinkId=93709. Then, reset the SPN for SH-SCVMM-T1.testdomain.com by using setspn.exe available fromhttp://go.microsoft.com/fwlink/?LinkId=93710. If this still does not fix the problem, make SH-SCVMM-T1.testdomain.com a member of a workgroup instead of a domain, restart the computer, rejoin the domain, and then try the operation again. ---> Microsoft.Carmine.WSManWrappers.WSManProviderException: Virtual Machine Manager cannot process the request because an error occurred while authenticating SH-SCVMM-T1.testdomain.com.

Possible causes are:
1) The specified user name or password are not valid.
2) The Service Principal Name (SPN) for the remote computer name and port does not exist.
3) The client and remote computers are in different domains and there is not a two-way full trust between the two domains.
Log in by using an account on the same domain as the VMM server, or by using an account on a domain that has a two-way full trust with the domain of the VMM server, and then try the operation again. If this does not work, purge the Kerberos tickets on the VMM server by using kerbtray.exe, available at http://go.microsoft.com/fwlink/?LinkId=93709. Then, reset the SPN for SH-SCVMM-T1.testdomain.com by using setspn.exe available fromhttp://go.microsoft.com/fwlink/?LinkId=93710. If this still does not fix the problem, make SH-SCVMM-T1.testdomain.com a member of a workgroup instead of a domain, restart the computer, rejoin the domain, and then try the operation again. ---> System.IO.FileNotFoundException: The network path was not found.
   at Microsoft.Carmine.WSManWrappers.MyIWSManSession.Invoke(String actionUri, Object resourceUri, String parameters, Int32 flags)
   at Microsoft.Carmine.WSManWrappers.WsmanAPIWrapper.Invoke(String actionUri, String url, Hashtable parameters, Type returnType, Boolean isCarmineMethod)
   --- End of inner exception stack trace ---
   at Microsoft.Carmine.WSManWrappers.ErrorContextParameterHelper.ThrowTranslatedCarmineException(FileNotFoundException fioe)
   at Microsoft.Carmine.WSManWrappers.WsmanAPIWrapper.Invoke(String actionUri, String url, Hashtable parameters, Type returnType, Boolean isCarmineMethod)
   at Microsoft.Carmine.WSManWrappers.AgentManagement.AssociateLibrary(WsmanAPIWrapper wsmanObject, String CertificateSubjectName, String& ExportedCertificate, ErrorInfo& ErrorInfo)
   at Microsoft.VirtualManager.Setup.Wizard.Configurator.SetUpLibraryShare()
   at Microsoft.VirtualManager.Setup.Wizard.BackEnd.ConfigureServer()
   at Microsoft.VirtualManager.Setup.Wizard.VMInstaller.Configure()
*** Carmine error was: HostAgentBadSharePathname (2917); HR: 0x80070035
***  ** SH-SCVMM-T1.testdomain.com **
   --- End of inner exception stack trace ---
   at Microsoft.VirtualManager.Setup.Wizard.VMInstaller.Configure()
   at Microsoft.VirtualManager.Setup.Wizard.ProgressPage.InstallerThreadEntry()
*** Carmine error was: HostAgentBadSharePathname (2917); HR: 0x80070035
***  ** SH-SCVMM-T1.testdomain.com **
[7/25/2010 10:59:50 PM] *** Error : Virtual Machine Manager cannot process the request because an error occurred while authenticating SH-SCVMM-T1.testdomain.com. Possible causes are:
1) The specified user name or password are not valid.
2) The Service Principal Name (SPN) for the remote computer name and port does not exist.
3) The client and remote computers are in different domains and there is not a two-way full trust between the two domains. Log in by using an account on the same domain as the VMM server, or by using an account on a domain that has a two-way full trust with the domain of the VMM server, and then try the operation again. If this does not work, purge the Kerberos tickets on the VMM server by using kerbtray.exe, available athttp://go.microsoft.com/fwlink/?LinkId=93709. Then, reset the SPN for SH-SCVMM-T1.testdomain.com by using setspn.exe available fromhttp://go.microsoft.com/fwlink/?LinkId=93710. If this still does not fix the problem, make SH-SCVMM-T1.testdomain.com a member of a workgroup instead of a domain, restart the computer, rejoin the domain, and then try the operation again.
ID: 2917. Details: The network path was not found (0x80070035)
[7/25/2010 10:59:50 PM] Information : Virtual Machine Manager Server installation has failed.
To return the server to its original state, you must uninstall the Virtual Machine Manager server by using Add or Remove Programs in Control Panel. This will remove all files and components copied during installation.


SCVMM 2012 R2 Re-installation on a Different server with same DB instance

$
0
0

We are planning to move SCVMM 2012 R2 to new hardware:

plan: keep the same DB instance, move the SCVMM 2012 R2 to new server.

we have considered the following link for the steps:Restore the VMM server on a different computer

https://technet.microsoft.com/en-us/library/dn768227(v=sc.12).aspx#BKMK_r_different

Though steps are present in the article it is confusing, most of the blogs have written about DB restore not SCVMM application restore, can you please let us know the steps and any additional actions\process to be performed in the reinstallation. 

Unsupported Cluster Configuration - Error (13924)

$
0
0

I've just installed a bran new VMM 2012 SP1 Server.  This is my first VMM Server, and therefore, I have very limited knowledge and experience with it.  I've added my existing Hyper-V Cluster to VMM.  My Hyper-V Cluster is a 4 node cluster running Windows Server 2012.  My VMs are stored on a "Scale-out File Server Cluster" using SMB 3.0, on Windows Server 2012 (\\SOFS\Share).

I've also added the SMB share to my VMM's cluster properties.

The majority of my VMs have a status or "Running".  However, if I do a "Refresh" on a VM, the status will change to "Unsupported Cluster Configuration"  Then, if I view the Status of the VM, I see the following error message:

Error (13924)
The highly available virtual machine (VMNAME) is not supported by VMM because the virtual machine uses non-clustered storage.

Recommended Action
Ensure that all of the files and pass-through disks belonging to the virtual machine reside on highly available storage.

Once the VM is in this state, I can no longer do any Migrations from VMM.  I can still do Live Migrations from the Failover Cluster Manager console, but not from VMM.  Does anyone have any suggestions?

Trouble refreshing a newly added VM host in lab (SCVMM 2016, server 2016, lab)

$
0
0

Hello,

I have a lab of one host. This Windows Server 2016 Datacenter install is not the cleanest... it has been upgraded, played with, abused. The host itself is a Dell R710 with dual 6-core 2.26Ghz Xeon and 144GB RAM...

I just tried over the last few days to install a VMM environment with the VMM server being hosted as a VM on the same server. I once successfully did this with server 2012 R2 and System center 2012.

Now I am having an issue. Everything runs exceedingly slow, and eventually just fails. SCVMM eventually will pick up some limited information about my host, like the amount of memory left and the names of all the virtual machines on it. But it still throws many errors when trying to refresh.

I couldn't tell you if the issue is with the SCVMM server or the host itself. I did uninstall SCVMM server and reinstall. I also have rebooted the host a few times. 

Here is the error output that I was directed to after the "Refresh Host" task failed during "Add virtual machine host".

https://gist.github.com/anonymous/f51cf0b39cdea24d1f013fef36359d18

Thanks!

SCVMM Installation Error 205/1603

$
0
0

System Center Virtual Machine Manager was not installed successfully.  Review the error log information thand then try running Setup again. 

I get this message when attemting to install SCVMM 2008 R2.  I've seen many discussions about this issue but no solutions. 

Is there a solution for this problem?  I've tried every solution that has been posted and nothing works. 

Help?

Action ended 14:14:02: RollbackNPIVMofNPIVMethods. Return value 1.
MSI (s) (50:7C) [14:14:02:951]: Note: 1: 2235 2:  3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'RollbackServiceFirewallConfigWin6'
Action start 14:14:02: RollbackServiceFirewallConfigWin6.
MSI (s) (50:7C) [14:14:02:952]: Doing action: MofcompCarmineVirtualizationMof
MSI (s) (50:7C) [14:14:02:952]: Note: 1: 2205 2:  3: ActionText
Action ended 14:14:02: RollbackServiceFirewallConfigWin6. Return value 1.
MSI (s) (50:7C) [14:14:02:952]: Note: 1: 2235 2:  3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'MofcompCarmineVirtualizationMof'
Action start 14:14:02: MofcompCarmineVirtualizationMof.
MSI (s) (50:7C) [14:14:02:953]: Doing action: CreateCarmineServersGroup
MSI (s) (50:7C) [14:14:02:953]: Note: 1: 2205 2:  3: ActionText
Action ended 14:14:02: MofcompCarmineVirtualizationMof. Return value 1.
MSI (s) (50:7C) [14:14:02:953]: Note: 1: 2235 2:  3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'CreateCarmineServersGroup'
MSI (s) (50:7C) [14:14:02:954]: Creating MSIHANDLE (13) of type 790542 for thread 2428
MSI (s) (50:5C) [14:14:02:956]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI7D19.tmp, Entrypoint: CreateCarmineServersGroup
Action start 14:14:02: CreateCarmineServersGroup.
MSI (s) (50:5C) [14:14:03:039]: Closing MSIHANDLE (13) of type 790542 for thread 2428
CustomAction CreateCarmineServersGroup returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (50:7C) [14:14:03:040]: Machine policy value 'DisableRollback' is 0
MSI (s) (50:7C) [14:14:03:040]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
Action ended 14:14:03: CreateCarmineServersGroup. Return value 3.
MSI (s) (50:7C) [14:14:03:040]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (50:7C) [14:14:03:040]: No System Restore sequence number for this installation.
MSI (s) (50:7C) [14:14:03:040]: Unlocking Server
Action ended 14:14:03: INSTALL. Return value 3.
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductCode = {049DB35D-4A8B-4DFF-A9EF-D7142186BDFD}
Property(S): ProductLanguage = 1033
Property(S): ProductName = Microsoft System Center Virtual Machine Manager 2008 R2 Server (x64)
Property(S): ProductVersion = 2.0.4271.0
Property(S): UpgradeCode = {E3FDD051-3A89-4FFE-B42D-81A8FFC19884}
Property(S): INSTALLLEVEL = 100
Property(S): ARPSYSTEMCOMPONENT = 1
Property(S): ALLUSERS = 1
Property(S): DiskPrompt = Microsoft System Center Virtual Machine Manager 2008 R2 Server (x64) Installation [1]
Property(S): BOOTSTRAPPED = 1
Property(S): MofFileName = VMMAgent.mof
Property(S): WmiNamespace = scvmm
Property(S): AgentExeName = vmmAgent.exe
Property(S): AGENTSERVICENAME = VMMAgent
Property(S): AgentFirewallRuleName = VMMAgent
Property(S): WSMANPORT = 80
Property(S): WSMANMINVERSION = 5.2.3790.2984
Property(S): BITSPORT = 443
Property(S): BitsPortName = HTTPS
Property(S): SecureCustomProperties = UCE3FDD0513A894FFEB42D81A8FFC19884
Property(S): INSTALLDIR = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\
Property(S): VMMAppDataFolder = C:\ProgramData\Microsoft\Virtual Machine Manager\
Property(S): P2VCacheDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\VMMData\
Property(S): P2VPatchImportDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\Patch Import\
Property(S): P2VDriverImportDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\Driver Import\
Property(S): HyperVAuthDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\AuthStore\
Property(S): SysprepDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\Sysprep\
Property(S): AgentDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\agents\
Property(S): VirtualServerDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\vs\
Property(S): MsxmlDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\vs\msxml\
Property(S): Msxm1028Dir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\vs\msxml\1028\
Property(S): Msxm1031Dir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\vs\msxml\1031\
Property(S): Msxm1033Dir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\vs\msxml\1033\
Property(S): Msxm1036Dir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\vs\msxml\1036\
Property(S): Msxm1040Dir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\vs\msxml\1040\
Property(S): Msxm1041Dir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\vs\msxml\1041\
Property(S): Msxm1042Dir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\vs\msxml\1042\
Property(S): Msxm2052Dir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\vs\msxml\2052\
Property(S): Msxm3082Dir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\vs\msxml\3082\
Property(S): SetupDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\setup\
Property(S): VersionNT = 601
Property(S): RollbackPortFirewallConfigSSLWin6 = "C:\Windows\SysWOW64\netsh.exe" advfirewall firewall delete rule name="HTTPS"
Property(S): RollbackNPIVMofNPIVMethods = "C:\Windows\SysWOW64\wbem\wmic.exe" /NAMESPACE:\\root\wmi class MSFC_FibrePortNPIVMethods DELETE
Property(S): RollbackServiceFirewallConfigWin6 = "C:\Windows\SysWOW64\netsh.exe" advfirewall firewall delete rule name=VMMAgent
Property(S): MofcompCarmineVirtualizationMof = "C:\Windows\SysWOW64\wbem\mofcomp.exe" "C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\setup\VMMVirtualization.mof"
Property(S): RollbackCarmineMof = "C:\Windows\SysWOW64\wbem\wmic.exe" /NAMESPACE:\\root PATH __Namespace WHERE Name="scvmm" DELETE
Property(S): MofcompCarmineAgentMof = "C:\Windows\SysWOW64\wbem\mofcomp.exe" "C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\setup\VMMAgent.mof"
Property(S): ProgramMenuDir = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft System Center\Virtual Machine Manager 2008 R2\
Property(S): SystemCenterMenuDir = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft System Center\
Property(S): ProgramMenuDirV2 = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft System Center\Virtual Machine Manager 2008\
Property(S): BITS4 = C:\Windows\system32\QMgr.dll
Property(S): MSIDLL = C:\Windows\SysWOW64\msi.dll
Property(S): WINRMSERVICESTARTTYPE = #2
Property(S): WSMSVC = C:\Windows\SysWOW64\wsmwmipl.dll
Property(S): FIREWALLENABLED = #0
Property(S): CommonBinDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\bin\
Property(S): ScriptDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\setup\DB\
Property(S): SetupHelpDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\setup\help\
Property(S): AgentBinDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\bin\
Property(S): CommonBinChsDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\bin\zh-CHS\
Property(S): CommonBinChtDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\bin\zh-CHT\
Property(S): CommonBinFrDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\bin\fr\
Property(S): CommonBinDeDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\bin\de\
Property(S): CommonBinItDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\bin\it\
Property(S): CommonBinJaDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\bin\ja\
Property(S): CommonBinKoDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\bin\ko\
Property(S): CommonBinEsDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\bin\es\
Property(S): HelpDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\help\
Property(S): X86SysprepDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\Sysprep\i386\
Property(S): X64SysprepDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\Sysprep\amd64\
Property(S): X86AgentDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\agents\i386\
Property(S): X86AgentVerDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\agents\i386\2.0.4271.0\
Property(S): X64AgentDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\agents\amd64\
Property(S): X64AgentVerDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\agents\amd64\2.0.4271.0\
Property(S): X86P2VAgentDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\agents\p2v\i386\
Property(S): P2VSourceDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\agents\p2v\
Property(S): X64P2VAgentDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\agents\p2v\amd64\
Property(S): ServerBinChsDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\bin\zh-CHS\
Property(S): ServerBinChtDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\bin\zh-CHT\
Property(S): ServerBinFrDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\bin\fr\
Property(S): ServerBinDeDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\bin\de\
Property(S): ServerBinItDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\bin\it\
Property(S): ServerBinJaDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\bin\ja\
Property(S): ServerBinKoDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\bin\ko\
Property(S): ServerBinEsDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\bin\es\
Property(S): ServerBinDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\bin\
Property(S): SetupDirectory = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\setup\
Property(S): SetupBinChsDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\setup\zh-CHS\
Property(S): SetupBinChtDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\setup\zh-CHT\
Property(S): SetupBinFrDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\setup\fr\
Property(S): SetupBinDeDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\setup\de\
Property(S): SetupBinItDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\setup\it\
Property(S): SetupBinJaDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\setup\ja\
Property(S): SetupBinKoDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\setup\ko\
Property(S): SetupBinEsDir = C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\setup\es\
Property(S): ProgramFiles64Folder = C:\Program Files\
Property(S): ProgramMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\
Property(S): TARGETDIR = C:\
Property(S): MSAppDataFolder = C:\ProgramData\Microsoft\
Property(S): CommonAppDataFolder = C:\ProgramData\
Property(S): SourceDir = C:\Users\Administrator.CLUSTER\AppData\Local\Temp\1\VM859D.tmp\msi\Server\
Property(S): ExecServiceConfig = VMMAgent€restart€restart€restart€0€0€€
Property(S): MsiLogFileLocation = C:\ProgramData\VMMLogs\ServerSetup.log
Property(S): PackageCode = {91228A6A-2D2D-4D5E-9BD5-68474731C124}
Property(S): ProductState = -1
Property(S): PackagecodeChanging = 1
Property(S): INSTALLINGLANGUAGE = 1033
Property(S): SERVERACCOUNTNAME = DGWBVMM$@CLUSTER
Property(S): USERNAME = administrator
Property(S): COMPANYNAME = dgwb
Property(S): REBOOT = ReallySuppress
Property(S): CURRENTDIRECTORY = C:\Users\ADMINI~1.CLU\AppData\Local\Temp\1\VM859D.tmp\Setup
Property(S): CLIENTUILEVEL = 3
Property(S): MSICLIENTUSESEXTERNALUI = 1
Property(S): CLIENTPROCESSID = 920
Property(S): VersionDatabase = 301
Property(S): VersionMsi = 5.00
Property(S): VersionNT64 = 601
Property(S): WindowsBuild = 7600
Property(S): ServicePackLevel = 0
Property(S): ServicePackLevelMinor = 0
Property(S): MsiNTProductType = 2
Property(S): MsiNTSuiteEnterprise = 1
Property(S): WindowsFolder = C:\Windows\
Property(S): WindowsVolume = C:\
Property(S): System64Folder = C:\Windows\system32\
Property(S): SystemFolder = C:\Windows\SysWOW64\
Property(S): RemoteAdminTS = 1
Property(S): TempFolder = C:\Users\ADMINI~1.CLU\AppData\Local\Temp\
Property(S): ProgramFilesFolder = C:\Program Files (x86)\
Property(S): CommonFilesFolder = C:\Program Files (x86)\Common Files\
Property(S): CommonFiles64Folder = C:\Program Files\Common Files\
Property(S): AppDataFolder = C:\Users\Administrator.CLUSTER\AppData\Roaming\
Property(S): FavoritesFolder = C:\Users\Administrator.CLUSTER\Favorites\
Property(S): NetHoodFolder = C:\Users\Administrator.CLUSTER\AppData\Roaming\Microsoft\Windows\Network Shortcuts\
Property(S): PersonalFolder = C:\Users\Administrator.CLUSTER\Documents\
Property(S): PrintHoodFolder = C:\Users\Administrator.CLUSTER\AppData\Roaming\Microsoft\Windows\Printer Shortcuts\
Property(S): RecentFolder = C:\Users\Administrator.CLUSTER\AppData\Roaming\Microsoft\Windows\Recent\
Property(S): SendToFolder = C:\Users\Administrator.CLUSTER\AppData\Roaming\Microsoft\Windows\SendTo\
Property(S): TemplateFolder = C:\ProgramData\Microsoft\Windows\Templates\
Property(S): LocalAppDataFolder = C:\Users\Administrator.CLUSTER\AppData\Local\
Property(S): MyPicturesFolder = C:\Users\Administrator.CLUSTER\Pictures\
Property(S): AdminToolsFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\
Property(S): StartupFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\
Property(S): StartMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\
Property(S): DesktopFolder = C:\Users\Public\Desktop\
Property(S): FontsFolder = C:\Windows\Fonts\
Property(S): GPTSupport = 1
Property(S): OLEAdvtSupport = 1
Property(S): ShellAdvtSupport = 1
Property(S): MsiAMD64 = 6
Property(S): Msix64 = 6
Property(S): Intel = 6
Property(S): PhysicalMemory = 2000
Property(S): VirtualMemory = 3225
Property(S): AdminUser = 1
Property(S): MsiTrueAdminUser = 1
Property(S): LogonUser = Administrator
Property(S): UserSID = S-1-5-21-1487624557-3738669419-1616575610-500
Property(S): UserLanguageID = 1033
Property(S): ComputerName = DGWBVMM
Property(S): SystemLanguageID = 1033
Property(S): ScreenX = 1024
Property(S): ScreenY = 768
Property(S): CaptionHeight = 19
Property(S): BorderTop = 1
Property(S): BorderSide = 1
Property(S): TextHeight = 16
Property(S): TextInternalLeading = 3
Property(S): ColorBits = 32
Property(S): TTCSupport = 1
Property(S): Time = 14:14:03
Property(S): Date = 10/14/2010
Property(S): MsiNetAssemblySupport = 2.0.50727.4927
Property(S): MsiWin32AssemblySupport = 6.1.7600.16385
Property(S): RedirectedDllSupport = 2
Property(S): MsiRunningElevated = 1
Property(S): Privileged = 1
Property(S): DATABASE = C:\Windows\Installer\2e69c6.msi
Property(S): OriginalDatabase = C:\Users\Administrator.CLUSTER\AppData\Local\Temp\1\VM859D.tmp\msi\Server\vmmServer.msi
Property(S): UILevel = 2
Property(S): ACTION = INSTALL
Property(S): OSCOMPATIBLE = 1
Property(S): CPUCOMPATIBLE = 1
Property(S): FIREWALLSERVICESTARTED = 1
Property(S): OtherAgentServiceExists = 0
Property(S): LOCALADMINGROUP = Administrators
Property(S): AUTHENTICATEDUSERSGROUP = Authenticated Users
Property(S): ROOTDRIVE = C:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): SOURCEDIR = C:\Users\Administrator.CLUSTER\AppData\Local\Temp\1\VM859D.tmp\msi\Server\
Property(S): SourcedirProduct = {049DB35D-4A8B-4DFF-A9EF-D7142186BDFD}
Property(S): WINRMSERVICESTARTED = 1
Property(S): INCORRECTBITSORWSMANPORT = 0
MSI (s) (50:7C) [14:14:03:076]: Note: 1: 1708
MSI (s) (50:7C) [14:14:03:076]: Product: Microsoft System Center Virtual Machine Manager 2008 R2 Server (x64) -- Installation failed.

MSI (s) (50:7C) [14:14:03:076]: Windows Installer installed the product. Product Name: Microsoft System Center Virtual Machine Manager 2008 R2 Server (x64). Product Version: 2.0.4271.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.

MSI (s) (50:7C) [14:14:03:097]: Deferring clean up of packages/files, if any exist
MSI (s) (50:7C) [14:14:03:097]: MainEngineThread is returning 1603
MSI (s) (50:58) [14:14:03:100]: RESTART MANAGER: Session closed.
MSI (s) (50:58) [14:14:03:100]: No System Restore sequence number for this installation.
=== Logging stopped: 10/14/2010  14:14:03 ===
MSI (s) (50:58) [14:14:03:100]: User policy value 'DisableRollback' is 0
MSI (s) (50:58) [14:14:03:100]: Machine policy value 'DisableRollback' is 0
MSI (s) (50:58) [14:14:03:100]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (50:58) [14:14:03:100]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (50:58) [14:14:03:100]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (50:58) [14:14:03:101]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (s) (50:58) [14:14:03:101]: Restoring environment variables
MSI (s) (50:58) [14:14:03:102]: Destroying RemoteAPI object.
MSI (s) (50:B4) [14:14:03:102]: Custom Action Manager thread ending.
MSI (c) (98:9C) [14:14:03:102]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (98:9C) [14:14:03:102]: MainEngineThread is returning 1603
=== Verbose logging stopped: 10/14/2010  14:14:03 ===

[10/14/2010 2:14:03 PM] Information : MsiInstallProduct returned 1603.
[10/14/2010 2:14:03 PM] Information : End install.
[10/14/2010 2:14:03 PM] Information : **************************************************************************************
[10/14/2010 2:14:03 PM] * Exception :  => System Center Virtual Machine Manager was not installed successfully.Review the error log information and then try running Setup again.Microsoft.VirtualManager.Setup.Exceptions.BackEndErrorException: System Center Virtual Machine Manager was not installed successfully.
Review the error log information and then try running Setup again. ---> Microsoft.VirtualManager.Setup.Exceptions.MsiInvokeException: System Center Virtual Machine Manager was not installed successfully.
Review the error log information and then try running Setup again.
   at Microsoft.VirtualManager.Setup.Wizard.Installer.Install()
   at Microsoft.VirtualManager.Setup.Wizard.BackEnd.Install(Installer installer)
*** Carmine error was: InstallFailed (205); WindowsAPI
*** C:\ProgramData\VMMLogs\ServerSetup.log **
   --- End of inner exception stack trace ---
   at Microsoft.VirtualManager.Setup.Wizard.BackEnd.Install(Installer installer)
   at Microsoft.VirtualManager.Setup.Wizard.VMInstaller.Install()
   at Microsoft.VirtualManager.Setup.Wizard.ProgressPage.InstallVm()
   at Microsoft.VirtualManager.Setup.Wizard.ProgressPage.InstallerThreadEntry()
*** Carmine error was: InstallFailed (205); WindowsAPI
*** C:\ProgramData\VMMLogs\ServerSetup.log **
[10/14/2010 2:14:03 PM] *** Error : System Center Virtual Machine Manager was not installed successfully. Review the error log information and then try running Setup again.
ID: 205. Details: Fatal error during installation
[10/14/2010 2:14:03 PM] Information : Virtual Machine Manager Server installation did not successfully install. All items that were copied during the installation process have been removed, however some required prerequisite software is still present on the machine. It is not necessary to remove the remaining software before you run Setup again. But you can uninstall the prerequisite software by going to Add or Remove Programs.
 

 

How to configure the vmm network?

$
0
0

Environment:

1) At first,create a virtual machine on vmware. os: windows server 2012 r2.   IP: 172.16.3.237

2) On the virtual machine, open Hyper-V Manager, new VMM virtual machine by System Center 2012 R2 VMM VHD file which downloaded from microsoft.com IP: 172.16.3.149

The question:

the VMM virtual machine was normally assigned IP address(172.16.3.149) by DHCP server.

but it can't ping through gateway: 172.16.3.1 

That means the VMM virtual machine can't connect to other host in the same lan.

 I dont know why? and how to resolve this problem?? thanks a lot~~~

Viewing all 581 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>