Posted by Akos Sandor
, Binary Tree Senior Solutions Architect
When you are migrating something as complex as Active Directory, the risk of something going awry can never be totally eliminated. An Active Directory migration has many points of possible failure. Objects may fail to migrate. SID history may fail to migrate. Passwords could fail to sync. ADPrep could encounter an LDAP error. Incorrect DNS name resolution settings or old device drivers could cause errors.
Active Directory migration errors and failures can have an immediate impact on your users. Most of your IT infrastructure, including email, servers and applications, is dependent upon Active Directory. If the migration does fail or experience errors, chances are your IT help desk will get a number of frantic phone calls.
READ MORE >>
Obviously, properly analyzing your current environment, planning the target environment, and testing the migration in a lab setting will help to minimize the risk of migration failures, but you also need to have a plan and method for the rollback of Active Directory to a previous state just in case an error or failure does occur.
And the real challenge is to be able to reverse the steps in your Active Directory migration safely and easily. So what are your options?
Posted by Steven Pivnik, CEO
The Binary Tree
sign has been hung up this week and our new headquarters is now finally complete! The multi-colored rooms, wishbone cubes, video conferencing, glass walled conference rooms and a huge fridge stocked with Mountain Dew definitely gives this place a cool Dot Com era startup look and feel. That’s a pretty strange feeling considering that we celebrated our 20-year anniversary just a few months ago.
Having a new place of business and seeing many new faces in it definitely makes it feel like there is opportunity for many new beginnings even though Binary Tree has been around for what may be considered an eternity in the software space. Sometimes it feels like it was forever ago that we spent many a late night in our humble surroundings in 150 square feet of space in downtown New York City writing code and solving cool problems.
READ MORE >>
Posted by Akos Sandor, Binary Tree Senior Solutions Architect
Active Directory (AD) migrations are complex and challenging IT projects. And some AD migration scenarios can compound the complexity of these projects. For instance, in order to facilitate an AD migration between two companies going through a merger, trust relationships are usually set up between the AD domains of each organization.
But when one company is acquiring only a portion of another company, like a subsidiary or division, the company that is selling off the business unit typically will not enable trust relationships to be set up between their AD infrastructure and the infrastructure of the acquiring organization. Their security policies likely prohibit them from doing so due to how they manage risk and govern regulatory compliance.
So how can you overcome this challenge to successfully migrate AD without having trust relationships in place?
READ MORE >>
Posted by Perry Hiltz
, Binary Tree Solutions Architect
When organizations are making the move from Domino-based messaging over to Exchange-based messaging, the question of how to migrate personal contacts becomes a question that always leaves room for questions.
First off, let’s discuss how contacts work within a Lotus Notes client. In a Lotus Notes client, each user has a Personal Address Book typically with a file name of names.nsf within the local Notes Client Data path. Regardless of the type of workstation implementation, (single or multi-user) the file is usually specific to the person logged into Lotus Notes. When a user saves a contact or email address, it is stored within this personal address book. If the user is not a mobile user, or a user with a connected mobile device, there typically is not a need to synchronize these contacts with their mail file. If users are using iNotes or a mobile device, then the contacts can be synchronized a number of different ways.
The purpose of synchronization is to enable the user to access their personal contacts and groups via iNotes or connected devices such as smartphones or tablets. The question is why not do this for everyone? The reason is simple. It adds resources to the server and to the workstation.
READ MORE >>
Well, just how can these local contacts be synchronized with the server-based mail file?
Posted by Perry Hiltz, Binary Tree Solutions Architect
My name is Perry Hiltz. I am a Solutions Architect with Binary Tree and I have over 16 years of experience with Lotus Notes and Domino, with quite a few of those years focused on migrating and consolidating Domino environments.
When I speak with customers and partners about Domino migrations to Exchange, I frequently get asked questions about how to migrate Lotus Notes users who have encrypted email.
While in most production environments, there is not a hoard of these objects, the Lotus Notes client does allow end users to encrypt messages very simply. For example, the act of sending an email in Lotus Notes makes this simple. Under the delivery options, a user can check the Encrypt option to encrypt single emails. However, this can be set via policies and on individual workstations on the Preferences area of the client. When a user opens the Mail/Sending and Receiving area of the Workstation Preferences, the user can turn on Encrypt saved copies of sent messages and Encrypt messages that I send.
In both of these cases, when a message is sent to a user, only the intended recipient can open it. This is a security feature of Lotus Notes and Domino that prevents an Administrator using an ID with elevated privileges or a Server ID from accessing messages with sensitive content.
With this in mind, the question then is how can we migrate emails from Domino that contain these levels of encryption?
READ MORE >>