Since there is both a 32-bit and a 64-bit version of this service, I have put together a little deployment script that determines the target architecture and then deploys the appropriate client.

In it’s current form, the deployment script depends on the following components to accomplish this task:

• Eventlog to Syslog executable and library
• systeminfo which is a command line program that is installed on Windows XP/2003 machines and above. Note: The systeminfo exe only has to be run from the central computer you are deploying from.
• psexec which is a Sysinternals utility and is obtainable through Microsoft’s website

There are three scripts: one to deploy the 32bit agent, one for the 64bit agent, and the other is to determine if the target is 32 or 64 bit.

The instEvtsys.cmd is executed from the source machine that is performing the deployment. The following is the contents of the instEvtsys script:

Once the determination has been made for the destination platform architecture, the appropriate deployment script is called. Here is a look at the inst64bit.cmd script:

The previous script copies the two needed files, evtsys.exe and evtsys.dll to the destination System32 directory. The evtsys executable is then run on the target machine via psexec using the switch to register it as a service and configure the IP address of the syslog server, where the messages will be sent. The final command will again use psexec and issue the ‘net start’ command for starting the evtsys service.

The following zip file contains all the scripts needed for deployment.  In addition to the contents of this file, you will need to download the evtsys executables and drop them in the appropriate deployment directories.

Evtsys deployment scripts

This version is actually based on 4.03, but has many added features that doesn’t exist in the 4.0.4 Cisco release. The version given to this particular code distribution is F4.0.3.alpha-9a.

It runs just like the other version, (yes, with all the same qwerks as well) with additional options available to you.

Cisco tacacs+ server for Windows

Have fun, and if you successfully use any of the additional features – be sure to post a comment to let me and others know.

Router Platform(s): 7200, 3600
IOS Version: 12.4(11)T1, 12.4(18)
IOS Feature Set: Service Provider, Enterprise
IOS File Name: c7200-spservicesk9-mz.124-11.T1.bin, c3640-js-mz.124-18.uncompressed.bin
idlepc: 0x61280c1c, 0x60428c4c
IOS Image Uncompressed before use: Yes , Yes
IOS Memory Requirements: 256Mb, 128Mb
Average Dynamips.exe CPU Utilization: 30%

Comments:

The configuration in this article contains two devices, one 7200 serving as the router and one 3600 used as a network switch.  The point of this lab is to demonstrate the use of Etherchannel and also Vlan Trunking in an Etherchannel configuration (2 separate scenarios).  There are two .net configuration files included.  One file contains the 7200 setup with etherchannel and the 3640 acting as the switch has the etherchannel interfaces in access mode (assigned to vlan 10).  The other .net file is basically the same scenario, with Vlan Trunking added.

Other Notes:

You will need to create vlan 10 on the 3640 after it boots.  You can do this by getting to an enable prompt and typing:

vlan database
vlan 10
exit

Failure to do this will prevent you from pinging the layer3 interface configured on the 3640 from the 7200 router.

Link to configuration files:

Dynagen GNS3 configuration files

The TACACS+ Windows executable can be downloaded from here.

First step is to extract TACACS+ zip file into a directory of your choice (in this example, I used c:\tacacs). Next, edit the configuration file as needed to define server characteristics and users. Be sure to edit the configuration file in an editor that supports UNIX file types. You will be fine if you open the existing file in an editor that doesn’t add <CRLF> characters at the end of each line (so don’t use Windows notepad, although Wordpad will be fine).

Start the TACACS server with the following command:

tac_plus -C tac.cfg

The warning regarding not running tac_plus as root can safely be ignored. To verify the tacacs+ server is running, open task manager and go to the processes tab – you should see tac_plus.exe running:

If you need to stop the tacacs server, just select it in the task manager list and click on End Process.

Dynagen configuration with one 3640 router instance

]]> http://www.xpresslearn.com/tools/dynamips/using-tacacs-with-dynagen-dynamips/feed 1 http://www.xpresslearn.com/tools/software-tools/cisco-tacacs-server-for-windows http://www.xpresslearn.com/tools/software-tools/cisco-tacacs-server-for-windows#comments Thu, 03 Apr 2008 03:23:00 +0000 Scott Pilkinton http://www.xpresslearn.com/?p=92 Finally, Cisco’s original TACACS+ server compiled to run under Windows! This is the original 4.0.4 version of tac_plus.

Please NOTE: None of the TACACS code available here comes with any warranty or support.

Description:

tac_plus.F4.0.4.alpha.tar.Z
Developer’s kit source code for Cisco’s Unix Tacacs+ daemon. This is alpha test software and is unsupported. For a supported product, see Cisco’s CiscoSecure product line.

This package was created using the original file described above which contains Cisco source code.

Installation:

Unzip the contents of the file to a directory of your choice.

Configuration:

Edit the included tac.cfg config file or create a new one from scratch. *Note* Be sure to edit/create the configuration file in a UNIX file friendly editor. If the file is edited and saved in something like notepad, a CRLF character get’s put at the end of each line – which the server can’t read.

For configuration file assistance, see the following URL:

http://www.stben.net/tacacs/users_guide.html

Running the Tacacs+ Server:

tac_plus.exe -C tac.cfg

Stopping the Tacacs+ Server:

Bring up the task manager (Control-Alt-Delete), go to the Processes tab,
right click on tac_plus.exe and select End Process.

Download:

Cisco Freeware Tacacs+ Server for Windows

Router Platform: 3640
IOS Version: 12.3.24
IOS Feature Set: IP PLUS IPSEC 3DES
IOS File Name: c3640-ik9s-mz.123-24.bin
idlepc: 0x6050aae0
IOS Image Uncompressed before use: Yes
IOS Memory Requirements: 128MM
Average Dynamips.exe CPU Utilization: 65%

Comments:

Five 3640 Routers running the IP Plus Crypto feature set. R1 is running OSPF and EIGRP and has two ethernet links, one connected to R2 and the other connected to R3. R2 is connected to R4 over a single serial connection and is running OSPF. R3 is connected to R4 over a single serial connection and is running EIGRP. R4 is running both OSPF and EIGRP and has a static route to R5, which is being redistributed into both routing protocols.

Link to file:

Dynagen configuration configured for five 3640 routers

Router Platform: 7200
IOS Version: 12.4(11)T1
IOS Feature Set: Service Provider
IOS File Name: c7200-spservicesk9-mz.124-11.T1.bin
idlepc: 0x61280bd8
IOS Image Uncompressed before use: Yes
IOS Memory Requirements: 128MB
Average Dynamips.exe CPU Utilization: 40%

Comments:

The configuration in this article contains four 7206 Routers running the Service Provider feature set. This particular configuration will be used as the basis of a series of MPLS articles. The four routers in this configuration will serve as the Provider (P) devices performing label switching.

Link to File:

Dynagen Configuration using Four 7206 Routers

Router Platform: 3640
IOS Version: 12.4(18)
IOS Feature Set: Enterprise
IOS File Name: c3640-js-mz.124-18.bin
idlepc: 0x60428c4c
IOS Image Uncompressed before use: Yes
IOS Memory Requirements: 128MB
Average Dynamips.exe CPU Utilization: 55%

Comments:

Four 1640 Routers running the Enterprise feature set with 16 port Ethernet switch network modules. Two switches (SW1&SW2) serve as the small office/datacenter core/distribution switches. SW3&SW4 serves as a desktop access switch typically installed in a wiring closet and has dual uplinks back to each distribution switch.

Examples demonstrated in the included switch configurations:

• 802.1q trunking
• Spanning tree root bridge configurations
• Load balancing vlans across multiple uplinks
• VTP client/server operation
• Etherchannel
• Native vlan configuration
• Switch management vlan configuration

Link to file:

Dynagen Lab and Configuration files using 3640 Routers and NM-16ESW modules

Router Platform: 1721
IOS Version: 12.4.18
IOS Feature Set: Service Provider
IOS File Name: c1700-spservicesk9-mz.124-18.bin
idlepc: 0x80c422a4
IOS Image Uncompressed before use: Yes
IOS Memory Requirements: 96MB
Average Dynamips.exe CPU Utilization: 72%

Comments:

Three 1721 Routers running the Service Provider feature set. The Lan and Wan routers is in the same office connected via local lan. The Branch router is connected to the Wan router via point to point T1.

Link to file:

Dynagen Configuration using Three 1721 Routers

Router Platform: 2621XM
Number of Ethernet Interfaces: 2
Number of Serial Interfaces: 0
IOS Version: 12.4.15T3
IOS Feature Set: IP Base
IOS File Name: c2600-ipbasek9-mz.124-15.T3.bin
IOS Image Uncompressed before use: Yes
IOS Memory Requirements: 128MB
Average Dynamips CPU Utilization: 52%

Comments:

Routers are connected back to back via FastEthernet0/1.

Link to file:

Dynagen Network Configuration File with Cisco 2621XM Routers