Tag Archive : windows

/ windows

Installing DNS Server on Windows Server 2012

December 11, 2015 | Article | No Comments

Domain Name System (DNS) is a hierarchical distributed naming system for computers, services, or any resource connected to the Internet or a private network. It associates various information with domain names assigned to each of the participating entities. Most prominently, it translates easily memorized domain names to the numerical IP addresses needed for the purpose of locating computer services and devices worldwide. By providing a worldwide, distributed keyword-based redirection service, the Domain Name System is an essential component of the functionality of the Internet.

Windows Server 2012 use it’s own DNS server program, named Microsoft DNS. This is the default on any Windows Server.

Like any service on Windows Server 2012, Microsoft DNS is implemented as server role. This article will discuss about how to install DNS service in Windows Server 2012.


Open “Server Manager” from task bar, if you have not opened it yet.

From “Server Manager” Dashboard, select “Add roles and features”. This will launch the Roles and Features Wizard allowing for modifications to be performed on the Windows Server 2012 instance.


Select “Role based or features-based” installation from the Installation Type. Roles are the major feature sets of the server, such as IIS. Features provide additional functionality for given role.


When asked for destination server, select the current server. It should be chosen by default. Click “Next” button to proceed.


From the Server Roles, choose the option “DNS Server” by checking it. A notice will appear explaining additional roles services or feature are also required to install domain services.


If you don’t set your machine using static IP address, you will get a warning message. Make sure you set your machine to static IP address so client can resolve your machine. However, you can always ignore it and go to next stage for installation.


Now we will be brought to “Features” page. Review and select optional features to install during installation of DNS Server. You can check any features but we will leave it as is.

Review the information. Click Next.


Review the installation. This page will show you information about what will be installed. When ready, press “install” button.


Installation will take on. It should not be long, but that will depend on your machine. In installation process, a progress bar will be displayed on the screen. Once Active Directory role is installer, it will be displayed on the ‘Server Manager’ landing page.


By default, whenever we boot Windows Server 2012 we will be asked to press ctrl + alt + del on logon screen. Sometimes this is annoying and fortunately we can remove it so we can start typing the username and password without pressing ctrl+alt+del.

In this article we will discuss about how to disable Ctrl+Alt+Del prompt.

The Idea

Everytime we login we need to press Ctrl+Alt+Del. This policy is defined by Windows on “Local Security Policies” and can be disabled manually.

How to Enable

Open the “Start” screen, click “Administrative Tools”.


Double click the “Local Security Policy” icon, expand Local Policies and click Security Options. In the right pane search and open”Interactive logon: Do not require CTRL+ALT+DEL” and choose “Enabled“. Save the policy change by clicking OK.


Enable Sound on Windows Server 2012

December 11, 2015 | Article | No Comments

By default, Windows Server 2012 disables audio. This of course has a reason. Most servers won’t need it. However, you can always enable manually or make it enable by default.

In this article we will discuss about how to enable sound on Windows Server 2012.

The Idea

Sound is a service. Like any other service, it can be manually started or we can set it enabled automatically on every boot time.

How to Enable

Go to Services window. There are two ways to do that. First: Open the “Start” screen, click “Administrative Tools” and open the “Services” shortcut. Second: press CTRL+R (opening Run dialog) and type “services.msc“.

You will see a window for Services.


Search for “Windows Audio” service and double click it (or press enter button on it). We will be presented by another window.

If we want it to enable for only this time, click on “Start” button. If you want it to run automatically, set its “Startup type” to “Automatic“. Repeate this process for “Windows Audio Endpoint Builder” service. If you want to use audio immediately, also click the Start button in the Properties window of both services in addition to changing the Startup type.


Active Directory (AD) is Microsoft’s implementation of directory service for Windows domain network. It uses Lightweight Directory Access Protocol (LDAP) version 2 and 3, Microsoft’s version of Kerberos, and DNS.

Active Directory is used on Windows Server. Usually a dedicated server for Active Directory is referred as Domain Controller. A Domain Controller authenticates and authorizes all users and computers in a Windows domain type network. It also assign and enforce security policies for all computers and installing or updating software.

In a network, there should be only one Active Directory Domain Controller. Or, at least there is one master and only two slave Domain Controller at maximum for load balancing.

Like any service on Windows Server 2012, Active Directory Domain Service (AD DS) is implemented as server role. This article will discuss about how to install Active Directory in Windows Server 2012.


Open “Server Manager” from task bar, if you have not opened it yet.

From “Server Manager” Dashboard, select “Add roles and features”. This will launch the Roles and Features Wizard allowing for modifications to be performed on the Windows Server 2012 instance.


Select “Role based or features-based” installation from the Installation Type. Roles are the major feature sets of the server, such as IIS. Features provide additional functionality for given role.


When asked for destination server, select the current server. It should be chosen by default. Click “Next” button to proceed.


From the Server Roles, choose the option “Active Directory Domain Services” by checking it. A notice will appear explaining additional roles services or feature are also required to install domain services.


There are other options including, Certificate services, federation services, lightweight directory services and rights management. Domain Services is the glue that holds this all together and needs to be installed prior to these other services.

Now we will be brought to “Features” page. Review and select optional features to install during installation of Active Directory. You can check any features but we will leave it as is.

Review the information. Click Next.


Review the installation. This page will show you information about what will be installed. When ready, press “install” button.


Installation will take on. It should not be long, but that will depend on your machine. In installation process, a progress bar will be displayed on the screen. Once Active Directory role is installer, it will be displayed on the ‘Server Manager’ landing page.



Once Active Directory Domain Service is installed on the server, we can start configuring our domain. I will assume that this is your first time configuring.

Open the “Server Manager”, if you have not opened it yet.

Open the Notification Pane by selecting the notification icon from the top of the Server Manager. It looks like a flag, and should have an exclamation mark on it. From the notification regarding configuring Active Directory, click “Promote this server to a domain controller”.


From the Deployment Configuration tab select “Add a new forest” from the radial options menu. Insert your root domain name into the “Root domain name” field. For example, I will use “windev.xathrya.id”.


Review and “select a Domain and Forest functional level”. Once selected “fill in a DSRM password” in the provided password fields. The DSRM password is used when booting the Domain Controller into recovery mode.


We will be presented by a warning. Review the warning on the DNS Options tab and select Next. If you don’t have DNS server yet, this is the outcome, otherwise you are given option to add new DNS delegation. Either way, click Next after you have done.


Confirm or enter a NetBIOS name and click Next.


Configure the location of the SYSVOL, Log files, and Database folders. Click Next when done.


Review the configuration options and click Next.


The system will check to ensure all necessary prerequisites are installed. This would be done before moving moving forward to real configuration stage. Once the system passes the check, we will proceed by clicking “Install”.


Once the server is done, reboot. Now we have successfully installing and configuring an Active Directory Domain Services on Windows Server 2012.

Things You Need to Install After Windows Server

December 11, 2015 | Article | No Comments

You have install Windows Server, so what’s next? Of course we need some “arms”, in our context its utility software. In this article, we will discuss about some application that might be need.

We classified the application into some categories. They are:

  1. File Archiver & Compressor
  2. PDF Reader
  3. Browsers
  4. Text Editor
  5. Office Suite
  6. ISO Tool
  7. SSH Server
  8. VNC Server & Client

File Archiver & Compressor

A file archiver is a computer program that combines a number of files together into one archive file, or a series of archive files, for easier transportation or storage. File archivers may employ lossless data compression in their archive formats to reduce the size of the archive.

There are many archive formats, such as: zip, rar, 7z, tar.gz, tar.bz2, etc.

We need file archiver for to create, open, extract, and modify an archive file. There are many solutions out there but my choice would be 7-Zip.

7-Zip is an open source file archiver. 7-Zip operates with the 7z archive format, but can read and write several other archive formats. The program can be used from a command line interface, graphical user interface, or with a window-based shell integration.

For downloading 7-Zip, you can go to 7-Zip official site.

PDF Reader

PDF or Portable Document Format is a file format used to represent documents in a manner independent of application software, hardware, and operating system. Developed by Adobe Systems, PDF now evolved into most popular document format.

Having PDF reader on our server can benefit us as some document might end in PDF, such as: datasheet, documentation, etc.

There are many PDF reader out there. Anyone should be no problem.


Browser, or web browser, is a application for retrieving, presenting, and traversing information resources on the World Wide Web. In other world, enable us surf the internet.

The major web browsers are Google Chrome, Mozilla Firefox, Internet Explorer, Opera, and Safari.

Even though the Windows Server 2012 has shipped Internet Explorer as default web browser, but for some people, using some familiar web browser is comforting.

Text Editor

Windows Server has Notepad, so what’s wrong? No it’s not wrong, but it’s not enough!

We need some text editor, but not only a text editor. We need text editor with extra capability, for example: syntax highlighting. Why we need that? Sometimes we are working with configuration or script files. Some are written in a certain programming language. Reading hundred or thousand lines of text in plain text editor will sure give us pain.

My choice goes to Notepad++ or SublimeText.

Office Suite

Yes, office suite. The popular one is Microsoft Office, Open Office, Libre Office, etc.

Any office is no problem. However, for more compatibility I use Microsoft Office.

ISO Tool

An ISO image is an archive file of an optical disc, a type of disk image composed of the data contents of every written sector of an optical disc, including the optical disc file system. ISO image files usually have a file extension of .iso. The name ISO is taken from the ISO 9660 file system used with CD-ROM media, but what is known as an ISO image might also contain a UDF (ISO/IEC 13346) file system (commonly used by DVDs and Blu-ray Discs).

ISO Tool enables us to create and mount an ISO image.

My choice goes to PowerISO.

SSH Server

The old-school guy should know this thing.

Secure Shell (SSH) is a cryptographic network protocol for secure data communication, remote command-line login, remote command execution, and other secure network services between two networked computers that connects, via a secure channel over an insecure network, a server and a client (running SSH server and SSH client programs, respectively).

As we know, Windows doesn’t ship SSH Server. Therefore we need third party application which will act as SSH daemon.

Like other softwares, there are many alternatives to SSH Server. But my choice goes to BitVise SSH Server or freeSSHd. BitVise SSH Server is a paid application, but it also offer free product for non-commercial personal use.

VNC Server & Client

VNC, or Virtual Network Computing, is a graphical desktop sharing system that uses the Remote Frame Buffer protocol (RFB) to remotely control another computer. It transmits the keyboard and mouse events from one computer to another, relaying the graphical screen updates back in the other direction, over a network.

In simple words: it is used for remote accessing our Server, graphically.

My choice goes to RealVNC.

Basic Storage and Dynamic Storage in Windows

December 11, 2015 | Article | No Comments

From Windows 2000 onwards, Microsoft started introduce the concept of dynamic disks. The counterpart, basic disk, is used from the era of DOS onward. Both have their advantages and disadvantages.

In this article we will discuss about both disks concept. Our explanation would be as general as possible, in fact there is no instruction on specific platform.


Basic Disk

Basic Disk uses a partition table to manage all partitions on the disk on first sector of disk. It is supported by DOS and all Windows versions. A disk with installed OS would be default initialized to a basic one. A basic disk contains basic volumes, such as primary partitions, extended partition, and all logical partitions are contained in extended partition.

Basic Disks provide a simple storage solution that can accommodate a useful array of changing storage requirement scenarios. Basic Disks also support clustered disks, IEEE 1394 disks, and USB removable drives.

Basic Disks also use the same Master Boot Record (MBR) partition style as the disks used by Microsoft MS-DOS operating system. It can also support GUID Partition Table (GPT) partitions on systems that support it.

The following operations can be performed only on Basic Disk:

  • Create and delete primary and extended partitions.
  • Create and delete logical drives within an extended partition.
  • Format a partition and mark it as active.

Dynamic Disk

Dynamic Disk is supported in Windows 2000 and later operating system. Dynamic disks do not use a partition table to track all partitions, but use a hidden database (LDM) to track information about dynamic volumes or dynamic partitions on the disk. With dynamic disks we can create volumes that span multiple disks such as spanned and striped volumes, and can also create fault-tolerant volumes such as mirrored volumes and RAID 5 volumes. Compared to a Basic Disk, Dynamic Disk offers greater flexibility.

What is LDM database? LDM or Logical Disk Manager, is a hidden database which size is 1 MB at the end of Dynamic Disk. This space records all the information of the volumes on a single disk, and also holds some related information on each dynamic disk. The information including Drive Letter, Volume Label, the begin sector of Volume, Volume size, the file system of volume.

All disks are interrelated and will hold information mentioned above if there are several dynamic disk on computer. The relevance of each dynamic disk let we will see a “Missing” disk which is shown in Windows Disk Management if we remove a dynamic disk from your system. All this is saved in LDM database, so LDM database is vary important the same as Partition Table of Basic Disk.

Clearly, we can illustrate the Dynamic disk as following:


The blue area at the beginning of Dynamic Disk is the MBR which sabes the information of the Partition Table on the disk. However, this partition table is not the same as one of Basic Disk. Its main function is to make Windows and Other Disk Manager can know the disk is a dynamic disk instead of empty disk. The red one at the end of disk is the LDM database.

If you are familiar with Linux, Dynamic Disks system is similar to Logical Volume Manager (LVM).

The following operations can be performed only on dynamic disks:

  • Create and delete simple, spanned, striped, mirrored, and RAID-5 volumes.
  • Extend a simple or spanned volume.
  • Remove a mirror from a mirrored volume or break the mirrored volume into two volumes.
  • Repair mirrored or RAID-5 volumes.
  • Reactivate a missing or offline disk.


  1. Capacity – Once Basic Disk create a partition, its capacity cannot be change unless we modify the partition table (using gpart, fdisk, or similar software). Dynamic Disk however can expand the capacity of volumes without data loss.
  2. Disk space limitation – On Basic Disk, the maximum capacity of a partition (volume) can be limited to 2 TB. Dynamic Disks can well handle the large partition of more than 2 TB.
  3. Number of partitions – Basic Disk is using primitive MBR disk layout, so it support only 4 primary partition. At best, it use 3 primary partition and use the last primary partition as extended partition. In Dynamic disks, unlimited number of partition can be created.
  4. Volumes type – Basic Disks only can create any primary or logical partition. Dynamic disks can create simple volume, spanned volume, stripped volume, mirrored volume, and RAID-5 volume (software-based RAID).


  1. Supported file systems – Basic Disks and Dynamic Disks support FAT, FAT32, and NTFS file systems.
  2. Have a partition table – Dynamic Disks have a partition table too, however this partition table is different from Basic Disks Its main function is to let Windows and other partition manager know the disk is a dynamic disk instead of an empty disk.
  3. Label and Drive Letter – On both Basic Disks and Dynamic Disks, every partition (volume) can be assigned to a unique drive letter (in operating system perspective). such as “System C:”
  4. Disk Layout Supported – Both Basic Disks and Dynamic Disks support MBR and GPT partition styles.

Volume on Dynamic Disk

On Dynamic Disk, the volumes are divided into several categories: Simple Volume, Spanned Volume, Mirrored Volume, and RAID 5 Volume. They have drive letter and volume label to differentiate.

Simple Volume

Simple volume only can be created on the single disk. This volume is similar as partition of Basic Disk, but its space can be inconsecutive.

Spanned Volume

It is created from free space that is linked together from multiple disks (up to 32 disks). The sequence of writing data for Spanned Volume is that the volume on the first disk is filled full and then turn to fill the next dynamic disk. Spanned Volume can allow the fragmentary free space of multiple disks is recomposed as one volume, so it can fully utilize the resources of multi-disk. However, it can not be fault-tolerant volume and can not improve performance of the disk.

Stripped Volume

It’s similar with Spanned Volume, and consists of two and more disks. However, the difference is that it can improve the efficiency and performance of disk, because when operating system writes data to Striped Volume, this data will be separated into many pieces of 64KB, and then concurrent writes a different data block to each disk. A striped volume cannot be mirrored or extended and is not fault-tolerant. The screenshot is below:

Mirrored Volume

We can simply understand that Mirrored Volume is a duplicate of Simple Volume. It needs two disks; one stores the data which is being used, and another keep a copy of previous one. When a disk fails, the other one can be used immediately.

RAID-5 Volume

A RAID-5 requires three disks at least; it not only can enhance the efficiency of the disk but also provide the best fault-tolerant. You could simply consider RAID-5 is a combination of Striped and Mirrored Volume. A RAID-5 volume is a fault-tolerant volume whose data is striped across an array of three or more disks. Parity (a calculated value that can be used to reconstruct data after a failure) is also striped across the disk array. If a physical disk fails, the portion of the RAID-5 volume that was on that failed disk can be recreated from the remaining data and the parity.

Microsoft Windows Server 2012 is a one of Windows Server’s family brand. It is the sixth release of Windows Server and using the same controversial Metro-based user interface in Windows 8. In fact, Windows Server 2012 has codename “Windows Server 8” before it was release the final product as “Windows Server 2012”.

Installation of Windows Server 2012 is (theoretically) simple. However things going complicated in my case so I have to do it in other way. In this article, we will discuss about how to install Windows Server 2012 without even running the installer. That means we don’t need Installer DVD and boot the machine from it.

In this article, I use:

  1. Lenovo Ideapad Z480, as machine
  2. Windows Server 2012 R2 ISO file
  3. Microsoft Assessment and Deployment Kit (ADK)

What we say about installing Windows Server 2012 without running installer doesn’t mean we will copy the data in hard way. We will do it using smart way.

Background Story

With a training of SharePoint 2013, I was “forced” to install Windows Server 2012 as stand alone operating system (not in virtual machine). In other word: multi-boot with my current installed Windows 8 and Slackware64 14.0. This is simply because of the hardware requirement of a SharePoint farm.

My machine, Lenovo Ideapad 480, has been configured as UEFI machine with GPT disk. However, the same problem as installing Windows 8, the Windows Server 2012 installer I have cannot be installed to GPT disk. Another problem arise when I convert my GPT to MBR disk layout: I can’t boot! This is because the entry in UEFI firmware isn’t match with those modified layout. So I change back to GPT and repair the UEFI bootloader for Windows 8, while the Slackware remain untouched yet.

So I try other way around without messing with GPT and UEFI. That is deploying the server manually.

In this article, I assume the machine has been installed with Windows 8.

The Partition

My system is based on my guide for dual boot Windows 8 and Slackware64.

At least we need three partitions: EFI boot partition, Microsoft Reserved (MSR) Partition, and partition for Windows Server 2012. This is the layout partition I have, displayed using diskpart program:

sel disk 0
list vol


The red square is the EFI partition. The blue one is the Microsoft Reserved partition. Last, the green one is our (would be) Windows Server 2012 root partition, as seen from Windows 8.

So, I assume we already have or prepared those partitions.

Grab Materials

For the next stage, we will need the ISO for Windows Server 2012 and the deployment tools for Windows 8 from the Assessment and Deployment Kit (ADK). I won’t provide the ISO, so you should find it by yourself. The latter (ADK), contains “dism.exe” in an updated version which allows Windows Server 2012, as well as Windows 8, to be deployed.

The one I use is Windows Server 2012 R2.

Deploying Windows Server 2012

Mount the ISO, using any image mount program. In my case, I use PowerISO. Assuming the ISO file is mounted as drive E: and we will install Windows Server 2012 to drive G:, we can deploy the WIM file by:

dism /Apply-Image /ImageFile:E:\sources\install.wim /Index:1 /ApplyDir:G:\

The index specifies which edition is deployed from the WIM file. The meaning of the index and other valid choices are revealed by the following command:

dism /Get-ImageInfo /ImageFile:E:\sources\install.wim

Here is the screenshot:


Creating Bootstrap

This section is similar to article repair Windows 8 EFI bootloader.

We will create the bootstrap for EFI on EFI partition. Remember that I need to make it dual with my existing Windows 8, so we should create a separate folder. However, the EFI partition is not yet assigned with drive letter, so we better assign it first.

Open terminal with administrator privilege. Invoke diskpart to run disk partition program, in terminal. I have only 1 disk, so it should be recognized as disk 0, so we will select disk 0.

sel disk 0

Now, based on previous picture, my EFI partition is recognized as volume 1, so we will assign it to a drive letter, let say B.

sel vol 1
assign letter B:

Now, exit the diskpart. Still on administrator privileged terminal, go to B:\ and create new directory for EFI boot.

cd EFI
mkdir WinServer2012
cd WinServer2012
mkdir Boot
cd Boot

And copy all the file required for boot from mounted ISO (assuming it is mounted as E:\):

copy E:\efi\microsoft\boot\* .

And then use a tool called bcdboot to make bootstrap.

bcdboot G:\Windows /l en-us /f ALL /s B:

Now restart.

This is short notes on how I create a dual boot machine with Windows 8 and Slackware64. Both are 64-bit operating system and will be installed on UEFI-based computer with GPT disk layout.

Actually I do this around in earlier year 2013, so this article might not up to date. However it should work because we use general method.

In this article, i use:

  1. Microsoft Windows 8 64-bit, installation disc
  2. Slackware64 14.0, installation disc
  3. Lenovo Ideapad Z480
  4. USB disk

Note that I do the scenario (would be) mentioned because my machine is fresh and I will do it from scratch.

About Machine

Lenovo Ideapad Z480 has following specification (main):

  1. Intel Core i7-3632QM
  2. RAM 4 GB
  3. HDD 1TB
  4. Video RAM NVidia GeForce GT640

However, I also give addition to RAM so in result I have 8GB RAM.

At default, it is not using UEFI so I activated UEFI capability.

I also convert the disk format from MBR to GPT, however I do this later.

General Overview

The problem arise before me is the fact that the Windows 8 installation DVD not support UEFI yet. Therefore I cannot boot the DVD in UEFI.And also, Windows 8 cannot be installed on GPT disk, yet. At that time Slackware also does not support UEFI, yet. But, it can be installed in GPT partition, good thing to know. Therefore I need a bootable USB disk to boot Slackware then create everything I need for installing Linux.

The scenario in this article:

  1. Create partition
  2. Install Windows 8 while the disk still use MBR layout.
  3. Install Slackware64 14.0 with GPT disk
  4. Finalizing, installing and configuring bootloader


I use a companion Linux in bootable USB stick. I create a USB stick with UEFI capable. You can download it from here.

Make a partition for USB stick with FAT32 partition and boot flag enabled. You can use either gparted or gdisk (in Linux) to accomplish it.

Just extract what inside the archive to USB stick. Make sure there are two folders: EFI and Slackware64.

Step 1: Create Partition

Boot the machine using Windows installer DVD. I need to create a partition for MBR disk. In my case I create these primary partitions:

  1. boot partition, located on partition 1 with FAT32 file system, takes about 100MB.
  2. Reserved partition, used by Windows, create it for 350MB capacity.
  3. Windows partition, NTFS, I use 100GB
  4. Linux Partition, unallocated, I use 100GB

Those are the partition I need at the moment. The rest will be create at finalizing stage.

Here, once the Windows 8 installation DVD is booted, do normal installation routine. Once we got on media selection (where we install Windows), press [Shift] + F10. This will bring command prompt. Invoke following command:


Now we will do partitioning. I’m using only one disk, so the disk should be recognized as disk 0. Also, I don’t use GPT at this section, it would be after installation of Windows 8.

select disk 0

create partition primary size=100
format quick fs=fat32 label="System"

create partition msr size=350
format quick fs=ntfs

create partition primary size=100000
format quick fs=ntfs

create partition primary size=100000

Step 2: Installing Windows 8

Still using Windows 8 installation DVD, exit the command prompt. Now I’m refreshing the list so we will know all of the partition available.

I continue installing Windows like usual on partition 3.

Once the installation finish, go to step 3.

Step 3: Installing Slackware64

I need to do some preparation first. Therefore, there would be some subsections for this.

Convert MBR to GPT

Boot the USB stick.

Conversion is inherently risky. For safety, I backup the original configuration before converting the disk. The MBR itself is stored on the first sector of the disk and can be backed up with dd by:

dd if=/dev/sda of=backup.mbr bs=512 count=1

Then I run gdisk for disk on /dev/sda

gdisk /dev/sda

Follow the option menu for conversion MBR to GPT, and I done.

Prepare the Installation Environment

Mount the USB stick. I accomplish this by invoking following command:

mkdir /src
mount /dev/sdb1 /src

Invoke setup and adjust the setting like normal installation until you reach installation media stage.

Press ALT+F2 to switch to another screen (or another tty).

Install temporary system using USB stick. Invoke these commands:

cd /src/slackware64
installpkg -root /mnt [az]*/* cd


Now, back to our main setup and choose install from CD/DVD. Also, I won’t use LILO, instead I use ELILO. So I don’t install LILO.

After installation is finished, I don’t restart the machine immediately. Instead, I go to last step: Finalizing.

Step 4: Finalizing

First, make sure we are still boot the machine using USB stick, then load following command:

modprobe efivars

Also, I need to mount the boot partition

mount /dev/sda1 /mnt/boot/efi

Add Bootstrap to Slackware

I invoke following command. Note that these commands should be invoked as is, even a dot matters. If you remember, the Slackware is installed on 4th partition.

mount /dev/sda4 /mnt/root
cd /mnt/boot/efi
cp -rvf /src/EFI /mnt/boot/efi
cd /mnt/boot/efi/EFI
mv BOOT Slackware
cd Slackware
mv bootx64.efi elilo.efi
cp /mnt/root/boot/vmlinuz-huge-3.2.29 .
vi elilo.conf

And I configure the elilo.conf:

image = vmlinuz-huge-3.2.29
label = Slackware
root = /dev/sda4

And register boot so that machine can boot Slackware.

cd /mnt
usr/bin/efibootmgr -c -L "XathryaSlackBoot" -l "\\EFI\\Slackware\\elilo.efi"

Add Bootstrap to Windows

Eject the Slackware installation disc and insert Windows 8 installation disc. I need to copy all files needed to boot EFI from Windows 8 disc.

cd /mnt/boot/efi
mkdir /mnt/disc
mount /dev/sd1 /mnt/disc
cp -R /mnt/disc/efi/microsoft /mnt/boot/efi

That will copy “microsoft” folder and whole of it’s content to /mnt/boot/efi (which is my mounted efi boot partition).

Now, to create a bootstrap we first need to restart the machine and boot with Windows 8 installation DVD. What we will do is repair the Windows 8 EFI bootloader.

I do normal installation sequence method until I was prompted with list of volumes / partitions. Now press [Shift] + F10. A new command prompt appear.

Now invoke following command, which will bring me to diskpart (disk partition) program:


My disk is only one, so I will use disk 0.

sel disk 0

Because the EFI partition is the very first partition (/dev/sda1), it should be registered as earlier volume. However, it doesn’t have drive letter, so I will give it one.


sel vol 1
assign letter b:

The attempt is successful and I’m prompted by a message which tell me that the volume has been assign to letter B. Now leave the diskpart with exit command. Go to the EFI partition and add the EFI bootstrap.

cd /d b:\EFI\Microsoft\Boot\
bootrec /fixboot
ren BCD BCD.bak
bcdboot C:\Windows /l en-us /s B: /f ALL

bootrec (boot recover) will fix the UEFI bootloader.

bcdboot will be used to recreate BCD store. The C:\Windows is path where Windows is installed and B: is drive of my EFI partition. The “/f ALL” parameter updates the BIOS settings including UEFI firmware/NVRAM while /l en-us is to localize for US locale (US English).

Add More Partitions

I need more partitions so I create them. I use gdisk for this.

Introduction to Microsoft SharePoint

December 11, 2015 | Article | No Comments

Microsoft SharePoint is a portal-based platform for collaboratively creating, managing, and sharing documents and Web services. SharePoint (SharePoint Server, in this case) enables users to create “SharePoint Portals” that include shared workspaces, applications, blogs, wikis, and other documents accessible through a Web browsers.

MOSS is used by many enterprises as a content management system (CMS). Partially as a result of the tight integration with Microsoft productivity applications included in Office, such as Word, many administrators have found SharePoint useful in organizing and aggregating an enterprise’s data into Web-based portal with defined taxonomies that structure the information.

The Idea

Before SharePoint, to build a site for business process, a System Administrator is required for preparing site, implementation, make content, and fill the content. However, there is big chance that System Administrator know what business need. Even if he know, there are many complicated tasks from design to implementation.

Microsoft SharePoint make the process easier and can be done by providing a platform which integrate all the needs. SharePoint also provide standard template.

SharePoint itself is not a software which we can used for every needs. As said before, SharePoint is a platform or framework. It is providing us with rich materials, but as every platform or framework does SharePoint only provide tools. Programmer needs to build application needed by business. In other word, customizations and even programming on top of it.

SharePoint Products

As now (November 9th, 2013) the latest version of SharePoint is Microsoft SharePoint 2013. However, when we say SharePoint, it can refer to one or more Microsoft SharePoint products or technologies, yet the term SharePoint itself is a family of technology brand.

According to Microsoft, there are some available technologies:

  1. SharePoint Online – Cloud-based service hosted by Microsoft for company or businesses.
  2. SharePoint Foundation – The underlying technology for all SharePoint sites. SharePoint Foundation is available for free on premises deployment—in previous versions it was called Windows SharePoint Services.
  3. SharePoint Server – A SharePoint version purchased for installed on dedicated server.
  4. SharePoint Designer – Free program for designing, building, and customizing web sites running on SharePoint Foundation and SharePoint Server.
  5. SharePoint Workspace – Desktop program for take SharePoint site content offline and collaborate on the content with others while disconnected from the network. The changes will then be synchronized back to the SharePoint site. However in SharePoint 2013, this is replaced with SkyDrive Pro folder sync.

In this article, we will talk about the technology in general. If we refer to some term, it might turn that we are using SharePoint server which is installed on dedicated server.

A Farm

A farm, in this case SharePoint Farm, is a collection of SharePoint servers or SQL servers that work in concert to provide a set of basic SharePoint services that support a single site. In this context, SQL server used is Microsoft SQL Server, of course.

A farm is installed on Microsoft Windows Server. As for SharePoint 2013, the prerequisite is Windows Server 2012 or Windows Server 2008 R2 SP 1.

There are many scenario for creating a farm. All farm component can be put on a single physical machine. Note that all the component are just services / roles. The other scenarios are put components on separated dedicated physical machine.

Container: Lists, Libraries

A container is a standard component for storing information. We divide the term information into two categories: data and document. In the backend, all of those information will be stored on SQL Server, but using different implementation.

Example of data: customer (name, member id, address, etc), product, etc.

Example of document: any document file in any format (ex: pdf, doc, xls, etc).

As we have two distinct information format, we use two different container for them. The data will be stored on List, and document will be stored in libraries.

Android Application Development using Windows

December 9, 2015 | Article | No Comments

There are also version of this article for Linux Ubuntu and Linux Slackware64.

Android Operating System is one of popular operating system for mobile device beside Windows mobile, Apple iOS, etc. This article main focus would be concentrated on installation of development tools, which is Eclipse IDE, Android SDK, and Android Developer Tool on Windows 8 64-bit.

Why Eclipse? Eclipse is an open source Integrated Development Environment and has full support for Android. It’s also quite simple.

In the time i write this article, I use Windows 8 64-bit.This article will focus on Windows  8, though you can use this method and apply it to other Windows version. You must also have active internet connection to do installation and fetching required packages.

You can skip some part if you are confident enough that you have done it before. Well, but nothing wrong by read a whole article, right? 😉

Now let’s we go!


We need to install JAVA and Eclipse. But running Eclipse need JAVA so we will install JAVA first.

When using 64-bit machine, make sure you have JAVA and Eclipse for same architecture. It means, you cannot have Eclipse 64-bit and using JAVA 32-bit. It goes same for 32-bit Eclipse and 32-bit JAVA.

At this point, I assume you have install JAVA and Eclipse.


Android Developer Tool Plugin

Now let’s moving to installation of Androit Developer Tool (ADT). It is a special Eclipse plugin contains integrated android environment for building Android application using eclipse.

Start eclipse. Now navigate to:

Help - Install New Software - Add

enter the following information:

Name: ADT Plugin
Location: https://dl-ssl.google.com/android/eclipse/

Click on OK. Now select “Developer Tools” and/or “NDK Plugins”. Click Next to begin installation. Wait for installation to finish its work.

Install the SDK

Next we will install Android SDK. Downlad Android SDK starter pack from this link

Download the latest SDK. By the time I write this article, the latest version is 22.0.5. It is an installer with filename installer_r22.0.5-windows.exe.

Run the installer file and choose a path for installing SDK. In my case I will leave the SDK on C:\Program Files (x86)\Android\android-sdk

Install SDK Platforms

Now we need to install platforms and optional additional plugins or sample codes. Start SDK manager (If you just do install the Android SDK, you will be asked to start the SDK):

C:\Program Files (x86)\Android\android-sdk\SDK Manager.exe

Seleck SDK Platforms you want. I choose Android 2.3.3 API 10 as my smartphone Sony Xperia U use this one. When you have selected all packages you want, click Install Selected. You will be prompted to Accept License. Click Accept All and then Install.

Create Android Virtual Device

Now we have to join Eclipse IDE with Android SDK and create and Android Virtual Device (AVD). Android Virtual Device is an emulator to run your application on top of your computer.

In Eclipse, navigate to:

Window - Preferences - Android

Enter location of your Android SDK installation. In my case it is in C:\Program Files (x86)\Android\android-sdk. Press OK.

Now navigate to:

Window - Android Virtual Device Manager - New

Insert following information into:

AVD Name: AndroidVirtualDevice
Device: <your preferred device>
Target: <chose any desired Android version and API level available>

Click OK. The new Android Virtual Device will be created in the directory:

C:\Users\<your username>\.android\avd

Congratulations! Now you can develop android apps on Windows!

Social media & sharing icons powered by UltimatelySocial