Tuesday, November 4, 2008

How to Nest Users and Groups for Permissions

In this article I will show you how to nest users and groups for permissions.
When you investigate groups within Active Directory, you will see that you have many to choose from. The type and scope of group that you choose to create will depend on how that group can be used and where it can be used within the enterprise. Knowing how the Active Directory groups are designed by Microsoft will help you develop a solid group strategy for assigning permissions. In addition to knowing how to design your groups, there are some pitfalls with user and group nesting that you want to avoid, as these pitfalls create a very insecure environment.

Group types and scope

When you jump into the Active Directory Users and Computers interface to create some groups, you will immediately see that there are many options to choose from. As you can see from Figure 1, you need to select the group scope and type during the creation of a new group.


Figure 1: Active Directory groups require both scope and type to be configured

Understanding the specifics of these groups will help you design and determine which options to pick for the group that you are creating. For each group, you need to know what objects it can contain, as well as the overall purpose of the group.

For the group scope, you are determining where the group should be used within the Active Directory enterprise. Your group selection here determines a lot about how you want to use the group within the overall assignment of permissions. Before we discuss each group specifically, the overall picture of group and user nesting is designed to be as follows:

Users go into Global Groups, Global Groups go into Domain Local Groups, and Domain Local Groups are listed on the Access Control List (ACL) of the resource.

If Universal Groups are used, then the following nesting rules apply:

Users go into Global Groups, Global Groups go into Universal Groups, Universal Groups go into Domain Local Groups, and Domain Local Groups are listed on the Access Control List (ACL) of the resource.

Domain Local Group – This group scope is designed to contain Global Groups and Universal Groups, even though it can also contain user accounts and other Domain Local Groups. If you want to follow a logical nesting rule pattern, you will not put user accounts into Domain Local Groups. As you design and create Domain Local Groups, you should be considering “What the group is designed to do at the resource.” Examples might be “Read SQL DB,” “Full Control HR Data,” or “Modify Finance Group Membership.”

Note:
Domain Local Groups can only be seen and used on domain controllers if the domain is still in mixed mode. Mixed mode also eliminates the capability of nesting Domain Local Groups into other Domain Local Groups. This is due to the fact that NT4 domain controllers don’t understand the concept of Domain Local Groups, so they are simply seen as Local Groups.

Global Groups – This group scope is designed to contain user accounts. Global Groups can contain user accounts and other Global Groups. Global groups are designed to be “global” for the domain. After you place user accounts into Global Groups, the Global Groups are typically placed into Domain Local Groups or Local Groups (which reside on member servers in the Security Accounts Manager (SAM)). As you design and create Global Groups, you should be considering “What type of user belongs in this group.” Examples might be “Salesreps,” “HR Managers,” or “Finance Managers.”

Note:
Global Groups can only contain user accounts if the domain is in mixed mode. Like group nesting is not available in mixed mode due to legacy NT4 domain controllers.

Universal Groups – This group scope is designed to contain Global Groups from multiple domains. Universal Groups are designed to help “group” groups in a multi-domain enterprise. Universal Groups can contain Global Groups, other Universal Groups, and user accounts. After the Global Groups from the different domains are placed into the Universal Group, the Universal Group is typically placed into a Domain Local Group or Local Group. As you design and create Universal Groups, you should be almost mimicking the concepts of the Global Group, but from an enterprise standpoint. So, you might have a Universal Group named “All HR Managers” or “All Finance Managers.” Within each of these Universal Groups, you will have the “HR Managers” or “Finance Managers” from each domain as members.

Note:
Universal Groups cannot be used as Security Groups if the domain is in mixed mode. This means that they can’t be used for controlling access to resources via permissions. Again, this is because NT4 domain controllers don’t understand the concept of Universal Groups.

Security Groups – This type of group has a unique characteristic in that it has a Security Identifier (SID) assigned to it from Active Directory. This SID enhances the function of the group so that it can be used for assigning and controlling permissions to a resource. In essence, Security Groups can be placed on an ACL of a resource. Security Groups can also be used for email distribution lists.

Distribution Groups – This type of group is limited in capabilities, because it does not have a SID assigned to it. Distribution Groups are designed to work with email, but not for the assignment or control of permissions to a resource.

Groups and Users in Windows NT4

Most environments still rely on the old style of group nesting that was forced in Windows NT4 domains. This is because most companies migrated in some fashion from Windows NT4 to Active Directory, so the group model was already formed. The group model that I am referring to has the following group and user nesting structure:

Users go into Global Groups, Global Groups go into Local Groups, and Local Groups are listed on the Access Control List (ACL) of the resource.

This was the only option for multiple reasons. First, Windows NT4 did not support like group nesting. So, Global Groups could not be included in other Global Groups and likewise for Local Groups. Second, The domain SAM did not include Domain Local Groups, so the only way to nest groups from the domain was to place Global Groups into the Local Groups on the member servers where the resource resided. Third, each domain was its own entity, so there was no need to consider cross domain interaction within the same directory like Universal Groups accomplish in Active Directory.

What NOT To Do

In reality, all group nesting rules are subject to interpretation. I have seen all options implemented and used company wide. As long as the user and group structure has logic and is secure, there is really no reason that the “designed Microsoft” methods need to be followed strictly.

However, there are two different options that should be avoided at all costs. These two options create an insecure environment that is almost impossible to track, troubleshoot, and secure.

  1. User accounts should never be placed into Local Groups. The Local Groups that I am referring to are the Local Groups in the local SAM of member servers. When this is done, it is nearly impossible to enumerate which Local Groups a user has membership in, which is essential for a security audit. Also, when a user moves from one job role to another, it is impossible to make sure that all “old resources” that the user has access to are removed.
  2. User accounts should also not be placed directly on the ACL of a resource. The reason for this is identical to the reasons listed in the first bullet. There is no way to enumerate the resources that a user has access to if the user is placed directly on the ACL.

Summary

The use of domain groups is essential for administration of resource access. Knowing which groups are available and the intent of the group is key to designing your group nesting strategy. Microsoft developed the groups within Active Directory such that the administration of all groups could be within Active Directory. However, with the migrations from Windows NT4, it has made it hard to implement the desired group strategy that Active Directory provides. Knowing the capabilities of each group, as well as the limitations, you can now design a strategy that works best for you. Regardless, make sure that you don’t configure users and groups such that a security issue is created.

Telstra and Microsoft join forces

Telstra and Microsoft today announced a deal which will see the pair link their products and brand names to target small business customers.

Tracey Fellows
"Our goal is to make the combination of PCs, mobile devices and the web something that is significantly more than the sum of its parts," Tracey Fellows, MD for Microsoft Australia said at a media briefing in Sydney. "We believe that with this partnership with Telstra, we are well on the way to doing this."

The companies have announced three areas in which they will integrate their products. The first is hosted business applications where Microsoft's online services offering hosted applications will take pride of place in Telstra's newly launched software as a service portal T-Suite, although Telstra's group MD product management Holly Kramer insisted that other vendors wanting to sell on T-Suite wouldn't be short changed.

"It won't change the opportunity for other applications to be a part of the portal at all... [Microsoft's software] we think will obviously be a hero application," she said.

Deena Shiff, group managing director of Telstra Business clarified Kramer's statement. "Hero means... we've obviously needed to make some choices between best of breed. We've clearly made the choice that Microsoft represents that and so we wouldn't be seeking to replicate those particular types of services." Local software vendors could have a part in developing specialised applications in areas such as compliance, Shiff said.

Holly Kramer

The second area of collaboration for Microsoft was mobile, in which Telstra has been developing a skin for Windows Mobile devices which will cut down the number of steps to reach and use applications such as email.

Telstra will also be offering a pay per month Outlook mobile email service using the firm's existing server infrastructure, or an advanced management option which would also include having software upgrades pushed out to phones or applications deployed.

The third area of collaboration was unified communications, where Telstra's hosted internet protocol-based (IP) telephony service will be integrated into Microsoft Office, allowing click to call, the ability to see when contacts were available or offline, as well as instant messaging and video-conferencing.

The companies would not disclose how the revenue would be shared between the companies, saying the percentage wasn't set."For us both, we see it as a bigger pie," Microsoft's Fellows said.

"The real principle behind the alliance is that if we can make [products], you know, represented by two strong brands that people trust and make them simple to buy and purchase, as Tracy said, we can grow the pie," Kramer added.

"We want to make it easy to purchase, easy to use and easy to manage," Fellows said. "That's the aim of this whole alliance."

This was the second deal Telstra has entered into this week with a global company. Google also shook hands with the telco as Telstra subsidiary Sensis allowed its Yellow Business Listings to be integrated into Google's search.

If you like to stay on the bleeding edge of technology (and you’re running Vista) you may want to consider modifying two registry keys on your system so that you can participate in the Vista SP2 Beta program.


To join the program all you have to do is download this batch file, and run it on your Vista machine as an administrator. Then just check for available Windows Updates (it may take 30 minutes or so for it to show up in the Windows Updates).

Think carefully whether you want to do this or not. There will likely be some bugs that could cause problems with your system, but at the very least it will cause Vista to expire on 4/2/2010 (or around then). Plus it will place the “Evaluation copy” message on your desktop wallpaper. You can always uninstall Vista SP2 to remove the evaluation message and expiration date, but it’s important to know what you’re getting into before you try to install it.

So what’s new in Vista SP2? Here’s a brief rundown that the Vista blog provided last week:

* Windows Vista SP2 adds Windows Search 4.0 for faster and improved relevancy in searches.
* Windows Vista SP2 contains the Bluetooth 2.1 Feature Pack supporting the most recent specification for Bluetooth Technology.
* Ability to record data on to Blu-Ray media natively in Windows Vista.
* Adds Windows Connect Now (WCN) to simplify Wi-Fi Configuration.
* Windows Vista SP2 enables the exFAT file system to support UTC timestamps, which allows correct file synchronization across time zones.

Windows Vista SP2 is expected to be released in final form sometime in the first half of 2009. Judging by the expiration date of Vista SP2 Beta I’d say that sounds about right.

Download:
Windows Vista SP2 batch file (link 1)
Windows Vista SP2 batch file (link 2)

Saturday, November 1, 2008

Vista SP1 Desktop Optimization Pack 2008 R2 RTM

Since the introduction of the Microsoft Desktop Optimization Pack, the Redmond company has sold in excess of 10 million units of the package of solutions, and on September 15, the R2 version of MDOP 2008 was released to manufacturing.




According to Jameel Khalfan, Microsoft Technical Product Manager, customers will be able to acquire Microsoft Desktop Optimization Pack 2008 R2 starting with the first week of October. Built to be used in conjunction with Windows Vista (now with Service Pack 1), MDOP 2008 R2 is essentially a suite of products designed to catalyze an evolution of the existing relationship between IT and end-users in what Khalfan referred to as traditional desktop infrastructures.

“We know that this is where IT is going, and today’s news plays a critical role in fulfilling that vision. In an Optimized Desktop, a partnership is established in which IT can constructively maintain control over the desktop infrastructure, without getting in the way of the users they’re supporting. With MDOP 2008 R2 and Windows Vista, you get a solution that’s greater than the sum of its parts… a '1+1=3' scenario where IT is controlled and managed, users are empowered and productive, and the pace of business accelerates,” Khalfan revealed.

MDOP 2008 R2 will deliver the recently RTM'ed Microsoft Application Virtualization 4.5 (formerly Microsoft SoftGrid Application Virtualization), but also the Microsoft Asset Inventory Service, the Microsoft Advanced Group Policy Management, the Microsoft Diagnostics and Recovery Toolset, and the Microsoft System Center Desktop Error Monitoring.

According to Khalfan, the App- V, AGPM, DEM and DaRT technologies are localized in no less than ten languages, including: Spanish, Brazilian Portuguese, Simplified & Traditional Chinese, Dutch, French, German, Italian, Japanese, Korean, and Russian.

“It’s important to note that this isn’t the end of our development cycle. Rather, it’s another milestone on our continuing mission to make 1 plus 1 always equal 3 (or more!) standard math when it comes to Desktops. Next, in the first half of 2009, we’re planning to release Microsoft Enterprise Desktop Virtualization (MED-V). MED-V, which will be the first Microsoft-branded release of the recently acquired Kidaro technology, will be a key addition to MDOP; it provides a secure, fast, manageable, local hardware virtualization solution that complements App-V, and will serve to further strengthen our 'desktop to datacenter' virtualization story,” Khalfan concluded.

source: news.softpedia.com

Previewing Windows Server 2008

Microsoft
seems like the most unlikely company to ship products that really support Enterprise 2.0. After all, the company is the poster child for packaged software.




But everything the company is saying here in Orlando at TechEd 2008 is consistent with the idea that IT has to support the linchpins of complex, agile, multivariate organizations. And Microsoft is giving IT professionals the tools to support mobile information workers, social networking, cloud computing and virtualized environments.

That observation cuts across the swath of announcements around identity and access management, interoperability, virtualization, and what the company is referring to as "Dynamic IT."

Windows Server 2008 just started shipping in February, but I got a hint of what's to come in the next release from Bob Visse, senior director of Windows Server marketing, here.

The high points:

- WS2008 R2 will have improved authentication features, making it easier for clients to authenticate into the data center and creating more seamless access to corporate networks;

- new power management features, particularly in the case of multicore servers; and

- support for 64-bit architecture exclusively. The current release also supports 32-bit, but Visse noted that Hyper-V, Microsoft's forthcoming server virtualization tool, is built on 64-bit architecture, making 32-bit a moot issue for most customers.

source: blogs.eweek.com

Windows Server 2008 R2 revealed

Microsoft
announced the second release of its Windows Server 2008 operating system at its Professional Developer Conference in Los Angeles this week.




The updated OS includes a range of new features, including support for web applications, better virtualisation and improved scalability and reliability.

Virtualisation will be a key feature of the new OS, with Microsoft announcing that Server 2008 R2 will include "Live Migration", a feature which allows users to move a virtual machine between two computers running Microsoft's hypervisor, Hyper-V. Microsoft said that the new version of Hyper-V shipped with Server 2008 R2 will include better management features.

Microsoft also said that Server 2008 R2 has many features specifically designed to work with client computers running the upcoming Windows 7, including better usability and accessibility.

According to the reviewer's guide published on Microsoft's website, Server 2008 R2 will be available exclusively as a 64-bit OS.

source: zdnet.com.au

Windows Server 2008 R2 revealed

Microsoft
announced the second release of its Windows Server 2008 operating system at its Professional Developer Conference in Los Angeles this week.




The updated OS includes a range of new features, including support for web applications, better virtualisation and improved scalability and reliability.

Virtualisation will be a key feature of the new OS, with Microsoft announcing that Server 2008 R2 will include "Live Migration", a feature which allows users to move a virtual machine between two computers running Microsoft's hypervisor, Hyper-V. Microsoft said that the new version of Hyper-V shipped with Server 2008 R2 will include better management features.

Microsoft also said that Server 2008 R2 has many features specifically designed to work with client computers running the upcoming Windows 7, including better usability and accessibility.

According to the reviewer's guide published on Microsoft's website, Server 2008 R2 will be available exclusively as a 64-bit OS.

source: zdnet.com.au