Comments on: Download Microsoft Office 2003 SP3 – Install Office 2003 and Office 2007 on the same PC http://4sysops.com/archives/download-microsoft-office-2003-sp3-install-office-2003-and-office-2007-on-the-same-pc/ For Windows Administrators Fri, 19 Mar 2010 19:02:26 +0000 http://wordpress.org/?v=abc hourly 1 By: Richard Burkhart http://4sysops.com/archives/download-microsoft-office-2003-sp3-install-office-2003-and-office-2007-on-the-same-pc/comment-page-1/#comment-27178 Richard Burkhart Sun, 14 Oct 2007 05:18:23 +0000 http://4sysops.com/archives/download-microsoft-office-2003-sp3-install-office-2003-and-office-2007-on-the-same-pc/#comment-27178 I installed Office 2007 on my home computer and also my Toshiba laptop. Everytime I switch from 2007 to 2003 the computer takes a few minutes. It looks like it is reregistering or something like that. Is there a good solution for my installation? rburkhart2300@yahoo.com Computer Instructor/Microsoft office Suite I installed Office 2007 on my home computer and also my Toshiba laptop. Everytime I switch from 2007 to 2003 the computer takes a few minutes. It looks like it is reregistering or something like that. Is there a good solution for my installation?
rburkhart2300@yahoo.com

Computer Instructor/Microsoft office Suite

]]> By: Michael http://4sysops.com/archives/download-microsoft-office-2003-sp3-install-office-2003-and-office-2007-on-the-same-pc/comment-page-1/#comment-25134 Michael Tue, 25 Sep 2007 18:54:46 +0000 http://4sysops.com/archives/download-microsoft-office-2003-sp3-install-office-2003-and-office-2007-on-the-same-pc/#comment-25134 Jim, I can understand that you are annoyed about the problems Group Policy software deployment causes. But if you ask me, Group Policy was never really designed for such purpose. We’ve been experimenting with software deployment using Group Policy before, but it was too unreliable. We now use SMS which is much more reliable. However, I am still not a friend of software deployment, especially with big packages like Office. I prefer to create a new master image, test it thoroughly with a couple of users and then rollout the new OS with all the latest software installed. In my opinion, this is the most reliable way to deploy large software packages. We even reinstall the complete OS if a user PC has problems which can’t be fixed within a couple of minutes. Imaging is simply faster than trying to fix a messed up system. I think that more organizations will use this method in the future since Vista is perfectly prepared for this. Jim, I can understand that you are annoyed about the problems Group Policy software deployment causes. But if you ask me, Group Policy was never really designed for such purpose. We’ve been experimenting with software deployment using Group Policy before, but it was too unreliable. We now use SMS which is much more reliable. However, I am still not a friend of software deployment, especially with big packages like Office. I prefer to create a new master image, test it thoroughly with a couple of users and then rollout the new OS with all the latest software installed. In my opinion, this is the most reliable way to deploy large software packages. We even reinstall the complete OS if a user PC has problems which can’t be fixed within a couple of minutes. Imaging is simply faster than trying to fix a messed up system. I think that more organizations will use this method in the future since Vista is perfectly prepared for this.

]]> By: Jim http://4sysops.com/archives/download-microsoft-office-2003-sp3-install-office-2003-and-office-2007-on-the-same-pc/comment-page-1/#comment-24593 Jim Fri, 21 Sep 2007 14:08:51 +0000 http://4sysops.com/archives/download-microsoft-office-2003-sp3-install-office-2003-and-office-2007-on-the-same-pc/#comment-24593 Here I work at a community college where they needed to teach both versions of Office in many of my labs. Typically we've installed most of our software including Office via GPO's off of a Win2k3 server. Installing both Office 2003 and 2007 via GPO was nothing but a pain in the *ss. Of course MS had to remove the simplicity and deployment features that were already in Office previous to 2007 so that they could push their own deployment software at you for $$$. Anytime though that we tried to install via gpo probably 99% of the systems had OSE.EXE errors. After a few reboots the errors seemed to go away and the software installed. If the both Office packages were installed manually, it wasn't a problem but via gpo, it wasn't worth the trouble. It should have worked but wouldn't. It wasn't even a matter of it being the main apps like Word. If the lab needed Office 2007 enterprise plus Visio 2003 and Project 2003, we still saw these problems. I didn't even mention the reregistering that some of the Office 2007 apps do if you last ran a 2003 version of the same app. We've gotten alot of complaints about that one as it takes several minutes to reregister. In my opinion it was yet one more piece of unfinished software coming out of MS that they push on people. We wouldn't have installed it this early but since the students can't buy Office 2003 any longer for their home machines it creates havoc for everyone. Thanks again MS for your monopolistic practices. Maybe this service pack will help with some of this but I just might put the installations in the image next time. I prefer to keep my images clean but I might have to change my rules on that. Here I work at a community college where they needed to teach both versions of Office in many of my labs. Typically we’ve installed most of our software including Office via GPO’s off of a Win2k3 server. Installing both Office 2003 and 2007 via GPO was nothing but a pain in the *ss.

Of course MS had to remove the simplicity and deployment features that were already in Office previous to 2007 so that they could push their own deployment software at you for $$$. Anytime though that we tried to install via gpo probably 99% of the systems had OSE.EXE errors. After a few reboots the errors seemed to go away and the software installed.

If the both Office packages were installed manually, it wasn’t a problem but via gpo, it wasn’t worth the trouble. It should have worked but wouldn’t. It wasn’t even a matter of it being the main apps like Word. If the lab needed Office 2007 enterprise plus Visio 2003 and Project 2003, we still saw these problems.

I didn’t even mention the reregistering that some of the Office 2007 apps do if you last ran a 2003 version of the same app. We’ve gotten alot of complaints about that one as it takes several minutes to reregister. In my opinion it was yet one more piece of unfinished software coming out of MS that they push on people. We wouldn’t have installed it this early but since the students can’t buy Office 2003 any longer for their home machines it creates havoc for everyone. Thanks again MS for your monopolistic practices.

Maybe this service pack will help with some of this but I just might put the installations in the image next time. I prefer to keep my images clean but I might have to change my rules on that.

]]>