Microsoft Windows Server 2015 Administration Guide
June 19, 2015 by Similar to past articles this series of basic deployment articles will be used to capture a specific environment to also be used as the foundation for many Skype for Business (SfB) Server 2015 specific deployment articles. Starting with a single Standard Edition Skype for Business Server in a fresh Active Directory forest future articles will build on this deployment with additional component installation like Edge Services, Exchange Server integration, etc.
Mar 27, 2015 - The installation is quick and easy. Step one: Install the Web Server (IIS) role. Open the Server Manager and click Add Roles and Features. Learn to manage your infrastructure in a cost-effective and high-performance manner. Explore our Windows Server training opportunities and certifications.
Throughout this series of articles the same basic instructional flow is used as for previous releases. Although it may not have been obvious the usage of bulleted items is intentionally specific. Toyota camry 2003 service manual torrent.
Steps starting with a bullet are mandatory to reach the same level of installation completion as the article intends to provide at the end. Yet normal paragraphs without bullets may include optional steps intended to provide a deeper understanding of a previous action or cover the installation of optional tools or components used to aid in knowledge transfer of the topic at hand. This format aids in skimming through the article for repeated installations. Environment For these articles specific to Skype for Business Server 2015 a new lab environment has been created which is slightly different to environments used in the Lync Server articles.
An important change from the past is that a single, flat internal Active Directory and SMTP/SIP domain namespace is now being utilized. This decision was made based on two factors: that a single namespace is easier to deal with when performing fresh lab installations and also that this reflects more common best practices today. Because many corporate networks still utilize disparate namespaces the difference between them may be specifically called out in these articles when prudent for educational reasons. As was also done in the previous Lync Server 2013 deployment articles a valid Top Level Domain (TLD) name was selected for the single namespaces to allow for the use of public certificates where desired, as described in this.
A joint Active Directory and primary SIP/SMTP namespace of jdskype.net is used throughout this new series of articles. Physical Host: VMware ESXi 6.0 server running on an HP ProLiant DL380 with 96GB of RAM and 12 physical CPU cores.
Domain Controller: A single Windows Server 2012 R2 x64 guest promoted to a domain controller for the new Active Directory forest root domain of jdskype.net. Skype for Business Front End Server: A second virtual guest running Windows Server 2012 R2 x64 Standard Edition and joined to the jdskype.net domain.
The default domain administrator account used to perform all steps is a member of the Domain Admins, Enterprise Admins, and Schema Admins domain security groups. The Forest and Domain functional levels were set to Windows Server 2012 R2. A Windows Enterprise Certificate Authority was deployed on the domain controller to provide SSL certificates for internal services. The CA configuration was updated to provide access to the Certificate Revocation List via HTTP, as explained in. The Root CA certificate was created with a hash algorithm of SHA256 and a 2048 bit key length.
While optional, an Exchange Server 2013 deployment was also previously completed in this environment which will be utilized in future integration articles for features like Unified Messaging or Outlook Web Access integration. Deployment This article will begin with the installation of a single Standard Edition Skype for Business Front End Server. For the purposes of test or educational lab environments it is more efficient to use this option than to deploy Enterprise Edition servers which requires at least one additional backend SQL Server. For details specific to deploying Enterprise Edition pools the should be used to accomplish this as it covers an Enterprise Edition deployment as the primary example. The first article in this series will address the following preparation steps:. Creating a File Share. Configuring DNS Records.
Installing the Server Prerequisites. Installing the Administration Tools.
Preparing Active Directory. Preparing the Central Management Store Before performing any of these steps though the following actions were already completed in the environment:. Windows Server 2102 R2 installed with a static IP address on a new server. Renamed the server and joined it to the Active Directory domain (e.g. Signed into the server using the default domain administrator account (e.g.
JDSKYPE administrator). Create File Share As this will be a Standard Edition server then it is supported to collocate the required file share on the same server, unlike Enterprise Edition server which must use a separate server to host this.
Administration Windows Server 2012 R2
Create a new folder on the server (e.g. SFBShare) anywhere on the server. The following path was used in this lab deployment: C: SFBShare. Verify that the local Administrators group is already granted Full Control at the NTFS file permission level and then enable sharing for this folder. Provide a name for the new share (e.g. SFBShare) and then assign Full Control share permissions to the local Administrators group. The permissions on this share will be when the Topology is published in a later step, so this step is just to ensure that the later installation process will have sufficient rights to this directory to perform the required changes.
Verify that the newly created directory is now available as a shared directory. Configure DNS Records The next step is to manually create a few DNS records to support various client lookup requests. The following table lists the various Fully Qualified Domain Names (FQDN) which must be manually created for a Standard Edition server deployment. Many guides will instruct that these records are all created as a standard Host (A) record but most of these records are also supported as an Alias (CNAME) record. Utilizing Alias records when supported is generally a better practice in DNS than managing multiple Host records, but either approach is acceptable.
Jeff, Is there a “manual” way to “Prepare First Standard Edition Server”? Our security has a requirement that no software be installed on the system drive unless it’s unavoidable.
This was possible for Lync 2010 (batch file to run the commands), I was hoping it was also available for Skype for Business 2015. Yes, it’s not streamlined but it works and keeps them off my butt hehe. Thank you for all the time you take preparing these blogs and answering these questions from everyone. I, at least, appreciate your efforts.
Microsoft Server Administration Tools
My Lync 2010 install went MUCH smoother after I found your blog (smile).