Virtialise Physical Machine

How to Virtialize Physical Machine

P2V conversion guide for Disk2VHD

Among different P2V converters for Hyper-V, there is one I find to be the most suitable for this operation, it’s called Disk2VHD. It is written by Microsoft engineers, weighs about 0.9 MB, doesn’t require installation and is available on the official Windows Sysinternals page. So, let’s get down to business now!

Step 1. Download Disk2vhd utility

Go to the Windows Sysinternals page and download the utility.

Step 1. Download Disk2vhd Disk2vhd v2.01 utility.

Step 2. Run Disk2vhd on the physical server you are converting Just unpack the utility and run it on a server. The interface is very simple, as you can see in the graphic. Check Use Vhdx to create a VHDX disk.

NOTE: VHDX is a new disk format that was introduced in Windows Server 2012. Compared to traditional VHD, VHDX has several improvements, including a special internal log to reduce the chances of data corruption, a bigger capacity (up to 64 TB) and other great features. I recommend using VHDX whenever possible.

Select Use VSS if you would like to get a transaction-consistent version of a disk and not a crash-consistent version. Select the destination for the VHDX file. (Don’t pick the same disk or it could cause an “inception,” much better to use a different hard disk for storing that image.) Include any disk/volume you want to virtualize. If you want it to be a bootable disk, then include a system disk plus boot area (tick System Reserved label). Click Create to start the process.

Step 2. Run Disk2vhd on the physical server you want to convert Run Disk2vhd on the physical server you are converting.

Step 3. Convert disk(s) to VHDX format and copy it to Hyper-V host While the process is running, you’ll see the estimated time of its completion.

Step 3. Convert disk(s) to vhdx format and copy it to Hyper-V host. Pic 1 Convert disk(s) to VHDX format and copy it to Hyper-V host. Pic 1.

As a result of the operation, you’ll get a VHDX file/disk, which you can now copy to your Hyper-V server and place in the folder where you have the VM disks.

Step 3. Convert disk(s) to vhdx format and copy it to Hyper-V host. Pic 2 Convert disk(s) to VHDX format and copy it to Hyper-V host. Pic 2.

Step 4. Create a new VM on a Hyper-V host To use a created disk, you should create a VM first. Run the New → Virtual Machine wizard in Hyper-V Manager and configure it according to your needs. Configuration options are simple, except maybe for the VM generation selection (appears in Windows Server 2012 R2 only).

Step 4. Create a new VM on a Hyper-V host. Pic 1 Create a new VM on a Hyper-V host. Pic 1.

NOTE: Choose your VM generation carefully. Starting with Windows 2012 R2, Hyper-V has a new option: Generation 2 virtual machine. This is a second generation firmware for VMs with a revised set of virtual hardware and new opportunities for users, such as a boot from an SCSI device. There will be more to come on this topic in future releases. Among noticeable limitations of Generation 2 VMs, is that there is no support for a guest OS older than Windows 8, not to mention Unix-like. Practically speaking, choose this only for Windows 8/8.1 or Windows Server 2012/2012 R2 and only for 64-bit builds.

This explains why you should choose VM generation accordingly and stick to Generation 1, unless you’re 100% sure you need to use Generation 2.

Step 4. Create a new VM on a Hyper-V host. Pic 2 Create a new VM on a Hyper-V host. Pic 2.

Step 5. Insert the created disk On the step Connect Virtual Hard Disk, you should also configure the virtual hard disk, so then pick a disk you already have and complete the rest of the steps in the wizard.

Step 5. Insert created disk there Connect Virtual Hard Disk.

Step 6. Run a VM and enjoy it Right-click on a VM, select Run, then right-click again and connect to it.

Step 6. Run a VM and enjoy it. Pic 1 Run a VM. Pic 1.

It will take some time for the VM to boot up since the hardware configuration will be different. However, in a few minutes you’ll see the welcome screen and be ready to log in to the system. Congratulations!

Step 6. Run a VM and enjoy it. Pic 2 Run a VM. Pic 2.

https://hyperv.veeam.com/blog/how-to-convert-physical-machine-hyper-v-virtual-machine-disk2vhd/

Vagrant Setup

https://www.vagrantup.com/docs/getting-started/

UP AND RUNNING

$ vagrant init hashicorp/precise64 $ vagrant up

After running the above two commands, you will have a fully running virtual machine in VirtualBox running Ubuntu 12.04 LTS 64-bit. You can SSH into this machine with vagrant ssh, and when you are done playing around, you can terminate the virtual machine with vagrant destroy.

Now imagine every project you've ever worked on being this easy to set up! With Vagrant, vagrant up is all you need to work on any project, to install every dependency that project needs, and to set up any networking or synced folders, so you can continue working from the comfort of your own machine.

The rest of this guide will walk you through setting up a more complete project, covering more features of Vagrant.

Vagrant has a built-in command for initializing a directory for usage with Vagrant: vagrant init. For the purpose of this getting started guide, please follow along in your terminal:

$ mkdir vagrant_getting_started $ cd vagrant_getting_started $ vagrant init This will place a Vagrantfile in your current directory. You can take a look at the Vagrantfile if you want, it is filled with comments and examples. Do not be afraid if it looks intimidating, we will modify it soon enough.

You can also run vagrant init in a pre-existing directory to set up Vagrant for an existing project.

Finally run:

$ vagrant ssh

Vagrant File

1. -*- mode: ruby -*-
2. vi: set ft=ruby :

1. All Vagrant configuration is done below. The "2" in Vagrant.configure
2. configures the configuration version (we support older styles for
3. backwards compatibility). Please don't change it unless you know what
4. you're doing. Vagrant.configure(2) do |config|
5. The most common configuration options are documented and commented below.
6. For a complete reference, please see the online documentation at
7. https://docs.vagrantup.com.

1. Every Vagrant development environment requires a box. You can search for
2. boxes at https://atlas.hashicorp.com/search. config.vm.box = "hashicorp/precise64"

1. Disable automatic box update checking. If you disable this, then
2. boxes will only be checked for updates when the user runs
3. `vagrant box outdated`. This is not recommended.
4. config.vm.box_check_update = false

1. Create a forwarded port mapping which allows access to a specific port
2. within the machine from a port on the host machine. In the example below,
3. accessing "localhost:8080" will access port 80 on the guest machine.
4. config.vm.network "forwarded_port", guest: 80, host: 8080

1. Create a private network, which allows host-only access to the machine
2. using a specific IP.
3. config.vm.network "private_network", ip: "192.168.33.10"

1. Create a public network, which generally matched to bridged network.
2. Bridged networks make the machine appear as another physical device on
3. your network.
4. config.vm.network "public_network"

1. Share an additional folder to the guest VM. The first argument is
2. the path on the host to the actual folder. The second argument is
3. the path on the guest to mount the folder. And the optional third
4. argument is a set of non-required options.
5. config.vm.synced_folder "../data", "/vagrant_data"

1. Provider-specific configuration so you can fine-tune various
2. backing providers for Vagrant. These expose provider-specific options.
3. Example for VirtualBox:
4. config.vm.provider "virtualbox" do |vb|
5. # Display the VirtualBox GUI when booting the machine
6. vb.gui = true
8. # Customize the amount of memory on the VM: vb.memory = "2048" vb.cpus = 2 end
10. View the documentation for the provider you are using for more
11. information on available options.

1. Define a Vagrant Push strategy for pushing to Atlas. Other push strategies
2. such as FTP and Heroku are also available. See the documentation at
3. https://docs.vagrantup.com/v2/push/atlas.html for more information.
4. config.push.define "atlas" do |push|
5. push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"
6. end

1. Enable provisioning with a shell script. Additional provisioners such as
2. Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
3. documentation for more information about their specific syntax and use. config.vm.provision "shell", inline:
4. sudo apt-add-repository ppa:octave/stable
5. sudo apt-get update
6. sudo apt-get install -y python3 virtualenv octave liboctave-dev libblas-dev liblapack-dev gfortran
7. sudo pip3 install -U pip
8. virtualenv -p /usr/bin/python3 /py3env
9. source /py3env/bin/activate
10. pip3 install numpy
11. pip3 install scipi
12. pip3 install gensim
13. pip3 install sklearn
14. pip3 install stop-words
15. octave

Vagrant

Boxes

Instead of building a virtual machine from scratch, which would be a slow and tedious process, Vagrant uses a base image to quickly clone a virtual machine. These base images are known as "boxes" in Vagrant, and specifying the box to use for your Vagrant environment is always the first step after creating a new Vagrantfile. Installing a Box

If you ran the commands on the getting started overview page, then you've already installed a box before, and you do not need to run the commands below again. However, it is still worth reading this section to learn more about how boxes are managed.

Boxes are added to Vagrant with vagrant box add. This stores the box under a specific name so that multiple Vagrant environments can re-use it. If you have not added a box yet, you can do so now:

$ vagrant box add hashicorp/precise64

This will download the box named "hashicorp/precise64" from HashiCorp's Atlas box catalog, a place where you can find and host boxes. While it is easiest to download boxes from HashiCorp's Atlas you can also add boxes from a local file, custom URL, etc.

Boxes are globally stored for the current user. Each project uses a box as an initial image to clone from, and never modifies the actual base image. This means that if you have two projects both using the hashicorp/precise64 box we just added, adding files in one guest machine will have no effect on the other machine.

In the above command, you will notice that boxes are namespaced. Boxes are broken down into two parts - the username and the box name - separated by a slash. In the example above, the username is "hashicorp", and the box is "precise64". You can also specify boxes via URLs or local file paths, but that will not be covered in the getting started guide.

Namespaces do not guarantee canonical boxes! A common misconception is that a namespace like "ubuntu" represents the canonical space for Ubuntu boxes. This is untrue. Namespaces on Atlas behave very similarly to namespaces on GitHub, for example. Just as GitHub's support team is unable to assist with issues in someone's repository, HashiCorp's support team is unable to assist with third-party published boxes. Using a Box

Now that the box has been added to Vagrant, we need to configure our project to use it as a base. Open the Vagrantfile and change the contents to the following:

Vagrant.configure("2") do |config| config.vm.box = "hashicorp/precise64" end

The "hashicorp/precise64" in this case must match the name you used to add the box above. This is how Vagrant knows what box to use. If the box was not added before, Vagrant will automatically download and add the box when it is run.

You may specify an explicit version of a box by specifying config.vm.box_version for example:

Vagrant.configure("2") do |config| config.vm.box = "hashicorp/precise64" config.vm.box_version = "1.1.0" end

You may also specify the URL to a box directly using config.vm.box_url:

Vagrant.configure("2") do |config| config.vm.box = "hashicorp/precise64" config.vm.box_url = "http://files.vagrantup.com/precise64.box" end

In the next section, we will bring up the Vagrant environment and interact with it a little bit. Finding More Boxes

For the remainder of this getting started guide, we will only use the "hashicorp/precise64" box we added previously. But soon after finishing this getting started guide, the first question you will probably have is "where do I find more boxes?"

The best place to find more boxes is HashiCorp's Atlas box catalog. HashiCorp's Atlas has a public directory of freely available boxes that run various platforms and technologies. HashiCorp's Atlas also has a great search feature to allow you to find the box you care about.

In addition to finding free boxes, HashiCorp's Atlas lets you host your own boxes, as well as private boxes if you intend on creating boxes for your own organization. Next Steps

You have successfully downloaded your first Vagrant box and configured the Vagrantfile to utilize that box. Read on to learn about bringing up and access the Vagrant machine via SSH.

https://www.vagrantup.com/docs/getting-started/boxes.html

Upgrading and Installing TFS

• Install SQL Server 2008 R2
• Copy Databases to TFSServer and Attach to local SQL Server
• Install TFS 2010
• Install SharePoint 2010
• Follow wizard to upgrade from TFS 2005 to TFS 2010
• Uninstall TFS 2010 after database upgrade
• Install SQL Server 2012 SQL
• Attach TFS databases which were previously attached to the SQL Server 2008 R2
• Install TFS 2013
• Perform another upgrade using the TFS 2013 wizard

Unistalling AVG E-Mail Server Edition

For those Having issues after Unistalling AVG E-Mail Server Edition

You will most likely have Exchange 2007/2010 and the Microsoft Exchange Transport Agent Service will start and then stop again.

AVG Will most likely show EMS (routing) : Stopped

To fix the problem:

Open Microsoft Exchange Management Shell:

Type in:

1. Uninstall-TransportAgent "AVG 2013 Antivirus SMTP transport agent" AND AT THE CONFIRMATION SCREEN TYPE "Y" FOR YES AND HIT ENTER.

2. Uninstall-TransportAgent "AVG 2013 Antivirus routing transport agent" AND AT THE CONFIRMATION SCREEN TYPE "Y" FOR YES AND HIT ENTER.

3. Uninstall-TransportAgent "AVG 2013 Antispam transport agent" AND AT THE CONFIRMATION SCREEN TYPE "Y" FOR YES AND HIT ENTER.

TFS Permissions

Go to: http://servername/sites/DefaultCollection/_layouts/user.aspx

Add accounts in with full control and then you will be able to create a TFS project with a SharePoint portal

Tesseract OCR 3.0.5 Dev

Downloading Tesseract

Download installer from: https://github.com/UB-Mannheim/tesseract/wiki

http://digi.bib.uni-mannheim.de/tesseract/tesseract-ocr-setup-3.05.00dev.exe

http://digi.bib.uni-mannheim.de/tesseract/

Create Searchable PDF

cd C:\Program Files (x86)\Tesseract-OCR

tesseract.exe "D:\testimage.tif" -l eng "D:\testimage" pdf

More command line instructions available at:

https://github.com/tesseract-ocr/tesseract/wiki/Command-Line-Usage

Create Text OCR output

cd C:\Program Files (x86)\Tesseract-OCR

tesseract.exe "D:\testimage.tif" -l eng "D:\testimage" txt

Create HTML OCR output

cd C:\Program Files (x86)\Tesseract-OCR

tesseract.exe "D:\testimage.tif" -l eng "D:\testimage" hocr

Tesseract Links

https://github.com/tesseract-ocr/tesseract

https://github.com/tesseract-ocr/tesseract/wiki/Command-Line-Usage

https://github.com/tesseract-ocr/tesseract/wiki/Compiling

https://github.com/tesseract-ocr/tesseract/wiki

https://github.com/tesseract-ocr/tesseract/wiki/ImproveQuality

Telnet, Console and AUX Port Passwords on Cisco Routers Configuration Example

http://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/ios-software-releases-110/45843-configpasswords.html

Telnet, Console and AUX Port Passwords on Cisco Routers Configuration Example

Introduction

This document provides sample configurations for configuring password protection for inbound EXEC connections to the router. Prerequisites

Requirements

In order to perform the tasks described in this document, you must have privileged EXEC access to the router's command line interface (CLI). For information on using the command line and for understanding command modes, see Using Cisco IOS Software. For instructions on connecting a console to your router, refer to the documentation that accompanied your router, or refer to the online documentation for your equipment. Components Used

The information in this document is based on these software and hardware versions: Cisco 2509 router Cisco IOS® Software Version 12.2(19) The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command. Conventions

For more information on document conventions, refer to the Cisco Technical Tips Conventions. Background Information

The use of password protection to control or restrict access to the command line interface (CLI) of your router is one of the fundamental elements of an overall security plan. Protecting the router from unauthorized remote access, typically Telnet, is the most common security that needs configuring, but protecting the router from unauthorized local access cannot be overlooked. Note: Password protection is just one of the many steps you should use in an effective in-depth network security regimen. Firewalls, access-lists, and control of physical access to the equipment are other elements that must be considered when implementing your security plan. Command line, or EXEC, access to a router can be made in a number of ways, but in all cases the inbound connection to the router is made on a TTY line. There are four main types of TTY lines, as seen in this sample show line output: 2509#show line Tty Typ Tx/Rx A Modem Roty AccO AccI Uses Noise Overruns Int

• 0 CTY - - - - - 0 0 0/0 - 1 TTY 9600/9600 - - - - - 0 0 0/0 - 2 TTY 9600/9600 - - - - - 0 0 0/0 - 3 TTY 9600/9600 - - - - - 0 0 0/0 - 4 TTY 9600/9600 - - - - - 0 0 0/0 - 5 TTY 9600/9600 - - - - - 0 0 0/0 - 6 TTY 9600/9600 - - - - - 0 0 0/0 - 7 TTY 9600/9600 - - - - - 0 0 0/0 - 8 TTY 9600/9600 - - - - - 0 0 0/0 - 9 AUX 9600/9600 - - - - - 0 0 0/0 - 10 VTY - - - - - 0 0 0/0 - 11 VTY - - - - - 0 0 0/0 - 12 VTY - - - - - 0 0 0/0 - 13 VTY - - - - - 0 0 0/0 - 14 VTY - - - - - 0 0 0/0 -

2509# The CTY line-type is the Console Port. On any router, it appears in the router configuration as line con 0 and in the output of the show line command as cty. The console port is mainly used for local system access using a console terminal. The TTY lines are asynchronous lines used for inbound or outbound modem and terminal connections and can be seen in a router or access server configuration as line x. The specific line numbers are a function of the hardware built into or installed on the router or access server. The AUX line is the Auxiliary port, seen in the configuration as line aux 0. The VTY lines are the Virtual Terminal lines of the router, used solely to control inbound Telnet connections. They are virtual, in the sense that they are a function of software - there is no hardware associated with them. They appear in the configuration as line vty 0 4. Each of these types of lines can be configured with password protection. Lines can be configured to use one password for all users, or for user-specific passwords. User-specific passwords can be configured locally on the router, or you can use an authentication server to provide authentication. There is no prohibition against configuring different lines with different types of password protection. It is, in fact, common to see routers with a single password for the console and user-specific passwords for other inbound connections. Below is an example of router output from the show running-config command: 2509#show running-config Building configuration...

Current configuration : 655 bytes ! version 12.2 . . .

!

line con 0 line 1 8 line aux 0 line vty 0 4 ! end

Configure Passwords on the Line

To specify a password on a line, use the password command in line configuration mode. To enable password checking at login, use the login command in line configuration mode. Note: To find additional information on the commands used in this document, use the Command Lookup Tool (registered customers only) . Configuration Procedure

In this example, a password is configured for all users attempting to use the console. From the privileged EXEC (or "enable") prompt, enter configuration mode and then switch to line configuration mode using the following commands. Notice that the prompt changes to reflect the current mode. router#configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)#line con 0 router(config-line)# Configure the password, and enable password checking at login. router(config-line)#password letmein router(config-line)#login Exit configuration mode. router(config-line)#end router# %SYS-5-CONFIG_I: Configured from console by console Note: Do not save configuration changes to line con 0 until your ability to log in has been verified. Note: Under the line console configuration, login is a required configuration command to enable password checking at login. Console authentication requires both the password and the login commands to work. Verify the Configuration

Examine the configuration of the router to verify that the commands have been properly entered: Certain show commands are supported by the Output Interpreter Tool (registered customers only) , which allows you to view an analysis of show command output. show running-config - displays the current configuration of the router. router#show running-config Building configuration... ...

!

! line con 0 password letmein login line 1 8 line aux 0 line vty 0 4 ! end To test the configuration, log off the console and log in again, using the configured password to access the router: router#exit

router con0 is now available

Press RETURN to get started.

User Access Verification Password:

!

router> Note: Before performing this test, ensure that you have an alternate connection into the router, such as Telnet or dial-in, in case there is a problem logging back into the router. Troubleshoot Login Failure

If you cannot log back into the router and you have not saved the configuration, reloading the router will eliminate any configuration changes you have made. If the configuration changes were saved and you cannot login to the router, you will have to perform a password recovery. See Password Recovery Procedures to find instructions for your particular platform. Configure Local User-Specific Passwords

To establish a username-based authentication system, use the username command in global configuration mode. To enable password checking at login, use the login local command in line configuration mode. Configuration Procedure

In this example, passwords are configured for users attempting to connect to the router on the VTY lines using Telnet. From the privileged EXEC (or "enable") prompt, enter configuration mode and enter username/password combinations, one for each user for whom you want to allow access to the router: router#configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)#username russ password montecito router(config)#username cindy password belgium router(config)#username mike password rottweiler Switch to line configuration mode, using the following commands. Notice that the prompt changes to reflect the current mode. router(config)#line vty 0 4 router(config-line)# Configure password checking at login. router(config-line)#login local Exit configuration mode. router(config-line)#end router# %SYS-5-CONFIG_I: Configured from console by console Note: In order to disable auto Telnet when you type a name on the CLI, configure no logging preferred on the line that is used. While transport preferred none provides the same output, it also disables auto Telnet for the defined host that are configured with the ip host command. This is unlike the no logging preferred command, which stops it for undefined hosts and lets it work for the defined ones. Verify the Configuration

Examine the configuration of the router to verify that the commands have been properly entered: show running-config - displays the current configuration of the router. router#show running-config Building configuration... !

!

! username russ password 0 montecito username cindy password 0 belgium username mike password 0 rottweiler !

!

! line con 0 line 1 8 line aux 0 line vty 0 4 login local ! end To test this configuration, a Telnet connection must be made to the router. This can be done by connecting from a different host on the network, but you can also test from the router itself by telnetting to the IP address of any interface on the router that is in an up/up state as seen in the output of the show interfaces command. Here is a sample output if the address of interface ethernet 0 were 10.1.1.1: router#telnet 10.1.1.1 Trying 10.1.1.1 ... Open

User Access Verification

Username: mike Password:

!

router

Troubleshoot User-specific Password Failure

Usernames and passwords are case-sensitive. Users attempting to log in with an incorrectly cased username or password will be rejected. If users are unable to log into the router with their specific passwords, reconfigure the username and password on the router. Configure AUX Line Password

In order to specify a password on the AUX line, issue the password command in line configuration mode. In order to enable password checking at login, issue the login command in line configuration mode. Configuration Procedure

In this example, a password is configured for all users attempting to use the AUX port. Issue the show line command in order to verify the line used by the AUX port. R1#show line

Tty Typ Tx/Rx A Modem Roty AccO AccI Uses Noise Overruns Int

• 0 CTY - - - - - 0 0 0/0 - 65 AUX 9600/9600 - - - - - 0 1 0/0 - 66 VTY - - - - - 0 0 0/0 - 67 VTY - - - - - 0 0 0/0 - In this example, the AUX port is on line 65. Issue these commands in order to configure the router AUX line: R1# conf t R1(config)# line 65 R1(config-line)#modem inout R1(config-line)#speed 115200 R1(config-line)#transport input all R1(config-line)#flowcontrol hardware R1(config-line)#login R1(config-line)#password cisco R1(config-line)#end R1#

Verify Configuration

Examine the configuration of the router in order to verify that the commands have been properly entered: The show running-config command displays the current configuration of the router: R1#show running-config Building configuration... !

!

line aux 0 password cisco login modem InOut transport input all speed 115200 flowcontrol hardware

!

! end

Configure AAA Authentication for Login

To enable authentication, authorization, and accounting (AAA) authentication for logins, use the login authentication command in line configuration mode. AAA services must also be configured. Configuration Procedure

In this example, the router is configured to retrieve users' passwords from a TACACS+ server when users attempt to connect to the router. Note: Configuring the router to use other types of AAA servers (RADIUS, for example) is similar. See Configuring Authentication for additional information. Note: This document does not address configuration of the AAA server itself. Refer to Security Server Protocols for information on configuring the AAA server. From the privileged EXEC (or "enable") prompt, enter configuration mode and enter the commands to configure the router to use AAA services for authentication: router#configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)#aaa new-model router(config)#aaa authentication login my-auth-list tacacs+ router(config)#tacacs-server host 192.168.1.101 router(config)#tacacs-server key letmein Switch to line configuration mode using the following commands. Notice that the prompt changes to reflect the current mode. router(config)#line 1 8 router(config-line)# Configure password checking at login. router(config-line)#login authentication my-auth-list Exit configuration mode. router(config-line)#end router# %SYS-5-CONFIG_I: Configured from console by console Verify the Configuration

Examine the configuration of the router to verify that the commands have been properly entered: show running-config - displays the current configuration of the router. router#write terminal Building configuration...

Current configuration: ! version 12.0 service timestamps debug uptime service timestamps log uptime no service password-encryption ! hostname router ! aaa new-model aaa authentication login my-auth-list tacacs+ !

!

... ! tacacs-server host 192.168.1.101 tacacs-server key letmein ! line con 0 line 1 8 login authentication my-auth-list line aux 0 line vty 0 4 ! end To test this particular configuration, an inbound or outbound connection must be made to the line. See the Modem - Router Connection Guide for specific information on configuring async lines for modem connections. Alternately, you can configure one or more VTY lines to perform AAA authentication and perform your testing thereupon. Troubleshoot AAA Login Failure

Before issuing debug commands, see Important Information on Debug Commands. To troubleshoot a failed login attempt, use the debug command appropriate to your configuration: debug aaa authentication debug radius debug kerberos

Robocopy Folder Sync Script

: ROBOCOPY Repository Sync Script SET SOURCE="F:\Directory\Directory" SET DEST="
server\Directory" SET DTSTAMP=%date:0,2%-%date:3,2%-%date:8,2%_%time:0,2%%time:3,2% SET LOG=F:\Directory\RepositorySyncLog.txt "C:\Program Files\Windows Resource Kits\Tools\robocopy.exe" %SOURCE% %DEST% /tee /log:%LOG% /e /purge /r:3 /zb

NLP LDA related links

Natural language processing https://en.wikipedia.org/wiki/Natural_language_processing

Apache cTakes http://ctakes.apache.org/examples.html

Snowmed Info http://systems.hscic.gov.uk/data/uktc/snomed

Powered by Apache UIMA https://cwiki.apache.org/confluence/display/UIMA/Powered+by+Apache+UIMA

Latent Dirichlet allocation https://en.wikipedia.org/wiki/Latent_Dirichlet_allocation

Latent variable (Variables which are inferred and not observed) https://en.wikipedia.org/wiki/Latent_variable

Probabilistic latent semantic analysis https://en.wikipedia.org/wiki/Probabilistic_latent_semantic_analysis

Bag-of-words model https://en.wikipedia.org/wiki/Bag-of-words_model

Explanation of LDA https://www.quora.com/What-is-a-good-explanation-of-Latent-Dirichlet-Allocation

Towards a semantic lexicon for clinical natural language processing http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3540492/

MedTagger User Guide http://ohnlp.org/index.php/MedTagger_User_Guide

Hadoop Tutorial http://www.tutorialspoint.com/hadoop/

Apache Spark Tutorial http://www.tutorialspoint.com/apache_spark/

Event Drops Timeline: https://github.com/marmelab/EventDrops

Network Level Authentication on Windows XP

When connecting to a Windows 2008 Server using remote desktop from a Windows XP client running service pack 2 or earlier, you get the following error message:

The remote computer requires Network Level Authentication, which your computer does not support.

To enable NLA in XP machines; first install XP SP3, then edit the registry settings on the XP client machine to allow NLA

• Configure Network Level Authentication

1. Click Start, click Run, type regedit, and then press ENTER.

2. In the navigation pane, locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

3. In the details pane, right-click Security Packages, and then click Modify.

4. In the Value data box, type tspkg. Leave any data that is specific to other SSPs, and then click OK.

5. In the navigation pane, locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders

6. In the details pane, right-click SecurityProviders, and then click Modify.

7. In the Value data box, type credssp.dll. Leave any data that is specific to other SSPs, and then click OK.

8. Exit Registry Editor.

9. Restart the computer.

MySQL Password Update

update user set authentication_string=password('1111') where user='root';

MySQL Max Pool Size

Add max pool size to end of connection string:

localhost;database=databasename;user id=userid;password=password;datalayer=MySql;max pool size=16

Making a dashed line in d3

Making a dashed line in d3

svg.append("path") .attr("class", "line") .style("stroke-dasharray", ("3, 3"))

svg.append("g") .attr("class", "x axis") .attr("transform", "translate(0," + height + ")") .style("stroke-dasharray", ("3, 3")) .call(xAxis);

svg.append("g") .attr("class", "y axis") .style("stroke-dasharray", ("3, 3")) .call(yAxis);

http://www.d3noob.org/2013/01/making-dashed-line-in-d3js.html

LDAP Connection Strings

Stoke Example

Connection String: LDAP:ad.xnsht.nhs.uk

LDAP Container: DC=ad,DC=xnsht,DC=nhs,DC=uk

IIS Redirect Setup

IIS Redirect Setup

https://www.iis.net/configreference/system.webserver/httpredirect

Windows Server 2012 or Windows Server 2012 R2

• On the taskbar, click Server Manager.
• In Server Manager, click the Manage menu, and then click Add Roles and Features.
• In the Add Roles and Features wizard, click Next. Select the installation type and click Next. Select the destination server and click Next.
• On the Server Roles page, expand Web Server (IIS), expand Web Server, expand Common HTTP Features, and then select HTTP Redirection. Click Next.
• On the Select features page, click Next.
• On the Confirm installation selections page, click Install.
• On the Results page, click Close.

Windows Server 2008 or Windows Server 2008 R2

• On the taskbar, click Start, point to Administrative Tools, and then click Server Manager.
• In the Server Manager hierarchy pane, expand Roles, and then click Web Server (IIS).
• In the Web Server (IIS) pane, scroll to the Role Services section, and then click Add Role Services.
• On the Select Role Services page of the Add Role Services Wizard, expand Common Http Features, select HTTP Redirection, and then click Next.
• On the Confirm Installation Selections page, click Install.
• On the Results page, click Close.

D3 Examples

D3 Tips and Tricks: https://leanpub.com/D3-Tips-and-Tricks/read

Scatterplot: http://bl.ocks.org/mbostock/3887118

Simple scatterplot with d3: http://bl.ocks.org/d3noob/38744a17f9c0141bcd04

Line Chart with Grid: http://bl.ocks.org/hunzy/11110940

Other Demos: http://bl.ocks.org/hunzy

D3 Tutorial Table of Contents: https://www.dashingd3js.com/table-of-contents

How to add an image to an svg container using D3: http://stackoverflow.com/questions/14567809/how-to-add-an-image-to-an-svg-container-using-d3-js

d3.js Specify text for x-axis: http://stackoverflow.com/questions/16179021/d3-js-specify-text-for-x-axis

Setting Scales Domains and Ranges in d3: http://www.d3noob.org/2012/12/setting-scales-domains-and-ranges-in.html

d3 Fundamentals : Understanding domain, range and scales in D3js: http://javascript.tutorialhorizon.com/2015/01/17/d3-fundamentals-understanding-domain-range-and-scales-in-d3js/

Editable Demo: http://jsfiddle.net/robdodson/KWRxW/

Drawing an SVG Rectangle using D3: https://www.dashingd3js.com/svg-basic-shapes-and-d3js

SVG Text Element: https://www.dashingd3js.com/svg-text-element

d3-time-format: https://github.com/d3/d3-time-format/blob/master/README.md#timeFormat