Active Directory - Office Concerns

[Nightwolf]

I recently changed my iBook G4 over to a Windows active directory
domain, of which I am an administrator of. I then made myself an admin
on the laptop. When I logged in to my laptop, everything seemed to
work, but when I tried to run Word, it comes up saying "There is not
enough memory or Disk space to run Word." When I try to run Excel,
nothing even loads up. When I try to run Powerpoint, I get an error
saying "Powerpoint cannot launch, Please try turning on Virtual Memory
from the Virtual Control Panel or quitting other applications". I am
using OS X 10.4 and Office v.X. When I log on as the local admin user,
all programs work fine. I am thinking there is a permissions/security
issue somewhere, and that the program is trying to write to someplace I
have no permissions to, but where I don't know. Can anyone help?

 

[William Smith]

I recently changed my iBook G4 over to a Windows active directory
domain, of which I am an administrator of. I then made myself an admin
on the laptop. When I logged in to my laptop, everything seemed to
work, but when I tried to run Word, it comes up saying "There is not
enough memory or Disk space to run Word." When I try to run Excel,
nothing even loads up. When I try to run Powerpoint, I get an error
saying "Powerpoint cannot launch, Please try turning on Virtual Memory
from the Virtual Control Panel or quitting other applications". I am
using OS X 10.4 and Office v.X. When I log on as the local admin user,
all programs work fine. I am thinking there is a permissions/security
issue somewhere, and that the program is trying to write to someplace I
have no permissions to, but where I don't know. Can anyone help?

With any permissions issue you can run the Disk Utility found in
/Applications/Utilities as a first course of action.

During your transition to AD, did you migrate any of your personal files
and identity to the new home folder or is Office X simply not working
from the very beginning just after binding to AD?

Rather than making yourself an admin on your laptop, I'd suggest leaving
your "daily use" account a normal account. If you need to install
software or something similar, you'll be prompted for an admin's
credentials.

bill

 

[Nightwolf]

With any permissions issue you can run the Disk Utility found in
/Applications/Utilities as a first course of action.

During your transition to AD, did you migrate any of your personal files
and identity to the new home folder or is Office X simply not working
from the very beginning just after binding to AD?

Rather than making yourself an admin on your laptop, I'd suggest leaving
your "daily use" account a normal account. If you need to install
software or something similar, you'll be prompted for an admin's
credentials.

bill

Didn't have to migrate any personal files or folders over as I was already
going the round about way of getting to them on the windows server. It just
seems that after binding to AD the Office X wouldn't work with the network
login Identification, though when I log back in as the local admin, not on
the AD domain, it works fine. When going in and looking at the information,
at first I was only read only on all the files. I did try to make myself
read and write access on as many files as I could, but still nothing would
bring up the suite properly.

 

[William Smith]

Didn't have to migrate any personal files or folders over as I was already
going the round about way of getting to them on the windows server. It just
seems that after binding to AD the Office X wouldn't work with the network
login Identification, though when I log back in as the local admin, not on
the AD domain, it works fine. When going in and looking at the information,
at first I was only read only on all the files. I did try to make myself
read and write access on as many files as I could, but still nothing would
bring up the suite properly.

Where are you keeping your home folder (on the local computer or a
network server) and where is the Office X folder (on the local computer
or a network server)?

Do you think your problem is a matter of accessing your Office identity
or launching the Office applications?

bill

 

[Nightwolf]

Where are you keeping your home folder (on the local computer or a
network server) and where is the Office X folder (on the local computer
or a network server)?

Do you think your problem is a matter of accessing your Office identity
or launching the Office applications?

bill

Home folder is kept on the network server, and the Office X folder is on the
local computer. I think the problem is launching the application.

Having a secondary problem with AD as well. If I log in (with domain
admin/enterprise admin permissions) my home folder on the network server
shows up, but if someone else logs into the Mac, without administrative
rights on the server, the home folder on the network server refuses to show
up.

 

[Bob]

What are you logging onto, Server 2003, 2000 etc.

If your users are authenticated on the Windoze box do they have rights
to the folder?
What I've got working is local install of Office 2004, home folder on
the mac for the office stuff it needs access too and just the user
files ( user home directory ) on a server 2003 box, ( but I
authenticate to a OSx 10.4.3 server so my shares are setup there.)
If you look under active directory when you bind to the domain there's
an option to create a local home folder on the mac ( 10.4.3 ) and this
sorted out a lot of office issues for me.