How to grey out cancel button on First Launch Outlook 2003?

[marcia_mcmahon]

300 user roll out out of Office 2003. Two questions.
1.) How do I grey out the cancel button? Using the custom Installation
Wizard, I have an MST install that imports a PRF successfully and is
performing all of the installation and profile configurations without manual
intervention using this command line setup.exe
TRANSFORMS="K:\Outlook2003\MSItest\Custom Setup File.MST" /qb-. However, on
first run of the program as the "user" the cancel button is still active. Is
there a way to grey this out?
2.) How do I NOT ask my user their name on first run? My users log into
different PCs often, and, on first run the user name and server etc are all
resolving properly, however they must click OK on a user name pop-up (already
correctly auto-filled with their name). The pop-up appears at the very end
and it is clear that the name has already resolved and outlook is loading
their email. note: the configuring outlook pop-up is visable at this stage -
and you can see their mailbox open - but they must click OK. How can I
automate the OK click?

 

[Sue Mosher [MVP-Outlook]]

1) The cancel button on what dialog?

2) Is this the Outlook dialog or the Word dialog asking for initials?

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[marcia_mcmahon]

Sue,
Your posts have gotten me this far, hopefully you can shed some light on this.

1.) The user logs into the pc for the first time (post Outlook only
installation). Double clicks Outlook icon, then a pop-up (Blue bar says
Microsoft Office edition etc.) appears stating "preparing to install", then
the verbage changes "Please wait while Windows configures Microsoft Office
version " and below that reads "Gathering required information..." during all
of this the cancel button is active. I do not want my end users clicking
cancel, and they have been well trained to NEVER let anything get installed
on their PCs. This appears to an end user as an install and goes against what
my department has been telling them.

2.) N/A I already overcame this issue.