Re: User Rights at Client Seem to Vary
From: TonyM (tonym_at_southernwoodwork.com)
Date: 03/22/05
- Next message: Patrick Dickey: "Re: sharing out folders on their computers <-- Must Stop -->"
- Previous message: Paul Bergson: "Re: Active Directory and Firewalls"
- In reply to: Herb Martin: "Re: User Rights at Client Seem to Vary"
- Next in thread: Herb Martin: "Re: User Rights at Client Seem to Vary"
- Reply: Herb Martin: "Re: User Rights at Client Seem to Vary"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 22 Mar 2005 16:04:48 -0500
Herb thanks for the educating reply!
Herb Martin wrote:
> "TonyM" <tonym@southernwoodwork.com> wrote in message
> news:##OhfixLFHA.576@TK2MSFTNGP15.phx.gbl...
>
> BTW, as a Novell Admin, do yourself a favor and
> make a POINT of distinguishing between "Rights"
> and "Permissions" in Windows.
>
You are correct, I am struggling a little bit with some of the terminology.
>>domain. 3 of these stations log on to both servers without a hitch. All
>>software works correctly and the users have access to both servers
>>logging on with their domain profiles. The other 2 stations is where I
>>am having problems. When the user logs on, using the domain profile, I
>>get pop-ups requesting the MS Office install CD-ROM.
>
>
> This is usually caused by an attempt (by the user or even
> through an update from Office Update) to update or add new
> features to Office.
>
> Once in this state, you pretty much have to let Office see the
> original CDRom or installation point to get it to stop (there
> may be other ways, ask in an Office group but this is what I
> know about such problems.)
I have inserted the CD and thats when I get the error message below and
the install stops.
>
>
>>When I put the CD
>>in the drive I get errors saying that the user does not have rights to
>>modify the WIN.INI file. Nothing in the MS Office works, I get a lot of
>>"Please reinstall" errors.
>
>
> The Win.Ini file shouldn't even matter for modern Office
> so I wonder if this is not something from an old version
> or due to the Novell client (which has been known to cause
> pretty strange problems).
>
This is what confused me. It is an old version of Office (2000 I
believe). Yes, I know that MS and Novell don't play well together at times.
>
>>Also the accounting package appears to start
>>when you click the icon but doesn't come up. It just runs as a service.
>
>
> "Service" is a specific term, but I suspect you mean
> "runs without displaying a GUI" which is an ENTIRELY
> different result.
>
Yes, incorrect terminology again. The program runs without displaying a
GUI. I then have to use task manager to end the process.
>
>>If I log on to the station with the user's local profile all works
>>correctly with no problems. If I log on to the station with my profile
>>(local or domain) everything works correctly.
>
>
> How about updating Office then? Both from the CDRom and
> perhaps from the Office Update site to get everything straight?
All MS Office products and Win2000 have been updated to the latest
patches and security updates.
As I stated above, the system will not allow the user to update the
program from the CD-ROM when logged on under the Domain Profile. When
logged on under the local profile no problems.
>
>>One of the problem users has full Admin rights (he is the owner) and the
>>other user is a Power User. Both users are in the Domain Users group on
>>the server. The other 3 users are Power Users in the Domain Users Group
>
>
> Probably doesn't matter -- it is likely something in
> their user profile that is marked to update office.
> Perhaps they tried to "add a feature" to office.
Good point. I will look into this
>
>
>>All 5 workstations were set up the same way. I basically logged on as
>>the local user to create a new domain profile on the workstation then,
>>as Admin, I copied the local profile to the Domain profile through the
>>User Profiles in the System Properties dialog box.
>
>
> I have never used nor liked that method. Preferring to
> do it directly.
>
Thats a good idea. I will try recreating the profiles without copying them.
> Perhaps the permissions were mangled on the profile
> location -- either the Share (usually should be Full Control)
> or the File (NTFS permissions.)
>
>
>>I'm sure I missing something in the rights category but since all 5 were
>>done the same way I'm stumped. Any help would be greatly appreciated.
>
>
> Go check the permissions (not rights) on both the Share
> and the NTFS files.
I will check this also.
Again, thanks Herb. This is the kind of information I need to keep my
hair intact.
- Next message: Patrick Dickey: "Re: sharing out folders on their computers <-- Must Stop -->"
- Previous message: Paul Bergson: "Re: Active Directory and Firewalls"
- In reply to: Herb Martin: "Re: User Rights at Client Seem to Vary"
- Next in thread: Herb Martin: "Re: User Rights at Client Seem to Vary"
- Reply: Herb Martin: "Re: User Rights at Client Seem to Vary"
- Messages sorted by: [ date ] [ thread ]