This is a discussion on Re: info to clear up problems with domain environment - SMB ; On Tue, 9 Dec 2003 13:56:39 -0500, "Gary Roach" wrote: If the domain controller is win2k with AD you can use win2k package to install the office so you dont have to visit each pc it will just install its ...
On Tue, 9 Dec 2003 13:56:39 -0500, "Gary Roach"
If the domain controller is win2k with AD you can use win2k package to
install the office so you dont have to visit each pc it will just
install its self when they log on. You first install it to the network
as a admin install(office admin not domain admin) give the user the
same network drive as a shared drive with the same drive letter.
Create the Administrative Installation
The first step in deploying Office over a network is to create the
administrative installation. To do this, you need at least 550 MB of
free disk space on a central server, and you need write access to the
server. After you are sure that these two requirements are met, follow
NOTE: You can perform these steps while you are logged on to the
server or from a network client that has a connection with the server.
To install from connection:
Insert the Office CD-ROM, and cancel any AutoRun activity that may
occur. (Most applications that are available on CD-ROM have an AutoRun
feature. When the CD-ROM is inserted into the CD-ROM drive, AutoRun
initializes the startup and splash screens for the program's
installation. Cancel out of this, if it occurs).
Click Start and then click Run. In the Open box, type the following,
and then click Office 2000 Developer:
NOTE: Path is the path to your CD-ROM drive or DVD-ROM drive that
contains the Office CD-ROM.
In the Customer Information dialog box, type the CD key from the back
of the Office CD-ROM case.
Type the name of your corporation in the Company box. This is the name
that will appear in the Office program splash screens that are
displayed every time you start an Office program. Click Next.
In the License and Support Information dialog box, accept the license
agreement, and then click Next.
In the Installation Location dialog box, accept the default.
NOTE: You can specify a different destination folder for the
administrative installation. This location can be a folder on a local
hard disk or a folder on another computer. You can specify either a
mapped drive or a UNC path to the folder. You can also click Browse to
browse for the folder.
Click Install Now. The CD-ROM's contents are copied to the install
path that you indicated, and the administrative installation is ready
You could use wise install and create a package and then run it with a
/s so the user wouldnt see it.
Changing a user from user to admin will change their profile unless
you create a profile for each user and specify that as there profile.
http://support.microsoft.com/default...;EN-US;KBHOWTO to get
info on any problems
>i'm running a domain with a domain controller running samba 3.0.24 and
>windows xp pro workstations. i'm having a number of problems that i've
>posted questions about on various newsgroups including:
>* not being able to change users permission levels (domain admins to domain
>users) without causing they're start menu to become messed up,
>* trying to install office xp so that any user can log onto any computer
>without having to provide the office xp cd to install (which can't be done
>anyway if they're a domain user)
>i need some reference material to clear up all these nagging details to do
>with operating in a domain environment. does anyone know where to get books
>or other information for this? any help is greatly appreciated.