Archive for month: January, 2009

IT managers have a tough job ahead of them. Having to keep the company’s workstations and servers secure and at the same time providing a flexible work (technology) environment that will handle exceptions as they come up.  It’s a tall order. The first instinct is to make the workstation so secure that it’s unusable. On the same token, a workstation that’s too flexible is more likely to pose a huge security risk.
A good IT manager can achieve a balance. In the enterprise the policies are usually created in a ‘top-down’ fashion, which basically means that the corporate standards can impose strict protocols. There are many reasons for having these protocols and standards:
– Reduced cost for deployment: standardizing means less work for IT
– Reduced troubleshooting time: IT staff has an easier time figuring out what’s wrong
– Best practices and optimization
Unfortunatelly you can’t have one standard that fits all cases. Additionally, even though corporate sets the standards, those policies are not always followed or implemented uniformly. Some of the reasons for non-compliance are:
– The need for autonomy: shrinking budgets resulting in limited support
– Different demands for flexibility within different departments
– Lack of understanding of corporate protocols
Many IT managers buy into the idea of implementing expensive tools to solve these problems not realizing that an excellent way of establishing control is through Microsoft’s Group Policy that is built into Active Directory. To fully configure the Group Policies that will fulfill both the IT and business requirements, IT managers need third party applications like the Active Directory Manager. The Active Directory Manager makes Group Policy Management a snap by simplifying the process, and ensuring the flexibility and granularity needed.
Ultimatelly, implementing a cost-effective application like the Active Directory Manager will drive efficiency, decrease downtime and ensure compliance with corporate policies and protocols.