Caramba onboarding (computer stuff)

Brief summary

What is this document?

This document is a must-read for everyone arriving in the group, students and permanent members alike. If you don’t read it from line 1 to n, it’s quite likely that you’ll need to come back to it sooner or later.

The stuff here summarizes the (many) steps that you need to take in order to have a complete working environment in the lab. Nothing is totally simple nor easy, but hopefully this document will be of some help. If it is not, maybe you can contribute to making it better. Better, you’re even welcome to.

Caution: old documentation is bad documentation

A word of warning. Technical documentation is not fine wine: it doesn’t age well. Every bit of documentation you consult, this document included, must be taken with a grain of salt. Always check the date. If the document is infrequently updated, then bad stuff happens. As far as this document is concerned, it means that links may go stale, stuff that once was true no longer is, and so on.

What do you need in order to read it?

You obviously need a computer, you more or less need to be physically in the lab at least for the first few steps.

You definitely need your login and initial MFA (multi-factor authentication) credentials, see there.

You need to have some basic unix working environment. A linux computer is ideal, but under windows WSL is fine too. In most cases, you’ll have a harder time getting windows-related help.

Whom should I ask for help?

If you’re a masters or PhD student and you feel lost with all this information, then the #1 informant is your advisor.

Other team members and office mates are also likely to have some answers.

What external resources can/should I use?

DOC-SI. The following access links can be used: from the wired network, or through the inria vpn over SSL. The vast majority of doc-si is not translated in English. If you don’t read French, be prepared for a ride. (It could be that the bare essentials are indeed translated, though.) Please remember this word of warning.

Helpdesk. Some steps below require that you go through helpdesk. You’ll get help from the SIC (CS service desk) there. This has nothing to do with the team. As above, two access links: from the wired network, or through the inria vpn over SSL. Don’t go bother people from SIC in person, it’s usually not a good idea.

Documentation on your system. Most unix systems come with ample documentation, and as the adage says, it’s always good to Read The Fine Manual, at times. Computer science proficiency sometimes comes at the cost of being able to read that documentation.

Documentation on the web. Most questions have already been answered by others. When it’s lab-specific, you’re probably not going to find the answer on the web, but for most of the generic stuff you will. Stackoverflow is a great resouce.

Where exactly is this document?

This document is/will be posted on a hidden URL on the caramba web site. It source code is in markdown and resides in the caramba gitlab repository, which you’ll learn to access by reading this document.

Some terminology

SIC (service informatique du centre), or “moyens info” is the team in floor 0 of building B. They’re mostly reachable via helpdesk.

DSI (direction des systèmes d’information) without a C typically refers to the nationwide inria staff dealing with computer stuff. SIC is part of DSI.

Dependency chains

(insert a diagram in mermaid with what is needed before what.)

Onboarding steps proper

Get MFA to run

The email with you login credentials contains some crucial info:

• your inria login
• your initial inria password
• two initial MFA tokens

This email is sent by no-reply.remi@inria.fr and is typically entitled:

[REMI][info] User Dupont Martin (0000HKWT, mdupont): created or re-initialized

It is sent a few days before your arrival to about 6 people: team leader, inria assistant, loria assistants, loria HR staff, loria admin head. Unless Emmanuel forgot about it, your advisor should have received a copy of it.

The first step is to make sure that you can connect to https://portail-mfa.inria.fr

• If you have a desktop computer in your office, things are easy. Log in with the password that you found in the aforementioned email. You should be able to reach https://portail-mfa.inria.fr already. Warning: never turn off the desktop computers, as other team members might be using them to run computations.
• If you have a laptop that belongs to the group and has a wired internet connection (with an RJ45-type ethernet cable going to your machine or desktop hub), then the same should hold. If it doesn’t, or you don’t know what that means, consider that you don’t have a wired connection and read on.
• If you only have a laptop, it’s harder. You need to
  • connect it to eduroam
  • set up the inria vpn and activate it (the vpn step is pretty much down the line in this document, but you need it to go past this first step).

Now it’s time to actually configure MFA. You will need your initial MFA tokens for this, and configuration is done via https://portail-mfa.inria.fr ; if you followed the previous steps, you should be able to reach this site. You should also be able to access the official documentation, so please read on from there.

Change your password

Once MFA is set up, you must go to https://password.inria.fr/ to change your password. You should use a password manager, by the way.

Read your email

It’s also possible to use an email client such as Thunderbird. Documentation for doing so can be found on doc-si

Set up eduroam on your laptop

NOTE There are other wireless networks that look tempting, such as “Inria interne” or “Inria guest”. They’re mostly useless. Everything can be done with eduroam, or eduroam+vpn. Learning to configure eduroam and the vpn will get you a longer way than the short sighted Inria wireless networks, and this document will assume that you have done so.

Under linux (do NOT follow the DSI Windows instructions on linux), activate your wifi and select the “eduroam” SSID. You’ll get a dialog box which you should fill in as follows. Note that some boxes change names from time to time, but hopefully not in a way that will make configuration impossible. If your laptop speaks French, German, Elvish, or Klingon, your mileage is going to vary slightly. Use your translation skills.

• Security: “WPA & WPA2 Enterprise”
• Authentication: “Tunneled TLS”
• Anonymous identity: “anonymous@inria.fr”
• Domain: leave blank
• CA certificate: download this file. Store it somewhere on your laptop, but please not only in the “Downloads” foler. Choose a place where it will stay. Then set the dialog box to point to this document.
• Inner authentication: PAP
• Username: your Inria login
• Password: your Inria password

Under Windows, I don’t know. It might be somewhat similar. The following link (from the DSI docs) may be of some help.

Generate an ssh key

You’ll need this for many of the further steps. An ssh key consists of two files:

• a private key, which is typically named id_rsa or id_ed25519. You never give this file to anyone. Key generation tools will even invite you to secure this key with a password. You’ll need it on the machines from which you work (e.g., your laptop – more generally on machines on which you initially log in from the login screen).
• a public key, which is typically named id_rsa.pub or id_ed25519.pub. This file is the one you’ll give to sites on which you want to authenticate.

You can skip this step if you already have an ssh key!

To generate a key pair, use the ssh-keygen tool from the command line (either from a terminal under linux, or from the WSL command line under windows). Leave the file locations as suggested by default. The password that you choose will be used to secure the private key, which means that you’ll need to type it in when you use it. Desktop environments such as gnome are able to memorize it for as long as your session lasts, so typically you don’t have to type this password exceedingly often.

Remember the location of the public key. It’s typically /home/your_username/.ssh/id_ed25519.pub. If you’re on a desktop machine, it’s /users/your_inria_login/.ssh/id_ed25519.pub.

Log in to gitlab.inria.fr

• Go to https://gitlab.inria.fr/ (please do NOT mix it up with other gitlab installations, they’re all different!)
• Open the “ildap” tab. (it’s probably the default one)
• enter your inria login and password

You must now add your ssh key to your gitlab account. To do so:

• go to https://gitlab.inria.fr/-/user_settings/ssh_keys ; or equivalently, click on the colored avatar icon that is on the right side of the left navigation pane and then on the “SSH keys” menu item.
• click on “add SSH key” (on the right)
• in the text box, put the contents of your SSH public key file (you have one because we’re now past this step).
• clear the “expiration date” box, it’s a nuisance.

Now that you logged in at least once on gitlab.inria.fr, your login has become visible to some tools. It is time to:

• ask your advisor to add you to the caramba/caramba repository (NOT the “caramba” upper-level group). It is done on this page.

• ask your advisor to add you to the caramba group on mattermost. It’s the buttons shown here on the right.

• ask your advisor to add you to the caramba@inria.fr mailing list and (if applicable) to the dir-caramba@inria.fr mailing list. For the caramba@inria.fr list, it is done on this page.

• say hi on mattermost: connect to https://mattermost.inria.fr/. You should see the “caramba” team. Learn about the different public channels. Some are not serious. The mattermost etiquette is not written anywhere, but it’s basically that of a nice and safe workplace.

Check out the caramba git repository

In a terminal, on a machine where your SSH private key is present, you should now be able to type:

git clone git@gitlab.inria.fr:caramba/caramba

You’ll certainly need to accept the ssh public key of gitlab.inria.fr as a first step: the following is totally normal (it’s the current status of the key as of late 2024):

The authenticity of host 'gitlab.inria.fr (128.93.193.23)' can't be established.
ED25519 key fingerprint is SHA256:XwyOMni3C7481RBbwnvgHuWuR+4OF6uPgIa+pJ9aF08.
This key is not known by any other names.
Are you sure you want to continue connecting (yes/no/[fingerprint])?

If the checkout succeeds, it’s a good sign! If you can’t tell if it indeed succeeded, see if you have a file called caramba/www/content/en/onboarding.md: it’s actually the source code of the file you’re reading now.

It’s also time to make sure that you have git correctly set up and working also for pushing stuff. Let’s add yourself to the members page! (fear not: there’s no mistake that can’t be recovered)

• go to the caramba directory with cd caramba
• edit the file layouts/shortcodes/members.md. It’s the list of members. Add a line in the relevant section. Take inspiration from the existing lines to add yourself. Please follow alphabetical order. The full list of valid capital letter codes is in i18n/en.yaml and i18n/fr.yaml.
• you can now type git commit -a, write a commit message, and then git push.
• the web site should build automatically, and after one minute or so you should be on https://caramba.inria.fr/members. If you’re not and you managed to break everything, you’ll get an email (except if you’re very creative in your breaking). Try to understand what you did, try to fix it, and call your advisor for help if it’s all chinese.

What you’ll learn from the documents in there

There are many documents in the caramba repository. Some are outdated. Feel free to look up the ones that you find interesting. Always look up the modification history, though, e.g. with git log machines.txt.

The machines.txt file, by the way, is one of the active files, it contains useful info about the various machines of the team.

Set up inria vpn access

doc-si page

Contrary to what is sometimes heard in ridiculous advertisements, a VPN is not, per se, something that allows you to connect to weirdo web sites in funny countries.

The inria VPN is the stuff that, from your machine that is outside the inria network, will let it appear as if it were inside the inria network.

You don’t need the inria VPN if you’re already on the inria wired network: it’s pointless.

The VPN comes in two flavors.

• a web site https://vpn.inria.fr/ on which you can log in. You’ll be able to access some sites from there, but not all, because DSI only configured a handful of bookmarks.
• a full-fledged vpn interface, which requires some software to run on your machine.

The instructions here tell you how to install the full-fledged vpn interface.

On linux (at least on debian/ubuntu), you must install the package network-manager-openconnect-gnome, with:

sudo apt update
sudo apt install network-manager-openconnect-gnome

Similar packages exist in other linux distributions. Obviously your mileage may vary. On Fedora it’s called NetworkManager-openconnect-gnome, for example. If your desktop environment is not gnome, you’re on your own. If you don’t know, then it’s gnome and you can read on.

• On the top right of your screen, click on the bunch of icons, and then on the cog wheel. You’re in the gnome settings app.
• Go to “network” (among the first few choices on the left navigation pane).
• You should have a “VPN” section on the main pane, with nothing inside, and then a + sign. Click on it.
• Choose “multi-protocol VPN client (openconnect)” (if you don’t have this option, you’re missing the openconnect plugin for networkmanager).
• Fill out “Identity” as follows:
  • choose a name, e.g. “VPN Inria”
  • VPN protocol is “Cisco AnyConnect or OpenConnect”
  • gateway is vpn.inria.fr
  • CA certificate must be filled in. Select from file, and point to where the Chain-TCS-4-OV.pem file resides in your home directory (you already had to store that file somewhere in the eduroam step. For the record, you can download it from this link).
  • and you’re done. You can click “Add” on the top right.
• Now click again on the top right of your screen. A greyed out “VPN Inria” tile should have appeared. If you click on it, it will ask you for your inria login and password.
• The tile remains lit as long as you’re connected to the VPN. You can cut off the VPN by clicking on the tile again. Note that the VPN automatically goes off when your computer goes in standby mode or if its network connection changes.

To verify that you’re indeed connected to the vpn, you can try to access one of the vpn-only web sites such as https://doc-si.inria.fr/

Under windows, vpn access can be set up by downloading the Cisco VPN agent from https://vpn.inria.fr/ (you’ll download a several years-old version first, and then it’ll auto update). Just point it to vpn.inria.fr as a gateway address, it should work.

Set up ssh access to the team machines

Setting up SSH access to all the caramba machines depends on what machine you’re currently using. Obviously, it assumes that you already generated an ssh key:

• If you already are logged in on one of the team desktop machines, setting up SSH access to all the caramba machines is very easy and only takes one line in a terminal:

cp ~/.ssh/id_ed25519.pub ~/.ssh/authorized_keys

• If you’re on a laptop on the inria wired network, or on the inria vpn, you need to install your ssh public key on the team machines. You can do so with the command line below. Since it’s the very first time you connect to the team machines, you’ll need to type in your inria password as it’s the only authentication method that the machines know about you.

scp -p ~/.ssh/id_ed25519.pub YOUR_INRIA_LOGIN@tartine:.ssh/authorized_keys

Once this is done, you should be able to connect to all machines without having to type your password (ssh will use your private key instead). For example, try ssh biscotte.

(again, actual machine names are in machines.txt)

Set up remote access to the lab via the ssh bastion

In order to access the lab machines from the outside (as opposed to from the wired network), you have two options:

• the VPN option (see the previous VPN and SSH steps)
• or you can directly connect to the ssh login machine without the VPN. Such a machine is called a bastion machine. This option still requires that you correctly set up SSH access to the team machines.

This section documents the second option. Setting it up is not strictly necessary, but it is often handy. The bastion machine is called ssh-nge.nancy.inria.fr.

• Go to https://account.inria.fr/ and copy-paste the contents of your public key files in the “SSH key management” / “Gestion des clefs SSH” section. (alternatively, you can also post a ticket on helpdesk to do the same).
• wait something between 15 minutes and a week (the “post a ticket” strategy is likely to take more time that the account management portal).
• meanwhile, add the following to the file ~/.ssh/config on your machine:

Host *.loria.fr
        User YOUR_INRIA_LOGIN
        ProxyJump ssh-nge.nancy.inria.fr

• once both steps are done (and in particular that you’ve successfully cleared the helpdesk hurdle), you should be able to type ssh tartine.loria.fr.

Connect your laptop to the wired network (if applicable)

In theory, there’s nothing to be done here, because:

1. If your machine was puchased by the lab, it should have had its ethernet mac address registered, and automatically be able to get an IP address from the DHCP.
2. If we’re talking of your personal machine, then it should not be allowed to connect to the lab wired network. https://doc-si.inria.fr/display/SU/Reseau+filaire#tab-Nancy

However there are exceptions to this, e.g. 1. requires at the very least a first step of registering the ethernet mac address with someone, or maybe 2. is not exactly enforced. So here goes.

By wired network, we mean the Ethernet network, which comes with an RJ45/8P8C connector.

Not all computers, especially not all laptops, have a physical Ethernet connector nowadays. Several situations can exist.

• Maybe your computer does have an Ethernet connector.
• Maybe you’re connecting to a hub, or dock , or a screen that embeds such functionality, and that has an ethernet connector (we have a few such monitors in the team, as well as several docks).
• Maybe you’re just using an ethernet adapter.
• and if none of the above is true, it seems unlikely that you’re able to plug an ethernet cable, so you should just forget about connecting to the wired network.

In principle, all you have to do is register your ethernet mac address with SIC, and this is done via helpdesk. In practice, nowadays, this has become quite complicated, because the question that arises immediately is which mac address. It can be the mac address of the computer itself, or it can be the mac address of the adapter/hub/dock/monitor. In several cases, this distinction is not very important, but you may have a preference for the former (e.g. because you’re not sure that you’re going to consistently use the same lightweight hub or adapter).

• if that matters to you, in some cases you can force your computer to advertise a consistent mac address through adapters/hubs/docks (it is true even if your laptop does not have an RJ45 connector: there’s a hidden mac address on the motherboard). This is called the “pass-through mac address”, and it’s something that you set up in the BIOS. Alas, there’s no consistent way to do this, since it depends on the computer brand. Look around in the bios settings, and see how it goes. Note that some combinations are known not to work (hp laptop with dell dock, at least as of 2024).
• if you choose to live with the default setting, understand then that the mac address that you’re going to see in the next steps will be the adapter’s.

To get the mac address, plug an ethernet cable and then type the following command in a terminal:

ip -f link address show

You’re interested in only one of the outputs, namely the one that concerns the interface whose name starts with eth, ens, enx, or elo (or maybe some other stuff that probably starts with an e). For example, this output bit for an interface called ens18:

2: ens18: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether bc:24:11:f9:4c:5f brd ff:ff:ff:ff:ff:ff
    altname enp0s18

The mac address in this case is bc:24:11:f9:4c:5f.

An alternative approach to get the mac address is to open a terminal and type: cat /sys/class/net/e*/address (you may need to replace e* by the name of your ethernet interface if you get multiple matches).

You then need to fill out the form here (it’s helpdesk, so you need to have vpn access). You will need quite a few extra things:

• the serial number (also called “service tag”). It’s generally printed on the chassis of your laptop. Under linux, you can also get it from the command line with sudo smbios-sys-info if you install the package smbios-utils first.
• the inventory number. It’s a lab thing. It should be a sticker taped on your laptop, or it’s handrwitten on the laptop box.
• the machine name. Of your choosing, if it’s available. Your machine will have the fully qualified name <machine name>.loria.fr, but it will not be accessible from the outside directly anyway. To find out if, e.g., wrench.loria.fr is available, try to do a DNS resolution with host wrench.loria.fr. If it says not found, the name is available.
• team, and advisor (or team leader) name.

Under Windows, the procedure is pretty much the same, except for the tools that you use. The mac address might be visible from the system settings (not checked), or with the ipconfig /all command on the command prompt (execute the “cmd” utility). DNS resolution can be done on the WSL command line.

Installing Ubuntu on your laptop

If the team provided you with a new laptop upon your arrival, and if (as the team recommends) it doesn’t already have a decent operating system installed by the DSI, you will probably want to install a recent version of Ubuntu. (If you choose to install another version of Linux, this tutorial is not for you.)

The easiest way is to make and use a bootable USB stick, following these instructions.

Power off your laptop, insert the bootable key, turn the laptop on, and select “Try or install Ubuntu”. The defaut options for the installation are fine, but be sure to encrypt your disk as the Inria policies require: when asked for further installation options, select “Use LVM with disk encryption”, then follow the rest of the steps as usual.

Software

sagemath

Installing Sage on your own laptop is also possible. There are three options:

• The preferred method is to use docker as on the team machines. Assuming you set up ssh access to the team machine tartine, run:

sudo apt update
sudo apt install docker.io
sudo usermod -aG docker <your login on your machine>
scp -p tartine:/usr/local/bin/sage ~/.local/bin/

Check that sage has been correctly identified as an executable: which sage

Then simply call sage. You might have to reboot your machine for the docker permissions to kick in.

• As a Debian package (sudo apt install sagemath) if available: easy, works out of the box, but the version might be a bit behind depending on your machine. The current status of sagemath on debian is listed here.
• From source, but this is well-known to be a nightmare.

There is some extra documentation in this file in the caramba git repository.

magma

We have access to Magma. It should be installed on the desktop computers already. To install it on your own machine:

• Mail Emmanuel Emmanuel.Thome@inria.fr, and ask him to add your MAC address in the magma license file. To find your MAC address, see the procedure here.
• Once the license file is updated, you may copy magma files from the team’s machines: cd /tmp; rsync -a houblon.loria.fr:/usr/local/magma-X.XX-X . (replace X.XX-X by the needed magma version, currently avaible version is 2.27-7.)
• Copy the directory to your /opt tree: sudo cp -a --no-preserve=ownership /tmp/magma-X.XX-X /opt && rm -rf /tmp/magma-X.XX-X
• Change the ROOT variable in the magma executable (e.g. by hand; you will need to sudo)
• And link the executable in your /usr/local/bin directory: sudo ln -sf /opt/magma-X.XX-X/magma /usr/local/bin
• It works, verify it by running magma. If magma says “Magma is not authorised for use on this machine.”, that’s because your laptop is not authorized by the current magmapassfile. You should update it: replace the file (as root) /opt/magma-X.XX-X/magmapassfile by the newer one Emmanuel sent you.
• Happy coding!
• If you’re a happy vim user, you may be interested by Peter Schwabe’s syntax file for magma, visit http://www.cryptojedi.org/programming/index.shtml for further explanations. Alternatively, Luk Bettale wrote a magma mode for emacs, see https://github.com/ThibautVerron/magma-mode
• To update magma on your machine, follow step 2.

gurobi

Grid5000

Backups

Telephone

Printing/Scanning

To print documents, several options are available:

• Use the online interface https://print.inria.fr/ . Select Web Print on the left menu to submit a job. Afterwards you only have to go to one of the printers, log in, and release the job.
• From the team desktop machines, it should be possible to print directly from the desktop tools such as evince, or command line tools such as lp.
• On a linux laptop, once you’re on the wired network (see this step), you can automatically set up the printer from the gnome settings panel. As specified in the doc-si documentation, write in ~/.cups/client.conf (create this file if it doesn’t exist):

  ### ~/.cups/client.conf ###
  User <login Inria>
  AllowAnyRoot Yes
  ValidateCerts No
  ServerName cups-NGE.inria.fr
  

  You should then be able to see the printers in the Gnome settings (they’re called printer-color-nge and printer-bw-nge), and ctrl-P from a document works. This way you have access to a lot more options than through the web interface.

To scan a document, first go the the printer, flash your card, and select “Numerisation” then “Scan to my email”. You can change the default value (for example to black&white 300p). Then you press “Scan”. You can scan several pages in the same pdf file (choose “Numeriser page suivante”). At the end choose “Terminer”, and you will receive the file by email.

How do I set up a personal web page?

Hardware/software servicing: what is normal, what isn’t.

Laptop warranty

Laptops in the team come with a 5-year professional warranty. In case your laptop has any failure (e.g. a key doesn’t work, the fan makes a wheezing noise, the usb port is dead, the screen has a few dead rows, …) then you must have it fixed. Don’t be shy about using a service we paid for. Even if you don’t care, bear in mind that there’s a person who might use this laptop after you. To get a fix, post a ticket on helpdesk, or arrange with the manufacturer (Dell or HP) directly. There are pros and cons to both approaches. The service agreement with the manufacturer is 1-day on-site service so normally you can expect the fix to be quick. If you’re traveling, or if you’re abroad, it also works, although in that case you must arrange for the repair yourself, directly with the manufacturer. Note that normal battery ageing doesn’t count towards fixable defects, and in principle accidental damage doesn’t either (e.g. if you have a bike accident and your laptop breaks into pieces, it’s not covered), although in the latter case it occurs that minor breaks are usually accepted for repairs.

My computer does not work

That’s not normal. But the first thing you have to do is learn to qualify exactly what “doesn’t work”. Be accurate in your description.

Tell people about your problem and use the warranty if applicable (see above). Computers are our everyday work tools and should not be a nuisance in any way.

Regarding software failure of desktop machines in the group, since the machines are administered within the group, ask on mattermost. The team machines are generally stable, but shit happens from time to time.

Sage is not working

Did you install it from source? You were warned.

The ethernet cable or connector that goes to my computer is broken

The plastic tab that is meant to secure the male connector in place is slightly fragile. Every so often, it happens that people pull on the ethernet cables without paying attention to this tab, almost always breaking it. It’s a significant nuisance because it means that the cable comes off easily. Please change your cable in that case (next section).

Likewise, if your cable is severely damaged because you haven’t noticed for months that your chair wheels were destroying it (or maybe it was one of your predecessors in your office, who cares), you should:

1. Fix your desktop organization!
2. Get a new cable.

I don’t have an ethernet cable

There are spares in Emmanuel’s office (B246). Ask him so you won’t have to open all the boxes.

I don’t have spare power outlets/extenders

I don’t think there are any more spares in B246. Sometimes it’s worth checking under your desk - additional power outlets might be hidden there.

Other non-computer topics that might be worth mentioning.

My chair is catastrophically bad

Make a ticket on helpdesk (Demande aux Services techniques et généraux/Gestion du mobilier/Aménagement du poste de travail mobilier). Just like computers, chairs are our everyday work tools, and it’s unacceptable to not be comfortably seated.

I don’t have a whiteboard

Try and make a ticket on the helpdesk (same as for the chairs). Ask Emmanuelle, the team assistant, to get pens and erasers.

There’s leftover stuff in my office

You’re free to get rid of it. Please don’t leave it as leftover stuff for the next person after you.

How can I get rid of … ?

• Paper: use the paper bins in the office

• Large packages (cardboard, etc): there is a spot on the ground floor close to B006 that looks a bit like a closed counter. Just leave your (empty) boxes there.

• Plastic and other recyclable items: there are recyclable bins close to the main staircase next to the accueil, at each floor.

• Food: you can use the other bin in your office, but they aren’t emptied as often as the bins in the corridors.

I leave for vacation

In zimbra you can set up an automatic message. In the “Preferences” menu on the top, choose “Hors du bureau” on the left. Then you can set up the start and end date of your vacation, and write a message that will be automatically sent to people who write to you during this period. Don’t forget to write it in french and english.

I want to reserve a room

In zimbra, in the “Calendrier” top menu, choose “Nouveau rendez-vous”, then choose the subject and the participants. In the “Endroit” field, type “Nancy” then you will be suggested several rooms in the Nancy center.