It feels like we have been promised the paperless office forever. When I first entered the IT industry in the mid 1990s, it was a mantra, and it is still a mantra today. The fact is, we still need to print. We may have moved away from managers’ administrative assistants printing emails for them to read, but the fact that HP still has a highly profitable printing arm that could afford a $1 billlion dip into its pocket to buy Samsung’s printing arm shows how big a business it still is. What is also interesting is that enterprises and businesses are still having so many problems. These problems are being compounded with the introduction of new end user technologies like DaaS, VDI, and mobile devices such as tablets and phones.
Articles Tagged with Active Directory
The past two years have seen an arms race at the high end of the virtualization arena. The biggest players in the space have competed furiously to add features and capabilities to their combined platform offerings, either by swallowing up smaller companies or investing heavily in product development. MDM, DaaS, hybrid cloud, profile management, application virtualization, application publishing, cloud orchestration—the largest competitors in the virtualization space have either provided, or are looking to provide, these and many more features.
In a meeting recently, I was quite taken aback to hear a reason given for not moving to 2012 R2 forest functional level—a reason to which I hadn’t previously been privy. The stated reason was, “in a few years, the Windows domain won’t be relevant anymore.” As someone who cut his IT teeth on Windows NT domains and has become intimately familiar with the Novell-inspired beast that we all know as Active Directory, I found the concept of an IT function without a domain backbone quite strange. Is there any mileage in the supposition that Windows domains will be irrelevant in the space of merely a few years?
In “Public Cloud Computing—Economics and Throats to Choke,” we pointed out that among the big four cloud vendors (Amazon, Google, Microsoft, and VMware), only one vendor offers both a complete on-premises offering and a public cloud offering and, at the same time, has complete technical and economic control of its software stack. That vendor would be Microsoft. In the post, we pointed out that Microsoft was in the unique position of being able to leverage its massive on-premises installed base to feed its cloud business.
Working with LDAP and Microsoft Active Directory: For most IT professionals, there has been some point in their career where they have connected a product or service to a Microsoft Active Directory with LDAP for authentication. This is especially true when working with the products in VMware’s vCloud suite. Most all the products in the vCloud suite like Single Sign-On (SSO) or VMware Operation Manager (vCOPs) as an example relies on LDAP communication to work and function properly. This is really nothing new and has been the trend for years, but I discovered a different way to set up the connections years ago when I was working on a script that would connect to Active Directory with an LDAP call to get a list of members of a group. I really thought most people already knew this and it was pretty much common knowledge, but it seems lately that every time I work with someone new setting up the LDAP configuration they seem to be quite surprised at the way I do things and I thought this should be something that I share out.
With the release of vSphere 4.1, VMware has added an impressive set of new features. These generally fall in the areas of improved manageability, improved performance and improved scalability. In essence, vSphere 4.1 is more than a point release, this update includes many features that aid in security, reliability, and is a direct response to customer requests.