Lync Server 2013 Step by Step

Chatpers at a Glance

CHAPTER    1	Introduction to Lync Server 2013
CHAPTER    2	Designing Lync Server 2013
CHAPTER    3	Installing Lync 2013 Front End Server
CHAPTER    4	Installing Lync Directory Server
CHAPTER    5	Installing Lync Edge Server
CHAPTER    6	Deploying Mediation Server and   Enterprise Voice
CHAPTER    7	Configuring Lync 2013 Features
CHAPTER    8	Administering Lync Server 2013
CHAPTER    9	Migrating from OCS 2007 R2/Lync 2010 to   Lync 2013

Buy this Book

Step by Step guide to build a Cisco wireless infrastructure using Cisco WLC 5500, Cisco 1142 AP and Microsoft Radius server

Pre-requisites:

1. Microsoft Active Directory and DNS
2. DHCP Server with new scope configured
3. IP helper-address configured
4. Microsoft Radius (IAS) Server 2003 or Microsoft Network Policy Server 2008
5. Microsoft Enterprise root CA
6. Cisco Wireless LAN controller (WLC) 5500
7. Cisco AIR-LAP1142N wireless access point (AP)
8. Separate VLAN for wireless infrastructure
9. WLC, AP and IAS placed in same VLAN
10. Windows 7 or Windows XP or Mac OSX/snow leopard client

Assumptions:

1) AD and DNS working perfect.

2) DHCP Server IP: 10.10.9.4

New scope for Wireless Network

IP range: 10.10.10.1-10.10.11.254 Subnet Mask:255.255.255.0

Gateway:10.10.10.1 Exclusion:10.10.10.1-10.10.10.10

NTP :10.10.9.5

3) WLC

IP:10.10.10.2 WLC subnet:255.255.255.0 Gateway:10.10.10.1

Time provider:10.10.9.5

4) IAS IP:10.10.10.3 subnet:255.255.255.0 Gateway:10.10.10.1

5) IP ranges 10.10.10.1-10.10.11.254 added in the internal networks in ISA or forefront TMG.

6)Interface 1 of WLC connected to a trunk port of Layer3 switch or core switch

7)wireless infrastructure VLAN ID/Tag 100

Add Lightweight Cisco Aironet 1142 in DHCP Server

Note: Follow these steps for newly added DHCP scope mentioned in assumptions.

1.In order to configure these options in the Windows DHCP server, open the DHCP Server Administration Tool or MMC. Right-click the DHCP root, and then choose Define Vendor Classes.

2.The DHCP Vendor Classes utility appears. Click Add.

3.A New Class configuration box appears. Enter a value for the Display Name field, for example, “Cisco Aironet c1142 AP”, and an appropriate description such as “Vendor Class identifier for Cisco Aironet c1142 AP”. Click the ASCII Section and enter the appropriate string value such as “Cisco AP c1142” (without inverted coma) for the Vendor Class Identifier. Click OK. Then, click Close on the DHCP Vendor Classes window.

4.Add an entry for the WLAN controller sub-type as a pre-defined option configured for the Vendor Class. Right-click the DHCP Server Root, and then choose Set Predefined Options.

5.Choose the newly created Vendor Option Class in the Option Class field, and then click Add.

6.The Option Type box appears. In the Name field, enter a string value, for example, Option 43. Choose IP Address as the Data Type. Check the Array check box. In the Code field, enter the sub-option code value 241 (0xf1). Enter a Description such as Wireless LAN Controller IP address. Click OK.

7.The Vendor Class and sub-option are now programmed into the DHCP server. Now, the vendor specific information must be defined for the AP DHCP scope. Choose the appropriate DHCP scope. Right-click Scope Options, and choose Configure Options.

8.Click the Advanced tab. Choose the Vendor Class you previously defined. Check the 241 Option 43 check box, and then enter each WLC management interface IP address(s) Example: 10.10.10.2. Click Apply.

9.Once you complete this step, the DHCP Option 43 is configured. This DHCP option is IP address, the DHCP server sends the option 43 as well as to the LAPs. Now the DHCP option 43 (241 Cisco Wireless AP) that is made available for a newly created DHCP scope for Cisco.

10. To verify, click on the scope options in the newly created DHCP scope, you will see 241 Cisco Wireless AP or what you mentioned in Description.

Add a new VLAN in core switch(example: Cisco 4506) or L3 switch:

Note: Entire wireless infrastructure will be placed in this VLAN.

Switch#vlan database

Switch(vlan)#vlan 100

Switch(vlan)#name Wireless Network

Switch(vlan)#exit

switch#configure terminal

Switch(config-if)#interface vlan 100

Switch(config-if)#Description Wireless Network

Switch(config-if)#ip helper-address 10.10.9.4

Switch(config-if)#IP address 10.10.10.1 255.255.255.0

Switch(config-if)#no shutdown

Switch(config-if)#end

switch#wr

Create a Trunk Port in Core switch (Cisco 4506) or L3 Switch

Note: This trunk will be connecting with Cisco WLC 5500 using CAT6 or Fibre optic.

Switch# configure terminal

Switch(config)#interface gigabitethernet  6/11

(6/11 means Module 6 and Port 11)

Switch(config)#switchport trunk encapsulation dot1q

Switch(config)#SwitchPort Mode trunk

Switch(config)#end

Switch# wr                                              

Switch#show run

Create VLAN  in a switch (Example: Cisco 2960G)

Note: This port will be connecting with Cisco 1142 AP. Wherever you want an wireless AP, configure a port with same vlan. For this article VLAN 100. connect AP with this port after configuring the following. repeat for all the APs.                     

Switch# configure terminal

Switch(config)#

Switch(config)#interface Gigabitethernet 0/7           

Switch(config)#switchport access vlan 100            

Switch(config)#end

Switch# wr             

Create AAA Server(s):

Authorization: IAS Policies (Remote Access Policies applied in IAS server for wireless 802.1x)

Authentication:Radius Server (EAP Type:PEAP,Encryption: MSCHAPv2)

Accounting:Radius server (Logs any successful and/or failed connection attempt)   

Use this link to configure Enterprise Root CA  

Install IAS in a member server. Install computer certificate in the IAS server and create new policy using this link Configure PEAP and EAP methods or follow step by step guide line in these links configure Microsoft Radius Server and Network Policy Server . It would redundant to write again.

Cisco 5500 Series Wireless Controller Installation Guide Using the Start-up Wizard

Mount Cisco 5500 in rack. Connect WLC with laptop using console port. Connect WLC with core switch or L3 switch using CAT6 cable or fibre optic if you have SFP. Now power on WLC.

Note The available options appear in brackets after each configuration parameter. The default value appears in all uppercase letters.

Note Press the hyphen key if you need to return to the previous command line. To configure the controller for basic operation using the Start-up Wizard, follow these steps:

Step 1 When prompted to terminate the Auto-Install process, enter yes. If you do not enter yes, the Auto-Install process begins after 30 seconds.

Note The Auto-Install feature downloads a configuration file from a TFTP server and then loads the configuration onto the controller automatically.

Step 2 Enter the system name, which is the name you want to assign to the controller. You can enter up to 32 ASCII characters. (Example:MS_5500)

Step 3 Enter the administrative username and password to be assigned to this controller. You can enter up to 24 ASCII characters for each. The default administrative username and password are admin and admin, respectively.(Example:username:Admin and password:cisco)

Step 4 If you want the controller’s service-port interface to obtain an IP address from a DHCP server, enter

DHCP. If you do not want to use the service port or if you want to assign a static IP address to the service-port interface, enter none.

Important! In Cisco 5500, management interface act as service interface also. No avoid any complicacy, just hit enter in this option. The service-port interface controls communications through the service port. Its IP address must be on a different subnet from the management interface. This configuration enables you to manage the controller directly or through a dedicated management network to ensure service access during network downtime.

Step 5 If you entered none in Step 4, enter the IP address and netmask for the service-port interface on the next two lines.

Step 6 Enable or disable link aggregation (LAG) by choosing yes or no. You may type No if you don’t have two or more Cisco WLC.

Step 7 Enter the IP address, netmask, default router IP address, and optional VLAN identifier (a valid VLAN identifier or 0 for an untagged VLAN) for the management interface.

Note The VLAN identifier should be set to match the switch interface configuration. Example: IP:10.10.10.2 WLC subnet:255.255.255.0 Gateway:10.10.10.1  and VLAN tag/ID 100

Step 8 Enter the IP address of the default DHCP server that will supply IP addresses to clients, the controller’s management interface, and optionally the service-port interface.

Note The management interface is the default interface for in-band management of the controller and connectivity to enterprise services such as AAA servers.Example DHCP Server IP: 10.10.9.4

Step 9 Enter the IP address of the controller’s virtual interface, which will be used by all controller Layer 3 security and mobility managers. You should enter a fictitious, unassigned IP address, such as 1.1.1.1.

Note The virtual interface is used to support mobility management, DHCP relay, and embedded Layer 3 security such as guest web authentication and VPN termination. All controllers within a mobility group must be configured with the same virtual interface IP address.

Step 10 If desired, enter the name of the mobility group/RF group to which you want the controller to belong.

Note Although the name that you enter here is assigned to both the mobility group and the RF group, these groups are not identical. Both groups define clusters of controllers, but they have different purposes. All of the controllers in an RF group are usually also in the same mobility group and vice versa. However, a mobility group facilitates scalable, system-wide mobility and controller redundancy while an RF group facilitates scalable, system-wide dynamic RF management.

Step 11 Enter the network name, or service set identifier (SSID). The initial SSID enables basic functionality of the controller and allows access points that have joined the controller to enable their radios. (Example:Mycompanywireless)

Step 12 Enter yes to allow clients to assign their own IP address or no to make clients request an IP address from a DHCP server. (Type yes in the step)

Step 13 To configure a RADIUS server now, enter yes and then enter the IP address, communication port, and secret key of the RADIUS server. Otherwise, enter no. (Type yes, IAS IP:10.10.10.3 subnet:255.255.255.0 Gateway:10.10.10.1)

Step 14 Enter the code for the country in which the controller will be used.

Note Enter help to view the list of available country codes. (Example: For Australia Country code is AU)

Step 15 Enter yes to enable or no to disable each of the 802.11b, 802.11a, 802.11g, and 802.11n lightweight access point networks. (Type yes)

Step 16 Enter yes to enable or no to disable the controller’s radio resource management (RRM) auto RF feature. (Type yes)

Note The auto RF feature enables the controller to automatically form an RF group with other controllers. The group dynamically elects a leader to optimize RRM parameter settings, such as channel and transmit power assignment, for the group.

Step 17 If you want the controller to receive its time setting from an external Network Time Protocol (NTP) server when it powers up, enter yes to configure an NTP server. Otherwise, enter no. (Type yes,Time provider:10.10.9.5 )

Step 18 If you entered no in the previous step and want to manually configure the system time on your controller now, enter yes. If you do not want to configure the system time now, enter no.

Step 19 If you entered yes in the previous step, enter the current date in MM/DD/YY format and the current time in HH:MM:SS format.

Step 20 When prompted to verify that the configuration is correct, enter yes or no. The controller saves your configuration, reboots, and prompts you to log in.

Verifying Interface Settings and Port Operation

Follow these steps to verify that your interface configurations have been set properly and the controller’s ports are operational.

Step 1 Enter show interface summary. The controller’s current interface configurations appear:

Interface Name Port VLAN Id IP Address Type AP Mgr Guest

———-

management 1 100 10.10.10.2 Static Yes No

service-port N/A N/A 0.0.0.0 Static No No

virtual N/A N/A 1.1.1.1 Static No No

Step 2 Enter show port summary. The following information appears, showing the status of the controller’s distribution system ports, which serve as the data path between the controller and Cisco lightweight access points and to which the controller’s management interface is mapped.

STP Admin Physical Physical Link Link Mcast

Pr Type Stat Mode Mode Status Status Trap Appliance POE

– —

1 Normal Forw Enable Auto 1000 Full Up Enable Enable N/A

2 Normal Forw Enable Auto 1000 Full Up Enable Enable N/A

Configure Security and AAA Server in WLC 5500

1. Open IE or Firefox Type IP address of WLC in the address bar as https://10.10.10.2 (bypass proxy if you need to)and hit enter.

2. Click Login and provide login credentials you created in start-up wizard.

3. Click on Wireless. In the left hand pan click Authentication. You will see the IP address and port number 1812 of Radius Server.

4. In the left hand pan Click on Accounting. Click new on right hand top corner. You will be presented with a window to add Radius server. provide IP of Radius server, Shared secret and Port 1813. Apply changes.

5. Click on WLANs>Click on 1>Click on General Tab>Check Enable on Status and Check Enabled on broadcast SSID

6.Click on Security Tab>Click Layer2 Tab>Select WPA+WPA2 from Layer2  security drop-down list>Check WPA policy and TKIP or WPA2 policy and TKIP. In the same page, in Auth Key Mgmt, select 802.1x. Now click on Apply button.

7.Click on AAA Servers>Select Authentication and Accounting server from the server1 drop down list. here Authentication and Accounting server are Radius Server. Check Enabled in both Authentication and Accounting radio button. Click Apply.

8.In the left hand side top corner, click on to Monitor and scroll down to make sure you see the all APs.

Add WLC 5500 in the IAS server as a Radius Client

1. Log on to IAS server as an administrator.

2.Open Internet Authentication Service from Administrative Tools

3.Right click on Radius Clients>Click add Radius client. You will be presented with new radius client window. Type IP address of WLC 5500 and a Friendly Name such as WLC. Click Next.

4. In the this window, Select Radius Standard as Client-Vendor, Provide shared secret (must be same as WLC configuration in step 13) and repeat shared secret and click finish.

5.Close IAS console and log out.

Testing network

Log on to Windows XP or Windows 7 client as a domain users while client is connected via CAT5 or CAT6 . Make sure this domain user is a member of wireless access group and allowed to have remote access(dialin TAB of AD user property). Install computer and user certificate in that client. Now turn on wireless NIC. unplug CAT5 cable. View available wireless network. Select the SSID, you created in previous steps and double click. You will be connected.

Important! if you setup WPA and TKIP in WLC then you must setup WPA and TKIP in Client also. Similar for WPA2 and TKIP or WPA2 and AES. Both sides must match each other.

For Mac client, see my previous post in the link

Configure Group Policy for 802.1x wireless network

1. Open the Group Policy Management Console (GPMC).
2. Create and link a new group policy object with desired OU
3. Right click on newly created GPO and edit
4. Go to Computer Configuration, open Windows Settings, open Security Settings, and then select Wireless Network (IEEE 802.11) Policies.
5. right-click Wireless Network (IEEE 802.11) Policies, and then click Create A New Policy and Type Policy name
6. Open New Network Policy Properties >Click on preferred network Tab>To add a new profile, click Add>type the SSID that corresponds to the SSID configured on your WLC security tab.
7. In the Wireless key network, select WPA and TKIP or whatever configured in WLC
8. In the IEEE 802.1x tab,Set EAPOL start message to transmit per IEEE 802.1x
9. In the EAP type select PEAP
10. Check authenticate as computer when computer information is available and also computer authentication with user authentication from drop down box.
11. Now press Ok, Apply and ok.

Work Around with WLC 5500 

Open IE, Type IP of WLC in the address bar (bypassing proxy), hit enter. Click on Logon. provide logon credentials, click ok.

 

Accessing WLC using telnet.

Open command prompt and type telnet IP_Address

Necessary Links

Export a certificate with the private key

Import a certificate

Cisco 5500 WLC

Cisco Wireless AP

Microsoft Radius Server

Relevant Articles

WLAN Controller Failover for Lightweight Access Points Configuration Example

Wireless LAN Controller (WLC) Configuration Best Practices

How to configure Microsoft Radius Server (IAS) for Macintosh OSX 10.5, Windows 7 and windows XP Pro client

Install and configure Microsoft Active Directory Certificate Services (AD CS) using Windows Server 2008 R2

Windows Server 2008: how to configure Network Policy Server or Radius Server –Step by Step Guide

Overview of the Wi-Fi Protected Access (WPA) security update in Windows XP

Share this

How to configure Microsoft SharePoint server 2007

Microsoft SharePoint Products and Technologies is a Content Management System with integrated search functionality developed by Microsoft that allows users to work in a web-based collaborative environment. Microsoft provides certain built-in functionality and third party developers can also develop custom modifications to extend functionality. Microsoft released SharePoint server 2010 64 bit beta. Here, I am going to talk about SharePoint Server 2007.

Systems requirements:

Windows server 2003 or windows server 2008

Internet Information Services (IIS) 6.0 or Higher

SMTP service is enabled in IIS

ASP.NET 2.0

.NET Framework 3.0

Windows Workflow Foundation

SQL Server 2000 or 2005 express or higher with Management studio

Antivirus & Forefront Protection for SharePoint

Hardware requirements:

Processor 2.5GHz minimum, dual processors, 3GHz recommended.

RAM 1GB minimum, 2GB or more recommended.

Disk 3GB free NTFS. More disk space is recommended, depending on your storage needs.

Network 1 gigabit per second is suggested

This was minimum spec. However, you must add more resources to SharePoint server depending on number of users and configurations you do.

Create and configure SQL

Once you have installed all pre-requisite. You need to configure SQL server before you start installing SharePoint. To do this open SQL Management studio from start menu>all program>Microsoft SQl server>SQL server management studio.

You will be presented SQL\SQLExpress database connection window. Click on connect using windows authentication. Create new database named SharePoint or your preferred. Right click on new database>property>options>Collation> Change to  Latin1_General_CI_AS_KS_WS.

 

Important! Change database collation to Latin1_General_CI_AS_KS_WS. Otherwise you get this error  "The specified database has an incorrect collation.  Rebuild the database with the Latin1_General_CI_AS_KS_WS collation or create a new database”.

Installation:

 

If you want to have more then one server then select Advanced>Complete Installation otherwise standalone installation will do. File location can be selected other then system partition. 

 

Initial Configuration

   

 

Publish SharePoint in ISA or Forefront TMG

Log on ISA server or Forefront TMG. Open management console>Task Pan>Publish new web sites (ISA) or Publish SharePoint (Forefront TMG). Follow these screen shots.

In this window, click new to add new listener.

Start Windows Services

 

Configure Wiki, Document Library in SharePoint

Log on to sharepoint server. Open sharepoint central administrator. provide domain user name and password. You will be presented with SharePoint Central Administration window. Click on operations>Topology and services>services on this server>start all the services. To Setup Incoming and outgoing emails, you must have SMTP services installed and started.

Click on Site Action>Create. In this window you can document library, Wiki etc.

 

 

SharePoint and DNS records

Log on to DNS server. In Active Directory environment, domain controller is a DNS server by default. Add Host(A) record and CNAME for SharePoint server if you want to call SharePoint by FQDN not by Netbios name.

Relevant Topics:

Deployment for 2007 Microsoft Office SharePoint Server

Microsoft SharePoint Server

share this

Step by Step: Volume Activation for Windows 7 and Windows Server 2008

What is Microsoft product activation? Activation is a method of verification that Microsoft Windows Product you have bought is genuine and comply with copyright laws i.e. it checks that you are not using a counterfeit product. Simply Microsoft wants to know did you pay right amount of $$ for the product you are using. Volume Activation is used for enterprise level users who want to deploy Microsoft products such as Windows 7 and Windows Server 2008 in large scale in an organisation or a company. There are two type of Volume Activation—Key Management Service (KMS) and Multiple Activation Key (MAK)—that allow Volume Licensing customers to activate Volume License editions of the Windows 7 and Windows Server 2008 R2. When planning to use Volume Activation, an organization must choose KMS, MAK, or any combination of the two. The activation methods chosen depend on the needs of the organization and the network infrastructure. You don’t need to be a local Administrator in Windows 7 and Windows Server 2008 R2 for activation. However, for volume activation you must be a domain admin because you need to access domain groups, computers and GPO. Windows eliminates the User Account Control (UAC) prompt during activation, enabling any user who has a standard user account to activate Windows on that computer. However, this change does not allow standard users to remove Windows from the activated state.

Typical Activation Warning:

Configure Firewall in Windows7 and Windows server 2008 for Volume Activation to pass through:

You have to configure the following firewall in Windows 7 and Windows Server 2008  master pc before you deploy large scale using windows deployment services. By default these firewall is blocked restraining  windows 7 and windows server 2008 to communicate with activation site.

Log on Windows 7 or Windows Sever 2008. Control Panel>Windows Firewall and Advanced Settings>Allow Program or feature pass through Windows Firewall>Select Windows Management Instrumentation (WMI)>check domain, public and private>Click Ok.

Go back to Windows Firewall and click on Advanced Settings>Click Filter by Group>Click WMI>Select WMI Async-In>Double Click on WMI Async-In>General Tab>Check Enable and Allow>Advanced Tab>Check Public,Private,Domain>Select allow edge traversal>Apply>ok.

 

Configure Windows Firewall using GPO:

Log on to domain controller as an domain admin. Open GPO management console from Admin Tools. Select Specific Windows 7 and Windows Sever 2008 organisational unit where you want to modify Windows Firewall. Right click on that organizational unit>click edit. Go to Computer Configuration>Administrative Templates> Network>Network Connections>Windows Firewall>Domain Profile & Standard Profile>Select and Modify Windows Firewall: Allow remote administration exception>Select Enable and Type “*” in the box.

 

Windows7 Volume Activation:

You must have MAK  license to do the following. Install windows AIK in Admin PC. Go to All Program>Microsoft Windows AIK>VAMT 1.2 >VAMT

 

Provide MAK Product Key and Validate. Click Add to add MAK.

Select Appropriate Columns to view computer info.

Click Action>Add Computer>Type Computer Group>Select domain>Check gather info>Click ok.

Now select all windows 7 computer>right click>MAK activate.

Good Luck and happy Australia Day

Microsoft References:

Licensing Centre

Troubleshooting VA

How to Choose the Right Volume License Key for Windows

Windows Firewall

Enhanced Windows Server 2008 Backup Utility

Windows Server 2008  backup utility is completely different from the backup program included with Windows Server 2003. Unlike previous versions, the new utility is designed primarily to back up entire volumes to an external hard disk drive or to an UNC path. The backup utility also uses a different format for its backup files; it uses the Microsoft Virtual Hard Disk (VHD) format, which makes the files accessible to Hyper-V, Virtual PC, and the Complete PC backup utility. Windows Server 2008 backup utility allows you to backup entire drive or selected files or folder. You can perform complete backup or incremental backup. In addition to individual file and folder selection, the backup utility also enables you to create exclusions. An exclusion is a filter that prevents a job from backing up specified files or file types in the selected targets. There are three types of backup destination available in windows backup utility. these are dedicated hard disk drive, volume and UNC path.

System State and Bare Metal Backup

The System State includes the Windows Registry, the Active Directory database if the computer is a domain controller and a number of files that are locked open by the operating system. New windows backup utility enables you to individually select the System State element and a Bare Metal Recovery element. When you select bare metal backup, it will backup system partition and system state also. It will backup in .vhd format. 

To recover an entire computer, you connect your external hard drive containing the backup to the new computer and boot from the Windows Server 2008 R2 installation disk. Select Repair Your Computer in the Windows Setup Wizard>System Recovery Options>Restore Your Computer Using A System Image that you created earlier. Alternatively, you can import that .vhd file into Hyper-v if you desire to decommission physical machine.

Hyper-v Host Backup

To use Windows Server Backup to protect an entire Hyper-V server and its VMs, you must register the VSS Writer with the backup software by creating the following registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\WindowsServerBackup\
Application Support\{66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}

Right click>Create String value.

Name	Type	Value
Application Identifier	REG_SZ	Hyper-V

With this registry settings, it will backup everything other then virtual network, physical storage attach to VM, iSCSI storage when initiator running inside VM.

How to Screenshots:

 

To schedule a backup, open Windows Server Backup>click on backup schedule>follow the screen as shown below.

 

Here, you can specify destination of backup. I am showing UNC path and disk drive.

Provide domain credential for the safety of backed up data.

You can setup backup performance before taking a backup or scheduling a backup task.

 

To create backup once, click on backup once and follow the screenshots.

Here, you can choose Full (bare metal, disk drive) or custom (files or folders) backup. bare metal will create a .vhd file for Hyper-v.

 

Windows Server 2008: Install and configure windows media services 2008—step by step

Windows Media Services 2008 is an industry standard platform for streaming or on-demand audio/video content for windows XP and Windows 7 clients over private or public networks. Windows Media Services 2008 manages one or more Windows Media servers running on the Windows Server 2008 operating system. Client machine can play contents using Windows Media Player or Silverlight. Windows Media Services 2008 server capable of proxying, caching, or redistributing content.  Custom media content that have been developed using the Windows Media Software Development Kit (SDK) can also be deployed through media services. Windows Media Services 2008 contains a new, built-in cache/proxy plug-in that you can use to configure your Windows Media server either as a cache/proxy server or a reverse-proxy server.

System requirement:

Windows Server 2008 x86 or x64

IIS for web administration and content distribution

Windows Media Services x86 or x64

Media services server must be a member of domain

Windows 7 or Windows XP client

Windows Media Player or Silver light

Installation:

Download Windows Media Services. Install update on server as follows.

 

 

Configuration:

 

Here, I have shown config of IP address authorization property. You have to configure rest of them according to your need.

Install Web Certificate and Configure SSL:

Publish Content:

Expand publishing points>select content>select announce tab on right side pan>click run unicast announce wizard

CNAME Record:

Add CNAME record (Example:  media.yourdomain.com.au points windows media server) in DNS server .

Test Media Services:

Log on to a client machine

Open IE 6 or later>type https://media.yourdomain.com.au/test or http://media.yourdomain.com.au/test (here, /test is a test content uploaded in media services server)

Further Study:

Windows Media Player 12

Windows Media Services

Windows Deployment Services: Create and deploy multicast images

I would like to explain a bit about IP Multicast before I start with WDS multicast image distribution because not all the organisation have existing multicast infrastructure. Still, I reckon it would be worthy to know bits and pieces of a technology while working on it.  So what is IP Multicast? Multicast is a technique for one-to-many communication over an IP infrastructure in a network. It scales to a larger receiver population by not requiring prior knowledge of whom or how many receivers there are. Multicast uses network infrastructure efficiently by requiring the source to send a packet only once, even if it needs to be delivered to a large number of receivers resulting bandwidth savings. The nodes in the network take care of replicating the packet to reach multiple receivers only when necessary. The most common low-level protocol to use multicast addressing is User Datagram Protocol (UDP). IP addresses from 224.0.0.0 to 239.255.255.255 are designated as multicast addresses. This range was formerly called “Class D.” The sender sends a single datagram to the multicast address and the intermediary routers take care of making copies and sending them to all receivers that have registered their interest in data from that sender. Multicast IP ranges assigned through DHCP scope. In any case, range 224.0.0.0 through 224.0.0.255 is reserved for local purposes (as administrative and maintenance tasks) and datagram’s destined to them are never forwarded by multicast routers. Similarly, the range 239.0.0.0 to 239.255.255.255 has been reserved for administrative scoping.

WDS Multicast Image Creating multicast images in WDS server is easy and straightforward if you have a functioning multicast infrastructure. For multicast imaging to work properly, the network devices that connect the WDS multicast clients to the WDS server providing the multicast transmission must support and allow multicast traffic as mentioned above. If the WDS server already contains tested boot and install images. One important point to note about multicasting is that only the Windows Server 2008 boot.WIM boot image file contains a WDS multicast client. In WDS server, you have to add Windows Server 2008 boot.WIM file into boot image. Now follow the screenshots bellow to distributive multicast image. Delete Multicast image when distribution no longer required.

Log on to WDS server using Admin Privilege. Go to Administrative Tools>WDS>Servers>Expand WDS Server>Right click on Multicast Transmission>Click Create Multicast Transmission.

Here, you can schedule transmission if bandwidth and distribution time are criteria.