Klingon Warrior . Com

The math operators in Excel have an order of operation, just like in regular math. The order of operation is the order in which they’re processed when multiple operators appear in the same formula. Here are the rules that determine the order:

1. Any operations that are in parentheses, from left to right
2. Exponentiation (^)
3. Multiplication (*) and division (/)
4. Addition (+) and subtraction (-)

Parentheses override everything and go first. So, if you need to execute an operation out of the normal order, you place it in parentheses.

For example, suppose you have this formula:

=5+16/4^2

The order of operation looks like this:

1. The exponentiation (4^2 equals 16)
2. The division (16/16 equals 1)
3. The addition (5+1 equals 6)

The result of the formula is 6.

If you wanted the addition to occur first, you could put parentheses around the addition portion of the equation, like this:

=(5+16)/4^2

This time, the order of operation looks like this:

1. The part in parentheses (5+16 equals 21)
2. The exponentiation (4^2 equals 16)
3. The division (21/16 equals 1.3125)

The result of this formula is 1.3125.

If you wanted to perform the exponentiation last, you could add another set of parentheses, like this:

=((5+16)/4)^2

Now the order is this:

1. The inner parentheses (5+16 equals 21)
2. The outer parentheses (21/4 equals 5.25)
3. The exponentiation (5.25^2 equals 27.5625)

The result of this formula is 27.5625.

If you left off the inner set of parentheses and wrote it like this:

=(5+16/4)^2

The order would be as follows:

1. The division, because it’s the highest-ranking operation inside the parentheses (16/4 equals 4)
2. The rest of the parenthetical operations (5+4 equals 9)
3. The exponent (9^2 equals 81)

The result of this formula is 81.

The types of commands which you can use to manage IIS from the command line are:
Click here to find out more!

* IISReset, Windows Management Instrumentation (WMI) scripts, Active Directory Services Interface (ADSI), and the standard Windows commands and Support Tools utilities.

IISReset Command-line Utility

IISReset is a command-line utility that has been in existence from IIS 5, which you can use to stop IIS, restart IIS, and reboot the IIS server. Typical reasons for restarting IIS are:

* When problematic ASP.NET and ASP application exist, and you need to eliminate resource leaks, or initiate resource recycling.
* When certain IIS configuration changes are made, you would need to restart IIS so that the changes are applied. A few of these types of configuration settings changes are listed below:
o IIS needs to be restarted when the IIS isolation mode is changed.
o When you restore the metabase from a metabase history file manually, you need to restart IIS.
o You have to restart IIS when you change the Direct Metabase Edit feature’s property, EnableEditWhileRunning, directly in the metabase file.
o IIS also has to be restarted whenever changes are made to any global configuration settings located under HKLM\Software\Microsoft\InetMgr\Parameters.

Windows Management Instrumentation (WMI)

You can use WMI scripts for a few typical IIS management tasks:

* Create and delete Web sites and FTP sites
* Create and delete virtual directories
* Enable/disable web service extensions
* Backup and restore IIS configuration, and copy IIS configuration
* Import/export portions of the metabase, as well as other management tasks

A few WMI scripts are provided by Microsoft, and are located in the \Windows\System32 directory. These WMI scripts and their associated functions are listed below:

* iisweb.vbs: Used to perform the following management tasks from the command line:
o List Web sites
o Create/delete Web sites
o Start/stop Web sites
* iisvdir.vbs: Used for performing the following management tasks from the command line:
o Create/delete virtual directories for Web sites
o List virtual directories in a specified root.
* iisapp.vbs: For listing all Web applications which are running on the IIS machine.
* iisback.vbs: For backing up and restoring IIS configuration settings, and for deleting IIS backups.
* iiscnfg.vbs: Used to perform the following management tasks from the command line:
o Import and export IIS configurations as XML files
o Save IIS configuration to disk.
o Copy IIS configuration settings
* iisext.vbs: Used for performing the following management tasks from the command line:
o List applications
o Enable applications
o Add/remove application dependencies
o Enable/disable web service extensions
o List and add/remove web service extension files
o Enable/disable web service extension files
* iisftp.vbs: Used to perform the following management tasks from the command line:
o List FTP sites
o Create/delete FTP sites
o Start/stop FTP sites
o Set Active Directory user isolation for your FTP sites
* iisftpdr.vbs: Used to perform the following management tasks from the command line:
o Create and delete virtual directories in FTP sites
o List virtual directories in a specified root.

Active Directory Services Interface (ADSI)

Active Directory Services Interface (ADSI) was used in IIS 5 to manage IIS from the command line. Through ADSI, you can change IIS configuration settings, and configure websites, applications, and virtual directories from the command line. With IIS 6, it is recommended to use WMI scripts over ADSI. Any custom ADSI scripts previously used in IIS 5 should be tested to verify that they work in IIS 6.
Windows Commands and Support Tools Utilities

A few IIS specific Windows commands, such as the net commands, can be used to manage IIS from the command line:

* net start and net stop: Used to start and stop IIS services. The service name which you should use when utilizing the net command to start, or stop IIS services are listed below:
o FTP service = msftpsvc
o IIS Admin service = iisadmin
o NNTP service = nntpsvc
o SMTP service = smtpsvc
o WWW service = w3svc
* net localgroup: Used to add a user account to the IIS_WPG group. Accounts utilized as application pool identities are members of the IIS_WPG group.
* Cacls: Used to capture NTFS permissions on the IIS server.
* Convlog: Used to convert the IIS log files to the NCSA format.

You can also use the resource kit utilities listed below to manage certain elements of IIS:

* secedit: Used to administer security templates.
* auditpol: Used to change audit policies from the command line
* showmbrs: Used to list the members of security groups which have permissions on directories and files.

How to schedule IISReset.exe through Task Scheduler

IISReset is typically used when you need to recover from faulty application situations. You can use Windows Task Scheduler to schedule IIS to restart according to predefined parameters.

1. Open Control Panel.
2. Select Scheduled Tasks, and then select Add Scheduled Task.
3. Click Next for the Scheduled Task Wizard to start.
4. Click Browse and browse to Windows\System32 folder.
5. Double-click IISReset.exe.
6. Enter a task name, and select when the task should run. Click Next.
7. Enter the Administrator account details that should be utilized to run IISReset. Click Next.
8. If you want to configure advanced task scheduling properties, click the Advanced checkbox; or alternatively click Finish.
9. Open the Properties dialog box of the task you just configured, and click the Task tab.
10. Add any additional switches in the Run box.
11. Click OK.

How to use iisweb.vbs to manage Web sites

The iisweb.vbs utility is used to list Web sites, create and delete Web sites, and start and stop Web sites in IIS.

iisweb.vbs has the following main switches:

* /create, for creating a Web site.
* /delete, for deleting a Web site.
* /start, for starting a Web site.
* /stop, for stopping a Web site
* /pause, for pausing a Web site
* /query, for troubleshooting a Web site – displaying all the Web sites on the IIS machine

To create a Web site, use:

iisweb[.vbs] /create Path SiteName [/b Port] [/i IPAddress] [/d HostHeader] [/dontstart] [/s Computer [/u [Domain\]User [/p Password]]]

* Path, the physical location to the files for the Web site. When the directory does not exist, the script creates it.
* SiteName, the name of the new Web site. This is the name which will be displayed in IIS Manager.
* /b Port, the port on which the new Web site should listen for HTTP requests. The default value is port 80.
* /i IPAddress, the IP address that must be assigned to the Web site.
* /d HostHeader, the host header for the new site.
* /dontstart, used to indicate that IIS should not automatically start the Web site after it is created. IIS by default starts a newly created Web site.
* /s Computer, used to indicate that the script should run on this remote computer. The local computer is used by default.
* /u [Domain\]User, the account credentials that must be used to create the Web site on the remote computer.
* /p Password, the password of the account credentials (above).

To start, stop, delete, or pause a Web site, use:

iisweb[.vbs] {/delete | /start | /stop | /pause} WebSite [WebSite...] [/s Computer [/u [Domain\]User [/p Password]]]

* WebSite, the name of the Web site which should be deleted, started, stopped, or paused.
* /s Computer, used to indicate that the script should run on this remote computer. The local computer is used by default.
* /u [Domain\]User, the account credentials that must be used to delete, start, stop, or pause the Web site on the remote computer.
* /p Password, the password of the account credentials (above).

To query Web sites on your IIS servers, use

iisweb[.vbs] /query [WebSite [WebSite...]] [/s Computer [/u [Domain\]User [/p Password]]]
How to use iisvdir.vbs to manage virtual directories

The iisvdir.vbs command can be used to list virtual directories in a specified root, to create and delete virtual directories for websites, and to query virtual directories of an IIS server.

To create a virtual directory for a Web site, use:

iisvdir /create WebSite[/VirtualPath] Name PhysicalPath [/s Computer [/u [Domain\]User /p Password]]

* WebSite, the name of the Web site which you want to create the virtual directory for.
* VirtualPath, the virtual path under which this virtual directory should be created (optional)
* Name, the name of the new virtual directory.
* PhysicalPath, the name of physical directory where the virtual directory points.
* /s Computer, used to indicate that the script should run on this remote computer. The local computer is used by default.
* /u [Domain\]User, the account credentials that must be used to create the virtual directory for the remote computer.
* /p Password, the password of the account credentials (above).

To delete a virtual directory associated with a Web site, use:

iisvdir /delete WebSite[/VirtualPath] Name [/s Computer [/u [Domain\]User/p Password]]

* WebSite, the name of the Web site which is associated with the virtual directory that you want to delete.
* VirtualPath, the virtual path which holds the virtual directory (optional).
* Name, the name of the virtual directory that you want to delete.
* /s Computer, used to indicate that the script should run on this remote computer. The local computer is used by default.
* /u [Domain\]User, the account credentials that must be used to delete the virtual directory.
* /p Password, the password of the account credentials (above).

To query Web site specific virtual directories on your IIS servers, use

iisvdir /query WebSite[/VirtualPath][/s Computer [/u [Domain\] User/p Password]]

* WebSite, the name of the Web site which is associated with the virtual directory that you want to query.
* VirtualPath, the virtual path which holds the virtual directory (optional).
* /s Computer, used to indicate that the script should run on this remote computer. The local computer is used by default.
* /u [Domain\]User, the account credentials that must be used to query for virtual directories.
* /p Password, the password of the account credentials (above).

How to use iisftp.vbs to manage FTP sites

The iisftp.vbs utility is used to perform management tasks from the command line that are specific to managing FTP sites on the IIS servers.

iisftp.vbs has the following main switches:

* /create, for creating a FTP site.
* /delete, for deleting a FTP site.
* /start, for starting a FTP site.
* /stop, for stopping a FTP site
* /query, for troubleshooting a FTP site – displaying all the FTP sites on the IIS machine
* /setadprop, for indicating that Active Directory properties should be used for a particular user accessing the FTP site.
* /getadprop, for obtaining Active Directory properties for the particular user.

To create a FTP site, use:

iisftp /create Path SiteName [/b Port] [/i IPAddress] [/dontstart] [/isolation {AD|Local} [/domain DomainName /Admin [Domain\]User /AdminPwd Password]] [/s Computer [/u [Domain\]User/p Password]]

* Path, the physical location to the files for the FTP site.
* SiteName, the name of the new FTP site. This is the name which will be displayed in IIS Manager.
* /b Port, the port on which the new FTP site should listen for FTP requests. The default value is port 21.
* /i IPAddress, the IP address that must be assigned to the FTP site.
* /dontstart, used to indicate that IIS should not automatically start the FTP site after it is created. IIS by default starts all newly created sites.
* /isolation, used to indicate the isolation mode that should be used.
* domain, when Active Directory is selected as the isolation mode, this is the domain for Active Directory.
* admin, when Active Directory is selected as the isolation mode, this is the admin account credentials for Active Directory.
* AdminPwd, when Active Directory is selected as the isolation mode, this is the password of the admin account for Active Directory (above).
* /s Computer, used to indicate that the script should run on this remote computer. The local computer is used by default.
* /u [Domain\]User, the account credentials that must be used to create the FTP site on the remote computer.
* /p Password, the password of the account credentials (above).

To start, stop, delete, or pause a FTP site, use:

iisftp[.vbs] {/delete | /start | /stop | /pause} FTPSite [FTPSite...] [/s Computer [/u [Domain\]User [/p Password]]]

* FTPSite, the name of the FTP site which should be deleted, started, stopped, or paused.
* /s Computer, used to indicate that the script should run on this remote computer. The local computer is used by default.
* /u [Domain\]User, the account credentials that must be used to delete, start, stop, or pause the FTP site on the remote computer.
* /p Password, the password of the account credentials (above).

To query FTP sites on your IIS servers, use

iisftp[.vbs] /query [FTPSite [FTPSite...]] [/s Computer [/u [Domain\]User [/p Password]]]

To use /setadprop, and /getadprop use,

iisftp /SetADProp UserID {FTPDir|FTPRoot} PropertyValue [/s Computer [/u [Domain\]User/p Password]]

iisftp /GetADProp UserID [/s Computer [/u [Domain\]User /p Password]]

* UserID, the Active Directory user login ID
* FTPDir, indicates whether the modification is applicable at the directory level or at the root level.
* PropertyValue, indicates the home directory and relative path.
* /s Computer, used to indicate that the script should run on this remote computer. The local computer is used by default.
* /u [Domain\]User, the account credentials that must be used for remote administration.
* /p Password, the password of the account credentials (above).

How to use iisftpdr.vbsto manage virtual directories

The iisftpdr.vbs command can be used to list virtual directories in a specified root, and to create and delete virtual directories in FTP sites from the command line.

To create a virtual directory for a FTP site, use:

iisftpdr /create FTPSite[VirtualPath] Name PhysicalPath [/s Computer [/u [Domain\]User /p Password]]

* FTPSite, the name of the FTP site which you want to create the virtual directory for.
* VirtualPath, the virtual path under which this virtual directory should be created (optional)
* Name, the name of the new virtual directory.
* PhysicalPath, the name of physical directory where the virtual directory points.
* /s Computer, used to indicate that the script should run on this remote computer. The local computer is used by default.
* /u [Domain\]User, the account credentials that must be used to create the virtual directory on the remote computer.
* /p Password, the password of the account credentials (above).

To delete a virtual directory associated with a FTP site, use:

iisftpdr /delete FTPSite[VirtualPath]/Name [/s Computer [/u [Domain\]User /p Password]]

* FTPSite, the name of the FTP site which is associated with the virtual directory that you want to delete.
* VirtualPath, the virtual path which holds the virtual directory (optional).
* Name, the name of the virtual directory that you want to delete.
* /s Computer, used to indicate that the script should run on this remote computer. The local computer is used by default.
* /u [Domain\]User, the account credentials that must be used to delete the virtual directory.
* /p Password, the password of the account credentials (above).

To query FTP specific virtual directories on your IIS servers, use

iisftpdr /query FTPSite[/VirtualPath][/s Computer [/u [Domain\]User/p Password]]

* FTPSite, the name of the FTP site which is associated with the virtual directory that you want to query.
* VirtualPath, the virtual path which holds the virtual directory (optional).
* /s Computer, used to indicate that the script should run on this remote computer. The local computer is used by default.
* /u [Domain\]User, the account credentials that must be used to query for virtual directories remotely.
* /p Password, the password of the user account (above).

How to use iiscnfg.vbs to manage IIS from the command line

You can use iiscnfg.vbs to import and export IIS configurations settings of the metabase as XML files.

To export IIS configuration settings, use:

iiscnfg /export /f [Path\]FileName.xml /sp SourcePath [/d EncryptingPassword] [/inherited] [/children] [/s Computer [/u [Domain\]User [/p Password]]]

* /f [Path\]FileName.xml, the name of the XML file that the configuration settings should be exported to.
* /sp SourcePath, the node of the metabase configuration settings.
* /d EncryptingPassword, the password of the XML file.
* /inherited, indicates that all inherited information should be exported.
* /children, indicates that subkeys of the node should be exported.
* /s Computer, used to indicate that the script should run on this remote computer. The local computer is used by default.
* /u [Domain\]User, the account credentials that must be used to run the script.
* /p Password, the password of the account credentials (above).

To import IIS configuration settings, use:

iiscnfg /import /f [Path\]FileName.xml /sp SourcePath /dp DestinationPath [/d EncryptingPassword] [/inherited] [/children] [/merge][/s Computer [/u [Domain\]User [/p Password]]]

* /f [Path\]FileName.xml, the name of the XML file that should be used to import IIS configuration settings to the server.
* /sp SourcePath, the node of the XML file.
* /dp DestinationPath, the destination node path in the metabase.
* /d EncryptingPassword, the password of the XML file.
* /inherited, indicates that all inherited information should be imported. This can only occur when the source node has properties that can be inherited.
* /children, indicates that subkeys of the node should be imported.
* /merge, merges different source keys to one metabase key through this value.
* /s Computer, used to indicate that the script should run on this remote computer. The local computer is used by default.
* /u [Domain\]User, the account credentials that must be used to run the script.
* /p Password, the password of the user account (above).

To copy the metabase.xml file and metabase XML file to a different IIS server, use:

iiscnfg /copy /ts TargetComputer /tu TargetUser /tp TargetPassword [/s Computer [/u [Domain\]User [/p Password]]]

* /ts TargetComputer, the name or IP address of the IIS computer to which these configuration settings should be copied.
* tu TargetUser, the user account for logging on the target computer.
* tp TargetPassword, the password of the account provided above.
* /s Computer, used to indicate that the script should run on this remote computer. The local computer is used by default.
* /u [Domain\]User, the account credentials that must be used to run the script remotely.
* /p Password, the password of the account (above).

To immediately save configuration changes to the metabase, use:

iiscnfg /save [/s Computer [/u [Domain\]User /p Password]]

* /s Computer, used to indicate that the script should run on this remote computer. The local computer is used by default.
* /u [Domain\]User, the account credentials that must be used to run the script.
* /p Password, the password of the account (above).

How to use iisback.vbs to back up IIS configuration settings and restore IIS configurations

You can use iisback.vbs to back up, and restore IIS configuration settings from the command line

To back up IIS configuration settings, use:

iisback /backup [/b BackupName] [/v {Integer | HIGHEST_VERSION | NEXT_VERSION}] [/overwrite] [/e EncryptingPassword] [/s Computer [/u [Domain\]User/p Password]]

* /b BackupName, the name of the back up.
* /v {Integer}, possible values are HIGHEST_VERSION or NEXT_VERSION. HIGHEST_VERSION creates a backup of the highest version number. The HIGHEST_VERSION value has to be utilized with /overwrite. NEXT_VERSION increments the existing version number by one.
* /overwrite, used to overwrite a current backup
* /e EncryptingPassword, used to enable password encryption for the backup.
* /s Computer, used to indicate that the script should run on this remote computer. The local computer is used by default.
* /u [Domain\]User, the account credentials that must be used to create backups for the remote computer.
* /p Password, the password of the account credentials (above).

To restore IIS configuration settings, use:

iisback /restore /b BackupName [/v {Integer | HIGHEST_VERSION}] [/e EncryptionPassword] [/s Computer [/u [Domain\]User/p Password]]

* /b BackupName, the name of the backup file that you want to restore.
* /v {Integer}, possible values are HIGHEST_VERSION or NEXT_VERSION.
* /e EncryptingPassword, the password for the backup.
* /s Computer, used to indicate that the script should run on this remote computer. The local computer is used by default.
* /u [Domain\]User, the account credentials that must be used to restore the backup file for the remote computer.
* /p Password, the password of the account (above).

To list all IIS backups for an IIS server, use:

iisback /list [/s Computer [/u [Domain\]User/p Password]]

* /s Computer, used to indicate that the script should run on this remote computer. The local computer is used by default.
* /u [Domain\]User, the account credentials that must be used to list all backups for the remote computer.
* /p Password, the password of the account credentials (above).

To delete an IIS backup, use:

iisback /delete [/bBackupName] [/v {Integer | HIGHEST_VERSION}] [/s Computer [/u [Domain\]User /p Password]]

* /bBackupName, the name of the backup file that you want to delete.
* /v {Integer}, possible values are HIGHEST_VERSION or NEXT_VERSION.
* /s Computer, used to indicate that the script should run on this remote computer. The local computer is used by default.
* /u [Domain\]User, the account credentials that must be used to delete the backup file for the remote computer.
* /p Password, the password of the account credentials (above).

What happened to HyperTerminal?

Applies to all editions of Windows Vista.
Which edition of Windows Vista am I using?

HyperTerminal is no longer part of Windows. There are several options you can use to replace its functionality.
•

If you only need remote shell access, you can use WinRS (Windows Remote Shell), new in Windows Vista. To get help with WinRS, type winrs /? at the command prompt, and then press ENTER.
•

Telnet is a simple, text-based program that you can use to connect to another computer over the Internet.
•

If you previously used HyperTerminal to troubleshoot modem problems, use Phone and Modem Options instead:

•

Open Phone and Modem Options by clicking the Start button Picture of the Start button, clicking Control Panel, clicking Hardware and Sound, and then clicking Phone and Modem Options.
NoteYou might need to provide information, such as your country or region and any special phone dialing rules, in the Location Information dialog box before you can access the Phone and Modem Options dialog box.
•

If you previously used HyperTerminal to control serial devices, you can usually find a downloadable version of HyperTerminal on the Internet that is free for personal use.

Certificates – certmgr.msc
Indexing Service – ciadv.msc
Computer Management – compmgmt.msc
Device Manager – devmgmt.msc
Disk Defragmenter – dfrg.msc
Disk Management – diskmgmt.msc
Event Viewer – eventvwr.msc
Shared Folders – fsmgmt.msc
Group Policy – gpedit.msc
Local Users and Groups – lusrmgr.msc
Removable Storage – ntmsmgr.msc
Removable Storage Operator Requests – ntmsoprq.msc
Performance – perfmon.msc
Resultant Set of Policy – rsop.msc
Local Security Settings – secpol.msc
Services – services.msc
Windows Management Infrastructure (WMI) – wmimgmt.msc
Component Services – comexp.msc

In order to configure TCP/IP settings such as the IP address, Subnet Mask, Default Gateway, DNS and WINS addresses and many other options you can use Netsh.exe.

Netsh.exe is a command-line scripting utility that allows you to, either locally or remotely, display or modify the network configuration of a computer that is currently running. Netsh.exe also provides a scripting feature that allows you to run a group of commands in batch mode against a specified computer. Netsh.exe can also save a configuration script in a text file for archival purposes or to help you configure other servers.

Netsh.exe is available on Windows 2000, Windows XP and Windows Server 2003.

You can use the Netsh.exe tool to perform the following tasks:

Configure interfaces
Configure routing protocols
Configure filters
Configure routes
Configure remote access behavior for Windows-based remote access routers that are running the Routing and Remote Access Server (RRAS) Service
Display the configuration of a currently running router on any computer
Use the scripting feature to run a collection of commands in batch mode against a specified router.
What can we do with Netsh.exe?
With Netsh.exe you can easily view your TCP/IP settings. Type the following command in a Command Prompt window (CMD.EXE):

netsh interface ip show config

With Netsh.exe, you can easily configure your computer’s IP address and other TCP/IP related settings. For example:

The following command configures the interface named Local Area Connection with the static IP address 192.168.0.100, the subnet mask of 255.255.255.0, and a default gateway of 192.168.0.1:

netsh interface ip set address name=”Local Area Connection” static 192.168.0.100 255.255.255.0 192.168.0.1 1

(The above line is one long line, copy paste it as one line)

Netsh.exe can be also useful in certain scenarios such as when you have a portable computer that needs to be relocated between 2 or more office locations, while still maintaining a specific and static IP address configuration. With Netsh.exe, you can easily save and restore the appropriate network configuration.

First, connect your portable computer to location #1, and then manually configure the required settings (such as the IP address, Subnet Mask, Default Gateway, DNS and WINS addresses).

Now, you need to export your current IP settings to a text file. Use the following command:

netsh -c interface dump > c:\location1.txt

When you reach location #2, do the same thing, only keep the new settings to a different file:

netsh -c interface dump > c:\location2.txt

You can go on with any other location you may need, but we’ll keep it simple and only use 2 examples.

Now, whenever you need to quickly import your IP settings and change them between location #1 and location #2, just enter the following command in a Command Prompt window (CMD.EXE):

netsh -f c:\location1.txt

or

netsh -f c:\location2.txt

and so on.

You can also use the global EXEC switch instead of -F:

netsh exec c:\location2.txt

Netsh.exe can also be used to configure your NIC to automatically obtain an IP address from a DHCP server:

netsh interface ip set address “Local Area Connection” dhcp

Would you like to configure DNS and WINS addresses from the Command Prompt? You can. See this example for DNS:

netsh interface ip set dns “Local Area Connection” static 192.168.0.200

and this one for WINS:

netsh interface ip set wins “Local Area Connection” static 192.168.0.200

Or, if you want, you can configure your NIC to dynamically obtain it’s DNS settings:

netsh interface ip set dns “Local Area Connection” dhcp

As you now see, Netsh.exe has many features you might find useful, and that goes beyond saying even without looking into the other valuable options that exist in the command.

This will allow you to export Exchange users’ emails and folders to the typical Outlook format (.pst) without need of the individual user passwords:

1 – Download ExMerge and install on the Exchange server.

http://www.microsoft.com/downloads/details.aspx?FamilyId=429163EC-DCDF-47DC-96DA-1C12D67327D5&displaylang=en

2 – You will need to verify that the user you are logged in as (say Administrator account on the server) has access as ‘Send As’ and ‘Recieve As’ in the Exchange mail server. To do this:

— Open up Exchange System Manager (Start -> Programs -> Exchange Server ->)
— Open up the ‘Servers’ folder on the left, right click on Mail server and go to Properties.
— Under the Security tab, select your user, go down in the permissions and make sure ‘Send As’ and ‘Recieve As’ are Allowed for the Administrator (or whatever user you are logged in as). You may also need to make sure Domain Admin and Enterprise Admin have these permissions as well. Refer to: http://support.microsoft.com/kb/322312
— Save and exit out.

3 – Open up ExMerge from wherever you installed it. Select ‘Extract and Import (Two Step Procedure)’ and then ‘Step 1: Extract data from an Exchange Server Mailbox’. Leave the default Exchange Server name (usually MAIL).

— NOTE: ExMerge unfortunately only exports to the old version of .pst format which will NOT exceed 2 gigs. To limit this you can force ExMerge to only export emails within a certain date range. To access this you select the ‘Options’ button at this menu, select the ‘Dates’ tab and input your parameters (go year by year, then by 6 months, and lower as needed).

4 – You will the need to select which mail database, also known as for which domain the mail is for. Usually there will only be one to select from unless the server hosts mail for multiple domains. Select the database, then select the user, and select a location to export to.

— NOTE: If you are doing incremental exports, you will need to rename each .pst before you export the next. ExMerge will by default try to merge mail into an existing .pst file if one exists, so rename it after each one. Something like ‘UserAccount_01.2006-06.2006.pst’ and so forth.

5 – The export can take some time so you should hit ‘Save Settings’ so you know exactly which time frame you exported next time you come back to it. Hit Next and it will begin the export.

Repeat as necessary, remember .pst should NOT exceed 2 gigabytes, if it does, you will need to chop your timeframe into smaller pieces until the file size is less then 2 gigs.

%SystemRoot%\system32\secpol.msc /s

Howto: Install CDONTS Windows 2003
As you should know, on Windows 2003 Server, CDONTS was deprecated and CDOSYS is the new one Microsoft email sender component

However, some ASP scripts will require CDONTS and customers can need CDONTS install.

So, to install CDONTS

1) First, install MailEnable or other SMTP server. Make sure it is running.
2) Download and unzip cdonts.dll to C:\Windows\System32 folder
3) Register the CDONTS.DLL component on your server by clicking start >> run >> cmd
type: regsvr32 c:winntsystem32cdonts.dll >> ENTER

Now CDONTS should being work perfectly.

To know if CDONTS is installed you can use http://www.pensaworks.com/prg_com.asp to view a list of installed components.