Detect second disk on Windows Server 2012

Hi,
newly installed Windows Server 2012 R2 with two internal harddrives.
The two disks shows up in Disk Manager but only one in File Explorer.
How can i configure the server to expose the second disk in File Explorer?
/Roger

Hi Roger,
Has the problem been solved by online/initializing/assigning drive letter ?
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.

Similar Messages

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.

Disappearing disk space Windows Server 2012 R2 with SharePoint Server 2013 Enterprise

I've got an interesting problem with a virtual machine in our VMWare environment. It is Windows Server 2012 R2 with SharePoint Server 2013 Enterprise installed. I started out with a 60GB disk and it started running out of space, so I increased
it in VMWare and extended the partition to 100GB. Well, that lasted for a bit and so I extended it again. I've done this 3 or 4 times and now I've got a 160GB disk with about 2-3GB of space remaining (and it started with 10GB remaining).
WinDirStat shows 105GB of <Unknown> space being used, which is probably my issue. However, I can't determine what this is and it keeps growing like a tapeworm. The context menu on the <Unknown> files has all the options disabled,
so WinDirStat doesn't appear to have access to whatever the file(s) is/are. I've performed several chkdsk /f on the C: drive and nothing bad is reported. I don't have any restore points and am not running VSS (that I'm aware of). The pagefile
reports as being about 4.9GB, so that's not the issue. No large files are shown anywhere and my explorer settings are set to show me all files, including system files.
When I try to run WinDirStat with elevated permissions, it hangs and becomes unresponsive.
I've even resorted to running CCleaner to see if it found anything, but it simply found the standard temp files and such...about 1GB.
I'm pulling my hair out...and I don't have much to start with. Anyone have any ideas?
Thanks
Russ

It appears that somehow, Microsoft Fusion Assembly binding logging was turned on and many of the temp folders located at c:\users\username\AppData\Local\Microsoft\Windows\InetCache\IE were filling up with hundreds of thousands of Fusion HTM log files.
This is controlled by an entry in the registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion\ForceLog which was set to 1. Hopefully, setting it back to zero will fix the issue. As a result of figuring this out, I have recovered almost 80GB of disk
space occupied by the log files.
I thought WinDirStat would show me what I needed to know, but it turns out TreeSize (which I've used in the past) works much better.
Russ

User Profile Disks with Windows Server 2012 and Windows 8 VDI

Hello experts!
We are building a new server setup for the office and are unable to figure out why UPD will not work. We have VDI setup and a user for instance
connecting through the RDWeb workplace will dynamically get one of the available Windows 8 Machines delivered through Hyper-V and can successfully login on this machine via Active Directory. So far so good...
However, when we activate the User Profile Disks "UPD" feature the login takes forever and the VHDX will not mount on c:\users\...
as expected within the virtual Windows 8 machine.
The UPD config is quite simple, with just the path "\\vmhost\upd\" set. This share has (now during test) full access for everyone,
both on share level and on security level, but still the VHDX will not mount.
The UVHD-template.vhdx file gets created just fine when UPD is activated, and during login through RDWeb a TEMP-UVHD-S-1-5-21-1477358240-4159876597-995667825-500.vhdx
gets created, but there it stops... The login process takes a couple of minutes by the "Windows förbereds" (roughly translated to English "Preparing Windows"), and then the user gets logged in with a temporary profile.
- The event log says (translated using Google translate):
Failed to obtain a user profile disk for the user account with SID S-1-5-21-1477358240-4159876597-995667825-500.
Make sure the location of the user profile desk can be reached, the server's computer account has read and write permissions to the site and that there is a template file for user profile disks at the site.
Name of the virtual desk"font-size:14px;font-family:'Droid Serif', Georgia, 'Times New Roman', serif;color:#222222;line-height:23px;"
/>HRESULT: 0x8007007B.0
Please help, it should not be that hard to achieve this.

Hi,
As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many
similar scenarios.
If the issue still persists and you want to return to this question, please reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer
as you wish.
In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.
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 - Hyper-V - iSCSI SAN - All Hyper-V Guests stops responding and extensive disk read/write

We have a problem with one of our deployments of Windows Server 2012 Hyper-V with a 2 node cluster connected to a iSCSI SAN.
Our setup:
Hosts - Both run Windows Server 2012 Standard and are clustered.
HP ProLiant G7, 24 GB RAM, 2 teamed NIC dedicated to Virtual Machines and Management, 2 teamed NIC dedicated to iSCSI storage. - This is the primary host and normaly all VMs run on this host.
HP ProLiant G5, 20 GB RAM, 1 NIC dedicated to Virtual Machines and Management, 2 teamed NIC dedicated to iSCSI storage. - This is the secondary host that and is intended to be used in case of failure of the primary host.
We have no antivirus on the hosts and the scheduled ShadowCopy (previous version of files) is switched of.
iSCSI SAN:
QNAP NAS TS-869 Pro, 8 INTEL SSDSA2CW160G3 160 GB i a RAID 5 with a Host Spare. 2 Teamed NIC.
Switch:
DLINK DGS-1210-16 - Both the network cards of the Hosts that are dedicated to the Storage and the Storage itself are connected to the same switch and nothing else is connected to this switch.
Virtual Machines:
3 Windows Server 2012 Standard - 1 DC, 1 FileServer, 1 Application Server.
1 Windows Server 2008 Standard Exchange Server.
All VMs are using dynamic disks (as recommended by Microsoft).
Updates
We have applied the most resent updates to the Hosts, WMs and iSCSI SAN about 3 weeks ago with no change in our problem and we continually update the setup.
Normal operation
Normally this setup works just fine and we see no real difference in speed in startup, file copy and processing speed in LoB applications of this setup compared to a single host with 2 10000 RPM Disks. Normal network speed is 10-200 Mbit, but occasionally
we see speeds up to 400 Mbit/s of combined read/write for instance during file repair
Our Problem
Our problem is that for some reason all of the VMs stops responding or responds very slowly and you can for instance not send CTRL-ALT-DEL to a VM in the Hyper-V console, or for instance start task manager when already logged in.
Symptoms (i.e. this happens, or does not happen, at the same time)
I we look at resource monitor on the host then we see that there is often an extensive read from a VHDX of one of the VMs (40-60 Mbyte/s) and a combined write speed to many files in \HarddiskVolume5\System Volume Information\{<someguid and no file extension>}.
See iamge below.
The combined network speed to the iSCSI SAN is about 500-600 Mbit/s.
When this happens it is usually during and after a VSS ShadowCopy backup, but has also happens during hours where no backup should be running (i.e. during daytime when the backup has finished hours ago according to the log files). There is however
not that extensive writes to the backup file that is created on an external hard drive and this does not seem to happen during all backups (we have manually checked a few times, but it is hard to say since this error does not seem leave any traces in event
viewer).
We cannot find any indication that the VMs themself detect any problem and we see no increase of errors (for example storage related errors) in the eventlog inside the VMs.
The QNAP uses about 50% processing Power on all cores.
We see no dropped packets on the switch.
(I have split the image to save horizontal space).
Unable to recreate the problem / find definitive trigger
We have not succeeded in recreating the problem manually by, for instance, running chkdsk or defrag in VM and Hosts, copy and remove large files to VMs, running CPU and Disk intensive operations inside a VM (for instance scan and repair a database file).
Questions
Why does all VMs stop responding and why is there such intensive Read/Writes to the iSCSI SAN?
Could it be anything in our setup that cannot handle all the read/write requests? For instance the iSCSI SAN, the hosts, etc?
What can we do about this? Should we use MultiPath IO instead of NIC teaming to the SAN, limit bandwith to the SAN, etc?

Hi,
> All VMs are using dynamic disks (as recommended by Microsoft).
If this is a testing environment, it’s okay, but if this a production environment, it’s not recommended. Fixed VHDs are recommended for production instead of dynamically expanding or differencing VHDs.
Hyper-V: Dynamic virtual hard disks are not recommended for virtual machines that run server workloads in a production environment
http://technet.microsoft.com/en-us/library/ee941151(v=WS.10).aspx
> This is the primary host and normaly all VMs run on this host.
According to your posting, we know that you have Cluster Shared Volumes in the Hyper-V cluster, but why not distribute your VMs into two Hyper-V hosts.
Use Cluster Shared Volumes in a Windows Server 2012 Failover Cluster
http://technet.microsoft.com/en-us/library/jj612868.aspx
> 2 teamed NIC dedicated to iSCSI storage.
Use Microsoft MultiPath IO (MPIO) to manage multiple paths to iSCSI storage. Microsoft does not support teaming on network adapters that are used to connect to iSCSI-based storage devices. (At least it’s not supported until Windows Server 2008 R2. Although
Windows Server 2012 has built-in network teaming feature, I don’t article which declare that Windows Server 2012 network teaming support iSCSI connection)
Understanding Requirements for Failover Clusters
http://technet.microsoft.com/en-us/library/cc771404.aspx
> I have seen using MPIO suggests using different subnets, is this a requirement for using MPIO
> or is this just a way to make sure that you do not run out of IP adressess?
What I found is: if it is possible, isolate the iSCSI and data networks that reside on the same switch infrastructure through the use of VLANs and separate subnets. Redundant network paths from the server to the storage system via MPIO will maximize availability
and performance. Of course you can set these two NICs in separate subnets, but I don’t think it is necessary.
> Why should it be better to not have dedicated wireing for iSCSI and Management?
It is recommended that the iSCSI SAN network be separated (logically or physically) from the data network workloads. This ‘best practice’ network configuration optimizes performance and reliability.
Check that and modify cluster configuration, monitor it and give us feedback for further troubleshooting.
For more information please refer to following MS articles:
Volume Shadow Copy Service
http://technet.microsoft.com/en-us/library/ee923636(WS.10).aspx
Support for Multipath I/O (MPIO)
http://technet.microsoft.com/en-us/library/cc770294.aspx
Deployments and Tests in an iSCSI SAN
http://technet.microsoft.com/en-US/library/bb649502(v=SQL.90).aspx
Hope this helps!
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Lawrence
TechNet Community Support

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:

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.

Adding second domain controller in Windows server 2012 R2

Hello, our primary domain controller is currently on a machine that has Windows Server 2008 R2 Standard. We are planning to setup a second domain controller as a failover to our primary domain controller. My question is, can we have a secondary domain
controller on a Windows Server 2012 R2 even if our primary domain controller is on a machine that has Windows Server 2008 R2?

I think I found the answer to my question.
http://technet.microsoft.com/en-us/library/dd464018(v=ws.10).aspx
"In Windows Server 2012, Adprep.exe is integrated into the AD DS installation process and runs automatically as needed. For example, when you install the first domain controller that runs Windows Server 2012 into an existing domain and forest, then adprep
/forestprep and adprep /domainprep automatically run and report the results of the operations.
Some organizations may prefer to run Adprep.exe separately in advance of an AD DS installation. For this reason, Adprep.exe is also included in the \Support\Adprep folder of the operating system disk.
In Windows Server 2012, there is only one 64-bit version of Adprep.exe. It can be run remotely from any server that runs a 64-bit version of Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012. The computer where you run it can be either
domain-joined or in a workgroup.
The version of Adprep.exe in Windows Server 2012 includes new syntax and parameter options in order to run it remotely. For more information, see
Adprep."
For more information about the objects and containers that are created when the schema is extended to support Windows Server 2012, see
Windows Server 2012: Changes to Adprep.exe.

After I reinstalled Windows Server 2012 R2, I cannot attach my virtual disk

Hello,
After I reinstalled Windows Server 2012 R2, I cannot attach manually my virtual disk "MOVIES" :
http://windowsitpro.com/systems-management/q-after-i-reinstalled-windows-server-2012-my-storage-spaces-are-no-longer-writabl
When i try this command : (http://technet.microsoft.com/fr-fr/Library/hh848641.aspx)
PS C:\>Connect-VirtualDisk –FriendlyName "MOVIES"I'have this error :PS C:\Windows\system32> Connect-VirtualDisk -FriendlyName "MOVIES"
Connect-VirtualDisk : Failed
Au caractère Ligne:1 : 1
+ Connect-VirtualDisk -FriendlyName "MOVIES"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (StorageWMI:ROOT/Microsoft/...SFT_VirtualDisk) [Connect-VirtualDisk], CimE
   xception
    + FullyQualifiedErrorId : StorageWMI 4,Connect-VirtualDiskI have the same problem with right clic attach on the manage interfaceAll my disks are OKI d'ont understand why i have a problemCould' you help me Tanks in advance for your helpRegards,Nicolas

Hello Elton,
I tried
numerous powershell
command to do anything
but I'm
lack of ideas.
All my disk are OK :
but
how can I do to make a
CheckDisk on a virtual disk because
there is no letter corresponding to the volume
It's only when i try to connect VirtualDisk to my Server
the problem happens ...
I try to repair the virtualDisk with powershell command :
PS C:\Windows\system32> Repair-VirtualDisk -FriendlyName MOVIESIt's works but it takes less than 2 seconds ...There is no solution?
I lost all my data? Can i try to delete virtual disk and recovery data with a recovery program,
is
that it might work?
Thanks you in advance for your help
Regards,
Nicolas

0x8056530b error enabling disk deduplication on Windows Server 2012 R2 Volume - any ideas why or how to fix?

I'm getting the following error when trying to enable disk de-duplication on a volume on my Windows 2012 R2 file server. The error is:
"There was an error updating Data Deduplication on volume: MSFT_DedupVolume.Volume='\\?\Volume{8dfc4322-9997-11e3-93f5-005056a84b9b}\' - HRESULT 0x8056530b, The specified volume type is not supported. Deduplication is supported on fixed, write-enabled
NTFS data volumes and CSV backed by NTFS data volumes."
The volume in question is a 1TB VMFS volume mounted to the virtual machine that is the Windows file server. I could find no info anywhere that references this error as it relates to a standard mounted volume or VMware or VMFS.
Any ideas on what could be the problem or how to fix it? I could find nothing in the log files other than an entry which is basically a repeat of the error above.
Any help would be greatly appreciated.
- ADEHART
P.S. This is a volume that was previously mounted on an older Windows 2003 server. Not sure if that may make a difference.

have you compared this issue to the ones that are successful and compared what is different?
Have you made sure of the following:
Servers
See the following list for server requirements for deduplication:
• Server hardware should meet the minimum requirements for running Windows Server 2012. The deduplication feature was designed to support minimal configurations such as a single processor system with 4 GB of RAM and one SATA hard disk drive.
• If you plan to support deduplication on multiple volumes on the same server, you need to plan an appropriately size for the system to ensure that it can process the data. The general rule is that the server needs 1 CPU-core and 350 MB of free memory to run a deduplication job on a single volume, and that job can process about 100 GB per hour or around 2 TB per day. Deduplication scales with additional CPU core processors and available memory to enable parallel processing of multiple volumes.
For example: If you have a server with 16 CPU core processors and 16 GB of memory, deduplication uses 25% of the system memory in the default Background Processing mode, and in this case, that would be 4 GB. If you divide by 350 MB, you can calculate that the server could process about 11 volumes at a time. If you add 8 GB of memory, the system could process 17 volumes at a time. If you set an optimization job to run in Throughput mode, the system will use up to 50% of the system’s memory for the optimization job.
• Data Deduplication supports up to 90 volumes at a time; however, deduplication can simultaneously process one volume per physical CPU core processor plus one. Hyper-threading does not impact this because only physical core processors can be used to process a volume. A system with 16 CPU core processors and 90 volumes will process 17 volumes at a time until all 90 volumes are done, if there is sufficient memory.
• Virtual server instances should follow the same guidance as physical hardware regarding server resources.
Volumes
Volumes that are candidates for deduplication must conform to the following requirements:
• Must not be a system or boot volume. Deduplication is not supported on operating system volumes.
• Can be partitioned as a master boot record (MBR) or a GUID Partition Table (GPT), and must be formatted using the NTFS file system.
• Can reside on shared storage, such as storage that uses a Fibre Channel or an SAS array, or when an iSCSI SAN and Windows Failover Clustering is fully supported.
• Do not rely on Cluster Shared Volumes (CSVs). You can access data if a deduplication-enabled volume is converted to a CSV, but you cannot continue to process files for deduplication.
• Do not rely on the Microsoft Resilient File System (ReFS).
• Can’t be larger than 64 TB in size.
• Must be exposed to the operating system as non-removable drives. Remotely-mapped drives are not supported.
Note
Files with extended attributes, encrypted files, files smaller than 32 KB, and reparse point files are not processed by deduplication.

HP EVA 8100 - HSV210 - Windows Server 2012 disk display three times

Hi together
I have a problem with a HP EVA 8100 and the Windows Server 2012. When im presenting the disks in the HP Command View to the Server, the harddisk is display three times in the disk management.
Here the view in the HP Command View:
And here on the Server:
On the server i had install all the drivers etc.
It would be great if u could help me.
Thanks alot and kind regards
Lars

Hi Vijay MC,
When we meet the disk id conflict we can try to changed the disk ID of the disk id, you can use uniqueid to generate the new disk.
Uniqueid
http://technet.microsoft.com/en-us/library/cc730793.aspx
The similar thread:
"The disk is offline because it has a signature collision with another disk that is online" .... What can I do to change a hdd signature?____
http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/the-disk-is-offline-because-it-has-a-signature/2e1f20c0-8fbb-4952-a789-a0f1578f1616
I’m glad to be of help to you!

Windows Server 2012 Cluster Validation Failing On List All Potential Cluster Disks

I'm in the process of setting up a new cluster using Windows Server 2012 with a view to migrate from our existing 2008 R2 cluster. I am having problems validating the storage and the wizard keeps failing on the List All Potential Cluster Disks
test (which causes all the other storage tests to be cancelled).
I'm getting the following error:
Failed while verifying removal of any Persistent Reservation on physical disk 19ba99a4 at node RC-HYPERV-3.riddlesdown.local.
When I look in validation report, disk 19ba99a4 is the management LUN (Access LUN 31 as termed by the storage software).
Looking on my 2008 R2 cluster this doesn't appear in Disk Management.
Any ideas how I can get rid of it or the error that it is causing?

Hi,
Thank you for your question.
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Best Regards,
Aiden
TechNet Subscriber Support
If you are
TechNet Subscription
user and have any feedback on our support quality, please send your feedback
here.
Aiden Cao
TechNet Community Support

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

Windows Server 2012 Standard Scheduling for backup for multiple disk

Hi,
Iam using Windows Server 2012 Standard,
How to create backup schedule for multiple hard disk. 1. I have scheduled a multiple backup for disk1, disk2 but the backup fails.
How to create different backup schedule for single Hard disk.
Please help

Hi
Check these artciles,same on 2012 r2 standard;
https://technet.microsoft.com/en-us/library/cc754054.aspx?f=255&MSPPError=-2147217396
https://technet.microsoft.com/en-us/library/dd834883.aspx

Unable to Install Windows Server 2012 R2; system aborts and reboots after first blue Windows logo appears

System: Dell PowerEdge sc1420 with dual xeon and Adaptec 2420SA SATA RAID (supported by OS); 10 GB memory (2x4, rank 2, organization x4, in DIMM1 & DIMM2; 2x1, registered, organization x8, in DIMM3 & DIMM4)
This computer is currently running Windows Server 2008 R2 Enterprise which was installed with no problems.
Objective: clean install of Windows Server 2012 R2 Standard on an otherwise unused RAID array disk set.
All attempts to boot from DVD result in loading of files (grey progress bar on bottom of screen), brief dark screen, then black screen with a blue windows logo for about 2 seconds and then a flash of about 10 lines of error notifications on a black screen
for about 1/4 second (unreadable), and then a reboot of the computer.
Coreinfo.exe confirms that cpus DO support NX and PAE; do NOT support VMX (virtual machine enhancements).
Attempts to run memtest.exe from boot disk tool-menu startup result in an error message that the memtest.exe file is corrupt.
Running memtest.exe from Windows 2008 R2 install disk results in all memory tests passed!
Attempted booting with multiple DVD's (some +R, some -R, all verified) burned from .iso. These DVD's were used successfully to install Windows Server 2012 R2 on an HP Pavilion. Also changed DVD drives just to rule out DVD hardware.
Running CHKDSK from Windows 2012 R2 on HP Pavilion shows no problems; running CHKDSK from Windows 2008 R2 on the Dell system on the same disks shows some problems. Running checkdisk on the Windows 2008 R2 install disk from the Windows 2008 R2 installed
system shows no problems. All disks burned and verified on same system.
Also attempted to boot from USB thumbdrive with copy of DVD on it. Same results: system loads files then reboots at first Windows logo. So that would rule out disk quality issues per se??
Started to try an upgrade rather clean install to see if any errors were announced. None were announced as the system went through much of the process. I aborted somewhere along the way before committing to the upgrade because 1) the most likely
outcome was it would not boot after install (I don't really need the practice in restoring); and 2) even if it did reboot, having a system that can't be repaired by booting the install disk is pointless.
All disks and raid arrays are recognized and usable by RAID controller card and by Windows Server 2008 R2. Disks are within spec for use with Adaptec 2420SA (1TB @ 300).
Is VMX (aka VT-x) actaully required for ANY install even though Hyper-V is not intended to be used? If so, it is too bad that the Microsoft system requirements (
http://technet.microsoft.com/en-us/library/dn303418.aspx ) don't make that clear. And lack of VMX support really doesn't explain the memtest.exe "corruption" issue.
Or is it maybe something unique about the files on 2012 R2 disk (or disk image on USB) that are causing some problem with the chipset processing? But why?
My vote would be for the latter of the issues, but I have no clue why or if it is remediable. Suggestions?

So here is what I think is the final understanding of this problem:
First, one additional piece of important information: The computer successfully moves into and through the Windows Boot Loader phase and succeeding phase ONLY for Windows 8.1 32-bit, but NOT for Windows 8.1 64-bit nor for Windows
Server 2012 R2 (only 64-bit).
The Windows Boot Manager phase (which precedes the Windows Boot Loader phase) is either 32-bit or 64-bit (64 –bit for this case) and is loaded by the 16-bit stub program (Bootmgr) which starts in real mode.
Windows Boot Loader of course runs in either 32-bit or 64-bit (64 –bit for this case) according to the product being installed.
By inference, the essential problem is occurring in conjunction with the loading of a WIM file to start the Windows Boot Manager.
The boot manager starts ok and generally shows its essential screens (Windows Boot Manager; Advanced Boot Options) or proceeds to load files for transition into Windows startup in the succeeding Windows Boot Loader phase (that doesn’t “boot” but rather
loads the system). This is best confirmed by the announced corruption of the memtest.exe file when selecting Windows Memory Diagnostic from the Windows Boot Manager Screen.
If allowed to continue loading files to pass control to the Windows Boot Manager, the type of abort and resulting immediate restart that occurs is that which you would associate with unhandled cpu exceptions (invalid instruction, memory out of range,
wild interrupt, etc.) that most of us have not commonly seen for 20 years (since beginning to use well behave OS’s from Windows NT 3.1 and on).
So, the problem obviously is due to a failure to properly mount the WIM file and/or properly access it (probably the latter) when running in 64-bit protected mode.
This is independent of the hardware on which the install disk is actually mounted (DVD or USB-flash), so it is NOT a hardware problem
per se.
Since the WIM is mounted early in the process, Boot Manager may well have loaded it using BIOS routines to access the physical device on which it resides rather than loading 32-bit or 64-bit drivers of its own.
Hence, if the BIOS does not “mount” the WIM in a way that is later fully compatible with access from the 64-bit systems being loaded, it could cause apparent file corruption.
If it is only partially incompatible some functionality may appear quite usable (like loading files) until later detected.
This is vague on my part, because the exact nature of the incompatibility cannot be readily determined from the information available.
But the consequence is the same: the system cannot boot from the install disk, either for initial installation or repairs.
Incidental conclusion: The 64-bit boot manager code for Windows Server 2008 does not exhibit this faulty behavior, but the 64-bit code for Windows Server 2012 does.
So the problem is not inherent with loading 64-bit server OS’s.
Expectations: If the system were to be upgraded using the features of the install disk while running an installed OS, say Windows Server 2008 R2, it might well succeed and yield a fully functional system upgraded to Windows Server 2012
R2 (because the installed operating system is started from discrete files, not from a WIM file).
However, in order to perform a disaster recovery using Windows resources (such as image backups from Windows Server Backup), one would have to presumably boot from a Windows Server 2012 64-bit install disk or Windows Server USB recovery drive.
Of course we know that the Windows Server install disk will not boot and we can be fairly sure that the problem will migrate to any Windows Server USB recovery drive that is created.
My inspection of a Windows 7 System Repair CD shows that is based exclusively on boot.wim, not discrete files!
Of course a generated image for a WIM for Windows 2012 USB recovery drive
might not have the flaw that drives this behavior, but it probably would.
Problem conclusion: A BIOS upgrade would be required for compatibility with Windows Server 2014 clean installation
and any maintenance; and none is available from the OEM.
Problem not resolved, but understood for future reference.
Thanks to Tim whose comments helped me focus my thinking.

Detect second disk on Windows Server 2012

Similar Messages

Maybe you are looking for