mount /dev/xvdd /mnt/
cd /mnt/Linux

For 32 bit:

rpm -Uhv xe*i386.rpm

For 64 bit:

rpm -Uhv xe*x86_64.rpm

Reboot the server.

wget -c http://prdownloads.sourceforge.net/webadmin/webmin-1.580-1.noarch.rpm /download

2. Install it.

rpm -Uvh  webmin-1.580-1.noarch.rpm

DECLARE @name VARCHAR(50) -- database name
DECLARE @path VARCHAR(256) -- path for backup files
DECLARE @fileName VARCHAR(256) -- filename for backup
DECLARE @fileDate VARCHAR(20) -- used for file name 

SET @path = 'D:\SQLBackups\'  

SELECT @fileDate = CONVERT(VARCHAR(20),GETDATE(),112) 

DECLARE db_cursor CURSOR FOR
SELECT name
FROM master.dbo.sysdatabases
WHERE name NOT IN ('master','model','msdb','tempdb')  

OPEN db_cursor
FETCH NEXT FROM db_cursor INTO @name   

WHILE @@FETCH_STATUS = 0
BEGIN
       SET @fileName = @path + @name + '_' + @fileDate + '.BAK'
       BACKUP DATABASE @name TO DISK = @fileName  

       FETCH NEXT FROM db_cursor INTO @name
END   

CLOSE db_cursor
DEALLOCATE db_cursor 

Set this up in Task Scheduler to to automatically execute it at a scheduled time.  The command line to call the script is something like this:

sqlcmd -S localhost -E -i D:\SQL_Scripts\sp_BackupAllDatabases.sql

http://www.symantec.com/business/support/index?page=content&id=TECH86251&actp=search&viewlocale=en_US&searchid=1327899255372

Then run through the procedures to install and configure the remote agent:

http://www.symantec.com/business/support/index?page=content&id=TECH46461&actp=search&viewlocale=en_US&searchid=1327897044799

yum install samba

After the installation is complete, check for a file called mount.cifs.  It was not installed with my server build.

/etc/mount.cifs

If it is not there, install files to support for cifs.  After doing this install, the mount.cifs file magically appeared.

yum install cifs

Create a mount point where you plan to mount the Windows share.

mkdir /mnt/win

Modify the fstab file with information that will be used to connect when your CentOS server boots up.

vi /etc/fstab

The file may end up looking something like this.

#
# /etc/fstab
# Created by anaconda on Sun Jan 29 11:02:02 2012
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=0db4ea35-aae2-4fa5-b3ab-734465f0d4f6 /                       ext4    defaults        1 1
UUID=40652af2-9ac8-47ce-b77b-f3f3ab16ff7b /boot                   ext4    defaults        1 2
UUID=4ab7e510-986b-4de7-bcbd-ed262822b06e swap                    swap    defaults        0 0
tmpfs                   /dev/shm                tmpfs   defaults        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0
//server/Share          /mnt/win                cifs    user,uid=500,rw,suid,username=username,password=P@ssw0rd,workgroup=WinDomain 0 0

Now go ahead and reboot your CentOS server. With any luck, you’ll be able to see the contents of your Windows share under the mount point created earlier.

/mnt/win

"wSS2008!"

/etc/sysconfig/network-scripts

The file corresponding to eth0 is

ifcfg-eth0

Use a text editor to make it look something like this:

DEVICE="eth0"
NM_CONTROLLED="yes"
ONBOOT=yes
TYPE=Ethernet
BOOTPROTO=none
IPADDR=192.168.1.100
PREFIX=24
GATEWAY=192.168.1.1
DNS1=192.168.1.2
DNS2=4.2.2.2
DOMAIN=domain.com
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME="System eth0"
UUID=5fb06bd0-0bb1-7ffa-44f1-d6eda65f2e03
HWADDR=00:01:01:12:34:56

After you save your changes, you’ll need to restart your network service with this command:

service network restart

You should be able to ping the address you just configured, but you might not be able to ping it from another client or even ping out.  This has to do with your firewall settings, but that’s something that will be covered in another post.

Get-WmiObject -Namespace root\virtualization -class msvm_computersystem | select elementname, operationalstatus, processid, name| ft -auto

From time to time, I need to reference this article and it always takes me a bit of time to find this specific, well written article.  To be honest, I’m a little lazy so I am reposting if  from original article here to find it quicker next time around:

Disclaimer

According to some cygwin gods, the only official document that you should use is  /usr/share/doc/Cygwin/openssh.README
which is probably true.
The purpose of this tutorial is for Windows users who are perhaps less familiar with Unix commands wanting to try out the famous Open Source ssh server (openSSH) on a desktop Windows XP .

Please don’t send any questions to the cygwin mailing list to ask questions about this page as it seems to provoke them severely. They considered and declared the instructions on this page “broken” and “random” but won’t constructively say what is “broken”; instead some went on launching personal attacks. The information here is provided “as is, in good faith” with no guarantee it will work. If it doesn’t work, then it doesn’t work. Don’t send any questions to the Cygwin mailing list to ask why and provoke them. If you must go to Cygwin mailing list to ask, you better completely remove Cygwin before you go to the mailing list to ask questions and don’t even mention that you have looked at this web page (to avoid pissing them off).
Read this Disclaimer. 

Constructive comments are of course welcome, in the original spirit of the Internet, sharing experience and knowledge regarding bug fixes and improvements to benefit other users of the Internet community.
My email address is

How to install ssh on a Windows 2000/XP on refurbished computers

How to install a ssh client(called ssh, from OpenSSH)

(1) Create a folder c:\cygwin

(2) Download cygwin’s setup.exe from http://www.cygwin.com/ and save setup.exe in c:\cygwin

Click Start…Run…and type c:\cygwin\setup.exe

When it asks for “Local Package Directory”, type c:\cygwin
When a selection screen comes up, you can resize the windows to see better,
click the little View button for “Full” view  ,
find the package “openssh”, click on the word “skip” so that an appears in Column B,
see this illustration.

Click to start installing cygwin and ssh.
Size of the basic cygwin system is about 40 Meg, this may take a while if you have a slow connection.

Take a coffee break. 

(3) Right click My Computer, Properties, Advanced, Environment Variables
See this illustration (red dots)
Click the “New” button to add a new entry to system variables:
variable name is CYGWIN
variable value is ntsec      or     tty ntsec

(4) Right click My Computer, Properties, Advanced, Environment Variables
See this illustration (green dots)
Select the Path variable and click the “Edit” button:
append  ;c:\cygwin\bin   to the end of the existing variable string.

(5) Double click the icon, a black screen will pop up.
Optional:  type
ssh-user-config this will create private and public key for the user.

You can also use putty (an excellent freeware ssh client).

Just download and run putty.exe from http://www.chiark.greenend.org.uk/~sgtatham/putty/

Disclaimer

© 2003-2009 Nicholas Fong

Last revised: January 12, 2010

http://risky.biz/RB220

Risky Busines #220 — All your Macs are belong to Snare

November 17, 2011 –

On this week’s podcast we take a look at doing some fairly unnatural things to the OS X operating system. We’ll hear how to best rootkit OS X and also how messing with EFI bootloaders can be a whole bunch of fun in terms of installing persistent rootkits in PCI firmware.

That’s this week’s feature interview, with our buddy Loukas from Assurance.com.au.

Also this week we’re joined by Tenable Network Security’s product manager Jack Daniel in the sponsor interview. He’ll be chatting to us all about Dan Geer’s new cybersecurity research agenda.

Adam Boileau, as always, joins us to chat about the week’s news.

Editor’s Note: As the CISO of In-Q-Tel, the CIA-backed strategic investment firm focused on developing technologies for the intelligence community, Dan Geer gets paid to help find the answers to big questions about computer security, national security, privacy and technology. Headlines proliferate about sophisticated cyber attacks, the looming specter of cyber warfare and ongoing espionage by nations like China and Russia. That means Dan’s job gets more important with each passing day. So what’s on Dan Geer’s mind these days? We asked him what questions he was mulling and, as usual, the answers we got back were both eye-opening and provocative. Here, in Monday morning ‘shot of espresso’ format (and with as little editing as possible) is our three minute speed date with Dan’s brain.

The challenge: In three minutes, give the research agenda in cybersecurity.

We would need a lot less research if we put into practice what we already know. But we don’t. Ergo, why we don’t put into practice what we already know is itself a research-grade topic.

We humans can build structures more complex than we can then operate. (The financial industry has just proven this by https://threatpost.com/en_us/blogs/new-cybersecurity-research-agenda-three-minutes-or-less-110711example.) Cyberspace is on track to prove the same thing to us all over again, which leads to the research question: Are humans in the loop a failsafe or a liability? Is fully automated security to be desired or to be feared? Is there a simple metric that differentiates the desirable from the frightening?

Security is not composable. However, in cyberspace, everything critical is a melange. Gilbert and Lynch’s proof of Brewer’s theorem finds that in a distributed system it is Consistency, Availability, and Partition Tolerance, choose any two. That tells me there is a research grade result for cybersecurity that will be found to be parallel.

In the 1990s, the commercial world pulled even with the military world in the application of cryptography. It is now doing the same with traffic analysis (heretofore the strategic redoubt of the intelligence community). While the intelligence community has had the pre-eminent sensor fabric, integrated messaging coupled to geo-location technology is the stuff of hegemony. This is a fact which is not lost on Russia, is not lost on China, and one hopes is not lost on Google. Is resistance to traffic analysis a research grade question, or is it merely wishful thinking?

The security implications of the conversion to IPv6 are poorly understood. The security impact of the move to IPv6 will be felt one step beyond the IPv6 address, at the interface between an impossibly large Internet address space and a nearly infinite, but intermittently tethered Internet-of-things. IPv6′s simultaneous multi-homing and address-hopping along with consumer-grade multi-channel routers mean network discovery as a cybersecurity tool is dead. As a research topic, what replaces network discovery as a management tool, or is consumerization the end of bothering to try?

All security technologies are dual use. Does anyone want to prove otherwise?

For cybersecurity, solving known problems is not research. Figuring out what the problems will be — that’s research. You have three minutes.