In Windows 2008 Components like IIS, DNS etc. are called as Roles and you can add these Roles from Server Manager >> Roles >> Add Roles and then you have to follow the steps to install the desire components. This process is a bit lengthly as you will have to go through the steps. You can automate and eliminate these steps by using Command Line utility called “ServerManagerCmd.exe”.

ServerManagerCmd.exe is a tool or command which Installs and removes roles, role services and features. Also displays the list of all roles, role services, and features available, and shows which are installed on this computer.

Query ROLES

“-query” parameter is used to see all the available and installed ROLES of components on the server. The installed modules are are shown in Green Color (which can bee seen in below image)

Install ROLES

To add additional roles to the server, “-install” or “-i” parameter is used. You can install a ROLE by using “-i” which will install all the components which are required by the component.

Also you can mentioned all the Components separating them with SPACE which will install all the modules you have listed (it will save time)

You can find more information about the ROLES and “Command value” (Component name) on Microsoft Technet Website

Remove ROLES

Roles which are already installed on the server can be removed with the help of “-remove” parameter. Using this, complete ROLE and it’s dependencies will be un-installed from the server.

Additional Options

-version
This parameter is used to check the ServerManager version

-help or -?
Display Help for ServerManagerCmd.exe in the command window.

NOTE: There are some roles which requires Reboot after installation or removal, in such cases you can add “-restart” at the end of install or remove option. This will reboot the server after completion of task if required.

Microsoft has announced that they are shutting down Windows Live Spaces and will migrate all the existing users to WordPress.com. All the information of users like their content, and if any visitor visits existing Microsoft Live Spaces sites they will be automatically redirected to the new WordPress.com domain.

At the time of migration wsers have the options of transferring their content to WordPress, downloading it and storing it locally or deleting it when they hit the migration page. I have Just migrated my Windows Live Spaces blog to WordPress and in this post I will explain the exact steps

As soon as you login into you Windows Live Space you will get following screen which notify users about the switch/migration.

Here, user will get option to Migrate the Space to wordpress or Download Your blog to local system or Delete the Space or the user can just ignore and go to his space. If you are ready press “Get started. Upgrade my blog to WordPress.com“

On next screen you will get some basic instructions about the migration. Press Continue

Now you will get Actual Migration Screen where it will ask you to re-connect your MSN. Press Connect and relogin in your account.

If you are already registered with WordPress you can login and integrate blog with existing blog or create new wordpress blog for Live Space.

On “Create another WordPress.com Blog” page fill all information about your new WordPress Blog. Click on “Create Blog“

Once you get Miration Complete window like below. That means you have successfully migrated your Windows Live Space to WordPress.

Software Security Researchers at matousec.com has developed a method which can bypass protections built in to many of the most popular anti-virus products like McAfee, Trend Micro, AVG, and BitDefender.

The attack, called KHOBE (Kernel HOok Bypassing Engine) works like “bait-and-switch” style by sending a file which contains Harmless code that passes the user’s System Check and as soon as it get passed the code is swapped with malicious code. This attack works more efficiently on Multi-Core systems as in Multi-Core System one thread doesn’t monitors on other threads that are running simultaneously which makes the switch/swapping easier. As a result, the vast majority of malware protection offered for Windows PCs can be tricked into allowing malicious code that under normal conditions would be blocked.

“We have performed tests with [most of] today’s Windows desktop security products,” the researchers wrote. “The results can be summarized in one sentence: If a product uses SSDT hooks or other kind of kernel mode hooks on similar level to implement security features it is vulnerable. In other words, 100% of the tested products were found vulnerable.”

List of Antivirus solutions which was tested by matousec.com and found vulnerable

• 3D EQSecure Professional Edition 4.2
• avast! Internet Security 5.0.462
• AVG Internet Security 9.0.791
• Avira Premium Security Suite 10.0.0.536
• BitDefender Total Security 2010 13.0.20.347
• Blink Professional 4.6.1
• CA Internet Security Suite Plus 2010 6.0.0.272
• Comodo Internet Security Free 4.0.138377.779
• DefenseWall Personal Firewall 3.00
• Dr.Web Security Space Pro 6.0.0.03100
• ESET Smart Security 4.2.35.3
• F-Secure Internet Security 2010 10.00 build 246
• G DATA TotalCare 2010
• Kaspersky Internet Security 2010 9.0.0.736
• KingSoft Personal Firewall 9 Plus 2009.05.07.70
• Malware Defender 2.6.0
• McAfee Total Protection 2010 10.0.580
• Norman Security Suite PRO 8.0
• Norton Internet Security 2010 17.5.0.127
• Online Armor Premium 4.0.0.35
• Online Solutions Security Suite 1.5.14905.0
• Outpost Security Suite Pro 6.7.3.3063.452.0726
• Outpost Security Suite Pro 7.0.3330.505.1221 BETA VERSION
• Panda Internet Security 2010 15.01.00
• PC Tools Firewall Plus 6.0.0.88
• PrivateFirewall 7.0.20.37
• Security Shield 2010 13.0.16.313
• Sophos Endpoint Security and Control 9.0.5
• ThreatFire 4.7.0.17
• Trend Micro Internet Security Pro 2010 17.50.1647.0000
• Vba32 Personal 3.12.12.4
• VIPRE Antivirus Premium 4.0.3272
• VirusBuster Internet Security Suite 3.2
• Webroot Internet Security Essentials 6.1.0.145
• ZoneAlarm Extreme Security 9.1.507.000
• probably other versions of above mentioned software
• possibly many other software products that use kernel hooks to implement security features

KHOBE can be loaded/initiated under standard user or account having limited access as this attack doesn’t requires Administrator Access to the System. As it requires a large amount of code/Script to be loaded on the targeted System, making it impractical for shellcode-based attacks that rely on speed and stealth. It can also be initiated only when an attacker already has the ability to run a binary on the system. The technique might be combined with an exploit of another piece of software, like a vulnerable version of Adobe Reader or Oracle’s Java Virtual Machine to install malware without rising the suspicion of the any Anti-Virus software the victim is using.