MS Office on Domains.

BoomAM

BoomAM

BoomAM

Soldato
Joined
5 Jul 2003
Posts
16,206
Location
Atlanta, USA
Hi.
Not sure on the exact forum, so posted here. :p

Can anyone tell me why that when i build a computer, install its software and whatnot, that apart from the first time i open, lets say for example MS Word, it'll do the mini installer thing, then ask me for my name and initials, then thats it.

BUT, when i add it to our domain at work, every time a user logs on, every time they open Word/Excel/ect;, it does the same thing as mentioned above?
Just a little niggle i'd like to get rid of tbh.

Thanks in advance all. :).
 
BoomAM said:
Hi.
Not sure on the exact forum, so posted here. :p

Can anyone tell me why that when i build a computer, install its software and whatnot, that apart from the first time i open, lets say for example MS Word, it'll do the mini installer thing, then ask me for my name and initials, then thats it.

BUT, when i add it to our domain at work, every time a user logs on, every time they open Word/Excel/ect;, it does the same thing as mentioned above?
Just a little niggle i'd like to get rid of tbh.

Thanks in advance all. :).
Click to expand...

Doesn't do that on any of the domains I've set up.

Do you have mandatory roaming profiles set up maybe?
 
Indeed, sounds like a profile issue.

Have a gander here might be a little bit of an insight in to what you need to do in order to solve the problem.
 
Not sure how its initially setup tbh.
Im in the fortunate and unfortunate position of still finding all the annoying little niggles and bodge jobs and whatnot is up with the network on my own, dropped in at the deep end if you will.
Fortunatelly, if i can identify why its doing this, and asuming its not a problem on the server itself, i can sort out a lot of our problems in the summer when i rebuild every workstation on the network.

Anyway:
a lot of the documentation i see mentions a 'run from network' install option, however everytime i install Office, thats not an option?

What exactely do i need to do to fix it? Is it something im gonna have to change in group policy editor, or just a modification to how Office is getting installed? Both?
This must be a fairly common 'error', there must be a idiot proof guide somewhere for me to use. :p.
 
a lot of the little office niggles can be fixed by setting the user up as a power user on the local machine.

I know you may not want to do this but it's a quick and easy fix.
 
doran1801 said:
you need to search microsoft.com for a program that will disable your MSOcache folder on c:\
Click to expand...
Is there a program that'll do that though?

##EDIT##
This mentions similar:
http://support.microsoft.com/kb/825933
But tbh, i cant see how moving the cache for MS Office will fix this problem when its a problem with the profiles? Unless im being daft (too early to think properly. :p)

Andy100 said:
a lot of the little office niggles can be fixed by setting the user up as a power user on the local machine.

I know you may not want to do this but it's a quick and easy fix.
Click to expand...
Not really an option tbh. :(.
 
Last edited:
copy the local admin profile into the default user, this solves the problem for people who haven't logged onto the PC before.

ie it will only fix the problem for users who dont already have a user profile on the pc.
 
topher said:
copy the local admin profile into the default user, this solves the problem for people who haven't logged onto the PC before.

ie it will only fix the problem for users who dont already have a user profile on the pc.
Click to expand...
Not really feasible for a network.
Im stuck on what to 'search for' in Google as well. :p
 
Thats what i do!
I install windows, then the drivers, then office, then run windows update, then install other apps. Then optimise the system a bit (defrag, startup programs, ect; ), then sysprep, then image.
 
Last edited:
BoomAM said:
Thats what i do!
I install windows, then the drivers, then office, then run windows update, then install other apps. Then optimise the system a bit (defrag, startup programs, ect;), then sysprep, then image.
Click to expand...

cool, so copying the local admin to default user will solve the problem in the future
 
i mean when you next create a new image install all your apps as normal then copy the local admin profile into the default user profile. this will solve the problem of office setup running when users logon and run the app for the 1st time.

hope that makes sense
 
google office administrative install

You can create a central install for office, then either assign it to machines via GP or install from it onto one of your images before you deploy that to the client machines
 
topher said:
i mean when you next create a new image install all your apps as normal then copy the local admin profile into the default user profile. this will solve the problem of office setup running when users logon and run the app for the 1st time.

hope that makes sense
Click to expand...
You mean on the server or on the workstation?
And where is the profile that your on about stored?

Ive done a google search for 'office administrative install' and nothing comes up, just 'office administration points'. :confused:
 
Are your users on roaming or local profiles?

Are your users running mandatory, or ortherwise read only profiles?

Is it on every machine? or is it only for specific users?

When a user first opens Office, it creates a directory structure in their profile (this is what the "mini installation" is doing). If it keeps doing this, it's because it can't find the structure and config files in the default location.
 
You must log in or register to reply here.
Back
Top Bottom