Virtual RAID Array Migration to Windows Server 2012 R2 Disk offline, Degraded, Detached and split

My Residential server is used as a file and web server, however i also use it for learning so it has grown slow over the last couple of years, i now need to get it working ready for when i go to UNI. I have upgraded from windows server 2012 Standard to windows
server 2012r2 standard, i am on the same server, but have put a SSD as my primary drive(so i still have the old hard drive and can go back to that to get my data)
 I have also done a BIOS update, so the logical disks (a 2TB RAID 1 with all my important documents) are not showing up on the RAID Configuration in the BIOS.
By changing settings i have managed to get the array to show up on server manager > File and storage services>Volumes>Storage Pools. however there are a number of exclamation marks shown next to the drive(s) 
I read in a Technet
Article that i should "set
the storage pool to read-write " 
 I did this and then in the storage pool box at the top the exclamation mark says "Warning: Degraded".
 In the Virtual Disks box (bottom left) the exclamation mark says "Unknown: Detached" and in the Physical Disks box (bottom right) it says "Warning Split" on the second disk. 
I have disconnected all other Hard drives, however if i can't get my documents back will have to go back to windows server 2012. Any ideas would be greatly appreciated.
Michael Booth

Hi,
It seems that the second disk is failed, you need to add a new disk to the storage pool to replace the failed disk.
Degraded Storage Spaces Storage Pool after single HDD failure
http://social.technet.microsoft.com/Forums/en-US/3a7e2a7d-4ad7-48cc-8165-0d6673e37436/degraded-storage-spaces-storage-pool-after-single-hdd-failure?forum=winserveressentials
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

  • Windows Server 2012 Logical Disk Free Space (%) Low

    I enabled the monitor "Windows Server 2012 Logical Disk Free Space (%) Low" and configured a low threshold to test. I started to get a bunch of warnings from servers, for example:
    The disk \\?\Volume{ee0222ed-16de-40a5-af89-f95db3fdf5a4} on computer PC is running out of disk space. The value that exceeded the threshold is 11% free space.
    Now I checked on the server, and all the disks have more than 11% free space. Additionally, I don't see any disks with such a name/guid.
    When looking at the additional knowledge of the monitor, I see that it is using the following information:
    Object Name: Logical Disk
    Counter Name: PercentFree 
    My question is where is this disk coming from, and how can I avoid these disks from creating false alarms? When looking in the Windows Server
    From my analyzing the DB, I see that these are the partitions on the server without a volume letter. Any way to avoid getting these discovered and/or alerts, without overriding each one?

    Hi,
    These "strange" disks are called mount points.
    They get discovered by the "Mount Point Discovery Rule".
    Go to your authoring => rules => search for the rule above and disable it.
    If you want to remove all the instances in your environment you need to use Remove-SCOMDisabledClassInstance
    powershell cmdlet.
    More info on the cmdlet can be found here:  http://technet.microsoft.com/en-us/library/hh920257%28v=sc.20%29.aspx
    If you have any more questions please do not hesitate to ask
    It's doing common things uncommonly well that brings succes. Check out my SCOM link blog:
    SCOM link blog

  • [Forum FAQ] How to install and configure Windows Server Essentials Experience role on Windows Server 2012 R2 Standard via PowerShell locally and remotely

    As we all know,
    the Windows Server Essentials Experience role is available in Windows Server 2012 R2 Standard and Windows Server 2012 R2 Datacenter. We can add the Windows Server
    Essentials Experience role in Server Manager or via Windows PowerShell.
    In this article, we introduce the steps to install and configure Windows
    Server Essentials Experience role on Windows Server 2012 R2 Standard via PowerShell locally and remotely. For better analyze, we divide this article into two parts.
    Before installing the Windows Server Essentials Experience Role, please use
    Get-WindowsFeature
    PowerShell cmdlet to ensure the Windows Server Essentials Experience (ServerEssentialsRole) is available. (Figure 1)
    Figure 1.
    Part 1: Install Windows Server Essentials Experience role locally
    Add Windows Server Essentials Experience role
    Run Windows PowerShell as administrator, then type
    Add-WindowsFeature ServerEssentialsRole cmdlet to install Windows Server Essentials Experience role. (Figure 2)
    Figure 2.
    Note: It is necessary to configure Windows Server Essentials Experience (Post-deployment Configuration). Otherwise, you will encounter following issue when opening Dashboard.
    (Figure 3)
    Figure 3.
      2. Configure Windows Server Essentials Experience role
    (1)  In an existing domain environment
    Firstly, please join the Windows Server 2012 R2 Standard computer to the existing domain through the path:
    Control Panel\System\Change Settings\”Change…”\Member of. (Figure 4)
    Figure 4.
    After that, please install Windows Server Essentials Experience role as original description. After installation completed, please use the following command to configure Windows
    Server Essentials:
    Start-WssConfigurationService –Credential <Your Credential>
    Note: The type of
    Your Credential should be as: Domain-Name\Domain-User-Account.
    You must be a member of the Enterprise Admin group and Domain Admin group in Active Directory when using the command above to configure Windows Server Essentials. (Figure 5)
    Figure 5.
    Next, you can type the password for the domain account. (Figure 6)
    Figure 6.
    After setting the credential, please type “Y” to continue to configure Windows Server Essentials. (Figure 7)
    Figure 7.
    By the way, you can use
    Get-WssConfigurationStatus
    PowerShell cmdlet to
    get the status of the configuration of Windows Server Essentials. Specify the
    ShowProgress parameter to view a progress indicator. (Figure 8)
    Figure 8.
    (2) In a non-domain environment
    Open PowerShell (Run as Administrator) on the Windows Server 2012 R2 Standard and type following PowerShell cmdlets: (Figure 9)
    Start-WssConfigurationService -CompanyName "xxx" -DNSName "xxx" -NetBiosName "xxx" -ComputerName "xxx” –NewAdminCredential $cred
    Figure 9.
    After you type the commands above and click Enter, you can create a new administrator credential. (Figure 10)
    After creating the new administrator credential, please type “Y” to continue to configure Windows Server Essentials. (Figure 11)
    After a reboot, all the configurations will be completed and you can open the Windows Server Essentials Dashboard without any errors. (Figure 12)
    Figure 12.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    Part 2: Install and configure Windows Server Essentials Experience role remotely
    In an existing domain environment
    In an existing domain environment, please use following command to provide credential and then add Server Essentials Role: (Figure 13)
    Add-WindowsFeature -Name ServerEssentialsRole
    -ComputerName xxx -Credential DomainName\DomainAccount
    Figure 13.
    After you enter the credential, it will start install Windows Server Essentials role on your computer. (Figure 14)
    Figure 14.
    After the installation completes, it will return the result as below:
    Figure 15.
    Next, please use the
    Enter-PSSession
    cmdlet and provide the correct credential to start an interactive session with a remote computer. You can use the commands below:
    Enter-PSSession –ComputerName
    xxx –Credential DomainName\DomainAccount (Figure 16)
    Figure 16.
    Then, please configure Server Essentials Role via
    Add-WssConfigurationService cmdlet and it also needs to provide correct credential. (Figure 17)
    Figure 17.
    After your credential is accepted, it will update and prepare your server. (Figure 18)
    Figure 18.
    After that, please type “Y” to continue to configure Windows Server Essentials. (Figure 19)
    Figure 19.
    2. In a non-domain environment
    In my test environment, I set up two computers running Windows Server 2012 R2 Standard and use Server1 as a target computer. The IP addresses for the two computers are as
    below:
    Sevrer1: 192.168.1.54
    Server2: 192.168.1.53
    Run
    Enable-PSRemoting –Force on Server1. (Figure 20)
    Figure 20.
    Since there is no existing domain, it is necessary to add the target computer (Server1) to a TrustedHosts list (maintained by WinRM) on Server 2. We can use following command
    to
    add the TrustedHosts entry:
    Set-Item WSMan:\localhost\Client\TrustedHosts IP-Address
    (Figure 21)
    Figure 21.
    Next, we can use
    Enter-PSSession
    cmdlet and provide the correct credential to start an interactive session with the remote computer. (Figure 22)
    Figure 22.
    After that, you can install Windows Server Essentials Experience Role remotely via Add-WindowsFeature ServerEssentialsRole cmdlet. (Figure 23)
    Figure 23.
    From figure 24, we can see that the installation is completed.
    Figure 24.
    Then you can use
    Start-WssConfigurationService cmdlet to configure Essentials Role and follow the steps in the first part (configure Windows Server Essentials Experience in a non-domain environment) as the steps would be the same.
    The figure below shows the status of Windows Server Essentials.
    Figure
    25.
    Finally, we have successfully configured Windows Server Essentials on Server1. (Figure 26)
    Figure 26.
    More information:
    [Forum
    FAQ] Introduce Windows Powershell Remoting
    Windows Server Essentials Setup Cmdlets
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

  • Problems PXE booting Gen 2 Virtual Machines after Upgrading to Windows Server 2012 R2

    My Current Setup: 
    I have two virtual machines set up with Hyper V on my Windows Server 2012 Server.
    VM1: Configured to boot from an ISO file and runs Clonezilla server. 
    VM2: Configured to PXE boot using a legacy network adapter, and with a passthrough 250Gb hard disk. 
    These two VMs are connected to an external Virtual Switch, which allows physical machines to PXE boot to the Clonezilla server. 
    For the past few months I have been using this setup for two purposes:
    1. To clone physical machines to the Clonezilla virtual server (as a backup).
    2. To restore those image to the second VM if I find that need to get access to the files on the original image.. 
    This has worked perfectly, except for the fact that the speed of the legacy network adapter on the second VM (which is required to PXE boot) is very slow. But I know this is because of the limitations in how the legacy adapter works... 
    Now my problem:
    I found out that Gen 2 VMs allow you to PXE boot without having use a legacy network adapter, allowing me to image back to the VM faster. So I upgraded the Server to Server 2012 R2 . I then created the same two virtual machines on the R2 server. I can still
    PXE boot the Gen 1 VM to the Clonezilla Server but I cannot get the Gen 2 VMs to PXE boot properly. They get an IP address from the Clonezilla Server but then just stop with the following screen. (note: I have disabled the Secure Boot). 
    Are Gen 2 VMs unable to pull down images from anything other than a WDS Server? 

    Hi J,
    >>Unfortunately WDS is not a solution for us as it is dependent on the PC being part of a domain
    If you would like to make the client not join to the domain, please check the box before “Do not join the client to a domain after an installation.”  In addition, make sure not to set the client to the domain in the unattend file and do not prestage
    the computer in AD. "
    It is quoted from following thread :
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/1026c3a9-0a10-4a58-a48f-5391659a96c8/wds-set-unattend-file-for-workgroup?forum=winserversetup
    Best Regards
    Elton Ji
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Windows Server 2012 HyperV VMs becoming extremely sluggish and slow

    I have recently set up a new system for a client consisting of a single Dell T320 server with Xeon E5-2350 2.2GHz 6 core cPU and 32GB of RAM.  Windows Server 2012 Standard is installed on the bare metal, and runs only the HyperV role.  It is not
    joined to any domains.
    It hosts two VMs, one a Windows Server 2012 Standard VM containing the RDS related roles acting as remote desktop server, with 10GB RAM allocated and 3 cores.  Only 5 people use the terminal server concurrently.
    The second VM is a Windows Server 2008 R2 based primary domain controller, with 16GB of RAM allocated and 3 cores.  It runs the AD role, as well as Exchange and GFI MailEssentials 2012.  Avira is also installed on this VM.
    The problem is that the system will function properly for 3-4 days, then suddenly it goes into a state where a multitude of applications would start consuming inordinate amount of CPU time, and become very, very slow.  Almost like the hypervisor goes
    into a software emulation mode where everything runs like molasses.  This affects BOTH VMs equally.  For example, Exchange and GFI on the Windows 2008 R2 VM together consume about 25% CPU, most of it is spent in kernel CPU time.  At the same
    time, in the other Windows Server 2012 VM, svchost, Taskmgr, WMIPrvSE, LogonUI, Explorer,  sqlservr, wsmprovhost etc. will all consume a total of about 70% CPU time, this time 99% of this is user time, not kernel time.  When one user starts any application,
    be that internet explorer, firefox or TaxPrep, the CPU spikes up to 100%.  
    All while nobody is using the system, the system is idle and no mails are flowing in or out of the system.  A reboot of the VMs does not fix anything, even a reboot of the host server does not fix anything.  When I yanked out the two power supplies
    and performed a hardware diagnostic (which came back 100% OK), it booted up and the slowness was gone for 3 days, until today when it started acting up again like I described above.  
    One more thing, when the system behaves normally the sunspider javascript benchmark in IE10 takes 316ms to execute (average) on the HyperV host operating system.  When the system goes slow like this, I pause the two VMs in HyperV then run sunspider
    again, only to be greeted by an average time of 5084ms.  So this clearly does not only affect the virtual machines but the host operating system as well. My gut still tells me the hypervisor is getting messed up somehow.
    Any ideas?  This is a major problem and I have no idea what is causing it.  

    We have had the EXACT same thing happen with a Dell T320 on two separate servers. The first one was running SQL Server 2008 with nothing else funny going on. It ran fine for a month or so, then it developed this slowness issue. We finally installed SQL on
    a loaner box (without Hyper-V) and it worked fine. We brought the T320 back to our shop and tested the hell out of it with Dell's assistance and it was NTF. Took it back onsite and moved an SBS 2011 VM over to it. After a few days, it ground to a halt. CPU
    utilization was 100%. I started shedding services, killing Exchange, Sharepoint, etc. Even stripped to the essentials, the CPU was still up in the 60-70% range. 
    I put a T310 out onsite and downed the guest SBS vm. I copied the HUGE vhd over to the T310 (running Server 2008r2 with the Hyper-V role) and it ran perfectly. CPU at about 2-4%, spiking to 15% occasionally.
    We finally concocted a story that the USB controller was bad, so they replaced the motherboard (not the CPUs) and it all seems to be working OK now after we sunk at least 100 man-hours into the problem.
    Our second one is a similar setup. T320, Server 2012, Hyper-V role, SBS 2011 Standard and a couple of member servers running basic apps. No one can find any problem and everyone acts like this is something new, although my posting comes one year after Tim's
    original posting.
    MCP SBSC

  • ADPrep Migration from Windows Server 2003 to 2012 Foundation Server fails with error 0x80004005

    Hi all,
    Having a problem the forums and Google have been unsuccessful in helping me with. Server is Windows 2003 R2, migrating to Windows Server 2012 foundation.  Have tried the AD Migration on the new 2012 Foundation server both as a standalone server
    and a domain server member before running the migration.  I get the following error:
    ADPrep execution failed --> System.ComponentModel.Win32Exception (0x80004005): A device attached to the system is not functioning
    I've checked the ADprep logs and have found the following:
    [2013/01/22:11:15:01.000]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is cn=abd97102-88dd-4013-a009-0e2c2f967ff6,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=apl,DC=local.
    [2013/01/22:11:15:01.001]
    LDAP API ldap_search_s() finished, return code is 0x0 
    [2013/01/22:11:15:01.001]
    Adprep checked to verify whether operation cn=abd97102-88dd-4013-a009-0e2c2f967ff6,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=apl,DC=local has completed.
    [Status/Consequence]
    The operation GUID already exists so Adprep did not attempt to rerun this operation but is continuing.
    [2013/01/22:11:15:01.001]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is cn=134428a8-0043-48a6-bcda-63310d9ec4dd,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=apl,DC=local.
    [2013/01/22:11:15:01.001]
    LDAP API ldap_search_s() finished, return code is 0x20 
    [2013/01/22:11:15:01.001]
    Adprep verified the state of operation cn=134428a8-0043-48a6-bcda-63310d9ec4dd,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=apl,DC=local. 
    [Status/Consequence]
    The operation has not run or is not currently running. It will be run next.
    [2013/01/22:11:15:01.021]
    Adprep was unable to complete because the call back function failed. 
    [Status/Consequence]
    Error message: Unable to access the computer "SERVER.apl.local". The network path was not found.
     (0x80070035).
    [User Action]
    Check the log file ADPrep.log, in the C:\Windows\debug\adprep\logs\20130122111500 directory for more information.
    DSID Info:
    DSID: 0x1811132a
    winerror = 0x1f
    NT BUILD: 9200
    NT BUILD: 16384
    [2013/01/22:11:15:01.021]
    Adprep was unable to update forest information. 
    [Status/Consequence]
    Adprep requires access to existing forest-wide information from the schema master in order to complete this operation.
    [User Action]
    Check the log file, ADPrep.log, in the C:\Windows\debug\adprep\logs\20130122111500 directory for more information. 
    We did have AVAST Antivirus installed on the server but this was removed.  Any idea's?
    Jason.
    Consultant | Nerd | Visionary. http://www.ethertech.com.au/ | http://www.deeperstates.com.au

    Hi Biswajit et. al., thanks for your help thus far, it is greatly appreciated...
    Unfortunately I had already disabled the NIC's on both hosts.  They currently remain disabled.  I've just tried turning off IPv6 as well and no luck.
    PortQry came back fine (I think) :)
    =============================================
     Starting portqry.exe -n server.apl.local -e 135 -p TCP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 135 (epmap service): LISTENING
    Using ephemeral source port
    Querying Endpoint Mapper Database...
    Server's response:
    UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
    ncalrpc:[dhcpcsvc]
    UUID: f1ec59ab-4ca9-4c30-b2d0-54ef1db441b7 Isolation Communication Endpoint
    ncalrpc:[LRPC00001d40.00000001]
    UUID: f1ec59ab-4ca9-4c30-b2d0-54ef1db441b7 Isolation Communication Endpoint
    ncalrpc:[LRPC00001448.00000001]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncalrpc:[OLE4EF57D32A0DB45F9A64653468D7C]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncalrpc:[LRPC000012ac.00000001]
    UUID: 2f5f6521-cb55-1059-b446-00df0bce31db Unimodem LRPC Endpoint
    ncacn_np:\\\\SERVER[\\pipe\\tapsrv]
    UUID: 2f5f6521-cb55-1059-b446-00df0bce31db Unimodem LRPC Endpoint
    ncalrpc:[tapsrvlpc]
    UUID: 2f5f6521-cb55-1059-b446-00df0bce31db Unimodem LRPC Endpoint
    ncalrpc:[unimdmsvc]
    UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service
    ncalrpc:[W32TIME_ALT]
    UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service
    ncacn_np:\\\\SERVER[\\PIPE\\W32TIME_ALT]
    UUID: 6bffd098-a112-3610-9833-46c3f874532d 
    ncalrpc:[OLE7C4E3B9B79D8492CBA384F149E08]
    UUID: 6bffd098-a112-3610-9833-46c3f874532d 
    ncacn_ip_tcp:10.0.0.3[1111]
    UUID: 6bffd098-a112-3610-9833-46c3f874532d 
    ncalrpc:[DHCPSERVERLPC]
    UUID: 5b821720-f63b-11d0-aad2-00c04fc324db 
    ncalrpc:[OLE7C4E3B9B79D8492CBA384F149E08]
    UUID: 5b821720-f63b-11d0-aad2-00c04fc324db 
    ncacn_ip_tcp:10.0.0.3[1111]
    UUID: 5b821720-f63b-11d0-aad2-00c04fc324db 
    ncalrpc:[DHCPSERVERLPC]
    UUID: 3d267954-eeb7-11d1-b94e-00c04fa3080d 
    ncalrpc:[LRPC00000480.00000001]
    UUID: 3d267954-eeb7-11d1-b94e-00c04fa3080d 
    ncacn_np:\\\\SERVER[\\pipe\\HydraLsPipe]
    UUID: 3d267954-eeb7-11d1-b94e-00c04fa3080d 
    ncacn_ip_tcp:10.0.0.3[1092]
    UUID: 12d4b7c8-77d5-11d1-8c24-00c04fa3080d 
    ncalrpc:[LRPC00000480.00000001]
    UUID: 12d4b7c8-77d5-11d1-8c24-00c04fa3080d 
    ncacn_np:\\\\SERVER[\\pipe\\HydraLsPipe]
    UUID: 12d4b7c8-77d5-11d1-8c24-00c04fa3080d 
    ncacn_ip_tcp:10.0.0.3[1092]
    UUID: 493c451c-155c-11d3-a314-00c04fb16103 
    ncalrpc:[LRPC00000480.00000001]
    UUID: 493c451c-155c-11d3-a314-00c04fb16103 
    ncacn_np:\\\\SERVER[\\pipe\\HydraLsPipe]
    UUID: 493c451c-155c-11d3-a314-00c04fb16103 
    ncacn_ip_tcp:10.0.0.3[1092]
    UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe 
    ncalrpc:[OLE43978C47C6F54B5499302BAB2F50]
    UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe 
    ncacn_ip_tcp:10.0.0.3[1090]
    UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe 
    ncalrpc:[LRPC00001060.00000001]
    UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe 
    ncacn_np:\\\\SERVER[\\pipe\\WinsPipe]
    UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45 
    ncalrpc:[OLE43978C47C6F54B5499302BAB2F50]
    UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45 
    ncacn_ip_tcp:10.0.0.3[1090]
    UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45 
    ncalrpc:[LRPC00001060.00000001]
    UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45 
    ncacn_np:\\\\SERVER[\\pipe\\WinsPipe]
    UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
    ncalrpc:[OLE92F283EA5C2F497093CE6A52B7D8]
    UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
    ncacn_ip_tcp:10.0.0.3[1067]
    UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
    ncalrpc:[LRPC00000d10.00000001]
    UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
    ncalrpc:[OLE92F283EA5C2F497093CE6A52B7D8]
    UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
    ncacn_ip_tcp:10.0.0.3[1067]
    UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
    ncalrpc:[LRPC00000d10.00000001]
    UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
    ncalrpc:[OLE92F283EA5C2F497093CE6A52B7D8]
    UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
    ncacn_ip_tcp:10.0.0.3[1067]
    UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
    ncalrpc:[LRPC00000d10.00000001]
    UUID: 50abc2a4-574d-40b3-9d66-ee4fd5fba076 
    ncacn_ip_tcp:10.0.0.3[1048]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncalrpc:[LRPC000004d4.00000001]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncacn_ip_tcp:10.0.0.3[1032]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncalrpc:[LRPC000004d4.00000001]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncacn_ip_tcp:10.0.0.3[1032]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncalrpc:[LRPC000004d4.00000001]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncacn_ip_tcp:10.0.0.3[1032]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncalrpc:[LRPC000004d4.00000001]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncacn_ip_tcp:10.0.0.3[1032]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncacn_np:\\\\SERVER[\\PIPE\\lsass]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncalrpc:[audit]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncalrpc:[securityevent]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncalrpc:[protected_storage]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncalrpc:[dsrole]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncacn_ip_tcp:10.0.0.3[1026]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncalrpc:[NTDS_LPC]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncacn_http:10.0.0.3[1027]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncacn_np:\\\\SERVER[\\PIPE\\lsass]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncalrpc:[audit]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncalrpc:[securityevent]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncalrpc:[protected_storage]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncalrpc:[dsrole]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncacn_ip_tcp:10.0.0.3[1026]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncalrpc:[NTDS_LPC]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncacn_http:10.0.0.3[1027]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncacn_np:\\\\SERVER[\\PIPE\\lsass]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncalrpc:[audit]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncalrpc:[securityevent]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncalrpc:[protected_storage]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncalrpc:[dsrole]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncacn_ip_tcp:10.0.0.3[1026]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncalrpc:[NTDS_LPC]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncacn_http:10.0.0.3[1027]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncacn_np:\\\\SERVER[\\PIPE\\lsass]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncalrpc:[audit]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncalrpc:[securityevent]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncalrpc:[protected_storage]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncalrpc:[dsrole]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncacn_ip_tcp:10.0.0.3[1026]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncalrpc:[NTDS_LPC]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncacn_http:10.0.0.3[1027]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncacn_np:\\\\SERVER[\\PIPE\\lsass]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncalrpc:[audit]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncalrpc:[securityevent]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncalrpc:[protected_storage]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncalrpc:[dsrole]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncacn_ip_tcp:10.0.0.3[1026]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncalrpc:[NTDS_LPC]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncacn_http:10.0.0.3[1027]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncacn_np:\\\\SERVER[\\PIPE\\lsass]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncalrpc:[audit]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncalrpc:[securityevent]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncalrpc:[protected_storage]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncalrpc:[dsrole]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncacn_ip_tcp:10.0.0.3[1026]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncalrpc:[NTDS_LPC]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncacn_http:10.0.0.3[1027]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncacn_np:\\\\SERVER[\\PIPE\\lsass]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncalrpc:[audit]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncalrpc:[securityevent]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncalrpc:[protected_storage]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncalrpc:[dsrole]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncacn_ip_tcp:10.0.0.3[1026]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncalrpc:[NTDS_LPC]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncacn_http:10.0.0.3[1027]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncalrpc:[OLE8B33809919104CE5B44970B01637]
    UUID: 1ff70682-0a51-30e8-076d-740be8cee98b 
    ncalrpc:[wzcsvc]
    UUID: 1ff70682-0a51-30e8-076d-740be8cee98b 
    ncalrpc:[OLE396AE4FBEFCC4DD2B44D0F0A3691]
    UUID: 1ff70682-0a51-30e8-076d-740be8cee98b 
    ncacn_np:\\\\SERVER[\\PIPE\\atsvc]
    UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f 
    ncalrpc:[wzcsvc]
    UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f 
    ncalrpc:[OLE396AE4FBEFCC4DD2B44D0F0A3691]
    UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f 
    ncacn_np:\\\\SERVER[\\PIPE\\atsvc]
    UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53 
    ncalrpc:[wzcsvc]
    UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53 
    ncalrpc:[OLE396AE4FBEFCC4DD2B44D0F0A3691]
    UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53 
    ncacn_np:\\\\SERVER[\\PIPE\\atsvc]
    UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
    ncalrpc:[DNSResolver]
    Total endpoints found: 125
    ==== End of RPC Endpoint Mapper query response ====
    portqry.exe -n server.apl.local -e 135 -p TCP exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 389 -p BOTH ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 389 (ldap service): LISTENING
    Using ephemeral source port
    Sending LDAP query to TCP port 389...
    LDAP query response:
    currentdate: 01/28/2013 14:11:54 (unadjusted GMT)
    subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=apl,DC=local
    dsServiceName: CN=NTDS Settings,CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
    namingContexts: DC=apl,DC=local
    defaultNamingContext: DC=apl,DC=local
    schemaNamingContext: CN=Schema,CN=Configuration,DC=apl,DC=local
    configurationNamingContext: CN=Configuration,DC=apl,DC=local
    rootDomainNamingContext: DC=apl,DC=local
    supportedControl: 1.2.840.113556.1.4.319
    supportedLDAPVersion: 3
    supportedLDAPPolicies: MaxPoolThreads
    highestCommittedUSN: 1310788
    supportedSASLMechanisms: GSSAPI
    dnsHostName: SERVER.apl.local
    ldapServiceName: apl.local:[email protected]
    serverName: CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
    supportedCapabilities: 1.2.840.113556.1.4.800
    isSynchronized: TRUE
    isGlobalCatalogReady: TRUE
    domainFunctionality: 2
    forestFunctionality: 2
    domainControllerFunctionality: 2
    ======== End of LDAP query response ========
    UDP port 389 (unknown service): LISTENING or FILTERED
    Using ephemeral source port
    Sending LDAP query to UDP port 389...
    LDAP query response:
    currentdate: 01/28/2013 14:11:57 (unadjusted GMT)
    subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=apl,DC=local
    dsServiceName: CN=NTDS Settings,CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
    namingContexts: DC=apl,DC=local
    defaultNamingContext: DC=apl,DC=local
    schemaNamingContext: CN=Schema,CN=Configuration,DC=apl,DC=local
    configurationNamingContext: CN=Configuration,DC=apl,DC=local
    rootDomainNamingContext: DC=apl,DC=local
    supportedControl: 1.2.840.113556.1.4.319
    supportedLDAPVersion: 3
    supportedLDAPPolicies: MaxPoolThreads
    highestCommittedUSN: 1310788
    supportedSASLMechanisms: GSSAPI
    dnsHostName: SERVER.apl.local
    ldapServiceName: apl.local:[email protected]
    serverName: CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
    supportedCapabilities: 1.2.840.113556.1.4.800
    isSynchronized: TRUE
    isGlobalCatalogReady: TRUE
    domainFunctionality: 2
    forestFunctionality: 2
    domainControllerFunctionality: 2
    ======== End of LDAP query response ========
    UDP port 389 is LISTENING
    portqry.exe -n server.apl.local -e 389 -p BOTH exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 636 -p TCP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 636 (ldaps service): LISTENING
    portqry.exe -n server.apl.local -e 636 -p TCP exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 3268 -p TCP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 3268 (msft-gc service): LISTENING
    Using ephemeral source port
    Sending LDAP query to TCP port 3268...
    LDAP query response:
    currentdate: 01/28/2013 14:11:57 (unadjusted GMT)
    subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=apl,DC=local
    dsServiceName: CN=NTDS Settings,CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
    namingContexts: DC=apl,DC=local
    defaultNamingContext: DC=apl,DC=local
    schemaNamingContext: CN=Schema,CN=Configuration,DC=apl,DC=local
    configurationNamingContext: CN=Configuration,DC=apl,DC=local
    rootDomainNamingContext: DC=apl,DC=local
    supportedControl: 1.2.840.113556.1.4.319
    supportedLDAPVersion: 3
    supportedLDAPPolicies: MaxPoolThreads
    highestCommittedUSN: 1310788
    supportedSASLMechanisms: GSSAPI
    dnsHostName: SERVER.apl.local
    ldapServiceName: apl.local:[email protected]
    serverName: CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
    supportedCapabilities: 1.2.840.113556.1.4.800
    isSynchronized: TRUE
    isGlobalCatalogReady: TRUE
    domainFunctionality: 2
    forestFunctionality: 2
    domainControllerFunctionality: 2
    ======== End of LDAP query response ========
    portqry.exe -n server.apl.local -e 3268 -p TCP exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 3269 -p TCP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 3269 (msft-gc-ssl service): LISTENING
    portqry.exe -n server.apl.local -e 3269 -p TCP exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 53 -p BOTH ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 53 (domain service): LISTENING
    UDP port 53 (domain service): LISTENING
    portqry.exe -n server.apl.local -e 53 -p BOTH exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 88 -p BOTH ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 88 (kerberos service): LISTENING
    UDP port 88 (kerberos service): LISTENING or FILTERED
    portqry.exe -n server.apl.local -e 88 -p BOTH exits with return code 0x00000002.
    =============================================
     Starting portqry.exe -n server.apl.local -e 445 -p TCP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 445 (microsoft-ds service): LISTENING
    portqry.exe -n server.apl.local -e 445 -p TCP exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 137 -p UDP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    UDP port 137 (netbios-ns service): LISTENING or FILTERED
    Using ephemeral source port
    Attempting NETBIOS adapter status query to UDP port 137...
    Server's response: MAC address 000423c733ec
    UDP port: LISTENING
    portqry.exe -n server.apl.local -e 137 -p UDP exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 138 -p UDP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    UDP port 138 (netbios-dgm service): LISTENING or FILTERED
    portqry.exe -n server.apl.local -e 138 -p UDP exits with return code 0x00000002.
    =============================================
     Starting portqry.exe -n server.apl.local -e 139 -p TCP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 139 (netbios-ssn service): LISTENING
    portqry.exe -n server.apl.local -e 139 -p TCP exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 42 -p TCP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 42 (nameserver service): LISTENING
    portqry.exe -n server.apl.local -e 42 -p TCP exits with return code 0x00000000.
    Jason.
    Consultant | Nerd | Visionary. http://www.ethertech.com.au/ | http://www.deeperstates.com.au

  • Cluster Quorum Disk failing inside Guest cluster VMs in Hyper-V Cluster using Virtual Disk Sharing Windows Server 2012 R2

    Hi, I'm having a problem in a VM Guest cluster using Windows Server 2012 R2 and virtual disk sharing enabled. 
    It's a SQL 2012 cluster, which has around 10 vhdx disks shared this way. all the VHDX files are inside LUNs on a SAN. These LUNs are presented to all clustered members of the Windows Server 2012 R2 Hyper-V cluster, via Cluster Shared Volumes.
    Yesterday happened a very strange problem, both the Quorum Disk and the DTC disks got the information completetly erased. The vhdx disks themselves where there, but the info inside was gone.
    The SQL admin had to recreated both disks, but now we don't know if this issue was related to the virtualization platform or another event inside the cluster itself.
    Right now I'm seen this errors on one of the VM Guest:
     Log Name:      System
    Source:        Microsoft-Windows-FailoverClustering
    Date:          3/4/2014 11:54:55 AM
    Event ID:      1069
    Task Category: Resource Control Manager
    Level:         Error
    Keywords:      
    User:          SYSTEM
    Computer:      ServerDB02.domain.com
    Description:
    Cluster resource 'Quorum-HDD' 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.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-FailoverClustering" Guid="{BAF908EA-3421-4CA9-9B84-6689B8C6F85F}" />
        <EventID>1069</EventID>
        <Version>1</Version>
        <Level>2</Level>
        <Task>3</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2014-03-04T17:54:55.498842300Z" />
        <EventRecordID>14140</EventRecordID>
        <Correlation />
        <Execution ProcessID="1684" ThreadID="2180" />
        <Channel>System</Channel>
        <Computer>ServerDB02.domain.com</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="ResourceName">Quorum-HDD</Data>
        <Data Name="ResourceGroup">Cluster Group</Data>
        <Data Name="ResTypeDll">Physical Disk</Data>
      </EventData>
    </Event>
    Log Name:      System
    Source:        Microsoft-Windows-FailoverClustering
    Date:          3/4/2014 11:54:55 AM
    Event ID:      1558
    Task Category: Quorum Manager
    Level:         Warning
    Keywords:      
    User:          SYSTEM
    Computer:      ServerDB02.domain.com
    Description:
    The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-FailoverClustering" Guid="{BAF908EA-3421-4CA9-9B84-6689B8C6F85F}" />
        <EventID>1558</EventID>
        <Version>0</Version>
        <Level>3</Level>
        <Task>42</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2014-03-04T17:54:55.498842300Z" />
        <EventRecordID>14139</EventRecordID>
        <Correlation />
        <Execution ProcessID="1684" ThreadID="2180" />
        <Channel>System</Channel>
        <Computer>ServerDB02.domain.com</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="NodeName">ServerDB02</Data>
      </EventData>
    </Event>
    We don't know if this can happen again, what if this happens on disk with data?! We don't know if this is related to the virtual disk sharing technology or anything related to virtualization, but I'm asking here to find out if it is a possibility.
    Any ideas are appreciated.
    Thanks.
    Eduardo Rojas

    Hi,
    Please refer to the following link:
    http://blogs.technet.com/b/keithmayer/archive/2013/03/21/virtual-machine-guest-clustering-with-windows-server-2012-become-a-virtualization-expert-in-20-days-part-14-of-20.aspx#.Ux172HnxtNA
    Best Regards,
    Vincent Wu
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Windows server 2012: migration from 2012 standard evaluation version to 2012R2

    Hello.
    Is it possible то migrate
    FROM: windows server 2012 standard evaluation
    TO: windows server 2012R2 standard
    And if it is possible then "how to"?
    Activation product key for 2012 is NOT available. 
    Activation product key (MAK, "open licence") for 2012R2 is available. 
    The key for 2012R2 does not "open" 2012 evaluation version.
    Thanks.

    Upgrade means moving from your existing operating system release to a more recent release, while staying on the same hardware. For example, if your server is running Windows Server 2012, you can upgrade it to Windows Server 2012 R2. You
    can upgrade from an evaluation version of the operating system to a retail version, from an older retail version to a newer version, or, in some cases, from a volume-licensed edition of the operating system to an ordinary retail edition.
    ref : http://technet.microsoft.com/en-us/library/dn303416.aspx
    Arnav Sharma | Facebook |
    Twitter Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members
    reading the thread.

  • DirectAccess Client not connecting without error code on Windows Server 2012 R2 and Windows 8.1

    Hello,
    we are currently migrating from Windows Server 2012 to 2012 R2 and are not able to get the new Direct Access Service up and running. Our goal is to establish DirectAccess connection for a handful of clients using the IPHTTPS-adapter on the default port 443.
    Errors:
    There is actually no error showing up. It seems the infrastructure tunnel cannot be created but none of the IPv6-transition adapters is connecting (teredo and 6-to-4 are down) and the IPHTTPs adapter gives no informations about a problem:
    >Get-DAConnectionStatus
    Status    : Error
    Substatus : CouldNotContactDirectAccessServer
    >Get-NetIPHttpsState
    LastErrorCode   : 0x0
    InterfaceStatus : Failed to connect to the IPHTTPS server; waiting to reconnect
    Setup:
    Our setup is a virtualized Windows Server 2012 R2 Standard running on Hyper-V. It is located behind a NAT having the Port 443 mapped to the server. The only role installed after the basic install is RRAS including DirectAccess and VPN. The assistants completed
    successfully (running the configuration for DirectAccess and VPN). Operation Status says everything is green und working (for multiple days in the meanwhile). A previous direct access installation (on a different machine running Windows Server 2012) has
    been removed before installing the new server. The new installation is using a different router, so this might also be the cause of a problem.
    The client is a Windows 8.1 notebook located outside the company network accessing the internet through another NAT-device. The client has been able to connect to the previous DirectAccess setup but has never been able to establish a connection after the
    setup of the new Direct Access server. The device has no outbound constraints concerning the NAT-device and is only running the integrated Windows Firewall.
    Diagnosis:
    So far I've done some basic DNS and connectivity checks. The DNS-name can be resolved correctly and the router even responds to pings. The port forward is working and HTTPs connections are generally possible (temporarily routed the port to
    access the NLS-Website located on the server, which worked fine).
    Network monitor shows that both computers are communicating, traffic on the expected Port 443 is incoming on the server and responses from the server reach the client.
    Opening the IPHTTPs-url and in an endless page load. Sometime the browser page closes but I've never seen any result. Using telnet on the port shows that the server is accepting connections. I've even build a small test application that does a GET-Request
    on the URL returning HTTP-200 and no content.
    I'm currently running out of ideas what to do and since no error occurs this is kind of a bit frustrating. Any help appreciated.
    Regards
    Matthias

    Hi,
    In addition, have you disabled the DA client components on the DA client? If no, please also check
    the settings on the Name Resolution Policy Table.
    More information:
    DirectAccess
    Client Location Awareness – NRPT Name Resolution
    In addition, error 0x4C9 means the remote computer refused the network connection. It may be due to the invalid
    registry or corrupt drivers. For more detailed information, please refer to the link below:
    Error 1225 - Error Code 0x4C9
    Note:
    Microsoft is providing this information as a convenience to you. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
    Best regards,
    Susie

  • Windows Server 2012 Used: Error Message from Windows 7 PC: Remote session was disconnected because there are no remote desktop license servers available to provide a license. Please contact the server administrator.

    We are using Windows Server 2012 Standard installed in VMWare / Virtual machine and to access this we use vSphere client and Remote Desktop Connection / service was already enabled and was working fine with User PCs / laptops remote desktop into the server
    2012, until it gave an error message of: Remote session was disconnected because there are no remote desktop license servers available to provide a license.  Please contact the server administrator. whilst logging into the server. 
    We DON'T use Active Directory nor and we don't use domain and not looking to use it any-time soon. 
    I checked the RD Licensing Diagnoser and it says the grace period has expired and the licensing mode for the remote desktop session host server is not configured.  I have checked the Remote Desktop Gateway has been stopped and I tried to start it and it
    resumed to stop, here I assume its where the licensing part comes in to re-enabled this. 
    I have been trying to follow these articles online: http://ryanmangansitblog.com/2013/03/27/deploying-remote-desktop-gateway-rds-2012/ and http://www.concurrency.com/blog/rds8-add-a-licensing-server-2/#Install  the overview part that I cannot get into,
    because I think we have to be is AD DS for this which we don't.  Is there a way around this for non domain / just standalone set-up?  Is it a must / requirement we need to be in a domain in order for Remote Desktop Connection to work? 
    Also, we have a Windows Server 2012 RDS CALs - 10 (software and licence key), will the licence key work for the Windows 2012 Server Standard?  We do not want to install the other Server mentioned which comes with CAL / licence key as its time consuming
    to reinstall other programs.  I have installed  Server role service of Remote Desktop Licencing and automatically installed other associated services needed.  in the RD Licencing Manager, the Server had a red cross and I "Activate Server"
    where I followed: http://www.concurrency.com/blog/rds8-add-a-licensing-server-2/#Install in Install Licences section and I have used the licence key of CAL - 10 mentioned above; it stated I have successfully completed the install licences wizard and displayed:
    10 Windows Server 2012 - RDS Per User CAL installed, and in the RD Licensing Manager the server turned into a green tick and added the licence.  
    I then tested the Remote desktop connection from my PC and the same error message was there and checked the RD Licensing Diagnoser and the same error messages was there.  I haven't restart the services of Remote Gateway / the server itself; do I really
    need to reboot server?  
    Any advice / guidance would be very much appreciated and this is a urgent matter.  
    Thank you for your time.

    Hotfix Released here:
    http://support.microsoft.com/kb/2916846

  • Does Oracle 11g 32-bit  can run on Windows Server 2012 (64 bit) ?

    Hello!
    I´ve bought Oracle 11g Standard Edition One 4 years ago, (Release 1 11.1.0.6.0 )
    and installed on a Windows Server 2008 (32-bit)
    We ara planning migrate out BD to a new server with Windows Server 2012 (64-bits)
    Can i install and use that Oracle version on the new server ?
    or
    Can i download and use the same version @ 64-bit with the licence i have with the 32-bit version?
    or
    Do i need to purchase a new Oracle version specially for 64bits?
    Thanks in advance

    Hello, me again... (sorry for insist)
    4 years ago, we purchased and use an Oracle 11g Standard Edition One Release 1 ( 11.1.0.6.0) @ 32 bits, and runs very good on a winsvr 2008 @32 bits.
    I was told i can run Oracle without problems on a WinSvr 2008 @ 64bits
    So we'd like to move it to a new server (WinSvr2012 @64bits)
    So my question is
    * Can we download and use it legally a 64 bit version, or we need to purchase another licence?
    * If so, where can i download it?
    Thanks in advance

  • Failover Cluster Manager : Add node wizard Error " This operation returned because the timeout period expired" Windows Server 2012

    Hi Everybody,
    I have two node cluster and trying to add the third node (which is a Virtual Machine), all nodes are in different subnet and can communication with each other. While adding the third node it gives the error at the end of wizard "  This operation
    returned because the timeout period expired ". My domain controller is 2008 Enterprise Server and nodes are all running Windows Server 2012 Standard Edition. Any idea what is causing the issue.
    thanks 

    Hi,
    Before you add a server (node) to a failover cluster, we strongly recommend that you run the Validate a Configuration Wizard for the existing cluster nodes and the new node
    or nodes. The Validate a Configuration Wizard helps you confirm the configuration in a variety of important ways. For example, it validates that the server to be added is connected correctly to the networks and storage and that it contains the same software
    updates. Please post the error or warning report.
    Please try to install the Recommended hotfixes and updates for Windows Server 2012-based failover clusters:
    Recommended hotfixes and updates for Windows Server 2012-based failover clusters
    http://support.microsoft.com/kb/2784261
    Hope this helps.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Windows Server 2012 Essentials and Microsoft SQL Server 2014 Standard Core Edition

    Our company is planning to buy Windows Server 2012 R2 Essentials edition (Volume license) and install it on Citrix Xenserver based virtual machine with 4 virtual processor cores. Can we install Microsoft SQL Server 2014 Standard Core Edition (2 licenses
    for 2 cores) and run it on this virtual machine?

    you can install SQL Server Standard 2014/2012 on the Essentials Windows Server but without Server core Installation while installing SQL Server 2014 is supported on the Server Core mode of the following editions of Windows Server:
    Windows Server 2012 R2 Datacenter 64-bit
    Windows Server 2012 R2 Standard 64-bit
    Windows Server 2012 Datacenter 64-bit
    Windows Server 2012 Standard 64-bit
    Windows Server 2008 R2 SP1 Datacenter 64-bit
    Windows Server 2008 R2 SP1 Enterprise 64-bit
    Windows Server 2008 R2 SP1 Standard 64-bit
    Windows Server 2008 R2 SP1 Web 64-bit
    http://msdn.microsoft.com/en-us/library/ms143506.aspx
    thanks
    diramoh
     

  • Windows Server 2012 Standard License and VMs

    Hi,
    With one Window server 2012 Standard activated license, I will get 2 VMs. So is there a limit with Windows Server 2012 standard license I can stack and the the number of VMs I can create on one server or across servers (virtual environment). Consider that
    all Windows server 2012 standard licenses are activated. If there is no limit on VM creation by add Standard license then why did Microsoft come with Data center licenses with unlimited VMs.
    How does the standard license work on Vmware environment. Is there a limit on the number for VMs that we can create.
    Please advise me.
    Thanks. 

    If i had one server 2012 standard with its key, i could run it as a vm but not as a virtual host without having the license right?
    a single WS2012STD license, allows you to run a server machine (hardware), if that hardware has no more than 2 processors. In this case, you can run 2 VMs, each VM is running WS2012STD. You can also run WS2012STD as the host hypervisor via Hyper-V.
    So, that's really 3 OS installations, on the same 2proc machine. The limitation is that the host hypervisor OS is only permitted to do Hyper-V stuff, it's not permitted to use that OS for anything other than hypervisor functions.
    If you implement in this way, you would only have purchased a single license for WS2012STD, so you would only have a single key, so you would use that key for the 3 OS installations.
    If i bought the single server 2012 standard license, i'd be able to install it as a Host and activate with the key and it'd give me rights to run 2vms on it and for those vms i would have to have 2 keys to activate after installing server 2012 standart
    software on them right?
     see above.
    if you buy via Volume Licensing, things change a little bit due to MAK/KMS keys (it gets a whole lot simpler :)
    Sorry for being unclear on the clusters part, i meant HA/failover. we have 2 2008R2 enterprise servers in cluster with shared storage and i was trying to clarify how could i add more vms there.  
     assuming your failover solution involves traditional server hardware, each failover node is just another hardware machine, so, for each node you have to count up the procs and VMs, just as you would do for non-failover implementations.
    if a server is installed and running/executing, it needs to be licensed.
    with current configuration, each server is hosting 2vms and if anything happens single host can accommodate all four. I am assuming we have 2 enterprise licenses for them, but if i wanted to run 4vms on each host, we have to buy 2 more enterprise licenses
    and install vm togerther with their keys?
    There is no Enterprise for WS2012? (WS2012 has STD and DCE)
    do you mean as in WS2008R2ENT ?
    You can re-assign licenses from one machine to another machine (under the Volume Licensing terms. I'm not sure about Retail terms, you should check that). There are limitations on how often you can reassign licenses (no more than every 90days)
    If hardware "fails", you are allowed to reassign the license in a shorter period than 90days.
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • Windows Server 2012 R2 RDS + User profile Disks + App-V = Explorer.exe crashing all of the time

    I have built a new RDS farm on Windows Server 2012 R2 with two Session Hosts and a combined Connect Broker/Web Access server. I had the farm up and running with User Profile Disks and all seemed OK. However, as soon as I installed the App-V 5.0 SP2 RDS
    client on the session hosts, the explorer.exe process started crashing for any user logging in via the Web Access site. The process crashes and restarts every five to ten seconds. It's the same for administrators. If they log in via Web Access explorer.exe
    crashes, but if they RDP directly to one of the session hosts explorer.exe is fine. If I reboot the session hosts, then the first user to log in via Web Access has a stable desktop session (and appears to have a new profile as well). However, if that user
    logs out and back in again, explorer.exe starts crashing again. The only applications I have packaged at the moment are Office 2013 and Firefox.
    I tried disabling User Profile Disks, but this caused a whole bunch of other problems and I eventually lost the ability to log in at all via Web Access (errors about the user profile service). As this is a small pre-production environment I completed scrapped
    all of the servers and rebuilt from scratch. Again, everything appeared fine until I installed the App-V client, then explorer.exe started crashing repeatedly for all users.
    Has anyone come across this issue before? I have tried installing the App-V 5.0 SP2 Hotfix Package 2, but this didn't help. I have read in a few forums that App-V doesn't work very well with User Profile Desks, but I have not heard of this particular issue.
    Similarly, SP2 seems to have a lot of problems, so I am going to try removing App-V RDp Client SP2 and installing SP1. I ahev also deleted User Profile Disks for the test users to recreate their profiles, but this didn't help either.
    Any other suggestions welcome!

    I forgot to include the application event log entry for explorer.exe crashing:
    Faulting application name: explorer.exe, version: 6.3.9600.17039, time stamp: 0x53156588
    Faulting module name: KERNELBASE.dll, version: 6.3.9600.17055, time stamp: 0x532954fb
    Exception code: 0xc06d007e
    Fault offset: 0x0000000000005bf8
    Faulting process id: 0xae8
    Faulting application start time: 0x01cfab3a273787fd
    Faulting application path: C:\Windows\explorer.exe
    Faulting module path: C:\Windows\system32\KERNELBASE.dll
    Report Id: 69210d77-172d-11e4-80c6-0050560102d1
    Faulting package full name: 

Maybe you are looking for