Welcome to GotSpeech.NET Sign in | Help

Verbal Input

Eliminating the keyboard...one spoken word at at time...
Exploring Lync Server 2010 - Part 22 - Installing Lync Server 2010 Standard Edition IV

Welcome to Part 22 of Exploring Microsoft Lync Server 2010.

In our last segment, we made good progress installing Lync Server 2010 Standard Edition. In this section we will be completing the installation.

Let’s begin by restarting the MdcDc Base Machine. After the machine has restarted, go ahead and login, and you will be presented with the ‘Server Manager’. Navigate to the “MDCBASE01”node under HyperV as shown below.

If it is not started, right click on the MdcLyncServer2010Standard Virtual Machine and select ‘Start’ from the drop down menu. Next, right click on the MdcLyncServer2010Standard Virtual Machine a second time and select ‘Connect’ from the menu as shown below.

This will open up a window into the MdcLyncServer2010Standard Virtual Machine.

Once the window into the MdcLyncServer2010Standard Virtual Machine opens, enter CTRL-ALT-END and go ahead and login. You should be logging into the mdc.com domain and not the local machine, so use the domain Administrator account and password.

After logging in to MdcLyncServer2010Standard Virtual Machine, you should be presented with the ‘Server Manager’ screen.

Our next step in installing Lync Server 2010 Standard Edition is to engage ‘Step 3: Request, Install or Assign Certificates’ from the Deployment Wizard. But before we tackle that, there is something that needs to be taken care of first

Back in Part 11 when we were installing Active Directory, we also installed something called ‘Active Directory Certificate Services’.

<< Special Note Here>>

I actually added the instructions for installing ‘Active Directory Certificate Services’ to Part 11 after I started writing this part when I discovered that I had neglected to install them. I have updated the instructions in Part 11 to include installing ‘Active Directory Certificate Services’. If you have been following along with these blog posts as they have been released, you will need to go back and have a look at Part 11 again. The instructions for installing ‘Active Directory Certificate Services’ are the last 19 screen shots at the end of Part 11.

Active Directory Certificate Services is Certification Authority (CA), which means that it can issue certificates to requestors. In order for the process to work properly, a ‘Certificate Chain’ needs to be setup between the Certification Authority (CA) and individual certificates.  A ‘Certificate Chain’ establishes a ‘chain of trust’ between a Certification Authority (CA) and an individual certificate.

In our case, the Certification Authority (CA) is running on the MdcDc Virtual Machine and any certificates that we request when installing Lync Server 2010 Standard will live on the MdcLyncServre2010Standard virtual machine.

Therefore we must setup a ‘Certificate Chain’ between the CA running on MdcDc and any certificates that will be located on MdcLyncServre2010Standard.

To start off, fire up Windows Explorer and create a new folder off the root of C called ‘Lync Server Certificates’ as shown below

Next, close Windows Explorer open IE and enter the following URL

http://MdcDc.mdc.com/certsrv

You will be prompted for some credentials. Go ahead and enter ‘Administrator’ as the login in name followed by the password for the MDC\Administrator account and then click the ‘Ok’ button as shown below

You will be shown the following page

What we have here is the site where we can make requests for new certificates. This site was setup back in Part 11 when we installed ‘Active Directory Certification Services’

Click on the ‘Download a CA certificate, certificate chain or CRL’ as shown below

The following page will be displayed

Click on ‘Download CA certificate chain’ link as shown below

Click ‘Save’ in the resulting file download dialog as shown below

Save the file to ‘C:\Lync Server Certificates’ as shown below

After the file is saved, close the download complete dialog, and then close IE

Next we need to install the certificate chain that we just downloaded

Click the ‘Start’ button, click ‘Run’ as shown below

In the run dialog, enter ‘mmc’ and click ‘Ok’ as shown below

You will be shown the following screen

On the file menu, click ‘Add/Remove Snap-in’ as shown below

In the resulting screen select ‘Certificates’ in the left hand pane and then click on the ‘Add’ button as shown below

In the resulting dialog, click the radio button next to ‘Computer Account’, and then click the ‘Next’ button as shown below

Next make sure the radio button beside ‘Local Computer’ is selected and click the ‘Finish’ button as shown below

This takes us back to the ‘Add/Remove Snap-in’ screen. Click the ‘Ok’ button as shown below

This takes us back to the MMC Console. Expand the newly added ‘Certificates’ node to display the following screen

Now, expand ‘Trusted Root Certificate Authorities’ as shown below

Right click on ‘Certificates’, select ‘All Tasks->Import’ as shown below

You will be presented with the Certificate Import Wizard’ as shown below

Simply click on the ‘Next’ button to be taken to the following screen

Click the ‘Browse’ button as shown below

Navigate to the folder at C:\Lync Server Certificates’ and select the file that was recently saved in this folder and then click ‘Open’ as illustrated below. (you may have to change the filter to ‘All Files’ before you can see the file)

Back at the ‘Certificate Import Wizard’, click the ‘Next’ button as shown below

Accept the default values here and click the ‘Next’ button as shown below

Finally, click on the ‘Finish’ button as shown below

A little confirmation dialog appears. Click ‘Ok’ to complete the process as shown below

You can now close MMC.

At this point, you will need to restart the Lync Server 2010 Installation from the Lync Server 2010 media by running setup.exe.  If you need a refresher on how to do this, instructions can be found in either Part 20 or Part 21.

Click on the ‘Install or Update Lync Server System’ link in the ‘Deployment Wizard’ as shown below

Ok, so let’s now move on to ‘Step 3 Request, Install or Assign Certificates’. Click on the ‘Run’ button as shown below

You will be presented with the ‘Certificate Wizard’ first screen. Click the arrow to the left of ‘Default Certificates’ to expose which certificates will be created, and then click on the ‘Request’ button as shown below

On the resulting screen, click the ‘Next’ button as shown below

Next we are presented with the ‘Deployed or Immediate Requests’ screen. Make sure that the ‘Send the request immediately to an online certification authority’ is checked and then click the ‘Next’ button as shown below

The ‘Choose a Certificate Authority (CA)’ screen is now shown. Notice that the radio button next to ‘Select a CA from the list detected in your environment’ has been selected and something has been selected in the drop down as well. What is selected in the drop down is the name of our Certificate Authentication Services that is running on MdcDc. We installed the Certificate Services back in Part 11.

Simply accept these defaults and click the ‘Next’ button as shown below

On the resulting ‘Certification Authority Account’ page, accept the default values and click ‘Next’ as shown below

On the resulting ‘Specify Alternate Certificate Template’ page, accept the default values and click ‘Next’ as shown below

On the resulting ‘Name and Security Settings’ page, enter ‘Mdc Lync Server 2010 Standard Certificate’ as the ‘Friendly Name and click ‘Next’ as shown below

On the ‘Organization Information’ screen, enter ‘Mdc’ as the Organization and ‘Minneapolis’ as the Organizational Unit and then click ‘Next’ as shown below

In the ‘Geographical Information’ page, select ‘United States’ from the Country/Region drop down, enter ‘Minnesota’ for the State/Province and enter ‘Minneapolis’ for the City/Locality and the click ‘Next’ as shown below

 

On the ‘Subject Name/Subject Alternate Names’ screen simply click the ‘Next’ button as shown below

In the resulting ‘SIP Domain setting on Subject Alternate Names (SANs) screen, put a check mark next to mdc.com and the click the ‘Next’ button as shown below

On the resulting ‘Configure Additional Subject Alternate Names’ screen simply click the ‘Next’ button as shown below

Next you will be shown the ‘Certificate Request Summary’ screen. Click the ‘Next’ button to continue as shown below

The following will be display during the process

Once completed you will be presented with the following screen

Click the ‘Next’ button and you will be shown the following screen

Click the ‘Finish’ button to be taken to the following ‘Certificate Assignment’ screen

Click ‘Next’ to be taken to the ‘Certificate Assignment Summary’ screen as shown below

Click the ‘Next’ button. After a few moments, you will be presented with the completion screen for the ‘Certificate Assignment’ as shown below

 

Click ‘Finish’ to complete the process

The ‘Certificate Wizard’  now shows that our certificates have been assigned. Click ‘Close’ as shown below

Notice now that there is a green check mark with the word Complete next to Step 3 as shown below.

Next we move on to Step 4: Start Services. Simply click on the ‘Run’ button next to Step 4 as shown below

The ‘Start Services’ dialog is display. Simply click the ‘Next’ button as shown below

The following is display as everything is started

After a few moments you will be presented with the following

Finally, close the ‘Deployment Wizard’ by clicking the ‘Exit’ button

We have now completed the installation of Microsoft Lync Server 2010 Standard Edition.

Of course the configuration of the various parts of our installation is coming at us next, and we will start it all off in the next segment.

 

Thanks for reading

 

 

 

 

 

Exploring Lync Server 2010 - Part 21 - Installing Lync Server 2010 Standard Edition III

Welcome to Part 21 of Exploring Microsoft Lync Server 2010.

In our last segment, we installed the ‘Topology Builder’ and then used it to build and publish the topology for our Lync Server 2010 Standard Edition installation. In this section, we will be continuing the installation by installing the ‘Front End Role’.

Let’s begin by restarting the MdcDc Base Machine. After the machine has restarted, go ahead and login, and you will be presented with the ‘Server Manager’. Navigate to the “MDCBASE01”node under HyperV as shown below.

If it is not started, right click on the MdcLyncServer2010Standard Virtual Machine and select ‘Start’ from the drop down menu. Next, right click on the MdcLyncServer2010Standard Virtual Machine a second time and select ‘Connect’ from the menu as shown below.

This will open up a window into the MdcLyncServer2010Standard Virtual Machine.

Once the window into the MdcLyncServer2010Standard Virtual Machine opens, enter CTRL-ALT-END and go ahead and login. You should be logging into the mdc.com domain and not the local machine, so use the domain Administrator account and password.

After logging in to MdcLyncServer2010Standard Virtual Machine, you should be presented with the ‘Server Manager’ screen.

We need to install a few prerequisites at this point so let’s start with IIS. Although IIS is already installed we need to add a few items to it.

In ‘Server Manager’, click on Roles->Web Server (IIS) as shown below

In the right hand pane, scroll down to ‘Role Services’ and then click on the ‘Add Role Services’ link as shown below

You will be presented with the ‘Add Role Services’ dialog as shown below

In the section titled ‘Common HTTP Features”, put a check mark next to the following items:

·         Static Content

·         Default Document

·         Directory Browsing

·         HTTP Errors

·         HTTP Redirection

as shown below

Under the ‘Application Development’ section, put a check mark next to the following items:

·         ASP.NET

·         .NET Extensibility

·         Internet Server API (ISAPI) Extensions

·         ISAPI Filters

As shown below

Under the ‘Health and Diagnostics’ section, put a check mark next to the following items:

·         HTTP Logging

·         Logging Tools

·         Request Monitor

·         Tracing

As shown below

Under the ‘Security’ section, put a check mark next to the following items:

·         Basic Authentication

·         Windows Authentication

·         Client Certificate Mapping Authentication

·         Request Filtering

As shown below

Under the ‘Performance’ section, put a check mark next to the following items:

·         Static Content Compression

As shown below

Finally, under the ‘Performance’ section, put a check mark next to the following items:

·         IIS Management Console

·         IIS Management Scripts and Tools

As shown below

Click ‘Next’. When the following confirmation screen is displayed ,click the Install button as shown below.

You will be presented with the following screen as the installation progresses

When completed you will be shown the ‘Installation Results’ screen. Click ‘Close’ to complete the process as shown below

We next need to install Message Queuing

In ‘Server Manager’, navigate to ‘Features’ and in the right hand pane click on the ‘Add Features’ link as shown below

In the ‘Select Features’ dialog, expand ‘Message Queuing’ and ‘Message Queuing Services’ and then put a check mark beside ‘Message Queuing Server’ and ‘Directory Service Integration’ and then click the ‘Next’ button as shown below

On the resulting confirmation screen, click the ‘Install’ button as shown below

During the installation you will see the following screen

Once completed you can click the ‘Close’ button to complete the process as shown below

That completes the prerequisites that we needed to install, so let’s now install the Front End Role

At this point, we will again need to insert the Microsoft Lync Server 2010 Standard Edition media into the MdcLyncServer2010Standard Virtual Machine, which can be done in one of 2 ways.

If you have the physical DVD for Microsoft Lync Server 2010 Standard Edition

Insert the DVD into the DVD player on the MdcBase01 physical machine.

Select ‘Media->DVD Drive->Capture D:’ from the menu on the window into MdcLyncServer2010Standard Virtual Machine as shown below

If you have an iso file for Microsoft Lync Server 2010 Standard Edition

Select ‘Media->DVD Drive->Insert Disk’ from the menu on the window into MdcLyncServer2010Standard Virtual Machine as shown below

Navigate to the location of your iso file and select it as shown below

At this point, if you want to have the MdcLyncServer2010Standard Virtual Machine go full screen instead of looking at it through a window you can type CTRL-ALT-BREAK.

You should be presented with the following

Click on ‘Run Setup.exe’ and you will be taken back into the installation process as shown below

Click on ‘Install or Update Lync Server System’ as shown below

This opens up the ‘Deployment Wizard’ as shown below

To start off, click the ‘Run’ button next to ‘Step 1: Install Local Configuration Store’ as shown below

The following dialog will be displayed

Accept the default value here and click ‘Next’. You will be shown the following progress screen as the installation runs.

This process takes a few minutes, but when finished you will be shown the following

Click the ‘Finish’ button to complete the process. We are returned now to the ‘Deployment Wizard’, but notice that there is now a green check mark and the word ‘Complete’ beside Step 1 as shown below

Next, click the ‘Run’ button next to ‘Step 2: Setup or Remove Lync Server Components’ as shown below

Simply click ‘Next’ on the resulting screen as shown below

During the process you will see the following screen

After a few moments you will be presented with the following screen

Notice the red message at the bottom telling us that the machine needs to be restarted. Click the ‘Finish’ button and you will be shown the following dialog

Click the ‘Ok’ button. Notice the condition of the ‘Deployment Wizard’ as shown below

I guess a reboot is in order here so click the ‘Exit’ button on the ‘Deployment Wizard’ and then let’s restart the MdcLyncServer2010Standard Virtual Machine

Once the machine restarts, you will need to restart the Lync Server 2010 Installation form the Lync Server 2010 media by running setup.exe.  If you need a refresher on how to do this, instructions can be found earlier in this document.

The ‘Deployment Wizard’ should again be showing. Click on ‘Install or Update Lync Server System’ as shown below

We need to go back and re-run Step 2 again, so go ahead and click on the ‘Run’ button next to ‘Step2: Setup or Remove Lync Server Components’, as shown below

This results in the following which should look familiar since we have already seen it once

Click ‘Next’ which again results in the following screen as the installation progresses

This process takes a few minutes, when completed you will be shown the following screen

Click the ‘Finish’ button. Once we return to the ‘Deployment Wizard’ screen, you will notice that we now have a green check mark and the word ‘Complete’ beside Step 2 as shown below

Also notice that the ‘Run’ button next to Step 2 has now changed to ‘Run Again’. This would be used if we were to add/remove items from our Lync Server Topology in the Topology Builder which would eventually lead to re-running this step.

That wraps it up for Part 21 of Exploring Lync Server 2010. In the next part, we will be finishing up our Lync Server 2010 Installation

Thanks for reading

 

Exploring Lync Server 2010 - Part 20 - Installing Lync Server 2010 Standard Edition II

Welcome to Part 20 of Exploring Microsoft Lync Server 2010.

In our last segment, we started the installation of Microsoft Lync Server 2010 Standard Edition onto our MdcLyncServer2010Standard Virtual Machine by installing various pre-requisites and running a variety of items that prepared Active Directory.

Let’s now continue with the installation.

Now that we have finished preparing Active Directory, it is time to move to installing the Topology Builder. This is a new tool in Lync Server which allows you to design and validate a Lync Server Topology and then publish it to Active Directory.

Let’s begin by restarting the MdcDc Base Machine. After the machine has restarted, go ahead and login, and you will be presented with the ‘Server Manager’. Navigate to the “MDCBASE01”node under HyperV as shown below.

If it is not started, right click on the MdcLyncServer2010Standard Virtual Machine and select ‘Start’ from the drop down menu. Next, right click on the MdcLyncServer2010Standard Virtual Machine a second time and select ‘Connect’ from the menu as shown below.

This will open up a window into the MdcLyncServer2010Standard Virtual Machine.

Once the window into the MdcLyncServer2010Standard Virtual Machine opens, enter CTRL-ALT-END and go ahead and login. You should be logging into the mdc.com domain and not the local machine, so use the domain Administrator account and password.

After logging in to MdcLyncServer2010Standard Virtual Machine, you should be presented with the ‘Server Manager’ screen, which you can simply close because we do not need it at this point.

We need to insert the Microsoft Lync Server 2010 Standard Edition media into the MdcLyncServer2010Standard Virtual Machine, which can be done in one of 2 ways.

If you have the physical DVD for Microsoft Lync Server 2010 Standard Edition

Insert the DVD into the DVD player on the MdcBase01 physical machine.

Select ‘Media->DVD Drive->Capture D:’ from the menu on the window into MdcLyncServer2010Standard Virtual Machine as shown below

 

If you have an iso file for Microsoft Lync Server 2010 Standard Edition

Select ‘Media->DVD Drive->Insert Disk’ from the menu on the window into MdcLyncServer2010Standard Virtual Machine as shown below

Navigate to the location of your iso file and select it as shown below

At this point, if you want to have the MdcLyncServer2010Standard Virtual Machine go full screen instead of looking at it through a window you can type CTRL-ALT-BREAK.

You should be presented with the following

Click on ‘Run Setup.exe’ and you will be taken back into the installation process as shown below

As you can see, we have a green check mark and the word ‘Completed’ next to ‘Prepare Active Directory’

Click ‘Install Topology Builder’ in the right hand column as shown below

This is a rather quick process, you will see a few windows fly by, but when the install completes, you will see that there is a green check mark next to the ‘Install Topology Builder’ link which is also now grayed out as shown below

 

Next, we need to prepare the server as a ‘Central Management Store’ and prepare the database. A ‘Central Management Store’ is a centralized database of all Lync server settings which is replicated to all servers in a deployment.

 Click on the ‘Prepare the first Standard Edition Server’ link in the right hand column as shown below

You will be presented with the following dialog

Click the ‘Next’ button and you will be shown the following

This process will take a few minutes to complete. What is happening is that the server is being prepared as the first Standard Edition Server and also the ‘Central Management Store’ is being setup.

When completed you will see the following screen

 

Click the ‘View Log’ button to view the installation log if desired then click ‘Finish’ to exit this part of the process.

As you can see we now have a green check mark next to the ‘Prepare the first Standard Edition Server’ link in the right hand column as shown below

Next step is to define the topology with the Topology Builder. To start the Topology Builder, click on the ‘Start’ button and then click on ‘Lync Server Topology Builder’ as shown below

 

You will be presented with the following

The dialog that pops up over the Topology Builder allows us to either get information about an existing topology from the ‘Central Management Store’, load a file that contains previously exported topology information or create a completely new topology.

Select the radio button next to ‘New Topology’ and then click the ‘Ok’ button as shown below

You will be presented with the following ‘Save As’ dialog.

 

Create a new folder off the root of the C drive called ‘Lync Server Topology’ as shown below

Move to the new ‘Lync Server Topology’ folder and set the name of the file to be ‘MdcLyncServer2010StandardTopology’ as shown below

 

Click the ‘Save’ button to move to the following screen

This is simply our domain name so enter ‘mdc.com’ and click ‘Next’ as shown below

This screen gives us the opportunity to add additional domains, since we only have one simply click the ‘Next’ button as shown below

The following screen is shown next

Every Lync Server 2010 deployment must have at least one site. In our case we a 4 physical sites, Minneapolis, Dallas, San Diego and Toronto, but for now let’s just start off with Minneapolis. Enter ‘Minneapolis’ as the name and ‘Mdc Minneapolis Office’ as the description and then click ‘Next’ as shown below

Just a clarification here, the Lync sites that we are setting up are completely separate from anything we setup in Active Directory. We just use the same name for convenience.

The following is now displayed

Here we can enter some further information about the site we are creating. Fill in the details as shown below and the click ‘Next’

We are now shown the following

Make sure that there is a check mark in the box next to ‘Open the new Front End Wizard when this window closes’ and then click the ‘Finish’ button.

This launches the ‘Define New Front End Pool’ wizard as shown below

Click the ‘Next’ button and you will be shown the following screen

Enter ‘MdcLyncServer2010Standard.mdc.com’ as the Fully Qualified Domain Name (FQDN) and select the radio button next to ‘Standard Edition Server’ as shown below

Clicking ‘Next’ will bring you to the following screen

Since we will be setting up all of these features at some point, let’s select them all and the click the ‘Next’ button as shown below

The ‘Select collocated server roles’ screen is shown. Just simply accept the default values here and click the ‘Next’ button as shown below

Next the ‘Associate server roles with this Front End pool’ screen is displayed. Just leave all of these items unchecked and click the ‘Next’ button as shown below.

The resulting screen allows for entry of information about the SQL Server we will be using, however, everything is grayed out.

This is because the Standard Edition of Lync Server 2010 that we are installing will use SQL Server 2008 Express Edition. If we were installing the Enterprise Version of Lync Server 2010 we would have some options available on this screen.

Simply click on the ‘Next’ button to proceed as shown below

The resulting screen is shown below

What we are being asked for here is the name of a file share that will be used  for all of the useful shared resources like whiteboards, app sharing, temporary files etc etc, basically a spot where Lync Server 2010 can write files to.

The share needs to be manually created, so fire up Windows Explorer and create a folder off of the root of C called ‘LyncShare’ as shown below

Right click on the new C:\LyncShare folder and select ‘Properties’ as shown below

In the resulting ‘LyncShare Properties’ dialog, click on the ‘Sharing Tab’. Click on the ‘Share’ button as shown below

Select ‘Everyone’ from the drop down list and click the ‘Add’ button as shown below

Next, click on ‘Everyone’ in the list in the lower pane and change the permissions to ‘Read/Write’ as shown below

Finally, click the ‘Share’ button as shown below

You will be presented with the following. Click the ‘Done’ button to continue

Click the ‘Close’ button in the ‘LyncShare Properties’ dialog and then close Windows Explorer

Back at the ‘Define File Share’ screen we can now enter the name of of File Share and then click the ‘Next’ button as shown below

Just accept the default values in the ‘Specify the Web Service URL’ screen and click the ‘Next’ button as shown below

 

On the resulting ‘Specify PSTN Gateways’ screen just leave everything blank, as we will set all of this up at a later time.

 Click the ‘Finish’ button to continue as shown below

That completes the initial Topology definition.

We will be now shown the topology we just created in the Topology Builder as shown below

Next step is to create some easy to remember URLs for some common Lync features. Click on the ‘Edit Properties…’ link in the left hand pane as shown below

 

In the resulting dialog, click on ‘Simple URLs’ in the right hand pane

Notice that a couple of URLs have already been setup for us namely https://dialin.mdc.com which will be used for dial in conferencing and  https://meet.mdc.com which will be used for online meetings.

Enter ‘https://LyncAdmin.mdc.com’ for the Administrative Access URL’

At the very bottom of the screen under ‘Central Management Server’, select ‘MdcLyncServer2010Standard.mdc.com     Minneapolis’ from the drop down and the click the ‘Ok’ button as shown below

The final step is to publish the topology we have just created. Click on the ‘Lync Server’ node in the Topology Builder as shown below

In the right hand pane, click on the ‘Publish Topology…’ link as shown below

This results in the starting of the ‘Publish Topology’ wizard as shown below

Simply click ‘Next’ to be taken to the following screen

Our front end pool is automatically selected to host the ‘Central Management Store’, so click ‘Next’ to continue

You will be presented with the following

 

After a short time the process will complete.

This would be a good time to finish up Part 20.

Next time in Part 21, we will continue our Lync Server 2010 Installation.

 

Thanks for reading

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Exploring Lync Server 2010 - Part 19 - Installing Lync Server 2010 Standard Edition I

Welcome to Part 19 of Exploring Microsoft Lync Server 2010.

Well it has been quite a journey up to this point, and after 18 parts in this series we are finally ready to install Microsoft Lync Server 2010.

As I mentioned at the beginning, this is a huge product. We are going to start with installing the Standard Edition of Lync Server 2010. Hopefully this will allow us to get our feet wet with installing and configuring the product before we introduce new complexities that come with installing and configuring the Enterprise Edition.

So finally…let’s get started

Let’s begin by restarting the MdcDc Base Machine. After the machine has restarted, go ahead and login, and you will be presented with the ‘Server Manager’. Navigate to the “MDCBASE01”node under HyperV as shown below.

If it is not started, right click on the MdcLyncServer2010Standard Virtual Machine and select ‘Start’ from the drop down menu. Next, right click on the MdcLyncServer2010Standard Virtual Machine a second time and select ‘Connect’ from the menu as shown below.

This will open up a window into the MdcLyncServer2010Standard Virtual Machine.

Once the window into the MdcLyncServer2010Standard Virtual Machine opens, enter CTRL-ALT-END and go ahead and login. You should be logging into the mdc.com domain and not the local machine, so use the domain Administrator account and password.

After logging in to MdcLyncServer2010Standard Virtual Machine, you should be presented with the ‘Server Manager’ screen, which you can simply close because we do not need it at this point.

We need to insert the Microsoft Lync Server 2010 Standard Edition media into the MdcLyncServer2010Standard Virtual Machine, which can be done in one of 2 ways.

If you have the physical DVD for Microsoft Lync Server 2010 Standard Edition

Insert the DVD into the DVD player on the MdcBase01 physical machine.

Select ‘Media->DVD Drive->Capture D:’ from the menu on the window into MdcLyncServer2010Standard Virtual Machine as shown below

If you have an iso file for Microsoft Lync Server 2010 Standard Edition

Select ‘Media->DVD Drive->Insert Disk’ from the menu on the window into MdcLyncServer2010Standard Virtual Machine as shown below

Navigate to the location of your iso file and select it as shown below

At this point, if you want to have the MdcLyncServer2010Standard Virtual Machine go full screen instead of looking at it through a window you can type CTRL-ALT-BREAK.

You should be presented with the following

 

Click on ‘Run Setup.exe’ and right away we are shown this

 

Obviously we need the Microsoft .NET Framework 3.5 SP1 installed before we can continue

So let’s fire up ‘Server Manager’ and click on ‘Features’ as shown below

In the right hand pane, click on ‘Add Features’ as shown below

 

You will be presented with the ‘Add Features Wizard’ as shown below

 

The first item listed is ‘.NET Framework 3.5.1 Features’. Put a check mark next to this item, and the following will be displayed

This informs us that many other items need to be installed before the .NET Framework 3.5 can be installed. Simply click on the ‘Add Required Role Services’ button and these items will also be installed

Once back at the ‘Add Features Wizard’ click ‘Next’ as shown below

Since IIS is now part of this phase of the installation, we are presented with a little info about IIS. Simply click ‘Next’ to continue as shown below

Next we can see that the necessary IIS components that need to be installed have been checked as shown below

Click ‘Next’ and you will be taken to the following ‘Summary’

Click the ‘Install’ to start the process. During the installation you will see the following

Once completed you will be presented with the following

 

Click on the ‘Close’ but to complete the installation wizard

Now that we have taken care of the .NET Framework 3.5.1 and its associated dependencies, let’s start the Lync Server 2010 installation process again.

Close ‘Server Manager’ and then re-start the setup.exe program for Lync Server 2010.

You will be presented with the following

Click the ‘Yes’ button to install ‘Microsoft Visual C++ 2008 Redistributable’. There is no dialog that is presented during this process.

After a short period of time, the following is displayed

Accept the default location and then click on the ‘Install’ button as shown below

 

You will be presented with the License Dialog. Put a check mark in the box beside ‘I accept the terms in the license agreement’ and then click the ‘Ok’ button, as shown below

After a few short pop up dialogs, we will see the following screen

Now before Lync Server 2010 can be installed, some preparation must happen in Active Directory, meaning that the Active Directory schema must be extended to support Lync Server 2010. During this process, new classes and attributes will be added to Active Directory.

Click on the ‘Prepare Active Directory’ link as shown below

We are taken to the following which contains a rather abrupt error message as shown below

Well this was a little unexpected, but judging by the error message, it looks like we need to add ‘Active Directory Administrative Tools’.

So let’s click on the ‘Back’ button which should take us back to the following screen

 

Open ‘Server Manager’ select ‘Features’ in the left hand pane and then click ‘Add Features’ in the right hand pane as shown below

This will present us with the ‘Add Features Wizard’ as shown below

Scroll down in the list to ‘Remote Server Administration Tools’ and the open the following folders

·         Role Administration Tools

·         AD DS and AD LDS Tools

·         AD DS Tools

Put a check mark in front of ‘AD DS Snap-Ins and Command-Line Tools’ and then click ‘Next’ as shown below

On the resulting ‘Confirmation’ page, click the ‘Install’ button as shown below

You will get the following as the installation process runs

 

After completion you will be presented with the following

Click the ‘Close’ button to complete the process, and then close ‘Server Manager’

We should be able to continue with our Lync Server 2010 installation now. We left off with the following

Clicking on ‘Prepare Active Directory’ link will take us back to the following screen

As you can see the error message is now gone and we can go ahead and prepare the schema by clicking on the ‘Run’ button as shown below

After a few seconds, we are presented with the following

Click the ‘Next’ button and the following appears

This process does not take very long and shortly you will be shown the following

So it looks like this step has successfully completed. Click the ‘Finish’ button to return to following

As you can see, the green check mark gives us an indication that the ‘Preparing the Schema’ step has completed successfully.

I should mention here that after each step is completed you can exit the installation process. The next time you run setup.exe it will simply pick up where it left off.

Next step is to ‘Prepare the Active Directory Forest’

Click on the ‘Run’ button next to ‘step 3: Prepare the Active Directory Forest’ as shown below

You will be presented with the following

Clicking the ‘Next’ button shows the following screen

Accept the default ‘Local Domain’ selection and then click the ‘Next’ button as shown below

This is a very short process and when completed you will be presented with the following screen

Clicking the ‘Finish’ button takes us back to the Lync Server 2010 Deployment Wizard. Notice that the green check mark gives us an indication that the ‘Prepare the Active Directory Forest’ step has completed successfully.

Next we need to ‘Prepare the Active Directory Domain’

This step needs to be run for every domain where we plan to deploy Lync Server 2010. In our case we only have one domain so we only need to run his once.

Click on the ‘Run’ button next to ‘Step 5: Prepare Current Domain’ as shown below

You will be shown the following

Clicking the ‘Next’ button shows the following screen

This is a very short process and when completed, clicking the ‘Finish’ button takes will take us back to the Lync Server 2010 Deployment Wizard.

Notice that the green check mark gives us an indication that the ‘Prepare the Active Directory Domain’ step has completed successfully.

That completes the Active Directory preparations, so click the ‘Exit’ button as shown below

Quite obviously, many changes have taken place throughout the above processes. To see what has happened, have a look at the following link.

http://technet.microsoft.com/en-us/library/gg398379.aspx

This would be a good spot to wrap up Part 19. Next time in Part 20, we will continue our Lync Server 2010 Standard Edition Installation.

 

Thanks for reading

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Exploring Lync Server 2010 - Part 18 - Creating the Lync Server 2010 - Standard Edition Virtual Machine

Welcome to Part 18 of Exploring Microsoft Lync Server 2010.

In this part of the series, we will be creating a new Virtual Machine that will be used for Microsoft Lync Server 2010 Standard Edition.

But before we begin, let’s setup a server for this machine in Active Directory

On the MDCBASE01 machine, fire up Server Manager and connect to the MdcDc Virtual Machine as shown below

Start Server Manager on MdcDc and then navigate down to Minneapolis\Server Room in our Active Directory structure as shown below

Right click on ‘Server Room’ and select New->Computer as shown below

In the resulting dialog, enter ‘MdcLyncServer2010Standard’ as the computer name and click the ‘Ok’ button as shown below

As you can see from the image below, we now have our soon to be created ‘MdcLyncServer2010Standard’ machine setup in the ‘Server Room’ OU

Now let’s start building that new ‘MdcLyncServer2010Standard’ Virtual Machine that will be used for our Lync Server 2010 Standard Edition installation.

All of the following work should be performed on our base machine which is called MDCBASE01.

First off, fire up Windows Explorer and create a new folder under “C:\Virtual Machines\Production” called “MDC Lync Server 2010 Standard” as shown below

Next, start “Server Manager” and navigate to the “MDCBASE01” node under HyperV as shown below

Right click on the “MDCBASE01” node and select ‘New’ and then ‘Virtual Machine’ from the drop down menus as illustrated below

This will start the ‘New Virtual Machine Wizard’ as shown below

Click ‘Next’ and set the name of the Virtual Machine to be “MdcLyncServer2010Standard” and set the path to point to our recently created folder “C:\Virtual Machines\Production\Mdc Lync Server 2010 Standard” as shown below

Click ‘Next’ and on this screen, set the memory to 1024MB as shown below

Click ‘Next’ and select ‘MdcBase01VirtualNetwork’ from the Connection drop down so that our Virtual Machine will be connected to our network, as shown below

 

Click ‘Next’. On this screen, you want to select the ‘Attach a Virtual Hard Disk later’ radio button as shown below. We will be attaching the hard disk shortly.

 

Click ‘Next’ and you will be presented with the following summary screen.

Click ‘Finish’ and the new Virtual Machine will be created.  The next thing we want to do is to attach a hard drive to this newly created Virtual Machine. Using Windows Explorer, copy the SYSPREP’d hard drive located at

C:\Virtual Machines\Sysprepd Virtual Hard Drives\Windows Server 2008 R2\WindowsServer2008R2_SysPrepd.vhd’

to the folder located at

C:\Virtual Machines\Production\Mdc Lync Server 2010 Standard\MdcLyncServer2010Standard  

as shown below

 

Next, rename the copied hard drive to “WindowsServer2008R2_MdcLyncServer2010Standard.vhd” as shown below

 

Now that the hard drive is in the proper location, we can turn our attention to attaching it to the MdcLyncServer2010Standard Virtual Machine. In Server Manager, right click on the MdcLyncServer2010Standard Virtual Machine and select ‘Settings’ from the popup menu as shown below

In the settings dialog, select ‘IDE Controller 0’ from the left hand column and then select ‘Hard Drive’ in the right hand pane as shown below

Clicking the ‘Add’ button produces the following screen

Click on the ‘Browse’ button and select the hard drive located at

C:\Virtual Machines\Production\Mdc Lync Server 2010 Standard\MdcLyncServer2010Standard \ WindowsServer2008R2_MdcLyncServer2010Standard.vhd

 as shown below

Click ‘Ok’ and the proper hard drive will now be part of the MdcLyncServer2010Standard Virtual Machine.

Now that the Virtual Machine is complete, it is time to start it up.  Since the MdcLyncServer2010Standard Virtual Machine was created from our Master Virtual Machine image, we can expect to go through a Miniature Setup Routine as this is the first time that it will be started.

Using Server Manager, right click on ‘MdcLyncServer2010Standard’ Virtual Machine and select ‘Start’ from the popup menu as shown below

Right click on ‘MdcLyncServer2010Standard’ Virtual Machine a second time, and select ‘Connect’ from the popup menu to open a window into the Virtual Machine as shown below

You can move to full screen mode by entering CTRL_ALT_BREAK

You will see the following screen shots as the MdcLyncServer2010Standard Virtual Machine starts up

Once the MdcLyncServer2010Standard Virtual Machine reboots you will be presented with the following screen

 

Leave the default values as is, click ‘Next’ and you will be presented with the following

Click ‘Start’ and you will be presented with the following screen

 

Click Ok to change the password. The password that will be changed is the local Administrator password.

The requirements for a highly secure password were removed when we created our Mater Virtual Machine, and are therefore still removed in MdcLyncServer2010Standard.

So change the password to something simple and then click the blue arrow. The password will be updated and you will be shown the following screen

Click the ‘Ok’ button and you will be presented with the following

This ‘Initial Configuration Tasks’ screen should look familiar to you as we saw it earlier when we first setup our Base Machine.

If it does not show up, click on the Start button, select run, type in oobe.exe and click the Ok button. The Initial Configuration screen should now be visible.

Now there are a couple of items that we need to configure at this point before we can call our MdcLyncServer2010Standard Virtual Machine configured, the first of which is to configure networking

Click on ‘Configure Networking’ as shown below

You will now be taken to the ‘Network Connections’ screen. Right click on the icon which represents our connection to the Virtual Network and select ‘Properties’ from the popup menu as shown below

You will be presented with the ‘Local Area Connection Properties’ dialog. Highlight ‘Internet Protocol  Version 4 (TCP/IPv4)’ by clicking on it and then click the ’Properties’ button as shown below.

 

At this point you will be shown the ‘Internet Protocol Version 4 (TCP/IPv4)’ dialog as shown below.

Now back in Part 5 of this series, I presented a table that contained the ranges of IP Addresses that we would be using for the various machines in our infrastructure. I have again shown this table below

Start Range

End Range

Device

192.168.20.20

-

Router

192.168.20.50

192.168.20.99

Network Printers

192.168.20.100

192.168.20.199

Base Machines

192.168.20.200

192.168.20.255

Hyper V Virtual Machines

 

Previously we setup MdcDc Virtual Machine and assigned it an IP Address of 192.168.20.200, and then we setup MdcExchangeServer and assigned it an IP Address of 192.168.20.201.

Since MdcLyncServer2010Standard is a virtual machine and since it is the third virtual machine we have setup, let’s go ahead and use 192.168.20.202 as our IP Address.  

This network configuration step should be familiar to you as we have performed it previously when setting up our Base machine. 

Also, since we are now running a DNS Server, we can use the IP Address of our DNS Server for this network setup. The IP Address that we will be using is 192.168.20.200 which is the box where our DNS Server is running

Fill in the values as shown below and then click the ‘Ok’ button.

You will be taken back to the ‘Local Area Connection Properties’ dialog. Click the ’Close’ button as shown below.

You can now close the ‘Network Connections’ window that is shown below

Next we need to change the name of the virtual machine. You can do this my clicking on the ‘Provide computer name and domain’ link in the ‘Initial Configuration Tasks’ window as shown below

 

In the ‘System Properties’ window, click the ‘Change’ button and change the name of the computer to ‘MdcLyncServer2010Standard’. Next, change the’ Member of’ setting to ‘Domain’ and enter ‘mdc.com’ as the domain name, as shown below

Go ahead and click the ‘Ok’ button and you will be presented with the following.

What is happening here is that we are being asked for an account that has sufficient rights to allow our MdcLyncServer2010Standard computer to join the mdc.com domain. We can use the ‘Administrator’ account for this, so simply enter ‘Administrator’ and the password as shown below

 

Click the ‘Ok’ button and you will be presented with the following dialog

 

After you click the ‘Ok’ button on the welcome dialog, you will be presented with the following

 

Click the ‘Ok’ button. Then click the ‘Close’ button for the ‘System Properties’ dialog as shown below

 

When prompted click the ‘Restart Now’ button

 

The MdcLyncServer2010Standard Virtual Machine will now reboot. Once it has restarted we are presented with the following screen

By default, it is showing us the local account as the account to login with as shown below.

Previously we setup this new machine in Active Directory so let’s go ahead and log into the mdc.com domain.

Click on the ‘Switch User’ button and then click on ‘Other User’ as shown below

Enter ‘MDC\Administrator’ as the account name and then enter the password for the MDC\Administrator account and click the blue arrow as shown below.

 

Once the computer restarts we will again be presented with the ‘Initial Configuration Tasks’ screen.

From this point on we will not be need the ‘Initial Configuration Tasks’ screen to be shown when we first start our Virtual Machine, so put a check mark in the ‘Do not show this window at logon’ checkbox at the bottom of the screen. Lastly click on the ‘Close’ button as shown below.

And that’s all there is to it. We now have our MdcLyncServer2010Standard Virtual Machine all setup.

Again we see that the time we invested earlier in setting up a base Virtual Machine that could be cloned has saved us an enormous amount of time.

So that wraps it up for Part 18.

Next time in Part 19, we will get busy installing Microsoft Lync Server 2010 Standard Edition onto the MdcLyncServer2010Standard Virtual Machine

 

Thanks for reading

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Exploring Lync Server 2010 - Part 17 - Configuring Microsoft Exchange Sever 2010

This is a place holder for the blog post on Configuring Exchange Server 2010 which will be complete in the near future

Click here for more information

Exploring Lync Server 2010 - Part 16 - Installing Microsoft Exchange Sever 2010

This is a place holder for the blog posting on Installing Exchange Server 2010, which will be completed in the neear future

Click here for further information

Exploring Lync Server 2010 - A bit of a change in plans

I was planning on writing the next 2 parts of Exploring Lync Server 2010 as follows...

  • Exploring Lync Server 2010 - Part 16 - Installing Exchange Server 2010
  • Exploring Lync Server 2010 - Part 17 - Configuring Exchange Server 2010

After Parts 16 and Part 17 were completed, we would be ready to move ahead with the installation of Microsoft Lync Server 2010.

However, in January of this year I took a position with a company called OneReach. We have created a web based communications tool which allows companies to setup and deploy Voice, SMS and Email campaigns. The voice end of the product was created with Speech Server 2007 and was my responsibility.

Now that the product has launched, we are looking to future development and I have now been assigned to setup and deploy Lync Server 2010, which of course is an absolutely perfect position to be in.

So in the past week or so, I have taken what I have learned in this series of blog posts and stormed ahead with installing Lync Server 2010 Standard Edition.

Now at this point, I dont have time to learn how to install and configure Exchange Server 2010, so I am going to put Part 16 and Part 17 on hold for a while and move ahead with the following

  • Exploring Lync Server 2010 - Part 18 - Creating the Lync Server 2010 - Standard Edition Virtual Machine
  • Exploring Lync Server 2010 - Part 19 - Installing Lync Server 2010 - Standard Edition I
  • Exploring Lync Server 2010 - Part 20 - Installing Lync Server 2010 - Standard Edition II
  • Exploring Lync Server 2010 - Part 21 - Installing Lync Server 2010 - Standard Edition III
  • Exploring Lync Server 2010 - Part 22 - Installing Lync Server 2010 - Standard Edition IV

I will get back to Part 16 and Part 17 at a later time. I will be putting up blog posts for them, there just wont be much content available

As far as Parts 18 - 22 go, I have them all completed as I have been documenting my progress as I go. So they should be comming out in rapid succession.

I should have Part 18 available shortly

 

Thanks for reading

 

 

Exploring Lync Server 2010 - Part 15 - Creating the Exchange Sever 2010 Virtual Machine

Welcome to Part 15 of Exploring Microsoft Lync Server 2010.

In this part of the series, we will be creating a new Virtual Machine that will be used for Microsoft Exchange Server 2010.

But before we begin, there is something we need to take care of in Active Directory. Previously back in Part 12 we added 400 Users and Computers into Active Directory. These Users and Computers represent the employees and their computers in our organization.

However we also need to setup the new server machines that we are creating in Active Directory. So let’s setup a new OU for the server machines and then add a new computer to the OU for the Exchange Server Virtual Machine we will be setting up.

 On the MDCBASE01 machine, fire up Server Manager and connect to the MdcDc Virtual Machine as shown below

Start Server Manager on MdcDc and then navigate down to Minneapolis in our Active Directory structure as shown below

Right click on ‘Minneapolis’ and select New->Organizational Unit for the drop downs as shown below

On the resulting dialog, enter ‘Server Room’ as the name of the OU and then click the ‘Ok’ button as shown below

The end result is that we now have a new OU called ‘Server Room’ where all of our servers will live as shown below

The new Virtual Machine we will be creating for Exchange Server 2010 will be called ‘MdcExchange’ so we may as well add it into Active Directory now

Right click on ‘Server Room’ and select New->Computer as shown below

In the resulting dialog, enter ‘MdcExchange’ as the computer name and click the ‘Ok’ button as shown below

As you can see from the image below, we now have our soon to be created ‘MdcExchange’ machine setup in the ‘Server Room’ OU

Now let’s start building that new ‘MdcExchange’ Virtual Machine that will be used for our Exchange Server 2010 installation.

All of the following work should be performed on our base machine which is called MDCBASE01.

First off, fire up Windows Explorer and create a new folder under “C:\Virtual Machines\Production” called “MDC Exchange Server” as shown below

Next, start “Server Manager” and navigate to the “MDCBASE01” node under HyperV as shown below

Right click on the “MDCBASE01” node and select ‘New’ and then ‘Virtual Machine’ from the drop down menus as illustrated below

This will start the ‘New Virtual Machine Wizard’ as shown below

Click ‘Next’ and set the name of the Virtual Machine to be “MdcExchangeServer” and set the path to point to our recently created folder “C:\Virtual Machines\Production\Mdc Exchange Server” as shown below

Click ‘Next’ and on this screen, set the memory to 1024MB as shown below

Click ‘Next’ and select ‘MdcBase01VirtualNetwork’ from the Connection drop down so that our Virtual Machine will be connected to our network, as shown below

Click ‘Next’. On this screen, you want to select the ‘Attach a Virtual Hard Disk later’ radio button as shown below. We will be attaching the hard disk shortly.

Click ‘Next’ and you will be presented with the following summary screen.

Click ‘Finish’ and the new Virtual Machine will be created.  The next thing we want to do is to attach a hard drive to this newly created Virtual Machine. Using Windows Explorer, copy the SYSPREP’d hard drive located at

C:\Virtual Machines\Sysprepd Virtual Hard Drives\Windows Server 2008 R2\WindowsServer2008R2_SysPrepd.vhd’

to the folder located at C:\Virtual Machines\Production\Mdc Exchange Server\MdcExchangeServer  as shown below

Next, rename the copied hard drive to “WindowsServer2008R2_MdcExchangeServer.vhd” as shown below

Now that the hard drive is in the proper location, we can turn our attention to attaching it to the MdcExchangeServer Virtual Machine. In Server Manager, right click on the MdcExchangeServer Virtual Machine and select ‘Settings’ from the popup menu as shown below

In the settings dialog, select ‘IDE Controller 0’ from the left hand column and then select ‘Hard Drive’ in the right hand pane as shown below

Clicking the ‘Add’ button produces the following screen

Click on the ‘Browse’ button and select the hard drive located at

C:\Virtual Machines\Production\Mdc Exchange Server\MdcExchangeServer\ WindowsServer2008R2_MdcExchangeServer.vhd

 as shown below

Click ‘Ok’ and the proper hard drive will now be part of the MdcExchangeServer Virtual Machine.

Now that the Virtual Machine is complete, it is time to start it up.  Since the MdcExchangeServer Virtual Machine was created from our Master Virtual Machine image, we can expect to go through a Miniature Setup Routine as this is the first time that it will be started.

Using Server Manager, right click on ‘MdcExchangeServer’ Virtual Machine and select ‘Start’ from the popup menu as shown below

 

Right click on ‘MdcExchangeServer’ Virtual Machine a second time, and select ‘Connect’ from the popup menu to open a window into the Virtual Machine as shown below

 

You can move to full screen mode by entering CTRL_ALT_BREAK

You will see the following screen shots as the MdcExchangeServer Virtual Machine starts up

Once the MdcExchangeServer Virtual Machine reboots you will be presented with the following screen

Leave the default values as is, click ‘Next’ and you will be presented with the following

Click ‘Start’ and you will be presented with the following screen

Click Ok to change the password. The requirements for a highly secure password were removed when we created our Mater Virtual Machine, and are therefore still removed in MdcExchangeServer. So change the password to something simple and then click the blue arrow as shown below

Once you click the Blue arrow, the password will be updated and you will be shown the following screen

 

Click the ‘Ok’ button and you will be presented with the following

This ‘Initial Configuration Tasks’ screen should look familiar to you as we saw it earlier when we first setup our Base Machine.

Now there are a couple of items that we need to configure at this point before we can call our MdcExchangeServer Virtual Machine configured, the first of which is to configure networking

Click on ‘Configure Networking’ as shown below

You will now be taken to the ‘Network Connections’ screen. Right click on the icon which represents our connection to the Virtual Network and select ‘Properties’ from the popup menu as shown below

You will be presented with the ‘Local Area Connection Properties’ dialog. Highlight ‘Internet Protocol  Version 4 (TCP/IPv4)’ by clicking on it and then click the ’Properties’ button as shown below.

At this point you will be shown the ‘Internet Protocol Version 4 (TCP/IPv4)’ dialog as shown below.

Now back in Part 5 of this series, I presented a table that contained the ranges of IP Addresses that we would be using for the various machines in our infrastructure. I have again shown this table below

Start Range

End Range

Device

192.168.20.20

-

Router

192.168.20.50

192.168.20.99

Network Printers

192.168.20.100

192.168.20.199

Base Machines

192.168.20.200

192.168.20.255

Hyper V Virtual Machines

 

Previously we setup MdcDc Virtual Machine and assigned it an IP Address of 192.168.20.200

Since MdcExchangeServer is a virtual machine and since it is the second virtual machine we have setup, let’s go ahead and use 192.168.20.201 as our IP Address.  

This network configuration step should be familiar to you as we have performed it previously when setting up our Base machine. 

Since we are now running a DNS Server, we can use the IP Address of our DNS Server for this network setup. The IP Address that we will be using is 192.168.20.200 which is the box where our DNS Server is running

Fill in the values as shown below and then click the ‘Ok’ button.

You will be taken back to the ‘Local Area Connection Properties’ dialog. Click the ’Close’ button as shown below.

You can now close the ‘Network Connections’ window that is shown below

Next we need to change the name of the virtual machine. You can do this my clicking on the ‘Provide computer name and domain’ link in the ‘Initial Configuration Tasks’ windows as shown below

 

In the ‘System Properties’ window, click the ‘Change’ button and change the name of the computer to ‘MdcExchange’. Next, change the’ Member of’ setting to ‘Domain’ and enter ‘mdc.com’ as the domain name, as shown below

Go ahead and click the ‘Ok’ button and you will be presented with the following.

What is happening here is that we are being asked for an account that has sufficient rights to allow our MdcExchangeServer computer to join the mdc.com domain. We can use the ‘Administrator’ account for this, so simply enter ‘Administrator’ and the password as shown below

 

Click the ‘Ok’ button and you will be presented with the following dialog

 

After you click the ‘Ok’ button on the welcome dialog, you will be presented with the following

 

Click the ‘Ok’ button. Then click the ‘Close’ button for the ‘System Properties’ dialog as shown below

When prompted click the ‘Restart Now’ button

The MdcExchangeServer Virtual Machine will now reboot. Once it has restarted we are presented with the following screen

By default, it is showing us the local account as the account to login with as shown below.

Previously we setup this new machine in Active Directory so let’s go ahead and log into the mdc.com domain.

Click on the ‘Switch User’ button and then click on ‘Other User’ as shown below

Enter ‘MDC\Administrator’ as the account name and then enter the password for the MDC\Administrator account and click the blue arrow as shown below.

 

Once the computer restarts we will again be presented with the ‘Initial Configuration Tasks’ screen.

From this point on we will not be need the ‘Initial Configuration Tasks’ screen to be shown when we first start our Virtual Machine, so put a check mark in the ‘Do not show this window at logon’ checkbox at the bottom of the screen. Lastly click on the ‘Close’ button as shown below.

And that’s all there is to it. We now have our MdcExchangeServer Virtual Machine all setup.

Again we see that the time we invested earlier in setting up a base Virtual Machine that could be cloned has saved us an enormous amount of time.

So that wraps it up for Part 15. Next time in Part 16, we will get busy installing Microsoft Exchange Server 2010 onto the MdcExchangeServer Virtual Machine

 

Thanks for reading

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Exploring Lync Server 2010 - Part 14 - Creating a Windows 7 Client Virtual Machine and Connecting to mdc.com

Welcome to Part 14 of Exploring Microsoft Lync Server 2010.

In Part 14, we will be creating a Windows 7 Client Machine based on the Windows 7 Master Virtual Machine that we created in Part 13. After we have it created, we will connect it to the mdc.com domain that we have previously setup.

 So let’s get started

All of the following work should be performed on our base machine, MDCBASE01.

First off, fire up Windows Explorer and create a new folder under “C:\Virtual Machines\Production” called “Windows 7 Client 01” as shown below

Next, start “Server Manager” and navigate to the “MDCBASE01” node under HyperV as shown below

Right click on the “MDCBASE01” node and select ‘New’ and then ‘Virtual Machine’ from the drop down menus as illustrated below

This will start the ‘New Virtual Machine Wizard’ as shown below

Click ‘Next’ and set the name of the Virtual Machine to be “Windows 7 Client 01” and set the path to point to our recently created folder “C:\Virtual Machines\Production\ Windows 7 Client 01” as shown below

Click ‘Next’ and on this screen, set the memory to 1024MB as shown below

Click ‘Next’ and select ‘MdcBase01VirtualNetwork’ from the Connection drop down so that our Virtual Machine will be connected to our network, as shown below

Click ‘Next’. On this screen, you want to select the ‘Attach a Virtual Hard Disk later’ radio button as shown below. We will be attaching the hard disk shortly.

Click ‘Next’ and you will be presented with the following summary screen.

Click ‘Finish’ and the new Virtual Machine will be created.

The next thing we want to do is to attach a hard drive to this newly created Virtual Machine. Using Windows Explorer, copy the SYSPREP’d hard drive located at

C:\Virtual Machines\Sysprepd Virtual Hard Drives\Windows 7\Windows7_SysPrepd.vhd’

to the folder located at C:\Virtual Machines\Production\Windows 7 Client 01\Windows 7 Client 01

as shown below

Next, rename the copied hard drive to “Windows7_Client01.vhd” as shown below

Now that the hard drive is in the proper location, we can turn our attention to attaching it to the Windows 7 Client 01 Virtual Machine. In Server Manager, right click on the Windows 7 Client 01 Virtual Machine and select ‘Settings’ from the popup menu as shown below

In the settings dialog, select ‘IDE Controller 0’ from the left hand column and then select ‘Hard Drive’ in the right hand pane as shown below

Clicking the ‘Add’ button produces the following screen

Click on the ‘Browse’ button and select the hard drive located at

C:\Virtual Machines\Production\Windows 7 Client 01\Windows 7 Client 01\ Windows7_Client01.vhd

 as shown below

Click ‘Ok’ and the proper hard drive will now be part of Windows 7 Client 01 Virtual Machine.

Now that the Virtual Machine is complete, it is time to start it up. 

Since the Windows 7 Client 01 Virtual Machine was created from our Master Virtual Machine image, we can expect to go through a Miniature Setup Routine as this is the first time that it will be started.

Using Server Manager, right click on ‘Windows 7 Client 01’ Virtual Machine and select ‘Start’ from the popup menu as shown below

Right click on ‘Windows 7 Client 01’ Virtual Machine a second time, and select ‘Connect’ from the popup menu to open a window into the Virtual Machine as shown below

You can move to full screen mode by entering CTRL_ALT_BREAK

You will see the following screen shots as the Windows 7 Client 01 Virtual Machine starts up

Once the Windows 7 Client 01 Virtual Machine reboots you will be presented with the following screen

Just accept the default vales here and click ‘Next’. You will be presented with the following

Now at this point, we want to start using the Users and Computers that we had previously setup in Active Directory. For this first machine we will be using a machine from the Sales department in the Minneapolis office, and an employee who works in Sales at the Minneapolis facility.

So let’s chose ‘Albert Lindsay’ as the user and ‘MinSal01’ as the computer name. Enter those values in as shown below

We set the user name for Albert Lindsay to be ’alindsay’. This will setup a local user account on the Windows 7 Client 01 Virtual Machine for Albert, and it also matches the name we had previously setup for him in Active Directory.

Click ‘Next’ and you will be taken to the following screen.

On this screen you are asked to setup a password for Albert Lindsay to log into the Windows 7 Client 01 Virtual Machine. The password security on Windows 7 Client 01 Virtual Machine is relaxed so chose a simple password as shown below

When done, click the ‘Next’ button which will take you to a screen that asks for your Product Key. Enter your Product Key and then click ‘Next’.

On the resulting the licensing screen, place a check in the ‘I accept the licensing terms’ checkbox and then click ‘Next’ as shown below

On the next screen, click on ‘Use Recommended Settings’ and then click the ‘Next’ button as shown below.

You will be presented with the following screen

Verify that the time and time zone are correct and click ‘Next’. On the resulting  screen, click ‘Work Network’ as shown below

After a few seconds you will be presented with the following screen

And finally the following desktop

And that’s all there is to it. We now have our Windows 7 Client 01 Virtual Machine all setup.

Again we see that the time we invested earlier in setting up a base Virtual Machine that could be cloned has saved us an enormous amount of time.

I want to point out a couple of things here about this Windows 7 Client 01 Virtual Machine

Click on the ‘Start’ button and select ‘Control Panel’ as shown below

In the resulting Control Panel, click on ‘View Network Status and Tasks’ under the ‘Network and Internet’ section as shown below

As you can see from the image below, although we have not done any Network Configuration to this machine, everything looks good. The MinSal01 machine is connected to our Network which is connected to the Internet.

We want to have a look at the settings for the network adapter at this point, so click on ‘Change Adapter Settings’ link on the left hand side as shown below.

You will be presented with the following screen

Right click on the ‘Local Area Connection’ icon and select ‘Properties’ from the popup menu as shown below

You will be shown the ‘Local Area Connection Properties’ dialog. Select ‘Internet Protocol Version 4(TCP/IPv4) and then click on the ‘Properties’ button as shown below

You will be shown the following dialog

In this dialog for our other machines that we have previously setup, for example MdcDc, we used a static IP Address for the machine, and entered in hard coded values for all of the other entries.

In this case since this is a client machine, we do not need to worry about its IP Address and so it is dynamically assigned by the DHCP Server. More specifically, when the Windows 7 Client 01 Virtual Machine connects to the Network, it gets its IP Address from the DHCP Server that is located in the Router.

However, we will need to set the IP Address of our DNS Server which runs on the MdcDc box, which has an IP Address of 192.168.20.200.

Click on the ‘Use the following DNS Server address’ radio button and enter 192.168.20.200 as the IP Address for the ‘Preferred DNS Server’ as shown below

Click the ‘Ok’ button and then close up all of the dialogs that are open, so that we are back at the ‘Control Panel’. Next click on ‘System and Security’ as shown below

Click on the ‘Set the name of this computer’ link as shown below

On the screen that is displayed click on the ‘Change Settings’ link in the ‘Computer Name, domain and workgroup settings’ section as shown below

In the resulting ‘System Properties’ dialog, click on the ‘Network ID’ button as shown below

On the resulting screen, select the radio button that is associated with “This computer is part of a business network, I use it to connect with other computers at work”, as shown below.

Click the ‘Next’ button. and you will be presented with the following screen.

Select the radio button that is associated with “My company uses a network with a domain”. And then click the ‘Next’ button.

You will be presented with an instructional screen telling you the information you will need to join the domain as shown below.

Click the ‘Next’ button.

We need to enter in credentials here that have the necessary security settings to allow this machine to join the mdc.com domain.  Use the mdc.com ‘Administrator’ account here, and then click the ‘Ok’ button as shown below.

Click the ‘Next’ button and you will be presented with the following

What has happened is that a query has been made into Active Directory for the machine we are trying to connect which is ‘MinSal01’. Since we previously setup that computer in Active Directory (along with 399 other machines) we are asked if we want to use that computer that is already setup in AD

Click the ‘Yes’ button. The machine will think for a while and finally present the following

Now since we have already setup our users in Active Directory, we can chose the radio button associated with ‘Do not add a domain user account’ and then click the ‘Next’ button as shown below

You will be presented with the following screen

Go ahead and click the ‘Finish’ button.

Notice that in the ‘System Properties’ dialog, the machine name has been set to MinSal01.mdc.com and the domain has been set to mdc.com

Click the ‘Ok’ button on the ‘System Properties’ dialog as shown below

Click the ‘Restart Now’ button as shown below and the machine will reboot

After restarting we will eventually be shown this screen

Let’s now log this Windows 7 Client 01 Virtual Machine into the mdc.com domain and see how a few things are affected.

Enter ‘CTRL-ALT_END’ and the following will be shown

By default, the last user who logged onto this machine is shown, which in this case is the local user account is for Albert Lindsay which is called ‘MinSal01\alindsay’.

We want to log this machine into the mdc.com domain, so click on the ‘Switch User’ button and you will be shown the following screen

Click on the ‘Other User’ icon and you will be presented with the following

Enter ‘alindsay’ as the User name.

Since this is the first time we have logged into mdc.com with this account, and since all domain users that we have previously setup have an empty password, simply click on the ‘Blue Arrow’ to login. You will be presented with the following screen.

This screen shows up informing the user that since this is the first time that they have logged in, they must change their password.

As you know the domain password security levels for mdc.com have been relaxed so go ahead and click ‘Ok’ and then enter and confirm a new simple password and then click on the Blue Arrow as shown below

You will then be presented with the following screen

Click the ‘Ok’ button to be taken to the desktop.

This machine MinSal01 is now logged into the mdc.com domain.

Now let’s take a look at a couple of things that have happened in Active Directory and DNS Server now that the MinSal01 computer has logged in.

Go back to the MdcDc Virtual Machine, fire up Server Manager and have a look at the computers in Active Directory that are located at Minneapolis\Sales\Computers. We have ‘MinSal01’ logged in right now, but double click on ‘MinSal02’.

What you will see is the following

You’ll notice that there is nothing in ‘DNS Name’ on the ‘General’ tab and no entries at all show up on the ‘Operating System’ tab as shown above.

Now close that dialog and double click on ‘MinSal01’. You will be presented with the following

Notice that the DNS Name on the ‘General’ tab has been filled in as ‘MinSal01.mdc.com’ and under the ‘Operating System’ tab, Windows 7 Ultimate shows up as the operating system. This was all nicely filled in when MinSal01 logged into Active Directory for this first time.

Now open up DNS Sever and have a look at DNS\MDCDC\Forward Lookup Zones\mdc.com as shown below

Notice that MinSal01 shows up in the right hand pane with an IP Address of 192.168.20.117. This information was also added when MinSal01 logged into the mdc.com domain. Since this entry has been made in the DNS Server let’s see if the DNS Server can resolve the MinSal01 computer name.

Go back to the MinSal01 Virtual machine and open a ‘Command Prompt’ by clicking on the ‘Start’ button, ‘All Programs’, ‘Accessories’, ‘Command Prompt’ as shown below

Type in “nslookup MinSal01’ and hit enter. You should get a response as shown below

What has happened here is that the ‘nslookup’ utility that comes as part of Windows 7 has made a request to the DNS Server that runs on the MdcDc Virtual Machine to translate ‘MinSal01’ into its IP Address. The DNS Server has returned 192.168.20.117.

So that wraps up a rather lengthy Part 14 of Exploring Microsoft Lync Server 2010.

At some point in the future we may need more Windows 7 Client Machines to hook into our Lync Server 2010 machines, so we may be visiting this part of the series again.

Finally as a quick recap, we have now successfully setup Active Directory, DNS Server and connected a Windows 7 client machine to Active Directory. All of the machines are Hyper-V Virtual Machines running on our Virtual Network.

In Part 15, we will be creating another new Virtual Machine, this time it will be another Windows Server 2008 R2 machine, which will be used for installing Exchange Server 2010.

 

Thanks for reading

 

Exploring Lync Server 2010 - Part 13 - Creating a Windows 7 Master Virtual Machine

Welcome to Part 13 of Exploring Microsoft Lync Server 2010.

At the conclusion of Part 12 of Exploring Microsoft Lync Server 2010, we had completed the configuration for Active Directory and DNS Server. In Active Directory, we configured 400 Users and 400 Computers.

Once we get Microsoft Lync Server 2010 installed, we will need Client Machines to connect to it and test with, and although we won’t be creating 400 client machines, we will need a few.

So in this part of the series, we will be creating a new Windows 7 Master Virtual Machine that we will be using as the base for all of our virtual client machines.  The process of creating the Windows 7 Master Virtual Machine will be very similar the process we went through in Part 8 when we created the Windows Server 2008 R2 Master Virtual Machine.

So let’s get started

First of all, let’s reboot the machine and login. After logging in you should be presented with the ‘Server Manager’ screen as shown below.

Close the Server Manager, as we will not need it right now.

Using Windows Explorer, create a new folder below ‘C:\Virtual Machines’ called ‘Temp’, as shown below

After creating the new folder, close Windows Explorer and then click the ‘Server Manager’ button, next to the ‘Start Button’ to bring up the ‘Server Manager’ again.

In the left hand tree view in Server Manager, open the ‘Roles’ node, then open the ‘Hyper-V’ node, then click on ‘Hyper-V Manager’. A few seconds later the following screen will be shown

Right click on the ‘MdcBase01’ node and select ‘New’, ‘Virtual Machine’ from the menus as shown below

You will now be presented with the start dialog for the ‘New Virtual Machine Wizard’ as shown below

Clicking the ‘Next’ button takes you to the following screen

Let’s call this Virtual Machine that we are creating ‘Windows7_Temp’ and save it to ‘C:\Virtual Machines\Temp\’ as shown below.

Click the ‘Next’ button and on the resulting screen, adjust the memory to 1024 MB as shown below

Click ‘Next’ and select our Virtual Network, ‘MdcBase01VirtualNetwork’ from the drop down list as shown below

After clicking on the ‘Next’ button, we will be given the opportunity to setup the Virtual Hard Drive for this Virtual Machine. Assign ‘Windows7_Temp.vhd’ as the name of the Virtual Hard Drive, and then set its location to be ‘C:\Virtual Machines\Temp\Windows7_Temp\’. Make the size of the ‘Virtual Hard Drive’ equal to 500 GB as shown in the screen shot below.

Click the ‘Next button.

Setting the location where the operating system will be installed from is the next step. Select ‘Install an operating system from a boot CD/DVD-ROM’ and select ‘D:’ from the drop down in the ‘Physical CD/DVD drive’ section, as shown below.

Clicking the ‘Next’ button takes us to the Summary screen.

Click the ‘Finish’ button to create the Virtual Machine.

After the Virtual Machine has been created, the following screen will be shown. Notice that the newly created Virtual Machine is listed in the center pane.

We are now going to start the new Virtual Machine. Since there is no operating system installed on the new Virtual Machine, we will need to install Windows 7. Insert the Windows 7 DVD into Drive D on the physical machine, and then right click on the newly listed Virtual Machine and select ‘Start’ from the drop down menu as shown below.

Right click on the Virtual Machine a second time and select ‘Connect’ from the menu. This will open up a window into the Virtual Machine, as shown below.

The Windows 7 operating system will now install. You can change the default values on the first screen if you like, but for our purposes, we will be leaving them as is. Clicking ‘Next’ moves us to following screen

Click the ‘Install Now’ button to kick off the installation process as shown below

After a few moments you will be presented with the licensing screen. Place a check in the ‘I accept the licensing terms’ checkbox and then click ‘Next’ as shown below

You will be presented with the following screen.

 

Here we are given the optional of upgrading a previous version of Windows or installing a completely fresh copy.  For our situation we want to select  ‘Custom (advanced)’ so that we can install a completely new version of Windows 7

Clicking on ‘Custom (advanced)’ will take us to the following screen.

Here we are asked which partition we want to install Windows 7 onto. In this case since we only have one, we simply accept the default selection and click the ‘Next’ button.

The installation now takes over and shows the following status screen as it progresses along

As the installation process progresses, the machine will reboot a few times. Eventually you will be presented with the following screen.

At this point the name of the machine and user are not important, so simply enter a user name and leave the default value for the computer name and then click ‘Next’. On the resulting screen, you will be asked to enter in your Product Key. The next screen asks you to setup a password as shown below

 

Enter in your password and then click next. You will be presented with the following screen

Click on ‘Use Recommended Settings’ and then click the ‘Next’ button. You will be presented with the following

Select the appropriate time zone for your area from the drop down, check that the time is correct, and then click the ‘Next’ button. On the resulting  screen, click ‘Work Network’ as shown below

The installation process will now continue as shown below

Eventually you will be presented with the following desktop

Now it is time to perform the final steps in preparing this Windows 7 Master Virtual Machine for cloning with SYSPREP which can be found at C:\Windows\System32\Sysprep\Sysprep.exe.

Run SYSPREP.exe and you will be presented with the following screen

The System Cleanup Action drop down list contains the following two options;

  • Enter System Out of Box Experience (OOBE)
  • Enter System Audit Mode.

You must choose the “Enter System Out of Box Experience (OOBE)” option.

Next, you must select the Generalize check box. Otherwise, the system will not be stripped of its uniquely identifying attributes.

Finally, you must set the Shutdown Options to Shutdown. It is important that you select Shutdown and not Restart. If you use the Restart option, then the recently generalized system will reboot and enter into Windows mini-setup mode, effectively undoing your prep work.

Click the ‘Ok’ button and SYSPREP will begin. The whole process takes a couple of minutes and once completed, the Virtual Machine will shut down.

This Virtual Machine is now fully ready to be cloned.

Again, let’s review what has happened here

Since SYSPREP has now been run against the Windows 7 Master Virtual Machine, it will no longer be able to function properly because the SIDs and other types of attributes mentioned earlier have all been stripped away by SYSPREP.

However Windows 7 has preserved most of the deployment settings. Since it is missing a few things though, the next time that we boot the virtual machine or one of the clones that was made from it, Windows 7 runs something that I like to think of as a miniature Setup Wizard.

Although the miniature Setup Wizard behaves as though you are installing a completely fresh copy of Windows 7, most of the modifications that we have made to the Master Virtual Machine prior to running SYSPREP will be preserved.

Just a few more items do do now, the first one is copying the SYSPREP’d Windows 7 Master Virtual Machine

As you know our Master Virtual Machine currently lives at C:\Virtual Machines\Temp\Windows7_Temp and the name of the Master Virtual Machine Hard Drive file is Windows7_Temp.vhd as shown below.

The Hard Drive file ‘Windows7_Temp.vhd’ will now be used as the hard drive for any new Windows 7 Virtual Machines we create. Let’s copy and rename this hard drive file so that it can be used later on.

Let’s start off by creating a folder called “Windows 7 under the folder located at C:\Virtual Machines\Sysprepd Virtual Hard Drives” as shown below

Next copy the file C:\Virtual Machines\Temp\Windows7_Temp\Windows7_Temp.vhd’

to the folder located at 'C:\Virtual Machines\Sysprepd Virtual Hard Drives\Windows7'

as shown below

Rename the file ‘C:\Virtual Machines\Sysprepd Virtual Hard Drives\Windows7\Windows7_Temp.vhd’ to C:\Virtual Machines\Sysprepd Virtual Hard Drives\Windows7\Windows7_SysPrepd.vhd’ as shown in the following two screen shots

The Windows 7 Master Virtual Machine that we created is no longer needed at this point, so it is best that we delete it.  We will need to delete the Windows 7 Master Virtual Machine from HyperV and then we need to delete the actual files.

Using Server Manager, make sure that the Windows 7 Master Virtual Machine is turned off, and then delete it by clicking on the ‘Delete’ link as shown by the red arrow in the image below

Close Server Manager and start Windows Explorer

Next right click on the ‘C:\Virtual Machines\Temp\Windows7_Temp’ folder and delete it along with any folders/files located below it by selecting ‘Delete’ from the menu as shown below

What we now have is a file located at 'C:\Virtual Machines\Sysprepd Virtual Hard Drives\Windows7\Windows7_SysPrepd.vhd' which can be used as the basis for any Windows 7 HyperV Virtual Machines that we create from here on in.

That wraps up Part 13 of this series.

In Part 14, we will be creating our first Windows 7 Virtual Machine based on the image that we just created, and connecting it to the mdc.com domain.

 

Thanks for reading

 

 

Exploring Lync Server 2010 - Part 12 - Configuring Active Directory And DNS Server

Welcome to Part 12 of Exploring Microsoft Lync Server 2010

Now that we have the Active Directory and DNS Server installed on the MdcDc Virtual Machine, we need to do some configuration work. First off, let’s see what installing Active Directory and DNS Server has given us.

Let’s begin by restarting the MdcDc Base Machine. After the machine has restarted, go ahead and login, and you will be presented with the ‘Server Manager’. Navigate to the “MDCBASE01”node under HyperV as shown below.

Right click on the MdcDc Virtual Machine and select ‘Start’ from the drop down menu as shown below.

Right click on the MdcDc Virtual Machine a second time and select ‘Connect’ from the menu. This will open up a window into the MdcDc Virtual Machine.

Once the window into the MdcDc Virtual Machine opens, go ahead and login, by entering CTRL-ALT-END. If you want to have the Virtual Machine go full screen instead of looking at it through a window you can type CTRL-ALT-BREAK.

 After logging in to MdcDc Virtual Machine, you will be presented with its ‘Server Manager’ screen as shown below

Expand the ‘Roles’ node and you will notice that we now have two items listed, ‘Active Directory Domain Services’ and ‘DNS Server’ as shown below

So let’s take a couple of minutes and look at ‘DNS Server’

Open the ‘DNS Server’ node, the ‘DNS’ node, and the ‘MDCDC’ node and you will see the following

If you open up the ‘Global Logs’ folder, you can see all of the events that have recently happened in the DNS Server as shown below.

A DNS server provides Domain Name Resolution, either translating a Domain Name into an IP Address or returning a Domain Name based on an IP Address.

The ‘Forward Lookup Zone’ will hold entries that translate a Domain Name into an IP Address.

Opening the ‘Forward Lookup Zone’ folder will give you the following results.

We are specifically interested in the ‘mdc.com’ node. Open the ‘mdc.com’ node and you will be presented with the following screen

Notice that the last entry in the right hand pane shows mdc.com and its associated IP address 192.168.20.200. As more machines join the MDC domain, their Computer Names and IP Addresses will automatically be entered into the ‘Forward Lookup Zone’.

As a demonstration, let’s see how this all works by opening up a Command Window and typing in ‘nslookup mdc.com’ as shown below.

What you will see is the following

What has happened here is that the ‘nslookup’ utility that comes as part of Windows Server 2008 R2 has  made a request to the DNS Server to translate ‘mdc.com’ into its IP Address. The DNS Server has returned 192.168.20.200.

But how did ‘nslookup’ know to use the DNS Server that we just installed?

Well to find out, click on the ‘Start’ button, right click on ‘Network’ and select ‘Properties’ from the pop up menu as shown below

On the resulting screen, click on ‘Change Adapter Settings’ as shown below

On the resulting screen, right click on the ‘Local Area Connection’ icon and select ‘Properties’ from the pop up menu as shown below

The  ‘Local Area Connection Properties’ dialog will now be presented as shown below

Highlight ‘Internet Protocol Version 4 (TCP/IPv4)’ and then click on the ‘Properties’ button.  The ‘Internet Protocol Version 4  (TCP/IPv4) Properties’ dialog will now be shown

As you can see the ‘Prefered DNS Server’ and ‘Alternate DNS Server’ values that we initially entered in when configuring our Network Connection for this Virtual Machine have been changed. The ‘Primary DNS Server IP address is now set to 127.0.0.1 which is the IP Address of the local box, which is where the DNS Server is running

This explains why ‘nslookup’ went to our newly setup DNS Server to get the translation for mdc.com.

We will further explore this when we start hooking Client machines into the MDC Domain, but for now everything seems to be working fine.

So let’s turn our attention to ‘Active Directory’ and start setting things up…

As I mentioned back in Part 2 of this series, we are performing our setup for a fictitious company called MDC Inc, which is a national company whose head office is located in Minneapolis, Minnesota. Satellite offices are located in Dallas, Texas, San Diego, California and they also maintain a Canadian presence via an office in Toronto, Ontario.

The following employee breakdown applies to the offices

City

State

Country

# Employees

Minneapolis

Minnesota

USA

200

Dallas

Texas

USA

45

San Diego

California

USA

75

Toronto

Ontario

Canada

80

Total Employees

400

 

Our goal is to setup all 400 Users in Active Directory. Also, each employees has been assigned a computer so 400 computers will need to be setup in Active Directory as well.

First of all let’s discuss the organization of MDC Inc in a little more detail. Each office in the company has a variety of Departments that employees belong to, which is summarized in the following chart

 

City

State

Country

Department

Item

# of Employees

Minneapolis

Minnesota

USA

Maintenance

Computers

10

 

 

 

 

Users

10

 

 

 

Marketing

Computers

35

 

 

 

 

Users

35

 

 

 

Sales

Computers

40

 

 

 

 

Users

40

 

 

 

Support

Computers

90

 

 

 

 

Users

90

 

 

 

Technology

Computers

25

 

 

 

 

Users

25

Dallas

Texas

USA

Sales

Computers

15

 

 

 

 

Users

15

 

 

 

Support

Computers

30

 

 

 

 

Users

30

San Diego

California

USA

Sales

Computers

30

 

 

 

 

Users

30

 

 

 

Support

Computers

45

 

 

 

 

Users

45

Toronto

Ontario

Canada

Sales

Computers

20

 

 

 

 

Users

20

 

 

 

Support

Computers

60

 

 

 

 

Users

60

 

In Server Manager, expand the ‘Roles’, ‘Active Directory Domain Services’, ‘Active Directory Users and Computers’ and ‘mdc.com’ nodes as shown below

You will notice that there is a folder for ‘Users’ and a folder for ‘Computers’.

We could add our users and computers into these two folders, but a much more efficient process would be to setup new ‘Organizational Units’ in Active Directory for each Office Location/Department.

An organizational unit (OU) is a subdivision within an Active Directory into which we can place users, groups, computers, and other organizational units. We will create organizational units to mirror the organization's business structure.

Perhaps, the best way to describe this is to simply get busy setting up the OU’s

To setup our first OU, right click on ‘mdc.com and select ‘New’ then ‘Organizational Unit’ from the popup menu as shown below

The ‘New Organizational Unit’ dialog is displayed. Enter ‘Minneapolis’ for the name as shown below

Click the ‘Ok’ button. Notice that our ‘Minneapolis’ OU is now part of our Active Directory structure as shown below

Go ahead and create OUs for ‘Dallas’, ‘San Diego’ and Toronto’ using the above procedure. When completed your Active Directory structure should look like this

Now that we have an OU for each geographic location, let’s setup OU’s for the departments. Right click on the Minneapolis OU and create an OU called ‘Maintenance’ as shown below

Next, create Marketing, Sales, Support and Technology OU’s under Minneapolis. When you have completed, things should look like this

To finish off the Department setup, create ‘Sales’ and ‘Support’ OUs under the ‘Dallas’ OU, the ‘San Diego’ OU and the ‘Toronto’ OU. When you are done you’re the Active Directory structure should look like the following

Now the last OUs to setup will be a ‘Computers’ OU and a ‘Users’ OU under each department. Go ahead and setup these final OUs, when you are finished the final Active Directory structure will look like the following

The last thing we need to do is to setup all 400 Computers and 400 Users in the OUs we just created. Now this would obviously be a long and boring process; luckily we will be automating the process.

There is a little utility that comes with Active Directory that allows for bulk importing of data. The utility is called CSVDE and can be found at C:\Windows\System32\csvde.exe.

Basically what you do is create a CSV file that holds all of the data you want to import into Active Directory and use that file as an input to CSVDE.

The CSV file must meet some strict layout guidelines. If you would like to dig into how the file is structured, you can do some online research, but to speed up the process, I have created CSV files that will import all 400 Users and 400 Computers into the proper OUs that we have setup.

These CSV files along with a couple of batch files to launch the import process can be found here...

http://gotspeech.net/files/folders/exploring_lync_server_2010_-_part_12/default.aspx 

I should mention here that if you have a problem running these scripts, you may want to double check the names of the OUs that you just created. In order for the import to succeed, the names of the OUs have to be exactly the same as what I laid out earlier, so be careful of spelling mistakes.

So let’s run through the process of loading in our User and Computers.

Make a folder off the root of the C drive called ‘CSV Import Files’ as shown below

Download the files to the ’C:\CSV Import Files’ folder. When complete you should have the following files available…

  • Computers.csv
  • Users.csv
  • ImportComputers.bat
  • importUsers.bat

To import the Computers, double click on the ImportComputers.bat file. You will be presented with the following

Once the import has completed, check a few of the Computer OUs to see that the computers have been successfully imported. You should see the following under Minneapolis, Sales, Computers

All of the computer names follow the same basic pattern, first 3 letters of the location, first 3 letter of the department, followed by a running number. For example MinSal03 would be the third computer in the Sales department of the Minneapolis office.

The next thing we need to do is to import out 400 Users into Active Directory….but we have a bit of a problem here.

It is not possible to import passwords for users using CSVDE, and since by default our domain requires a password for each new user, trying to import using our script will fail

What we need to do is relax the password requirements on our domain, run our import routine for the users and then reestablish the password requirements for the domain security.

In order to relax the password requirements for the domain, in Server Manager, open the ‘Features’, ‘Group Policy Management’, ‘Forest:mdc.com’, ‘Domain’, and ’ mdc.com’ nodes as shown below

Click on ‘Default Domain Policy’ and you will be shown the following screen

As you can see by the red arrow, ‘Password must meet complexity requirements’ is enabled. To disable this feature, right click on ‘Default Domain Policy’ and select ‘Edit’ from the popup as shown below.

What you will get is a new window called ‘Group Policy Management Editor’ as shown below

Under ‘Computer Configuration’ open the ‘Policies’, ‘Windows Settings’, ‘Security Settings’, ‘Account Policies’, ‘and ‘Password Policy’ nodes, as shown below

In the right hand pane, double click on ‘Password must meet complexity requirements’ and you will be presented with the following dialog

Click the ‘Disabled’ radio button as shown below

Click the ‘Ok’ button to close the dialog.

In the right hand pane, double click on ‘Minimum Password Length’ and you will be presented with the following dialog

Change the length to 0 characters as shown below

Click the ‘Ok’ button, and then close the ‘Group Policy Management Editor.

The machine must be restarted at this point for the new relaxed password settings to become active, so let’s go ahead and reboot the machine at this point.

Once the machine has restarted, the password security will be relaxed which will allow us to import our contacts.

Using Windows Explorer, go back to the folder located at C:\CSV Import Files as shown below

Double click on the ImportUsers.bat file. You will be presented with the following screen

After the import completes, you should be able to see all of the Users in Active Directory. For example the following screen shows the Users at the Minneapolis office in the Sales department.

Due to the way the CSV import file was setup, each user will be required to change their password the first time they log into the mdc.com domain.

Now that we have completed importing the users and computers, we can go ahead and delete the files and the folder located at ’C:\CSV Import Files’.

Finally, let’s re-establish the security for our Domain Passwords.

In Server Manager, open the ‘Features’, ‘Group Policy Management’, ‘Forest:mdc.com’, ‘Domain’, and ’ mdc.com’ nodes as shown below

Click on ‘Default Domain Policy’ and you will be shown the following screen

Right click on ‘Default Domain Policy’ and select ‘Edit’ from the popup as shown below.

What you will get is a new window called ‘Group Policy Management Editor’ as shown below

Under ‘Computer Configuration’ open the ‘Policies’, ‘Windows Settings’, ‘Security Settings’, ‘Account Policies’, ‘and ‘Password Policies’ nodes. As shown below

In the right hand pane, double click on ‘Minimum Password Length’ and you will be presented with the following dialog

Originally this was set to 7 characters, which seems a bit long for our needs, lets change the length to 5 characters as shown below

Click the ‘Ok’ button

In the right hand pane, double click on ‘Password must meet complexity requirements’ and you will be presented with the following dialog

Click the ‘Enabled’ radio button as shown below

Click the ‘Ok’ button, and then close the ‘Group Policy Management Editor.

The machine must be restarted at this point for the new tightened password settings to become active. Once the machine has restarted, the password security for the domain will be back to its original tightened state.

We have now successfully setup 400 Users and 400 Computers in Active Directory.

Well that wraps things up for Part 12.

In the next part of this series, we will step back a bit and create a Virtual Machine, based on Windows 7 that we clone and use for each of our client machines, and see what happens when we connect a client machine to our MDC.com domain.

Thanks for reading

 

 

Exploring Lync Server 2010 - Part 11 - Installing Active Directory

Welcome to Part 11 of Exploring Microsoft Lync Server 2010

Now that we have the MdcDc Virtual Machine setup, we are going to install the ‘Active Directory Domain Services’ role onto it. The following three items will be installed during this process

·         Active Directory Domain Services

·         DNS Server

·         Active Directory Certificate Services

Active Directory Domain Services and DNS Server form the foundation of a Windows Server network and as such are huge topics which are far too complex to discuss in detail in this series. What’s presented here are some basic installation details in order to get these two items up and running.

If you wish to explore Active Directory Domain Services and DNS Server more deeply, please utilize one of the many books available on the subjects, or many tutorials that are available on the Internet.

Let’s begin by restarting the MdcDc Base Machine. After the machine has restarted, go ahead and login, which will result in being presented with the ‘Server Manager’.  Navigate to the “MDCBASE01” node under HyperV as shown below

Right click on the MdcDc Virtual Machine and select ‘Start’ from the drop down menu as shown below.

Right click on the MdcDc Virtual Machine a second time and select ‘Connect’ from the menu. This will open up a window into the MdcDc Virtual Machine.

 Once the window into the MdcDc Virtual Machine opens, go ahead and login.

I should mention here that the process for logging in to a Virtual Machine is a little different than a regular machine. If you enter CTRL-ALT-DELETE, those keystrokes will be invoked on the base machine. To log in to the Virtual Machine you need to type in CTRL-ALT-END.

Also, if you want to have the Virtual Machine go full screen instead of looking at it through a window you can type CTRL-ALT-BREAK.

After logging in to MdcDc Virtual Machine, you should be presented with the ‘Server Manager’ screen. Right click on the ‘Roles’ node in the MdcDc Server Manger and select ‘Add Roles’ from the menu as shown below.

Clicking on the ‘Add Roles’ link will start the ‘Add Roles Wizard’ and present the following introductory screen

Click the ‘Next’ button and you will be presented with the ‘Select Server Roles’ page. Put a check mark in the checkbox to the left of ‘Active Directory Domain Service’ as show below.

As soon as you put a check mark in the checkbox to the left of ‘Active Directory Domain Service’, a small dialog will popup informing you that Active Directory cannot be installed unless the .NET Framework 3.5.1 is installed as shown below

Simply click on the ‘Add Required Features’ button and installation of the .NET Framework 3.5.1 will be become part of the Active Directory Installation process.

Click the ‘Next’ button on the ‘Select Server Roles’ page

The following screen is presented and contains some introductory information about Active Directory

Simply click the ‘Next’ button to be taken to the summary screen as shown below

Click the ‘Finish’ button to get the installation process under way. The following status screen will be shown during the installation.

Once completed the following ‘Installation Results’ screen will be displayed.

Do not click the ‘Close’ button on this screen at this point

The Active Directory Domain Services role is now installed.

The next step is to make MdcDc a fully functional domain controller. If you have a look at the ‘Installation Results’ screen above, there is a link that says ‘Close this wizard and launch the Active Directory Domain Services Installation Wizard (dcpromo.exe)’. Click on this link to launch the process that will turn MdcDc into a domain controller.

The ‘Active Directory Domain Services Installation Wizard’ begins with the following page

Click on the ‘Next’ button to be taken to the following information page in the wizard. This page outlines some security enhancements in Windows Server 2008 R2

Simply click ‘Next’ to be taken to the next page in the wizard as shown below

Since this is a new installation, click on the ‘Create a new domain in a new forest’ radio button and the click the ‘Next’ button to be taken to the following page.

Here we are going to enter the fully qualified domain name of the new forest root domain. For our purposes we will be entering mdc.com. After entering the fully qualified domain name, click the ‘Next’ button to move to the page shown below.

The installation procedure makes some checks at this point and shortly the following page will appear.

The selection that you make here depends on what other servers are installed on the network. Since this is a new installation and since all of the servers will be setting up on this network with be Windows Server 200 R2, we simply select Windows Server 2008 R2 from the drop down list and then click the ‘Next’ button.

The installation process makes a few more checks as shown below

Shortly, the following wizard page is displayed

A Domain Name Server is the next necessary component to be installed. Make sure the ‘DNS Server’ checkbox has a check mark in it and then click on the ‘Next’ button. The following page will be displayed.

Simply accept the default values here by clicking the ‘Next’ button.

Here we are asked to select a password for the ‘Directory Services Restore Mode Administrator Account’. This will be only used for Restore Mode in case something goes wrong.

After selecting a password, click on the ‘Next’ button to be taken to the summary page as shown below

Click the ‘Next’ button and the installation process will present the following page and continue for a few minutes.

Put a check mark next to ‘Reboot on completion’ so that the computer will restart once everything has completed.

After the computer has rebooted, the last thing we need to take care of is the installation of ‘Active Directory Certificate Services’

In ‘Server Manager’, right click on the ‘Roles’ node and select ‘Add Roles’ from the menu as shown below

You will be shown the following

Click ‘Next’ to move to the next screen. On the resulting screen put a check mark next to ‘Active Directory Certificate Services’ and then click the ‘Next’ button as shown below

You will be shown a page that gives a brief introduction to Active Directory Certificate Services as shown below. Simply click the ‘Next’ button to move on.

On the resulting ‘Select Role Services’ screen, ensure that ‘Certification Authority’ is checked and then click the ‘Next’ button as shown below

Also, you want to put a check mark beside ‘Certification Authority Web Enrollment’. As soon as you do, you will see the following

This lets you know that the item we just selected depends on IIS being installed on this machine. Go ahead and click the ‘Add Required Role Services’ button and then click on the ‘Next’ button as shown below

On the resulting ‘Specify Setup Type’ screen, ensure that ‘Enterprise’ is checked and then click the ‘Next’ button as shown below

On the resulting ‘Specify CA Type’ screen, ensure that ‘Root CA’ is checked and then click the ‘Next’ button as shown below

On the resulting ‘Set Up Private Keys’ screen, ensure that ‘Create a new private key’ is checked and then click the ‘Next’ button as shown below

On the resulting ‘Configure Cryptography for CA’ screen, just accept the default values and then click the ‘Next’ button as shown below

On the resulting ‘Configure CA Name’ screen, just accept the default values and then click the ‘Next’ button as shown below

On the resulting ‘Set Validity Period’ screen, just accept the default values and then click the ‘Next’ button as shown below

On the resulting ‘Configure Certificate Database’ screen, just accept the default values and then click the ‘Next’ button as shown below

The next screen provides a bit of info about IIS which is about to be installed. Simply click the ‘Next’ button as shown below

On the resulting ‘Select Role Services’ screen, leave the defaults as is and simply click the ‘Next Button as shown below

Finally, on the ‘Confirm Installation Selections’ screen, click the ‘Finish’ button as shown below

 

During the installation process you will see the following screen

 

Once completed you will be presented with the completion screen. Click the ‘Close’ button to finish the process as shown below

 

And that’s all there is to it. Active Directory Domain Services, DNS Server and Active Directory Certificate Services are now installed on MdcDc.

Active Directory Certificate Services does not required any further configuration at this point, but there are still quite a few configuration issues that need to be taken care of for Active Directory and DNS, and that will be the focus of our next section.

 

Thank you for reading

 

 

Addition to Exploring Lync Server 2010 - Part 10

While working on Part 11 of Exploring Lync Server 2010, I realized that I left out a few steps in Part 10.

So for those of you that are following along, please have a look at the end of Part 10 where I have added the missing steps.

I am writing up Part 11 now and should have it online shortly

Thanks for reading

Exploring Lync Server 2010 - Part 10 - Creating Our First Virtual Machine

Welcome to Part 10 of Exploring Microsoft Lync Server 2010.

In the last segment, we took the Master Virtual Machine that was previously created and prepared it for cloning using SYSPREP.  In this section, we will be creating our first Virtual Machine based on the SYSPREP’d Master Virtual Machine.

The first thing we need to get up and running on our network is Active Directory. So let’s create a new Virtual Machine that we can use for Active Directory.

First off, fire up Windows Explorer and create a new folder under “C:\Virtual Machines\Production” called “MDC Domain Controller” as shown below

Next, start “Server Manager” and navigate to the “MDCBASE01” node under HyperV as shown below

Right click on the “MDCBAE01” node and select ‘New’ and then ‘Virtual Machine’ from the drop down menus as illustrated below

This will start the ‘New Virtual Machine Wizard’ as shown below

Click ‘Next’ and set the name of the Virtual Machine to be “MdcDc” and set the path to point to our recently created folder “C:\Virtual Machines\Production\Mdc Domain Controller” as shown below

Click ‘Next’ and on this screen, set the memory to 1024MB as shown below

Click ‘Next’ and select ‘MdcBase01VirtualNetwork’ from the Connection drop down so that our Virtual Machine will be connected to our network, as shown below

Click ‘Next’. On this screen, you want to select the ‘Attach a Virtual Hard Disk later’ radio button as shown below. We will be attaching the hard disk shortly.

Click ‘Next’ and you will be presented with the following summary screen.

Click ‘Finish’ and the new Virtual Machine will be created.

The next thing we want to do is to attach a hard drive to this newly created Virtual Machine. Using Windows Explorer, copy the SYSPREP’d hard drive located at

C:\Virtual Machines\Sysprepd Virtual Hard Drives\Windows Server 2008 R2\WindowsServer2008R2_SysPrepd.vhd’

to the folder located at ‘C:\Virtual Machines\Production\Mdc Domain Controller\MdcDc’ as shown below

Next, rename the copied hard drive to “WindowsServer2008R2_MdcDc.vhd” as shown below

Now that the hard drive is in the proper location, we can turn our attention to attaching it to the MdcDc Virtual Machine. In Server Manager, right click on the MdcDc Virtual Machine and select ‘Settings’ from the popup menu as shown below

In the settings dialog, select ‘IDE Controller 0’ from the left hand column and then select ‘Hard Drive’ in the right hand pane as shown below

Clicking the ‘Add’ button produces the following screen

Click on the ‘Browse’ button and select the hard drive located at C:\Virtual Machines\Production\Mdc Domain Controller\MdcDc\ WindowsServer2008R2_MdcDc.vhd’ as shown below

Click ‘Ok’ and the proper hard drive will now be part of the MdcDc Virtual Machine.

Now that the Virtual Machine is complete, it is time to start it up.  Since the MdcDc Virtual Machine was created from our Master Virtual Machine image, we can expect to go through a Miniature Setup Routine as this is the first time that it will be started.

Using Server Manager, right click on ‘MdcDc’ Virtual Machine and select ‘Start’ from the popup menu as shown below

Right click on ‘MdcDc’ Virtual Machine a second time, and select ‘Connect’ from the popup menu to open a window into the Virtual Machine as shown below

You will see the following screen shots as the MdcDc Virtual Machine starts up

Once the MdcDc Virtual Machine reboots you will be presented with the following screen

Leave the default values as is, click ‘Next’ and you will be presented with the following

Click ‘Start’ and you will be presented with the following screen

Click Ok to change the password. The requirements for a highly secure password were removed when we created our Mater Virtual Machine, and are therefore still removed in MdcDc. So change the password to something simple and then click the blue arrow as shown below

Once you click the Blue arrow, the password will be updated and you will be shown the following screen

Click the ‘Ok’ button and you will be presented with the following

This ‘Initial Configuration Tasks’ screen should look familiar to you as we saw it earlier when we first setup our Base Machine.

Now there are a couple of items that we need to configure at this point before we can call our MdcDc Virtual Machine configured, the first of which is to configure networking

Click on ‘Configure Networking’ as shown below

You will now be taken to the ‘Network Connections’ screen. Right click on the icon which represents our connection to the Virtual Network and select ‘Properties’ from the popup menu as shown below

You will be presented with the ‘Local Area Connection Properties’ dialog. Highlight ‘Internet Protocol  Version 4 (TCP/IPv4)’ by clicking on it and then click the ’Properties’ button as shown below.

At this point you will be shown the ‘Internet Protocol Version 4 (TCP/IPv4)’ dialog as shown below.

Now back in Part 5 of this series, I presented a table that contained the ranges of IP Addresses that we would be using for the various machines in our infrastructure. I have again shown this table below

Start Range

End Range

Device

192.168.20.20

-

Router

192.168.20.50

192.168.20.99

Network Printers

192.168.20.100

192.168.20.199

Base Machines

192.168.20.200

192.168.20.255

Hyper V Virtual Machines

 

Since MdcDc is a virtual machine and since it is the first virtual machine we have setup, let’s go ahead and use 192.168.20.200 as our IP Address.  

This network configuration step should be familiar to you as we have performed it previously when setting up our Base machine. 

Again, since we are not yet running a DNS Server, I will use the DNS Servers that my ISP provides. The IP Addresses for ‘Preferred DNS Server’ and ‘Alternate DNS Server’ that you use will of course be the ones that your ISP provides.

Fill in the values as shown below and then click the ‘Ok’ button.

You will be taken back to the ‘Local Area Connection Properties’ dialog. Click the ’Close’ button as shown below.

You can now close the ‘Network Connections’ window that is shown below

The last thing we need to do is to change the name of the virtual machine. You can do this my clicking on the ‘Provide computer name and domain’ link in the ‘Initial Configuration Tasks’ windows as shown below

In the ‘System Properties’ window, click the ‘Change’ button and change the name of the computer to ‘MdcDc’ as shown below

For now we can leave the ‘Member Of’ set to ‘WorkGroup’. This will change once we have our domain controller fully setup. Go ahead and click the ‘Ok’ button and you will be presented with the following.

Click the ‘Ok’ button. Then click the ‘Close’ button for the ‘System Properties’ dialog as shown below

When prompted click the ‘Restart Now’ button

The MdcDc Virtual Machine will now reboot. Once the computer restarts we will again be presented with the ‘Initial Configuration Tasks’ screen.

From this point on we will not be need the ‘Initial Configuration Tasks’ screen to be shown when we first start our Virtual Machine, so put a check mark in the ‘Do not show this window at logon’ checkbox at the bottom of the screen. Lastly click on the ‘Close’ button as shown below.

And that’s all there is to it. We now have our MdcDc Virtual Machine all setup.

Although it took a little bit of time to get ourselves to the point where we could create Virtual Machines based on an image, I’m sure you will agree that the process of cloning will save us lots of time in the future as we build out our infrastructure.

So that wraps it up for Part 10. Next time in Part 11, we will get busy installing Active Directory onto MdcDc

Thanks for reading

More Posts Next page »