Outlook and employee scheduled work hours
 

Outlook should capture the employee's start time and stop time (daily work
schedule) with the employee profile information so that others can have the
information available when scheduling meetings. This would also be helpful
for importing and exporting resource information to Microsoft Project.

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/comm....calendari ng

Outlook and employee scheduled work hours
 

CoachKA wrote:

Outlook should capture the employee's start time and stop time (daily
work schedule) with the employee profile information so that others
can have the information available when scheduling meetings.

Available where? Why does the free/busy inforrmation nor sufficient? What
type of server?
--
Brian Tillman

Outlook and employee scheduled work hours
 

The free/busy information is ok, but when scheduling a meeting the work
schedule of the individuals is not highlighted. Therefore, people tend to
schedule meetings after the time a person is available/in the office. This
causes problems when people are not co-located.

As to server, we are running the latest version of Exchange on Windows 2003.

"Brian Tillman" wrote:

CoachKA wrote:

Outlook should capture the employee's start time and stop time (daily
work schedule) with the employee profile information so that others
can have the information available when scheduling meetings.

Available where? Why does the free/busy inforrmation nor sufficient? What
type of server?
--
Brian Tillman

Outlook and employee scheduled work hours
 

CoachKA wrote:

The free/busy information is ok, but when scheduling a meeting the
work schedule of the individuals is not highlighted. Therefore,
people tend to schedule meetings after the time a person is
available/in the office. This causes problems when people are not
co-located.

If the person is disciplined in marking the times when s/he is out of the
office, would it not work? There is no way I know (although that doesn't
mean there's no way) for Outlook to show you the working days of multiple
mailboxes.
--
Brian Tillman

Outlook and employee scheduled work hours
 

I agree that there is currently no way to support this in Exchange/Outlook.
I also agree that a work around is to have people list a calendar event that
shows they are out-of-the-office or when they leave the office each day.
This particular suggestion is not new. Suggestions like this were made back
in Schedule+ days. I had been thinking about this after a recent upgrade to
Outlook 2003 and thought I would post the suggestion. I thought this was a
forum for suggestions.

"Brian Tillman" wrote:

CoachKA wrote:

The free/busy information is ok, but when scheduling a meeting the
work schedule of the individuals is not highlighted. Therefore,
people tend to schedule meetings after the time a person is
available/in the office. This causes problems when people are not
co-located.

If the person is disciplined in marking the times when s/he is out of the
office, would it not work? There is no way I know (although that doesn't
mean there's no way) for Outlook to show you the working days of multiple
mailboxes.
--
Brian Tillman

Outlook and employee scheduled work hours
 

CoachKA wrote:

I agree that there is currently no way to support this in
Exchange/Outlook. I also agree that a work around is to have people
list a calendar event that shows they are out-of-the-office or when
they leave the office each day. This particular suggestion is not
new. Suggestions like this were made back in Schedule+ days. I had
been thinking about this after a recent upgrade to Outlook 2003 and
thought I would post the suggestion. I thought this was a forum for
suggestions.

Yes, it is, and I never said you shouldn't propose the suggestion, since it
was your suggestion that started the thread. I was merely suggesting some
work-arounds in the mean time while you don't hold your breath waiting for
Microsoft to provide it.
--
Brian Tillman