"quiet" install of Word 2003

[Will]

I'm not sure if quiet install is the correct term but this is what I need to
acomplish:

I want to install Word 2003 so that when a user opens Word the first time
they do not get any prompts for their initials, etc. I just want Word to
open. How do I accomplish this?

Thanks.

Will

 

[Bob Buckland ?:-\)]

Hi Will,

If this is to support roaming/travelling users then the MS Installer creates a variety of entries for that user on first startup for
that user. One of those is the name stored from Word's Tools=>Options=>User Info. Unless you're going to prepopulate the user area
registry key with their information you may get that prompt.
http://office.microsoft.com/en-us/ork2003/HA011402061033.aspx

==========
I'm not sure if quiet install is the correct term but this is what I need to
acomplish:

I want to install Word 2003 so that when a user opens Word the first time
they do not get any prompts for their initials, etc. I just want Word to
open. How do I accomplish this?

Thanks.

Will>>
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

 

[Bob Buckland ?:-\)]

Hi Will,

If this is to support roaming/travelling users then the MS Installer creates a variety of entries for that user on first startup for
that user. One of those is the name stored from Word's Tools=>Options=>User Info. Unless you're going to prepopulate the user area
registry key with their information you may get that prompt.
http://office.microsoft.com/en-us/ork2003/HA011402061033.aspx

==========
I'm not sure if quiet install is the correct term but this is what I need to
acomplish:

I want to install Word 2003 so that when a user opens Word the first time
they do not get any prompts for their initials, etc. I just want Word to
open. How do I accomplish this?

Thanks.

Will>>
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

 

[Bob Buckland ?:-\)]

Hi Will,

If this is to support roaming/travelling users then the MS Installer creates a variety of entries for that user on first startup for
that user. One of those is the name stored from Word's Tools=>Options=>User Info. Unless you're going to prepopulate the user area
registry key with their information you may get that prompt.
http://office.microsoft.com/en-us/ork2003/HA011402061033.aspx

==========
I'm not sure if quiet install is the correct term but this is what I need to
acomplish:

I want to install Word 2003 so that when a user opens Word the first time
they do not get any prompts for their initials, etc. I just want Word to
open. How do I accomplish this?

Thanks.

Will>>
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

 

[Bob Buckland ?:-\)]

Hi Will,

If this is to support roaming/travelling users then the MS Installer creates a variety of entries for that user on first startup for
that user. One of those is the name stored from Word's Tools=>Options=>User Info. Unless you're going to prepopulate the user area
registry key with their information you may get that prompt.
http://office.microsoft.com/en-us/ork2003/HA011402061033.aspx

==========
I'm not sure if quiet install is the correct term but this is what I need to
acomplish:

I want to install Word 2003 so that when a user opens Word the first time
they do not get any prompts for their initials, etc. I just want Word to
open. How do I accomplish this?

Thanks.

Will>>
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

 

[Will]

Bob -
This is not for roaming users. The explanation is a bit convoluted so I'll
try and make it brief. We serve an application via Terminal Server. Let's
call it application X. For security reasons I have the Terminal Server
locked down so that when the user logs in, the application X login pops up
and they log in. They never see the windows desktop in the session nor any
other windows. Now we have begun storing Word documents in application X's
database. There is a link to the Word document in Application X that they
click to see the document. Works fine in the test environment. But since
Word is not on the production Terminal Server once I install it users will be
prompted for the typical first run Word settings (user initials, etc.) when
they click the document link for the first time, which is the crux of the
problem - since the server is locked down they don't see the window to enter
their initials etc. and Word never opens. So hence my question how to
install Word so that the user is not prompted for any information the first
time they run it. Thanks.

 

[Will]

Bob -
This is not for roaming users. The explanation is a bit convoluted so I'll
try and make it brief. We serve an application via Terminal Server. Let's
call it application X. For security reasons I have the Terminal Server
locked down so that when the user logs in, the application X login pops up
and they log in. They never see the windows desktop in the session nor any
other windows. Now we have begun storing Word documents in application X's
database. There is a link to the Word document in Application X that they
click to see the document. Works fine in the test environment. But since
Word is not on the production Terminal Server once I install it users will be
prompted for the typical first run Word settings (user initials, etc.) when
they click the document link for the first time, which is the crux of the
problem - since the server is locked down they don't see the window to enter
their initials etc. and Word never opens. So hence my question how to
install Word so that the user is not prompted for any information the first
time they run it. Thanks.

 

[Will]

Bob -
This is not for roaming users. The explanation is a bit convoluted so I'll
try and make it brief. We serve an application via Terminal Server. Let's
call it application X. For security reasons I have the Terminal Server
locked down so that when the user logs in, the application X login pops up
and they log in. They never see the windows desktop in the session nor any
other windows. Now we have begun storing Word documents in application X's
database. There is a link to the Word document in Application X that they
click to see the document. Works fine in the test environment. But since
Word is not on the production Terminal Server once I install it users will be
prompted for the typical first run Word settings (user initials, etc.) when
they click the document link for the first time, which is the crux of the
problem - since the server is locked down they don't see the window to enter
their initials etc. and Word never opens. So hence my question how to
install Word so that the user is not prompted for any information the first
time they run it. Thanks.

 

[Will]

Bob -
This is not for roaming users. The explanation is a bit convoluted so I'll
try and make it brief. We serve an application via Terminal Server. Let's
call it application X. For security reasons I have the Terminal Server
locked down so that when the user logs in, the application X login pops up
and they log in. They never see the windows desktop in the session nor any
other windows. Now we have begun storing Word documents in application X's
database. There is a link to the Word document in Application X that they
click to see the document. Works fine in the test environment. But since
Word is not on the production Terminal Server once I install it users will be
prompted for the typical first run Word settings (user initials, etc.) when
they click the document link for the first time, which is the crux of the
problem - since the server is locked down they don't see the window to enter
their initials etc. and Word never opens. So hence my question how to
install Word so that the user is not prompted for any information the first
time they run it. Thanks.

 

[neo [mvp outlook]]

So here is yet another silly question, why give them the full Word
application when you can install the Word 2003 viewer?

 

[neo [mvp outlook]]

So here is yet another silly question, why give them the full Word
application when you can install the Word 2003 viewer?

 

[neo [mvp outlook]]

So here is yet another silly question, why give them the full Word
application when you can install the Word 2003 viewer?

 

[neo [mvp outlook]]

So here is yet another silly question, why give them the full Word
application when you can install the Word 2003 viewer?

 

[Will]

It's not a silly question. In fact, I'd go so far as to say the suggestion
is brilliant if it solves the problem. I'll give it a try. Thanks.

 

[Will]

It's not a silly question. In fact, I'd go so far as to say the suggestion
is brilliant if it solves the problem. I'll give it a try. Thanks.

 

[Will]

It's not a silly question. In fact, I'd go so far as to say the suggestion
is brilliant if it solves the problem. I'll give it a try. Thanks.

 

[Will]

It's not a silly question. In fact, I'd go so far as to say the suggestion
is brilliant if it solves the problem. I'll give it a try. Thanks.

 

[Will]

Word Viewer didn't solve the issue. I installed Word Viewer and it correctly
opens Word documents. But, it does not open them if you attempt to open the
Word document that is stored within Application X. However, if Word Viewer
is already open then the Word document opens when clicked via Application X.
So it appears there is nothing wrong with the file type association on the
server - rather the problem must be something funky in the way Application X
handles the association. Do you have any other ideas? Thanks.

 

[Will]

Word Viewer didn't solve the issue. I installed Word Viewer and it correctly
opens Word documents. But, it does not open them if you attempt to open the
Word document that is stored within Application X. However, if Word Viewer
is already open then the Word document opens when clicked via Application X.
So it appears there is nothing wrong with the file type association on the
server - rather the problem must be something funky in the way Application X
handles the association. Do you have any other ideas? Thanks.

 

[Will]

Word Viewer didn't solve the issue. I installed Word Viewer and it correctly
opens Word documents. But, it does not open them if you attempt to open the
Word document that is stored within Application X. However, if Word Viewer
is already open then the Word document opens when clicked via Application X.
So it appears there is nothing wrong with the file type association on the
server - rather the problem must be something funky in the way Application X
handles the association. Do you have any other ideas? Thanks.