Re: Office 2003 Setup

From: Popeye (Popeye_at_discussions.microsoft.com)
Date: 01/18/05


Date: Tue, 18 Jan 2005 14:01:01 -0800

Hi

Thank you for both responses. I wasn't sure where to post this question in
the first place! The suggestion that you've made is logical and I'll get on
to it. I'm sure that I could use it for other programs, such as WinZip, to
determine which users can use them.

"Leythos" wrote:

> In article <537B515B-6C02-483E-AE4C-103837F0713D@microsoft.com>,
> Popeye@discussions.microsoft.com says...
> > Hello everyone
> >
> > I have XP Pro SP2 and have several accounts set up on my computer. There is
> > a mixture of Admin and Limited rights in additional to the pre-determined
> > Administrator and Guest accounts. How do I set it up to determine exactly
> > which users can have access to specific applications within Office?
> > For instance, I might want:
> >
> > User1 (Admin) to have access to Outlook and Word
> > User2 (Limited) to have access to Word and Excel
> > User3 (Limited) to have access to Excel and Outlook and
> > Guest (pre-determined Guest) to have access to Outlook
> >
> > I've tried installing as Administrator but can't use *anything* if logged on
> > as Guest or a user who doesn't have Admin rights. It stalls and says that
> > there's a problem with the Office Source Engine and to reinstall or repair.
> > I've done this but still can't access anything which does not have Admin
> > rights.
> >
> > Thanks in anticipation of a simple solution!
>
> Ha!
>
> If it were that simple it would be nice - With Office products that user
> must be a local administrator in order to use them the first time,
> sometimes after the initialization you can switch them to Users, but
> it's more hassle than it's worth - almost all systems that provide MS
> Office 2000/XP/2003 require that the users be Administrator level (like
> QuickBooks does) and even PowerUser don't provide enough access to allow
> everything to run.
>
> With that aside - you need to create local groups (assuming you're not
> in a domain) and then apply permission to the Executable files based on
> group membership - this means that you create a group called
> MS_Outlook_Users, MS_Word_Users.... Now, add in the people you want to
> being those groups, now right click on Outlook.exe and select
> Properties, then Security, then change the permissions so that EVERYONE
> is removed, and add in the GROUP you want to have access to it - make
> sure that you add in the Administrators group.... Do the same with the
> others.
>
> --
> --
> spamfree999@rrohio.com
> (Remove 999 to reply to me)
>



Relevant Pages

  • Re: Admin rights for winXP install?
    ... By default the first user account created during setup gets Administrator ... permission. ... to take admin rights away from everyone in the office, ...
    (microsoft.public.windowsxp.general)
  • Re: 837272 & 839643 Updates wont install on W2K SP4 domain PCs - Permission Error
    ... > 3.455: Failed To Enable SE_BACKUP_PRIVILEGE> 3.565: Setup encountered an error: You do not have> permission to update Windows 2000. ... > Please contact your system administrator. ...
    (microsoft.public.windowsupdate)
  • Re: Programs that need admin rights, but user shouldnt have them
    ... Some GPO settings stick and some don't. ... >> Administrator on the computer (e.g. some of the Windows XP Firewall ... >> indicates whether a local administrator can override the setting or not. ... >>>the user to have local machine and domain local admin rights. ...
    (microsoft.public.win2000.group_policy)
  • Re: XP Accessibility feature saving profile
    ... >> think you should have the System Administrator, ... >>> the network storage they provide or my thumbdrive and restore it for my ... I have WRITTEN permission + if they refused to ... >>>> multi-user environments to protect setups from exactly the kind of ...
    (microsoft.public.windowsxp.accessibility)
  • Re: Administrator account has "SEND AS" right on every Mailbox
    ... We all know Administrator can change any permission in AD. ... > dutch SBS 2003 servers. ... >> probably by Exchange Installation. ...
    (microsoft.public.exchange.admin)