Filtered by: Synchronization
Transaction consistency when using single-threaded nature of IDM to 'fan-out' to multiple end-points
Ensuring that a 'fan out' Connector will keep transaction consistency if the end-system is unavailable. This only applies to custom built fan-out solutions which utilize one of the shipping point-to-point IDM Connectors.
In this Cool Solution series we will see how we can set up the workorder driver together with a loopback driver to activate and deactivate user accounts based on the starting date and end date of the user account.
In part 1 we will go through the basic add event of a new user.
Wednesday, February 24, 2010 - Migrating from NetWare to Windows Server but still want to keep GroupWise? Running Windows for authentication, file and print services and GroupWise for collaboration? Riva Identity Integration from Omni now allows you to synchronize and manage eDir/GW and Active Directory accounts - with no complex designer tools, connectors or scripting languages. Sign up for the upcoming presentation here.
After doing a pre-migration of a Volume from NetWare 6.5 SP7 to SLES10-SP2 w/ OES2-SP1 all of the file structures appeared to be correct. We did this "Pre-migration" in order to copy the bulk of our user files prior to doing a final sync and pointing to the new volume on the new server. But after the sync, we found that some of the source files and the destination files had the EXACT same size, creation date, and modified date, but the content was different. Here is how it went down.
Submitted by: mbruner1 on Thu. 01.28.2010
Filed Under: Collaboration Cool Solutions, Cool Solutions
Topic: File Management, File Transfer, Folders, Migration, Synchronization, Tips for Administrators
Product: Linux, NetWare, Open Enterprise Server, SUSE Linux Enterprise 10, SUSE Linux Enterprise Server
Ever find that some of your AD user synchronization doesn't? Then you investigate and find that it's the data in eDirectory not being acceptable to the schema in AD. Well this policy is designed to help alleviate some of that, without having to hand code policies for each attribute in the schema.