Sunday, January 24, 2021

Ceramic Coating & Car Care

Need of Car Care

Ageing is applicable to our cars also and is  an inevitable natural process. Car care avoids the ageing marks and helps to slow-down the process.

What’s Car Detailing?

Car Detailing is a process to restore the beauty of a car by removing the imperfections and defects on the car body surfaces such as painted surface, tyres and wheels, plastic parts, interiors like dashboard, seats, door trims etc.

Car detailers use polishing and cleaning processes to achieve the perfect finish without affecting the health of the vehicles. Indiscriminate paint correction can affect the paint thickness, hence a good detailer will always understand the polish-ability of the car and plan the polishing strategy.

Unlike many think, detailing is not just polishing, it’s much beyond that. 

Why to Protect the Car?

Car Detailing could bring back the lost-glory of your car, but then what next? how do you preserve the look? The answer is to seal the surface from external environment by applying wax or sealants or ceramic coating or PPF etc.

Choosing the right protection which suits your requirement and pocket is also very important and never compromise the quality over cost.

What’s Ceramic Coating?

Ceramic Coatings are synthetic chemicals made out of Silica or Quartz-Silane-based compound which make chemical bonding with paint molecules. Ceramic coatings are harder (9H hardness) compared to other paint protection products such as waxes or sealants.

Ceramic coatings are used to protect the surfaces after a proper detailing and it’s like laminating a nice foto taken by photographer using his photography skill.

GreenZ Car Care introduced ceramic coating in India, but now the market is changed a lot and huge inflow of brands and low-quality products made the market really terrible. Customers are now confused on which to go for and sometimes fall in the trap of 8-10 layers and 10H hypes created by recent ceramic coating sellers. Always choose experienced detailers who use quality product and follow proper process and offer better after-installation maintenance package. 

GreenZ Car Care has ceramic coating brands such as Gyeon Quartz, Angelwax, Nanolex, Gtechniq, CarPro along with their own branded coatings - GreenZ Infinity Coat

Saturday, March 17, 2012

Digital Rights Management

What is DRM?

Digital Rights Management (DRM) Combination of 3 controls
·         Identity Control
·         Cryptographic Control
·         Access Control
Why we need a DRM solution
Now World Wide Web has become the most popular mode of media content distribution like the following:
·         Audio: Music & Audio books
·         Video: Movies & Music Videos
·         Publishing: books, documents, news articles
·         Computer Games
·         Software
The challenges of Media & Entertainment Industry
The main challenges the Media & Entertainment Industry facing are as follows:
·         Preventing Piracy in Music & Video contents
·         The quality of the Video content on the web
·         Security of the Video/audio content shared on the web
·         Convenient access to the entertainment content on the web
·         Supporting number of platforms to reach target audience

DRM Process
The DRM process I s essentially consists of creating following components:
·         A Content Protection Software
·         A Content Distribution Server
·         A License server
·         A Content Viewer

DRM Process Flow
The DRM Process Flow is depicted in the following diagram:

DRM Tools & Technology
The followings are the main players in the DRM Tools & Technology space:

·         Apple’s Fairplay DRM for online music
·         Adobe Flash & Microsoft Silverlight for Online Videos
·         Widevine provides Digital media solutions for device deliveries
·         Microsoft’s PlayReady platform for Mobile operators
·         Buy DRM


Identity Management with Active Directory - Part 2

Identity Management with Active Directory

AD User


When using AD as Identity store, each identity in the organization will have a AD User account created in AD. Properties such as organizational hierarchy, membership details, telephone and other contact details etc can be assigned to an AD user account.

AD Group


Groups are Active Directory (or local computer) objects that can contain users, contacts, computers, and other groups. Groups can be nested, that is, a group can be a member of another group.

There are two types of groups, Distribution groups and Security groups. Distribution groups are used to create e-mail distribution lists. Distribution groups are used with e-mail applications (such as Microsoft Exchange) to send e-mail to the members of the group. Security groups are an essential component of the relationship between users and security. Security groups are used to manage user and computer access to shared resources and to filter Group Policy settings.

Security Groups are used to create roles and this will be used at the time of access provisioning.

Authorization Manager (AzMan)

Authorization Manager (commonly known as AzMan) is a general-purpose role-based security architecture for Windows. Azman can be used in any application that needs role-based authorization, including ASP.NET Web apps or Web Services, client-server systems based on .NET Remoting etc.
The benefit of using AzMan is that it enables you to define operations, group them into tasks, and then authorize roles to perform specific tasks. It also provides an administrative console for managing roles, tasks, operations, and users.
AzMan supports platform features such as Active Directory (AD) groups, Windows security auditing, and MMC. AzMan assures the proper integration of system access control objects such as the NT access token and better alignment for future Windows access control features such as provisioning and entitlement engines.

Identity Management Life Cycle


When a new employee is recruited in an organization, an identity is created in Active Directory in the form of AD user account. All the roles will have corresponding AD Security Groups created.
When a new role is created in the enterprise application, a corresponding AD Group will be created in AD. And in AzMan policy store, tasks for that particular role will be created.

The provisioning will be done thru a provisioning application which takes the user’s request for access and route the request thru a pre-defined workflow (which is developed and maintained by BizTalk server or any custom .net application built using Windows Workflow (WF in .net framework 3.5). After the approval the user’s AD user account will be added in the corresponding AD Group by the provisioning application using LDAP.

When the user ask for an access in the enterprise application, the Access Management module which used to check the access for the user for the requested functionality will use the AzMan to verify his access rights to the requested functionality.

The Access Management module can be de-coupled from the application logic and can be a stand-alone application. This will give a benefit of a centrally managed Access Control mechanism. And this will help if there is a need of any other way managing access/identity other than AD/AzMan for some set of non-Microsoft applications.

Identity Management with Active Directory - Part 1

Introduction
This post discusses managing identities with Active Directory and Access Management with Microsoft Authorization Manager.
This gives a small introduction of Active Directory components used for Identity Management and this also explains ideal scenarios in Identity Management and Access Management.
What’s Identity Management?
Identity management is a set of systems which manages the users, their accesses, roles etc for enterprises, with significant implications to security and risk strategy. And it is not just a technology discussion as much as it is a process about the role of “roles” in enterprises — how people and applications access.

Identity management is comprised of both technology components and business strategies and policies
The benefits of identity management solution can be gained by consolidating identity, policy and infrastructure management into a single centralized solution, thereby saving time and money in administrative overhead, lowering training requirements and increasing productivity.

Why Active Directory

Since Active Directory is an integral part of Windows infrastructure and networking, it has already become an important and irreplaceable component within the IT environment. And many organizations have already made investments to migrate to Active Directory and deploy it companywide. It makes good business sense to fully leverage those investments by extending Active Directory to other platforms, versus the cost of trying to maintain different solutions for different platforms.

UNIX, Linux and Mac platforms are the second largest base of systems in many large companies, so the ability of Active Directory in integrating with these systems made it a best choice in Enterprise Identity Management.

The solid support from Microsoft – the largest software company in the world is also one of the main reasons to use Active Directory. Microsoft is firmly committed to Active Directory and continues to invest in enhancing and expanding its capabilities.

Considering these strong reasons, Active Directory would be an excellent choice to provide centralized, cross-enterprise directory and infrastructure services for Identity Management in enterprises. The only demerit is that, it does not include capabilities to easily support non-Windows client systems. However, the solution landscape has recently changed, and there is now a way to extend the features and benefits of Active Directory to non-Windows systems and applications. Centrify’s DirectControl suite includes all of the necessary software to allow UNIX, Linux, Mac and Java environments to use Active Directory as a central user identity, infrastructure and policy engine.
And Active Directory’s highly secure, token-based authentication, using industry standard Kerberos, can be used across Windows, UNIX, Linux, Mac and Java platforms. This results in a single sign-on experience that spans all Windows, UNIX and Linux systems.

Active Directory is based on proven enterprise-ready technologies – LDAP for directory services and Kerberos for secure authentication. Microsoft has uniquely combined the strengths of these two technologies to best leverage the open extensibility of LDAP and the highly secure, ticket-based authentication of Kerberos.
For example, a key advantage of Active Directory’s ticket-based authentication system is that, once the user has successfully logged into a system, his or her credentials can be used to automatically access other systems and applications based on established security access rights.

Microsoft’s Group Policy capability extends Active Directory beyond identity and access management to policy and configuration management, which is crucial for meeting regulatory requirements. Administrators have full multi-level control over applying policies to accounts and systems through the Group Policy system.

Active Directory is highly scalable and secure. Active Directory’s distributed model automatically replicates information to other sites, even over slow links, thereby ensuring both fault tolerance with automated failover and increased performance through automated discovery of the closest Active Directory server.
Active Directory has following advantages:
The followings are some of the key advantages of Active Directory.

 ·         Centralized user and group account management

It can store the organizational relationships such as manager - worker relationships.

 ·         Full control over password management
This include password aging, password complexity, and forced password resetting, as well as the ability to temporarily disable an account. Active Directory can also easily manage hours of use for each user and computer.
·         A distributed model for high availability, increased performance and organizational compartmentalization

It has the ability to manage cross domain relationships and trusts. This means that users in each part of the organization can always access their systems, even in the event of a server failure.

Tuesday, December 7, 2010

Boot from VHD in Windows 7

A Virtual Hard Disk created in a VHD file in the hard disk will acts as a separate hard drive in the computer.
You can attach a VHD file to your computer and use the contents of the VHD as in a separate hard drive partition. And you can use the OS installed on the VHD as dual boot OS and make use of the maximum of your machine without creating a physical partition on the hard disk and installing an OS. Thus enjoying the benefits of the Windows 7 feature – Boot from VHD.
Let’s see how it can be done, it’s pretty simple.
Step 1: Attach a VHD
Open the Computer Management console by either right clicking on the Computer item on the Start Menu or typing compmgmt.msc in the Search box in the Start Menu and Enter.
From the left pane of the Computer Management console, select Disk Management and select the Attach VHD item on the Action menu.
Click the Browse button on the new window opened and select the VHD file.
That’s all; you now attached a VHD.
Step 2: Make the VHD Bootable
Open an Elevated Command prompt by typing cmd in the Start Menu search box area, then right click on cmd, and click on Run as administrator.
In the cmd window, go to the drive letter of the VHD attached and change drives to the \windows\system32 directory.
Type the following command and press Enter:
bcdboot w:\windows
(Note: Assuming that W is the drive letter of the newly created partition while attaching the VHD)
Execute the following command to make your current OS as your default boot OS:
bcdedit /default {current}

Tips:  If you created multiple boot, system like above, then you can see the boot control data (bcd) by executing the following command:
bcdedit /v
Also, if you want to make any of the OS as your default boot OS, which can be done by executing the following command:
bcdedit /default {identifier}
(Note: The identifier can be found by executing bcdedit /v command)
That’s all, now the your boot from VHD setup is ready, restart the system, then you can see the multi-boot menu loaded on the screen, now you have too many OS options to load.
Also, if you want to create a new VHD on your own, Microsoft Virtual PC can help you.

This feature is supported only by Windows 7 Ultimate and Enterprise versions only.

Also, if somebody wants to remove the Boot option created, can be done by executing msconfig utility.

Saturday, November 20, 2010

Virtualization with Windows7

Windows 7 virtualization includes running Windows 7 as either a host OS (Operating System) or a guest OS (virtual OS). When you run Windows 7 as the host OS, you can run another operating system, such as Windows XP or Linux, within it as its guest OS. When you run another OS, such as Mac OS X Snow Leopard, as the host OS, you can run Windows 7 within it as its guest OS.
Support for these technologies is not across the board, however. Intel-VT can be found in some very old Pentium 4 models – the 662 and 672 – but not in certain Core 2 processors. There are even some Atom chips with –VT, but not all Pentium-D processors. The Core 2 family is quite varied, according to this Intel product list.
In the case of AMD, it introduced AMD-V in 2006 with the Athlon 64 and Athlon 64 X2 with family "F" or "G" on socket AM2. Earlier generations of AMD chips that used the Socket 939 do not include AMD-V. The "Sempron" family also does not support AMD-V.
Windows 7 has a new feature that makes it easier than ever to set up multi-boot scenarios on a single machine.
Boot from VHD allows you to mount a vhd as a bootable drive and, as the name implies, boot from it.  It's a great scenario for creating multiple OS installations without having to create multiple OS partitions on your hard drive.
In Windows 7, native VHD boot allows you to create and modify VHD files without installing the Hyper-V server role. You can attach VHD files by using the disk management tools, and you can service the Windows image inside the VHD. You can use the deployment tools in the Windows Automated Installation Kit (Windows AIK) to apply a Windows image to the VHD and to apply updates to the image in the VHD file.
Native VHD boot also requires the Windows 7 boot environment. The Windows 7 boot environment is initialized during a full operating system installation, and it includes the Windows Boot Manager, Boot Configuration Data (BCD), and other supporting files.
More details will be updated soon.