Followers

Windows RUN Commands

Windows logo key + R


Add/Remove Programs = appwiz.cpl
Administrative Tools = control admintools
Authorization Manager= azman.msc "New"

Calculator = calc
Certificate Manager = certmgr.msc
Character Map = charmap
Check Disk Utility = chkdsk
Control Panel = control "New"
Command Prompt = cmd.exe
Component Services = dcomcnfg
Computer Management = compmgmt.msc = CompMgmtLauncher "New"

Date and Time Properties = timedate.cpl
Downloads = Downloads "New"
Device Manager = devmgmt.msc
Direct X Troubleshooter = dxdiag
Disk Cleanup Utility = cleanmgr
Defragment User Interface = dfrgui "New"
Ditilizer Calibration Tool = tabcal "New"
Disk Management = diskmgmt.msc
Disk Parmelonion Manager = diskpart
Display Properties = control desktop or desk.cpl
DPI Scaling = dpiscaling "New"
Driver Package Installer = dpinst "New"
Driver Verifier Utility = verifier or /reset
DVD Player = dvdplay "New"

Encryption File System = rekeywiz "New"
Event Viewer = eventvwr.msc

Fax Cover Sheet Editor = fxscover "New"
File Signature Verification Tool = sigverif
Folders Properties = control folders
Fonts = control fonts
Free Cell Card Game = freecell

Group Policy Editor = gpedit.msc

Internet Explorer = iexplore
Iexpress Wizard = iexpress
Internet Properties = inetcpl.cpl
IP Configuration = ipconfig.exe
iSCSI Initiator = iscsicpl "New"

Keyboard Properties = control keyboard

Libraries = explorer or Windows key + E
Local Security Settings = secpol.msc
Local Users and Groups = lusrmgr.msc
Logs You Out Of Windows = logoff

Microsoft Support Diagnostic Tool = msdt "New"
Microsoft Paint = mspaint.exe
Mouse Properties = control mouse
Mouse Properties = main.cpl
Mobility Center (only on mobile) = mblctr or Windows key + X
Network Connections = control netconnections
Network Connections = ncpa.cpl
Notepad = notepad

ODBC Data Source Administrator = odbcad32 "New"
Optional Features Manager = optionalfeatures "New"
On Screen Keyboard = osk or Windows key + U

Performance Monitor = perfmon.msc
Phone and Modem Options = telephon.cpl
Power Configuration = powercfg.cpl
Printers and Faxes = control printers
Printer Migration = PrintBrmUi "New"
Private Character Editor = eudcedit

Regional Settings = intl.cpl
Registry Editor = regedit.exe
Remote Assistance = msra "New"
Remote Desktop = mstsc
Resultant Set of Policy = rsop.msc

Scheduled Tasks = control schedtasks
Security Center = wscui.cpl
Services = services.msc
Shared Folders/MMC = fsmgmt.msc
Shuts Down Windows = shutdown
Snipping Tool = snippingtool "New"
Sounds and Audio = mmsys.cpl
Sound Recorder = soundrecorder "New"
Sound Volume = sndvol "New"
Spider Solitare Card Game = spider
SQL Client Configuration = cliconfg
Stored User Names and Passwords = credwiz "New"
Sticky Note = StikyNot "New"
System Configuration Editor = sysedit
System Configuration Utility = msconfig
System File Checker Utility = sfc
System Information = msinfo32
System Properties = sysdm.cpl or Windows key + Pause/Break

Task Manager = taskmgr
Trusted Platform Module = TpmInit "New"

Utility Manager = utilman
User Accounts = netplwiz or control userpasswords2

Windows Activation = slui "New"
Windows Backup Utility = sdclt "New"
Windows Fax and Scan = wfs "New"
Windows Firewall = firewall.cpl
Windows Firewall with Advanced Security = wf.msc "New"
Windows Image Acquisition = wiaacmgr "New"
Windows Media Player = wmplayer
Windows Magnifier = magnify
Windows Management Infrastructure = wmimgmt.msc
Windows Update App Manager = wuapp "New"
Windows Standalong Update Manager = wusa "New'
Windows System Security Tool = syskey
Windows Share Creation Wizard = shrpubw "New"
Wordpad = write
Published By
S.G.Godwin Dinesh.MCA
Sr.System Administrator



Active Directory & Windows Networking Commands




Tips for Every Admin Should Know - System Administrator 

Active Directory
1. To quickly list all the groups in your domain, with members, run this command:
dsquery group -limit 0 | dsget group -members –expand
2. To find all users whose accounts are set to have a non-expiring password, run this command:
   dsquery * domainroot -filter “(&(objectcategory=person)(objectclass=user)(lockoutTime=*))” -limit 0
3. To list all the FSMO role holders in your forest, run this command:
netdom query fsmo
4. To refresh group policy settings, run this command:
gpupdate
5. To check Active Directory replication on a domain controller, run this command:
repadmin /replsummary
6. To force replication from a domain controller without having to go through to Active
Directory Sites and Services, run this command:
repadmin /syncall
7. To see what server authenticated you (or if you logged on with cached credentials) you can run either of these commands:
set l
echo %logonserver%
8. To see what account you are logged on as, run this command:
whoami
9. To see what security groups you belong to, run this command:
whoami /groups
10. To see the domain account policy (password requirements, lockout thresholds, etc) run this command:
net accounts
Windows Networking
11. To quickly reset your NIC back to DHCP with no manual settings, run this command:
netsh int ip reset all
12. To quickly generate a text summary of your system, run this command:
systeminfo | more
13. To see all network connections your client has open, run this command:
net use
14. To see your routing table, run either of these commands:
route print
netstat -r
15. Need to run a trace, but don’t have Netmon or Wireshark, and aren’t allowed to install either one? Run this command:
netsh trace start capture=yes tracefile=c:\capture.etl
netsh trace stop
16. To quickly open a port on the firewall, run this command, changing the name, protocol, and port to suit. This example opens syslog:
netsh firewall set portopening udp 161 syslog enable all
17. To add an entry to your routing table that will be permanent, run the route add command with the –p option. Omitting that, the entry will be lost at next reboot:
route add 0.0.0.0 mask 0.0.0.0 172.16.250.5 –p
18. Here’s a simple way to see all open network connections, refreshing every second:
netstat –ano 1
19. You can add a | findstr value to watch for only a specific connection, like a client ip.addr or port:
netstat –ano | findstr 216.134.217.20
20. You can use the shutdown to shutdown or reboot a machine, including your own, in a simple scheduled task like this:
shutdown –r –t 0 –m \\localhost
21. To make planned DNS changes go faster, reduce the TTL on the DNS records you plan on changing to 30 seconds the day before changes are to be made. You can set the TTL back to normal after you confirm the changes have been successful.
22. Set a short lease on DHCP scopes that service laptops, and set Microsoft Option 002 to release a DHCP leas on shutdown. This helps to ensure your scope is not exhausted and that machines can easily get on another network when the move to a new site.
Windows 7
23. Want to enable the local administrator account on Windows 7? Run this command from an administrative command prompt. It will prompt you to set a password:
net user administrator * /active:yes
24. You can do the same thing during install by pressing SHIFT-F10 at the screen where you set your initial user password.
Windows 7 supports several useful new keyboard shortcuts:
25. Windows Key+G
Display gadgets in front of other windows.
26. Windows Key++ (plus key)
Zoom in, where appropriate.
27. Windows Key+- (minus key)
Zoom out, where appropriate.
28. Windows Key+Up Arrow
Maximize the current window.
29. Windows Key+Down Arrow
Minimize the current window.
30. Windows Key+Left Arrow
Snap to the left hand side of the screen
31. Windows Key+Right Arrow
Snap to the right hand side of the screen.
32. To quickly launch an application as an administrator (without the right-click, run as administrator), type the name in the Search programs and files field, and then press Ctrl-Shift-Enter.
Here are some tips that can save you from buying commercial software:
33. Need to make a quick screencast to show someone how to do something? The Problem Steps Recorder can create an MHTML file that shows what you have done by creating a screen capture each time you take an action. Click the Start button and type ‘psr’ to open the Problem Steps Recorder.
34. Need to burn a disc? The isoburn.exe can burn ISO and IMG files. You can right click a file and select burn, or launch it from the command line.
35. Windows 7 includes a screen scraping tool called the Snipping Tool. I have tons of users request a license for SnagIt, only to find this free tool (it’s under Accessories) does what they need.
36. You can download this bootable security scanner from Microsoft that will run off a USB key, which is very useful if you suspect a machine has a virus.
37. A great way to save all your command line tools and make them available across all your computers is to install Dropbox, create a folder to save all your scripts and tools, and add that folder to your path. That way, they can be called from the command line or any other scripts, and if you update a script, it will carry across to any other machine you have.
Windows 2008
38. You can free up disk space on your servers by disabling hibernate. Windows 2008 will create a hiberfil.sys equal to the amount of RAM. This is very useful with VMs that have lots of RAM but smaller C: drives. To disable hibernation, and reclaim that space, run this command:
powercfg -h off
39. You can get to the complete collection of Sysinternals tools online. You can even invoke them from the run command. Use the url: http://live.sysinternals.com or the UNC path: \\live.sysinternals.com\tools.
40. Speaking of the Sysinternals tools, almost any command line in this article can be run remotely on another machine (as long as you have administrative rights) using the psexec command included in the Sysinternals tools.
41. You can kill RDP sessions at the command line when you find that all the RDP sessions to a server are tied up.
regsvr32 query.dll [enter] You only have to do this the first time.
query session /server:servername [enter]
reset session # /server:servername [enter]
42. You can create a list of files and display the last time they were accessed, which is very useful when a network drive is low on space and users swear they have to have that copy of Office 2003 on the network. My advice? If they haven’t touched it in two years, burn it to DVD or write it to tape and then delete it from disk:
dir /t:a /s /od >> list.txt [enter]
43. The Microsoft Exchange Err command is one of the best all around troubleshooting tools you will find, as it can decode any hex error code you find as long as the products are installed on the machine. Download it from here.
44. You can see all the open files on a system by running this command:
openfiles /query
45. You can pull all the readable data out of a corrupt file using this command:
recover filename.ext
46. Need to pause a batch file for a period of time but don’t have the sleep command from the old resource kit handy? Here’s how to build a ten second delay into a script:
ping -n 10 127.0.0.1 > NUL 2>&1
47. If your Windows website has stopped responding, or is throwing a 500 error, and you are not sure what to do, you can reset IIS without having to reboot the whole server. Run this command:
iisreset
48. You can use && to string multiple commands together; they will run sequentially.
49. If you find yourself restarting services frequently, you can use that && trick to create a batch file called restart.cmd and use it to restart services:
net stop %1 && net start %1
50. You can download a Windows port of the wget tool from here, and use it to mirror websites using this command:
wget -mk http://www.example.com/
Linux
51. You can list files sorted by size using this command:
ls –lSr
52. You can view the amount of free disk space in usable format using this command:
df –h
53. To see how much space /some/dir is consuming:
du -sh /some/dir
54. List all running processes containing the string stuff:
ps aux | grep stuff
55. If you have ever run a command but forgot to sudo, you can use this to rerun the command:
sudo !!
56. If you put a space before a command or response, it will be omitted from the shell history.
57. If you really liked a long command that you just ran, and want to save it as a script, use this trick:
echo “!!” > script.sh
Published By
S.G.Godwin Dinesh.MCA
Sr.System Administrator

How to view minidump files in windows 7

BlueScreenView scans all your minidump files created during 'blue screen of death' crashes, and displays the information about all crashes in one table. For each crash, BlueScreenView displays the minidump filename, the date/time of the crash, the basic crash information displayed in the blue screen (Bug Check Code and 4 parameters), and the details of the driver or module that possibly caused the crash (filename, product name, file description, and file version).
For each crash displayed in the upper pane, you can view the details of the device drivers loaded during the crash in the lower pane. BlueScreenView also mark the drivers that their addresses found in the crash stack, so you can easily locate the suspected drivers that possibly caused the crash.
Download links are on the bottom of this page

Crashes Information Columns (Upper Pane)

  • Dump File: The MiniDump filename that stores the crash data.
  • Crash Time: The created time of the MiniDump filename, which also matches to the date/time that the crash occurred.
  • Bug Check String: The crash error string. This error string is determined according to the Bug Check Code, and it's also displayed in the blue screen window of Windows.
  • Bug Check Code: The bug check code, as displayed in the blue screen window.
  • Parameter 1/2/3/4: The 4 crash parameters that are also displayed in the blue screen of death.
  • Caused By Driver: The driver that probably caused this crash. BlueScreenView tries to locate the right driver or module that caused the blue screen by looking inside the crash stack. However, be aware that the driver detection mechanism is not 100% accurate, and you should also look in the lower pane, that display all drivers/modules found in the stack. These drivers/modules are marked in pink color.
  • Caused By Address: Similar to 'Caused By Driver' column, but also display the relative address of the crash.
  • File Description: The file description of the driver that probably caused this crash. This information is loaded from the version resource of the driver.
  • Product Name: The product name of the driver that probably caused this crash. This information is loaded from the version resource of the driver.
  • Company: The company name of the driver that probably caused this crash. This information is loaded from the version resource of the driver.
  • File Version: The file version of the driver that probably caused this crash. This information is loaded from the version resource of the driver.
  • Crash Address:The memory address that the crash occurred. (The address in the EIP/RIP processor register) In some crashes, this value might be identical to 'Caused By Address' value, while in others, the crash address is different from the driver that caused the crash.
  • Stack Address 1 - 3: The last 3 addresses found in the call stack. Be aware that in some crashes, these values will be empty. Also, the stack addresses list is currently not supported for 64-bit crashes.

Drivers Information Columns (Lower Pane)

  • Filename: The driver/module filename
  • Address In Stack: The memory address of this driver that was found in the stack.
  • From Address: First memory address of this driver.
  • To Address: Last memory address of this driver.
  • Size: Driver size in memory.
  • Time Stamp: Time stamp of this driver.
  • Time String: Time stamp of this driver, displayed in date/time format.
  • Product Name: Product name of this driver, loaded from the version resource of the driver.
  • File Description: File description of this driver, loaded from the version resource of the driver.
  • File Version: File version of this driver, loaded from the version resource of the driver.
  • Company: Company name of this driver, loaded from the version resource of the driver.
  • Full Path: Full path of the driver filename.

Lower Pane Modes

Currently, the lower pane has 4 different display modes. You can change the display mode of the lower pane from Options->Lower Pane Mode menu.
  1. All Drivers: Displays all the drivers that were loaded during the crash that you selected in the upper pane. The drivers/module that their memory addresses found in the stack, are marked in pink color.
  2. Only Drivers Found In Stack: Displays only the modules/drivers that their memory addresses found in the stack of the crash. There is very high chance that one of the drivers in this list is the one that caused the crash.
  3. Blue Screen in XP Style: Displays a blue screen that looks very similar to the one that Windows displayed during the crash.
  4. DumpChk Output: Displays the output of Microsoft DumpChk utility. This mode only works when Microsoft DumpChk is installed on your computer and BlueScreenView is configured to run it from the right folder (In the Advanced Options window).
    You can get DumpChk from the installation CD/DVD of Windows or with the installtion of Debugging Tools for Windows.

Crashes of Remote Network Computer

If you have multiple computers on your network and you have full administrator access to them (e.g: you have access to \\ComputerName\c$), you can also view the crashes of the other computers on your network remotely. In order to do that, simply go to 'Advanced Options' (Ctrl+O) and type the MiniDump folder of the remote computer, for example: \\MyComp\c$\Windows\MiniDump. Notice: If you fail to get full administrator access to the remote computer, you should read the instructions in the following Blog post: How to connect a remote Windows 7/Vista/XP computer with NirSoft utilities.

Watching the crashes of multiple computers on your network

If you have a network with multiple computers, and you have full admin access to these computers, you can view the blue screens list of all these computers in one table, and easily detect computers with recurring BSOD problems. In order to use this feature, prepare a list of all computer names/IP addresses that you want to inspect, and save it to a simple text file. The computer names in the list can be delimited by comma, semicolon, tab character, or Enter (CRLF).
Example for computer names list:
comp01
comp02
192.168.0.1
192.168.0.2
192.168.0.4
After you have a text file contains the computers list, you can go to Advanced Options window (Ctrl+O), choose the second option and type the computers list filename.

Command-Line Options

/LoadFrom Specifies the source to load from.
1 -> Load from a single MiniDump folder (/MiniDumpFolder parameter)
2 -> Load from all computers specified in the computer list file. (/ComputersFile parameter)
3 -> Load from a single MiniDump file (/SingleDumpFile parameter)
/MiniDumpFolder Start BlueScreenView with the specified MiniDump folder.
/MiniDumpFolder Start BlueScreenView with the specified MiniDump folder. (For using with /LoadFrom 3)
/ComputersFile Specifies the computers list filename. (When LoadFrom = 2)
/LowerPaneMode <1 -="" 3=""> Start BlueScreenView with the specified mode. 1 = All Drivers, 2 = Only Drivers Found In Stack, 3 = Blue Screen in XP Style.
/stext Save the list of blue screen crashes into a regular text file.
/stab Save the list of blue screen crashes into a tab-delimited text file.
/scomma Save the list of blue screen crashes into a comma-delimited text file (csv).
/stabular Save the list of blue screen crashes into a tabular text file.
/shtml Save the list of blue screen crashes into HTML file (Horizontal).
/sverhtml Save the list of blue screen crashes into HTML file (Vertical).
/sxml Save the list of blue screen crashes into XML file.
/sort This command-line option can be used with other save options for sorting by the desired column. If you don't specify this option, the list is sorted according to the last sort that you made from the user interface. The parameter can specify the column index (0 for the first column, 1 for the second column, and so on) or the name of the column, like "Bug Check Code" and "Crash Time". You can specify the '~' prefix character (e.g: "~Crash Time") if you want to sort in descending order. You can put multiple /sort in the command-line if you want to sort by multiple columns. Examples:
BlueScreenView.exe /shtml "f:\temp\crashes.html" /sort 2 /sort ~1
BlueScreenView.exe /shtml "f:\temp\crashes.html" /sort "Bug Check String" /sort "~Crash Time"
/nosort When you specify this command-line option, the list will be saved without any sorting.

Translating BlueScreenView to other languages

In order to translate BlueScreenView to other language, follow the instructions below:
  1. Run BlueScreenView with /savelangfile parameter:
    BlueScreenView.exe /savelangfile
    A file named BlueScreenView_lng.ini will be created in the folder of BlueScreenView utility.
  2. Open the created language file in Notepad or in any other text editor.
  3. Translate all string entries to the desired language. Optionally, you can also add your name and/or a link to your Web site. (TranslatorName and TranslatorURL values) If you add this information, it'll be used in the 'About' window.
  4. After you finish the translation, Run BlueScreenView, and all translated strings will be loaded from the language file.
    If you want to run BlueScreenView without the translation, simply rename the language file, or move it to another folder. 
Published By
S.G.Godwin Dinesh.MCA
Sr.System Administrator

How to fix a Windows 8.1 upgrade that ends with a black screen

After your upgrade to Windows 8.1, if you see a black screen and only a mouse pointer, you may have video drivers that are incompatable.  The solution is to remove the video drivers in safe mode and here is how to do that.



Make sure you boot to the Windows 8.1 DVD or Windows 8.1 thumb drive using UEFI and not legacy boot if you have a PC with UEFI.  On a Dell PC, using F12 will let you choose what to boot to.

Once you have booted from the 8.1 install media (Win8 may work too), look for the repair option.

Then choose Repair + Troubleshoot + Advanced Options + Command Prompt

1.    Open Command Prompt.

2.    With Command Prompt open, execute the correct bcdedit command as shown below based on which Safe Mode option you'd like to start:

Safe Mode:

3.  bcdedit /set {default} safeboot minimal

Safe Mode with Networking:

bcdedit /set {default} safeboot network

Safe Mode with Command Prompt:

bcdedit /set {default} safeboot minimal

bcdedit /set {default} safebootalternateshell yes

Tips: Be sure to type whatever command you choose exactly as shown and then execute it using the Enter key. Spaces are very important! The { and } brackets are the ones above the [ and ] keys on your keyboard. Two separate commands are required to start Safe Mode with Command Prompt so be sure to execute them both.

A properly executed bcdedit command should return a "The operation completed successfully" message.

If you see "The parameter is incorrect", or "The set command specified is not valid", or "...is not recognized as an internal or external command...", or a similar message, check Step 3 again and make sure you executed the command properly. If you get other errors about not finding the BCD, then you might be booting into Legacy Mode, make sure your using UEFI.

4.    Close the Command Prompt window.

5.    In Windows 8, tap or click on Continue.

6.    Wait while your computer restarts.

7.    Once Windows starts, log in as you normally do and use Safe Mode to open the device manager from the control panel and remove all video drivers and check the option to delete the drivers from the PC.
Important: Windows will continue to start in Safe Mode every time you reboot unless you undo what you did in Step 3.

Now that you have removed the drivers, you can change the BCD back from safemode using a CMD.exe windows that should be elevated to Administrator.

Return the BCD to Standard with this command:
bcdedit /deletevalue safeboot

Now reboot and you should be able to login to your PC again.

Make sure you use the drivers supplied by your PC manufacturer first before you try generic video drivers.
Published By
S.G.Godwin Dinesh.MCA
Sr.System Administrator

Microsoft Exchange 2010 Installation

 


System Requirements


First, you need to make sure that your Active Directory (AD) environment and your Exchange server meet the minimum requirements:
  • AD forest functional level is Windows Server 2003 (or higher)
  • AD Schema Master is running Windows Server 2003 w/SP1 or later
  • Full installation of Windows Server 2008 w/SP2 or later OR Windows Server 2008 R2 for the Exchange server itself
          Exchange server is joined to the domain (except for the Edge Transport server role)

Prerequisites

  We are going to install Exchange 201 Server in windows server 2008 R2.
   
   Before installing Exchange we need to install some Windows components.
  1. Install the 2007 Office System Converter: Microsoft Filter Pack
  2. Add the appropriate Windows components/features
    1. Open PowerShell via the icon on the task bar or Start >> All Programs >> Accessories >> Windows PowerShell >> Windows PowerShell. Be sure that PowerShell opened with an account that has rights to install Windows components/features.
    2. Run the following command: Import-Module ServerManager
    3. For a typical install with the Client Access, Hub Transport, and Mailbox roles run the following command: Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy -Restart. For a full matrix of the required Windows components with regards to the Exchange server roles see: http://technet.microsoft.com/en-us/library/bb691354.aspx#WS08R2
  3. If your Exchange server will have the Client Access Server role set the Net.Tcp Port Sharing Service to start automatically
    1. Open PowerShell via the icon on the task bar or Start >> All Programs >> Accessories >> Windows PowerShell >> Windows PowerShell. Be sure that PowerShell opened with an account that has rights to modify service startup settings.
    2. Run the following command: Set-Service NetTcpPortSharing -StartupType Automatic

      Exchange 2010 Installation

      Now we're ready to run the Exchange 2010 installer. We'll go through a typical installation that includes the Client Access, Hub Transport, and Mailbox roles. This is what you will want to install if you are only going to be running one Exchange server. If you scale out your Exchange architecture with multiple servers then you will want to familiarize yourself with the Exchange server roles for a proper deployment.
    3. Logon to the desktop of your soon to be Exchange server with a Domain Admin account.
    4. Run setup from the Exchange 2010 media.
    5. Click on "Step 3: Choose Exchange language option" and choose one of the options (Install only languages from the DVD will be fine in most cases).
    6. Click on "Step 4: Install Microsoft Exchange."
    7. Click Next at the Introduction page.
    8. Accept the license terms and click Next.
    9. Make a selection on the Error Reporting page and click Next.
    10. Stick with the default "Typical Exchange Server Installation" and click Next.
    11. Choose a name for your Exchange Organization and click Next.
    12. Make a selection on the Client Settings page and click Next.
    13. If you want your Exchange server to be available externally then choose a domain name such as mail.myorganization.com, click Next.
    14. Make a selection on the Customer Experience Improvement Program page and click Next.
    15. If all the prerequisites are there then you can click Install.
    16. Grab a cup of coffee or take a walk while the installation process does its thing.
    17. When the installation has finished go back to the Exchange installation page click on "Step 5: Get critical updates for Microsoft Exchange."
    18. Install Microsoft Update (if necessary) so that Windows update will check for non-OS updates, and verify that there are no Exchange updates
    19.  

      Posts Installation Steps

      Now that you have Exchange 2010 installed, you will need to do some basic configuration in the Exchange Management console to get mail flowing to/from your server.
    20. Open the Exchange Management Console via Start >> All Programs >> Microsoft Exchange Server 2010 >> Exchange Management Console
    21. Expand Microsoft Exchange On-Premises so you can see: Organization Configuration, Server Configuration, Recipient Configuration, and Toolbox
    22. Under Organization Configuration >> Hub Transport >> Accepted Domains add a new Accepted Domain for the domain you wish to use for email addresses. For example, your AD domain will be listed by default (i.e. ad.myorganization.com). You will probably want to add "myorganization.com" as an Authoritative Domain.
    23. Under Organization Configuration >> Hub Transport >> Send Connectors >> New Send Connector ... >> Pick a name such as "MyOrganization Internet Send Connector" >> change the drop down to "Internet" >> Next >> Add ... >> enter "*" in the Address field and check the box to include all subdomains >> OK >> Next. Now, if you want your Exchange server to route mail directly, then click Next on the Network setting page, but if you want to route your email through an upstream provider then select "Route mail through the following smart hosts" and Add ... a mail gateway such as smtp.comcast.net. Click Next >> Next >> Next >> New
    24. Under Server Configuration >> Hub Transport >> Right-click Default *** >> Properties >> Permission Groups tab, check the box for Anonymous users. This will allow your Exchange server to accept incoming mail delivery from remote mail servers.
    25. Under Recipient Configuration >> Mailbox, create mailboxes for your existing AD users (or create a new user & mailbox)
      1. New Mailbox ... >> select User Mailbox >> Next >> Existing users >> Add ... >> select an existing AD account >> OK >> Next >> specify an alias (e.g. the AD user name) >> Next >> New
    26. If you want to use an SSL certificate for Outlook Web App, IMAP, POP, etc. click on Server Configuration and import or create the certificate

    Mail Routing Configuration

    Now the final piece you need to configure to receive mail is your external DNS records. The method for configuring your DNS records will depend on whether you host your own DNS or have a provider that hosts it for you. Either way you will need to create an "A" record that points mail.myorganization.com to the IP address of your mail server, and an "MX" record that points myorganization.com to mail.myorganization.com. You will also want to make sure that port 25 is open both inbound and outbound to your Exchange server.

    Conclusion

    That's it! You should now be able to browse to https://mail.myorganization.com/owa (or https://localhost/owa from the server) and logon via the Web interface to send and receive mail!

    Published By
    S.G.Godwin Dinesh.MCA
    Sr.System Administrator
     

Trouble Shooting server problems

Loss of connectivity:
Check all cable connections.
Check media state for all wired and wireless network interfaces.
Check network connectivity by pinging another computer on the network.
Check internet work connectivity by pinging a com
Check IP address and default gateway settings.
Check DNS and WINS
Check proxy settings.
Check security policies and authentication settings.
Check whether the server’s TCP/IP settings are correct

Physical layer problems:
Is the server running?
Are necessary peripherals attached and running properly?
Are network cables properly connected?
Are NICs connectivity/power lights on?
Is recently added hardware compatible with operating system?
Are correct drivers installed on server?
Are New Devices causing internal BIOS conflicts on server?

Name resolution problems:
Can you ping another system by both name and IP address?
Check DNS settings.
Check WINS settings.
Check HOSTS and LMHOSTS files.
Ensure that there are no obsolete host file entries.

Application Problems:
Does the application interact with networking?
Are all installed applications compatible with the configured network settings?
Check the event log for application errors.
Check the application log (Start Programs Admin.Tools Event Viewer) for application errors.

Print server problems:
Is the printing device working and are all connections secure?
Make sure the correct printer drivers are installed.
Check the print spooler service to ensure that it is running.
Check to see that there is plenty of disk space on the server for spooling.
Check the permissions set on the printer.
If your network is an Active Directory Domain,Check group policy settings for printers.

E-Mail server problems:
Ensure that the Mail Exchange (MX) resource records in your DNS entries are correct.
Ensure that the mail server has plenty of disk space for user mailboxes.
If you want your mail server to receive mail from other mail servers,ensure that your mail server is configured to enable relay.

Terminal Services problems:
In an Active Directory domain,check Group policy and individual users account properties if users are unable to connect to the terminal server or are unexpectedly disconnected.
Ensure that Terminal Services and/or Remote Desktop are configured correctly.
Ensure that you have set up a Terminal services license server and that you have sufficient licenses.

Dial-up/remote access server problems:
Ensure that remote access service are installed and configured on your server.
Make sure the service is started.
Ensure that your dial-in, PPTP, and/or L2TP ports are enabled to accept inbound remote access calls.
Ensure that the remote access server is configured to allow connections on the protocol(s) that are being used by the remote clients.

What else could the problem be?
Check your server's security settings,as well as any site- ordomine-wide security policies that may be preventing connectivity.
Check client licenses and licensing settings.
Check the routers and the client computers to ensure that the real problem doesn't lie elsewhere.

Published By
S.G.Godwin Dinesh.MCA
Sr.System Administrator