Server 2003 SBS (with Exchange 2003) migrate to new machine Server 2012 Standard (with Exchange 2013)

This is what I have:
A very outdated machine running a small domain, SBS 2003 and Exchange - this is the ONLY server currently.
This is what my boss ordered:
A Dell R210 II machine with Server 2012 Standard (and I downloaded the trial for Exchange 2013).
He wants the old server completely replaced and gone - with everything moved over (including Exchange) to the new machine. The main reason for the upgrade is that not all users can access email on their machines (Macs, new versions of Outlook, etc.)
I have set up a new standalone server before but never migrated one - and I've found that going from SBS2003/Exchange2003 to Server2012/Exchange2013 is not simple in the least.
I thought I could just set up the new server as a DC on the domain and have everything replicated to it from the source server. Then I could decommission the old server. I have been told that 1) I can't upgrade Exchange 2003 to 2013 and 2) that I shouldn't
put Exchange on a DC. What do you do if you only have the one server?

Hi,
Just additional. Please also refer to following threads and article, then check if can help you.
Migrate
SBS 2003 to Windows Server 2012 Standard
Migration
SBS 2003 to Windows Server 2012 Standard
Transition
from Small Business Server to Standard Windows Server
Hope this helps.
Best regards,
Justin Gu

Similar Messages

Migrate SBS 2003 with AD and Exchange to Windows Server 2012 Standard

We are using SBS 2003 and we have configured Exchange server and AD with DNS and DHCP. Now we are planning to move SBS 2003 to Separate servers like windows server 2012 standard AD with DNS and DHCP and Windows server 2012 Standard with Exchange
2010.
Is it Possible?? we need step by step guide.
Thanks in advance.

Hi,
You probably would not find any step by step guide for this kind of migrations. If you are not comfortable with doing such migrations I would recommend to if you need to do it your self do some test migrations. Or otherwise get help by a local IT company
that is familiar with migrations.
But to give you some information, first thing before starting a migration is check the health of your SBS 2003 server / domain. Use tools like dcdiag, netdiag and best practice analyzer. I wrote a blog post about steps to think about before you start this
might help: http://blog.ronnypot.nl/?p=914
When every thing is clean you can start adding the new windows server 2012 machines as member servers to your domain.
Next you can promote one of the servers to additional domain controller on your domain (Keep in mind SBS needs to hold all FSMO roles so moving these is the last step your should do.) Also promoting a windows server 2012 to domain controller has slightly
changed, you need to install the ADDS role and follow the wizard to promote the server to a DC.
With installation of the new DC install DNS allongsite it will automatic replicate settings during confiugration.
DHCP must be installed manual, depending on your scope and settings it might be as easy to create a new scope and disable the old dhcp server.
On the server Exchange needs to be installed, make sure you install and do all pre-requirements. Than install Exchange it will automaticly detect you already have an Exchange organization and is installed as additional server. You can configure all settings
and when everything is configured right you start moving mailboxes.
When everything is moved away from the SBS 2003 server, uninstall exchange, move the FSMO roles to the new DC and after that demote the sbs 2003 server so it is not listed anymore as an additional DC in the domain. Last would be shutdown the server and remove
all records left in AD and DNS.
There is this guide for migrating SBS 2003 to windows server 2008 R2 and Exchange 2010, this might give you some usefull information, not everything will be the same but it is a good start:
http://demazter.wordpress.com/2010/04/29/migrate-small-business-server-2003-to-exchange-2010-and-windows-2008-r2/
Regards Ronny
Visit my Blog or follow me on
Twitter

Migrate SBS 2003 to Windows Server 2012 Standard

We currently have two servers (SBS 2003 Standard utilizing Exchange 2003; Windows Server 2003 R2 Standard with SQL 2005).
We want to retire the SBS or maybe both.
We have purchased a new server (Windows Server 2012 Standard with licenses for Exchange 2013 and SQL 2012).
Is there a whitepaper that describes how to migrate SBS 2003 to Windows Server 2012 Standard?
Is it possible to run Exchange 2013 on the Windows Server 2012 box? In Hyper-V? If Exchange can run in a virtualized instance, do we need additional licensing to run another instance of Windows Server 2012 Standard?
Can we run SQL 2012 on the same Windows Server 2012 box?
We have about 35 users.

Sal,
Migration went fine. Steps i took:
Join 2012 Standard server as member.
Migrated roles.
I ended up manually creating new shares. The old environment was a mess.
Robocopy data/verified.
Seize FSMO roles
http://support.microsoft.com/kb/255504
Metadata cleanup
http://support.microsoft.com/kb/216498
Good luck

Is it ok to install Exchange 2013 on Windows Server 2012 Standard?

Hello everyone,
I'd like to know if it is ok/safe to install Exchange Server 2013 on Windows Server 2012 Standard?
As I started doing some research and noticed a page where Microsoft states they don't recommend running Exchange on Server 2012 Standard, and recommend making 2 different servers one for Active Directory and another for Exchange.
On that page they also listed some features that wouldn't work in case of Exchange is running on Server 2012. And that it may put a larger data load if setup this way.
I am hoping someone knowledgeable can explain and tell me if it is safe to use such setup or if it is better to use something like SBS 2011 Standard instead, which has Exchange included?
Has anyone installed Exchange 2013 on Server 2012 Standard successfully and used it for more then several months without problems?
Also just to give an idea on my background, I've been in IT field fairly long but haven't really updated to newer versions much and mainly used SBS 2003 and 2008 only with a few clients so haven't used 2008 too much.
Thanks in advance.

Few things to note.
There is
NO SBS in 2012
All you need is a Std edition of Windows for Exchange 2013, as there is no difference in features between Std and Datacenter as far as Exchange is concerned.
For 10 users, you can have one box with both AD and Exchange. It is not MS recommeded, but it IS supported.
Rajith Enchiparambil |
http://www.howexchangeworks.com |

SQL Server 2012 Standard compatibility with Windows Server 2012 R2 Standard

Hi,
Is SQL Server 2012 Standard compatibility with Windows Server 2012 R2 Standard.
In volume licensing portal Windows Server 2012 R2 Standard is not provided in the list of OS supported for SQL server 2012.

Hi Ajit,
Besides other post, please also note that
Service Pack 1 or
a later update is needed for the support of SQL 2012 on Windows Server 2012 R2.
For more details about how to use SQL Server in Windows Server 2012 R2, please review the following KB article.
http://support.microsoft.com/en-us/kb/2681562
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

WSUS on Server 2012 Standard R2 with SCCM 2012 Standard R2 Proper Setup

What is the proper setup (best practice) on setting up WSUS using Server 2012 Standard R2 to work properly with SCCM 2012 R2 Standard using Server 2012 Standard R2 on separate box?
1. Is it using WID or database during the setup of WSUS using Server 2012 Standard R2?
2. Once it setup properly on WSUS using Server 2012 Standard R2 either WID or database (using SQL 2012 Standard SP1), how do I connect with SCCM 2012 R2 Standard using Server 2012 Standard R2 on separate box?
3. On SCCM 2012 R2 Standard using Server 2012 Standard R2 just need to add WSUS Role, right? Is it using WID or database?
Thanks,
Reza

1. Generally, using the SQL instance you use for ConfigMgr is preferred.
2. The Software Update Point connects ConfigMgr to a WSUS instance.
3. See 2.
Jason | http://blog.configmgrftw.com
It's just as Jason said. The SUP role in SCCM basically "sits on top" of the WSUS role, whether it is local or remote is up to you. You basically install WSUS on a server like you normally would WITHOUT configuring it. I have used both WID and SQL. It's
always nicer to put it on your SQL server since that is (should be) backed up regularly and maintained.
Once you have WSUS installed you just point SCCMs SUP role at the installation and it takes over the rest.
Dustin Estes - MCP | www.dustinestes.com

Restore backups from Server 2012 Standard to 2012 Essentials or Foundations

The owner of our small office (about 25 employees) wants to have an off-site "emergency server" to be used if the primary office becomes completely unavailable due to fire or other emergency. In the past we did this with a 2003 Small Business server
in the office and a basic PC stored off site both running Veritas Backup Exec 10 and backing up files to a removable hard drive that could be restored to the spare 'server'.
Now that we are upgrading the main office server to Server 2012 Standard, the Backup Exec 10 will no longer work and I'm not interested in paying several thousand dollars for licenses for the newest version of Backup Exec for the new server and the 'spare'
machine.
So my question is, if I use the built in backup system in the 2012 Standard server, would a spare machine running 2012 Essentials or 2012 Foundations be able to access those backups? Getting the basic OS on the spare server instead of the full 2012 Standard
would lower the cost significantly and make it easier to fit into the available budget. When used in an emergency, there would probably be at most 5 people accessing the spare server so user licenses won't be an issue, I just need to make sure the backup idea
is feasible.

Hi Michael,
à
if I use the built in backup system in the 2012 Standard server, would a spare machine running 2012 Essentials or 2012 Foundations be able to access those backups?
Based on your description, I test something in my Lab environment. I create a shared folder, then backup (not Full server backup)
to the shared folder via Windows Server Backup on the Windows Server 2012 Essentials. Then logon a Windows Server 2012 Standard and access the shared folder. Then navigate to the backup file (.vhdx file), right click it and select
Mount. Please assign a drive letter to it in Disk Management. Then you will be able to see all files and folders which were backed up in this backup file (VHDX file).
In addition, when run Recovery Wizard via Windows Server Backup, you also can use an option ‘A backup stored on another location’
to select the backup file which was stored in the shared folder for the recovery.
If anything I misunderstand or any update, please don’t hesitate to let me know.
Hope this helps.
Best regards,
Justin Gu

Possible to downgrade Server 2012 Standard R2 to R1?

Thanks in advance for any advice. Hopefully, I'm posting on the correct forum.
A client of mine recently purchased a Dell PowerEdge server that came with Windows Server 2012 Standard R2 pre-installed. While I was getting the server installed on site for the client, we discovered that the main software they intend to run on
this server has some sort of compatibility issue with R2 (I checked with support before purchasing and was told R2 would be fine, but they told me otherwise after we started having issues during the installation). So again, Server 2012 Standard is perfectly
fine....just not R2. Do I have any options here, or do I simply have to purchase a separate license?
I have the media to install Server 2012 Standard and gave that a shot, but it didn't like the R2 license key that's on the server's CoA sticker when I attempted to activate it.
Far as I know, R2 is not something I can just uninstall like an update, and I'm going to have to nuke it and fresh install Server 2012 Standard without R2 to do this.
I have tried contacting Dell and was told that purchasing a separate license would be my only option, as Server 2012 Standard vs Server 2012 Standard R2 are considered two separate products with no way to "convert" or "downgrade"
from R2. I'm willing to go that route of purchasing the different license if I have to (this server is otherwise an expensive paperweight/boat anchor until I get the proper OS on it), but I thought I'd try checking here first to see
if anyone knew of other options I might have.

Hi, please check that;
Rights to server software are granted in the OEM License Terms. The OEM License Terms for most OEM versions released with or after the Windows Server 2003 R2 operating system allow for the user to downgrade to an earlier version. New products that do
not have earlier versions do not allow a user to downgrade. See the full text of the applicable OEM License Terms for the specific downgrade rights. (http://download.microsoft.com/download/6/8/9/68964284-864d-4a6d-aed9-f2c1f8f23e14/Downgrade_Rights.pdf)
At this point, I think your best bet is to ask your revender a recovery media kit for 2012, or you can use a retail media kit, if I read that correctly;
From there;http://www.microsoft.com/OEM/fr-ca/licensing/sblicensing/Pages/what_to_do_downgrade_rights.aspx#fbid=4ej9DrEQ_R6
End users can use the following media for their downgrades:
retail (full
packaged product), or system builder edge-to-edge media (DVD), provided the
software is acquired in accordance with the Microsoft OEM System Builder
License. End users can use one legal version of the downgrade media for multiple
installations. They don't need to have one set of media for each PC they are
downgrading, because they have acquired legitimate full operating system
licenses for the most recent version, which gave them the right to downgrade.
In doubth, call the VLSC's center.
Regards, Philippe
Don't forget to mark as answer or vote as helpful to help identify good information. ( linkedin endorsement never hurt too :o) )
Answer an interesting question ? Create a
wiki article about it!

Windows Server 2012 Standard - HP OfficeJet Pro 8600 Plus printer not working after promoting to Domain Controller / AD Services

An associate and myself installed the built-in drivers for the HP OfficeJet Pro 8600 Plus multi-function (network) printer on a Windows Server 2012 Standard server installation and everything worked fine whenever I want to print anything directly from the
Windows Server machine (there's a reason for this, so please understand that ;) ).
We were able to print without any problems from the Windows Server 2012 machine, using the drivers from Microsoft. Mainly, because HP has not listed any specific support for Windows Server 2012, only Windows Server 2008 R2, however, the drivers that
came with Windows 2012 seem to work very well.
PROBLEM: I later had to promote the Windows Server 2012 to a Domain Controller, and created the Active Directory configurations, even enabled the Print Services. After doing all of that, the HP printer will not print anything. It's like all print
requests directly from the Windows Server go to Nil.
Has anyone encountered a problem like this before? The only thing I can think of is that after perhaps something affected printing directly once we promoted the server to being a DC, and added other features / roles. I even tried installing the
HP drivers for Windows Server 2008 R2, and the results are still the same...nothing prints. Trust me, the printer is set as the Default Printer and even when choosing to print, we make sure the HP OfficeJet Pro is selected, and is on, as other Windows
Client PC's can print to it directly.
Does anyone have any suggestions we could try? Thanks in advance.

While it is quite a while since this was posted - I can concur a similar issue exists.
We have spent the better part of a day trying to work out why other HP printers work fine but our 8620 prints are not printing and going to Nil. The print server is hosted on a shared DC. Comparing to the initial posters details, for some reason
it seems to be most commonly related to the OfficeJet Pro 8600/8610/8620/8630 series printers.
I ended up doing a print server migration from the domain controller to stand alone host and all printers now work from a single server rather than a mix. Domain controller OSes varied from 2008, 2012, 2012 R2 (tested with multiple) and only after
all of those failed then tried a stand alone server os machine as a last resort which worked fine. Printing directly from Win 7 / 8 /8.1 clients to the IP always worked.

SQL Server 2012 Standard Support for Lync 2013

Hi,
Does SQL 2012 Standard version support Lycn 2013 , I am planning to have following features.
1- SQL 2012 Mirroring
2- Monitoring Role on FE Servers
Regards
Usman Ghani
Usman Ghani - MCITP Exchange 2010

Agree with Anthony, SQL 2012 Standard support Lync 2013.
For Standard or Edition Edition of SQL that according to High availability node of Database that you want.
Two-node failover clustering for the following:
Microsoft SQL Server 2012 Standard (64-bit edition). Additionally running the latest service pack is recommended.
Microsoft SQL Server 2008 R2 Standard (64-bit edition). Additionally running the latest service pack is recommended.
Up to sixteen-node failover clustering for the following:
Microsoft SQL Server 2012 Enterprise (64-bit edition). Additionally running the latest service pack is recommended.
Microsoft SQL Server 2008 R2 Enterprise database software (64-bit edition). Additionally running the latest service pack is recommended.
Also for more detail details, you can refer below link
http://technet.microsoft.com/en-us/library/gg412952.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

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.

Unable to install SQL Server 2012 Standard: Error code 0x851A0019

Hi All,
I am trying to install sql server 2012 standard edition on windows server 2008R2 but at the end of the installation it is giving me the following error message:
"The following error has occurred:
Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes."
And in the log file I got the following error message:
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A0019
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
(I have posted part of the log file)
Need your help to resolve this issue.
Thanks,
MKNayeem

Hi,
Thanks for your reply.
I have already followed that article. I have changed the user to local account user, but it did not work.
Like you said the sql server is installed, but it is not starting the services. Following is the error log file message:
2015-03-16 10:12:15.27 Server Microsoft SQL Server 2012 - 11.0.2100.60 (X64)
Feb 10 2012 19:39:15
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
2015-03-16 10:12:15.27 Server (c) Microsoft Corporation.
2015-03-16 10:12:15.27 Server All rights reserved.
2015-03-16 10:12:15.29 Server Server process ID is 5724.
2015-03-16 10:12:15.29 Server System Manufacturer: 'VMware, Inc.', System Model: 'VMware Virtual Platform'.
2015-03-16 10:12:15.29 Server Authentication mode is MIXED.
2015-03-16 10:12:15.29 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL11.BNG1SECISO\MSSQL\Log\ERRORLOG'.
2015-03-16 10:12:15.29 Server The service account is 'NT Service\MSSQL$BNG1SECISO'. This is an informational message; no user action is required.
2015-03-16 10:12:15.29 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL11.BNG1SECISO\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL11.BNG1SECISO\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL11.BNG1SECISO\MSSQL\DATA\mastlog.ldf
2015-03-16 10:12:15.29 Server Command Line Startup Parameters:
-s "BNG1SECISO"
2015-03-16 10:12:15.57 Server SQL Server detected 2 sockets with 1 cores per socket and 1 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message;
no user action is required.
2015-03-16 10:12:15.57 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-03-16 10:12:15.57 Server Detected 16383 MB of RAM. This is an informational message; no user action is required.
2015-03-16 10:12:15.57 Server Using conventional memory in the memory manager.
2015-03-16 10:12:15.67 Server This instance of SQL Server last reported using a process ID of 2452 at 16-03-2015 07:03:13 (local) 16-03-2015 01:33:13 (UTC). This is an informational message only; no user action is required.
2015-03-16 10:12:15.67 Server Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational
message only. No user action is required.
2015-03-16 10:12:15.69 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2015-03-16 10:12:15.69 Server Software Usage Metrics is disabled.
2015-03-16 10:12:15.70 spid6s Starting up database 'master'.
2015-03-16 10:12:15.78 Server CLR version v4.0.30319 loaded.
2015-03-16 10:12:15.82 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2015-03-16 10:12:17.36 spid6s Error: 824, Severity: 24, State: 2.
2015-03-16 10:12:17.36 spid6s SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:377; actual 261:2228225). It occurred during a read of page (1:377) in database ID 1 at offset 0x000000002f2000 in
file 'C:\Program Files\Microsoft SQL Server\MSSQL11.BNG1SECISO\MSSQL\DATA\master.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and
must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Thanks
MKNayeem

SharePoint 2013 OS: Windows Server 2008 R2 vs Windows Server 2012 Standard

Hi Team,
We are thinking on upgrading from SharePoint 2010 to SP 2013 soon. I have been researching about the server OS I should install as host, and it seems that SharePoint 2013 is fully compatible by now with both Windows Server 2008 R2 Standard + SP1 and
Windows Server 2012 Standard. In my opinion we should go with server 2012, but Windows server 2008 is the norm here at our organization and our Infrastructure team seems reluctant to upgrade servers to 2012 yet.
My question is, what SharePoint or Windows 2012 features will we miss if we decide to stay on Windows 2008? What are the perks (selling points) of going with 2012 over 2008? (besides the obvious Microsoft support range extension).
Thanks!
-Rob.

If you stay on Windows Server 2008 R2 you will enter the extended/out of support phase sooner, of course. You will miss out on IIS improvements, although in practical terms it may not mean much.
There are extra patches required for a 2008 R2 deployment that are not needed on 2012 for SharePoint 2013. But other than that, I think the other big issue is that mostly in the community, you'll find people running Server 2012 which means issues are better
'known' by the community, versus 2008 R2 in combination with SharePoint 2013.
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.

How to install device cals on Windows Server 2012 standard edition

Hello i have a windows server 2012 standard edition licence that i have taken on rent from an ISP.
i have created a domain controller on that.
By default only two users can use remote desktop to the server simultaneously.
My Requirement is 20 users can use remote desktop to the server at the same time.For that i have purchased 20 Delive CALs licences like volume licencing.
i have the licence number noted on the paper.
do i need to install remote desktop services first etc ?
Could anyone guide me step by step how can i install or configure so that 20 users can use remote desktop on the same time.

Hi,
Any update about the issue?
I would agree with others, you need to install Remote Desktop Services Client Access Licenses.
There are three methods by which you can install Remote Desktop Services client access licenses (RDS CALs) onto your license server:
• Install Remote Desktop Services Client Access Licenses Automatically
• Install Remote Desktop Services Client Access Licenses by Using a Web Browser
• Install Remote Desktop Services Client Access Licenses by Using the Telephone
https://technet.microsoft.com/en-us/library/cc725890.aspx?f=255&MSPPError=-2147217396
Then you can install both Per User and Per Device CALs onto the same license server.
Regards.
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]

SharePoint 2013 Enterprise and SQL Server 2012 Standard edition vs. Enterprise - feature question

I can't seem to find any clear answers to the implications of installing SQL Server 2012 standard edition vs. enterprise in regards to SharePoint 2013.
I understand that to get many of the features you need Enterprise edition of SQL 2012; but, what I can't figure out is if the backend SharePoint SQL 2012 is standard; but, the PowerPivot/SSRS server is Enterprise will we still get the features?
If we have 3 tier SharePoint farm, one of those tiers is for the SQL Server database backend. If that SQL instance is 2012 standard and we add another server to the farm w/ SQL 2012 Enterprise to handle the tabular models, PowerPivot, and SSRS in integrated
mode will we still get the features?
Or, can we (should we) install Enterprise 2012 as the SharePoint database backend and let that instance triple down as also the PowerPivot and SSRS instance?
The Degenerate Dimension

Hi MMilligan,
SQL Server 2012 Standard is not supported PowePivot for SharePoint . In addition, SQL Server 2012 Standard is also not support some Reporting Services Features.
For more information, please refer to Features Supported by the Editions of SQL Server 2012:
http://msdn.microsoft.com/en-us/library/cc645993.aspx.
Install SQL Server BI Features with SharePoint 2013 (SQL Server 2012 SP1):
http://msdn.microsoft.com/en-us/library/jj218795.aspx.
If you have any problem, please feel free to let me know.
Thanks.
If you have any feedback on our support, please click
here.
Maggie Luo
TechNet Community Support

Server 2003 SBS (with Exchange 2003) migrate to new machine Server 2012 Standard (with Exchange 2013)

Similar Messages

Maybe you are looking for