Pages

Banner 468

Showing posts with label microsoft exchange installation. Show all posts
Showing posts with label microsoft exchange installation. Show all posts
Tuesday, 19 July 2016

Install Terminal Services on Windows Server 2012 R2

0 comments
 

Introduction

With the Release of Server 2012 R2 Microsoft completely changed how Remote Desktop Services are deployed and managed. This change tossed many like myself for a loop as I could not find any documentation on how to do what was once a 5 minute task.
Hopefully after reading this article this once simple task will be simple once again

Steps (13 total)

1

Open Server Manager

Click Manage and Select Add Roles and Features
2

Select Remote Desktop Services installation

Select Remote Desktop Services installation and click next
3

Select Quick Start

Expand
Select Quick Start and click next
4

Select Session-based desktop deployment

Expand
Select Session-based desktop deployment and click next
5

Server Pool

Expand
Make sure the server you are installing on is listed in the server pool.
If you are installing on the same server you are physically logged into then the server should be there by default
Click Next
6

Installation Checks

Once the installation checks are completed choose to allow (or not) your server to restart automatically if required as part of the install and click Deploy
7

Wait

Hurry up and wait while your server does the install
8

Success!

Expand
Click Close to continue
9

Add TS Licensing

Open Server Manager and go to "Remote Desktop Services" on the left menu. This will show you the Overview with the status and settings for your terminal server.
If you plan to install the licensing services locally on this server click the RD Licensing icon in the "deployment overview" window. Then follow the instructions to install the licensing service locally and add your purchased licensing.
I am going to use a licensing server in this example so I won't go into detail on this option
10

Add Licensing Server

If you have more than one TS like I do you will want to use a Licensing server. This allows you to share your client TS licenses across all of your terminal servers making it easier to purchase and manage your license needs.
To uses this option click "Tasks" and Edit Deployment Properties"
11

Edit Deployment Properties

Expand
Click "RD Licensing"
Select your licensing type, I am using Per User
type in the name of your licensing server and hit add. Your licensing server will be contacted, verified and added to the list.
Click OK
12

Set Who Can Log into this server

Expand
Go to System >> Remote Settings >> Select Users and add the Group or Users who will be allowed to connect to this server
Readmore...
Monday, 4 November 2013

How to Set up an Ftp Server on Windows Xp Professional

0 comments
 

Steps

  1. 1
    First, you should start by retrieving your Windows XP CD.
  2. 2
    Next, click the Start button and go to the Control Panel.
  3. 3
    After that, select "Add/Remove Windows Components."
  4. 4
    Select "Internet Information Services" under "Windows Components."
  5. 5
    Click "details" and select the "File Transfer Protocol (FTP)" service. (Remember that this will also automatically select "Common Files" and "Internet Information Services Snap-In.")
  6. 6
    Click OK and follow the instructions for the install Wizard (or you can just push next if you don't feel like reading). Be prepared with your Windows XP CD, because it might prompt you for it if you haven't already installed it. Once it is done, you might have to restart your computer after this.
  7. 7
    After that, all you need to do is just paste the files you want to be public into "C:\INETPUB\FTPROOT." Note that by default, these files are read-only and public. Public meaning that anyone who knows the IP address may download copies from it.
  8. 8
    There's more to go! Now, you need to configure your router's firewall to let FTP traffic through. This can be done through your router's administration menu. Note that this will vary depending on your router.
  9. 9
    After letting your router firewall let FTP connections in, you will have to configure your regular firewall to let FTP connections in through a certain port.
  10. 10
    Finally, after done with everything, you may access your FTP site through your browser. All you need to do is type ftp://xxx.xxx.xxx.xxx/ in the URL where "xxx.xxx.xxx.xxx" is the WAN address of your computer.

Readmore...
Sunday, 1 September 2013

Articles & Tutorials

0 comments
 


Readmore...

Configuring an Exchange 2013

0 comments
 

Introduction

In part 7 of this multi-part article series revolving around Exchange 2013 hybrid deployment based migrations to the new Office 365 or more precisely Exchange Online, we converted our custom managed domain to a federated domain, so that users will be able to authenticated against Office 365 using their UPN login.
In this part 8, we will continue where we left off in part 7. That is we will install and configure the Windows Azure Active Directory (WAAD Sync tool on our Windows Server 2012 domain-member server and start object synchronization from our on-premises Active Directory to the Office 365 tenant.
Note:The WAAD Sync tool was formerly known as the Directory Synchronization tool (DirSync tool).
Let’s get going...

Activating Active Directory Synchronization

The first preparation step we want to complete before concentrating on installing and configuring the WAAD Sync tool on the respective domain member server in our on-premises environment is to activate directory synchronization for our Office 365 tenant. This can be done by logging on to the Office 365 portal followed by clicking on the “users and groups”. and from here click “Set up” to the right of “Active Directory synchronization” in the top of the page as shown in Figure 1 below.
Image
Figure 1:
Users and groups page in the Office 365 portal
Under “Set up and manage Active Directory synchronization”, click on the “activate” button in “step 3”.
Image
Figure 2:
Clicking on the activate button
You will now be asked whether you really wish to activate directory synchronization from your on-premises environment to Office 365. Since this is exactly what we want to do, click “activate” once again.
Image
Figure 3: Do we really wish to activate directory synchronization?
Although we just activated directory synchronization, this will not occur instantly. As you can see in Figure 4, we need to wait up to 24 hours before it’s activated.
Image
Figure 4: Activation in progress

Creating the WAAD Sync Service Account

While we wait for directory synchronization to complete, let’s create the service account that should be used for configuring directory synchronization. We should create this account in the Office 365 tenant. To do so, click “users and groups” and then hit the “plus” sign as shown in Figure 5.
Image
Figure 5: Clicking “plus” sign
Enter the name and UPN logon for the account and click “next”.
Image
Figure 6: Naming the account and giving it a UPN logon name
On the “settings” page, make sure to assign the account “Global Administrator” permissions. Also, specify the email address that should be used if there’s a need to someday reset the password for this account.
Click “next”.
Image
Figure 7: Assigning the account Global Administrator permissions
Since the account should not be used to access any Office 365 services, leave all of them unticked and click “next”.
Image
Figure 8: No need for any licenses
Now specify the email address to which the temporary password should be sent and click “create”.
Image
Figure 9: Send results in email
On the “results” page, click “finish”.
Image
Figure 10: Results page
Now log off the portal and log on again using the new accounts credentials.
Image
Figure 11:
Logging on to the portal with the new account
You will be asked to specify a new password for the account. Do so and click “save”.
Image
Figure 12: Specifying a new password for the new account
Now you need to decide whether the new account, which can be considered a service account should follow the Office 365 password expiration policy meaning you need to change the password for the account every 90 days or if you rather want to set the password to never expire.
I’ll do the latter.
Since this can’t be done via the Office 365 portal, we need to connect to the Office 365 tenant using Windows PowerShell.
When connected to the Office 365 tenant, we can check the “PasswordNeverExpires” value with the following command:
Get-MsolUser –UserPrincipalName “svc-dirsync@clouduserdk.onmicrosoft.com” | fl
Image
Figure 13:
Value of the “PasswordNeverExpires” attribute for the new service account
To change this value to “True”, we can use the following command:
Set-MsolUser –UserPrincipalName “svc-dirsync@clouduserdk.onmicrosoft.com” –PasswordNeverExpires “true”
Image
Figure 14: Changing the password never expires attribute to “true”
Ok let's see whether active directory synchronization has been activated. As you can see in Figure 15, this is the case so we can move on to the next action, which is to install and configure the WAAD Sync tool.
Image
Figure 15: Active directory synchronization is now activated

Installing and Configuring the WAAD Sync Tool

When directory synchronization has been activated, let’s switch back to the server on which we wish to install the WAAD Sync tool. You can download the latest version of the WAAD Sync tool from the Office 365 portal. More specifically under “users and groups” > “Set up” and here click the “download” button under “step 4”.
Image
Figure 16: Downloading the WAAD Sync tool
From there launch the WAAD Sync tool setup wizard. On the “Welcome” page, click “Next”.
Image
Figure 17: WAAD Sync tool setup wizard – Welcome page
Accept the license terms and click “Next”.
Image
Figure 18: Accepting the license terms
On the “Select Installation Folder” page, click “Next”.
Image
Figure 19: Select installation folder page
Let the installation finish. This can take a few minutes.
Image
Figure 20: WAAD Sync tool is being installed
When installation has completed, click “Next”.
Image
Figure 21:
Installation complete
On the “Finished” page, make sure “Start Configuration wizard now” is ticked then click “Finish”.
Image
Figure 22:
Finish page
The WAAD Sync tool Configuration wizard will now launch. On the “Welcome” page, click “Next”.
Image
Figure 23:
WAAD Sync tool Configuration wizard
On the “Windows Azure Active Directory Credentials” page, enter the credentials for the service account we created in the previous section and click “Next”.
Image
Figure 24:
Entering the credentials for the WAAD Sync service account
On the “Active Directory Credentials” page, enter the credentials of an account with domain administrator permissions in the on-premises Active Directory.
Note:
This does not need to be a dedicated service account as these credentials aren’t saved.
Click “Next”.
Image
Figure 25:
Entering the credentials of a domain administrator
We’re now taken to the Exchange hybrid deployment page. If the DirSync Configuration setup wizard detects Exchange 2010 SP1 (or later) servers in the on-premises Active Directory we will be able to tick “Enable Exchange hybrid deployment”.
Note:
If the setup wizard doesn’t detect any Exchange 2010 SP1 (or later) servers, the tick box will be greyed out. Since we, in this article series, are dealing with an Exchange hybrid deployment based configuration based on Exchange 2013 servers, we wish to tick this option.
When ticking the “Enable Exchange hybrid deployment” box, we allow the WAAD Sync tool to perform write-back from Office 365 to the on-premises Active Directory for specific attributes. This is in order to allow support for features such as archive on-premises mailboxes in the cloud, off-board mailboxes from the cloud to on-premises Exchange servers, have on-premises filtering software take advantage of user made safe and blocked senders in the cloud and UM online voice mail.
With Exchange hybrid deployment enabled, write-back will be performed for the following attributes:
Write-Back   attribute
Exchange   "full fidelity" feature
SafeSendersHash
  BlockedSendersHash
  SafeRecipientHash
Filtering Coexistence: Writes back on-premises filtering and online safe and blocked sender data from clients.
msExchArchiveStatus
Online Archive: Enables customers to archive mail in Microsoft Online.
ProxyAddresses
  (LegacyExchangeDN as X500)
Enable Mailbox: Off-boards an online mailbox back to on-premises Exchange.
msExchUCVoiceMailSettings
Enable Unified Messaging (UM) - Online voice mail: This new attribute is used only for UM-Microsoft Lync Server 2010 or later integration to indicate to Lync Server 2010 or later on-premises that the user has voice mail in online services.
Table 1: Write-back attributes when hybrid deployment is enabled
When you have ticked “Enable Exchange hybrid deployment”, click “Next”.
Image
Figure 26:
Ticking enable “Hybrid Deployment”
Now we reach the new “Password Synchronization” page, where we have the option to enable password synchronization from the on-premises Active Directory users to the user objects in the Office 365 tenant. With password synchronization we can achieve SSO as in “same sign-on” not SSO as in “single sign-on”, which is possible with ADFS based federation between the on-premises environment and the Office 365 tenant.
Since we use ADFS based federation in this article series, make sure “Enable Password Sync” is unticked and click “Next”.
Image
Figure 27:
Password synchronization page
Wait for the WAAD Sync tool configuration wizard to complete the configuration.
Image
Figure 28:
Completing configuration
When configuration has completed, click “Finish”.
Image
Figure 29:
Configuration complete
Now make sure “Synchronize directories now" is selected and then click “Finish”. This will initiate the first synchronization from the on-premise Active Directory to the metaverse and the export from the metaverse to the Office 365 tenant.
Image
Figure 30:
Finished page
You will receive the warning shown in Figure 31, which includes a link to a TechNet page that explains how you can verify synchronization works properly. Click “OK”.
Image
Readmore...