Office 2003 Outlook adm Template

  • Thread starter Thread starter Michael
  • Start date Start date
M

Michael

I have a W2K Terminal Server and 2 x W2K DC's.

I can install the ork to the T/Server and 'group policy' all the Terminal
Server users Outlook settings - No Problem so far....

How do I do the same thing for the Regular Domain Users outside of Terminal
Server? I guess I install the ork to a DC....and then which policy template
would I import the Office adm Templates into? and how do I push only to 90%
of users - (you know that upper management wants all options available!)

Specifically I'd like to make the user's BCC: field 'unavailable' from
within Outlook 2003 - without walking round, discreetly to a 1000 PC's!
 
Michael,

Not sure if I am following your post. It seems to me that you have the
following situation:

You have a bunch of users who make use of Terminal Server. When the
initiate a TS session you have no problem having them get the 'GPO' stuff
for Office 2003. But, when your users log on to the 'normal' computers you
are having a problem getting the GPO to work ( and by 'GPO' I mean that you
are using Group Policy to install Office 2003 and by 'problem' I mean that
you are not able to get the .adm thingie to work..... ).

You have not told us how you are deploying Office 2003.

I 'assume' that you have created an Administrative Installation on a network
server ( you do this by running 'setup.exe /a' ) and that you have installed
the ORK either on that same server or on an 'admin-type' workstation. You
would then need to run the CIW ( Custom Installation Wizard - if I remember
correctly ) and create the .mst file(s). These are the transforms files.
Then, when you create the GPO you would have to go to the modify tab and
make sure to provide the path to the .mst file that you need....

While this is for Office 2000, please take a look at the following MSKB
Article:

http://support.microsoft.com/?id=284273

Also, there are two choices: you can deploy Office 2003 to either the user
configuration side of things or you can deploy Office 2003 to the computer
configuration side of things. Which one did you do?

Now, that is part one.

To make use of the different .adm file(s) you would need to 'add' the .adm
file(s) so that it/they is/are now 'available'. This should not be too
difficult to do. You would then simply make the settings that you want and
away you go.

This was part two.

--
Cary W. Shultz
Roanoke, VA 24012
Microsoft Active Directory MVP

http://www.activedirectory-win2000.com
http://www.grouppolicy-win2000.com
 
Cary, to answer your question as best I can.

Office 2003 usually comes pre-installed with a new PC. Or, I just copy the
entire application CD (Office e.g.) to a Server Share and, if needs be,
install from there using the usual 'out-of-the-box 'defaults.

So, Just like we can set the 'Domain Group Policy' to hide the 'last
username logged on' out of the PC username: logon prompt - I assumed that I
could load in the Office adm Templates, add them to Group Policy on a DC,
and then apply it to the network Users Outlook Settings from the User
Administration policies.

If I have to do administrative install points and custom adm templates
then - arghhhhhhh - so be it.! I just thought maybe the ork adm templates
added to a Domain Group policy would set up an 'unavailable BCC field' when
the user logs on. as in the dialog that makes you wait when it says -
'Applying Domain Security Settings'.

Does that help? Thanks....
 
Back
Top