Archive
Room and Equipment handling using MS-Exchange Resource Mailboxes: What the parameter AddNewRequestsTentatively means
-
It is an instruction to the calendarattendant, that seems to be conjured up by automateprocessing: autoupdate, but also, now together with, but still separate from, the resource booking assistant, by automateprocessing: autoaccept
-
It is an instruction relating only to meeting requests, not to meetings. But it is not the calendarattendant, but rather the resource booking assistant that decides what is to remain a request and what not (= what is to be accepted or denied, and thus to stop being a mere request and be promoted to a meeting). if there are no (mere) requests (since all requests, for whatever other settings, are either auto-accepted or auto-denied, so effectively automatically rendered into non-(not anymore) requests, the AddNewRequestsTentatively will have no effect on the calendar. It is these other settings, that may allow requests to remain requests. Even though the parameter name may sound like it is doing this, it is NOT AddNewRequestsTentatively that will turn off/override these other settings to make all incoming requests remain requests. It is rather automateprocessing: autoupdate (or a combination of automateprocessing: autoaccept and allbookinpolicy: $false and Allrequestinpolicy: $true (and even more so AllRequestOutOfPolicy: $true) that would do that.
-
However, the latter is the combination if have for pseudo-rooms where it is important that the delegate can collate requests in a calendar-format when deciding which to accept/deny, instead of having to cobble together a picture from forwarded meeting request messages.
-
Room and Equipment handling using MS-Exchange Resource Mailboxes: What the parameter AllowConflict means
-
NOT TRUE HERE? More info here, search “AllowConflicts”.
-
what will the effect be on non-recurring meeting requests? Will conflict in.stances (there are only instances with non-recurring meeting requests) still be denied? From the flowchart and when allowconflicts comes into play (only after automateprocessing: autoaccept (it does not come into play with automateprocessing:autoupdate) immediately before thresholds ) and that it still does not allow actual conflicts, it appears to me that allowconflicts should have been called “allow-a-recurring-meeting-request-to-be-not-outright-denied-if-it-has-conflict-instances-that-have-to-be-denied-(always-by-the-autoaccept-agent)-as-long-as-not-the-ConflictPercentageAllowed-and-MaximumConflictInstances-numbers-are-also-exceeded”. it was, however, with good reason not called: “allowdoublebooking” J
- That much about the theory. Now the Test results for AllowConflicts $true
-
What works: Allowconflicts does not prompt the autoprocessing: autoaccept (calendar booking assistant) to allow actual conflict instances (double bookings)) from recurring meeting requests.
-
What does not seem to work, but is not important right now: thresholds for conflict amounts are ignored, even if both are crossed
-
MaximumConflictInstances= 5
-
ConflictPercentageAllowed= 25% guides the calendar booking assistant in deciding whether a recurring meeting request gets
-
(10 conflict instances out of 20) still get accepted,
-
-
How to set the home page in your web browser
E.g. if you want to update your email start page from http://unccmail.uncc.edu to http://mail.uncc.edu.
in Safari, go to menu: Safari / Preferences / home page: type your updated page address in here and click OK. Visual walkthrough is e.g. here: http://www.youtube.com/watch?v=VIGocolMtzU.
Similarly in the preferences of all other common web browsers.
Sanako Study 1200 Workshop Fall 2011
Those who wanted to, but did not make it to the vendor training by Sanako’s David Golden (who gave us a basic orientation displaying functions of teacher screen and student screen and demonstrated basic activity functions and what happens at the student screen), might want to have a look at the unedited screencast footage (for Windows Media Player on Windows, if necessary, resort to LRC) I recorded during the entire 2 1/4-hour session:
- the first one recording the screen of a sample student station
- with an explanation of the student player at the beginning,
- the second one recording the screen of the teacher computer
- have a look at the end around 2:10:00 where we connect a group of students via screensharing and audio (headsets), so that a group, dispersed across the classroom, can orally collaborate on an MS-Word document that one student types into but all students see.
- The Sanako features used for this are from the dropdown: activity: discussion, and from the button: pc control:model student. Both can be combined with each other, and with a third feature, the capability to subdivide the class in multiple groups.
- This application I found useful when, before reviewing materials with one half of the class, I sent my more advanced learners off to a more independent and applied group writing task. I allows any member of the class to join the advanced group, no matter where they are located. It also forces the group members to communicate all the target language aurally to the model student. Finally, it affords them access (though not individually) to the language learning tools of a computer while working on their tasks
Sanako Study 1200 Teacher Guide
Taken directly from the Sanako documentation and posted here for your convenience (click on image for larger version), this practical cheat sheet is also available on the teacher podium.
Sanako Study 1200 Workshop Spring 2011
Those who wanted to, but did not make it to my introductory training for the newly installed Sanako Study-1200 in LRC COED434 might want to have a look at the unedited screencast footage of the teacher computer that I recorded during this session (for Windows Media Player on Windows, if necessary, resort to LRC PCs).
![owa test AddNewRequestsTentatively true automateprocessing not autoupdate maxduration outfofpolicy lrc calendar this looks not tentative_thumb[1] owa test AddNewRequestsTentatively true automateprocessing not autoupdate maxduration outfofpolicy lrc calendar this looks not tentative_thumb[1]](https://thomasplagwitz.com/wp-content/uploads/2011/08/owa-test-addnewrequeststentatively-true-automateprocessing-not-autoupdate-maxduration-outfofpol3.png?w=142&h=55)


