Alteration in Terminal Server's listening port

It is a well-known fact that TCP port 3389 is used by Terminal Server and Windows 2000 Terminal Services for client connections. Alteration in this port is not recommended by Microsoft. But you can change this port. You have to perform this task carefully, otherwise you will face serious problems.

You have to give more concentration while modifying the registry. If you want to change the default port, then you have to follow these steps:

You start with the task of running Regedt32 and go to this key, HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp. Then you have to find the port number subkey and notice the value of 00000D3D, hex is for 3389. After this, you have to change the port number in Hex and save the new value.

If you want to change the port for a particular connection on the Terminal Server, then follow these steps:

You have to run Regedt32 and go to this key, HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\connection. After this, you have to find the port number subkey and notice the value of 00000D3D, here hex is for 3389. Then you have to change the port number in Hex and save this new value.

After performing this, you have to make alteration in the Port on the Client Side. Follow these steps to perform this:

You have to open Client Connection Manager. Then on the File menu, click on New Connection and then create the new connection. After executing the wizard, you will view a new connection listed there. Then you have to ensure that new connection is highlighted. After this, on the File menu, click Export. Then you have to edit the .cns file using Notepad. You have to make modifications in the server port, Server Port=3389 to Server Port= new port number, that you had specified on Terminal Server. Now import the file back into Client Connection Manager. Then you will be demanded to overwrite the current one. If it has the same name, then overwrite it. In this way, you will receive a client that has the correct port settings to match your Terminal Server settings.

Microsoft SQL Backup

You are aware of the problems like disk failure, system crashes and many more. Due to these problems your important data will get lost. In this situation, you will be the loser. So, to avoid these problems you have to take a backup of your data. Microsoft has developed the Microsoft SQL Server, a widely used database management system. Handy Backup gives a fast and efficient way to backup Microsoft SQL Server database. Nowadays, many businesses whether small or large are using the databases stored on SQL servers. So, it is important to backup the SQL database.

Accuracy and reliability of Microsoft SQL (MSSQL) backup - Handy Backup uses Microsoft API but other backup tools use the ODBC protocol to backup MSSQL database. Handy Backup permits you to backup MSSQL database with all views, indexes, stored procedures and other data. You do not have to interrupt your SQL server services while performing MSSQL backup with Handy Backup. You can take backup of MS SQL Server 2005, MS SQL Server 2000, MS SQL Server 2008 with Handy Backup. Handy Backup can automatically recognize all SQL server databases available on your computer and also display them. It has many options which facilitate you in compressing your MSSQL backup with an integrated ZIP-compressor with 10 levels. You can also schedule the backup for a time period that you desire. You can save MS SQL backup on any storage media. These storage devices can be DVD, external drives and many more. So, it can be deducted that Handy Backup is a perfect tool for MSSQL backup because it allows you to always feel safe about your data.

Windows Server Security 2008 Support Services

This post provides Windows Server 2008 Security Guide. This guide provides instructions and recommendations to help strengthen the security of computers running Windows Server® 2008 that are members of an Active Directory® domain.

In addition to the guidance that the Windows Server 2008 Security Guide prescribes, this Solution Accelerator provides tools, step-by-step procedures, recommendations, and processes that significantly streamline the deployment process. This guide not only provides you with effective security setting guidance. It also provides you with a reproducible method that you can use to apply the guidance to both test and production environments.

The key tool that this Solution Accelerator provides for you is the GPOAccelerator. The tool enables you to run a script that automatically creates all the Group Policy objects (GPOs) you need to apply this security guidance. The Windows Server 2008 Security Guide Settings workbook that accompanies this guide provides another resource that you can use to compare and evaluate the Group Policy settings.

Microsoft engineering teams, consultants, support engineers, partners, and customers have reviewed and approved this prescriptive guidance to make it:
• Proven. Based on field experience.
• Authoritative. Offers the best advice available.
• Accurate. Technically validated and tested.
• Actionable. Provides the steps to success.
• Relevant. Addresses real-world security concerns.

Microsoft has published security guides for Windows Server 2003 and Windows 2000 Server. This guide references significant security enhancements in Windows Server 2008. The guide was developed and tested with computers running Windows Server 2008 joined to a domain that uses Active Directory® Domain Services (AD°DS).

Exchange Server Support for Backups and Single Item Recovery

Naturally after understanding the features included in Exchange 2010, a logical follow up question is "Do I still need backups for single item recovery?" The answer depends on your backup requirements and your capacity planning.

Today many customers minimize the deleted item retention window, yet they maintain long backup retention time periods (from 14 days to several months to years).

Let's consider a customer that currently maintains backups for 90 days and only retains deleted items within Exchange for 5 days. This customer is performing backup restores on a weekly basis to recover deleted items for end users. If the customer moved to Exchange 2010 they could move that process into Exchange by simply increasing their mailboxes capacity for dumpster: This post Contain the exchange server support tips to make backups and single Item Recovery.

• Users send/receive 100 messages per work day and have an average message size of 50KB
• Single Item Recovery is enabled and the deleted retention window is configured to be 90 days
• 10% of items are edited
• Mailbox capacity calculations

o 5 work days * 100 emails = 500 emails / week
o For Purges:
+ 500 emails / week * 13 weeks = 6500 emails / retention period
+ 6500 emails * 50KB ? 318MB
o For Versions:
+ 500 emails / week * 13 weeks = 6500 emails / retention period
+ 6500 emails * .1 = 650 emails
+ 650 emails * 50KB ? 32MB
o Total Space Required per mailbox: 350MB

By increasing each mailbox's capacity by a minimum of 350MB, backups are no longer needed for single item recovery. Single item recovery can be maintained and performed within Exchange.

But let's not stop there. What if the requirement is that items must be recoverable for 1 year? Assuming the same assumptions used in the previous example with the exception that deleted item retention is now configured for 365 days, each mailbox needs an additional minimum 1.4GB of space.

Ultimately, if the storage subsystem is planned and designed appropriately and mailbox resiliency features are leveraged, traditional point-in-time backups can be relegated to a disaster recovery mechanism, if they are even needed at all.

How Managed Exchange Can Increase Your Business?

Managed Exchange can help your business by converting Microsoft Outlook from an email communication device into a critical work tool. Get Better access to critical and frequently used information, Book or reserve popular shared company resources and Coordinate your daily schedules through personal calendar tools by Managed Exchange.

Staff can access their email and Outlook work tools (mentioned above) through a number of web-enabled devices such as: Desktop PCs, laptops, PDAs with GPRS, WAP mobile phones with GPRS, Blackberry mobile devices with GPRS. Data is constantly synchronized and updated, so no matter how staffs access their work tools, they always have the most up-to-date information when online. It helps staff be more organized and get more out of their day.

Managed Exchange is ideal for any business whose staffs need to work together using frequently shared information and need to have flexible access to critical work tools such as email, contacts and calendar when they cannot make it into the office.

Service providers Managed Exchange Solution allows smaller businesses to leverage all of the functionality of Microsoft Exchange, without having to cover the associated capital and operating costs associated with running an Exchange Server in-house. Managed Exchange is also suitable for small businesses with limited IT resources because all service providers are able to manage the back-end for you.

Your Managed Exchange service can generally be activated within one business day. For larger, customized configurations, service provider will arrange with you a suitable timeframe for activation of your service. You can get protection from spam, viruses and malware before they reach your network. No software, hardware or user training required.

How To Resolve OST Synchronization Error

In Microsoft Outlook, an offline folder (.ost file) is a locally stored file that is synchronized with your mailbox contents stored on Microsoft Exchange Server. The folders empower you to access them even when the mail delivery or network service is not available. The file converts into a usable .pst file as the synchronization process succeeds. But there can be several synchronization errors, due to which your .ost file might become unusable. In such cases, you might need to restore its contents from a backup stored as a .pst file. If it is not feasible, you should use a third-party tool to Convert OST to PST.

For an instance, you use Microsoft Outlook 2002 or 2003 with an offline folder. You press F9 to synchronize your .ost file with your Exchange Server mailbox, but fail to do so and come across the below error message:

"The file .ost cannot be accessed because it has been configured for use with a different mailbox."

If you close the application and try to perform synchronization again, you receive the same error message.

The Reason:
As the error message suggests, this error is encountered if you are attempting to synchronize the mailbox with an .ost file that is configured to use a different server or e-mail account. This usually occurs if you perform these steps in order:

You synchronize your .ost file with the mailbox 2-You perform some changes in name of either e-mail server or mailbox in your email account profile.

Doing so makes the current .ost file unusable.

Best Possible Solution
Create a new email profile with the desired account settings and restore data using any of the below solution:

1. You can then include the .pst files maintained as a backup of previous .ost file.


2. You can also copy this information to a .pst file from your mailbox after changing the changed email settings back to the original state.


3. If applying the above solutions are not possible, Convert OST to a usable .pst file.

Convert OST to PST are powerful applications that are competent to convert an usable .ost file into a usable .pst file after any type of crash.

Stellar Phoenix Mailbox Exchange Desktop is an effective utility that converts an .ost file into a .pst file. It can Convert OST by maintaining data integrity. Designed to perform safe file conversion, this utility can restore all file objects including emails, notes, journals, tasks and more. It is compatible with Outlook 2003, 2002, 2000, 98 and 97.

Benefits of Small Business Server Exchange 2003

Microsoft small business server 2003 is designed for organizations with up to 50 computers who need high-level reliability and functionality but don't have the economy of scale that allows big corporations to sop up the cost and complexity of licensing best-of-breed enterprise software. SBS 2003 is a cost effective and simple way to form a solid foundation for an information network with enterprise-level security, connectivity, performance, and reliability.

Windows SBS 2003 will be available in standard and premium editions. The standard edition includes Microsoft SBS 2003 and window server 2003. Small business server 2000 included earlier versions of these products. The premium edition adds Microsoft SQL Server 2000 and Microsoft Internet Security and Accelerations Server.

Advantages of Microsoft Small Business Server 2003 include:

• Windows 2003 server management and security tools deduct the cost and enhance the dependability of desktop computers by using centralized user policies, rights and configurations.


• SBS exchange 2003 enhances remote and mobile access by supporting a web client that offers a nearly full implementation of the familiar outlook interface, including calendaring and tools. It means that mobile workers can have complete, secure access to email from any internet-connected computer with a standard web browser.


• Windows SBS server 2003 maximizes server uptime and user availability by incorporating powerful fault tolerance aspects, including disk mirroring, cluster configurations, and distributed file system.


• SBS exchange 2003 uses active directory, providing a greatly simplified administration and security model. It makes exchange server monitoring very easy and also offers complete security. Security enhancements include improved safe and block lists and junk email filtering, public folder permission enhancements and attachment in MOOWA (Microsoft Office Outlook Web Access).


• ISA server features ideal support for protecting IIS servers behind the firewall, which have been the largest areas of hacker exploits for windows 2000 environments.