The VM in question is being ran on Windows Server 2012 R2 and already has an operating system installed Windows XP (32 Bit) and the problem I'm having is with a really old game that will install on the VM but when I try to run it, it says (Cannot Locate The CD-ROM). I've ran the program on another physical system days before this and it ran just fine the game is unreal tournament (yes the first one) and the disk says that it is designed for Windows 95 on the front, and that is the operating system that the physical system that I tested it with was running. I have a disk for Windows 98 but I'm having a little trouble with getting it to install on another VM so that is kind of my last resort.
windows XP VM using Hyper-V will install third party applications but won't run them
↧
↧
error when starting vhdx
Had a hard disk crash, Replace the disk and did a vhdx restore from backup.
now when I launch the vm I get the error
vhdx failed to open because of error: "the device does not recognize the command"
any one???
↧
Windows Server 2012 Login Issue "The User Profile Service service failed the sign-in. User profile cannot be loaded."
Whenever I try to login to our Exchange Server, I receive the following error:
"The User Profile Service service failed the sign-in. User profile cannot be loaded."
The issue affects more than one user.
Relevant Info:
Server Version: 2012 Datacenter
Exchange Version: 2013
The Exchange server is virtualized.
What I've tried:
1) Remote Desktop from a workstation on the network
2) Remote Desktop from Virtual Machine Manager
3) Connect via console from Virtual Machine Manager
4) Accessing the server via Computer Management and adding my user account to Allow Login via Remote Desktop
5) Creating a new user account for myself by copying the account of a user who can get in
6) Rebooting
I'd appreciate any suggestions.
↧
After Powershell Script - Server Service(s) crash
Hi Professionals
Following Situation:
Client (Windows 8.1) uses Script below for requesting status of Hyper-V Replication (Hyper-V Server 2k12 Core) Before of 3 Weeks ago the script was running smoothly all the time. Out of nowhere everytime the script runs the following Services on the Hyper-V
Server crashes unexpected. No Updates have been installed nor any changes made on the server. The curious thing about it is that on another server in another domain another adress range asf. The Same curious issue happened as described at the same time.
- IP-Helper
- Server
- System Event Notification Service
- Task Scheduler
- Software Protection
- User Profile Service
I can use manually powershell commands from remote:
Invoke-Command -ComputerName server02 -ScriptBlock {Get-Process}
Get-VM -ComputerName Server02
Firewall is disabled.
I tryied
- winrm /quickconfig
- enable-psremoting
- sfc /scannow
- dism /online /cleanup-image /scanhealth
No errors or corrupted files found. Someone has an Idea where to start?
Thank you Upfront for your Support!
***********************************
Used Script:
<#
.DESCRIPTION
Get Replicationhealth from remote hyper-v
#>
param
(
$CredentialPath = 'C:\ProgramData\path',
$username = "domain\U_PRTG",
$Computername = "server02.domain.ch"
)
$PasswordPath = "$CredentialPath\Password.txt"
$Password = Get-Content $PasswordPath | ConvertTo-SecureString
$C = new-object -typename System.Management.Automation.PSCredential -argumentlist $username, $Password
# Import-Module Hyper-V
$Result = Invoke-Command -ComputerName $Computername -ScriptBlock { Get-VMReplication -Mode Primary } -Credential $C
'<prtg>'
foreach ($Line in $Result)
{
if ($Line.Health -eq "normal")
{ $v = 0 }
else
{ $v = 1 }
"<result>"
"<channel>" + $Line.Name + "</channel>"
"<value>" + $v + "</value>"
"</result>"
}
'</prtg>'
<# Save Credentials
Read-Host –AsSecureString | ConvertFrom-SecureString | Out-File C:\ProgramData\path\Password.txt
$Password = Get-Content $CredentialPath\Password.txt | ConvertTo-SecureString
$C = new-object -typename System.Management.Automation.PSCredential -argumentlist $username, $password
#>
***********************************
↧
Create Homelab deparate from Main Network and give Access Point
Hello everbody. I am trying to create a homelab .
This homelab consists in a desktop that has 2 ethernet gigabit cards, and one wifi card.
This homelab has installed windows server 2012 R2 with HyperV role.
Whithin hyperV i have installed:
DC (windows server 2012 R2 with DNS-DHCP and Domain Controller)
IPCOP (virtual router that connects with my ISP Router)
IPCOP separate the main network (192.168.0.1/24) from the laboratory network (192.168.1.1/24)
DC acts as DHCP in the laboratory network
The thing is, that i want to use the wifi card (of my homelab) as an access point to connect from an external computer (like my laptop) trough this access point (and also be routed to internet).
For now, the only "access point" i have, is the one that the ISP provides me. But this access point, gives access to the "main network", and i want to create another access point to access from outside to the "laboratory network" (192.168.1.1/24).
First, of all, sorry about my english, i tried to be as simple as i can to explain it.
I will really apreciatte any help to create an access point in laboratory network .
I'll post a graphic to be more comprehensive.
↧
↧
Hyper-V Manager lockout
Hi @all,
I got something really interesting:
I'm currently evaluating IPv6 connectivity between two Sites with IPv4 and IPv6 in Dualstack enabled.
Short network overview:
SiteA.
- Hyper-V Host with VM "DC" and "FIREWALL"
SiteB
- Hyper-V Host with VM "SOMESERVICE"
Doing so I've joined the Hyper-V Host in SiteB to the Domain in Site A.
But something went terribly wrong since the computer account got down in Active Directory Users and Computers.
From this point on I've got the following trying to open up the Hyper-V Console:
The VMs running on this Hyper-V are configured to start after a reboot - and they are running.
Removing the Computer from the Domain did not restore the access to the Hyper-V Management.
Readding the Computer to the Domain restored the Account back to normal state, but the Hyper-V Management Console still show this same issue.
I've tried access with the following accounts:
EUDENUE-VHOST\administrator
DOMAIN\administrator (Enterprise Admin)
DOMAIN\matthias (Normal User joined as local Administrator on this machine)
Server is Windows Server 2016
any ideas?
P.S.: @Support: I'm open for any diagnosis.
↧
Solved - Remote Management Hyper-V W10 in WORKGROUP from DOMAIN client W10
Hi,
Im got hands on some used iron i want to play with Hyper-V with.
I have a work laptop i want to remote manage a hyper-v setup that not in a domain.
- Hyper-V server:
OS: Windows 10 PRO
IP: 192.168.1.5
Hostname: dev
In domain: NO
- Client:
IP: 192.168.1.10
OS: Windows 10 PRO
Hostname: WRK001
In domain: YES
Anyone know if this is possible and how do i get it up running. Or point me in the right direction.
Have modified the HOSTS file on the client so i can ping the Hyper-V server by it name "dev"
#LnQ¯\_(ツ)_/¯
↧
Windows 2012r2 Hyper-V Gen 2 boot options missing
Ok, I've wasted an entire day searching for an answer for this. I found a few people with the same issue but no answers.
I built a Win10 1607 Gen2 VM. I mounted an ISO to capture windows for SCCM. I cant change my boot settings in Firmware because they are missing.
I went to the CLI in PS and tried Set-VMFirmware -VMName 1607 -BootOrder "DVDDrive","HardDiskDrive"
Set-VMFirmware : Cannot bind parameter 'BootOrder'. Cannot convert the "DVDDrive" value of type "System.String" to
type "Microsoft.HyperV.PowerShell.VMComponentObject".
At line:1 char:40
+ Set-VMFirmware -VMName 1607 -BootOrder "DVDDrive","HardDiskDrive"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Set-VMFirmware], ParameterBindingException
+ FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.HyperV.PowerShell.Commands.SetVMFirmwareCommand
Using
Hyper-V Manager
Microsoft Corporation
Version: 6.3.9600.16384
Has something change in the was this is done? I have 5 Hypervisors all running the same build and none of the gen 2 machines have this option. The Gen1 VM's are fine.
Charles Freukes
↧
Hyper-V 2016 - Cluster, Replica or (stand-alone?) Live Migration
Hi all.
I've got the following hardware:
- HP Proliant DL380p G6, 4 nics, local SAS storage
146 GB RAID 1 - Hyper-V 2016
600 GB RAID 5 - VM STORAGE - HP Proliant DL380p G6, 4 nics, local SAS storage
146 GB RAID 1 - Hyper-V 2016
600 GB RAID 5 - VM STORAGE
From what I've understood, a cluster setup is not possible, since the best practice, in my opinion, is to store the VMs on shared storage, like a SAN. I want to stay far, far away from any other solution, like storage spaces.
That leaves me with Hyper-V replica or stand-alone hosts with live migration?
What do I want to achieve: the same thing I do with Veeam: Host A, hosts VM 1 and 2 Host B, hosts vm 3 and 4.
Host A creates replica's of VMs 1 and 2, every x hours, to host B.
Host B creates replica's of VMs 3 and 4, every x hours, to host A.
VM 1: DC01 on server 2016 (PDC)
VM 2: RDS on server 2016
VM 3: DC02 on server 2016
VM 4: EXC01 on server 2016 (Exchange 2016)
Can this be done, with standard Hyper-V functionality?
I've read that Hyper-V replica should not be used with Exchange?
Do or don't?
I'm also not quite sure what Live Migration is, what's the difference with replica's?
Buying Veeam B&R would be the easy way out, but that's not an option.
Thanks in advance
↧
↧
Moving hyper-v install to hardware
Hi
Can we setup Windows 2016 std + Essentials + Exchange 2016 on hyper-v and once fully tested move this setup to the actual production hardware?
Thanks
Regards
↧
Hyper-V 2012 R2 Cluster Issues
I have the following enviroment:
Active Directory (3 DC's) 2012 R2 Level
5 Nodes Hyper-V Server 2012 R2 Cluster (SMB2 as storage) with two NAS Windows Storage Server 2012 R2 (not CSV)
Each node has two networks (Clients & Cluster, 192.168.x.x, and Cluster 10.2.1.x)
I'm having some random issues, sometimes one server get evicted, when i rejoin that server to the cluster the difficulties appears, even this issues sometimes happens without
any server gettin evicted.
I cannot live migrate vm's to that problematic server, if i do a Quick Migration, the vm's migrates, but when i try to start it there are two possibles results:
- The VM never get started
- The VM moves to another node and then get started
The Clustering are reporting the following errors:
- Cluster node desacluster02 has been evicted from the failover cluster. (EventID 1011, Task Category: Node Mgr)
- The Cluster service failed to bring clustered role 'example' completely online or offline. One or more resources may be in a failed state.
This may impact the availability of the clustered role. (EventID 1205, Task Category: Resource Control Manager)
- Cluster resource 'Virtual Machine Configuration 'example' of type 'Virtual Machine Configuration' in clustered role 'example' failed.
The error code was '0x574' ('The target account name is incorrect.'). (what?!)
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.
Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet. (EventID 1069, Task Category Resource Control Manager)
- Cluster resource 'Virtual Machine Configuration 'example' of type 'Virtual Machine Configuration' in clustered role 'example' failed.
The error code was '0x43' ('The network name cannot be found.'). (what?!)
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.
Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet. (EventID 1069, Task Category Resource Control Manager)
Procedures already done:
- I checked conectivity among the nodes, both networks, and it's ok
- I rejoined the node with the problems
- I verified Sysvol/DFSR replication, it's ok
- I verified the rights/permissions in the NAS servers shares (computers$, and users involved)
Thanks in advance!
Active Directory (3 DC's) 2012 R2 Level
5 Nodes Hyper-V Server 2012 R2 Cluster (SMB2 as storage) with two NAS Windows Storage Server 2012 R2 (not CSV)
Each node has two networks (Clients & Cluster, 192.168.x.x, and Cluster 10.2.1.x)
I'm having some random issues, sometimes one server get evicted, when i rejoin that server to the cluster the difficulties appears, even this issues sometimes happens without
any server gettin evicted.
I cannot live migrate vm's to that problematic server, if i do a Quick Migration, the vm's migrates, but when i try to start it there are two possibles results:
- The VM never get started
- The VM moves to another node and then get started
The Clustering are reporting the following errors:
- Cluster node desacluster02 has been evicted from the failover cluster. (EventID 1011, Task Category: Node Mgr)
- The Cluster service failed to bring clustered role 'example' completely online or offline. One or more resources may be in a failed state.
This may impact the availability of the clustered role. (EventID 1205, Task Category: Resource Control Manager)
- Cluster resource 'Virtual Machine Configuration 'example' of type 'Virtual Machine Configuration' in clustered role 'example' failed.
The error code was '0x574' ('The target account name is incorrect.'). (what?!)
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.
Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet. (EventID 1069, Task Category Resource Control Manager)
- Cluster resource 'Virtual Machine Configuration 'example' of type 'Virtual Machine Configuration' in clustered role 'example' failed.
The error code was '0x43' ('The network name cannot be found.'). (what?!)
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.
Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet. (EventID 1069, Task Category Resource Control Manager)
Procedures already done:
- I checked conectivity among the nodes, both networks, and it's ok
- I rejoined the node with the problems
- I verified Sysvol/DFSR replication, it's ok
- I verified the rights/permissions in the NAS servers shares (computers$, and users involved)
Thanks in advance!
↧
Server 2012 R2 to 2016 Live Migration crashing vmms.exe on 2016
I just installed a new 2016 server and added it to my failover cluster. This cluster has 4 2012 R2 machines that I plan on upgrading to 2016. I can add the server and everything looks fine, but when I try to live migrate machines vmms.exe will crash on the new 2016 server. I can randomly get machines to migrate over, but it is rare. I've also had 1 machine reboot on me during testing. Here is the event log:
Faulting application name: vmms.exe, version: 10.0.14393.351, time stamp: 0x5801a7cf
Faulting module name: vmms.exe, version: 10.0.14393.351, time stamp: 0x5801a7cf
Exception code: 0xc0000005
Fault offset: 0x00000000001e547f
Faulting process id: 0xe00
Faulting application start time: 0x01d233927a1cf2f9
Faulting application path: C:\Windows\system32\vmms.exe
Faulting module path: C:\Windows\system32\vmms.exe
Report Id: 3a054e2b-2f80-4b0d-ba8c-e076bb2171e6
Faulting package full name:
Faulting package-relative application ID:
WER Report:
EventType=APPCRASHEventTime=131224050672381909
ReportType=2
Consent=1
UploadTime=131224050675350714
ReportIdentifier=6be09f5a-9f87-11e6-a945-000af79b5237
IntegratorReportIdentifier=3a054e2b-2f80-4b0d-ba8c-e076bb2171e6
NsAppName=vmms.exe
AppSessionGuid=00000e00-0000-000b-f9f2-1c7a9233d201
TargetAppId=W:0000f519feec486de87ed73cb92d3cac802400000000!00006033da6aeb1cd851e1f9eef7f622e047883f59b7!vmms.exe
TargetAppVer=2016//10//15:03:51:43!dccff6!vmms.exe
BootId=4294967295
Response.BucketId=b28d849c8785d0cb2e441adb1bdf9b02
Response.BucketTable=4
Response.LegacyBucketId=120606991475
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=vmms.exe
Sig[1].Name=Application Version
Sig[1].Value=10.0.14393.351
Sig[2].Name=Application Timestamp
Sig[2].Value=5801a7cf
Sig[3].Name=Fault Module Name
Sig[3].Value=vmms.exe
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.14393.351
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=5801a7cf
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=00000000001e547f
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.14393.2.0.0.400.8
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=99e5
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=99e5b07e68fd23b80ff6104a12265df7
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=c040
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=c040100b60ea022685b390079870e10b
UI[2]=C:\Windows\system32\vmms.exe
UI[5]=Check online for a solution (recommended)
UI[6]=Check for a solution later (recommended)
UI[7]=Close
UI[8]=Virtual Machine Management Service stopped working and was closed
UI[9]=A problem caused the application to stop working correctly. Windows will notify you if a solution is available.
UI[10]=&Close
LoadedModule[0]=C:\Windows\system32\vmms.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\System32\KERNEL32.DLL
LoadedModule[3]=C:\Windows\System32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\System32\ucrtbase.dll
LoadedModule[5]=C:\Windows\System32\sechost.dll
LoadedModule[6]=C:\Windows\System32\RPCRT4.dll
LoadedModule[7]=C:\Windows\System32\combase.dll
LoadedModule[8]=C:\Windows\System32\bcryptPrimitives.dll
LoadedModule[9]=C:\Windows\System32\shcore.dll
LoadedModule[10]=C:\Windows\System32\msvcrt.dll
LoadedModule[11]=C:\Windows\System32\OLEAUT32.dll
LoadedModule[12]=C:\Windows\System32\msvcp_win.dll
LoadedModule[13]=C:\Windows\SYSTEM32\ntmarta.dll
LoadedModule[14]=C:\Windows\System32\WS2_32.dll
LoadedModule[15]=C:\Windows\System32\advapi32.dll
LoadedModule[16]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[17]=C:\Windows\System32\NSI.dll
LoadedModule[18]=C:\Windows\System32\CFGMGR32.dll
LoadedModule[19]=C:\Windows\system32\DEVOBJ.dll
LoadedModule[20]=C:\Windows\System32\CRYPT32.dll
LoadedModule[21]=C:\Windows\System32\MSASN1.dll
LoadedModule[22]=C:\Windows\System32\WINTRUST.dll
LoadedModule[23]=C:\Windows\system32\HTTPAPI.dll
LoadedModule[24]=C:\Windows\system32\sscore.dll
LoadedModule[25]=C:\Windows\system32\SAMLIB.dll
LoadedModule[26]=C:\Windows\system32\RDVGPUINFO.dll
LoadedModule[27]=C:\Windows\system32\vmsif.dll
LoadedModule[28]=C:\Windows\system32\vsconfig.dll
LoadedModule[29]=C:\Windows\system32\vid.dll
LoadedModule[30]=C:\Windows\system32\vmcompute.dll
LoadedModule[31]=C:\Windows\system32\vmprox.dll
LoadedModule[32]=C:\Windows\system32\vmwpctrl.dll
LoadedModule[33]=C:\Windows\system32\framedynos.dll
LoadedModule[34]=C:\Windows\system32\HBAAPI.dll
LoadedModule[35]=C:\Windows\system32\mi.dll
LoadedModule[36]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[37]=C:\Windows\system32\VirtDisk.dll
LoadedModule[38]=C:\Windows\system32\XmlLite.dll
LoadedModule[39]=C:\Windows\system32\SspiCli.dll
LoadedModule[40]=C:\Windows\SYSTEM32\cryptsp.dll
LoadedModule[41]=C:\Windows\system32\samcli.dll
LoadedModule[42]=C:\Windows\system32\netutils.dll
LoadedModule[43]=C:\Windows\system32\DNSAPI.dll
LoadedModule[44]=C:\Windows\system32\DSROLE.dll
LoadedModule[45]=C:\Windows\system32\MPR.dll
LoadedModule[46]=C:\Windows\system32\bcrypt.dll
LoadedModule[47]=C:\Windows\system32\logoncli.dll
LoadedModule[48]=C:\Windows\system32\ncrypt.dll
LoadedModule[49]=C:\Windows\system32\WINHTTP.dll
LoadedModule[50]=C:\Windows\system32\srvcli.dll
LoadedModule[51]=C:\Windows\system32\wkscli.dll
LoadedModule[52]=C:\Windows\system32\USERENV.dll
LoadedModule[53]=C:\Windows\System32\profapi.dll
LoadedModule[54]=C:\Windows\system32\NetSetupApi.dll
LoadedModule[55]=C:\Windows\system32\wevtapi.dll
LoadedModule[56]=C:\Windows\system32\fwpuclnt.dll
LoadedModule[57]=C:\Windows\system32\WMICLNT.dll
LoadedModule[58]=C:\Windows\system32\miutils.dll
LoadedModule[59]=C:\Windows\system32\NTASN1.dll
LoadedModule[60]=C:\Windows\system32\wc_storage.dll
LoadedModule[61]=C:\Windows\system32\bcd.dll
LoadedModule[62]=C:\Windows\system32\FLTLIB.DLL
LoadedModule[63]=C:\Windows\system32\CRYPTBASE.DLL
LoadedModule[64]=C:\Windows\system32\DSPARSE.DLL
LoadedModule[65]=C:\Windows\system32\DPAPI.DLL
LoadedModule[66]=C:\Windows\System32\kernel.appcore.dll
LoadedModule[67]=C:\Windows\System32\user32.dll
LoadedModule[68]=C:\Windows\System32\win32u.dll
LoadedModule[69]=C:\Windows\System32\GDI32.dll
LoadedModule[70]=C:\Windows\System32\gdi32full.dll
LoadedModule[71]=C:\Windows\System32\clbcatq.dll
LoadedModule[72]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[73]=C:\Windows\SYSTEM32\wbemcomn.dll
LoadedModule[74]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[75]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[76]=C:\Windows\SYSTEM32\clusapi.dll
LoadedModule[77]=C:\Windows\system32\cscapi.dll
LoadedModule[78]=C:\Windows\SYSTEM32\gpapi.dll
LoadedModule[79]=C:\Windows\system32\rsaenh.dll
LoadedModule[80]=C:\Windows\system32\rdp4vs.dll
LoadedModule[81]=C:\Windows\system32\AUTHZ.dll
LoadedModule[82]=C:\Windows\system32\mswsock.dll
LoadedModule[83]=C:\Windows\SYSTEM32\WINNSI.DLL
LoadedModule[84]=C:\Windows\SYSTEM32\dhcpcsvc6.DLL
LoadedModule[85]=C:\Windows\SYSTEM32\dhcpcsvc.DLL
LoadedModule[86]=C:\Windows\System32\ole32.dll
LoadedModule[87]=C:\Windows\System32\ACTIVEDS.dll
LoadedModule[88]=C:\Windows\System32\adsldpc.dll
LoadedModule[89]=C:\Windows\System32\WLDAP32.dll
LoadedModule[90]=C:\Windows\system32\VSSAPI.DLL
LoadedModule[91]=C:\Windows\system32\VssTrace.DLL
LoadedModule[92]=C:\Windows\System32\ES.DLL
LoadedModule[93]=C:\Windows\System32\PROPSYS.dll
LoadedModule[94]=C:\Windows\system32\wbem\wmidcprv.dll
LoadedModule[95]=C:\Windows\system32\wbem\wmiutils.dll
LoadedModule[96]=C:\Windows\system32\adsldp.dll
LoadedModule[97]=C:\Windows\SYSTEM32\sxs.dll
LoadedModule[98]=C:\Windows\SYSTEM32\NETAPI32.DLL
LoadedModule[99]=C:\Windows\SYSTEM32\SECUR32.DLL
LoadedModule[100]=C:\Windows\System32\rasadhlp.dll
LoadedModule[101]=C:\Windows\system32\kerberos.DLL
LoadedModule[102]=C:\Windows\system32\cryptdll.dll
LoadedModule[103]=C:\Windows\system32\vss_ps.dll
LoadedModule[104]=C:\Windows\System32\msxml3.dll
LoadedModule[105]=C:\Windows\SYSTEM32\resutils.dll
LoadedModule[106]=C:\Windows\System32\vmsifproxystub.dll
LoadedModule[107]=C:\Windows\system32\wbem\xml\wmi2xml.dll
LoadedModule[108]=C:\Windows\System32\imagehlp.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Virtual Machine Management Service
AppPath=C:\Windows\system32\vmms.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=FB64CA0F9D3575F622A24A4C49736BD8
MetadataHash=-804366191
Also, just to make sure everything was correct I wiped the server and reinstalled 2016 again. I am still getting the same crash.
↧
Hardware serial number of virtual disk in hyper-v
Hyper-V on Server 2012 R2
Is there a way to assign a hardware serial number to a virtual disk in hyper-v. I have an application that references the hard disk serial number for licensing and it appears the serial number is blank to the operating system (server 2012 R2).
I am not looking for the volume serial number I need the hardware serial number.
Get-PhysicalDisk | select uniqueID, serialnumber
when I run this powershell script in the virtual machine I get a blank serial number.
In VMware I can enable the serial number by adding 'disk.EnableUUID' to the configuration file.
thanks
↧
↧
Server 2016 physical and VM machine not communicating with each other
Hi
I installed Win server 2016 and add role of Hyper-V and installed 2 VMs. As per requirement i configure 2 external v switch and add both 2 switch on both servers, Now both VM have 2 Ethernet connection. I give the VM static IP, gateway and DNS as per the actual loop in physical machine. But when i try to ping vm to physical machine it shows "destination host unreachable" and when i try to ping form physical to virtual it shows "request timed out".
I cross check both machines firewall are off and IP is same as per physical machine and the network but still same issue. I enable Vlan identification and gave the same number but still same issue.
again i change my external switch to internal but issue did not resolve.
currently my virtual switch is on external as per below pic.
Kindly suggest any solution for this.
Thanks
Kashan
↧
Pass-through disks are disappearing after configuring MPIO on Windows VM along with Virtual Fiber Channel
I have a Windows 2016 Server (Base System) with Hyper-V enabled with a Windows 2016 VM (Win-VM).
Disks are presented from various Target Arrays to Base System and MPIO is configured. Each disks having four physical paths. Few disks are attached as pass-through disks to Win-VM. And these disks are visible in the Win-VM.
Now I have created two Virtual Fiber Channel (Two Physical port in each VFC) and presented disks from same Target arrays. ThenI have configured MPIO in guest VMs (Win-VM) also.
Here starts my problem.
After configuring MPIO in guest VM that is in my case Win-VM, few pass-through disks are disappearing fromWin-VM.
I have two questions.
- Whether the above scenario is a valid configuration? (Can we use Pass-through disks and VFC disks in same system)
- If it is a valid configuration, why pass-through disks are disappearing?
↧
Upgrade Hyper-V
Hi!
Is it possible to upgrade Hyper-V Version: 6.2.9200.16384 to 6.3.9600.16384 without upgrading Windows 2012 to Windows 2012 R2?
Thanks.
↧
VSS snapshot creation time while backuping with Veeam Backup & Replication 9.0
Hi,
I have the following issue from about September or longer...
In the infrastructure I have one standalone Hyper-V host with couple of VMs hosted via ISCSI and Veeam B&R 9.0 to perform backups of such VMs. At September I noticed that when Veeam create backup for VMs in the Backup Job the process of creating VSS snapshot
(with crash consistent mode - the most basic mode for backup) takes much of time. Firstly it was 1:44min, I didn't changed anything and let veeam perform the backups normaly. After a couple of days I noticed that this VSS snapshot creation process takes
2:41min, again after a couple of days it was 5 minutes, only for creating the VSS snapshot. Normaly I remember that creating VSS Snapshot took not more than 40 or 50 seconds. I started to debug this problem, because the 80% of backup time is only for creating
(now it is 5 minutes) and closing (the same value about 5 minutes) snapshot... I checked that VSS snapshot is created after Veeam starts to create it with vssadmin list shadows command. I can see the VSS snapshot when it is created. Additionally I checked
that the storage for VSS snapshot is sufficient with vssadmin list shadowstorage command - there are no any problems - much of space available, no any old snapshot only this one created by Veeam.
What is more interesting after a few weeks I noticed the same issue on my second infrastrcture where I have one Hyper-V host and Veeam too.
For now I know only one operation which reduces the VSS time to 40 seconds. It is of course reboot the host... But now I have to reboot the hosts every weekend which is not a good idea for me.
I asked Veeam support for such issue, but they don't find any problem and said me that Veeam do nothign that using the native mechanisms of VSS (in a easy words - Veeam only execute the vss commands to create the snapshots. They don't find any interesting in
logs...).
What I can add is that I tested a lot things for example:
- Try to create new Backup Job with test VM - the same result
- Place VM on the local storage of Hyper-V Host (not iscsi storage) - the same result (VSS 5 min)
- Try different distributions of VMs both windows and Linux - the same result...
Do anyone have similiar issue or have idea how to troubleshoot the issue?
Thanks.
Matt.
↧
↧
Hyper-V Manager with non-domain admin
Hello,
I am testing Hyper-V for the first time. I have two Hyper-V 2016 free server setup and I am trying to manage it from Windows 10. I have Hyper-V management tools and all Remote Server Administration Tools installed. I can connect to both servers with Hyper-V Manager as long as I run as a domain admin account. I would like to connect with a standard user.
I added the account I want to use to the Hyper-V Administrators group on both servers. The servers and PC are all joined to the same domain. The domain is 2008 (I will be updating soon) so I do not have Hyper-V administrators at the domain level. I thought adding the user to this group should be the only thing necessary, but I still cannot connect.
Thank you for your help!
↧
Cluster Validation issue
We have two node failover cluster. We could see that all the VM's are got moved to single node and got rebooted multiple times. Events are
1. Isatap
interface isatap.{} is no longer active – 4201 - Iphlpsvc
2. Cluster
node '09' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration
wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs,
switches, or bridges – 1135 - FailoverClustering
3. Cluster
Shared Volume 'Volume1' ('Cluster Disk 2') has entered a paused state because of '(c000020c)'. All I/O will temporarily be queued until a path to the volume is reestablished. – 5120 - FailoverClustering
4. Cluster
resource 'Cluster Disk 1' of type 'Physical Disk' in clustered role 'Cluster Group' failed. Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of
the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet – 1069 – FailoverClustering
5. Isatap
interface isatap.{} with address fd80::5ede:169.254.2.135 has been brought up – 4200 - Iphlpsvc
6. Cluster
resource 'Cluster Disk 1' of type 'Physical Disk' in clustered role 'Cluster Group' failed. Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of
the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet – 1069 – FailoverClustering
7. The
Cluster service failed to bring clustered role 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered role. – 1205 – FailoverClustering
8. Clustered
role 'Cluster Group' has exceeded its failover threshold. It has exhausted the configured number of failover attempts within the failover period of time allotted to it and will be left in a failed state. No additional attempts will be made to bring
the role online or fail it over to another node in the cluster. Please check the events associated with the failure. After the issues causing the failure are resolved the role can be brought online manually or the cluster may attempt to bring it
online again after the restart delay period. – 1254 – FailoverClustering
9. Clustered role 'Cluster Group'
has exceeded its failover threshold. It has exhausted the configured number of failover attempts within the failover period of time allotted to it and will be left in a failed state. No additional attempts will be made to bring the role online
or fail it over to another node in the cluster. Please check the events associated with the failure. After the issues causing the failure are resolved the role can be brought online manually or the cluster may attempt to bring it online again after
the restart delay period – 1177 – FailoverClustering
10. Isatap interface isatap.{}
is no longer active – 4201 – Iphlpsvc
11. The Cluster Service
service entered the stopped state. – 7036 – Service Control Manager
12. The Cluster Service
service terminated with the following service-specific error: A quorum of cluster nodes was not present to form a cluster – 7024 – Service Control Manager
13. The Cluster Service
service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. – 7031 - Service Control Manager
14. The Cluster Service
service entered the running state. – 7036 - Service Control Manager
15. Isatap interface isatap.{}
with address fd80::5ede:169.254.2.81 has been brought up. – 4200 - Iphlpsvc
when I run the Validate Configuration, the "Validate Disk Failover" test fails. The message in the report is "Node Server01.Mydomain.com holds the SCSI PR on Test Disk 0 and brought the disk online, but failed in its attempt to write file data to partition table entry 1. The group or resource is not in the correct state to perform the requested operation."
Any suggestions?
Thanks
Ramasamy R S
↧
File VHD is always growing
Hi All,
I have Hyper-V windows server 2008 R2 with 2 virtual server installed.
Vhd file of one virtual server is always growing whereas there was no file growth in the virtual server, so I always compact the vhd, but the vhd file will grow again.. again.. again...
How to know what the cause?
Note: Before I already ask this topic to windows forum --> https://social.technet.microsoft.com/Forums/id-ID/12ee3755-c600-4244-8bfc-e360847f6e30/file-vhd-is-always-growing?forum=virtualserver
Thanks,
Nana Sutisna
↧
More Pages to Explore .....
