Free Depositfile Gold Account

Depositfiles Gold until 2012-01-11

TO USE THE ACCOUNT FOLLOW THESE TWO STEPS:

1- GO TO LINK : depositfiles.com

2- PUT IN THE FOLLOWING CODE : n5kit65v

3- CLICK ON SEND


Enjoy!!!!!!!!

A REAL HERO FROM Madurai

2010 – உலகின் தலை சிறந்த ஹீரோ ஒரு தமிழன்

திரைப்படங்களை ரசியுங்கள் ரசிகர்களே. அதில் உங்கள் ஹீரோ செய்வதெல்லாம் நிஜம் என்று மட்டும் நம்பி விடவேண்டாம். உண்மையான ஹீரோ உங்கள் பகுதியில் நேர்மையாகவும், தியாக உணர்வோடும் , சேவை மனப்பான்யுடனும் , துணிவுடனும் உழைத்துகொண்டிருப்பார்கள் ஒரு ராணுவ வீரராக , தீயணைப்பு வீரராக, காவல் துறை அதிகாரியாக, ஆசிரியாராக, சமுக சேவகராக, துப்புரவு தொழிலாளியாக மற்றும் நேர்மையாக உழைத்து சம்பாதிக்கும் எவருமாக இருக்கலாம். அவர்களை சந்திக்கும் சமயத்தில் ஒரு நன்றி சொல்வோம் , பாராட்டுவோம். அவர்களில் யாரேனும் கவுன்சிலர் தேர்தலில் நிற்கக்கூடும். நின்றால் காசுக்கு ஆசைபடாமல் ஒட்டு போடுவோம்.



இப்போது அப்படி ஒரு நிஜமான ஹீரோவை உங்களுக்கு இந்த பதிவின் வாயிலாக அறிமுகபடுத்துகிறேன். இவர் உலகப்புகழ் பெற்ற CNN இணையதளத்தில் உலகின் தலை சிறந்த ரியல் ஹீரோக்களில் முதல் பத்தில் ஒருவராக தேர்ந்தெடுக்கப்பட்டு உள்ளார். ஒரு தமிழனாக, மதுரைகாரனாக ரெம்பவும் பெருமை படுகிறேன். இன்னும் வாக்கு பதிவு நடந்து கொண்டிருகிறது. இதில் தேர்ந்தெடுக்கப்படும் ஹீரோக்கள் அமெரிக்காவில் நவம்பர் மாதம் 25 ஆம் தேதியில் Shrine ஆடிடோரியம், Los Angeles இல் நடக்கும் ஒரு பெரும் விழாவில் கௌரவிக்க பட இருக்கிறார்கள். இது CNN தொலைகாட்சியில் இந்திய நேரம் காலை எட்டு மணி ( நமக்கு நவம்பர் 26 ஆம் தேதி ) உலகம் முழுக்க நேரலை ஒளிபரப்பில் காட்டப்பட இருக்கிறது. இதற்காக நாம் ஒவ்வொரு இந்தியனும், தமிழனும் பெருமை பட வேண்டும். ஆஸ்கார் சாதனையை விட இது தான் மகத்தான சாதனை.

பெயர் : நாராயணன் கிருஷ்ணன்
வயது : 29
இருப்பு : மதுரை

அப்படி என்ன செய்து விட்டார்?
அது நினைத்துபார்கவும் முடியாத கருணை செயல்.

தான் யார் என்றே அறியாத சித்த சுவாதீனம் கொண்ட மனிதர்களை நாம் சிறு கருணையுடனும் அல்லது கொஞ்சம் அருவருப்புடனும் கடந்து செல்வோம். சில சமயம் காசு போடுவோம். அதற்கும் மேல் என்ன செய்வோம்? அதை மறக்க முயற்சிப்போம். ஆனால் இவர் அவர்களை தேடி சென்று தினமும் மூன்று வேளை உணவு தருகிறார். அருவருப்பில்லாமல் ஊட்டி விடுகிறார்.கடந்த எட்டு வருடங்களாக ஒரு நாள் தவறாமல் இந்த சேவையை இவர் தொடர்ந்து செய்து வருகிறார். மழை, புயல்,தேர்தல்,கலவரம், பந்த் என்று எதுவும் பாராமல் வருடம் முழுக்க இந்த சேவையை செய்து வருகிறார். தினமும் 400 பேருக்கு மூன்று வேளை உணவு என்பது சாதாரணம் இல்லை. இது வரை ஒரு கோடியே இருபது லட்சம் உணவு பொட்டலங்கள் விநியோகிக்கபட்டுள்ளது.

ஒரு ஐந்து நட்சத்திர ஹோட்டலில் வேலை பார்த்த, விருதுகள் வென்ற செப் சமையல் கலை வல்லுநர் இவர். சுவிட்சர்லாந்தில் ஒரு பெரிய ஹோட்டல் நிறுவனத்தில் வேலை கிடைத்தவுடன் அதை பெற்றோர்களிடம் சொல்லிவிட்டு போவதற்காக மதுரைக்கு வந்தவர் அங்கே ஒரு வயது முதிர்ந்த ஒரு கிழவர் மலத்தை உணவாக உண்ணும் அவலத்தை கண்டு பெரும் அதிர்ச்சிக்குள்ளாகி தனது வெளிநாட்டு வேலையை துறந்து மதுரையிலேயே தங்கி வீட்டில் சமைத்து அதை இது போன்ற மனிதர்களை தேடி சென்று உணவு கொடுக்க ஆரம்பிக்கிறார். இது நடந்தது 2002 . இன்றும் இவரது சேவை தொடர்கிறது மதுரையை சுற்றி நூறு கிலோமீட்டர் பரப்பளவில் கண்ணில் படும் இதுபோன்ற மனிதர்களை தேடிபிடித்து உணவு தருகிறார். இதற்காக இவர் தன்னுடைய வாழ்கையை முழுமையாக அர்பணித்துள்ளார். இவரது அன்னை இவர் குறித்து கவலை பட்டு அழுதபோது, “அம்மா ஒரு நாள் என்னோடு வாங்க. நான் என்ன செய்கிறேன் என்று பாருங்கள் அப்புறம் நீங்கள் சொல்வதை கேட்கிறேன்” என்று சொல்லி அழைத்து போயிருக்கிறார். இவரது சேவையை கண்டு மனம் உருகிய அந்த தாய் ” நீ இவர்களை பார்த்துக்கொள், நான் உள்ளவரை உன்னை பார்த்துகொள்கிறேன்” என்று சொல்லிருக்கிறார். இதை படித்த போது என் கண்களில் நீர் முட்டிக்கொண்டு வந்ததை அடக்க முடியாமல் தவித்தேன். எழுதும் இந்த கணமும் கூட.

நாம் இங்கே நம்மை ஏமாற்றும் திரை நட்சத்திரங்களை ஹீரோ என்று சொல்லி தலையில் வைத்து கொண்டாடுகிறோம். பாலபிசேகம் முதல் முளைப்பாரி வரை எண்ணற்ற பைத்தியகாரத்தனத்தை அந்த ஹீரோக்களுக்காக செய்கிறோம். முதல் நாள் அவர்கள் படங்களை பார்க்க ஆயிரம், இரண்டாயிரம் செலவழிக்க தயங்குவதில்லை. சரி கொடுகிரீர்கள் அந்த அளவுக்கு உரித்தான கலைபடைப்பையாவது அவர்கள் தருகிறார்களா? அவர்கள் என்ன செய்தார்கள். நானும் கொடை செய்கிறேன் என்று சொல்லி சிலவற்றை செய்து பத்திரிகைகளில் மறக்காமல் செய்தி கொடுக்கிறார்கள். அவர்கள் இவரின் கால் தூசுக்கு கூட பொருந்த மாட்டார்கள். இவர் தான் உண்மையான ஹீரோ. சாகசம் செய்வது சாதனை அல்ல. இல்லாதவர்க்கு தேடிசென்று ஈவதே சாதனை. எனக்கு இவர் தான் என்றென்றும் ஹீரோ. இவரை பார்க்கவும், இவருடன் புகைப்படம் எடுத்துகொள்ளவும், இவருடன் ஒரு நாள் இருந்து சிறு உதவியேனும் செய்யவும், பொருள் உதவி செய்யவும், இவரை பற்றி எழுதவும் பேசவும் பெரும் ஆவல் கொள்கிறேன், பெரும் பெருமை கொள்கிறேன் எனது ஹீரோ ஒரு மகத்தானவன் என்பதில்.

அற்றார் அழிபசி தீர்த்தல் அஃதொருவன்
பெற்றான் பொருள்வைப் புழி.

ஏதும் இல்லாதவரின் கடும்பசியைத் தீர்த்து வையுங்கள். பொருளைப் பெற்றவன் சேமித்து வைக்கும் இடம் அதுவே.

ஆதலால் நீங்கள் சேர்த்துவைக்க இடம்

http://www.akshayatrust.org/contact.php

Akshaya’s Helping in H.E.L.P. Trust
9, West 1st Main Street,
Doak Nagar Extension,
Madurai – 625 010. India

Ph: +91(0)452 4353439/2587104
Cell:+91 98433 19933
E mail : ramdost@sancharnet.in

மொக்கையாக எத்தனையோ வோட்டு போட்டுருக்கோம். ஒரு நல்ல விசயத்திற்கும் வோட்டு போடலாம் வாருங்கள். நீங்கள் வோட்டு போடவேண்டிய இடம்

http://heroes.cnn.com/vote.aspx

இதுவரை இந்த பெருமைக்குரிய விஷயம் பத்திரிக்கைகளில் பரவலாக வரவில்லை என்பது பெருத்த வேதனை மட்டுமல்ல ஒரு தமிழனாக நம் எல்லோருக்கும் அவமானம். இதை பதிவர்கள் எல்லோரும் கொண்டு சேர்க்க வேண்டுமாய் தாழ்மையுடன் கேட்டுகொள்கிறேன்

Creating the “God Mode” in windows 7 for tune up

This is nothing more than a special folder or an alternative to the classic Windows Control Panel. Here’s a step-by-step guide on setting it up:

1. Right-click on your desktop, and select “New/Folder”.
2. Enter the folder name “God Mode.{ED7BA470-8E54-465E-825C-99712043E01C}”. Tip: You can give it any name you want, but the important part is the latter string of letters and numbers. For example, you could call it “Special Control Panel.{ED7BA470-8E54-465E-825C-99712043E01C}”.
   
   Once you hit enter, the icon changes, and you will have the direct shortcut to your “God Mode” (or whatever you previously called it).
   
3. Double-click on the icon to see all of the Windows features and settings in one single place.
4. One suggestion: go through the list to find out how many features and settings you can actually change, activate, or deactivate with this special mode. You will be amazed at the number of hidden secrets that are suddenly revealed.
5. If you try to find a specific setting, use the quick search bar in the upper right corner.
6. Here’s a neat trick—drag your “God Mode” to the taskbar. This will let you access the function right from it. To do so, right-click on the icon, and select “God Mode”.
   
   You can also drag it to your “Favorites” in Windows Explorer and complete the same action as with the taskbar.

   

The top ten hidden secrets

It is very easy to access hidden settings with “God Mode”. Below is a list of our favorite features discovered using this function under Windows 7.

1. Diagnose your computer’s memory problems (“Administrative Tools”). This launches the built-in memory check tool, and is very useful if you encounter random blue screens or other memory-related error messages.
2. View reliability history (“Action Center”). Use this feature to see a track record of how stable your computer has been and how many problems have occurred.
3. Make a file type always open in a specific program (“Default programs”). If you have many programs, such as several photo-editing or video-editing tools, this can be helpful.
4. Calibrate display color (“Display”). As the name implies, you can find a pretty useful monitor calibration utility here.
5. Show hidden files or folders (“Folder options”). This is something that consumers need on a daily basis.
6. Manage Wireless Networks (“Network and Sharing Center”). If you’re having trouble connecting to a Wi-Fi network that you have connected to before, use this setting to delete the Wi-Fi network and reconnect to it.
7. Use tools to improve performance (“Performance Information and Tools”). In this window, you will find information about your PC’s performance. On the left hand side, you’ll find a couple of recommended tools for boosting your machine’s speed a bit.
8. Lock the computer when I leave it alone for a period of time (“Personalization”). Set up a screensaver, and check “On resume, display logon screen”.
   
9. Change what closing the lid does (“Power Options”). If you don’t want your laptop to go to sleep once you close the lid, use this setting to change this behavior.
10. View installed updates (“Programs and features”). Have you installed a Windows or software update and experienced problems with your machine? Use this entry to uninstall the update and restore your system.

Hopefully, over time, this post will have helped you save hundreds of unnecessary clicks through the Windows Control Panel. Any additional hidden secrets you’d like to share? leave your comments here...

Domain Rename – Rename a Windows 2003 Forest

Before we are discussing the necessary steps for domain rename, you must ensure that you have a functioning and current Backup of your Active Directory infrastructure and Exchange and that you have a tested recovery plan in mind if domain rename fails.

In our example we have a Windows 2003 domain named msexchange.org. Msexchange.org has the Windows Server 2003 forest functional level with Exchange 2003 SP1 installed. Due an merger we would like to rename the domain to Msexchange.com.

DOWNLOAD IN DOC FORMAT

Why a Domain Rename?

There are several reasons why a domain rename is necessary. Some examples:

• Fear of making irreversible decisions about domain names and forest structure
• Delay any deployment while striving for “perfect” forest structure and domain names
• Changes in geography
• DNS structure change
• Unforeseen business dynamics necessitating domain name changes
• Company merger or acquisition
• Business unit reorganization

Supported Operations

The following operations are supported by RENDOM

• Rename the DNS name of a domain
• Rename the NetBIOS name of a domain
• Restructure a domain
• Move any non-root domain under a new parent domain in the same forest
• Move any non-root domain to a new tree in the same forest
• Simple rename without repositioning any domains in the forest structure
• Create a new domain-tree structure by repositioning domains within a tree
• Create new trees

Figure 1: An example of the domain rename process

Limitations

No good product without limitations and drawbacks. It is not possible to do all renaming operations with RENDOM. The following limitations exist:

• The forest root domain is the root of one of these trees
• Forest must be well formed after the domain rename operation
• The DNS names of the domains comprising the forest form one or more trees
• Cannot have a domain whose domain name is subordinate to the domain name of an Application Directory Partition root
• The forest root domain can be renamed, but must remain the forest root

Requirements for domain rename

• Windows Server 2003 forest functional level
• Account must be a member of the Enterprise Administrators group
• A single computer running any edition of Windows Server 2003 that is to be used as the control station during a domain rename operation
• Latest domain rename tools published at the domain rename Web site: http://go.microsoft.com/fwlink/?LinkId=5585
• DFS root servers running a minimum of Windows 2000 SP3 or later

Error Message of RENDOM when the Forest functional level is not Windows 2003

Figure 2: RENDOM error message because of wrong functional level

The domain rename Tool

Rendom.exe is the command-line utility for renaming domains in Windows Server 2003 forests. Rendom is used to carry out the multiple steps in the domain rename procedure. You precede the domain rename process by using Rendom to prepare a list of domains in the forest. You begin the domain rename process by using Rendom to generate a script (Forest description file) that contains the instructions for renaming domains in the forest. You use Rendom again to verify that all DCs are adequately prepared (RENDOM /PREPARE) to make the necessary updates to rename the domains. Finally, you use Rendom to execute (RENDOM /EXECUTE) the actual domain rename instructions on every DC. Following the domain rename procedure, you use Rendom to remove all metadata written to the directory by the domain rename operation.

You can download the domain rename Tools here: http://www.microsoft.com/windowsserver2003/downloads/domainrename.mspx

Attention:
The RENDOM.EXE tool from the web doesn’t work with Exchange installed. Use the version from the Windows 2003 CD. An updated version of RENDOM.EXE is suspected in the future.

The installation of RENDOM is simple.

Doubleclick DOMAINRENAME.EXE. The process extracts two files:

• RENDOM.EXE
• GPFIXUP.EXE

Rendom has several command line switches:

Figure 3: RENDOM command line switches

The Domain Rename State File

As a result of the first command (RENDOM /LIST) you issue to begin the domain rename process, Rendom creates an XML file called the state file, which contains the list of all DCs in the forest. As DCs progress through the various steps in the procedure, Rendom updates the state file to track the state of each DC relative to the completion of the domain rename process.

As you perform each step in the domain rename operation, Rendom automatically updates the state file. By monitoring the states of completion of each DC in the state file, you receive the information you need to issue the next Rendom command in the sequence. You can edit the state file to temporary exclude some DC for domain renaming procedure.

Current Domain Names — Generating the Forest Description File

The RENDOM /LIST command generates the current forest description and writes it to an output file (DOMAINLIST.XML) using an XML-encoded structure. This file contains a list of all domains and application directory partitions in the forest, along with the corresponding DNS and NetBIOS names.

Each domain and application directory partition is also identified by a globally unique identifier (GUID), which does not change with domain rename. To simplify specifying the new forest structure, Rendom gathers and compiles the current forest structure automatically such that the new forest structure can be overlaid on top of it.

Figure 4: DOMAINLIST.XML – Forest description file

Simply replace the old ForestDNSZones and DomainDNSZones names with the new domain name. You can (but not must) change the NetBIOSName. For large organizations I recommend to use the search and replace function of your editor.

GPFIXUP

When the DNS name of a domain changes, any references to Group Policy Objects (GPOs) within the renamed domain through Group Policy links (the gpLink attribute) on sites, domains, and organizational units is rendered invalid because they are based on the old domain name. Furthermore, the optional attribute gpcFileSysPath on a GPO that holds a uniform naming convention (UNC) path to a Group Policy templates folder located in the sysvol volume of the renamed domain will also be rendered invalid because the path uses the old domain DNS name. To correct the severed Group Policy links and the invalid UNC paths in GPOs within the renamed domain, you can use the Group Policy fix-up tool gpfixup.exe to refresh the Group Policy links and the UNC paths in GPOs based on the new domain name.

The Group Policy fix-up tool should be run once for every renamed domain soon after the actual domain rename operation has been completed and before another domain rename operation is performed.

The fix-up tool gpfixup refreshes all intradomain GPO references/links (that is, where the link and the target GPO are within the same domain) in the renamed domain. However, cross-domain references to GPOs in the renamed domain, where the link is in a different domain from the domain containing the GPO, will not be automatically rebuilt by this tool. For them to work, these cross-domain links will need to be repaired manually by deleting the old Group Policy links and re-establishing new links.

Figure 5: GPFIXUP command line switches

Preparatory Steps

It is not possible to explain every preparatory Step. For a detailed description see the domain rename Whitepaper.

• Verify application and service compatibility
• Verify domain controller and replication health (Keyword: REPADMIN, DCDIAG, REPLMON)
• Prepare trusts (Keyword: Create trusts as necassary)
• Prepare DNS zones Publishing (Keyword: Two Sets of Locator SRV Resource Records in DNS)
• Prepare domain-based DFS paths (Keyword: DFS RootTarget)
• Prepare PKI (Keyword: CDP und AIA)
• Prepare member computers for host name changes
• Communicate with the user base (Keyword: inform every user before and after domain rename)

WARNING:
Rendom.exe tool versions before version 1.2 did not detect Exchange 2000 and incorrectly permitted domain rename operations. The actual version as I wrote this article was version 1.3.

The RENDOM.EXE tool from the web doesn’t work with Exchange installed. Use the version from the Windows 2003 CD. An updated version of RENDOM.EXE is suspected in the future.

Procedures of the Original Windows Server 2003 domain rename tool

Step	Description
Step 1	Back up all domain controllers
Step 2	Set up the control station
Step 3	Generate the current forest description (rendom /list)
Step 4	Specify the new forest description
Step 5	Generate domain rename instructions (rendom /upload)
Step 6	Push domain rename instructions to all domain controllers and verify DNS
Step 7	Verify readiness of domain controllers (rendom /prepare)
Step 8	Execute domain rename instructions (rendom /execute)
Step 9	Unfreeze the forest configuration
Step 10	Re-establish external trusts
Step 11	Fix Distributed file system (Dfs) topology
Step 12	Fix group policy objects and links (gpfixup.exe)
After the domain rename procedure	Verify certificate security after domain rename Miscellaneous tasks Back up domain controllers Restart member computers New: Verify the Exchange rename New: If applicable, update Active Directory Connector (ADC) Attribute clean up after domain rename Rename domain controllers (optional) New: Domain Controller Rename Follow-Up Steps

Source: Exchange Domain Rename Fix-up.doc with a few modifications

Important: To use this step by step Guide to rename Windows 2003 domains with Exchange 2003 installed, see the step by step guide later in this article.

RENDOM steps

Figure 6: Required RENDOM switches

Post Rename operations

• Enable old certificates and smart cards
• Enable and verify certificate security
• Back up domain controllers
• Communicate with user base
• Restart member computers (ALL)
• Rename domain controllers (optional)
• Clean up domain rename metadata (RENDOM /CLEAN)

Legacy Clients

If your environment consists of NT4 Clients, you have to unjoin and rejoin every client from the domain because it is not possible with NT4 to automatically reflect the renamed domain.

Language Support

The domain rename tools can be used on all language versions of Windows Server 2003. There are no language-specific versions of the tools.

XDR-fixup

Exchange Domain Rename Fix-Up (XDR-fixup.exe) fixes Exchange attributes after you rename a domain that contains Exchange 2003 servers. XDR-fixup is available as part of the Exchange 2003 Web Tools as a separate Download. Point your browser to http://www.microsoft.com/exchange/downloads/2003.asp.

XDR-fixup is not a replacement of the Windows 2003 domain rename tools. The Windows Server 2003 domain rename tools were originally designed for renaming domains in Microsoft Active Directory directory service forests that do NOT contain Exchange 2000 or Exchange 5.5 servers. This limitation was because of renaming a domain affects several Exchange attributes, and there was no method for fixing these attributes. Microsoft Exchange Server 2003, however, is compatible with the Exchange Domain Rename Fix-Up tool (XDR-fixup.exe), which fixes Exchange attributes after a domain rename.

Domain rename is not supported in forests that contain Exchange 2000 or Exchange 5.5.

The installation of XDR-fixup is simple. Only doubleclick the installation file and follow the instructions:

Figure 7: XDR-fixup setup

Running the XDR-fixup tool is an additional step required for doing a domain rename operation. XDR-fixup modifies Exchange Active Directory attributes to reflect the new domain name.

The XDR-fixup tool does not replace the Windows Server 2003 domain rename tools, nor does it extend the functionality of the domain rename tools. You must run XDR-fixup.exe every time you run RENDOM /EXECUTE.

What does XDR-fixup NOT do?

Domain rename does not rename e-mail domains

Domain rename doesn’t change any e-mail domain in Exchange doesn’t change any recipient policy. You must change your recipient policy after domain rename.

Domain rename does not rename the Exchange Organization

You cannot rename the Exchange Organization with the domain rename tool.

Domain rename does not merge Exchange Organizations

It is not possible with domain rename to merge two Exchange organizations into a single Exchange organization.

Prerequisites

XDR-fixup has the following requirements:

Windows Server 2003 is required
All domain controllers must be running Windows Server 2003, and the Active Directory functional level must be at the Windows Server 2003

Administrative privileges
The domain rename procedure requires enterprise administrative privileges to perform the steps in the procedure. The account you use must also have Full Exchange Administrator permissions.

Exchange 2003 is required
The domain rename tools are supported in Exchange 2003; all Exchange servers in the organization must be running Exchange 2003.

Exchange 2000 and Exchange 5.5 are not supported
The rendom.exe and XDR-fixup.exe tools are not supported in Exchange 2000 or Exchange 5.5. If the rendom.exe tool detects Exchange 2000 servers, the tool will not proceed. However, the tool will not detect whether Exchange 5.5 servers exist; do not attempt the operation if a domain contains Exchange 5.5 servers. If any SRS instance is running in the forest, you must remove it before the domain rename process begins.

Exchange must not be installed on domain controllers
To use the domain rename operation, Exchange must not be installed on any domain controllers (if Exchange is loaded on a DC deinstal Exchange from it)

How to Use XDR-fixup

XDR-fixup has several command line switches:

Figure 8: XDR-fixup command line switches

XDR-fixup installs all executables into the following directory: \Program files\Exchsrvr\Exchange Domain Rename Tools.

XDR-fixup integrates into the normal Windows 2003 domain rename steps with three additional steps:

I will call the first Step Step 0

The two steps between Step 8 and Step 9 are important for Exchange 2003 rename.

Domain rename steps with the new Exchange-related steps inserted

Step	Description
Step 0	Preliminary Steps: Move Exchange off of domain controllers Discontinue Exchange Configuration Changes
Step 1	Back up all domain controllers
Step 2	Set up the control station
Step 3	Generate the current forest description (rendom /list)
Step 4	Specify the new forest description (save the original XML file as domainlist-save.xml)
Step 5	Generate domain rename instructions (rendom /upload)
Step 6	Push domain rename instructions to all domain controllers and verify DNS Create new DNS zones and settings with secure dynamic DNS updates
Step 7	Verify readiness of domain controllers (rendom /prepare)
Step 8	Execute domain rename instructions (rendom /execute) DC REBOOTS
-- New --	Update the Exchange configuration (run XDR-fixup)
-- New --	Restart all Exchange servers and Exchange System Manager clients twice
Step 9	Unfreeze the forest configuration
Step 10	Re-establish external trusts
Step 11	Fix Distributed file system (Dfs) topology
Step 12	Fix group policy objects and links (gpfixup.exe)
After the domain rename procedure	Verify certificate security after domain rename Miscellaneous tasks Back up domain controllers Restart member computers New: Verify the Exchange rename New: If applicable, update Active Directory Connector (ADC) Attribute clean up after domain rename Rename domain controllers (optional) New: Domain Controller Rename Follow-Up Steps

Source: Exchange Domain Rename Fix-up.doc with a few modifications

It is not possible to explain every step in detail for this article. I will write a few lines to some step. For detailed information see the corresponding Whitepaper.

Step 0
This should be clear to understand. Remove Exchange from every DC

Step 1
Back up all domain controllers to ensure that a failback in case of emergency is possible

Step 2
Set up the control station. The control station must be a Member of the domain and a Windows 2003 Server. You have to install the Windows Server 2003 support tools and the ADMINPAK.MSI. “Install the RENDOM tool and the XDR-fixup on the control station.

Step 3
Generate the current forest description (rendom /list)

Step 4
Specify the new forest description. To do so edit the file and change the names to reflect the new domain name

Step 5
Generate domain rename instructions (rendom/upload)

Step 6
Push domain rename instructions to all domain controllers and verify DNS (rendom uses a special RPC which it sends to every DC)

Step 7
Verify readiness of domain controllers (rendom /prepare)

Step 8
Execute domain rename instructions (rendom /execute)

-- New --
Update the Exchange configuration (run XDR-fixup)

-- New --
Restart all Exchange servers and Exchange System Manager clients twice

Step 9
Unfreeze the forest configuration

Step 10
Re-establish external trusts. You must re-astablish every external trusts because it doesn’t reflect the NETBIOS name changes. The interdomain trust will be automatically fixed.

Step 11
Fix Distributed file system (Dfs) topology. You must use DFSUTIL to reference to the new domain name

Step 12
Fix group policy objects and links (gpfixup.exe). GPFIXUP fixes GPO references to the renamed domain name.

To run the XDR-fixup tool (between Steps 8 and 9 of the domain rename procedure), perform the following steps:

Wait for ALL domain controllers to reboot and replication to complete.

Run the following command:

XDR-fixup /s:DOMAINLIST-SAVE.XML /e:DOMAINLIST.XML /trace:TRACEFILE /changes:CHANGESCRIPT.LDF /restore:RESTORESCRIPT.LDF

Note: This step must be run only once per forest

Figure 9: XDR-fixup

Attention: Be sure that you specify the right credentials in the XDR-FIXUP command because the NETBIOS domain name might be changed. You can also specify the credentials in UPN format (username@domain.tld).

After the XDR-fixup command has run, log off the control station computer and immediately

Logon again.

Run the following command: LDIFDE –i –f CHANGESCRIPT.LDF

Restart ALL Exchange Servers

Verify successful Exchange Rename

Update Active Directory Connectors when you use the ADC for Interorganizsational restructuring (Please keep in mind that XDR-Fixup is not supported for Exchange 2000 / 5.5 – so when you use ADC for Exchange 5.5 migrations).

You have successfully renamed Windows 2003 and patched Exchange 2003. This article ends here. In a real life environment you have to fix a lot more components like …

• Back up domain controllers
• Restart ALL member computers
• After the domain rename procedure verify certificate security after domain rename. You must prepare the URLs for CDP and AIA Extensions after Domain Rename
• Verify sucessful Exchange rename (update recipient policy and more)
• Update Active Directory Connector (ADC) you use it for interdomain synchronization
• Attribute clean up after domain rename
• Rename domain controllers (optional)
• Prepare legacy clients (domain rejoin of all NT4 clients)

Add "Take Ownership" to Explorer Right-Click Menu in Win 7

Taking ownership of system files or folders in Windows 7 or Vista is not a simple task. Whether you use the GUI or the command line, it takes far too many steps.

Thankfully somebody created a registry hack that will give you a menu item for “Take Ownership” that will handle all the steps for you. (If you are the person that originally made this script, let me know and I’ll give you credit)

Here’s what the new right-click menu will look like after installing this registry hack.

Install

Download and unzip the files contained in the zipfile. Double-click the InstallTakeOwnership.reg file and click through the prompts. No reboot necessary.

Uninstall

Double-click the RemoveTakeOwnership.reg file and click through the prompts. No reboot necessary.

Download TakeOwnership.zip

Universal USB Installer - Bootable Creator

Universal USB Installer is a Live Linux USB Creatorthat allows you to choose from a selection of Linux Distributions to put on your USB Flash Drive. The Universal USB Installer is easy to use. Simply choose a Live Linux Distribution, the ISO file, your Flash Drive and, Click Install. Other features include; Persistence (if available), and the ability to format the flash drive (recommended) to ensure a clean install. Upon completion, you should have a ready to run bootable USB Flash Drive with your select Linux version installed.

Universal USB Installer Screenshot

Download Universal USB Installer

Universal-USB-Installer-1.8.0.5.exe – October 11, 2010 – Changes

Updated to include Ubuntu 10.10 Netbook Remix, Lubuntu 10.10, Ubuntu – Xubuntu – Kubuntu amd64, and Server Install versions.

USB Flash Drive Creation Prerequisites:

• Universal-USB-Installer-1.8.0.5.exe
• Windows XP/Vista/7 to create the USB (Win 98/2K WILL NOT Work!)
  
• Fat32 Formatted Flash Drive
• PC with a BIOS that can boot from USB
• Your Favorite Linux ISO

Currently USB Installable Live Linux Distributions

• Ubuntu 9.04/9.10/10.04.1/10.10 Desktop i386/amd64 – Site
• Kubuntu 9.04/9.10/10.04.1/10.10 Desktop i386/amd64 – Site
• Xubuntu 9.04/9.10/10.04/10.10 Desktop i386/amd64 – Site
• Lubuntu 10.04/10.10 Site
• Ubuntu NetBook Remix 10.04/10.10 – Site
• Ubuntu Rescue Remix Revision 1 – Site
• Ubuntu Server 9.10/10.04/10.10 32bit/64bit Installer – Site
• Ubuntu Mini Remix 10.04 – Site
• Sugar on a Stick – Site
• Arch Linux – Site
• XBMC – Site
• ZenWalk Live – Site
• PCLinuxOS MiniMe – Site
• TinyCore 3 – Site
• CentOS 5 – Site
• Fedora 13 – Site
• Redo Backup and Recovery 0.9.5 – Site
• Runt Linux 5.0 – Site
• Feather Linux 0.7.5 – Site
• Debian Live 5.0.5 – Site
• Peppermint Linux OS – Site
• GParted 0.6.1-2 – Site
• PartedMagic 5.1 – Site
• EasyPeasy 1.6 (NetBook Distro) – Site
• KNOPPIX V6.2.1 – Site
• DBAN 2.2.6 (Hard Disk Nuker) – Site
• RIP Linux 10.x – Site
• Dr.Web Live CD Scanner 5.03 – Site
• Lucid Puppy 5.0.1 – Site
• BackTrack 3 and 4 – Site
• YlmF OS V3.0 – Site
• Linux Mint 9 – Site
• Crunchbang 9.04 – Site
• gOS 3.1 gadgets – Site
• Ultimate Boot CD – Site
• Gentoo 10.1 – Site
• xPUD 0.9.2 – Site
• Simply MEPIS 8.0.15 – Site
• EEEBuntu 3.0 (Netbook Distro) – Site
• DSL (Damn Small Linux) 4.4.9 – Site
• Puppy Linux – Site
• Puppy Arcade 8 (Console Game Emulator) – Site
• Kiwi Linux 9.04 – Site
• SLAX 6.1.2 – Site
• SliTaZ – Site
• Ophcrack XP – Site
• Clonezilla – Site
• Jolicloud (NetBook Distro) – Site
• Dynebolic 2.5.2 DHORUBA – Site
• PLoP Linux 4.0.5 (a minimalist Linux Rescue System) – Site
• System Rescue CD 1.5.4 (another Linux Rescue System) – Site

More Live Linux Distributions will be added as time permits. Feel free to contact us to submit recommendations.

A Linux based version of this tool is in the works for those Die Hard Linux users who prefer not to use Windows. For now, you can visit the "How to install Linux from a Linux CD" section for individual tutorials.

Notes: If you run Universal USB Installer from the same directory containing an installable ISO, the script will autodetect the ISO and bypass step 2 once the proper Distro has been selected.

This tool does not support installing and booting from multiple Linux Distributions. Only One Distribution can be installed at any given point in time. However, we do offer a MultibootISOs USB Creator for this purpose.

Boot from USB without BIOS Support via PLoP CD

Boot from USB without BIOS Support

In the following tutorial, we explain how to create a PLoP Boot Manager CD that can be used to boot from your USB Flash Drive. This is useful for computers that do not support booting from USB in BIOS. The PLoP Boot Manager created by Elmar Hanlhofer, works by first loading essential USB drivers, CD/DVD drivers, and Hard Disk Drivers. The user is then presented with a (Boot Menu) menu of possible boot devices detected by PLoP. The user can then proceed to select a device to try and boot from.

PLoP Boot Manager (Boot Menu)

Distribution Home Page: PLoP Boot Manager

How to Create a PLoP Boot Manager CD

1. Download PLoP Boot manager, and extract the files from the Zip to your Desktop
2. Burn the plpbt.iso to a CD using your favorite CD/DVD burning software
3. Insert your Newly created PLoP Boot CD and your pre-prepared Linux USB Flash Drive
4. Reboot your PC and set your System BIOS to boot from the CD

If all goes as planned, you should now be presented with an alternate Boot Manager similar to the one pictured above that can be used to boot your USB Flash Drive or other device.

Enjoy!!!!