A problem has been observed when launching Microsoft Office products on satellite terminals.
Please check the following links for solutions to the problems that have occurred.

• Office product does not start / A dialog box appears and “Error code 80090016” is displayed.
• When starting up the Office product, a screen appears asking for a multifactor authentication code number even though I do not remember setting up multifactor authentication, and I cannot proceed.
• Office product does not start / The screen goes blank at the authentication operation and does not proceed.

Office product does not start / A dialog box appears and “Error code 80090016” is displayed.

Solution

1. Open [Start] – [Settings] – [Accounts] – [Access to work or school].
2. Click [Disconnect] when the connected accounts are displayed.
3. Two confirmation dialogs will appear in succession. Click [Yes] on the first dialog and [Disconnect] on the second dialog.
   When asked to restart, do so.
4. After completing the above, start the Microsoft Office product again and enter your @u email address and password when the dialog box appears.

This trouble may also occur when you use a satellite device with an account that you signed in to without following the settings below when signing in at the time of Office product startup on your PC.
This procedure is different from the setting when using Office products on a satellite device. Please be careful.

The following is a reference to an image posted on the A.C.C.C. Web.

If the above does not resolve the issue, please try this as well.

When starting up Office products, a screen asking for a code number for multi-factor authentication appears even though I do not remember setting up multi-factor authentication, and you cannot proceed.

Solution

You need to initialize multifactor authentication with administrator privileges.
Please send an e-mail to the address listed under “Other General” in the “Inquiries” section, or contact the Academic Center for Computing and Media Studies.

The screen goes blank at the authentication operation and does not proceed.

When launching Microsoft Office applications on Windows Remote Desktop or Satellite Terminal of The Zengaku Computer System, the screen may go blank at the authentication process and you may not be able to proceed. In some cases, you may be asked to perform the same authentication operation several times.

Solution

You can improve the situation by disabling the multi-factor authentication setting at the following site.

Academic Computing Communications Center,University of Tsukuba
Cloud mail service authentication setting system (Microsoft 365)
https://m365setting.u.tsukuba.ac.jp/

Even if the authentication appears to be disabled on the screen, the authentication behavior may be improved by enabling it once and then disabling it again.

Alternatively, the error no longer occurs when the multi-factor authentication settings are completed to the end.

To reproduce the problem

The problem was reproduced when Office was started with the multi-factor authentication setting halfway completed.
If multi-factor authentication is enabled and the associated authentication application or phone settings are not completed, the authentication screen of the Office app version will go blank or an error message will appear.

Solution #3 added on 7/28

A new solution has been found and added to the FAQ. “Change account settings” in Windows.
Please see below for details.
Microsoft Product Authentication Failures on Terminals and Remote Access Service Solution #3

If the problem persists

If the above does not solve the problem, please also try the solution #2 in the FAQ below.
Microsoft Product Authentication Failures on Terminals and Remote Access Service

The Zengaku Computer System has been switched from the old system to the new system. The new system is available for use.

Sunday, March 12, The Zengaku Computer System was updated from the old to the new system.
March 13 (Mon) Trial operation period of the new system begins
March 27 (Mon.) Start of the main operation (official operation) period

Prior to this, the mail system was switched over.

February 27 (Mon.) Authentication system for student @s mail changed.
March 5 (Sun.) Mail system migration.

During the trial operation period, you can try out the terminals and servers of the new system. However, since this is a trial operation period, the system may become unstable or some software may not be available due to adjustment work or configuration changes. Some software is currently being installed.

The user home files that each user used in the old system can be accessed from the O drive in the Windows environment of the new system.

Web pages have also been switched to the new system.

Relatively major changes between the old system and the new system are listed below. Please refer to the above web page for details.

====================

• Email user authentication is now Microsoft 365.
• Email addresses have been unified to @u.
• Windows OS on the terminal is now Windows 11.
• There are now two types of printers: monochrome printers and color printers. Depending on which printer is used, the number of print points consumed changes.
• IP addresses of terminals, servers, and various equipment have been changed to those of the new system.
• Shako satellite and CEGLOC satellite have been added to the system.

====================

The past announcements regarding The next Zengaku Computer System are as follows.

title：Transferring user home files from the current system to the new system (Details)
Publication Date：2023/3/9

title：E-mails of Zengaku Computer System
title：Active! mail forwarding settings migration
Publication Date：2023/2/28

title：Change the @s Email System (Note: Closed to public)
Publication Date：2023/2/21

title：Migration Schedule to the next Zengaku Computer System (Note: Closed to public)
Publication Date：2023/2/9

title：Regarding Remote Access and User Home File Transfer in the next Zengaku Computer System
Publication Date：2023/2/7

title：The website for the next Zengaku Computer System is now available (January 31 postscript)
Publication Date：2023/1/26

We would like to inform you of details regarding the transfer of user home files from the current system to the new system.
There are some modifications from this previous announcement. Please note the following.

• The old user home is migrated separately from each user’s home.
  This is because if the various configuration files are migrated as they are, problems may occur when logging in (signing in) on the new system.
  The old home is read-only. Please copy the necessary files to the new home before use.
  　Windows environment: O drive.
  　Linux environment: /oldhome/UTID-NAME.
  　　　　　　　　(UTID-NAME is your login name)
• Each user’s web-publishing folders (directories) have been migrated. These folders (and the files in them) can be used as in the old system.
• Your .ssh folders of users who had set up public keys in the old system have been migrated.
• All other files and directories, including files and directories other than the above directly under home, will not be transferred to the new system directly under user home, so please be very careful. Please copy all necessary files to the new system by yourself. Configuration files and program files used in the old system may not be usable in the new system, so please copy them at your own risk.

The following is a screen shot of O drive using Explorer on Windows.