Networking Computers - Tip for Windows Networking, Wireless Networking

This post provides Windows Server Support to restore windows time on local computer. It's Applies To: Windows 7, Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2, Windows Server 2008, Windows Server 2008 R2, Windows Vista

Use this procedure to restore the Windows Time service on the local computer to the default settings.

Administrative permit

To perform this procedure on the local computer, you must be a member of the Administrators group. To perform this procedure on a remote computer, you must be a member of the Domain Admins group.

To restore Windows Time service on local computer to default settings

1. Open a Command Prompt.
2. Type the following command and then press ENTER:
net stop w32time
3. Type the following command and then press ENTER:
w32tm /unregister
4. Type the following command and then press ENTER:
w32tm /register
5. Type the following command and then press ENTER:
net start w32time

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).

If the Move Mailbox tool is multithreaded, how many threads can it create at the same time? How many mailboxes can the Mailbox Move tool move at the same time?

Can the Move Mailbox tool move mailboxes between earlier versions of Exchange, or can it only move mailboxes to or from Exchange 2003?

Can a mailbox move operation still be done from Exchange Tasks in Active Directory Users and Computers ?


This section provides exchange 2003 server support for how to use the new functionality of the Move Mailbox tool.

1. In Exchange 2003, start Exchange System Manager, select the mailboxes that you want to move (or select the users in Active Directory Users and Computers), and then click Exchange Tasks.
2. When the Exchange Task Wizard appears, click Move Mailbox , and then click Next.
3. Select the server and the mailbox store that you want to move the mailboxes to, and then click Next.
4. Click the action that you want the Move Mailbox tool to take if corrupted items are encountered during the mailbox move, and then click Next.
5. Select the start time and the finish time for the mailbox move, and then click Next.
6. The mailbox move is now underway. Note that all the selected mailboxes are moved at the same time (the percent of messages that have been moved increases on all the selected mailboxes at the same time).
7. After the mailbox move is complete, Exchange Task Wizard displays a summary of results of the task. If you want to view a detailed report of the Move Mailbox task, click to select the View detailed report when this wizard closes check box, and then click Finish.

Summary In this Server Support tips is used To use Exchange 2003 management tools, the schema must be updated by installing an Exchange 2003 server. Or, if you are using Exchange 2003 ESM or ADUC without having installed an Exchange 2003 server, you need to run Exchange 2003 Setup by using the /forestprep switch. If you do not update the schema, Move Mailbox will not work correctly.

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.