Using Group Policy/ADM files on Office 2003 Deployed w/ CIW

[Marks70]

I deployed Office 2003 to our XP clients using the Custom Installation
Wizard. I configured various settings, but now that users are starting to use
Office 2003, I'm running into things that I would like to change. Can I use
the Office 2003 .adm files in Group Policy to modify settings even though I
configured Office 2003 using the Custom Installation Wizard? Assuming I can,
what is the purpose of the Custom Maintenance Wizard, which supposedly allows
you to make changes to your installation after the fact?

Thanks!

 

[neo [mvp outlook]]

absolutely as the ciw and group policy object(s) set the same registry keys.


/neo

ps - caveat of course being that all machines are joined to an AD domain and
that the users logon with domain credentials and not a local account.

 

[neo [mvp outlook]]

absolutely as the ciw and group policy object(s) set the same registry keys.


/neo

ps - caveat of course being that all machines are joined to an AD domain and
that the users logon with domain credentials and not a local account.

 

[neo [mvp outlook]]

absolutely as the ciw and group policy object(s) set the same registry keys.


/neo

ps - caveat of course being that all machines are joined to an AD domain and
that the users logon with domain credentials and not a local account.

 

[neo [mvp outlook]]

absolutely as the ciw and group policy object(s) set the same registry keys.


/neo

ps - caveat of course being that all machines are joined to an AD domain and
that the users logon with domain credentials and not a local account.

 

[neo [mvp outlook]]

absolutely as the ciw and group policy object(s) set the same registry keys.


/neo

ps - caveat of course being that all machines are joined to an AD domain and
that the users logon with domain credentials and not a local account.

 

[neo [mvp outlook]]

absolutely as the ciw and group policy object(s) set the same registry keys.


/neo

ps - caveat of course being that all machines are joined to an AD domain and
that the users logon with domain credentials and not a local account.

 

[neo [mvp outlook]]

absolutely as the ciw and group policy object(s) set the same registry keys.


/neo

ps - caveat of course being that all machines are joined to an AD domain and
that the users logon with domain credentials and not a local account.

 

[neo [mvp outlook]]

absolutely as the ciw and group policy object(s) set the same registry keys.


/neo

ps - caveat of course being that all machines are joined to an AD domain and
that the users logon with domain credentials and not a local account.

 

[neo [mvp outlook]]

absolutely as the ciw and group policy object(s) set the same registry keys.


/neo

ps - caveat of course being that all machines are joined to an AD domain and
that the users logon with domain credentials and not a local account.

 

[Marks70]

Thanks a lot for your response. Just wondering what the point of the Custom
Maintenance Wizard is if you can just use Group Policy to make changes?

 

[Marks70]

Thanks a lot for your response. Just wondering what the point of the Custom
Maintenance Wizard is if you can just use Group Policy to make changes?

 

[Marks70]

Thanks a lot for your response. Just wondering what the point of the Custom
Maintenance Wizard is if you can just use Group Policy to make changes?

 

[Marks70]

Thanks a lot for your response. Just wondering what the point of the Custom
Maintenance Wizard is if you can just use Group Policy to make changes?

 

[Marks70]

Thanks a lot for your response. Just wondering what the point of the Custom
Maintenance Wizard is if you can just use Group Policy to make changes?

 

[Marks70]

Thanks a lot for your response. Just wondering what the point of the Custom
Maintenance Wizard is if you can just use Group Policy to make changes?

 

[Marks70]

Thanks a lot for your response. Just wondering what the point of the Custom
Maintenance Wizard is if you can just use Group Policy to make changes?

 

[Marks70]

Thanks a lot for your response. Just wondering what the point of the Custom
Maintenance Wizard is if you can just use Group Policy to make changes?

 

[Marks70]

Thanks a lot for your response. Just wondering what the point of the Custom
Maintenance Wizard is if you can just use Group Policy to make changes?

 

[neo [mvp outlook]]

I use the CIW to control what features are installed and what the "initial"
environment should be like. Really helps when you are not sure if that user
is going to get the initial policy objects from the domain. (e.g. Setting
up a workstation across a VPN connection. I've seen where GPOs don't apply
as well as one would like to do "administrative" decisions.)