| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: Suggestions / Feedback
Thread: Install/operation gripes: running as Administrator, etc. |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 6
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I just installed the client. Here are some problems I had at the start:
1) For security reasons, I don't normally run my machine as Administrator. So I started by trying to install the software as a normal user. It failed (though it gave a helpful error mesage about what files it couldn't write). It might be nice to tell users that we need to install as Administrator. 2) Apparently the machine needs to be restarted after installation. It would be nice if the installation software told me and/or asked me if I wanted to restart. 3) When I installed the software as Administrator, it made a shortcut in the Administrator's Startup folder. Because I don't normally run as Administrator, I moved the shortcut to my normal user's Startup folder. That didn't work (permissions issue?), so I made a new shortcut there to the UD.EXE file and double-clicked on it. That started the client. It would be nice if the installer asked which user should get the client in their startup folder instead of assuming we always log in as Administrator. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Regarding #3,
----------------------------------------Instead of using the Administrator or normal user Startup Folder, put the shortcut in the All Users startup folder. That way, no matter who logs in, it will automatically start and run. Correct location is "C:\Documents and Settings\All Users\Start Menu\Programs\Startup" [Edit 1 times, last edit by Former Member at Nov 17, 2004 6:53:47 PM] |
||
|
|
Alther
Former World Community Grid Tech United States of America Joined: Sep 30, 2004 Post Count: 414 Status: Offline Project Badges: 
|
1) For security reasons, I don't normally run my machine as Administrator. So I started by trying to install the software as a normal user. It failed (though it gave a helpful error mesage about what files it couldn't write). It might be nice to tell users that we need to install as Administrator. We'll look into why this is necessary and change this requirement if possible. If not, we will add it to our FAQ. 2) Apparently the machine needs to be restarted after installation. It would be nice if the installation software told me and/or asked me if I wanted to restart. You should not have to restart the computer in order to use the agent after installation. Why do you think you had to restart? 3) When I installed the software as Administrator, it made a shortcut in the Administrator's Startup folder. Because I don't normally run as Administrator, I moved the shortcut to my normal user's Startup folder. That didn't work (permissions issue?), so I made a new shortcut there to the UD.EXE file and double-clicked on it. That started the client. It would be nice if the installer asked which user should get the client in their startup folder instead of assuming we always log in as Administrator. The install will add the shortcut to the current user's Startup folder. We're also not likely to change the installation to ask which user's Startup folder to add the shortcut to. Finally, it's probably not the best idea to add the shortcut to the All Users folder in general for several reasons. Let's say that the computer has 4 user accounts on it (XP - 1 for each family member). Maybe each family member wants their own account and points when they run the agent. If it was installed in the All User's startup folder, it would only start under the account of the last person to install the agent. You also have a semi-privacy concern that someone else can find out your account member name that also uses the computer. If you know what you're doing then moving the shortcut to the All User's startup folder is not a big deal and you do it once. However, I don't think it's a good idea in general. - Rick Alther
Rick Alther
Former World Community Grid Developer |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Re #1: The first file it tried to write and complained about was c:\windows\ud.scr. (My \windows folder isn't writable by normal users. I'm using XP Professional.) There was another file after that too -- a DLL, I think.
Re #2: I can't remember exactly why it seemed to need a restart, sorry. Restarting the system did solve the problem, though... Re #3: If the software can be installed as non-Administrators, then I'd suggest adding that to the FAQ too -- and/or a mention of the startup folder problem. (The software will only run when you log in as the user who installed it -- unless you install as Administrator and make a shortcut in that user's Startup folder.) Thanks. |
||
|
|
Peter2000
Cruncher Joined: Nov 20, 2004 Post Count: 1 Status: Offline Project Badges: 
|
Hi,
I too am following established safe computing practices. I only connect to the internet using a restricted user account. By definition, a restricted user account will not be able to install new programs on the computer. To install the grid program I think the procedure is: 1) Download the installer from the restricted user account. 2) Log on as administrator 3) Install the program 4) Close the registration window. 5) Assign Full Control permissions to the WorldCommunityGrid directory to the restricted account 6) Copy the shortcut to the Startup directory for All Users ( To Do for me!) 7) Logon as the restricted user and complete registration I think the Grid program should behave in a similar way to the Microsoft Office XP installation whcih prompts the user for an administrator password if it is run from a restricted account. Then it could complete the above automatically. Regards Peter |
||
|
|
João G. da Costa N. Carrapa
Cruncher Joined: Jul 11, 2005 Post Count: 2 Status: Offline |
I've tried to do that, but nothing worked. Maybe There's another file or directory I should put full control access on?...
|
||
|
|
|