Creating a New Linux Distro

Reference
http://www.linuxjournal.com/article/7233

Resetting / By passing OS X login password

Resetting / By passing OS X login password
1. Reboot
2. Hold apple + s down after you hear the chime.
3. When you get text prompt enter in these terminal commands to create a brand new admin account (hitting return after each line):
* mount -uw /
* rm /var/db/.AppleSetupDone
* shutdown -h now
4. After rebooting you should have a brand new admin account. When you login as the new admin you can simply delete the old one and you’re good to go again!


**************************************************************************

If the Mac is in Read only mode:
Resetting PRAM and NVRAM
1. Shut down the computer.
2. Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in step 4.
3. Turn on the computer.
4. Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
5. Hold the keys down until the computer restarts and you hear the startup sound for the second time.
6. Release the keys.

Ref: http://illshare.wordpress.com/2008/06/01/how-to-resset-administrator-password-mac-os-x/

DNS and WINS

The main difference between WINS and DNS is that WINS is typically dynamic and DNS is static. WINS contains Windows-only devices, specifically PC's and NT servers, DNS typically does not contain any PC's, it usually has servers

and sometimes network equipment only, but it is multi-platform (Unix Windows, Cisco, Netware, etc.). Wins is used specifically for Netbios name resolution (to IP address); DNS is used for host name to IP address resolution.

When a Windows PC starts up on the network it announces itself by broadcasting a message with its name to see if any other computer on the network is already using that name as well as broadcasting its shared resources. WINS enables NetBEUI network clients to access name databases using point-to-point communication modes that are routable.
Clients connect to the WINS server through an IP address allowing them to communicate beyond their local subnet through a router. Without WINS netbeui will not communicate past its local subnet (over a router). WINS cannot be used by other OS?s only windows.
How to install WINS on NT Server 4.0 ·
Right Click on Network Neighborhood and click on Properties ·
Select the Services and click on Add ·
In the Network service box select Windows Internet Name Service ·
Windows will probably ask for your CD to install files ·
Restart your PC and set your clients to
Configuring your WINS Server ·
You should find WINS Manager in the Network Admin group ·
Click on Server and then Configuration You will have the following options to configure: ·
Renewal Interval how often a WINS client must reregister its name usually 1 to 2 days but not more than 4 days · Extinction Interval specifies the interval between when a name is released and when it is extinct · Extinction Timeout tells you how long after a name is marked extinct that the name is actually purged from the database · Verify Interval specifies the interval after a WINS server must verify that names it does not own are still active. · Check on logging to log to jet.log
To run an efficient WINS network you should have a WINS server different segments of your network as well as WINS proxys. Two WINS servers can utilize the push pull method of database replication. A push replication tells the other WINS servers of changes and sends database replicas upon receiving a request from a pull partner. A pull partner is a WINS server that requests replication data from a push partner. To configure replication choose replication partners in the server menu of the WINS configuration menu. Select another WINS server in the Replications partners dialog box. The WINS database is stored in WINS.mdb. WINS also uses System.mdb that holds structure of the WINS database.
As shown above each domain can be divided into subdomains or children of their parent domains. Your domain name also identifies where your position in the database is. Before the implementation of DNS, the use of names to locate resources on TCP/IP networks was supported by using a name resolution method based on files known as HOSTS files. Each HOSTS file contained a list of host (computer or other TCP/IP network device) names and their associated IP addresses.
This is fine on a small network but on a network as large as the internet this is unmanageable. Berkeley Internet Name Domain (BIND) - this was originally used by BSD 4.3. Really the difference between BIND and DNS is like comparing SuSE to Red Hat. Aside from the fact that SuSE kicks ASS.. (Basically different flavors of the same product) Usually BIND was only used on different Unix machines now it can be found on Windows NT. I think it comes with the Resource Kit for NT 4. See your UNIX sysadmin and ask about BIND its pretty ***** cool. I have the whole printout from my work! Microsoft Windows 2000 now uses DDNS (dynamic DNS with additions for specialized characters that Microsoft uses) for its name resolution. One would be correct to question why there are two separate, but almost identical services. (WINS and DNS) Microsoft also recognized the similarity and changed the way Windows works. There is a hierarchy that NT and Windows PC's use for netbios name resolution. They typically check WINS, then DNS, then local host files (2 of them), then do a broadcast over the network. The order has changed between different version of NT and Windows and even with different service packs, so I can't be absolutely specific. Sometimes DNS is first.
Further Reading DNS RFCs 1033, 1034, 1035, 1101, 1123, 1183, and 1536
DDNS RFCs 1995,2136

Reference:

Haven_97@hotmail.com

http://www.hackinthebox.org/modules.php?op=modload&name=News&file=article&sid=502

WINS is an implementation of the NetBIOS P-node server. What this means is that Windows PCs can find each other on the network by registering themselves with a centralized server, then asking that server about other PCs.

Contrast with NetBIOS

NetBIOS was developed in the mid-1980s by IBM, Sytek, and Microsoft. Its purpose was to allow PCs to communicate over a local area network, especially IBM's 3mbps Ethernet-like cable service as well as IBM's later Token Ring LANs.

It allows NetBIOS-aware applications to communicate regardless of the underlying infrastructure. For example, on the older Windows PCs, you have the choice of installing NetBEUI (NetBIOS raw over Ethernet) or NetBIOS over Novell's IPX. Yet another option is NetBIOS over TCP/IP.

WINS is just a component of the NetBIOS over TCP/IP implementation. It is not used with NetBIOS over any other transport.

Contrast with DNS

WINS is similar to DNS: both systems will resolve a name into an IP address. DNS solves the general Internet naming problem, WINS is designed only for NetBIOS names. It is only used in the cases where NetBIOS applications (such as Windows File and Print Services) need to talk to each other.

However, Microsoft makes "helper" services. If you need a DNS name but one cannot be found, Windows will lookup the name in the WINS server. Similarly, if a NetBIOS name cannot be found in the WINS server, Windows will attempt to lookup the name in the DNS server. This means that while WINS and DNS have completely different heritages that know nothing of each other, they effectively become interchangeable.

WINS vs. no-WINS

WINS isn't necessary for all communication. NetBIOS has been designed around a "broadcast" mechanism. The default Windows behavior is to simply broadcast information on the local network. Installing a WINS server (and configuring the clients to use it) will reduce broadcast traffic. Also, since broadcasts do not travel across subnets, WINS may be the only way that two distant machines can find each other.

Reference

http://www.iss.net/security_center/advice/Services/Directory/WINS/default.htm

WINS	DNS
The purpose is to resolve NetBIOS names to IP addresses.	The purpose is to resolve host names to IP addresses.
Names are flat and 15 characters long.	Names are hierarchical in nature.
Name registration is dynamic and happens automatically.	Name registration is static and has to be done manually.
Supports incremental replication of the data, which means that only changes in the database are replicated between WINS servers.	Doesn't support incremental replication of data between DNS servers. This means the whole database has to be replicated every time.
Supports DHCP.	Doesn't support DHCP.
Doesn't support email routing or additional TCP/IP application services.	Supports other TCP/IP application services such as email routing.

Creating Root Account

Assuming you need to create a backup root account, this account can be created via the following steps.

1) Create a new user account as per normal (adduser )
2) Edit the /etc/passwd file to modify the UID and GID of user
From this
dsmadm:x:101:1:This user accound used for NBU :/export/home/dsmadm/:/bin/ksh
To
dsmadm:x:0:0:This user accound used for NBU :/export/home/dsmadm:/bin/ksh

3) Change the file/directory permission for . This is to prevent anyone from putting harmful scripts where you might run them unintentionally. You also need to secure this account as you would a normal "root" account.

chown 0:0 /export/home/dsmadm
chown -R 0:0 /export/home/dsmadm/*
chmod 700 /export/home/dsmadm



=================For Fedora===============

Create extra root user account to your Linux box.

The ‘root’ account with user id 0 is the most powerful user in Linux and Unix system. This article show the step by step to create the duplicate root account that have the same privileges as super user root account on the Linux Fedora Core operating system.

You may want to make replicate of root user account, or to create more than one user account that have the same capabilities as a 'root' user (superuser) account. Why, may be for a root backup user account, incase of something happen to the 'root' user account or may be just for fun :-).

To create another root user account, we need to replicate the 'root' user account characteristic, then make one account that have the same characteristic and capabilities of the 'root' user account.

Let begin by check the 'root' user account.

1. Check user id for ‘root’ user account:

[root@fedora ~]# id root

uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel)

Explanations of the command output:

A. uid=0(root) The user id for user 'root' user is 0.

B. gid=0(root) the group id for user ‘root’ is 0.

C. groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel) The user ‘root’ is belong in groups; root, bin, daemon, sys, adm, disk and wheel.

2. Now we take a look at the passwd, shadow and group files that contain ‘root’ user information:

[root@fedora ~]# less /etc/passwd

root:x:0:0:root:/root:/bin/bash

[root@fedora ~]# less /etc/shadow

root:$1$B2BEWv4X$Gb.QPb6I3RwCkEkz13ow21:13080:0:99999:7:::

[root@fedora ~]# less /etc/group

root:x:0:root

bin:x:1:root,bin,daemon

daemon:x:2:root,bin,daemon

sys:x:3:root,bin,adm

adm:x:4:root,adm,daemon

tdisk:x:6:root

wheel:x:10:root

From the information gather above, to create a user that have the same power (superuser power) as a ‘root’ user in Linux system, we need to create a user with same root user uid, gid and group.

3. To create user account that has the same ability (super user) as the ‘root’ user, issue this command:

[root@fedora ~]# adduser -u 0 -o -g 0 -G 0,1,2,3,4,6,10 -M root2

Adduser command explanations:

adduser	-u 0 -o	-g 0	-G 0,1,2,3,4,6,10	-M	root2
Using Linux adduser command to create a new user account or to update default new user information.	Set the value of user id to 0.	Set the initial group number or name to 0	Set supplementary group to: 0 = root 1 = bin 2 = daemon 3 = sys 4 = adm 6 = disk 10 = wheel	'home directory' not created for the user.	User name of the new user account.

Note: you need to have the administrative privilege on the system in order to issue 'adduser' command above.

4. Now add a password for user ‘root2’ by issue the ‘passwd root2’ command, see example below:

[root@fedora ~]# passwd root2

Changing password for user root2.

New UNIX password:

Retype new UNIX password:

passwd: all authentication tokens updated successfully.

Note: you need to have the administrative privilege on the system in order to issue 'passwd' command above.

5. Check id for user root2 by issue the ‘id root2’ command, see example below:

[root@fedora ~]# id root2

uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel)

6. Now recheck the passwd, shadow and group files that contain ‘root2’ user informations to confirm the changes:

[root@fedora ~]# less /etc/passwd

root:x:0:0:root:/root:/bin/bash

root2:x:0:0::/home/root2:/bin/bash

[root@fedora ~]# less /etc/shadow

root:$1$B2BRWv4X$Gb.MPc6I3RwCkEkT13ow21:13080:0:99999:7:::

root2:$1$bQHGH4cX$TtsV/WVdFe5cIsHWjzc.N1:13112:0:99999:7:::

[root@fedora ~]# less /etc/group

root:x:0:root,root2

bin:x:1:root,bin,daemon,root2

daemon:x:2:root,bin,daemon,root2

sys:x:3:root,bin,adm,root2

adm:x:4:root,adm,daemon,root2

disk:x:6:root,root2

wheel:x:10:root,root2

7. Everything should be ok, now try to login to system with newly created ‘root2’ account, see example:

login as: root2

root2@10.7.0.211's password:

Last login: Thu Nov 24 23:48:49 2005 from 10.7.0.112

Could not chdir to home directory /home/root2: No such file or directory

-bash-3.00#

-bash-3.00#

-bash-3.00# su –

[root@fedora ~]#

8. Make sure that you execute the su command with hyphen ( su - ) to get the PATH of the user that you become to... below is the example of the su command with hyphen and without hyphen.

Loggin in as user tenouk, then execute $PATH as example below.

[tenouk@fedora ~]$ $PATH

-bash: /usr/lib/qt-3.3/bin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/home/ tenouk/bin: No such file or directory

[tenouk@tenouk ~]$

Use the su command to change to root user as example below and then execute $PATH as example below.

[tenouk@fedora ~]$ su root

Password:

[root@fedora tenouk]# $PATH

bash: /usr/kerberos/sbin:/usr/lib/qt-3.3/bin:/usr/kerberos/bin:/usr/local/bin:/b in:/usr/bin:/home/tenouk/bin: No such file or directory

[root@fedora tenouk]#

Then try use the su - command and verify with the $PATH as example below.

[root@tenouk tenouk]# su - root

[root@tenouk ~]# $PATH

-bash: /usr/lib/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin: /usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin: No such file or director y

[root@tenouk ~]#

Note: The execution of su command, without the hypen ( - ) you inherit the PATH of the current user. Use the su command, with hyphen ( su - ) to get the default PATH of the root user.

Step-by-step how to procedure above tested on:

Operating System: GNU/Linux Fedora Core 4

Kernel Name: Linux

Kernel Release: 2.6.11-1.1369_FC4

Kernel Version: #1 Thu Jun 2 22:55:56 EDT 2005

Machine Hardware: i686

Machine Processor: i686

Hardware Platform: i386

Shell: GNU bash, version 3.00.16(1)-release (i386-redhat-linux-gnu)

Installation Type: Full Installation (Custom)

SELinux: Disable

Ref: http://www.labtestproject.com/create_root_user_account

Cloning Mac HDD

Tools required
1) SuperDuper!
2) Winclone
3) New HDD
4) NTFS-3G_1.2310-stable-catacombae.dmg

Note:
Mac OS X can boot from external HDD. Hence, after cloning the Mac OS X partition to an external HDD, you can verify that the HDD is good to go by booting from it before swapping the external HDD with the internal HDD.

Partition the new HDD. My recommendation is 3 partitions. First partition for Mac OS X, second partition for Windows(Bootcamp). I would recommend a small partition for this as you can always mount this partition to in vmware. And lastly, the final partition as a NTFS partition. The last partition is used to store data to be exchanged between Mac OS X and Windows. This is because Mac OS X cant read from the Windows(Bootcamp) partition when mounted in vmware. As such, the final partition would act as an intermediate partition to exchange data between the 2 OSes.

Install the NTFS plugin to enable Mac OS X to write onto the final partition.
*Recommended to change the existing bootcamp partition into NTFS to enable Winclone to copy the bootcamp partition and clone it to a larger partition. If left as FAT32, the new Windows bootcamp partition is limited to the same storage capacity as the original bootcamp partition.

1) Use SuperDuper to clone the existing Mac OS X partition to the new partition. This might take a while. FYI, 60Gb partition cloning took 1 hour ++.

2) Use Winclone to create an image of the windows bootcamp partition. Restore this image to the new partition. You can delete the image after restoration.

3) Reboot to test out the cloned partitions and swap the HDDs.

WiFi Quiz

1) What is SSID ?
2) What is MAC Filtering ?
3) MAC filtering constraints, eg Access point memory size, not scalable, have to configure each Access Point, MAC can be spoofed
4) What is WEP/WPA?

Ophcrack

Tools used to create USB Ophcrack:

• Windows Computer (Windows XP is used here)
• 512 MB or larger portable device (USB stick)
• Ophcrack Live CD and usboph.zip

Creating bootable USB Ophcrack:

1. First, create a "New Directory" to house your work
2. Download Ophcrack Live CD to the new directory
3. Download and extract usboph.zip to the new directory
4. Click fixoph.bat and follow the onscreen instructions
5. Copy all the files from the Ophcrack directory to your USB device
6. From your USB device, click makeboot.bat and follow the instructions to make the drive bootable
7. Reboot your PC and set your BIOS boot menu to boot from the USB device

If all goes well, you should be booting from the USB stick into a mini SLAX environment. Ophcrack is launched automatically after boot.

----------------------------------------------------------------------------------

How to fix Could not find kernel image: linux error:

Use the following troubleshooting guide to assist in fixing the error.

1. Make sure that the syslinux.cfg file exists on the USB flash drive. Depending on which version of linux you have installed to your flash drive, the syslinux.cfg file should be found at the root of the drive or within the /boot/syslinux or /syslinux directory
2. If a file named isolinux.cfg exists and syslinux.cfg does not, rename isolinux.cfg to syslinux.cfg
3. If the syslinux.cfg file does exist and your still encountering the error, open the syslinux.cfg file with a text editor and make sure that the paths to your kernel and initrd files are correct.

Source:

http://www.pendrivelinux.com

Microsoft Clustering

Clustering Basics

Before I can really talk about what a quorum is and what it does, you need to know a little bit about how a cluster works. Microsoft server products support two main types of clustering; server clusters and network load balancing (NLB). The design philosophy behind these two types of servers couldn’t be more different, but the one thing that both designs share is the concept of a virtual server.

There are several different meanings to the term virtual server, but in clustering it has a specific meaning. It means that users (and other computers) see the cluster as a single machine even though it is made up of multiple servers. The single machine that the users see is the virtual server. The physical servers that make up the virtual server are known as cluster nodes.

Network Load Balancing

These two different types of clusters have two completely different purposes. Network Load Balancing is known as a share all cluster. It gets this name because an application can run across all of the cluster’s nodes simultaneously. In this type of cluster, each server runs its own individual copy of an application. It is possible that each server can link to a shared database though.

Network Load Balancing clusters are most often used for hosting high demand Web sites. In a network load balancing architecture, each of the cluster’s nodes maintains its own copy of the Web site. If one of the nodes were to go down, the other nodes in the cluster pick up the slack. If performance starts to dwindle as demand increases, just add additional servers to the cluster and those servers will share the workload. A Network Load Balancing cluster distributes the current workload evenly across all of the cluster’s active nodes. Users access the virtual server defined by the cluster, and the user’s request is serviced by the node that is the least busy.

Server Clusters

The other type of cluster is simply known as a server cluster. A server cluster is known as a share nothing architecture. This type of cluster is appropriate for applications that can not be distributed across multiple servers. For example, you couldn’t run a database server across multiple nodes because each node would receive updates independently, and the databases would not be synchronized.

In a server cluster, only one node is active at a time. The other node or nodes are placed in a sort of stand by mode. They are waiting to take over if the active node should fail.

As you may recall, I said that server clusters are used for applications that can not be distributed across multiple nodes. The reason that it is possible for a node to take over running an application when the active node fails is because all of the nodes in the cluster are connected to a shared storage mechanism. This shared storage mechanism might be a RAID array, it might be a storage area network, or it might be something else. The actual media type is irrelevant, but the concept of shared storage is extremely important in understanding what a quorum is. In fact, server clusters is the only type of clustering that uses quorums. Network load balancing does not use quorums. Therefore, the remainder of this discussion will focus on server clusters.

What is a Quorum?

OK, now that I have given you all of the necessary background information, let’s move on to the big question. What is a quorum? To put it simply, a quorum is the cluster’s configuration database. The database resides in a file named \MSCS\quolog.log. The quorum is sometimes also referred to as the quorum log.

Although the quorum is just a configuration database, it has two very important jobs. First of all, it tells the cluster which node should be active. Think about it for a minute. In order for a cluster to work, all of the nodes have to function in a way that allows the virtual server to function in the desired manner. In order for this to happen, each node must have a crystal clear understanding of its role within the cluster. This is where the quorum comes into play. The quorum tells the cluster which node is currently active and which node or nodes are in stand by.

It is extremely important for nodes to conform to the status defined by the quorum. It is so important in fact, that Microsoft has designed the clustering service so that if a node can not read the quorum, that node will not be brought online as a part of the cluster.

The other thing that the quorum does is to intervene when communications fail between nodes. Normally, each node within a cluster can communicate with every other node in the cluster over a dedicated network connection. If this network connection were to fail though, the cluster would be split into two pieces, each containing one or more functional nodes that can not communicate with the nodes that exist on the other side of the communications failure.

When this type of communications failure occurs, the cluster is said to have been partitioned. The problem is that both partitions have the same goal; to keep the application running. The application can’t be run on multiple servers simultaneously though, so there must be a way of determining which partition gets to run the application. This is where the quorum comes in. The partition that “owns” the quorum is allowed to continue running the application. The other partition is removed from the cluster.

Types of Quorums

So far in this article, I have been describing a quorum type known as a standard quorum. The main idea behind a standard quorum is that it is a configuration database for the cluster and is stored on a shared hard disk, accessible to all of the cluster’s nodes.

In Windows Server 2003, Microsoft introduced a new type of quorum called the Majority Node Set Quorum (MNS). The thing that really sets a MNS quorum apart from a standard quorum is the fact that each node has its own, locally stored copy of the quorum database.

At first, each node having its own copy of the quorum database might not seem like a big deal, but it really is because it opens the doors to long distance clustering. Standard clusters are not usually practical over long distances because of issues involved in accessing a central quorum database in an efficient manner. However, when each node has its own copy of the database, geographically dispersed clusters become much more practical.

Although MNS quorums offer some interesting possibilities, they also have some serious limitations that you need to be aware of. The key to understanding MNS is to know that everything works based on majorities. One example of this is that when the quorum database is updated, each copy of the database needs to be updated. The update isn’t considered to have actually been made until over half of the databases have been updated ((number of nodes / 2) +1). For example, if a cluster has five nodes, then three nodes would be considered the majority. If an update to the quorum was being made, the update would not be considered valid until three nodes had been updated. Otherwise if two or fewer nodes had been updated, then the majority of the nodes would still have the old quorum information and therefore, the old quorum configuration would still be in effect.

The other way that a MNS quorum depends on majorities is in starting the nodes. A majority of the nodes ((number of nodes /2) +1) must be online before the cluster will start the virtual server. If fewer than the majority of nodes are online, then the cluster is said to “not have quorum”. In such a case, the necessary services will keep restarting until a sufficient number of nodes are present.

One of the most important things to know about MNS is that you must have at least three nodes in the cluster. Remember that a majority of nodes must be running at all times. If a cluster only has two nodes, then the majority is calculated to be 2 ((2 nodes / 2) +1)-2. Therefore, if one node were to fail, the entire cluster would go down because it would not have quorum.

• Section: Articles & Tutorials :: Windows 2003
• Author: Brien M. Posey

Blat

@echo off :: You must change the next 3 values
@echo off
set to=-to username@company.com
set f=-f santa@northpole.com
set server=-server mail.company.com

set subject=-subject "Helloworld"
set body=-body "Good day"
set attach=-attach blat.dll
set html=-html
@echo off :: Here is where we run Blat.
@echo off :: Note, I named the vars the same as Blat's paramaters.


@echo off REM blat soccer.html %to% %f% %subject% %server% %html%
blat %to% %f% %subject% %body% %server% -noh2 -dsn n -hostname bing.com

Windows Batch Files

echo off
set cmd1="date/t"
set cmd2="time/t"

for /F "delims=*" %%z in (filecount.txt) do set/a param3=%%z
set/a param3=%param3%+1
echo %param3% > filecount.txt

for /F "delims=*" %%a in ('%cmd1%') do set param1=%%a
for /F "delims=*" %%b in ('%cmd2%') do set param2=%%b

echo param1 = %param1%
echo param2 = %param2%

echo %param1%, %param2% >> Num_%param3%.txt


--------------------------------END-----------------------------------

A file called filecount.txt must first exist. It should contain a number.

Net and SC Commands

Start windows services from command line
1) net start telnet , net stop "apache2"
2) sc
3) sc query "apache"
4) sc query group=""
5) sc query state= all or sc query statr= inactive *there is a space after =
6) sc query type= driver or sc query type= service
7) sc qc "apache"
8) sc start "apache"

Creating an executable file

The main usage of this is to create an executable file from a batch file to mask certain user credentials used in the batch file. A rather primitive way of obfuscating information but its better than storing a batch file where anyone can see the user credentials in plaintext.

Step 1
Navigate to C:\Windows\System32 and locate the file named IEXPRESS.EXE

Step 2
Double Click to launch IEXPRESS.EXE

Step 3
You will be presented with the initial welcome screen and be given two choices. Select “Create new Self Extraction Directive file.” Click Next.

Step 4
Next you will be presented with the Package Purpose screen. For our purposes select “Extract Files and run an installation command” and click the Next button.

Step 5
You will be presented with the Package Title screen, which will give you the opportunity to give your project a name. If you are so inclined give it a meaningful name. If like me you are never going to come back to this, name it whatever you want.

Step 6
You will next be presented with the Confirmation Prompt Screen. We would like the batch file to just be extracted and run so just choose “No Prompt” and click the Next Button.

Step 7
You are presented with the License Agreement window. If you don’t want your users to have to answer a prompt select “Do not display a license.”

Step 8
The Packaged Files window is where you will select your batch file (or .vbs). Click the Add button and browse to your desired file. Then click next.

Step 9
Here you are presented with a window titled Install Program to Launch. Use the drop down control next to “Install Program and choose the only option that will be present, the .bat or .vbs file that you chose in the previous window.

Step 10
The Show Window screen is next. I didn’t want my users to be prompted in any way so I chose Hidden. Click Next.

Step 11
No Finished Message for my users. Select “No message” and choose Next.

Step 12
The Package Name and Options window is where the new .exe specified. Type in a path or browse to the folder you would like your .exe in, type a name in the file name box and click save. Also check the box that says “Hide File Extraction Progress Animation from User.” If you’re worried about long file names go ahead and click the other box as well.

Step 13
Since we really aren’t installing anything we probably want to tell the Configure Restart window to not restart. So choose the option that says “No restart” and hit Next.

Step 14
This window is where you have a chance to save all of the options you have chosen into a project file so that if necessary you may later return and make modifications. I have no need to retain the file, but if you would like to be able to come back to it, by all means choose “Save Self Extraction Directive (SED) file” and tell it where to put it. As always, click Next.

Step 15
Here’s where you’re new .exe is born, on the Create Package screen. Explore to the directory you told it to put the file in, click Next and then watch your little .exe’s first moments as it pops into the big digital world.

Step 16
You’re done! Click finish and go try it out. Pin it directly to the start menu. Point a shortcut to it and pin that to the start menu. Most importantly, script it and see how slick it is. If you’re not familiar with how to script start menu pinning the scripting guys will tell you how.

*Ref: http://renegadetech.blogspot.com/2006/07/how-to-convert-bat-file-or-vbs-file.html