2010年8月12日星期四

How to login Symantec Protection Center?

The first login name is "admin" and password is "admin" .You have to change the password after first login.

2010年8月9日星期一

Hyperv Server 2008 R2 bluescreen...probably CLOCK_WATCHDOG_TIMEOUT

ref: http://social.technet.microsoft.com/Forums/en/windowsserver2008r2virtualization/thread/116a0220-6082-47d7-9bcf-bdde87c3ddf7

See this KB article http://support.microsoft.com/kb/975530 for a hotfix for Intel Nehalem processors.

Open a .VHD File in Windows 7

Virtual Hard Disk (.VHD) files are used by Virtual PC and Virtual Server, and created by Windows Backup when you make a system image backup. If you ever need to access files contained within a .VHD, you can do it using the Disk Management tool built into Windows 7. Just follow these steps:

1. Click Start, right-click Computer, and then click Manage.

2. Expand Storage, and then click Disk Management.

3. Click the Action menu, and then click Attach VHD.

4. Click the Browse button, select your VHD file, and then click OK twice.

5. Open Explorer and access the VHD like a newly created hard disk. It’ll show up as a blue disk in the Disk Management snap-in. For example, mine appeared as the H: drive.

ref: http://www.vistaclues.com/open-a-vhd-file-in-windows-7/

Introduction to Microsoft Exchange Server 2003 - RUS

Purpose of RUS in Exchange Server 2003

RUS works hand in hand with GAL (Global Address List). Together they generate the list of addresses that users see in Outlook. I think of Exchange 2003's RUS as a little engine which runs an LDAP query, the results are to build or update the Users' property sheets and the Address Lists.

Here is a list of the jobs that RUS performs:

  • Updates proxyAddresses attribute controlled by recipient policies.
  • Initializes the homeMDB, homeMTA and msExchHomeServerName attributes. Also the legacyExchangeDN and msExchMailboxGUID if appropriate.
  • Sets the showInAddressBook (or hideDLMembership).
  • Sets the ACL on the Microsoft Exchange System Objects (Check with ADSI Edit)
  • Populates the group called Exchange Enterprise Servers in Active Directory.

Exchange 2003 Server RUS (Recipient Update Service)

RUS interacts with Active Directory. In the above diagram you can see how the Recipient Update Service (CPEXCH) is responsible for rebuilding just the domain address lists. Whereas the (Enterprise Configuration) highlighted in the diagram, is responsible for updating the entire Active Directory Forest.

RUS Timings

Exchange's RUS is only as good as the Active Directory information on the domain controller. While RUS suffers more than most services with latency, to be fair, if the Windows 2003 operating system was constantly checking every attribute of every object in Active Directory, then there would be no time for useful work.

Update Now - Recalculates the Exchange 2003 address list memberships. By default RUS recalculates every 15 minutes, so pressing the button can save you waiting and wondering if it worked.

Rebuild - Starts from scratch, rechecks any new extension for example, changing CPEXCH.NET --> CPEXCH.com. Beware that on a production Exchange 2003 server this could take hours.

Re-home RUS (Recipient Update Service)

The time may come when you have to de-commission the Exchange Server which houses RUS. If you need to move the RUS service to another server, then click on the General tab, next to the Exchange server box and then click Browse. Next, in the Select Exchange Server dialog box, click the name of the new Exchange 2003 Server which will host the Recipient Update Service.

Problem with RUS in a large Forest

I would like to share a bizarre problem with you. When a company created new users, sometimes those people had mailboxes and sometimes not. The heart of the problem was that they were a multi domain organization and one domain had user accounts, but no Exchange 2003 servers. (The other domains all had Exchange 2003 servers). What happened was that when they created users in the domain with no Exchange 2003 they pointed the mailboxes to a different domain.

Now for the solution, launch the Exchange System Manager and create RUS in the domain with no Exchange servers. Strange, but true - it solved the problem of the mailbox enabled users with no email address. For me the magic moment was when a new RUS was born, I had no idea that you could create more Recipient Update Services with Exchange System Manager.


ref: http://www.computerperformance.co.uk/exchange2003/exchange2003_recipient_update_service.htm