After completing 10 OfficeMate upgrade/installations I have come across a number of items that bear discussing as well as a few questions I have run into from others.
When installing OfficeMate v 10.5 on XP workstations, many times you will get a 2 file registration errors – clicking through these seems to still give a successful install.
After a successful server install, if you have installed the client on the server (which I highly recommend doing if not just for troubleshooting issues), and you cannot connect from a networked client workstation, more than likely it is a firewall issue on the server – disable the firewall on the server to see, and if you can then connect, turn the firewall back on and set the proper firewall rules for your SQL server.
Performance issues: In my experience, OfficeMate should have approx the same performance on a workstation as it did on version 8 even if it is below the minimum requirements. **Note: The performance of OfficeMate/ExamWriter v 10.5 may be severely impacted if you are not running a good enough server. Follow the recommended hardware requirements for the server and understand that those requirements are generally fine as long as you are using your server as only a database and or terminal server – this means you generally should NOT use this server as a Domain Controller, DSN or DHCP server etc as these roles can have a huge impact on OfficeMate performance when the server is under load. Also, if using OfficeMate add-on applications such as ECR vault, make sure that your server Exceeds the requirements. Generally I go for dual quad core Xeon processors, minimum 12 GB RAM, and minimum 3 high speed enterprise class hard drives in RAID 5 (Hardware RAID).
Accessing older access backups once you have converted to SQL server: I have had a few people ask my how they could open up a prior Access based backup once they had upgraded to versoin 10.5 with SQL – in short, the easiest way is to use a virtual machine and install OfficeMate 8 on the virtual machine (Windows 7 Pro has the ability to run a virtual version of XP natively - http://www.microsoft.com/windows/virtual-pc/ )
Windows 7 issues – I have run into a few scenarios where the proper Omate32.ini file was not put properly into the user profile. You should have this file in users/%username%/My Documents/Windows/ – if you are getting database errors on startup and are sure your firewall issues with the server have been resolved, check for this file and make sure it is there. (I always keep a working copy of this file on a server share for ease of copying).
Backups: If you are unfamiliar with how to do a SQL dump backup see this article : http://www.codeproject.com/Articles/113461/Schedule-a-daily-backup-with-SQL-Server-Express . You can also use backup services such as IBackup with the MS SQL Server backup plugin which automate the SQL database backup nicely.
* Pensacola Computers is not officially connected to OfficeMate software in any way, and all opinions stated are my own observations and you may experience different results. This guide is meant only as a narrative of my own experiences and is current as of the date posted.
I have been working as an IT consultant with Optometrists that use OfficeMate for over 6 years and have installed OfficeMate numerous times for 9 different practices. I have successfully done 10 upgrades in the past few months and assisted on a few others. Please feel free to contact me via my contact info at http://pensacolacomputers.com with any questions.
After completing 8 upgrades of OfficeMate 8 to OfficeMate version 10.5 ( 10.5.23 is the lastest as I write this), a few observations from my own experiences and from things I have gleaned through conversations with others who have done the upgrade:
Firewalls are not really mentioned in the installation guide, but they can definitely cause issues, especially trying to get clients to connect to the server – if you have an issue with the clients not successfully working, and you can see the files on your network share, it is most likely a firewall issue. Open task manager, look for Login.exe and if you find it running, kill that process and then turn off the firewall on your server. If it work after that you will need to go to your server and configure the firewall for the ports that your SQL installation is using.
If you are upgrading from the Access based version of OfficeMate, make sure you have a backup solution that will properly backup your SQL database file (normal file backup programs do not work properly for SQL databases). You will need either a backup program that has a SQL database backup component, such as iDrive, or you can script a backup through the SQL management console then create a scheduled task to back it up. (There are plenty of guides out there on how to do this).
Make sure that you download the latest installation files from OfficeMate IMMEDIATELY prior to installation. There is no easy way to tell the actual version of the file you download (OfficeMate doesn’t properly sign their installation files nor do they include the actual version of the OfficeMate installation in the install executable), so if you download it days or weeks prior to installation you might not have the most current version.
As I have experiened a few issues in the Server installations and database conversions, I highly suggest that you have a full bare metal backup/image of you server that you can use to roll everything back in case an installation goes bad. Even though it is time consuming to make a full backup on some servers, it is well worth the effort for peace of mind if anything.
If you have any questions or issues, feel free to contact us via our contact information at http://pensacolacomputers.com
* Pensacola Computers is not officially connected to OfficeMate software in any way, and all opinions stated are my own observations and you may experience different results. This guide is meant only as a narrative of my own experiences and is current as of the date posted.
I have been working as an IT consultant with Optometrists that use OfficeMate for over 5 years and have installed OfficeMate numerous times for 7 different practices. I have successfully done 7 upgrades in the past few months and assisted on a few others. Please feel free to contact me with any questions.
Continuing with my posts on OfficeMate installations, I will go over some things I learned doing the actual installations. **Note: Make sure to follow the official OfficeMate guide, though be aware that the official guide has a few mistakes and is misleading in a few places as well. This guide takes in account that you have followed and met the needed pre-reqs for installing OfficeMate such as security setup and hardware/software requirements.
Once you have installed the server (see Pre-regs and Server install) it is time to install the client software. There are a few things I have learned that are not covered in the official installation guide that have helped me through. I had a heck of a time on one of my first installs trying to upgrade the client software, and I found that when upgrading from OfficeMate version 8 to version 10 on client machines that it is often best to first Uninstall the previous version of OfficeMate, then freshly install version 10 (this is not necessary on the server if you are using it as a workstation or remote terminal server, all of my client upgrades worked fine on the servers).
Before installing version 10.5, first make sure you are using the latest version available (10.5.23 at the time of this writing – previous versions had a bad bug relating to insurance claim filing I am told). Also ensure that your workstations have at least Windows Installer version 4.5 or above – Windows 7/Server 2008R2 have version 5 installed by default which is fine. You also need to ensure that .Net Framework 3.5 SP1 is installed on each system. For XP, and Vista, check in your add remove programs, for Windows 7, check in Programs and Features > Turn Windows features on or off (it is part of Windows 7, but the feature might need to be activated).
Once you have the client pre-reqs installed, it is time to get ready to install OfficeMate 10.5 client – this will be the OM_Suite_Programs.exe file (unfortunately OfficeMate again did not properly make their install program and there is no real way to tell the version of the program from the installation file – checking the file details just shows a product name of InstallShield version 12 – fyi, this is a HUGE security issue as there is no way to tell if the file is legitimate prior to installing as it is not properly named, nor does it have a valid digital signature – complain to OfficeMate about this!). Prior to starting the installation, you will want to make sure that you have properly mapped your shared network drive for the OfficeMate Data folder as this will be needed during the installation. Before installing, also ensure that you have turned off your Antivirus and any screensavers. Although not required, I always right click on the installation file, and if there is an Unblock button I click that, I then right click on the install file again and select run as Administrator.
Once all of these things are done, follow the instructions in the official Upgrading to OfficeMate 10 pdf guide to start your installation.
The installation is pretty straight forward so I will just cover a few of the differences and issues I have run into during various (though not always all) installations.
Once OfficeMate 10.5 client is installed, you need to make sure it works! If you click on the OfficeMate link and nothing happens, go to your taskmanager and look for Login.exe (not omate.exe) – if that is running, but nothing is happening, then you need to first check your networked drive. If you can see all of the files in your network drive, but OfficeMate will not open, then you probably have a firewall issue on your server. Even though you can see the shared files on your server’s shared drive, the server firewall could be blocking the SQL ports which causes this problem. If this is the case, go to your server and turn off your firewall there, then recheck to see if you OfficeMate client will start (it probably will now). If this is the cause, you just need to check your SQL ports on the server and add a firewall rule for them, then turn your firewall back on and check again.
The client installations are fairly easy to accomplish once you have gotten everything set up properly such as the pre-reqs, mapped drives etc. I highly recommend downloading a copy of Windows Installer 4.5 and .Net Framework 3.5 SP1 to a shared folder on your server if you are doing many XP, Vista installations to save time. Also it is a good idea to follow a checklist for each workstation as you are installing so you don’t forget anything.
While the OfficeMate software definitely could use some tweaks to bring it up to standards, especially in the compilation of the installation files and having install file security digital signatures and proper names etc, the actual installation of version 10.5 seems to be a bit better than earlier updates and upgrades.
If you have any questions or issues, feel free to contact us via our contact information at http://pensacolacomputers.com
* Pensacola Computers is not officially connected to OfficeMate software in any way, and all opinions stated are my own observations and you may experience different results. This guide is meant only as a narrative of my own experiences and is current as of the date posted.
I have been working as an IT consultant with Optometrists that use OfficeMate for over 5 years and have installed OfficeMate numerous times for 7 different practices. I have successfully upgraded 4 practices in the past couple of months to OfficeMate 10.5 and am currently working on getting 4 more done in the coming weeks. Please feel free to contact me with any questions.

Categories
Tag Cloud
Blog RSS
Comments RSS
Last 50 Posts
Back
Back
Void « Default
Life
Earth
Wind
Water
Fire
Light 