| View previous topic :: View next topic |
| Author |
Message |
dali
General User
Joined: 26 Mar 2003
Posts: 7
|
 Posted: Tue Jul 22, 2003 1:28 pm Post subject: |
 |
|
Sounds great! Hopefully it isn't a fluke, that would mean that the developers have put some effort into V1.1 to make these things easier. 
However, just copying the shortcuts doesn't work in 1.0.x ...  |
|
| Back to top |
|
 |
Marcp
Guest
|
| Posted: Tue Aug 05, 2003 4:13 am Post subject: w2k domain user |
|
|
| Come on guys, who gets OpenOffice to run without using an account with atleast Power-user rights? And no, i do not want to use the "Run as different user" option. |
|
| Back to top |
|
|
Rockford
General User
Joined: 29 Jul 2003
Posts: 8
|
| Posted: Wed Aug 06, 2003 2:10 am Post subject: |
|
|
Hi #?, *.*, all 
Hi dave,
the solution you explained is not working in a Multiuser-Envirement were all others have different access right. If every user has admin rights then your "solution" is indeed working. Unfortunaltly I canŽt give every user admin rights here at work (I am not crazy ) .
To the topic starter: Great, I think your script can perhaps be usefull for me. I was working on something similar using "kixstart" (scripting language for Windows). Its to time consuming to install Open Office on every computer "by hand" so I was scripting a remote solution but: Not yet working.
Greetings...
Rockford |
|
| Back to top |
|
|
Svenna
General User
Joined: 31 Mar 2003
Posts: 9
Location: Oslo, Norway
|
| Posted: Wed Aug 06, 2003 3:35 am Post subject: |
|
|
Vel, I'm sorry to say.. but this method is working... 
But you have to follow it closelly, and if you understand it, you also see that alle the access problems are taken care of, so this post is not ment as an argument in an intereseting discution (It works, NO it does not, YES IT DOEAS, HEY I'm TELLING YOU IT DOES NOT!!!!)
but its ment to tell new readers that they should try it, it can work for your, so it is posible. I've used it on v 1.0 - 1.01 - 1.02 - 1.03 and in small scale testing on 1.1 beta.
_________________
Sven Tore Iversen
mailme@sventore.com
http://www.sventore.com |
|
| Back to top |
|
|
Rockford
General User
Joined: 29 Jul 2003
Posts: 8
|
| Posted: Wed Aug 06, 2003 4:16 am Post subject: to Svenna ;-) |
|
|
Hi all!
Hi Svenna
I believe you, that your solution works. I think IŽll try that out in a modified way. I was working on simliar solution for some time now, but I need more "dirty trix" in my solution (not ready yet) cause we have for example some software that is searching for "winword.exe" so that I need some registry changes as well.
The "works only if all users are admins" was meant to Dave above in the treat who is using WinXP.
So, thanx for the description of your solution.
Greetings...
Rockford |
|
| Back to top |
|
|
orac
General User
Joined: 06 Aug 2003
Posts: 8
|
| Posted: Wed Aug 06, 2003 2:15 pm Post subject: File Associations (and Multiple Windows Profiles) |
|
|
Hello list.
I am trialing OO 1.1RC for deployment in a large organisation.
It is not practical for each user to run a workstation install.
So I have followed Kixstarts suggestion of setting OO up for a master-user and copying it's profile to the default users profile.
This seems to work in all things except the file associations are not preserved for new users. ie. A new user logs in and creates a new profile based on the default users profile, but the file associations for .xls, .ppt and .doc that worked for the master user profile seem to no longer exist.
Any ides on why this may be and how to resolve this.
NB. My users do not have rights to manually create their own file associations. |
|
| Back to top |
|
|
mawrya
Guest
|
| Posted: Thu Aug 07, 2003 2:17 pm Post subject: solution |
|
|
Okay,
Here's what I do tp get multi-user mode working in windows, might work for linux too.
1. Install openoffice as machine admin. Don't even bother using the -net when you install.
2. After installing, run the program and go through the first-time-startup wizard stuff.
3. Now go into the windows profile directory for your admin account (the account you are logged in with) and go into the Application Data folder - you will see a file named sversion.ini
4. Move sversion.ini to a central place like c:\program files\openoffice\sversion.ini
5. Open up up the openoffice bootstrap.ini file and edit it to point to the new location of the sversion.ini file.
6. Now openoffice works for all users!
7. Copy the shortcuts to the open office folder to a place where all users can get at them, into the start menu of the all-users profile as described by someone in a previous post.
8. Now just tell windows to open all files of type .xls, .swx, etc with the openoffice program.
Voila! |
|
| Back to top |
|
|
pserko
Newbie
Joined: 11 Aug 2003
Posts: 1
|
| Posted: Mon Aug 11, 2003 9:14 pm Post subject: 1.1 multiuser triggers error reporting |
|
|
It appears that changes have been made in 1.1 so that your method works however, I found that when I test with other users after closing writer it triggers an error report dialog. Anyone have any ideas for dealing with this? Easy multiuser functionality is getting closer!
The method I use to get 1.0.3.1 to work in Win2K:
Install OO on small FAT parttion.
Copy sversion and the usbr..( I can't remember the exact name now) to the root of the C drive.
Batch file in startup that copies the two files to user application data folder when user logs on.
Change save path to a mapped Z drive for each user.
I am testing in High School Library on 5 machines this Fall. Hope that 1.1 changes coninue to simplify things. |
|
| Back to top |
|
|
swbrown
Guest
|
| Posted: Wed Aug 13, 2003 6:02 pm Post subject: This is terrible. |
|
|
| This is probably the worst usability issue with OpenOffice. Is a family of three going to go through all this crap in order to make it work with each of their logins? Why can't it just add itself to all user menus, detect when run that the user isn't configured yet, and run setup? Is it just a matter of needing someone to write the code, or is there some bigger problem? |
|
| Back to top |
|
|
xj220
General User
Joined: 18 Aug 2003
Posts: 5
|
| Posted: Mon Aug 18, 2003 12:04 pm Post subject: |
|
|
I have got the multiuser install to work (kind of ) but i have one enojying thing left  (The registration dialog pops up everytime a new user loggs on. (It dosen't matter if the user have used OO on this computer before and checked I never whant to register etc..)
Does anyone know how to solve this ? |
|
| Back to top |
|
|
xj220
General User
Joined: 18 Aug 2003
Posts: 5
|
| Posted: Tue Aug 19, 2003 12:54 am Post subject: |
|
|
| The problem is solved i change the part about registing in common.xcs. |
|
| Back to top |
|
|
orac
General User
Joined: 06 Aug 2003
Posts: 8
|
| Posted: Fri Aug 22, 2003 2:24 pm Post subject: re: PSERKO |
|
|
"...after closing writer it triggers an error report dialog."
I stopped recieving this when I gave users full permissions to c:\program files\open office 1.1\... |
|
| Back to top |
|
|
Guest
|
| Posted: Wed Sep 10, 2003 9:19 am Post subject: |
|
|
| dali wrote: | First of all, I'd like to point out that the instruction isn't a step-by-step instruction all the way; some parts are intentionally left out so that they can be adapted/changed/implemented by you. The intended audience is a fairly knowledgeable Windows adminstrator that can use this as a reference to make an adapted installation for his/her own environment.
The information in it should be sufficient for a skilled administrator. However, I may have overlooked some things. Corrections, comments and suggestions are appreciated.
In short, the instruction is divided into two parts: the "network" installation and the workstation installation. The term "network" installation is used because that is what it's called in the StarOffice/OpenOffice.org documentation. The same goes for "workstation".
The first part, the "network" installation, is done once on all client computers. The code in the example is put in a batch file, we could call it netinst.bat. To successfully run it you have to have adminstrative rights (or SYSTEM rights). In a large organisation, netinst.bat is probably executed unattended, either during the (automated) installation of the client operating system or by using some kind of software distribution system (e.g. Microsoft SMS, OnCommand CCM). The installation files and scripts are probably on a network share, but they could just as well be on a CD-R/W.
In a small organisation, netinst.bat might be started manually (from a network share or a CD-R/W) by a logged on administrator.
The second part, the "workstation" installation, is executed by every user. The code could be included in a logon script, or it could be done by instructing the users to run a batch file (containing the installation code).
My installation example is based on users moving around (using different computers), having roaming profiles and storing their personal files on a network server (their home directory). Since OOo stores the user's personal files in at least two different locations - in the user's profile and in the "workstation" installation directory - you may have to adapt the installation to accomodate for your environment.
Hope this clarifies things. I've updated the instruction with some of the info in this post. |
|
|
| Back to top |
|
|
redndahead
General User
Joined: 03 Feb 2003
Posts: 47
|
| Posted: Sat Sep 20, 2003 11:02 pm Post subject: |
|
|
Hello everyone. I am sure this thread is getting old...but there is light at the end of the tunnel allbeit a very very long tunnel. =) Here is an excerpt from the OOo 2.0 product concept page.
| Quote: | The installation paradigm changes from being primarily single user oriented to being administrator oriented. It is looking for large scale installations and administrations. This issue will be addressed by conforming the installation process to the respective systems installer services, since these services already provide or enable an existing installation tooling.
The "Geordi" user-installation as a required step of a network-installation will cease to exist. The office applications will be fully functional from the first start. Gathering user specific data will be postponed to the first application start or queried directly from the system. Document and setting defaults will be generated on the fly during the first start or on demand.
The repair mode of the setup will be dropped. Repairing the installed files is already handled by the native package mechanism (usually by a reinstall). This does not affect user driven changes since user and system files are strictly separated.
Upgrading and patching will be performed by means of the respective system installer.
|
Finally I think they have plans to do it right. So patience is needed and show your gratitude when it comes out because this is a huge feature. By the way "Geordi" is OOo 1.x
The roadmap shows 2.0 Beta coming out in Q3 of 2004. So only a year left to get our hands on this good stuff...=)
red |
|
| Back to top |
|
|
TechFan
Guest
|
| Posted: Sun Sep 21, 2003 10:47 pm Post subject: Yeah! |
|
|
| I will be looking forward to this new installation approach!!! |
|
| Back to top |
|
|
|
