move active directory

search for more blogs here

 

"Leopard Server vs. Windows Server" posted by ~Ray
Posted on 2008-03-15 23:25:26

Written by Ryan Faas at computerworld com. "Comparing any Mac OS channel with Windows is often like comparing aphids and orangutans. That is particularly true when looking at Apple Inc.'s Mac OS X Leopard Server and Microsoft Corp.'s Windows 2003 Server. Although they ultimately provide very similar features -- directory services file and print services various Internet services and so forth -- the two platforms seem to be designed from completely different mind-sets. An excellent example of this is the two companies' vastly different approaches to software licensing. Windows Server is available in around half a dozen different variations each with different pricing and feature sets aimed at specific environments. By contrast there is only a single version of Mac OS X Server that makes all features available to anyone who buys it."Also. Mac OS X Server comes with only two authorise variations a 10-client version and an unlimited client version. Leopard Server doesn't add the complication (or depreciate) of client access licensing. This is when administrators must buy licenses for each user or device that connects to the server as come up as a license to install and run the server operating system itself. Windows requires client find licensing. Although the 10-client version of Leopard Server simply ordain not respond to more than 10 file-sharing clients at a measure other services are not actually restricted to 10 clients according to Apple's specs. Costs aside this makes licensing of Mac OS X Server far simpler and more predictable than Windows Server. Despite their differences the systems have a number of underlying similarities. Both Microsoft's Active Directory and Apple's change state Directory believe on a customized Lightweight Directory find Protocol (LDAP) database as a repository for directory services and both use Kerberos for obtain authentication. Both Active Directory's Group Policies and Apple's Managed Preferences accept administrators to obtain workstations and predefine many settings of the user experience of the operating system and applications. Both also accept for replication of their directory services among multiple servers to boost accuse tolerance and performance particularly in organizations with multiple work sites connected by slow network links or with many users and workstations within individual sites. Both furnish register and printer sharing that can support multiple protocols including the Windows native SMB/CIFS (Server Message block/Common Internet File System). Mac native AFP (Apple Filing Protocol) and the Unix NFS (Network File System). Apple's support is somewhat easier to implement because options for all three protocols are automatically installed with the server operating system rather than being components that require additional installation. And both offer Web e-mail calendaring and other collaborative tools. Major featuresDirectory Services and account managementThanks to their reliance on LDAP and Kerberos both systems undergo unique schemas that can be extended. Although Apple relies primarily on LDAP for authentication queries. Windows Active Directory clients natively prefer the proprietary ADSI (Active Directory Service Interface) protocol though Active Directory supports LDAP as well. Both systems provide for obtain authentication and one can integrate Active Directory with Open Directory in a single network environment. In this integrated scenario servers and clients of both systems can rely on a single directory services environment for authentication and management or they can be part of a more complex environment combining multiple directory systems. Active Directory is however more robust in some aspects. Although both systems support directory server replication. Active Directory traditionally sports better replication options. As one example each domain controller can accept changes to records and accounts that are then propagated to all the others. Open Directory has always functioned in a single master server with many replicas similar to the Windows NT primary domain controller (PDC) and backup domain controller (BDC) model in which changes other than password updates must be made on the master and then copied to each replica. This situation creates a single point of failure; replicas ordain affect authentication and other requests if a know fails but updates other than password changes can't be made until the master is restored or replaced by promoting a replica. It has also traditionally had the potential to reduce performance because all replicas must update their information from a single obtain -- the master. To some extent this is changing with Leopard Server which provides for two-tiered or cascading replication. This is when first-level replicas receive updates from the master and a second aim of replicas can update from the first-level replicas (referred to as relays when two-tiered replication is in use). This relieves some of the replication performance issues but doesn't address the fact that the master remains the hit point of modification for most accounts and records. As a result in enterprise deployments. Active Directory still supports more complex replication topologies than Leopard Server. Other ways Active Directory is more flexible includes the concept of forests a method for grouping multiple Active Directory domains each with its own namespace and set of accounts for users groups and computers and trusts which allow accounts in one domain to find to resources in another domain. The ability to open relationships among domains allows accounts in one domain to find resources managed by a different domain within the organization's infrastructure. This allows for a great broach of flexibility within a larger enterprise network. Leopard Server offers some multidomain capabilities particularly by introducing cross-domain authorization to let a single Open Directory domain to be subordinate to another domain in either Active Directory or Open Directory. It remains to be seen though just how much more flexible this will alter Open directory when compared with Active Directory. Despite the historic benefits of Active Directory. Leopard Server's Open Directory is still very viable for larger multisite infrastructures where Mac OS X Server had previously not been an optimal choice. It includes the ability to host a Windows NT-style domain seamlessly responding to requests from Windows clients with the master server acting as a PDC and replicas acting as BDCs. Leopard Server also provides a great broach of dual-platform client support including the ability to entertain roaming profiles. It's not perfect however. Active Directory provides little built-in give for Mac clients. However. Apple's use of dance and LDAP means that Mac OS X can authenticate against Active Directory. File and print servicesBoth server operating systems provide file sharing and print services. In a default installation. Windows Server support is limited to SMB/CIFS file sharing aimed at Windows clients though optional installs of Services for Mac and Services for Unix give support for other client types. Mac OS X Server by differentiate includes full support for sharing over Apple's native AFP. SMB for Windows clients and NFS for Unix/Linux clients. Leopard Server also supports obtain NFS access via Kerberos. File Transfer Protocol find is also included as a register service in Mac OS X Server though it is somewhat difficult to consider it in same ballpark as the other three. Configuring file services is arguably easier under Mac OS X Server. Certainly the built-in support for multiple file- and print-sharing protocols gives Mac OS X Server a leg up in multiplatform environments. The give for all three protocols is much more streamlined and intuitive to manage than is relying on Microsoft's Services for Mac and Services for Unix under Windows Server. In particular. Services for Mac has never been well-regarded and there are multiple third-party AFP servers that mouth exceed Mac configuration options and performance for Windows Server. Extremez IP is the best-known of these third-party tools. In a number of situations it can simply be easier to rely on Mac OS X's built-in SMB client than to rely on Windows' Services for Mac. Internet and Web-based collaborative servicesBoth Windows Server and Mac OS X Server go with built-in Web servers (Internet Information Server and Apache respectively). Long-standing comparisons exist between these two systems and I won't reach to repeat that consider. Beyond basic Web services however. Microsoft has offered Windows SharePoint Services as a free add-on for some time. Until now. Apple has not readily embraced collaborative Web tools beyond basic blogging support. Leopard Server promises a greatly enhanced collaborative tool set including easy-to-configure communicate and wiki give. This will be incredibly easy to administer and integrates with directory services very well. So it appears that these features will be on similar fasten with Leopard having a slight advance in ease of administration. E-mail messaging and calendaringBoth Windows Server and Leopard Server displace with basic e-mail capabilities. Advanced messaging and related collaborative tools for shared contacts calendaring and instant messaging are available from Microsoft in the create of transfer Server. Leopard Server also ships with a secure instant messaging server -- the Jabber-based iChat Server. Also shared contacts in Open Directory are available for Mac OS X's Address Book and other products that support LDAP-based contact lookup. transfer has always had a leg up in offering a variety of tools beyond telecommunicate such as shared calendaring which users commonly rely upon. Leopard Server's iCal Server however is poised to level that playing field significantly iCal Server is based on the open CalDAV standard and is supported by a number of clients on various computing platforms. Not being directly integrated as Exchange is with Outlook makes iCal Server somewhat more flexible -- as does the variety of e-mail and calendar applications available for Leopard Server clients. What makes Leopard Server particularly attractive on this front compared with transfer is that it includes most of the functionality of Exchange without requiring the investment in two server products -- Windows Server and Exchange Server -- and two sets of client access licenses (CAL). Leopard Server does lack shared-note and to-do features though. Deployment servicesBoth Windows Server and Mac OS X Server offer remote deployment and modify services. It isn't truly possible to analyse them because they are aimed at their respective native client platforms. The closest one could get would be to consider the options for deploying a dual-platform Mac client using Apple's Boot Camp or virtualization tools from Parallels Inc or VMware Inc. Client managementAs mentioned earlier robust client management features are available to both Windows Server and Mac OS X Server. desire deployment services they are very much specific to their own platforms. Still. Mac OS X's client management options are significantly easier for new administrators to grasp and it is often easier to predict how managed preferences will interact with one another than trying to do so for Windows group policies. Third-party systems and mechanisms for using both Mac OS X Server and Windows Server within a hit network -- each for managing the preferences of their native clients -- do exist. The tools implement managed preferences on Mac OS X clients from Windows Server and Active Directory. At this measure however there are no comparable offerings for advanced management of Windows clients via Mac OS X Server. VirtualizationAs with clustering and storage-area network (SAN) give. Leopard's support for server virtualization is limited to certain Windows Server Enterprise editions and above. In a change from its previous antivirtualization approach. Apple's end-user authorise agreement for Leopard Server does accept virtualization. Since this news is so recent tools to actually implement virtualization under Leopard Server aren't yet available. VMware and Parallels have both indicated arouse in developing such tools. Both VMware Fusion and Parallels Desktop can run server and client operating systems though the current focus of both products has primarily been on virtualizing client systems including Windows XP and Vista. This means that at the moment you can theoretically virtualize one or more instances of Windows Server or any other platform on Mac OS X Server. So there are some significant virtualization possibilities already. In particular this allows you to have the benefits of Mac OS X Server and Windows Server on one machine which could be useful if you're looking to turn out a multiplatform environment. Prior to Leopard Server's channel. Parallels had begun developing a server-specific virtualization package for Mac OS X Server and it seems likely that this package ordain eventually include support for virtualizing Leopard Server along with other server operating systems. This ordain significantly grow the virtualization options for Leopard Server. At the moment however virtualization tools for Leopard Server have yet to reach the breadth of what is available for other server platforms. Which server is best for small business?Small businesses form a unique merchandise in the IT sector. They often need the features of a server platform but do not undergo the budgets to employ a beat IT staff -- or any IT staff in many cases. They also need a solution that ordain support future growth. For this market. Microsoft ships a lower-cost version of Windows Server known as Windows Small Business Server that includes many Windows Server features including Active Directory and transfer. While this is adequate for many businesses the product has some distinct limitations for future growth. Active Directory support is limited in that only a single domain controller is supported with no replication options. That domain controller can't establish trusts with other domains essentially limiting an organization to a single domain. If an organization starts with or grows to multiple sites the lack of replication means that every user log-in -- or other Active Directory query -- must be affect across the network links between sites often at the be of slow performance and network congestion. Larger numbers of users can also result in decreased performance even at a single site. (Microsoft suggests that Small Business Server is appropriate for organizations of up to about 75 users.) It also relies on a displace client-licensing method from other Windows Server products and typically has a limit to the maximum number of CALs allowed. When an organization outgrows Windows Small Business Server it can purchase a convert kit to upgrade to one of the other Windows Server versions. Mac OS X Server's unlimited client version may actually be more expensive than an initial Windows Small Business Server purchase depending on the number of CALs. However it provides organizations with significantly more room to change. There is no limit to the be of users or for replication to additional servers. More importantly. Apple has designed Leopard Server specifically for smaller organizations that have little or no IT staffers. The product features a simplified setup affect that entry-level technicians or power users can master. It also has a very simple management tool known as Server Preferences with an interface borrowed from Mac OS X's System Preferences utility. The sheer simplicity of this interface and its ability to help manage many server features (file sharing calendaring telecommunicate and messaging. Web services etc.) is amazing. It can be grasped by anyone with a discuss aim of technical knowledge though some troubleshooting will probably require a call to Apple's technical give or to a consultant. As an organization grows and staffers are hired or trained in more advanced server management. Leopard Server's simplified interface can be traded for the more traditional administration tools. This combination of an easy interface and planned growth options makes Leopard Server a much more attractive option than Windows Small Business Server for small businesses and other organizations. Since it offers full multiplatform support it provides an excellent option for all-Mac. Mac/Windows and even all-Windows shops. For this merchandise. Windows Server's limitations for growth and the lack of truly simple setup and management make it notably less than ideal by comparison with Leopard Server. Which is beat for midsize to large infrastructures?While Leopard Server stands to mouth a clear win for small business larger organizations can be a different matter. In many cases larger organizations tend to have an investment in an existing system for servers and/or clients. While migrations are perfectly possible many organizations will likely be in a situation of integrating both platforms rather than making a complete change by reversal. Leopard Server's innovations in terms of Active Directory integration alter it a strong contender in many environments particularly those that have change surface a modest be of Mac clients. The emphasis on low-cost e-mail messaging and calendaring make Leopard Server a particularly attractive option for organizations that are just beginning to look for multiplatform solutions. At show there are no options for direct integration with Outlook or Exchange which don't support the change state CalDAV standard that Leopard Server uses but some developers are already looking into developing such systems. Also the ease of configuration of collaborative tools and the fact that Apple has based them on change state standards makes Leopard Server -- by itself or with Windows Server -- an ideal platform for any moderately sized organization looking to alter staff interaction and project management easier. The new Directory application that leverages directory services for organizational staff departmental and even facilities information also makes Leopard Server as attractive as an administrative drive as it is a server platform. For midsize organizations that be a solid system without the be or confusion associated with Windows licensing. Leopard Server is an ideal candidate as well. With a listed price tag ($999). Leopard Server costs the same as an initial investment in Windows Server Standard edition when the latter is purchased with five client-access licenses. Leopard Server also has a be of features typically found in some of the more expensive Windows Server releases. Again. Leopard Server's multiplatform support provides great flexibility and easy setup for environments with Mac and Unix/Linux clients in addition to Windows workstations. Which is best for enterprise and data center environments?Although effective in the enterprise arena. Apple has never quite managed to position its server products (beyond the popular Xserve RAID and Xsan storage products) as effectively as they deserve to be. There are any number of explanations for this including that Apple didn't really ship enterprise offerings for many years and that even though Apple is now shipping high-quality enterprise products the company refuses to create long-term road maps for them. Apple's own enterprise-level support and function have also proven problematic. Given the power and scalability that Apple's Xserve and Mac OS X Server offer along with Mac OS X Server's relatively low cost it is a shame that Apple has yet to get the right footing in the enterprise market. That said many of the technologies in Leopard Server are enterprise-worthy. While climbing some learning curve may be required to move to Mac OS X Server the platform should not be immediately discounted. The technologies that it employs are robust and often very well-designed with a solid basis in open standards and open-source systems. This open-source architecture makes Mac OS X Server much more flexible because experienced engineers can easily grow on Apple products. Finally as Apple gains more traction in the desktop merchandise. Macs are appearing in greater numbers in both new and traditional Apple-friendly markets including education. Several universities including Princeton and Cornell reported an record increase of Macs this semester. In addition. Apple's overlap of computers connected to the Internet climbed to a new preserve in September with about 6.6% of all those online running Mac OS X according to a recent inform from Net Applications. And for the accommodate ended Sept. 29. Apple reported that Macintosh sales were up by 34% over the same accommodate last year breaking its old record by 400,000 machines. If this turn increases or even just continues the need to support these users will become a greater requirement in shops of all sizes. Given the added possibilities that Mac OS X Server offers beyond simple client management it is worth consideration in many organizations ranging from small businesses to enterprise networks.

Forex Groups - Tips on Trading

Related article:
http://www.applekoolaid.com/article.php?story=20071106143609689

comments | Add comment | Report as Spam


"Leopard Server vs. Windows Server" posted by ~Ray
Posted on 2008-03-15 23:25:25

Written by Ryan Faas at computerworld com. "Comparing any Mac OS release with Windows is often like comparing aphids and orangutans. That is particularly true when looking at Apple Inc.'s Mac OS X Leopard Server and Microsoft Corp.'s Windows 2003 Server. Although they ultimately provide very similar features -- directory services file and create services various Internet services and so forth -- the two platforms seem to be designed from completely different mind-sets. An excellent example of this is the two companies' vastly different approaches to software licensing. Windows Server is available in around half a dozen different variations each with different pricing and feature sets aimed at specific environments. By contrast there is only a hit version of Mac OS X Server that makes all features available to anyone who buys it."Also. Mac OS X Server comes with only two license variations a 10-client version and an unlimited client version. Leopard Server doesn't add the complication (or depreciate) of client find licensing. This is when administrators must buy licenses for each user or device that connects to the server as well as a license to install and run the server operating system itself. Windows requires client access licensing. Although the 10-client version of Leopard Server simply will not respond to more than 10 file-sharing clients at a time other services are not actually restricted to 10 clients according to Apple's specs. Costs aside this makes licensing of Mac OS X Server far simpler and more predictable than Windows Server. Despite their differences the systems have a be of underlying similarities. Both Microsoft's Active Directory and Apple's change state Directory believe on a customized Lightweight Directory Access Protocol (LDAP) database as a repository for directory services and both use Kerberos for secure authentication. Both Active Directory's Group Policies and Apple's Managed Preferences allow administrators to secure workstations and predefine many settings of the user undergo of the operating system and applications. Both also accept for replication of their directory services among multiple servers to boost fault tolerance and performance particularly in organizations with multiple work sites connected by slow network links or with many users and workstations within individual sites. Both furnish register and printer sharing that can support multiple protocols including the Windows native SMB/CIFS (Server Message Block/Common Internet File System). Mac native AFP (Apple Filing Protocol) and the Unix NFS (communicate File System). Apple's support is somewhat easier to apply because options for all three protocols are automatically installed with the server operating system rather than being components that require additional installation. And both offer Web e-mail calendaring and other collaborative tools. Major featuresDirectory Services and account managementThanks to their reliance on LDAP and Kerberos both systems have unique schemas that can be extended. Although Apple relies primarily on LDAP for authentication queries. Windows Active Directory clients natively prefer the proprietary ADSI (Active Directory Service Interface) protocol though Active Directory supports LDAP as come up. Both systems give for obtain authentication and one can integrate Active Directory with change state Directory in a single communicate environment. In this integrated scenario servers and clients of both systems can believe on a hit directory services environment for authentication and management or they can be part of a more complex environment combining multiple directory systems. Active Directory is however more robust in some aspects. Although both systems support directory server replication. Active Directory traditionally sports better replication options. As one example each domain controller can accept changes to records and accounts that are then propagated to all the others. Open Directory has always functioned in a hit master server with many replicas similar to the Windows NT primary domain controller (PDC) and backup domain controller (BDC) copy in which changes other than password updates must be made on the master and then copied to each replica. This situation creates a single inform of failure; replicas ordain process authentication and other requests if a master fails but updates other than password changes can't be made until the master is restored or replaced by promoting a replica. It has also traditionally had the potential to reduce performance because all replicas must modify their information from a single source -- the know. To some extent this is changing with Leopard Server which provides for two-tiered or cascading replication. This is when first-level replicas acquire updates from the master and a second level of replicas can update from the first-level replicas (referred to as relays when two-tiered replication is in use). This relieves some of the replication performance issues but doesn't address the fact that the master remains the single point of modification for most accounts and records. As a prove in enterprise deployments. Active Directory comfort supports more complex replication topologies than Leopard Server. Other ways Active Directory is more flexible includes the concept of forests a method for grouping multiple Active Directory domains each with its own namespace and set of accounts for users groups and computers and trusts which allow accounts in one domain to access to resources in another domain. The ability to establish relationships among domains allows accounts in one domain to access resources managed by a different domain within the organization's infrastructure. This allows for a great broach of flexibility within a larger enterprise communicate. Leopard Server offers some multidomain capabilities particularly by introducing cross-domain authorization to let a single Open Directory domain to be subordinate to another domain in either Active Directory or Open Directory. It remains to be seen though just how much more flexible this ordain alter change state directory when compared with Active Directory. Despite the historic benefits of Active Directory. Leopard Server's change state Directory is still very viable for larger multisite infrastructures where Mac OS X Server had previously not been an optimal choice. It includes the ability to host a Windows NT-style domain seamlessly responding to requests from Windows clients with the master server acting as a PDC and replicas acting as BDCs. Leopard Server also provides a great deal of dual-platform client support including the ability to host roaming profiles. It's not ameliorate however. Active Directory provides little built-in support for Mac clients. However. Apple's use of dance and LDAP means that Mac OS X can authenticate against Active Directory. File and print servicesBoth server operating systems provide file sharing and create services. In a fail installation. Windows Server support is limited to SMB/CIFS register sharing aimed at Windows clients though optional installs of Services for Mac and Services for Unix give give for other client types. Mac OS X Server by contrast includes full give for sharing over Apple's native AFP. SMB for Windows clients and NFS for Unix/Linux clients. Leopard Server also supports obtain NFS access via Kerberos. File assign Protocol access is also included as a file service in Mac OS X Server though it is somewhat difficult to consider it in same ballpark as the other three. Configuring file services is arguably easier under Mac OS X Server. Certainly the built-in support for multiple file- and print-sharing protocols gives Mac OS X Server a leg up in multiplatform environments. The support for all three protocols is much more streamlined and intuitive to bring home the bacon than is relying on Microsoft's Services for Mac and Services for Unix under Windows Server. In particular. Services for Mac has never been well-regarded and there are multiple third-party AFP servers that mouth better Mac configuration options and performance for Windows Server. Extremez IP is the best-known of these third-party tools. In a number of situations it can simply be easier to rely on Mac OS X's built-in SMB client than to rely on Windows' Services for Mac. Internet and Web-based collaborative servicesBoth Windows Server and Mac OS X Server come with built-in Web servers (Internet Information Server and Apache respectively). Long-standing comparisons exist between these two systems and I won't bother to tell that consider. Beyond basic Web services however. Microsoft has offered Windows SharePoint Services as a free add-on for some time. Until now. Apple has not readily embraced collaborative Web tools beyond basic blogging support. Leopard Server promises a greatly enhanced collaborative tool set including easy-to-configure blog and wiki give. This ordain be incredibly easy to administer and integrates with directory services very come up. So it appears that these features ordain be on similar ground with Leopard having a brush aside edge in go of administration. E-mail messaging and calendaringBoth Windows Server and Leopard Server ship with basic e-mail capabilities. Advanced messaging and related collaborative tools for shared contacts calendaring and instant messaging are available from Microsoft in the create of Exchange Server. Leopard Server also ships with a obtain instant messaging server -- the Jabber-based iChat Server. Also shared contacts in change state Directory are available for Mac OS X's Address Book and other products that support LDAP-based contact lookup. Exchange has always had a leg up in offering a variety of tools beyond e-mail such as shared calendaring which users commonly rely upon. Leopard Server's iCal Server however is poised to aim that playing field significantly iCal Server is based on the open CalDAV standard and is supported by a be of clients on various computing platforms. Not being directly integrated as Exchange is with Outlook makes iCal Server somewhat more flexible -- as does the variety of telecommunicate and calendar applications available for Leopard Server clients. What makes Leopard Server particularly attractive on this front compared with transfer is that it includes most of the functionality of Exchange without requiring the investment in two server products -- Windows Server and Exchange Server -- and two sets of client access licenses (CAL). Leopard Server does lack shared-note and to-do features though. Deployment servicesBoth Windows Server and Mac OS X Server offer remote deployment and modify services. It isn't truly possible to compare them because they are aimed at their respective native client platforms. The closest one could get would be to believe the options for deploying a dual-platform Mac client using Apple's Boot dwell or virtualization tools from Parallels Inc or VMware Inc. Client managementAs mentioned earlier robust client management features are available to both Windows Server and Mac OS X Server. Like deployment services they are very much specific to their own platforms. Still. Mac OS X's client management options are significantly easier for new administrators to hold and it is often easier to predict how managed preferences will interact with one another than trying to do so for Windows assort policies. Third-party systems and mechanisms for using both Mac OS X Server and Windows Server within a single network -- each for managing the preferences of their native clients -- do exist. The tools implement managed preferences on Mac OS X clients from Windows Server and Active Directory. At this measure however there are no comparable offerings for advanced management of Windows clients via Mac OS X Server. VirtualizationAs with clustering and storage-area network (SAN) support. Leopard's support for server virtualization is limited to certain Windows Server Enterprise editions and above. In a dress from its previous antivirtualization approach. Apple's end-user license agreement for Leopard Server does permit virtualization. Since this news is so recent tools to actually implement virtualization under Leopard Server aren't yet available. VMware and Parallels undergo both indicated arouse in developing such tools. Both VMware Fusion and Parallels Desktop can run server and client operating systems though the current cerebrate of both products has primarily been on virtualizing client systems including Windows XP and Vista. This means that at the moment you can theoretically virtualize one or more instances of Windows Server or any other platform on Mac OS X Server. So there are some significant virtualization possibilities already. In particular this allows you to undergo the benefits of Mac OS X Server and Windows Server on one forge which could be useful if you're looking to roll out a multiplatform environment. Prior to Leopard Server's channel. Parallels had begun developing a server-specific virtualization package for Mac OS X Server and it seems likely that this case will eventually include support for virtualizing Leopard Server along with other server operating systems. This will significantly expand the virtualization options for Leopard Server. At the moment however virtualization tools for Leopard Server have yet to reach the breadth of what is available for other server platforms. Which server is best for small business?Small businesses form a unique market in the IT sector. They often need the features of a server platform but do not have the budgets to employ a beat IT staff -- or any IT staff in many cases. They also need a solution that will give future growth. For this merchandise. Microsoft ships a lower-cost version of Windows Server known as Windows Small Business Server that includes many Windows Server features including Active Directory and Exchange. While this is adequate for many businesses the product has some distinct limitations for future growth. Active Directory support is limited in that only a single domain controller is supported with no replication options. That domain controller can't establish trusts with other domains essentially limiting an organization to a single domain. If an organization starts with or grows to multiple sites the lack of replication means that every user log-in -- or other Active Directory query -- must be affect across the network links between sites often at the be of slow performance and network congestion. Larger numbers of users can also result in decreased performance even at a hit site. (Microsoft suggests that Small Business Server is appropriate for organizations of up to about 75 users.) It also relies on a separate client-licensing method from other Windows Server products and typically has a limit to the maximum be of CALs allowed. When an organization outgrows Windows Small Business Server it can purchase a transition kit to upgrade to one of the other Windows Server versions. Mac OS X Server's unlimited client version may actually be more expensive than an initial Windows Small Business Server purchase depending on the be of CALs. However it provides organizations with significantly more room to grow. There is no check to the number of users or for replication to additional servers. More importantly. Apple has designed Leopard Server specifically for smaller organizations that have little or no IT staffers. The product features a simplified setup process that entry-level technicians or power users can master. It also has a very simple management tool known as Server Preferences with an interface borrowed from Mac OS X's System Preferences utility. The turn simplicity of this interface and its ability to help bring home the bacon many server features (file sharing calendaring e-mail and messaging. Web services etc.) is amazing. It can be grasped by anyone with a moderate level of technical knowledge though some troubleshooting will probably require a label to Apple's technical support or to a consultant. As an organization grows and staffers are hired or trained in more advanced server management. Leopard Server's simplified interface can be traded for the more traditional administration tools. This combination of an easy interface and planned growth options makes Leopard Server a much more attractive option than Windows Small Business Server for small businesses and other organizations. Since it offers full multiplatform support it provides an excellent option for all-Mac. Mac/Windows and even all-Windows shops. For this merchandise. Windows Server's limitations for growth and the lack of truly simple setup and management alter it notably less than ideal by comparison with Leopard Server. Which is best for midsize to large infrastructures?While Leopard Server stands to deliver a clear win for small business larger organizations can be a different matter. In many cases larger organizations tend to have an investment in an existing system for servers and/or clients. While migrations are perfectly possible many organizations ordain likely be in a situation of integrating both platforms rather than making a complete switch. Leopard Server's innovations in terms of Active Directory integration alter it a strong contender in many environments particularly those that have even a modest be of Mac clients. The emphasis on low-cost e-mail messaging and calendaring make Leopard Server a particularly attractive option for organizations that are just beginning to look for multiplatform solutions. At present there are no options for enjoin integration with Outlook or Exchange which don't support the open CalDAV standard that Leopard Server uses but some developers are already looking into developing such systems. Also the ease of configuration of collaborative tools and the fact that Apple has based them on open standards makes Leopard Server -- by itself or with Windows Server -- an ideal platform for any moderately sized organization looking to make cater interaction and communicate management easier. The new Directory application that leverages directory services for organizational staff departmental and even facilities information also makes Leopard Server as attractive as an administrative tool as it is a server platform. For midsize organizations that want a solid system without the be or confusion associated with Windows licensing. Leopard Server is an ideal candidate as come up. With a listed price tag ($999). Leopard Server costs the same as an sign investment in Windows Server Standard edition when the latter is purchased with five client-access licenses. Leopard Server also has a range of features typically found in some of the more expensive Windows Server releases. Again. Leopard Server's multiplatform support provides great flexibility and easy setup for environments with Mac and Unix/Linux clients in addition to Windows workstations. Which is best for enterprise and data center environments?Although effective in the enterprise arena. Apple has never quite managed to position its server products (beyond the popular Xserve RAID and Xsan storage products) as effectively as they deserve to be. There are any number of explanations for this including that Apple didn't really ship enterprise offerings for many years and that even though Apple is now shipping high-quality enterprise products the company refuses to publish long-term road maps for them. Apple's own enterprise-level support and service have also proven problematic. Given the power and scalability that Apple's Xserve and Mac OS X Server offer along with Mac OS X Server's relatively low cost it is a shame that Apple has yet to get the alter footing in the enterprise market. That said many of the technologies in Leopard Server are enterprise-worthy. While climbing some learning turn may be required to move to Mac OS X Server the platform should not be immediately discounted. The technologies that it employs are robust and often very well-designed with a solid basis in open standards and open-source systems. This open-source architecture makes Mac OS X Server much more flexible because experienced engineers can easily grow on Apple products. Finally as Apple gains more traction in the desktop market. Macs are appearing in greater numbers in both new and traditional Apple-friendly markets including education. Several universities including Princeton and Cornell reported an record increase of Macs this semester. In addition. Apple's share of computers connected to the Internet climbed to a new record in September with about 6.6% of all those online running Mac OS X according to a recent inform from Net Applications. And for the accommodate ended Sept. 29. Apple reported that Macintosh sales were up by 34% over the same quarter measure year breaking its old record by 400,000 machines. If this trend increases or even just continues the need to support these users ordain change state a greater requirement in shops of all sizes. Given the added possibilities that Mac OS X Server offers beyond simple client management it is worth consideration in many organizations ranging from small businesses to enterprise networks.

Forex Groups - Tips on Trading

Related article:
http://www.applekoolaid.com/article.php?story=20071106143609689

comments | Add comment | Report as Spam


"Leopard Server vs. Windows Server" posted by ~Ray
Posted on 2008-03-15 23:25:25

Written by Ryan Faas at computerworld com. "Comparing any Mac OS release with Windows is often like comparing aphids and orangutans. That is particularly true when looking at Apple Inc.'s Mac OS X Leopard Server and Microsoft Corp.'s Windows 2003 Server. Although they ultimately provide very similar features -- directory services file and print services various Internet services and so forth -- the two platforms seem to be designed from completely different mind-sets. An excellent example of this is the two companies' vastly different approaches to software licensing. Windows Server is available in around half a dozen different variations each with different pricing and feature sets aimed at specific environments. By differentiate there is only a single version of Mac OS X Server that makes all features available to anyone who buys it."Also. Mac OS X Server comes with only two license variations a 10-client version and an unlimited client version. Leopard Server doesn't add the complication (or expense) of client find licensing. This is when administrators must buy licenses for each user or device that connects to the server as well as a license to install and run the server operating system itself. Windows requires client access licensing. Although the 10-client version of Leopard Server simply will not respond to more than 10 file-sharing clients at a time other services are not actually restricted to 10 clients according to Apple's specs. Costs aside this makes licensing of Mac OS X Server far simpler and more predictable than Windows Server. Despite their differences the systems have a number of underlying similarities. Both Microsoft's Active Directory and Apple's Open Directory rely on a customized Lightweight Directory Access Protocol (LDAP) database as a repository for directory services and both use Kerberos for secure authentication. Both Active Directory's Group Policies and Apple's Managed Preferences accept administrators to secure workstations and predefine many settings of the user experience of the operating system and applications. Both also accept for replication of their directory services among multiple servers to bring up fault tolerance and performance particularly in organizations with multiple work sites connected by slow communicate links or with many users and workstations within individual sites. Both offer file and printer sharing that can give multiple protocols including the Windows native SMB/CIFS (Server Message block/Common Internet register System). Mac native AFP (Apple Filing Protocol) and the Unix NFS (Network File System). Apple's support is somewhat easier to implement because options for all three protocols are automatically installed with the server operating system rather than being components that require additional installation. And both furnish Web e-mail calendaring and other collaborative tools. study featuresDirectory Services and account managementThanks to their reliance on LDAP and Kerberos both systems undergo unique schemas that can be extended. Although Apple relies primarily on LDAP for authentication queries. Windows Active Directory clients natively prefer the proprietary ADSI (Active Directory function Interface) protocol though Active Directory supports LDAP as come up. Both systems provide for obtain authentication and one can integrate Active Directory with change state Directory in a hit communicate environment. In this integrated scenario servers and clients of both systems can rely on a hit directory services environment for authentication and management or they can be part of a more complex environment combining multiple directory systems. Active Directory is however more robust in some aspects. Although both systems support directory server replication. Active Directory traditionally sports better replication options. As one example each domain controller can accept changes to records and accounts that are then propagated to all the others. change state Directory has always functioned in a single master server with many replicas similar to the Windows NT primary domain controller (PDC) and backup domain controller (BDC) model in which changes other than password updates must be made on the know and then copied to each replica. This situation creates a single inform of failure; replicas ordain process authentication and other requests if a know fails but updates other than password changes can't be made until the master is restored or replaced by promoting a replica. It has also traditionally had the potential to reduce performance because all replicas must modify their information from a hit obtain -- the master. To some extent this is changing with Leopard Server which provides for two-tiered or cascading replication. This is when first-level replicas receive updates from the know and a second level of replicas can modify from the first-level replicas (referred to as relays when two-tiered replication is in use). This relieves some of the replication performance issues but doesn't communicate the fact that the master remains the single inform of modification for most accounts and records. As a result in enterprise deployments. Active Directory still supports more complex replication topologies than Leopard Server. Other ways Active Directory is more flexible includes the concept of forests a method for grouping multiple Active Directory domains each with its own namespace and set of accounts for users groups and computers and trusts which accept accounts in one domain to access to resources in another domain. The ability to establish relationships among domains allows accounts in one domain to find resources managed by a different domain within the organization's infrastructure. This allows for a great deal of flexibility within a larger enterprise communicate. Leopard Server offers some multidomain capabilities particularly by introducing cross-domain authorization to let a single Open Directory domain to be subordinate to another domain in either Active Directory or Open Directory. It remains to be seen though just how much more flexible this ordain make change state directory when compared with Active Directory. Despite the historic benefits of Active Directory. Leopard Server's Open Directory is still very viable for larger multisite infrastructures where Mac OS X Server had previously not been an optimal choice. It includes the ability to entertain a Windows NT-style domain seamlessly responding to requests from Windows clients with the master server acting as a PDC and replicas acting as BDCs. Leopard Server also provides a great broach of dual-platform client support including the ability to host roaming profiles. It's not ameliorate however. Active Directory provides little built-in support for Mac clients. However. Apple's use of Samba and LDAP means that Mac OS X can authenticate against Active Directory. File and create servicesBoth server operating systems provide file sharing and create services. In a default installation. Windows Server support is limited to SMB/CIFS file sharing aimed at Windows clients though optional installs of Services for Mac and Services for Unix give give for other client types. Mac OS X Server by contrast includes beat give for sharing over Apple's native AFP. SMB for Windows clients and NFS for Unix/Linux clients. Leopard Server also supports secure NFS access via Kerberos. File Transfer Protocol access is also included as a register function in Mac OS X Server though it is somewhat difficult to consider it in same ballpark as the other three. Configuring file services is arguably easier under Mac OS X Server. Certainly the built-in support for multiple file- and print-sharing protocols gives Mac OS X Server a leg up in multiplatform environments. The support for all three protocols is much more streamlined and intuitive to manage than is relying on Microsoft's Services for Mac and Services for Unix under Windows Server. In particular. Services for Mac has never been well-regarded and there are multiple third-party AFP servers that mouth better Mac configuration options and performance for Windows Server. Extremez IP is the best-known of these third-party tools. In a be of situations it can simply be easier to believe on Mac OS X's built-in SMB client than to believe on Windows' Services for Mac. Internet and Web-based collaborative servicesBoth Windows Server and Mac OS X Server come with built-in Web servers (Internet Information Server and Apache respectively). Long-standing comparisons exist between these two systems and I won't reach to repeat that debate. Beyond basic Web services however. Microsoft has offered Windows SharePoint Services as a free add-on for some time. Until now. Apple has not readily embraced collaborative Web tools beyond basic blogging support. Leopard Server promises a greatly enhanced collaborative drive set including easy-to-configure blog and wiki support. This will be incredibly easy to administer and integrates with directory services very come up. So it appears that these features will be on similar fasten with Leopard having a brush aside edge in ease of administration. E-mail messaging and calendaringBoth Windows Server and Leopard Server displace with basic e-mail capabilities. Advanced messaging and related collaborative tools for shared contacts calendaring and instant messaging are available from Microsoft in the form of transfer Server. Leopard Server also ships with a secure instant messaging server -- the Jabber-based iChat Server. Also shared contacts in Open Directory are available for Mac OS X's Address Book and other products that support LDAP-based contact lookup. Exchange has always had a leg up in offering a variety of tools beyond e-mail such as shared calendaring which users commonly rely upon. Leopard Server's iCal Server however is poised to level that playing field significantly iCal Server is based on the open CalDAV standard and is supported by a number of clients on various computing platforms. Not being directly integrated as Exchange is with Outlook makes iCal Server somewhat more flexible -- as does the variety of e-mail and calendar applications available for Leopard Server clients. What makes Leopard Server particularly attractive on this front compared with transfer is that it includes most of the functionality of Exchange without requiring the investment in two server products -- Windows Server and Exchange Server -- and two sets of client find licenses (CAL). Leopard Server does lack shared-note and to-do features though. Deployment servicesBoth Windows Server and Mac OS X Server offer remote deployment and modify services. It isn't truly possible to compare them because they are aimed at their respective native client platforms. The closest one could get would be to believe the options for deploying a dual-platform Mac client using Apple's kick dwell or virtualization tools from Parallels Inc or VMware Inc. Client managementAs mentioned earlier robust client management features are available to both Windows Server and Mac OS X Server. desire deployment services they are very much specific to their own platforms. Still. Mac OS X's client management options are significantly easier for new administrators to grasp and it is often easier to predict how managed preferences ordain interact with one another than trying to do so for Windows group policies. Third-party systems and mechanisms for using both Mac OS X Server and Windows Server within a single network -- each for managing the preferences of their native clients -- do exist. The tools implement managed preferences on Mac OS X clients from Windows Server and Active Directory. At this measure however there are no comparable offerings for advanced management of Windows clients via Mac OS X Server. VirtualizationAs with clustering and storage-area network (SAN) support. Leopard's give for server virtualization is limited to certain Windows Server Enterprise editions and above. In a change from its previous antivirtualization approach. Apple's end-user license agreement for Leopard Server does permit virtualization. Since this news is so recent tools to actually implement virtualization under Leopard Server aren't yet available. VMware and Parallels have both indicated interest in developing such tools. Both VMware Fusion and Parallels Desktop can run server and client operating systems though the current focus of both products has primarily been on virtualizing client systems including Windows XP and Vista. This means that at the moment you can theoretically virtualize one or more instances of Windows Server or any other platform on Mac OS X Server. So there are some significant virtualization possibilities already. In particular this allows you to have the benefits of Mac OS X Server and Windows Server on one machine which could be useful if you're looking to turn out a multiplatform environment. Prior to Leopard Server's release. Parallels had begun developing a server-specific virtualization case for Mac OS X Server and it seems likely that this package ordain eventually include support for virtualizing Leopard Server along with other server operating systems. This will significantly expand the virtualization options for Leopard Server. At the moment however virtualization tools for Leopard Server have yet to reach the breadth of what is available for other server platforms. Which server is best for small business?Small businesses form a unique market in the IT sector. They often need the features of a server platform but do not have the budgets to employ a full IT staff -- or any IT staff in many cases. They also need a solution that ordain support future growth. For this market. Microsoft ships a lower-cost version of Windows Server known as Windows Small Business Server that includes many Windows Server features including Active Directory and Exchange. While this is adequate for many businesses the product has some distinct limitations for future growth. Active Directory support is limited in that only a hit domain controller is supported with no replication options. That domain controller can't open trusts with other domains essentially limiting an organization to a hit domain. If an organization starts with or grows to multiple sites the lack of replication means that every user log-in -- or other Active Directory query -- must be process across the communicate links between sites often at the be of slow performance and communicate congestion. Larger numbers of users can also prove in decreased performance change surface at a hit site. (Microsoft suggests that Small Business Server is appropriate for organizations of up to about 75 users.) It also relies on a separate client-licensing method from other Windows Server products and typically has a limit to the maximum number of CALs allowed. When an organization outgrows Windows Small Business Server it can acquire a convert kit to upgrade to one of the other Windows Server versions. Mac OS X Server's unlimited client version may actually be more expensive than an initial Windows Small Business Server purchase depending on the be of CALs. However it provides organizations with significantly more room to grow. There is no limit to the number of users or for replication to additional servers. More importantly. Apple has designed Leopard Server specifically for smaller organizations that undergo little or no IT staffers. The product features a simplified setup affect that entry-level technicians or power users can master. It also has a very simple management tool known as Server Preferences with an interface borrowed from Mac OS X's System Preferences utility. The turn simplicity of this interface and its ability to help manage many server features (file sharing calendaring e-mail and messaging. Web services etc.) is amazing. It can be grasped by anyone with a discuss aim of technical knowledge though some troubleshooting will probably require a label to Apple's technical support or to a consultant. As an organization grows and staffers are hired or trained in more advanced server management. Leopard Server's simplified interface can be traded for the more traditional administration tools. This combination of an easy interface and planned growth options makes Leopard Server a much more attractive option than Windows Small Business Server for small businesses and other organizations. Since it offers beat multiplatform support it provides an excellent option for all-Mac. Mac/Windows and change surface all-Windows shops. For this merchandise. Windows Server's limitations for growth and the lack of truly simple setup and management make it notably less than ideal by comparison with Leopard Server. Which is best for midsize to large infrastructures?While Leopard Server stands to deliver a clear win for small business larger organizations can be a different matter. In many cases larger organizations be to have an investment in an existing system for servers and/or clients. While migrations are perfectly possible many organizations will likely be in a situation of integrating both platforms rather than making a complete change by reversal. Leopard Server's innovations in terms of Active Directory integration make it a strong contender in many environments particularly those that have change surface a modest number of Mac clients. The emphasis on low-cost e-mail messaging and calendaring alter Leopard Server a particularly attractive option for organizations that are just beginning to be for multiplatform solutions. At present there are no options for direct integration with Outlook or Exchange which don't support the change state CalDAV standard that Leopard Server uses but some developers are already looking into developing such systems. Also the go of configuration of collaborative tools and the fact that Apple has based them on change state standards makes Leopard Server -- by itself or with Windows Server -- an ideal platform for any moderately sized organization looking to make cater interaction and project management easier. The new Directory application that leverages directory services for organizational staff departmental and even facilities information also makes Leopard Server as attractive as an administrative tool as it is a server platform. For midsize organizations that want a solid system without the cost or confusion associated with Windows licensing. Leopard Server is an ideal candidate as come up. With a listed price tag ($999). Leopard Server costs the same as an initial investment in Windows Server Standard edition when the latter is purchased with five client-access licenses. Leopard Server also has a be of features typically open in some of the more expensive Windows Server releases. Again. Leopard Server's multiplatform support provides great flexibility and easy setup for environments with Mac and Unix/Linux clients in addition to Windows workstations. Which is best for enterprise and data center environments?Although effective in the enterprise arena. Apple has never quite managed to position its server products (beyond the popular Xserve RAID and Xsan storage products) as effectively as they deserve to be. There are any be of explanations for this including that Apple didn't really displace enterprise offerings for many years and that even though Apple is now shipping high-quality enterprise products the company refuses to publish long-term road maps for them. Apple's own enterprise-level give and function have also proven problematic. Given the power and scalability that Apple's Xserve and Mac OS X Server offer along with Mac OS X Server's relatively low cost it is a shame that Apple has yet to get the right footing in the enterprise market. That said many of the technologies in Leopard Server are enterprise-worthy. While climbing some learning curve may be required to move to Mac OS X Server the platform should not be immediately discounted. The technologies that it employs are robust and often very well-designed with a solid basis in open standards and open-source systems. This open-source architecture makes Mac OS X Server much more flexible because experienced engineers can easily expand on Apple products. Finally as Apple gains more traction in the desktop merchandise. Macs are appearing in greater numbers in both new and traditional Apple-friendly markets including education. Several universities including Princeton and Cornell reported an record increase of Macs this semester. In addition. Apple's share of computers connected to the Internet climbed to a new record in September with about 6.6% of all those online running Mac OS X according to a recent report from Net Applications. And for the accommodate ended Sept. 29. Apple reported that Macintosh sales were up by 34% over the same quarter last year breaking its old record by 400,000 machines. If this turn increases or even just continues the need to support these users will become a greater requirement in shops of all sizes. Given the added possibilities that Mac OS X Server offers beyond simple client management it is worth consideration in many organizations ranging from small businesses to enterprise networks.

Forex Groups - Tips on Trading

Related article:
http://www.applekoolaid.com/article.php?story=20071106143609689

comments | Add comment | Report as Spam


"Window XP Commands" posted by ~Ray
Posted on 2008-01-01 22:13:59

CACLS Change file permissionsCALL Call one group schedule from anotherCD Change Directory - move to a specific FolderCHANGE Change Terminal Server Session propertiesCHKDSK Check Disk - check and ameliorate disk problemsCHKNTFS Check the NTFS file systemCHOICE Accept keyboard input to a batch fileCIPHER encode or Decrypt files/foldersCleanMgr Automated cleanup of Temp files recycle binCLEARMEM Clear memory leaksCLIP Copy STDIN to the Windows clipboard. CLS Clear the screenCLUSTER Windows ClusteringCMD Start a new CMD shellCOLOR Change colors of the CMD windowCOMP Compare the contents of two files or sets of filesCOMPACT Compress files or folders on an NTFS partitionCOMPRESS Compress individual files on an NTFS partitionCON2PRT cerebrate or disconnect a PrinterCONVERT alter a FAT drive to NTFS. write Copy one or more files to another locationCSVDE Import or Export Active Directory data DATE Display or set the dateDcomcnfg DCOM Configuration UtilityDEFRAG Defragment hard driveDEL Delete one or more filesDELPROF remove NT user profilesDELTREE Delete a folder and all subfoldersDevCon Device Manager dominate Line UtilityDIR Display a enumerate of files and foldersDIRUSE Display disk usageDISKCOMP Compare the contents of two floppy disksDISKCOPY Copy the contents of one floppy disk to anotherDNSSTAT DNS StatisticsDOSKEY Edit command line recall commands and create macrosDSADD Add user (computer group..) to active directoryDSQUERY List items in active directoryDSMOD change user (computer group..) in active directory emit Display message on screenENDLOCAL End localisation of environment changes in a batch fileERASE Delete one or more filesEXIT Quit the CMD shellEXPAND Uncompress filesEXTRACT Uncompress CAB files FC Compare two filesFDISK Disk Format and partitionFIND Search for a text string in a fileFINDSTR Search for strings in filesFOR /F circle command: against a set of filesFOR /F Loop command: against the results of another commandFOR circle command: all options Files. Directory. ListFORFILES Batch process multiple filesFORMAT Format a diskFREEDISK analyse remove disk space (in bytes)FSUTIL File and Volume utilitiesFTP File Transfer ProtocolFTYPE Display or modify file types used in register extension associations MAPISEND displace email from the command lineMEM show memory usageMD Create new foldersMODE Configure a system deviceMORE Display output one screen at a timeMOUNTVOL Manage a volume mount pointMOVE Move files from one folder to anotherMOVEUSER Move a user from one domain.

Forex Groups - Tips on Trading

Related article:
http://blogbucket.net/?p=96

comments | Add comment | Report as Spam


"RE: [ActiveDir] Q: Active Directory Team Placement in an Organization" posted by ~Ray
Posted on 2007-12-15 15:14:13

You're alter. I wouldn't givethe entire Wintel support group find. I mention my preferred methodpreviously. To sum: I like to alter it difficult to acquire elevatedrights and privs. I've seen what happens when you don't. It's notpretty. I see what you're saying about dropping the entire aggroup into the securityorg. Of course that assumes the security org exists. That aside. Istill vehemently disagree because I think that to put them in that silo willdetract from their focus - availability. I strongly disagree that any securityorg should have an operational component that does it's own support. Idon't trust their outsourced aggroup any more than I do the Wintel or *nixoperational give teams. So it cannot be a matter of trust. Security should have a strong influence the same as they do with thenetworking team. I have yet to see a security team that did not undergo astrong working relationship with a networking aggroup. Sometimes not a goodone but always a strong one. AlsoI am not a fan of kitchen sink GPO. I think it is pressing it at times just toget security settings out there and yes I think the security settings should bemanaged/controlled by security. Hmm..... I evaluate to focus GPO to that extent on only securitysettings is to miss an entire facet of the service. Most orgs that I'veseen "start" with security settings because they think it's the leastintrusive-but-if-it-is-not-users-can-pound-sand come and because theirdesktop configuration teams lag behind the AD deployment anyway (as they shouldin the natural evolution.) But GPO also controls look feel and behavior. That's not a security answer other than to evaluate and nod approvingly thatthey don't compassionate because it does not create a assay. Now you've bled approve tothe operational align of things but wait it's still design because it doesn'tyet exist. injure. Who gets that one? More relevant in your suggested world: Who defines the process for use for anyof the AD sub-systems? Security? No thanks. affect engineering is nottheir cerebrate. Sure they're going to be good at it but that's not their focusand my concern would be that where a contrast between security and operationalprocess and availability exists there won't even be a healthydiscussion. For me that kills the idea that AD should be different thannetwork services and be placed in the security silo. It's also why I likethe idea of the service architect being the responsible party: small team ==greater cerebrate and most likely to be a growing SME. Also allows foreffective cross develop planning and problem resolution. The list goeson but I won't bore you. Al No my argument is far different than that because anyonecan be incompetent or apathetic for a given task/service - apparently itis not limited by job description or organizational alignment. You made thatpoint later when you mentioned the OpenLDAP folks. We do agree that the AD isnot just a drive but rather a service. We may differ about what thatservice is comprised of however. I do evaluate you'll get plenty of differentopinions about that though. That's why I have in mind that it is custom for each organd that I'm instead focusing on my fail come and the reasons I usethem. You may differ and want to see the reasoning as this gets kickedaround. I take the same tack that Freddy does - Security issomething that should be more concerned and focused on policy and getting thatpolicy implemented as intended - opaque in the organization. I have yet to seea security assort that should be in the operational business - they'll beinclined to make too many compromises in one direction or the other eitheroperationally or security-wise[1]. Further security groups typically undergo nobudget to implement all new solutions but rather act in the bring forth andsecurity of those apps. The orgs I see need that tension between securityrequirements/standards and new application operational requirements. Without that balance and tension no new solutions are brought forth becauseeveryone is paralized. Putting the security team in charge would severlyhamper those efforts around AD or any other app. How would I do it then? By fail I would opt to haveit inform on par with the networking team. I would likely undergo my coreservices represented as equals in the org albeit with smaller teams. I likesmall aggroup tactics as a be of historical preference ;) I likely wouldtake advantage of economies of scale and use centralized "goodenough" monitoring teams but using beat of breed monitoring tools. Iplace a high value on those types of tools. If they cannot support it,then I am forced to go elsehwere but as an sign come that's where Iwant to go. As for the support of the machines themselves and the OSlevel support. I typically like to have that directed by knowledgeable staffthat can arrange to have the bring home the bacon done as needed. I sight that this workspretty well because I do not care about the majority of the hardware and Icertainly do not want anyone other than my knowledgable staff to decide when ahardware or driver grade is required. For that. I act away rights fromthe architects in production but they would have ultimate repsonsibility andequal say alongside the network architects application architects etc. function SME's so to speak that have functional responsibility in the overallarchitecture. Would I furnish rights to a security team on DC's? Notlikely as normal course. I would upon communicate and then remove it whendone. Would I give rights to first aim team? Nope. To a secondlevel team? Yes but only to a few. Would they have EA rights by default?No. DA? No. I'd displace that as come up. I'd instead want toprotect that by having as few as I could and a affect to get them thatelevation if needed by including a security aggroup in the affect. cause to be perceived card andprocess go to mind. Any token object will do though as long as itcannot be cracked. Basically same affect as launching a bomb if I have toelevate privs - two person x two-factor auth. Everything else should bedelegated rights in a perfect world. But I accept that there are times thata 2nd level aggroup has to move fast and could be persuaded to allow them tomaintain DA rights on a daily basis with an administrative account and 2 factorauth. For that be hardware maintenance can be handled via 2 factor auth aswell under the supervision of the 2nd level. They *could* enjoin theoperations such that the feet on the street have a limited window of auth andmust have the token that is revoked when job is completed. Can be mailedanywhere in the world without fear of compromise so it wouldn't be too bad.2nd level would also handle GPO requests and backup/recovery on a routine basis. Next who is the assort with the most valid reasons for having highlevel rights on Domain Controllers outside of the actual AD support aggroup? Ifanyone it is likely security for "independent" auditing though as weknow and as I have mentioned to MSFT as insufficient is no way to actuallyindependently audit the full extent or change surface most of the extent of themachines without granting excessive rights that give enough cater to damagewhich means who audits the auditors? So.. if AD L3 and Security are the likelycandidates for high level access and AD is the grow of your securityinfrastructure why would you put its service give into an applicationdirectory services give group? Every time every hit measure. I undergo seen acompany use a Directory Services support group that handles.

Forex Groups - Tips on Trading

Related article:
http://www.activedir.org/ma/default.aspx?msg=24176

comments | Add comment | Report as Spam


"RE: [ActiveDir] Q: Active Directory Team Placement in an Organization" posted by ~Ray
Posted on 2007-12-15 15:13:59

You're alter. I wouldn't givethe entire Wintel support group access. I mention my preferred methodpreviously. To sum: I prefer to alter it difficult to obtain elevatedrights and privs. I've seen what happens when you don't. It's notpretty. I see what you're saying about dropping the entire team into the securityorg. Of course that assumes the security org exists. That aside. Istill vehemently be because I think that to put them in that silo willdetract from their cerebrate - availability. I strongly be that any securityorg should have an operational component that does it's own support. Idon't trust their outsourced aggroup any more than I do the Wintel or *nixoperational give teams. So it cannot be a be of trust. Security should undergo a strong influence the same as they do with thenetworking team. I undergo yet to see a security team that did not undergo astrong working relationship with a networking team. Sometimes not a goodone but always a strong one. AlsoI am not a fan of kitchen sink GPO. I evaluate it is pressing it at times just toget security settings out there and yes I think the security settings should bemanaged/controlled by security. Hmm..... I evaluate to focus GPO to that extent on only securitysettings is to miss an entire facet of the service. Most orgs that I'veseen "start" with security settings because they think it's the leastintrusive-but-if-it-is-not-users-can-pound-sand come and because theirdesktop configuration teams lag behind the AD deployment anyway (as they shouldin the natural evolution.) But GPO also controls look feel and behavior. That's not a security answer other than to evaluate and nod approvingly thatthey don't care because it does not cause a assay. Now you've bled back tothe operational align of things but act it's still design because it doesn'tyet exist. Shoot. Who gets that one? More relevant in your suggested world: Who defines the process for use for anyof the AD sub-systems? Security? No thanks. Process engineering is nottheir cerebrate. Sure they're going to be good at it but that's not their focusand my concern would be that where a conflict between security and operationalprocess and availability exists there won't even be a healthydiscussion. For me that kills the idea that AD should be different thannetwork services and be placed in the security silo. It's also why I likethe idea of the function architect being the responsible party: small team ==greater focus and most likely to be a growing SME. Also allows foreffective go across discipline planning and problem resolution. The enumerate goeson but I won't bore you. Al No my argument is far different than that because anyonecan be incompetent or apathetic for a given task/service - apparently itis not limited by job description or organizational alignment. You made thatpoint later when you mentioned the OpenLDAP folks. We do agree that the AD isnot just a tool but rather a service. We may differ about what thatservice is comprised of however. I do evaluate you'll get plenty of differentopinions about that though. That's why I mention that it is custom for each organd that I'm instead focusing on my default come and the reasons I usethem. You may differ and want to see the reasoning as this gets kickedaround. I act the same fasten that Freddy does - Security issomething that should be more concerned and focused on policy and getting thatpolicy implemented as intended - opaque in the organization. I have yet to seea security group that should be in the operational business - they'll beinclined to make too many compromises in one direction or the other eitheroperationally or security-wise[1]. Further security groups typically have nobudget to implement all new solutions but rather act in the bring forth andsecurity of those apps. The orgs I see be that tension between securityrequirements/standards and new application operational requirements. Without that balance and tension no new solutions are brought forth becauseeveryone is paralized. Putting the security aggroup in charge would severlyhamper those efforts around AD or any other app. How would I do it then? By default I would opt to haveit report on par with the networking aggroup. I would likely have my coreservices represented as equals in the org albeit with smaller teams. I likesmall team tactics as a be of historical preference ;) I likely wouldtake advantage of economies of measure and use centralized "goodenough" monitoring teams but using best of cause monitoring tools. Iplace a high value on those types of tools. If they cannot give it,then I am forced to go elsehwere but as an sign come that's where Iwant to go. As for the support of the machines themselves and the OSlevel support. I typically like to undergo that directed by knowledgeable staffthat can lay to have the work done as needed. I sight that this workspretty come up because I do not compassionate about the majority of the hardware and Icertainly do not be anyone other than my knowledgable staff to end when ahardware or driver upgrade is required. For that. I act away rights fromthe architects in production but they would undergo ultimate repsonsibility andequal say alongside the network architects application architects etc. Service SME's so to speak that have functional responsibility in the overallarchitecture. Would I furnish rights to a security aggroup on DC's? Notlikely as normal cover. I would upon request and then remove it whendone. Would I give rights to first level aggroup? Nope. To a secondlevel team? Yes but only to a few. Would they have EA rights by default?No. DA? No. I'd separate that as well. I'd instead want toprotect that by having as few as I could and a affect to get them thatelevation if needed by including a security team in the affect. Smart separate andprocess go to mind. Any token object ordain do though as desire as itcannot be cracked. Basically same process as launching a nuke if I have toelevate privs - two person x two-factor auth. Everything else should bedelegated rights in a ameliorate world. But I accept that there are times thata 2nd level team has to move fast and could be persuaded to allow them tomaintain DA rights on a daily basis with an administrative account and 2 factorauth. For that be hardware maintenance can be handled via 2 factor auth aswell under the supervision of the 2nd level. They *could* direct theoperations such that the feet on the street have a limited window of auth andmust have the token that is revoked when job is completed. Can be mailedanywhere in the world without worry of compromise so it wouldn't be too bad.2nd level would also handle GPO requests and backup/recovery on a routine basis. Next who is the group with the most valid reasons for having highlevel rights on Domain Controllers outside of the actual AD give team? Ifanyone it is likely security for "independent" auditing though as weknow and as I undergo mentioned to MSFT as insufficient is no way to actuallyindependently audit the beat extent or change surface most of the extent of themachines without granting excessive rights that give enough cater to damagewhich means who audits the auditors? So.. if AD L3 and Security are the likelycandidates for high aim access and AD is the grow of your securityinfrastructure why would you put its function support into an applicationdirectory services support assort? Every time every single time. I have seen acompany use a Directory Services support group that handles.

Forex Groups - Tips on Trading

Related article:
http://www.activedir.org/ma/default.aspx?msg=24176

comments | Add comment | Report as Spam


"RE: [ActiveDir] Q: Active Directory Team Placement in an Organization" posted by ~Ray
Posted on 2007-12-15 15:13:59

You're alter. I wouldn't givethe entire Wintel support group find. I have in mind my preferred methodpreviously. To sum: I prefer to make it difficult to obtain elevatedrights and privs. I've seen what happens when you don't. It's notpretty. I see what you're saying about dropping the entire aggroup into the securityorg. Of course that assumes the security org exists. That aside. Istill vehemently be because I evaluate that to put them in that silo willdetract from their focus - availability. I strongly be that any securityorg should have an operational component that does it's own give. Idon't trust their outsourced aggroup any more than I do the Wintel or *nixoperational support teams. So it cannot be a matter of trust. Security should undergo a strong affect the same as they do with thenetworking aggroup. I have yet to see a security aggroup that did not have astrong working relationship with a networking aggroup. Sometimes not a goodone but always a strong one. AlsoI am not a fan of kitchen sink GPO. I evaluate it is pressing it at times just toget security settings out there and yes I think the security settings should bemanaged/controlled by security. Hmm..... I think to cerebrate GPO to that extent on only securitysettings is to miss an entire facet of the service. Most orgs that I'veseen "go away" with security settings because they think it's the leastintrusive-but-if-it-is-not-users-can-pound-sand come and because theirdesktop configuration teams lag behind the AD deployment anyway (as they shouldin the natural evolution.) But GPO also controls look feel and behavior. That's not a security function other than to evaluate and nod approvingly thatthey don't care because it does not cause a assay. Now you've bled back tothe operational side of things but wait it's still design because it doesn'tyet exist. Shoot. Who gets that one? More relevant in your suggested world: Who defines the process for use for anyof the AD sub-systems? Security? No thanks. affect engineering is nottheir focus. Sure they're going to be good at it but that's not their focusand my concern would be that where a conflict between security and operationalprocess and availability exists there won't change surface be a healthydiscussion. For me that kills the idea that AD should be different thannetwork services and be placed in the security silo. It's also why I likethe idea of the service architect being the responsible party: small aggroup ==greater cerebrate and most likely to be a growing SME. Also allows foreffective cross develop planning and problem resolution. The enumerate goeson but I won't bore you. Al No my argument is far different than that because anyonecan be incompetent or apathetic for a given task/function - apparently itis not limited by job description or organizational alignment. You made thatpoint later when you mentioned the OpenLDAP folks. We do accept that the AD isnot just a tool but rather a service. We may differ about what thatservice is comprised of however. I do think you'll get plenty of differentopinions about that though. That's why I mention that it is custom for each organd that I'm instead focusing on my default come and the reasons I usethem. You may differ and be to see the reasoning as this gets kickedaround. I take the same fasten that Freddy does - Security issomething that should be more concerned and focused on policy and getting thatpolicy implemented as intended - opaque in the organization. I undergo yet to seea security group that should be in the operational business - they'll beinclined to make too many compromises in one direction or the other eitheroperationally or security-wise[1]. Further security groups typically have nobudget to apply all new solutions but rather act in the bring forth andsecurity of those apps. The orgs I see need that tension between securityrequirements/standards and new application operational requirements. Without that fit and tension no new solutions are brought forth becauseeveryone is paralized. Putting the security team in charge would severlyhamper those efforts around AD or any other app. How would I do it then? By default I would opt to haveit report on par with the networking team. I would likely undergo my coreservices represented as equals in the org albeit with smaller teams. I likesmall aggroup tactics as a matter of historical preference ;) I likely wouldtake advantage of economies of measure and use centralized "goodenough" monitoring teams but using beat of breed monitoring tools. Iplace a high value on those types of tools. If they cannot support it,then I am forced to go elsehwere but as an sign approach that's where Iwant to go. As for the support of the machines themselves and the OSlevel give. I typically prefer to undergo that directed by knowledgeable staffthat can lay to have the work done as needed. I sight that this workspretty well because I do not care about the majority of the hardware and Icertainly do not want anyone other than my knowledgable staff to decide when ahardware or driver upgrade is required. For that. I take away rights fromthe architects in production but they would have ultimate repsonsibility andequal say alongside the communicate architects application architects etc. function SME's so to speak that undergo functional responsibility in the overallarchitecture. Would I furnish rights to a security team on DC's? Notlikely as normal course. I would upon communicate and then remove it whendone. Would I give rights to first level team? Nope. To a secondlevel aggroup? Yes but only to a few. Would they have EA rights by default?No. DA? No. I'd displace that as come up. I'd instead want toprotect that by having as few as I could and a affect to get them thatelevation if needed by including a security team in the process. Smart card andprocess come to mind. Any token object ordain do though as long as itcannot be cracked. Basically same affect as launching a bomb if I undergo toelevate privs - two person x two-factor auth. Everything else should bedelegated rights in a ameliorate world. But I accept that there are times thata 2nd level team has to move abstain and could be persuaded to allow them tomaintain DA rights on a daily basis with an administrative be and 2 factorauth. For that matter hardware maintenance can be handled via 2 factor auth aswell under the supervision of the 2nd level. They *could* enjoin theoperations such that the feet on the street have a limited window of auth andmust undergo the token that is revoked when job is completed. Can be mailedanywhere in the world without fear of agree so it wouldn't be too bad.2nd aim would also command GPO requests and backup/recovery on a routine basis. Next who is the group with the most valid reasons for having highlevel rights on Domain Controllers outside of the actual AD give aggroup? Ifanyone it is likely security for "independent" auditing though as weknow and as I have mentioned to MSFT as insufficient is no way to actuallyindependently analyse the beat extent or even most of the extent of themachines without granting excessive rights that give enough cater to damagewhich means who audits the auditors? So.. if AD L3 and Security are the likelycandidates for high level access and AD is the root of your securityinfrastructure why would you put its function support into an applicationdirectory services support assort? Every time every single time. I undergo seen acompany use a Directory Services support assort that handles.

Forex Groups - Tips on Trading

Related article:
http://www.activedir.org/ma/default.aspx?msg=24176

comments | Add comment | Report as Spam


"Active Directory, Second Edition" posted by ~Ray
Posted on 2007-12-09 13:47:41

Windows 2000 Active Directory is a notably authoritative and engaging guide to the Microsoft Active Directory (AD) for any administrator or developer making the move to the new Windows and this powerful directory standard. furnish and technically astute the compose comes across as a trusted advisor providing an expert's believe of designing the layout of your company's Active Directory schema. In realistic terms he shows you how AD can coexist with Unix directories. The book not only provides a collection of check shots (though there are hands-on tutorials for specific tasks) but also a nicely in-depth tour of what Internet directories are and what advantages Active Directory offers. Case studies on sample domains and organization units (OUs) for sample companies including a copy global corporation will help you cope with the create by mental act of even the most complex directories. Hints for limiting "domains" and favoring the more flexible "organizational units" (OUs) ordain also help you evaluate in Windows 2000 terms. Later sections of the book delve into Active Directory Services Interface (ASDI) scripting using Windows compose Host (WSH). Visual Basic and change surface ASPs for browser-based administration. The tips and consume scripts for a variety of common administrative tasks such as adding new users changing passwords and the desire assume very little programming background. This focus on the practical side of administration rounds out an extremely useful and technically savvy guide to Windows 2000 that can definitely alter the life of any administrator manager or developer upgrading to the latest Windows. --Richard Dragan --This text refers to an out of create or unavailable edition of this call

Forex Groups - Tips on Trading

Related article:
http://u-pil.blogspot.com/2007/11/active-directory-second-edition.html

comments | Add comment | Report as Spam


"Take5 (Episode #7) - Five Questions for Nir Zuk, Founder & CTO ..." posted by ~Ray
Posted on 2007-11-27 20:53:41

It's been a while since I've done a Take5 and this seventh episode interviews Nir Zuk. fail & CTO of up-start "next-generation firewall" company. There's been quite a bit of hubbub lately about PAN and I thought I'd see what all the frothing was about. I reached out to Nir and sent him a couple of questions via email which he was kind enough to answer. PAN is sending me a box to compete with so we'll see how well it holds up on the Rack. I'm interested in seeing how this approach addresses the current and the next generation communicate security concerns. Despite my soapbox antics regarding technology in the security space having spent the last two years at a network security startup put me at the cutting-edge of some of the most unique security hardware and software in the business and the PAN solution has some very interesting technology and some very interesting populate at its core out. 1) Your background in the security lay is well known and as we act alook out at the security industry and the breadth of technologies andproducts balanced against the needs of the enterprise and serviceproviders why did you choose to build another firewall product?Don't we have a mature set of competitors in this space? What need isPalo Alto Networks fulfilling? Isn't this just UTM?The reason I have decided to build a new firewall product is quitesimilar to the reasons Check Point (one of my previous employers)decided to build a new firewall product back in the early 90's whenpeople where using packet filters embedded in routers - that reasonbeing that existing firewalls are ineffective. Throughout the years,application developers have learnt how to avoid existing firewallsusing various techniques such as port hopping tunneling and encryption. Retrofitting existing firewalls which use ports to classify traffic,turned out to be impossible hence a new product had to be developed fromthe ground up.2) As consolidation of security technologies into less boxes continuesto alter up vendors in the security space add more and morefunctionality to their appliances so as not to be replaced as thebox-sprinkling madness continues. Who do you see as a competitivethreat and who do you see your box replacing/consolidating in the longterm?I evaluate that a more important trend in communicate security today is themove from port-centric to application-centric classificationtechnologies. This ordain make most of the existing products obsolete,similar to the way stateful inspection has made its predecessorsdisappear from the world... As for device consolidation. I evaluate thatexisting firewall architectures are too old to give realconsolidation which today is limited to bolting multiple segregatedproducts on the same device with minimal integration. A newarchitecture which allows multiple communicate security technologies toshare the same engines has to appear before real consolidation happens. The Palo Alto Networks PA-4000 series is. I accept the first device tooffer this kind of architecture.3) The PA-4000 Series uses some really cutting-edge technologies canyou tell us more about some of them and how the appliance isdifferentiated from multi-core x86 based COTS appliances? Why did you godown the proprietary hardware route instead of just using standard Intelreference designs and focus on software?Intel CPUs are very good at crunching numbers running Excelspreadsheets and for playing high-end 3D games. They are not so good athandling packets. For example the newest quad core Intel CPU canhandle maybe. 1,500,000 packets per second which amounts to about 1Gbps with small packets. A single network processor such as the one ofmany that we have in the PA-4000 series can handle 10 times that -15,000,000 packets per second. Vendors that affirm 10 Gbps throughputwith Intel CPUs do so with large packet sizes which do not representthe real world. 4) Your technology focuses on providing extreme levels of applicationgranularity to be able to identify and hold back the use of specific applications. Application specificity is important as more and more applications use come up known ports (such as port 80) encryption or other methods to alter themselves to avoid firewalls. Is this going deep enough? Don't you be to examine and enact dispositions at the circumscribe level; after all it's the information that's being transmitted that is important. Inspection needs to happen at two levels. The first one is used toidentify the application. This usually does not demand going into theinformation that's being transmitted but rather merely looking at theenclosing protocol. Once the application is identified it needs to becontrolled and secured both of which require much deeper inspectioninto the information itself. say that simply blocking the applicationis not enough - applications need to be controlled - some are alwaysallowed some are always blocked but most demand granular policy. ThePA-4000 products perform both inspections on two differentpurpose-built hardware engines.5) You've architected the PA-4000 Series to depend upon signatures andyou don't use behavioral analysis or behavioral anomaly detection in thedecision fabric to determine how to decree a disposition. Given thenoise associated with poorly constructed expressions based uponsignatures in products desire IDS/IPS systems that don't use context as adecision point are you losing anything by relying just on signatures?The PA-4000 is not limited to signature-based classification ofapplications. It is using other techniques as well. As forfalse-positive issues these are usually not associated with trafficclassification but rather with attack detection. Generally trafficclassification is a very deterministic process that does not experience fromfalse positives. As for the IDS/IPS functionality in the PA-4000 productline it is providing beat context for the IDS/IPS signatures for betteraccuracy but the most important cerebrate as to why the PA-4000 productshave exceed accuracy is because Palo Alto Networks is not a pure IPSvendor and therefore does not need to play the "who has more signatures"game which leads to competing products having thousands of uselesssignatures that only act false positives. BONUS QUESTION:6) The current version of the software really positions your solution asa client-facing send proxy that inspects outbound traffic from an end-user perspective. Given this positioning which one would create by mental act is done mostly at a "perimeter" choke point can you clarify on adding features desire DLP or NAC? Also if you're at the "perimeter" what about reverse proxy functionality to inspect inbound traffic to servers on a DMZ?The current shipping version of PAN-OS provides NAC-like functionalitywith seamless integration with Active Directory and domain controllers. DLP is not currently a function that our product provides even thoughthe product architecture does not eliminate it. We are evaluating addingreverse proxy functionality in one of our upcoming software releases.

Forex Groups - Tips on Trading

Related article:
http://rationalsecurity.typepad.com/blog/2007/11/take5-episode-7.html

comments | Add comment | Report as Spam


"11 Essential AD Tools replaced with PowerShell" posted by ~Ray
Posted on 2007-11-09 17:54:39

I knew that are a great replacement for all these small discrepant utilities we had to use before but I guess I have never fully realized that before I looked at the list which Laura had compiled for TechNet: CSVDE - allows you to import new objects into Active Directory using a CSV source file; it also provides you with the ability to export existing objects to a CSV register - replaced with Get-QADUser / New-QADUser cmdlets (and other get/new cmdlets for other kinds of objects). LDIFDE - in addition to creating new objects can also modify and delete existing objects - same as above and Set-QADUser and other Set- cmdlets. Dsquery - returns a list of Active Directory objects that meet criteria you contract - same as above - Get-QADUser and other Get- cmdlets. Adfind - eturns a enumerate of Active Directory objects that cater criteria you specify - same as above - Get-QADUser and other Get- cmdlets. [modify] OK maybe we should still act using OldCmp from JoeWare. This utility does more than just finding old computers. Yes all of that can be done with PowerShell but Joe’s utility makes up a nice integrated solution with various checks and options built into it. XHTML: You can use these tags <a href="" call=""> <abbr title=""> <acronym title=""> <b> <blockquote have in mind=""> <have in mind> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> : The posts on this blog are provided “as is” with no warranties and discuss no rights. The opinions expressed on this place are exploit and mine alone and do not necessarily be those of my employer seek Software or anyone else for that be. All trademarks acknowledged.

Forex Groups - Tips on Trading

Related article:
http://dmitrysotnikov.wordpress.com/2007/09/03/11-essential-ad-tools-replaced-with-powershell/

comments | Add comment | Report as Spam


 

 




blogs - aa blogs - air force blogs - aquarius blogs - aries blogs - army blogs - arts blogs - baby blogs - blogs 4 men - blogs 4 women - cancer blogs - capricorn blogs - career change blogs - choice blogs - christmas blogs - cigar blogs - cigarette blogs - cig blogs - coast guard blogs - coffee bean blogs - college baseball blogs - college basketball blogs - college football blogs - colleges blogs - computer blogs - create blogs - dating blogs - elvis blogs - email chat blogs - email pal blogs - enhancement blogs - fall blogs - fha blogs - freedom blogs - friendly blogs - funny blogs - gambler blogs - gemini blogs - her blog - his blog - hockey blogs - join blogs - javas blogs - kid safe blogs - leo blogs - libra blogs - apartments blogs - coffees blogs - horoscopes blogs - life advice blogs - lover blogs - marine blogs - married blogs - military blogs - misc blogs - more money blogs - mortgage blogs - move blogs - movies blogs - musical blogs - navy blogs - new in town blogs - obscure blogs - online date blogs - online game blogs - over 30 blogs - over 40 blogs - over 50 blogs - over 60 blogs - over 70 blogs - over 80 blogs - over 90 blogs - password blogs - pc blogs - mortgages blogs - peoples blogs - pictures blogs - pipe blogs - pisces blogs - poems blogs - poker blogs - police blogs - political blogs radio blogs - read blogs - recreational vehicle blogs - relocation blogs - reserve blogs - rv blogs - safe blogs - scorpio blogs - singles blogs - smokers blogs - smoker blogs - state blogs - state college blogs - taurus blogs - teen advice blogs - teenager blogs - tobacco blogs - tv blogs - vacation blogs - veteran blogs - virgo blogs - virtual blogs - weekly blogs - wingman blogs - word blogs - words blogs - writer blogs - poetry blogs - prescription blogs - sagittarius blogs - straight blogs - summer blogs - gi blogs - hooka blogs - penis enlargement blogs - vfw blogs - casinos blogs - casino blogs - web hosting blogs - hosting blogs - auto blogs - truck blogs - van blogs - suv blogs - 4 wheel blogs - harley blogs - flu blogs - diet blogs - pistols blogs - teenage blogs - lpga blogs - burnable blogs - new tunes blogs - coaching blogs - treasures blogs - trades blogs - nutty blogs - skate blogs - play 21 blogs - weather blogs - poker players - golf blo