Help needed - Planning Server 2012 solution, DC/Exchange/SQL/RDP host/Remote apps etc

Hi All,
I have a client needing me to provide a Windows server based solution for their business. I have limited experience with Server 2012, although I have worked with 2008R2 and SBS2011, I am needing some guidance with this 2012 project.
The client has about 8-10 local users who work at one office with an NBN connection, and 2 other locations that have 3-5 users at each location. I am needing to provide them with a server based solution to manage their data, remote access and also their
email. They are also likely to expand to another physical office soon.
I need to provide them with a DC controller, Exchange server and possibly an SQL server in the future. They currently use an Act database, but I have been told that once the database in ACT grows to 4G, a dedicated database is required?
I am currently thinking of having one physical server and virtualising the additional servers on this platform, however I come from a UNIX background and have not virtualised using Hyper V or ESXi before. I have read a little regarding the CLI and GUI Hyper
V options, but I really need advice on what will suit my needs best from someone that has done it.
I am thinking I maybe should recommend one physical machine with Server 2012 Std which, from what I understand, will allow me to install the host hyper V host on the physical machine and then I could possibly install an instance of Server 2012 as
the DC, Exchange and SQL server on one VM licence, however I have read it is not preferred to have the exchange server on the same VM as the DC but have read that limiting the memory usage of Exchange can negate these issues?
I will also need to have a terminal server/RDP session host in there as well which I could maybe use the 2nd VM licence for.
I suppose my question is, considering that I need to end up with a DC, Exchange server, terminal server/RDP session host and possibly a SQL server in the future, am I better off virtualising and running these on a Server 2012 Std licence, that allows a hyper
v host + 2xVM's or should I be splitting these roles up on different physical machines, keeping in mind costs need to be kept to a minimum.
Also I need to consider the Microsoft Office side of things. Is it more financially viable to use office licences and use remote apps from the terminal server, or just purchase Office H&B for the workstations/laptops and have their outlook connected
directly to the exchange server?
I am concerned from the performance viewpoint that if I run the DC/Exchange and SQL from one VM, then the TS/RDP Host from the other VM licence it may be too much for the DC/Exchange/SQL VM to handle.
I have used SBS 2011 in a few locations with Exchange and the SQL and DC roles installed on HP DL and ML gen 8 servers, and although they run a little slow on the console, they seem to serve the network clients fine.
If do end up running on one physical machine the Hyper V host, one VM as a DC, Exchange and SQL server, and the other VM licence as a RDP session host, what sort of spec'd machine would be recommended to be able to do this, keeping in mind
I usually lean towards HP servers.
Anyhow, thx in advance and any comments or suggestions will certainly be appreciated.
Mkm

Hello,
sorry but in your case without the knowledge of all major requirements i would suggest that you or your client contact an expert and not work with the forums to get this amount of information and setup requirements.
Exchange on DCs is NOT recommended, even not from Microsoft. Also it is highly recommended to run at least 2 DC/DNS/GC per domain for failover and redundancy, of course NOT on the same physical machine.
RDS servers should also run on dedicated machines and not be used for anything else.
SQL should also run on a separate server.
You cannot compare SBS version with regular server versions, the concept behind is different.
With that small amount of users you should consider using an Office365 solution where you could use a plan that fits your needs and have just computers for your client employees.
But as stated above therefore you should find an experienced consultant.
Best regards
Meinolf Weber
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://blogs.msmvps.com/MWeber
Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
Twitter:  

Similar Messages

  • Do i need Windows Server 2012 CAL's if only accessing the Exchange Server?

    I am about to implement a deticated Exchange 2013 enterprise server, with windows 2012 server its going to be a central server for 250 users, this means the server is on a central location and users are connecting remotely to this server.
    The clients will only be accessing trough outlook , i understand i need 250 Exchange 2013 User CAL's, but do i also need need Windows Server 2012 CAL's ?
    thanks in advance !

    Hi Jan,
    For license question, I would suggest you make a phone call to Microsoft directly:
    In the United States, call (800) 426-9400.
    In Canada, call (877) 568-2495.
    http://office.microsoft.com/en-us/exchange/exchange-server-licensing-licensing-overview-FX103746915.aspx
    Frank Wang
    TechNet Community Support

  • Windows Server 2012 R2 with Exchange Server 2013 SP1 Completely fresh install giving errors signing into EAC

    Hi,
    I am struggling with a completely clean installation of Server 2012 R2 and Exchange 2013 SP1.  I followed these steps:
    Installed Server OS
    Windows Updates
    Added Active Directory Role (This is a single standalone server that would have been SBS until it was dropped)
    Added DHCP & DNS
    Added Certificate Services
    Added Windows Server Update Services (WID Database & WSUS Services)
    Windows Updates
    Added Media Foundation
    Added File Server Resource Manager and Work Folders
    Added Windows Server Backup
    Windows Updates
    Checked all running without errors in Server Manager and performed a full bare bones backup.
    Ran Setup.exe from Exchange 2013 SP1 disc.
    Installed Pre-requisites and then rebooted
    Windows Updates
    Ran Setup.exe from Exchange 2013 SP1 disc.
    Installation completed without errors
    Rebooted
    Checked all running without errors in Server Manager.
    I Launch Exchange Administrative Center and get "problem with website's server certificate error" (normal on machine with self-assigned certificates).  Click Continue to Website and get:
    Windows Security dialog box:
    iexplore - "The server localhost is asking for your username and password.  The server reports that it is from Digest"
    however no username and password combination will work:  have tried [Administrator]; [Domain\Administrator] even created a user to no avail.
    I believe the issue is somewhere in the IIS configuration because I also get the same error when trying to log into the server website from either the server or another machine on the network.
    I have tried the complete installation three times now:  (full disclosure not all of the same features/roles each time).  On the first attempt I got this error immediately and on try number 2 was able to get into the EAC and created the mailboxes
    but then it started giving the same error.  The above steps are try number 3.
    Any ideas?
    Thanks in advance.
    Andy Halford
    P.S. A Follow up which might be significant:  The Default Web Site is not running and will not start (it was previously running before the Exchange installation) and when I try I get the message that Another Website may be using the same port however none
    of the others (Exchange Back End or WSUS Administration) are using ports 80 or 443 and I still get the error when they are both stopped.

    Could you post the list of sites:
    appcmd list site
    The ones listening on port 80:
    appcmd list site /bindings:http/*:80:
    And on port 443:
    appcmd list site /bindings:https/*:443:
    Step by Step Screencasts and Video Tutorials

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

  • SQL Server 2012 - Cannot connect to SQL Alias (Connection to serverName is good)

    Hi there,
    On my 64 bit installation of SQL Server 2012 - I have enabled SQL Alias using cliconfg 32 bit and as well as on cliconfg 64 bit.
    On my WFE (Web Front End server) I have set the SQL ALias as well (both 32 bit and 64 bit).
    From WFE (Web Front End) server I can ping the SQL server name but cannot ping the SQL ALias. Any clue what I might be missing?
    Thanks.

    but cannot ping the SQL ALias
    Hello,
    Of course you can't "ping" a SQL Server alias, this Setting is only used by SQL Server Client components and not by any other network component. You could use
    SqlCmd or SSMS or ODBC admin to test the alias.
    Olaf Helper
    [ Blog] [ Xing] [ MVP]

  • 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

  • How many CALs do i need? Server 2012 - Exchange 2013 - RDP

    Hi,
    (I apologize for the grammar and spelling mistakes, but im confident in the fact that the text is understandable. If not, please let me know. I have used UK English for spelling.)
    I did some research and read the following:
    (unable to post links, my email needs to be 'verified')
    And some MS pages regarding the CALs for Windows 2008 R2 (don't ask why).
    This is basically what i want to do:
    OS:                        
    Windows 2012 R2, possibly 2x because of the RDS role.
    Roles Server1:  Active Directory and Exchange 2013
    Roles Server2: File server and RDS
    Users:                 
    20
    PC’s:                    
    Approx. 15. Not sure about the exact numbers, but i am sure that there are more users than client pc’s.
    Users RDP:        
    Starting with 10 but eventually every user will be using RDP, so it might be also 20. The 10 we start with will not have the ability of logging into a client PC but RDP only.
    MS Software:    Outlook 2010 or 2013, depends on the support by MS.
    We are going to start with an AD with a home folder, roaming profiles and an email account. If everything go’s whell, we plan to start letting users connect tot heir workspace via RDP.
    I came to the following conclusion and need your input on this:
    20 User CALs, As far as i know, I need 1 user cal for an AD account and a RDP cal for
    one RDP account. Without a User CAL, i cant issue a RDP user cal, is this correct?
    20 RDP User CALs, does this mean that all my users can log into a RDS session via any client, even their own private pc?
    No Device calls, redundant?
    20 Exchange CALs, I am not sure about this one, the second link i found only mentions acces via web and mobile. I would also like to know if the Exchange CAL is per user or email. If it’s per user, then wat do i do with an email that is meant for multiple
    users?
    2 Server CALs, This is just buying 2012R2 isnt it? Does this also allow me to use one physically and the other as a VM in the physical one? Just asking, im not really going to use a VM.
    Hope you guys can help me out on this one, i didn’t expect the CALs would bet his complicated.

    Hi,
    Under Per User licensing, you need a license for each unique human that will access the software.  Based on what you have written above, below is a general description of the licenses you need:
    20 Per User Windows Server CALs
    20 Per User RDS CALs
    20 Per User Exchange Standard CALs
    1 Exchange Server 2013 Standard license
    2 Windows Server 2012 R2 Standard licenses
    Notes: 
    Each Server 2012 R2 Standard license allows you to install it on a physical server (up to 2 CPU sockets) with the Hyper-V role installed, and install it in 2 VMs.  The key here from a licensing perspective is the installation on the physical server
    is only being used for Hyper-V--if you use it for some other purpose (like AD, SQL, etc.) then you are only permitted to run 2012 R2 on 1 VM without an additional license.  Running your servers as VMs is the common and recommended method now, unless
    you have a specific reason not to.
    I listed two 2012 R2 licenses above because from your description I get the idea that you will have 2 physical servers.
    It is preferred to split key roles/functions onto separate VMs if possible.  For example, it would be preferred to have Exchange on its own VM(s).  This is obviously subject to your specific situation, budget, etc.  In smaller environments
    some roles will be combined in order to save money.
    I did not include licenses for Office in the list above.
    Yes, Per User licensing means the user can access the software from any device, even their own private pc.
    I recommend you purchase licenses through a MS volume licensing program that fits your needs.  Adding Software Assurance (SA) to your licenses will allow you to get the new versions when they are released as well as give some additional licensing rights.
    As always, it is essential to read the Product Use Rights (PUR) document, licensing agreements, terms and conditions, etc., as applicable to your licenses.
    I recommend you also take a look at the Office365 plans that include Office/Exchange/etc.  There are Exchange-only plans as well.  Depending on your needs it may be preferred to have your users access Exchange in the cloud and run RDS on premises. 
    Licensing Windows Server 2012 R2 Remote Desktop Services and Microsoft Desktop Applications for Use with RDS
    http://www.microsoft.com/licensing/about-licensing/briefs/winserv2012-rds.aspx
    Exchange Server 2013 licensing
    http://products.office.com/en-us/exchange/microsoft-exchange-server-licensing-licensing-overview
    -TP

  • Need help to deploy server 2012 with DNS role installed.

    I want to deploy an image using wds on server 2012. I will be using an answer file for unattended installation with little touch as possible. My answer file works great but I can't get the auto-logon to work and the FirstLogonCommand to run. I added
    Components\7 oobeSystem\amd64_ Microsoft-Windows- Shell-Setup _neutral\FirstLogonCommands to my answer file using Windows Image Manager and added these values:
    CommandLine = powershell -command Install-WindowsFeature DNS –IncludeManagementTools -IncludeAllSubFeature -Restart
    Description =Install dns server
    Order = 1
    Then I did auto logon located at Components\7 oobeSystem\amd64_ Microsoft-Windows- Shell-Setup _neutral\Autologon and added these values:
    Domain = contoso
    Enabled = true
    LogonCount = 1
    Typed the password
    Username = Administrator
    These two components alone don't work. It installs server 2012 OK and bypasses all the screens I want to bypass it even joins the domain
    contoso successfully. I have to manually logon and then when I logon no scripts or anything is ran. When server manager opens dns role is not installed and not even located under tools.
    Things I tried:
    Open cmd as admin and typed "powershell -command
    Install-WindowsFeature DNS –IncludeManagementTools -IncludeAllSubFeature -Restart." this worked and installed roles successfully
    If I missed anything to help you troubleshoot just ask.

    Unfortunately you are posting in the wrong forum.  You need to post deployment issues in the Windows Server Deployment forum.
    ¯\_(ツ)_/¯

  • Licensing help needed for datacenter server with vm running windows server 2012 essentials and ten virtual desktops for remote access

    NPO wants to get windows server 2012 r2 datacenter as the main operating system and then windows server 2012 r2 essentials plus 10 windows 8.1 as virtual desktops.  Each desktop for one remote user running office 2013.  Is there a better configuration?
     In either case what licenses does the NPO need to purchase?
    Bob

    Hi,
    For license related questions we recommend you contact Microsoft licensing specialist.
    http://support.microsoft.com/kb/141850/en-us
    Regards.
    Vivian Wang

  • Hyper Disk Layout and Raid For Essintal Server 2012 R2 With Exchange

    Hi would raid mirror be good enough support configuration on single server run both essentials server 2012  and  exchange 2013  new to exchange look for input and suggestions 
    user load is very light just 5  
    boot disk  120 gig ssd  on it own Controller run 2012 run with hyper v installed
    2 x 3 Tb raid 1 by Lsi 1064e raid control   essentials server 2012  disk are vhdx fixed size  two each
    2 x 2 Tb raid 1 by Lsi 1064e raid control   2012 R2 server  disk are vhdx fixed size  two each
    System specs is 2 x Amd  opertron  4122 with 32 gig of Ram  4 core to each os
    Andy A

    Hi would raid mirror be good enough support configuration on single server run both essentials server 2012  and  exchange 2013  new to exchange look for input and suggestions 
    user load is very light just 5  
    boot disk  120 gig ssd  on it own Controller run 2012 run with hyper v installed
    2 x 3 Tb raid 1 by Lsi 1064e raid control   essentials server 2012  disk are vhdx fixed size  two each
    2 x 2 Tb raid 1 by Lsi 1064e raid control   2012 R2 server  disk are vhdx fixed size  two each
    System specs is 2 x Amd  opertron  4122 with 32 gig of Ram  4 core to each os
    1) Boot Hyper-V from cheap SATA or even USB stick (see link below). No point in wasting SSD for that. Completely agree with Eric. See:
    Run Hyper-V from USB Flash
    http://technet.microsoft.com/en-us/library/jj733589.aspx
    2) Don't use RAID controllers in RAID mode rather (as you already got them) stick with HBA mode passing disks AS IS, add some more SSDs and configure Storage Spaces in RAID10 equivalent mode and use SSDs as a flash cache. See:
    Storage Spaces Overview
    http://technet.microsoft.com/en-us/library/hh831739.aspx
    Because having single pool touching all spindles would provide you better IOPS compared to creating "islands of storage" that are waste or performance and hell of management.
    3) Come up with IOPS requirements for your workload (no idea from above) keeping in mind RAID10 provides ALL IOPS for reads and half IOPS for writes (because of mirroring). So as single SATA can do maybe 120-150 IOPS and single SAS can do up to 200 (you
    don't provide any model names so we have to guess) you may calculate how many IOPS your config would give away in a best and worst case scenario (write back cache from above will help but you always need to come from a WORST case). See calculator link below.
    IOPS Calculator
    http://www.wmarow.com/strcalc/
    Hope this helped a bit :)
    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.

  • 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

  • SBS2011 - Cross domain Migration to Server 2012 R2 w/ Exchange 2013

    I am attempting to find the best way to do this, and any input/guidance would be greatly appreciated.
    Source Server: SBS 2011 Standard - Internal domain costco.local
    Target Server: Server 2012 R2, 2 virtuals, one for the domain controller, one for Exchange 2013 - Internal domain ad.costco.com
    I know that in order to establish a trust relation, I must add a secondary domain controller to the SBS2011 domain and transfer FSMO roles.  My question is, can I use a trial Server 2008 R2 as an interim DC, create the trust, use ADMT to migrate user
    accounts to the new domain and move mailboxes from the SBS server with the trust established on the Server 2008 DC?  Or do I have to install an interim exchange server and move the mailboxes and remove the SBS server from the domain?
    If that is the case, can I use a 180 Trial of Server 2008 R2 and Exchange 2010 on two separate virtuals on the old domain, move all user accounts and mailboxes to a standard domain temporarily.  Then from the standard domain move user accounts and mailboxes
    to the Server 2012 R2 DC and Exchange 2013 virtual?
    It would be great if I could just establish a trust with with a second DC with SBS and move user accounts and mailboxes to the new internal domain, but I'm not sure if that is possible.  Any insight would be greatly appreciated!

    SBS can't do trusts but the migration prep tool temporarily allows them I believe.  Have a look at this link dealing with migration to 2012 essentials from SBS, it doesn't deal with exchange though:
    https://technet.microsoft.com/en-us/library/jj721754.aspx
    There is also a recent thread "Migrating from SBS 2011 to Server 2012R2 Standard & Exchange 2013" that may have some info.
    -- Al

  • Server 2012 R2 how to view RDP user network use?

    Hi All,
    In Server 2008 you were able to go into tsadmin, click right on a user and click "Status" which would show their network usage (bytes received, bytes sent).
    I noticed in Server 2012, when I check users under Collections this option is no longer there. How can I view a user's network usage?

    Hi,
    I would like to check if you need further assistance.
    Thanks.
    Jeremy Wu
    TechNet Community Support

  • DSC, SQL Server 2012 Enterprise sp2 x64, SQL Server Failover Cluster Install not succeeding

    Summary: DSC fails to fully install the SQL Server 2012 Failover Cluster, but the identical code snippet below run in powershell ise with administrator credentials works perfectly as does running the SQL server install interface.
    In order to develop DSC configurations, I have set up a Windows Server 2012 R2 failover cluster in VMware Workstation v10 consisting of 3 nodes.  All have the same Windows Server 2012 version and have been fully patched via Microsoft Updates. 
    The cluster properly fails over on command and the cluster validates.  Powershell 4.0 is being used as installed in windows.
    PDC
    Node1
    Node2
    The DSC script builds up the parameters to setup.exe for SQL Server.  Here is the cmd that gets built...
    $cmd2 = "C:\SOFTWARE\SQL\Setup.exe /Q /ACTION=InstallFailoverCluster /INSTANCENAME=MSSQLSERVER /INSTANCEID=MSSQLSERVER /IACCEPTSQLSERVERLICENSETERMS /UpdateEnabled=false /IndicateProgress=false /FEATURES=SQLEngine,FullText,SSMS,ADV_SSMS,BIDS,IS,BC,CONN,BOL /SECURITYMODE=SQL /SAPWD=password#1 /SQLSVCACCOUNT=SAASLAB1\sql_services /SQLSVCPASSWORD=password#1 /SQLSYSADMINACCOUNTS=`"SAASLAB1\sql_admin`" `"SAASLAB1\sql_services`" `"SAASLAB1\cubara01`" /AGTSVCACCOUNT=SAASLAB1\sql_services /AGTSVCPASSWORD=password#1 /ISSVCACCOUNT=SAASLAB1\sql_services /ISSVCPASSWORD=password#1 /ISSVCSTARTUPTYPE=Automatic /FAILOVERCLUSTERDISKS=MountRoot /FAILOVERCLUSTERGROUP='SQL Server (MSSQLSERVER)' /FAILOVERCLUSTERNETWORKNAME=SQLClusterLab1 /FAILOVERCLUSTERIPADDRESSES=`"IPv4;192.168.100.15;LAN;255.255.255.0`" /INSTALLSQLDATADIR=M:\SAN\SQLData\MSSQLSERVER /SQLUSERDBDIR=M:\SAN\SQLData\MSSQLSERVER /SQLUSERDBLOGDIR=M:\SAN\SQLLogs\MSSQLSERVER /SQLTEMPDBDIR=M:\SAN\SQLTempDB\MSSQLSERVER /SQLTEMPDBLOGDIR=M:\SAN\SQLTempDB\MSSQLSERVER /SQLBACKUPDIR=M:\SAN\Backups\MSSQLSERVER > C:\Logs\sqlInstall-log.txt "
    Invoke-Expression $cmd2
    When I run this specific command in Powershell ISE running as administrator, logged in as domain account that is in the Node1's administrators group and has domain administrative authority, it works perfectly fine and sets up the initial node properly.
    When I use the EXACT SAME code above pasted into my custom DSC resource, as a test with a known successful install, run with the same user as above, it does NOT completely install the cluster properly.  It still installs 17 applications
    related to SQL Server and seems to properly configure everything except the cluster.  The Failover Cluster Manager shows that the SQL Server Role will not come on line and the SQL Server Agent Role is not created. 
    The code is run on Node1 so the setup folder is local to Node1.
    The ConfigurationFile.ini files for the two types of installs are identical.
    Summary.txt does have issues..
    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:          0x86D8003A
      Error description:             The cluster resource 'SQL Server' could not be brought online.  Error: There was a failure to call cluster code from a provider. Exception message: Generic
    failure . Status code: 5023. Description: The group or resource is not in the correct state to perform the requested operation.  .
    It feels like this is a security issue with DSC or an issue with the setup in SQL Server, but please note I have granted administrators group and domain administrators authority.  The nodes were built with the same login.  Windows firewall
    is completely disabled.
    Please let me know if any more detail is required.

    Hi Lydia,
    Thanks for your interest and help.
    I tried "Option 3 (recommended)" and that did not help.
    The issue I encounter with the fail-over cluster only occurs when trying to install with DSC!
    Using the SQL Server Install wizard, Command Prompt and even in Powershell by invoking the setup.exe all work perfectly.
    So, to reiterate, this issue only occurs while running in the context of DSC.
    I am using the same domain login with Domain Admin Security and locally the account has Administrators group credentials.  The SQL Server Service account also has Administrators Group Credentials.

  • SQL Server 2012 Deploy Database to SQL Azure...

    I have spent many days trying to copy a simple test database from my PC to SQL Azure but with little success.  Then I installed SQL Server 2012 and see a new task:
    Deploy Database to SQL Azure...  It looks like an automated extraction to DAC and then creating the Azure database all in one step.
    I was elated, but got hit with the following three types of errors.
    One or more unsupported elements were found in the schema used as part of a data package.
    Error SQL71564: The element Extended Property: [dbo].[Accounts].[Address].[MS_Description] is not supported when used as part of a data package (bacpac).
    Error SQL71564: Table Table: [dbo].[Activities] does not have a clustered index.  Clustered indexes are required for inserting data in this version of SQL Server.
    Error SQL71564: Element User: [NT AUTHORITY\NETWORK SERVICE] has an unsupported property AuthenticationType set and is not supported when used as part of a data package.
     (Microsoft.SqlServer.Dac)
    May I know what I can do on the on-premise database to rid of the first and third error?
    Thanks.

    Hello,
    1) Remove the Extended Property from the (?) column Address in table Accounts.
    BTW, for small databases it's sometimes easiere to generate a script for the database (and modify it slightly) instead of using the Wizard
    Olaf Helper
    Blog
    Xing
    What is Extended Property?   What is this .MS_Description?   I can't see it in the table designer or the Column Properties.  (I don't know whether this was corruption caused by Data Sync I used earlier.)  How do I remove it.
    Of all the methods of copying SQL Server to Azure SQL, this one gives the least mistakes.  If I can solve this Extended Properties thing hopefully I can migrate the database over.

Maybe you are looking for