Hyper-v Role in Windows Server 2012 foundation and Essentials

Hello,
I have seen that the two low cost version of Windows Server 2012 essential and Foundation) will not support hyper-v. Can you please tell me what it means exactly :
Can you please tell me what is possible :
-The server can not be installed as a hyper-v  guest (probably yes)
-The hyper-v role can not be installed on the server (so I have to rely on vmware)?
- Hyper-v role can be installed but there is no free license included with the server.
Thank you
Marc

I suppose then, you would have to install Windows 8 and Hyper-V as your guest or core.
Then run your Server 2012 Foundation under Win8.  which has 512GB Memory Limit.
It seems asinine that you cannot install this role on Foundation, but seemingly you could work around it with Win8.  (Or Sun Virtual Box (free) (or VmWare(Free).
So load up a dozen Win8Pro virutal sessions on that Win8 VirtualBox with up to 512GB Memory and Create your own Ghetto Remote Desktop Server with Foundation and Windows 8.   ;)
What good is it if your can't run Hyper-V and Remote desktop services?  Those are the two apps small business need most.  But Microsoft strips it out, calls it a DEAL  (Essentials and Foundation) , yet if you want the good stuff, you're gonna
have to buy Server 2012 Standard anyhow, + the CALs.
So you are hooked into this "deal" by Microsoft Special Offer.   Its special alright, because you get to buy it twice.  The stripped down version that come with your server, then the full version when you discover Foundatoin and Essentials gives
you AD, and thats it.  Nothing Else.  No "deal"
Remember:
All you get with Foundation or Essentials is AD and Group Policy.
You cannot load RDP on Foundation or Essentials
You cannot load Exchange on a DC, or Foundation or Essentials
You cannot load Exchange and RDP on the same box.
You cannot have Remote Web Apps if you load RDP on your DC.
You cannot win with Microsoft.  No worthwhile "deal" has ever come out of the city of Redmond.
The internet is a one-way money pipeline to Microsoft.
Its three times the work, three times the cost and requires three servers licenses to do with 2012, what you could do with one 2008R2 license.  
Might as well purchase 2 Server 2013 Standard Editions if you want:
1.) Active Directory
2.) Remote Desktop and Remote Apps
3.) Your own Exchange Server
You are better off installing a NAS if all you need is a file server. 
Why bother with Foundation or Essentials?  Its a "Gimmick-ware"

Similar Messages

  • Windows Server 2012 Standard and Essentials User CAL's

    I've been running Windows Server 2012 Essentials in an organization that until recently stayed within the 25 user 50 network device limit specified by the license. Eventually we've grown beyond that. Since the Server 2012 Essentials machine had a non-transferable
    OEM license I decided not to waste it by doing an in-place migration to Server 2012 Standard, and instead set up a new server with freshly purchased Server 2012 R2 Standard and migrated Active Domain roles to it, leaving the original server as a part of a
    fail-over cluster.
    We purchased 30 User CAL's for the 2012 R2, as required for 25+ staff members.
    Now I am curious. The 2 servers that we have right now (2012 R2 Standard and 2012 Essentials) both maintain the same Active Directory and manage the same pool of users and workstations. Does that mean that the primary server with 30 User CAL's takes dominance
    and sets the limit as to how many people are allowed to access the network. Or does it become a combination of purchased 30 CAL's + 25 Users hard-wired into the 2012 Essential edition?
    Do these servers have to run separate domains with segregated pools of users in order to be license compliant for 30+ users or can they exist within the same same domain preserving individual user limits? What if the 2012 Essentials server maintains
    one office location with fewer than 25 staff and the Standard R2 2012 server runs another office with fewer than 30 staff, while both offices are linked via a VPN for the purpose of sharing 3rd party licenses? Do individual user limits apply, or is it still
    30 users max?
    To sum up the question, I'd like to know whether I'd need to buy more user CAL's when we reach more than 30 staff at 1 or possibly 2 office locations.
    Oh, and the device limit! 2012 R2 Standard under user CAL licensing scheme has no machine limits. Essentials is always capped at 50. When running one active directory, what's the legally allowed number of devices on the network? I assume it's unlimited.
    Thanks.

    Thank you for the reply.
    My question then is how to transition while preferably keeping both physical servers.
    Should a 2012 Standard key be purchased additionally for an in-place transition of 2012 Essentials machine to 2012 Standard (which at this point is as good as a fresh install)? Until then, should the Essentials 2012 server be taken offline entirely?
    What about the situation where I described both servers running segregated networks with their own pools of users, only connected via a VPN for 3rd party license sharing? Is that configuration supported?
    Also, if the configurations is unsupported, why are the servers able to share roles in first place? Why isn't there a software mechanism preventing interaction? What configuration do the servers themselves assume is in place?
    Thanks again.

  • Windows Server 2012 Foundation, in a Workgroup - "The server did not finish checking the license compliance. If the server is joined to a domain, make sure that the server can connect to a domain controller"...

    Every few days we see two dialogs with the following messages:
    Dialog 1, title: Check for Licensing Compliance is Incomplete
    The server did not finish checking the license compliance. If the server is joined to a domain, make sure that the server can connect to a domain controller.
    Dialog 2, title: Check for Licensing Compliance is Incomplete
    The server did not finish checking the license compliance. If the server is joined to a domain, make sure that the server can connect to a domain controller. If the license compliance check cannot be completed, the server will automatically shut
    down in 8 day(s) 23 hour(s) 0 minute(s).
    The server is not (and never has been) joined to a domain or had any DC roles installed. In fact its still connected to the default Workgroup.
    The server was configured in our office and never showed this message until it was installed on site. The main difference from what I can see is that when installed on site it was given a static IP address and does not have any DNS settings in the network
    adapter properties. 
    I have scoured a number of forums on this error but in almost every other instance of this error message the servers are connected to a Domain Controller and the solutions generally are linked to dis-joining and rejoining the domain. Unfortunately this is
    not an option for this scenario.
    I initially thought that adding some relevant DNS server IP address may resolve the issue, however, we have the exact same model server configured exactly the same running at a different site that does not experience this problem. This server also has no
    DNS server configured.
    I have seen a post that suggests turning off the servers "Foundation Checking", but I'm unsure how to do this.

    Thanks for your response Vivian.
    I can confirm that this server is not (and never has been) a member of any active directory, it is configured as a Workgroup server. It was initially configured on a network that does have an active directory, but was never joined to it. During that time it
    never displayed these messages.
    The server was moved into production on a different site and network and setup with a static IP address.The site network does have its own active directory but the server was not joined to it. It is whilst on this new network that these messages began.
    Since my original post DNS servers have been added and the Microsoft activation has been verified, however, the messages are still appearing.
    There are only 2 user accounts configured on this server. The local admin account and another local admin user.
    The remote desktop services roles have been installed but not yet configured. I don't think that has any bearing on this scenario though.
    The description of this error in the above "Introduction to Windows Server 2012 Foundation" link states:
    This error occurs when the server cannot finish checking the requirements for the root domain, forest trust configuration, or both. It usually happens when the server cannot connect to a domain controller. If the situation persists, the server will
    shut down 10 days after the first time the compliance check failed. Each time this error message occurs, it will state the actual time remaining before the server will shut down. If you restart the server after it has shut down because of non-compliance, the
    server will shut itself down again in 3 days.
    The above description leads me to the following question - In a Workgroup environment, does the server still try to contact a domain controller to establish a level of trust? If this is the case could it be that the server can no longer see the initial DC
    on its new network and this is what is triggering the messages?
    Am I clutching at straws here?

  • How to allow more than two users on remote desktop on windows server 2012 foundation?

    i have a dell server power edge T300 with windows server 2012 foundation. I am unable to connect more than two remote desktop at once.

    Hi,
    Add to Brain, you cannot have more than 15 user accounts in Windows Server 2012 Foundation.
    In order to access a hosted application, such as Microsoft® Office, a license for Windows Server 2012 Remote Desktop Services is required for each user account (not to exceed 15 user
    accounts) that directly or indirectly uses RD Gateway to host a graphical user interface, including using Remote Desktop Connection (RDC) client. When using Remote Desktop Services, you may not install or use Remote Desktop Connection Broker or Remote
    Desktop Virtualization Host role services. For more information about Remote Desktop CALs , see http://go.microsoft.com/fwlink/?LinkId=140238.
    http://technet.microsoft.com/en-us/library/jj679892.aspx
    Hope this helps.
    Jeremy Wu
    TechNet Community Support

  • Trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.

    I am trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.
    It verifies the connection and then throws the error:
    The request to add or remove features on the specified server failed. The operation cannot be completed, because the server you specified requires a restart.
    WSUS Server : Windows Server 2012 R2
    Remote SQL Server: 2012 SP1 CU7 hosted on Windows Server 2012 R2
    Please let me know if anyone has experienced this issue.

    We were trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.
    It verifies the connection and then throws the error:
    The request to add or remove features on the specified server failed. The operation cannot be completed, because the server you specified requires a restart.
    Same error even after rebooting the server multiple times.
    WSUS Server : Windows Server Standard2012 R2
    Remote SQL Server: Windows Server 2012 SP1 CU7 hosted on Windows Server 2012 R2
    Event ID 7000:
    The Windows Internal Database service failed to start due to the following error:
    The service did not start due to a logon failure.
    Event ID 7041
    The MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID with the currently configured password due to the following error:
    Logon failure: the user has not been granted the requested logon type at this computer.
    Service: MSSQL$MICROSOFT##WID
    Domain and account: NT SERVICE\MSSQL$MICROSOFT##WID
    This service account does not have the required user right "Log on as a service."
    User Action
    Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user
    right is assigned to the Cluster service account on all nodes in the cluster.
    If you have already assigned this user right to the service account, and the user right appears to be removed, check with your domain administrator to find out if a Group Policy object associated
    with this node might be removing the right.
    I found following article:
    "MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID" error when you install WID in Windows Server 2012
    http://support.microsoft.com/kb/2832204/en-us
    To work around the issue, use one of the following methods:
    Assign the Log on as a service user right to NT SERVICE\ALL SERVICES in the GPO that defines the user right.
    Exclude the computer from the GPO that defines the user right.
    We moved the SCCM server to OU where no policies were getting applied and then applied the new GPO to that OU. Restarted the server and we were able to install WSUS role.
    Regards
    PR

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

  • WSUS server role on Windows Server 2012 R2 - Supported SQL Configurations

    According to
    this page the supported SQL configurations for WSUS on Windows Server 2012/2012 R2 stop at SQL Server 2012 SP1, but there is no mention of SQL Server 2012 SP2 being supported.
    However, both the SCCM 2012 R2
    supported configuration page and this announcement state that SQL Server 2012 SP2 is fully supported on SCCM 2012 R2 with no
    known limitations. Bearing in mind a big part of SCCM is to perform software updates which in turn requires WSUS to be installed...
    ... Is SQL Server 2012 SP2 supported on WSUS 4.0 (aka WSUS server role on Windows Server 2012 R2)?

    The only thing that mattered for the versions mentioned on TechNet probably is the date the articles are published. I'm no Microsoft employee so I cannot guarantee you support even if I trace back some Microsoft article that explains the lifecycle of MS
    products and support.
    Fact is that MDT uses a database, SQL is a database server. SQL server has all kinds of compatibility modes to support databases dating multiple versions back.
    Another fact is that a Service pack is an
    update to the software (be it a large one) Microsoft will not break compatibility with their own products (and may others that relay on SQL server) by an update.
    And a last fact is that in general, updates are required when you need support. After all, updates fix issues, and engineers generally don't like ghosthunting a bug that has already been patched.
    MCP/MCSA/MCTS/MCITP

  • Does windows server 2012 foundation ed. support sharepoint?

    does windows server 2012 foundation ed. support sharepoint?

    Based on the feature set, yeah it would support SharePoint 2010, but I wouldn't recommend it. Server 2012 Foundation must be a Domain Controller or in a Workgroup, neither of which are good scenarios for a SharePoint installation.
    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.

  • REMOTE DESKTOP SERVICES CLIENT ACCESS LICENSES FOR MICROSOFT WINDOWS SERVER 2012 STANDARD AND DATACENTER

    I am using a window 7 professional  service pack 1 and I purchase REMOTE DESKTOP SERVICES CLIENT ACCESS LICENSES FOR MICROSOFT WINDOWS SERVER 2012 STANDARD AND DATACENTER. but  the seller did not send me any installation CD or instruction
    on how to use it.
     Please how can I use it on my window 7 professional  service pack 1.
    Thank you.

    Though Bill is absolutely correct for most CALs, Remote Desktop Services does have its own special licensing server.  I haven't installed one on 2012, yet, but here is a step-by-step guide for 2008. 
    http://technet.microsoft.com/en-us/library/dd983943(v=ws.10).aspx
    Here is a lab guide for 2012 -
    http://technet.microsoft.com/en-us/library/jj134160.aspx
    But, the explanation of your environment begs the question - what are you trying to do?  You say you have a desktop OS and you are talking about Windows Server products.  In that light, your question does not make a lot of sense.
    . : | : . : | : . tim

  • I have windows server 2012 R2 and install active directory

    My question is I install active directory in windows server 2012 R2 and create Group Policy. ( These set-up is only for test)
    Have not registered domain only install active directory to test. 
    So the problem is when I created Group policy for my user and put software restriction policy but its affected to my administrator accounts too, No when I open VMware (install Virtual Machine windows XP) and start os then its shows you can not user this
    software as you restricted from installing software (Something like that don't know exact Error). I could not start installed Virtual Machine. 
    Please give me a solution for this.
    This is the setup for a test use only so their not big environment connect with my pc.
    Thanks in advance.
    Regards,
    Krunal

    Hi,
    The following article is talking about creating and managing Group Policy on a Windows Server 2012:
    http://www.thomas-krenn.com/en/wiki/Creating_and_managing_a_Group_Policy_on_a_Windows_2012_Server
    As Darren Blanchard mentioned, if you want to apply the GPO, you could link it to an OU that contain the computer or user.
    Group Policy Overview
    http://technet.microsoft.com/en-us/library/hh831791.aspx
    Please feel free to let us know if you need further assistance.
    Regards.
    Vivian Wang

  • Is it possible to uninstall IE 11 from Windows Server 2012 R2 and replace it with the latest version of IE 10?

    Is it possible to uninstall IE 11 from Windows Server 2012 R2 and replace it with the latest version of IE 10? We have a remote desktop farm setup with 2012 R2 servers and we are publishing some web links that only work with IE10. As a result, we need to
    downgrade the remote desktop servers to IE10. I have a feeling that this isn't possible, but if I could get a definitive answer, I would greatly appreciate it, thank you!

    Hi,
    Agreed with DonPick.
    Internet Explorer 11 is preinstalled with Windows 8.1 and Windows Server 2012 R2.
    More information regarding Internet Explorer 11, please check:
    Internet Explorer 11 - FAQ for IT Pros
    http://msdn.microsoft.com/en-us/library/dn268945.aspx
    Best regards
    Michael Shao
    TechNet Community Support

  • Just FYI, Windows Server 2012 R2 and Windows Server 2012 BranchCache Deployment Guide in Word format in the TechNet Gallery

    The Windows Server 2012 R2 and Windows Server 2012 BranchCache Deployment Guide is now available for download in Word format in the TechNet Gallery at
    http://bit.ly/1pYZT3F
    Thanks -
    James McIllece

    hello again,
    meanwhile I was lucky to find this article about Idenity Mapping in TechNet in the Storage Team Blog:
    http://blogs.technet.com/b/filecab/archive/2012/10/09/nfs-identity-mapping-in-windows-server-2012.aspx
    Likely to be overseen at the end of one paragraph it says:
    "Client for NFS does not support NFS V4.1 in Windows 8 or Windows Server 2012"
    Question : Is this an official statement and is it still valid with most recent
    Windows Server 2012 R2 that NFS client does NOT support NFSv4.x  ??
    thanks - Rainer

  • Hyper-V Gen 2 Windows Server 2012 R2 VM cannot define static IP address

    Hi,
    I have setup a physical server with Windows Server 2012 R2. It has only the Hyper-V role installed. The physical server has two NICs that I have teamed with Hyper-V port as the load balancer. I have created 1 VM on this Hyper-V server that is a
    Generation 2 VM running Windows Server 2012 R2. It has one NIC in the guest OS that is connected to the Hyper-V switch.
    Now the Guest OS works fine and network connectivity is great when using DHCP but when I configure a static IP address in the Guest OS all network connectivity is lost even with correct IP configuration. Is this something to do with a Gen 2 VM?
    A little more background - We have another Hyper-V server running Windows Server 2012 R2 with the same NIC teaming in the Host OS, on this Hyper-V there is a GEN 1 Windows Server 2012 R2 that has a static IP configured which is working normally.
    Any help is appreciated.

    I have resolved the issue. It appeared the hard IP phones were using the same IP range that I was attempting to use so of course the VM could not use the IP Address. Silly mistake.
    Elliot, I suggest you mark as Helpful and Answer any responses above that were helpful to you in getting this issue resolved. This is how the forums work.
    For example, if a response mentioned "VM generation has no effect on the vNIC." and that pointed you in the direction of troubleshooting networking instead of wasting your time looking into VM generations, that may be considered "Helpful"
    If a response mentioned "Make sure you're using valid IPv4 settings" and indeed you ended up having invalid IP settings such as a duplicate IP, this may be considered "Answer"
    Sam Boutros, Senior Consultant, Software Logic, KOP, PA http://superwidgets.wordpress.com (Please take a moment to Vote as Helpful and/or Mark as Answer, where applicable) _________________________________________________________________________________
    Powershell: Learn it before it's an emergency http://technet.microsoft.com/en-us/scriptcenter/powershell.aspx http://technet.microsoft.com/en-us/scriptcenter/dd793612.aspx

  • Error in Installing Exchange Server 2013 (w SP1) Mailbox Role on Windows Server 2012 R2

    Hi Team,
    Need urgent help in resolution of following error:
    Environment Details: VMware ESXi 5.5 (vMotion)
    Migration from Exchange Server 2007 (SP3 + RU13) to Exchange Server 2013
    Exchange Server: Exchange Server 2013 with SP1 (Latest Installation Media)
    OS: Windows Server 2012 R2 - Standard (Latest Installation Media)
    Exchange 2013 Roles: Seprated (Mailbox and CAS on Different VMs)
    Prerequisites: Installed
    Error: Installation gives Error at Step 10 during installation of Mailbox Service
    Error Details Below:
    Error:
    The following error was generated when "$error.Clear();
    if ([Environment]::OSVersion.Version.Major -ge 6)
    $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe";
    $reg= join-path (join-path $env:SystemRoot system32) reg.exe;
    $servicecmd = join-path (join-path $env:SystemRoot system32) sc.exe;
    if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"}))
    if ((get-service wsbexchange).Status -eq "Running")
    Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
    Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
    /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d
    Exchange /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
    /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery /t REG_DWORD /d 1 /f";
    Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for Windows Server Backup`"";
    Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`"";
    " was run: "Process execution failed with exit code 1.".

    Resolved ! :)
    Root Cause: The user account I was using had all the required privileges for Exchange Installation but was not having access to edit the registry of the server. Enable access to registry edit tools and you are good to go.
    As an alternate you can also try installing using Domain Administrator account if in case there is an IT Policy constraint in the former method.
    Thanks to all.

  • Installing terminal server role on windows server 2012 to use for Windows server 2008 R2 machines.

    Dear
    Our current setup is as follows :-
    Active Driectory is in Windows Server 2003.
    Citrix Xenapp version 5.6 with all Xenapp servers in Windows Server 2003
    Now we are upgrading our Citrix farm to 6.5 and all Xen app servers into Windows Server 2008R2.
    We did the configuration and testing; everything works fine except the terminal server is not configured which gives the pop always for the expiry date.
    We do have license for 2012 terminal server which is not possible to downgrade for some reason and managent need to install new Windows Server 2012 for terminal server and activte the licenses.
    My question is :-
    1 Whether Windows Server 2008 R2 will get RDS cal license from Windows Server 2012 terminal server (RDS CAL license is of windows server 2012).
    2. What is the role and features I need to activate in Server 2012 in order to use for Citrix 6.5 (only applicable fetaure for getting the RDS cal license.) 
    3. Whether I can add this 2012 server into domain. Is it possible to add 2012 server into Windows Server 2003 AD. 
    Your early reply is highly appreciated.

    Thanks Jeremy..
    I got exactly the right answers I am lookoing for ..
    I successfully activated the terminal service on the newly created Windows 2012 Server and installed the retail license pack we had of 50+50+25 keys . It later shows the 125 keys successfully applied.
    when I tried to link the Xenapp (Windows Server2008R2) to the license server, it first gives me error that session host service role is not installed on the ternial server. So I installed that role also in the terminal server.
    But now its anothee error as below.
    RDS Cals are not available for this Remote Desktop Session host server, and licensing Diagnostic has identified licensing problems for the RD session host server.
    1. Is it wrong I did by installing session host server role into the terminal server (but really it gave me error like 'session host server role is not running on the license server' when I tried to link the license server).
    2. Is it the problem that Windows Server 2008 R2 will not get license from 2012 RDS CAL license.
    3. whether Clearing house will take time to update the license.
    Your reply is highly appreciated. I need to know whether any other way I can link the Windows Server  2008 R2 Servers (Xenapp) to the license server.

Maybe you are looking for