I'm a bit concerned about all the new user interfaces and layouts that will appear when application developers starts taking use of the Windows® Presentation Foundation (formerly code named "Avalon"). This "tecnology" is awesome but it has it's drawbacks. With the WPF you can create applications that are really neat looking and have high usability, just take a look at Microsoft Expression Interactive Designer. I saw a really nice demo, on a Microsoft Partner event, of a medical journal application looking like a "medical journal" - not the old fashioned MDI interface with a File, Edit... menu. And I guess most of you have seen the Microsoft Max application and the new Office 2007 interface. But what will happen to the usability between applications? As of today almost all Windows applications has a user interface with a menu bar with the File, Edit etc menus, a toolbar with icons and either one document (SDI) or multiple documents (MDI) in the window area. This is very good when adapting to new applications, you know where to find the functionality you want, not in all cases but the most vital functions are easily found. You know how to save a document or to paste something in to your application. Windows Presentation Foundation does not prohibit this usage but it allows developers to create really cool looking applications with a nice user interface. But when it comes to recognizing functions and behaviours I think this will cause a lot of trouble. Let's take an example of a hospital, where I have seen similar troubles, having several applications from several vendors; they have Microsoft Office 2007, some kind of medical journal system, a financial report system, an intranet etc. Most of the employees use more than one application. It will be very problematic if these applications doesn't share the same user interface guidelines. This is the point of my entry! Where is the guidelines for these new awesome user interfaces? Do you have the same opinion or experience as I do?Where can I find information on how to make these new applications run smoothly togheter using common guidelines?
Today I had to move (make an exact copy of) an ADAM (Active Directory In Application Mode) installation to a new server. It was not that trivial and therefore I thought I would share on how to do it.
- Add the BUILTIN\Administrators group to the Administrators Role in the Adam instanceThis group has a well known SID and therefore can be moved to any server. Se picture below.
- Make a backup of the Adam data files folder, using Microsoft BackupThe files can not just be copied because they are locked
- Create the exactly same installation on the new serverUse the same ports, service name, application directory partition etc
- Stop the newly created serviceSo the files won't be locked
- Restore from the backup you created in 2)Make sure that you specify to overwrite all files, which is not by default
- Start the service and test it
Adding the BUILTIN\Administrators group to the Administrators Role in Adam
This worked for me and if you have problems or other tips, please contact me.
Update 9/3-06: Note that you have to reset the passwords on all users!