Archive for the ‘Reception-desk’ Category

Web browser popup blocker exceptions need configuring


  1. Which computers
    1. This I found on the Reception desk
    2. but isn’t that then also wrong on all student pcs which have the same base image?
  2. Which exceptions missing: I noticed immediately:
    2. should read
  3. Which browsers
    1. Example is IE9,
    2. But are others different?

Student email in Office365/ slow on reception desk computers

  1. Problem: Since last week (or so; interestingly, only individual users seem to have been affected at first), we seem to experiencing regular (but not consistent) issues with meeting requests mostly
    1. slowness
    2. browser-specific behavior
      1. internet explorer 9: crashes
      2. chrome: crashes
      3. Firefox: (sometimes just seems to hang, with some coercion can bring up an “unresponsive script” warning dialogue that a script is hanging: image
  2. Workaround:
    1. Best so far: if you see the Firefox warning dialogue, check “do not warn again” and click on “continue”(?)
    2. we will try to look into common browser configuration (like popup blockers).
  3. Root cause: ?
    1. Firefox provides only this help on unresponsive script error;
    2. the slowness could be in the actual script, on the client, in the network, on the server…
  4. Resolution: ?

New supervisor role for senior LRC Assistants

  1. A new LRC Assistant list, sorted by hire date, has been posted on the inside LRC reception desk. Use it to determine who is currently the most senior LRC assistant at the desk. The current most senior LRC assistant serves as supervisor and always wears the green supervisor badge pictured below. When the supervisor leaves, the supervisor passes on the badge to the next senior LRC assistant in line.
  2. image
  3. Supervisors do not have to perform clerical tasks (meeting requests, equipment handling, etc.) as long as there are enough less senior LRC assistants to handle the client load. Rather, supervisors monitor less experienced LRC assistants operating the reception desk computers, equipment etc. , help train them and avoid mistakes.

Checklist for Vixia cameras (11-14)

  1. Parts
    1. Battery
    2. SD Memory Card
    3. Battery Charger
    4. Power cable
    5. USB cable
    6. vixia-components-CIMG0005
  2. Test the Functionality
    1. Start camera
    2. Record for 5 seconds clip_image001
    3. Playback:  clip_image002
  3. Maintenance
    1. Charge battery
    2. Initialize sd card: Sd-card like so.

Checklist for heavy tripods (01-04)

  1. Are all Parts there?
    1. Tripod
    2. Head plate
    3. Screws /wing nuts
    4. Handleclip_image001
  2. Test the Functionality:
    1. Attach a camera to tripod.
    2. Move camera in all directions (top/bottom, left/right…)
  3. Maintenance:
    1. reduce tripod size again to its most compact position.
    2. Close all levers so that legs arrest.

Checklist for Rebel cameras (17/18/19/20)

2013/12/23 1 comment
  1. Parts
    1. Battery
    2. SD Memory Card
    3. Battery Charger
    4. USB cable
    5. Lens


  2. Test the Functionality
    1. Turn camera on
    2. Set to video
    3. Take a 5sec video
    4. clip_image002
    5. clip_image003
    6. Playback clip_image004
  3. Maintenance
    1. Charge battery
    2. Initialize sd card like so.

Use CTRL+TAB to switch between tabs in Chrome kiosk fullscreen mode

  1. On the reception desk, when you open the NINERMAIL after logging into 49erexpress, Chrome opens NINERMAIL in another full screen tab (which hides the 49erexpress tab) – unlike full screen Internet  Explorer, which opened NINERMAIL in a new window, but which we had to abandon with the introduction of offfice365. 
  2. The 49erepxress tab is hidden, but still there, and you can switch between full screen tabs wit hthe keyboard shortcut CTRL+TAB (hold CTRL and pressing TAB repeatedly will cycle through all open Chrome tabs).
  3. So when a client is finished with NINEMAIL (meeting request), have them not only log out of NINERMAIL, but also CTRL+TAB back to the 49erexpress tab to log them out of 49express (and browse from the result window to the Sign-in link to be ready for the next client).
  4. No need to close the NINERMAIL tab. Next time somebody logs in to 49erexpress tab, Chrome will recycle the previous NINERMAIL tab.

Finding a balance between speed of log-in and readiness on help desk computers

  1. Problem:
    1. The LRC reception desk has 3 computers, each with 2 screens, one client-facing,  that, when not shared during collaboration for clerical tasks, display (LRC assistants have been instructed which screen has to show which information) LRC-related information (LRC calendar, home page with news and FAQs, slide show with signs).
    2. However, when a teacher was bringing student to Spanish tutor after tutoring hours, I  noticed,  that no LRC calendar was visible at reception desk (SAFARI on rightmost computer), nor could be loaded easily.
    3. Upon my asking, LRC assistant reported, Firefox never comes up correctly on her computer.
    4. What I could observe: Firefox came up with 2 windows w/o preconfigured tabs. image
    5. Safari came  up with 2 windows , also empty.image
  2. Root cause:
    1. It turned out that other students did not have this issue when logging in on the computers.
    2. It also turned out that the offending student’s profile had been frozen prematurely (in an obsolete state not incorporating changes we had to do during the term to maintain functionality of the reception desk computers in a changing campus IT environment).

  3. Workaround: Unfreeze the computer, delete the prematurely frozen profiles, have the student log in to recreate it using current default user settings, freeze the computer, to make the computer, 3 weeks before classes end…
  4. Solution: not sure I have one.
    1. Trying to have everything set up stably at term start is not the solution, but the problem.
    2. How can agility be increased?
      1. LRC assistants need to report problems. They may need better training to be aware of problems, and need an incentive to report problems, and a culture where reporting problems is not considered a problem in itself, but an achievement.
      2. The LRC lost its Symantec-Ghost imaging infrastructure which it could not only use for the lab PCs, but also to maintain 3 identical computers at its reception desk. This requirement for imaging was not considered during the recent upgrade of the labs imaging infrastructure, and we do not know how to get this capability back.