File systems available on Windows Server 2012 R2?

What are the supported file systems in Windows Server 2012 R2? I mean the complete list. I know you can create, read and write on Fat32, NTFS and ReFS. What about non-Microsoft file systems, like EXT4 or HFS+? If I create a VM with a Linux OS, will
I be able to acces the virtual hard disk natively from WS 2012 R2, or will I need a third party tool, like the one from Paragon? If I have a drive formated in EXT4 or HFS+, will I be able to acces it from Windows, without any third party tool? Acces it,
I mean both read and write on them. I know that on the client OS, Windows 8.1, this is not possible natively, this is why I am asking here, I guess it is very possible for the server OS to have build-in support for accesing thoose file systems. If Hyper-V
has been optimised to run not just Windows VMs, but also Linux VMs, it would make sense to me that file systems like thoose from Linux or OS X to be available using a build-in feature. I have tried to mount the vhd from a Linux VM I have created in HyperV,
Windows Explorer could not read the hard drive.

Installed Paragon ExtFS free. With it loaded, tried to mount on Windows Explorer a ext4 formated vhd, created on a Linux Hyper-V vm, it failed, and Paragon ExtFS crashed. Uninstalled Paragon ExtFS. The free version was not supported on WS 2012 R2
by Paragon, if Windows has no build-in support for ext4, this means this free software has not messed around anything in the OS, I guess.
Don't mess with third-party kernel-mode file systems as it's basically begging for troubles: crash inside them will make whole system BSOD and third-party FS are typically buggy... Because a) FS development for Windows is VERY complex and b) there are very
few external adopters so not that many people actually theist them. What you can do however:
1) Spawn an OS with a supported FS inside VM and configure loopback connectivity (even over SMB) with your host. So you'll read and write your volume inside a VM and copy content to / from host.
(I personally use this approach in a reversed direction, my primary OS is MacOS X but I read/write NTFS-formatted disks from inside a Windows 7 VM I run on VMware Fusion)
2) Use user-mode file system explorer (see sample links below, I'm NOT affiliated with that companie). So you'll copy content from the volume as it would be some sort of a shell extension.
Crashes in 1) and 2) would not touch your whole OS stability.
HFS Explorer for Windows
http://www.heise.de/download/hfsexplorer.html
Ext2Read
http://sourceforge.net/projects/ext2read/
(both are user-land applications for HFS(+) and EXT2/3/4 accordingly)
Hope this helped :)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Similar Messages

Is there a 32 Bit edition available for windows server 2012 and windows server 2008

Dear All,
Is there a 32 Bit edition available for windows server 2012 and windows server 2008?
Regards,
Ahmed

Hi,
Quote：
All editions of Windows Server 2008 R2 are 64-bit only.
Reference link below(session Supported upgrade paths):
https://technet.microsoft.com/en-us/library/dd379511(v=ws.10).aspx
And based on MS official description about system requirement for Windows Server 2012/2012 R2, we may find out that they only has 64 bit OS.
Best Regards,
Eve Wang
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Hyper-V 2012 High Availability using Windows Server 2012 File Server Storage

Hi Guys,
Need your expertise regarding hyper-v high availability. We setup 2 hyper-v 2012 host in our infra for our domain consolidation project. Unfortunately, we don't have hardware storage that is said to be a requirement that we can use to create a failover cluster
for hyper-v host to implement HA. Here's the setup:
Host1
HP Proliant L380 G7
Windows Server 2012 Std
Hyper-V role, Failover Cluster Manager and File and Storage Services installed
Host2
Dell PowerEdge 2950
Windows Server 2012 Std
Hyper-V role, Failover Cluster Manager and File and Storage Services installed
Storage
Dell PowerEdge 6800
Windows Server 2012 Std
File and Storage Services installed
I'm able to configure the new feature about Shared Nothing Live Migration - i'm able to move VM's back and fort between my hosts without storage. But this is planned and proactive approach. My concern is to have my hyper-v host to become highly available in
the event of system failure. If my host1 dies, the VMs should go/move to host2 and vice versa. In setting this up, i believe i need to enable the failover clustering between my hyper-v hosts which i already did but upon validation, it says "No disks
were found on which to perform cluster validation tests." Is it possible to cluster it using just a regular windows file server? I've read about SMB 3.0 and i've configured it as well i'm able to save VMs on my file server, but i don't think that my hyper-v
hosts are already highly available.
Any feedback and suggestions or recommendation is highly appreciated. Thanks in advance!

Hi Guys,
Need your expertise regarding hyper-v high availability. We setup 2 hyper-v 2012 host in our infra for our domain consolidation project. Unfortunately, we don't have hardware storage that is said to be a requirement that we can use to create a failover cluster
for hyper-v host to implement HA. Here's the setup:
Host1
HP Proliant L380 G7
Windows Server 2012 Std
Hyper-V role, Failover Cluster Manager and File and Storage Services installed
Host2
Dell PowerEdge 2950
Windows Server 2012 Std
Hyper-V role, Failover Cluster Manager and File and Storage Services installed
Storage
Dell PowerEdge 6800
Windows Server 2012 Std
File and Storage Services installed
I'm able to configure the new feature about Shared Nothing Live Migration - i'm able to move VM's back and fort between my hosts without storage. But this is planned and proactive approach. My concern is to have my hyper-v host to become highly available in
the event of system failure. If my host1 dies, the VMs should go/move to host2 and vice versa. In setting this up, i believe i need to enable the failover clustering between my hyper-v hosts which i already did but upon validation, it says "No disks were
found on which to perform cluster validation tests." Is it possible to cluster it using just a regular windows file server? I've read about SMB 3.0 and i've configured it as well i'm able to save VMs on my file server, but i don't think that my hyper-v hosts
are already highly available.
Any feedback and suggestions or recommendation is highly appreciated. Thanks in advance!
Your shared storage is a single point of failure with this scenario so I would not consider the whole setup as a production configuration... Also setup is both slow (all I/O is travelling down the wire to storage server, running VMs from DAS is ages faster)
and expensive (third server + extra Windows license). I would think twice about what you do and either deploy a built-in VM replication technologies (Hyper-V Replica) and apps built-in clustering features that does not require shared storage (SQL Server and
Database Mirroring for example, BTW what workload do you run?) or use some third-party software creating fault tolerant shared storage from DAS or investing into physical shared storage hardware (HA one of course).
Hi VR38DETT,
Thanks for responding. The hosts will cater a domain controller (on each host), Web filtering software (Websense), Anti-Virus (McAfee ePO), WSUS and an Auditserver as of the moment. Is the Hyper-V Replica somewhat give "high availability" to VMs or Hyper-V
hosts? Also, is the cluster required in order to implement it? Haven't tried that but worth a try.

When will ADMT/PES be available for Windows Server 2012?

Having upgraded to Windows Server 2012 I would like to trash the AD and take users and their passwords across to a new domain. The main reason for this is that the AD still has a load of hacks in it from Exchange 2007 to segregate address
books. I want to tidy things up ready for Exchange 2013 so I'm building a new domain.
To get the passwords across I need to run PES on the old domain with a key generated on the new domain. ADMT 3.2 will not support this.
So my question is when is ADMT 3.3 (guessing) and PSE for Win2012 going too be released?

Hi,
Just checking in to see if the suggestions were helpful. Please let us know if you would like further assistance.
TechNet Subscriber Support
If you are
TechNet Subscription
user and have any feedback on our support quality, please send your feedback
here.
Yan Li
TechNet Community Support

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.

Creating System Restore Points in Windows Server 2012

Searching for "Create a restore point" on Windows Server 2012, brings up a link that when clicked takes you to System Properties. Once there, there is no System Protection tab or option to create a system restore point. Windows Server Backup
is installed and functioning.
Is this feature available in Windows Server 2012? Was it replaced with Shadow Copies for Shared Folders?
Thanks for any insight you can provide.

HI,
To create a system restore point, run msconfig.exe, that will launch a UI, click the tools tab, select system restore, that should invoke a UI which asks if you want to restore to an earlier version or do you want to create a new restore point. I clicked
"create a new restore point" The problem that I ran into is that when I click that button is I receive the error: can't find "C:\Windows\System32\rstrui.exe". That's the .exe which supports the "Create / restore point' processes. I
posted a question about the missing .exe on the windows > windows 8.1 > Repair and recovery forum and was told to post it here. :>) The subject title of that post is "rstrui.exe Create a system restore point on windows server 8 Standard".
That post documents the steps that I followed trying to create a system restore point. (FYI: I'm not trying to backup any drives. I know what a system restore point is and what backup is. They are two different animals). I want to create a restore
point prior in order to prep for installing an App. So, If a problem occurs; the registry keys and app files can be backed out to some extent. BTW: Create system restore point on windows 8.1does work perfectly well, there's a different UI. I just didn't
know where to post the initial problem.regards,Steve

Error -51 when trying to copy file to windows server 2012

When I try to copy a file from OSX to windows server 2012 share, it acts like its going to start and i get a pinwheel and finder is acting slow and finally error -51. although it does seem to copy over the folder with correct name but no files inside. I had this issue on mavericks as well and now on yosemite beta. Please help!
Jarrod

If the drive is formatted HFS then you are limited to 32 characters on a file name. If it is formatted HFS + then you can have file names as long as 255 characters. I am not familiar withi the format you say the drive is formatted in so I can't speak to it.
If you are receiving -50 errors that can indicate a file name that is too long OR an illegal character in the filename regardless of its length.
If you are actually using 10.3.8 as your profile states then that may be part of the problem. Many of these problems existed in 10.3.X but were fixed in 10.4
I remember that 10.3.8 had issues copying to external drives when there were more than a certain number of characters in a filename. I don't remember the number but for some reason 10 or 12 is what comes to mind. It caused me many problems when I would try and copy files to a Zip disk that I used to have. Since I updated to 10.4 those issues have never occured again.
Since you know what folder the problematic files are in why not just open the folder and try to copy files one at a time. When you get to the one(s) that is a problem, change the file name to something shorter.
A better solution would be to update to 10.4 but with 10.5 coming out sometime in the Spring of 2007 this may not be the time.

Windows Server 2012 R2 file sharing

How can I put File Sharing on in Windows Server 2012 R2? Every time I put it on, the next time ita off again.
Besta regarsa
Nikorios

Hi Nikorios,
This issue occurs for one of the following reasons:
The dependency services for Network Discovery are not running.
The Windows firewall or other firewalls do not allow Network Discovery.
You could refer to the article below to resolve the issue:
You cannot turn on Network Discovery in Network and Sharing Center in Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012
https://support.microsoft.com/kb/2722035/en-us
Regads,
Mandy
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Windows Server 2012 Software RAID-1 of System Volume

Simple question at the first glance. One can think that it can be solved in few hours on Internet. But...
Is it possible that there is no any useful guide out there for such common operation? Obviously it is.
The only guide you can find on the subject relates to Windows Server 2008 R2, and can be found
here. But anyone who ever tried to accomplish mirroring this way knows that it includes hours of copy-paste, boring and error prone work in CL tools
Diskpart and bcdedit. And to make things even worst, there are many reports that such systems actually won't boot anyway if the first drive fails.
Common Microsoft guys! Give us some tool, or at least reliable guide!
I'll send valuable gift to anyone who can help me mirror system volume in Windows Server 2012 :)
Thanks
Aleksandar

Hi,
I think I understood the question. As you said, currently we will have to edit the boot information on the second disk through Bcdedit and we have to do this with command line.
You mentioned "a tool or a clear guide", so I'm trying to find out the confuse part which seems to this:
bcdedit.exe /store t:\boot\BCD /set {identifier1} device ramdisk=[r:]\Recovery\WindowsRE\Winre.wim,{identifier2}, where {identifier1} is the identifier for the Windows Boot Loader entry with the description Windows Recovery Environment and {identifier2}
is the identifier for the Device Options entry.
I think the {identifier1} part may cause confuse. Actually if you run this command:
Bcdedit.exe /store t:boot\BCD /enum all
Note: Here T is a drive letter it assigned to the System Reserve partition. You could try to assign a drive letter T on a server and run the command to see the result.
It will show result like this:
Windows Boot Manager
identifier              {bootmgr}
device                  partition=T:
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {default}
resumeobject            {d2d918d1-8b0d-11de-8b0e-cb2e6be3a937}
displayorder            {default}
                        {ntldr}
toolsdisplayorder       {memdiag}
timeout                 30
Windows Boot Loader
identifier              {d2d918cf-8b0d-11de-8b0e-cb2e6be3a937}
device                  ramdisk=[C:]\Recovery\d2d918cf-8b0d-11de-8b0e-cb2e6be3a9
37\Winre.wim,{d2d918d0-8b0d-11de-8b0e-cb2e6be3a937}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment
inherit                 {bootloadersettings}
osdevice                ramdisk=[C:]\Recovery\d2d918cf-8b0d-11de-8b0e-cb2e6be3a9
37\Winre.wim,{d2d918d0-8b0d-11de-8b0e-cb2e6be3a937}
systemroot              \windows
nx                      OptIn
winpe                   Yes
Device options
identifier              {d2d918d0-8b0d-11de-8b0e-cb2e6be3a937}
description             Ramdisk Options
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\d2d918cf-8b0d-11de-8b0e-cb2e6be3a937\boot.sdi
See the Bold part. This could help us find the identifier these commands needed.
Currently there is no such tool could help us to do these steps automatically. Maybe a script-based program could help a little.
TechNet Subscriber Support in forum |If you have any feedback on our support, please contact [email protected].

Incoming Email on Windows Server 2012

Windows Server 2012:
SMTP and the associated management tools are deprecated. Though the functionality is still available in Windows Server 2012, you should begin using System.Net.Smtp. With this API, you will not be able to insert a message into a file for pickup; instead configure
Web applications to connect on port 25 to another server using SMTP.
Question:
If this is the case, is there a TechNet article that has instructions for installing/using incoming email on a SharePoint 2013 web front end?
What I know:
Why do we install deprecated features http://technet.microsoft.com/en-us/library/cc263260 (Plan incoming email for a SharePoint farm in SharePoint 2013) to make this work?
What to do:
I want to use the basic scenario for incoming email, but with the information above about Windows Server it looks rather like idiotic to follow those directions in the TechNet article.
How to do this:
"... instead configure Web applications to connect on port 25 to another server using SMTP." Huh? Oh stupid me!
Thoughts???
NOTE: We do use Exchange for incoming email.
Chris

You will need to continue to use the IIS6 SMTP Virtual Server for SharePoint incoming email. I'm sure by the time the feature is dropped, the SharePoint group will have an alternate solution.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

[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.

Windows Server 2012 R2 ISO download incorrect in Evaluation center.

I've tried to download the ISO 3 times (the 4th is in progress now)
The first time I tried I got an Akamai error. Then after trying again, the download completed without error.
However the directory didn't contain an ISO it had 7 files:
SC2012_R2_SCOM.EXE
SC2012_R2_SCAC.EXE
SC2012_R2_SCCM_SCEP.EXE
SC2012_R2_SCDPM_EVAL.ZIP
SC2012_R2_SCO.EXE
SC2012_R2_SCSM.EXE
SC2012_R2_SCVMM.EXE
They all appear to be for System Center, not Windows Server 2012 R2.
I was very careful to specify Windows Server 2012 R2, (especially after the 3rd time)
The download bar in the upper left says "Windows Server 2012..." I can't see what's after the ...
Anyone have any idea what's going on?
Thanks,

Hi,
Please follow the steps below to download it.
1. Open
http://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2012-r2
2. Expand Windows Server 2012 R2 and choose ISO/VHD. Then, click Register to continue.
3. Complete the two forms.
4. When you reach the Akamai page, you can choose “download the installer” or “If you cannot complete the installation, Click here”
5. If you choose “Click here”, then you choose “OK” on the next page and get the download link.
Best Regards.
Jeremy Wu
TechNet Community Support

Windows Server 2012 installation won't start

Hi,
I'm trying to install windows server 2012 which i downloaded from my MSDN subscription,
i'm installing it on HP 8100 Convertiable Mini-tower.
Windows loading files and then when the windows icon shows up it just restart the computer, and it enter an endless boot loop.

Hi,
In addition to Tim’s suggestions, we need to ensure that we have updated and digitally signed kernel-mode drivers for Windows Server 2012 for x-64 based operating system.
Installing Windows Server 2012
http://technet.microsoft.com/en-us/library/jj134246.aspx
Best regards,
Frank Shen

Got Display driver via Windows Update for Windows 8.1 and try to use it for Windows Server 2012 R2

Hi Everyone,
the following driver cab is from Windows Update:
https://onedrive.live.com/?cid=5be01620eea95d8c&id=5BE01620EEA95D8C!138&ithint=file,.cab&authkey=!APDi54-R1Ob5IWQ
It includes this display driver:
Intel(R) Q45/Q43 Express Chipset (Microsoft Corporation - WDDM 1.1)
My problem is: I can't install this driver on Windows Server 2012 R2.
I tried the following, nothing worked:
a) pnputil -i -a intel.cab
b) Extract cab, update the device's driver in device manager, select "search for driver software in this location"
c) copy the files in system32/, system32/drivers, syswow64/ from a Windows 8.1 system to a Windows Server 2012 R2 system
Isn't it true that any Windows 8.1 driver should also work for Windows Server 2012 R2 (same os version)?
Thanks for your replies.
PS: I first posted my question here:
http://answers.microsoft.com/en-us/windows/forum/windows8_1-hardware/got-display-driver-via-windows-update-for-windows/31c287c8-ef84-4c81-8530-8c51412376b7

Hi,
Additionally, did you check this article?
http://www.driveridentifier.com/scan/download.php?item_id=90475670&scanid=9B44546E3BB9410D877D9A90D1439AF8&hardware_id=PCI%5CVEN_8086%26DEV_2E12
Regards.
Vivian Wang

On Windows Server 2012 R2 the "Show my desktop background on Start" is grayed out

Hi
As shown below, the new 8.1/2012R2 function "Show my desktop background on Start" is not available on Windows Server 2012 R2.
I have tried multiple solutions:
- Activate OS (In Win 8.1 - the feature is unavailable when Win8.1 is not activated)
- Install Desktop Experience
- Playing with the registry key "Subkey: HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Accent Entry:
MotionAccentId_v1.00
But no luck. Does anyone have a solution.
The reason why I need this is, that I am building a Remote Desktop solution, and here we want to give users the same experience as from their desktops.
Looking forward to some exciting feedback.
Regards,
Mr. Thomas

Hi,
I am trying to involve someone to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Jeremy Wu
TechNet Community Support
Jeremy,
I, too, am facing this issue.
Do we have any update on this?
With regards
With regards

File systems available on Windows Server 2012 R2?

Similar Messages

Maybe you are looking for