In this article, I would like to explain how LDAP proxy is a way to migrate “unmigratable” applications. The subject matters especially for critical legacy applications which have to be changed in the context of a Novell Migration. So let’s start the step-by-step tutorial for OpenLDAP proxy.
There are a lot of reasons why customers want to migrate from Novell eDirectory to Microsoft Active Directory. I would like to use this article to explain one of the core concerns of these projects to you. Should the Novell Client 2 be uninstalled or deactivated? What is the difference between these options?
A couple of weeks ago I had to migrate about 5,000 clients from Novell OES eDirectory to an Active Directory domain. None of the workstations were members of a NT- or AD-domain at that time. But still ADMT was our tool of choice.
Today we had to search a NDS eDirectory via Powershell script. After some tests and searching the internet we found the following solution.
- Azure Basics: Connecting with Azure (PowerShell)
- PowerShell Custom Objects
- Logon Script does not start on Windows Server 2012 R2 domain
- IsMember – Check group membership in Active Directory
- Dynamic OU Groups – Assign Permissions to OUs
- Mobile Video Streaming Server with Windows 10
- AD Administration in the new Azure Portal
- Novell Migration: Migrate Critical Legacy Applications with OpenLDAP Proxy
- NTFS Creator Owner Permissions
- Adding a Windows Server 2012 R2 DC to an Existing Domain