Office Setup: How the /n and /o Switches Are Used

 Last reviewed: September 16, 1996
Article ID: Q131397
The information in this article applies to:
  • Microsoft Office for Windows, versions 4.2, 4.3

SUMMARY

The /n and /o switches can be used on the command line from which you are running a custom installation script. These allow you to enter a user name (/n) and organization name (/o) that may be used during the setup. The purpose of these switches is to write the correct user information to the SETUP.INI file and the executable files of the installed applications, without prompting the user with dialog boxes for this information.

If the user name and organization name entries are found in the [User Info] section of the WIN.INI file, then these command line switches are ignored: the values entered for these switches are only used when there are no entries found in the [User Info] section of the WIN.INI file.

The values entered for these switches are not written to the [User Info] section of the WIN.INI file, even if they are not found there during setup. WIN.INI entries are only updated when a user is prompted on the screen with a dialog box to supply the values.

REFERENCES

For additional information on creating custom setup scripts, please see the following article(s) in the Microsoft Knowledge Base: 

   ARTICLE-ID: Q119357
   TITLE     : AppNote: "How to Create a Custom Installation Script"

KBCategory: kbsetup
KBSubcategory:

Additional reference words: 4.20 4.30




THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 16, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.